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_SERVER | BAdI: Server-Driven Object Keys |
| Transaction Code | S_EB5_05000313 | (empty) |
| Created on | 20090324 | |
| Customizing Attributes | BADI_EAM_MSAM_SERVER | Customer BAdI for Server Driven object keys |
| Customizing Activity | BADI_EAM_MSAM_SERVER | Customer BAdI for Server Driven object keys |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_EAM_MSAM_SERVER |
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 Service and asset management for Mobile functionality is provided and additionally the Business Add-In calls are provided to facilitate enhancement or replacement.
The following API is provided to fetch the Service and asset management for Mobile data object keys and RFC destinations to which the keys need to be pushed.
MSAM_SERVER_DRIVEN_TRIGGER - Trigger key push to middleware
Implementing Business Add-In BADI_ EAM_MSAM_SERVER_DRIVEN not only allows you to enhance the standard Service and asset management for Mobile functionality for server driven object keys, but also to replace it with your own functionality if you choose to.
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_SERVER_DRIVEN .
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_SERVER_DRIVEN
Requirements
Standard settings
Activities
Example
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_SERVER | 0 | HLA0009595 O | |
| SIMG | BADI_EAM_MSAM_SERVER | 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 |
