Kontakt

Ansicht
Dokumentation

FMCA_PS_ODATA - BAdI: SAP Multichannel Foundation for Public Sector OData Service

FMCA_PS_ODATA - BAdI: SAP Multichannel Foundation for Public Sector OData Service

CPI1466 during Backup   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI), FMCA_MC_ODATA, is called in the data provider extension class for each OData entity requested. You can use this BAdI to create new or modify existing OData entity implementations for SAP Multichannel Foundation for Public Sector. The purpose of this BAdI is to provide the implementation for a specific entity.

SAP provides a default Gateway Service Builder project for SAP Multichannel Foundation for Public Sector OData Services. You can redefine the default project ERP_FMCA_MC or create your own project using service extensibility. You can maintain additional entities, entity attributes, and navigation properties in the data model for the project. You do this in the Gateway Service Builder. This BAdI implementation provides the necessary infrastructure to incorporate the additional functions in the existing SAP Multichannel Foundation for Public Sector implementation.

All BAdI implementations are active as a default setting and are flagged as default implementations. The default implementation is executed automatically. However, you can create your own implementation with the same filter value, where the system executes your code instead of the default code.

This BAdI is filter-dependent. The filter is based on the entity name.

BAdI Implementations

The following is a list of all the BAdI implementations:

  • FMCA_MC_ODATA_ACCOUNT - Implementation for the Account Entity
  • FMCA_MC_ODATA_ACCOUNTALERT - Implementation for the AccountAlert Entity
  • FMCA_MC_ODATA_ACCOUNTBALANCE - Implementation for the AccountBalance Entity
  • FMCA_MC_ODATA_ACCOUNTCONTACT - Implementation for the AccountContact Entity
  • FMCA_MC_ODATA_ACCOUNTRELATIONS - Implementation for the AccountRelationship Entity
  • FMCA_MC_ODATA_ACCOUNTSEX - Implementation for the AccountSex Entity
  • FMCA_MC_ODATA_ACCOUNTTITLE - Implementation for the AccountTitle Entity
  • FMCA_MC_ODATA_ACCOUNTTYPE - Implementation for the AccountType Entity
  • FMCA_MC_ODATA_ACCTRELTYPE - Implementation for the AccountRelationshipType Entity
  • FMCA_MC_ODATA_ADDITIONALINFO - Implementation for the ContactAddtionalInfo Entity
  • FMCA_MC_ODATA_ADDRDEPEMAIL - Implementation for the AccountAddressDependentEmail Entity
  • FMCA_MC_ODATA_ADDRDEPFAX - Implementation for the AccountAddressDependentFax Entity
  • FMCA_MC_ODATA_ADDRDEPMOBILE - Implementation for the AccountAddressDependentMobilePhone Entity
  • FMCA_MC_ODATA_ADDRDEPPHONE - Implementation for the AccountAddressDependentPhone Entity
  • FMCA_MC_ODATA_ADDRESS - Implementation for the AccountAddress Entity
  • FMCA_MC_ODATA_ADDRESSTYPE - Implementation for the AddressType Entity
  • FMCA_MC_ODATA_ADDRESSUSAGE - Implementation for the AccountAddressUsage Entity
  • FMCA_MC_ODATA_ADDRINDEMAIL - Implementation for the AccountAddressIndependentEmail Entity
  • FMCA_MC_ODATA_ADDRINDFAX - Implementation for the AccountAddressIndependentFax Entity
  • FMCA_MC_ODATA_ADDRINDMOBILE - Implementation for the AccountAddressIndependentMobilePhone Entity
  • FMCA_MC_ODATA_ADDRINDPHONE - Implementation for the AccountAddressIndependentPhone Entity
  • FMCA_MC_ODATA_BANK - Implementation for the Bank Entity
  • FMCA_MC_ODATA_BANKACCOUNT - Implementation for the BankAccount Entity
  • FMCA_MC_ODATA_BUSINESSDIR - Implementation for the BusinessDirectory Entity
  • FMCA_MC_ODATA_COMMCATEGORY - Implementation for the CommunicationCategory Entity
  • FMCA_MC_ODATA_COMMMETHOD - Implementation for the CommunicationMethod Entity
  • FMCA_MC_ODATA_COMMPREFERENCE - Implementation for the CommunicationPreference Entity
  • FMCA_MC_ODATA_CONTACTACTION - Implementation for the ContactAction Entity
  • FMCA_MC_ODATA_CONTACTCLASS - Implementation for the ContactClass Entity
  • FMCA_MC_ODATA_CONTACTPRIORITY - Implementation for the ContactPriority Entity
  • FMCA_MC_ODATA_CONTACTTYPE - Implementation for the ContactType Entity
  • FMCA_MC_ODATA_CONTRACCBAL - Implementation for the ContractAccountBalance Entity
  • FMCA_MC_ODATA_CONTRACTACCOUNT - Implementation for the ContractAccount Entity
  • FMCA_MC_ODATA_CONTRACTOBJ_FACT - Implementation for the ContractObjectFact Entity
  • FMCA_MC_ODATA_CONTRACT_OBJECT - Implementation for the ContractObject Entity
  • FMCA_MC_ODATA_CORRESPONDENCE - Implementation for the Correspondence Entity
  • FMCA_MC_ODATA_COTYPE - Implementation for the CorrespondenceType Entity
  • FMCA_MC_ODATA_COUNTRY - Implementation for the Country/Region Entity
  • FMCA_MC_ODATA_FBATTACHMENT- Implementation for the FormBundleAttachment Entity
  • FMCA_MC_ODATA_FILINGOBLIGATION - Implementation for the FilingObligation Entity
  • FMCA_MC_ODATA_FORMBUNDLEHDR - Implementation for the FormBundleHeader Entity
  • FMCA_MC_ODATA_FORMBUNDLERULE - Implementation for the FormBundleRule Entity
  • FMCA_MC_ODATA_FORMBUNDLETYPE - Implementation for the FormBundleType Entity
  • FMCA_MC_ODATA_INVOICE - Implementation for the Invoice Entity
  • FMCA_MC_ODATA_INVOICEPDF - Implementation for the InvoicePDF Entity
  • FMCA_MC_ODATA_ LANGUAGE - Implementation for the Language Entity
  • FMCA_MC_ODATA_PAYMENTDOCITEM - Implementation for the PaymentDocumentItem Entity
  • FMCA_MC_ODATA_PAYMENTDOCUMENT - Implementation for the PaymentDocument Entity
  • FMCA_MC_ODATA_PAYMENTONACCOUNT - Implementation for the PaymentOnAccount Entity
  • FMCA_MC_ODATA_PAYMENTSTATUS - Implementation for the PaymentStatus Entity
  • FMCA_MC_ODATA_PAYMETHOD - Implementation for the PaymentMethod Entity
  • FMCA_MC_ODATA_PCARD - Implementation for the PaymentCard Entity
  • FMCA_MC_ODATA_PCARDTYPE - Implementation for the PaymentCardType Entity
  • FMCA_MC_ODATA_PERIOD - Implementation for the Period Entity
  • FMCA_MC_ODATA_P_FORMBUNDLEHDR - Implementation for the FormBundleHeader Entity (Anonymous

Service)

  • FMCA_MC_ODATA_P_FORMBUNDLERULE - Implementation for the FormBundleRule Entity (Anonymous

Service)

  • FMCA_MC_ODATA_P_PAYMENTDOCITEM - Implementation for the PaymentDocumentItem Entity in

