Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PM-WOC (Application Component) Maintenance Processing⤷
MSAM_MOREP (Package) MSAM for Handheld - Data Replication
IMG Activity
| ID | BADI_EAM_MSAM_PARTNE | BAdI: Partner |
| Transaction Code | S_EB5_05000311 | (empty) |
| Created on | 20090324 | |
| Customizing Attributes | BADI_EAM_MSAM_PARTNE | Customer BAdI for Partner |
| Customizing Activity | BADI_EAM_MSAM_PARTNE | Customer BAdI for Partner |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_EAM_MSAM_PARTNE |
Use
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 Mobile data 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 Mobile functionality 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 PREPROCESS are 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.
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.
Requirements
Standard settings
Activities
Following are the steps invovled:
- Go to transaction SE19.
- 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.
Example
See also
BAdI interface IF_EX_EAM_MSAM_PARTNER.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | BADI_EAM_MSAM_PARTNE | 0 | HLA0009595 O | |
| SIMG | BADI_EAM_MSAM_PARTNE | 1 | HLA0009533 | Maintenance Processing |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20091202 |
| SAP Release Created in | 605 |
