Kontakt

Ansicht
Dokumentation

ISU_UMC_ODATA - BAdI: SAP Multichannel Foundation for Utilities OData Service

ISU_UMC_ODATA - BAdI: SAP Multichannel Foundation for Utilities OData Service

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) ISU_UMC_ODATA is called in the Data Provider extension class for each OData entity that is being requested. This BAdI can be used to create new or modify existing OData entity implementations for SAP Multichannel Foundation for Utilities. The purpose of the BAdI is to provide the implementation specific to the entity name.

SAP provides a default Gateway Service Builder project for SAP Multichannel Foundation for Utilities OData Services. You can redefine the default project ERP_ISU_UMC or create your own project using service extensibility. You can maintain additional entities, entity attributes, and navigation properties in the Data Model of the project. You do this in the Gateway Service Builder (transaction SEGW). This BAdI implementation provides the necessary infrastructure to extend the existing SAP Multichannel Foundation for Utilities implementation with the additional functionality.

By default, all BAdI implementations are active and flagged as default implementations. The default implementation is executed automatically. However, you can create your own implementation with the same filter value and your code is executed instead of the default code.

This BAdI is filter-dependent. The filter is based on the name of the entity, for example, ENTITY_NAME = Accountand SERVICE_NAME = ERP_ISU_UMC or SERVICE_NAME = ERP_ISU_UMC_PUBLIC_SRV.

If you want to overwrite standard behavior, you must create a new BAdI implementation with the proper filter value. This implementation is then called instead of a standard one. The BAdI definition is based on the interface IF_ISU_UMC_ODATA_BADI. This interface has only one method GET_INSTANCE. This method provides an instance of a Multichannel service implementation class to 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 have the possibility of redefining all the methods of both IF_ISU_UMC_ODATA_BADI and IF_ISU_UMC_ODATA_IMPL interfaces to replace the SAP default functionality with your own. Also, some of the implementation classes provide additional methods which can be redefined. If you want to use the code provided by SAP, we recommend that you call methods of the super class in your implementation, wherever possible. That will ensure that all of the corrections provided by SAP are used in your new code.

  • Class: CL_ISU_UMC_ODATA_ABSTRACT
  • Interfaces:
  • IF_ISU_UMC_ODATA_BADI

  • IF_ISU_UMC_ODATA_IMPL

  • For information on 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.






General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4575 Date: 20240523 Time: 170009     sap01-206 ( 140 ms )