(Anonymous Service)

  • FMCA_MC_ODATA_P_PAYMENTDOCMNT - Implementation for the PaymentDocument Entity in

(Anonymous Service)

  • FMCA_MC_ODATA_REGION - Implementation for the Region Entity
  • FMCA_MC_ODATA_USER - Implementation for the User Entity
  • FMCA_MC_ODATA_USERGROUP - Implementation for the UserGroup Entity
  • FMCA_MC_ODATA_USERPRIVILEGE - Implementation for the UserPrivilege Entity
  • FMCA_MC_ODATA_USRPRVLGITEM - Implementation for the UserAssignedPrivilege Entity

If you want to overwrite standard behavior, you must create a new BAdI implementation with the correct filter value. This implementation is then called instead of the standard one. The BAdI definition is based on the interface IF_ISU_UMC_ODATA_BADI. This interface contains only one method GET_INSTANCE. This method provides an instance of a Multichannel service implementation class for the standard data provider class (class with the suffix DPC_EXT). You can define your own entity-based service implementation class with the inheritance to the existing class that was assigned to the BAdI implementation by default. In your service implementation class, you can redefine all the methods in both IF_ISU_UMC_ODATA_BADIand IF_ISU_UMC_ODATA_IMPL interfaces to replace the SAP default functionality with your own. Some of the implementation classes also provide additional methods that can be redefined. If you want to use the code provided by SAP, we recommend that you call methods from the super class in your implementation, wherever possible. That ensures that all of the corrections provided by SAP are used in your new code.

See Also

Class: CL_ISU_UMC_ODATA_ABSTRACT

Interfaces:

  • IF_ISU_UMC_ODATA_BADI
  • IF_ISU_UMC_ODATA_IMPL

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP NetWeaver Platform on the SAP Help Portal at: http://help.sap.com/nw_platform. Choose a release and then Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View → Application Server → Application Server ABAP → Application Development on AS ABAP → ABAP Customer Development → Enhancement Framework.






ABAP Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 10780 Date: 20240523 Time: 201718     sap01-206 ( 136 ms )