Kontakt

Ansicht
Dokumentation

BADI_EAM_MSAM_PARTNE - BAdI: Partner

BADI_EAM_MSAM_PARTNE - BAdI: Partner

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Maintenance Processing (PM-WOC)component.

For Service and asset management for Mobile, standard remote-enabled BAPI wrappers in the ERP backend are provided to communicate with the middleware and the mobile client. Within these BAPI wrappers, the standard MSAM functionality is provided and additionally the Business Add-In calls are provided to facilitate enhancement or replacement.

The following BAPI wrappers are provided for the Service and asset management for Mobiledata object partner:

  • ,,MSAM10_PARTNER_GETLIST
  • ,,MSAM10_PARTNER_GETDETAIL

Implementing Business Add-In BADI_EAM_MSAM_PARTNER not only allows you to enhance the standard Service and asset management for Mobilefunctionality for Partner data object, but also to replace it with your own functionality if you choose to.

The BAdI uses the following methods. Call to these BAdI methods is in their respective BAPI wrappers.

  • PARTNER_GETLIST_PREPROCESS

  • PARTNER_GETLIST_OUTBOUND

  • PARTNER_GETDETAIL_PREPROCESS

  • PARTNER_GETDETAIL_OUTBOUND

All methods having the suffix PREPROCESSare called before SAP standard code and can be used for inbound mapping and/or to skip the standard EAM logic. The user can skip the SAP standard code provided inside the BAPI wrapper by filling the Xvalue for field EV_SKIP_STANDARD. In this case customer can decide to have his own implementation through the outbound methods in each BAPI wrapper.

All methods having the suffix OUTBOUND are called after the SAP standard code and can be used for outbound mapping and/or to enhance standard EAM logic.

CUSTOMER_BTE_PUSH

VENDOR_BTE_PUSH

Above two BAdI methods can be used to have any enhancements before calling the middleware.

This Business Add-In has been incorporated in the enhancement spot ES_MSAM.

Following are the steps invovled:

  1. Go to transaction SE19.
  2. Create an enhancement implementation for the enhancement spot ES_MSAM and subsequently create an implementing class for the Business Add-In BADI_EAM_MSAM_PARTNER.

Information about the implementation of BAdIs in the context of the Enhancement Concept is available in the SAP Library for SAP NetWeaver under BAdIs → Implementation.

For more information about the procedure, see the SAP Library under Enhancement Framework → Business Add-Ins (BAdIs) → BAdIs Concept → Screen Enhancements.

When the BAPI wrappers are executed, the code you created in the Business Add-In implementation is run through.

BAdI interface IF_EX_EAM_MSAM_PARTNER.






Fill RESBD Structure from EBP Component Structure   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 3640 Date: 20240523 Time: 233337     sap01-206 ( 47 ms )