Kontakt

Ansicht
Dokumentation

BADI_EAM_MSAM_APPL_C - BAdI: Application Customizing

BADI_EAM_MSAM_APPL_C - BAdI: Application Customizing

ABAP Short Reference   General Data in Customer Master  
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 back end is provided to communicate with the middleware and the mobile client. Within these BAPI wrappers, the standard Service and Asset management fMobile functionality is provided and additionally the Business Add-In calls are provided to facilitate enhancement or replacement.

The following BAPI wrappers are available for the mobile-specific back-end application customizing:

  • MSAM10_EQUIP_PROFILE_GETLIST - Get the list of template equipment profiles
  • MSAM10_EQUIP_PROFILE_GETDETAIL - Get the details of template equipment profiles
  • MSAM10_CUST_ORD_PROF_GETLIST - Get the list of Order Processing Profiles
  • MSAM10_CUST_ORD_PROF_GET,, - Get the details of Order Processing Profiles
  • MSAM10_NOTIF_PROFILE_GETLIST - Get the list of Notification Profiles
  • MSAM10_NOTIF_PROFILE_GETDETAIL - Get the details of Notification Profiles
  • MSAM10_APPL_CUST_GETLIST - Get the list of applications
  • MSAM10_APPL_CUST_GETLIST - Get the details of backend application customizing

,,

Implementing Business Add-In BADI_EAM_MSAM_APPL_CUST not only allows you to enhance the standard Service and asset management for Mobilefunctionality for application customizing, 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.

  • EQUI_PRF_GETLIST_PREPROCESS

  • EQUI_PRF_GETLIST_OUTBOUND

  • EQUI_PRF_GETDETAIL_PREPROCESS

  • EQUI_PRF_GETDETAIL_OUTBOUND

  • ORDER_PRF_GETLIST_PREPROCESS

  • ORDER_PRF_GETLIST_OUTBOUND

  • ORDER_PRF_GETDETAIL_PREPROCESS

  • ORDER_PRF_GETDETAIL_OUTBOUND

  • NOTIF_PRF_GETDETAIL_OUTBOUND

  • NOTIF_PRF_GETDETAIL_PREPROCESS

  • NOTIF_PRF_GETLIST_OUTBOUND

  • NOTIF_PRF_GETLIST_PREPROCESS

  • APPL_CUST_GETDETAIL_OUTBOUND

  • APPL_CUST_GETDETAIL_PREPROCESS

  • APPL_CUST_GETLIST_OUTBOUND

  • APPL_CUST_GETLIST_PREPROCESS

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 X value 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.

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_FUNCLOCATION .
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_APPL_CUST






rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 5480 Date: 20240523 Time: 223422     sap01-206 ( 72 ms )