Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
PM-WOC-MO (Application Component) Maintenance Orders⤷
IWO_BAPI_EX (Package) BAPI Interfaces ALM Order
IMG Activity
| ID | IBAPI_ALM_ORD_MODIFY | BAdI: Adapt Transferred Data to BAPI |
| Transaction Code | S_PLN_16000340 | (empty) |
| Created on | 20020507 | |
| Customizing Attributes | IBAPI_ALM_ORD_MODIFY | BAdI: Adapt Transferred Data to BAPI |
| Customizing Activity | IBAPI_ALM_ORD_MODIFY | BAdI: Adapt Transferred Data to BAPI |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | IBAPI_ALM_ORD_MODIFY |
Use
The Business Add-In (BAdI) IBAPI_ALM_ORD_MODIFY can be used to check and change the transferred data.
The BAdI is called up after the transfer structure has been converted in structure used internally. However, the method table is only only interpreted after the BAdI has been called up. The methods remain in the transferred format. Additional data can be transferred using the table EXSTENSION_IN. Only then is the data check performed.
With this BAdI, for example, data from SAP ERP can be read in addition to the transferred data, or decoding tables can be used to convert the data to the required format.
Requirements
Standard settings
The following tables are transferred:
EXTENSION_IN Reference structure for BAPI Parameter ExtensionIn / ExtensionOut
CT_METHODS Table with processing methods BAPI interface
CT_HEADER Table with order header data BAPI interface
CT_HEADER_UP Table with update flags for order header BAPI interface
CT_HEADER_SRV Table with service data
CT_HEADER_SRV_UP Order BAPIS in PM/CS: service-specific data, ext. ext. structure
CT_USERSTATUS Structure for maintenance-/service order, user status change
CT_PARTNER Order BAPIs in PM/CS: Table type for partner data (Multiorder)
CT_OPERATION Table with operation data BAPI interface
CT_OPERATION_UP Table with update flags for operations BAPI interface
CT_RELATION Table with relationships BAPI interface
CT_RELATION_UP Table with update flags for relationships BAPI interface
CT_COMPONENT PM/CS BAPI order components (table type)
CT_COMPONENT_UP Table with update flags for components BAPI interface
CT_TEXT Table with text data for the BAPIs in PM/CS
CT_TEXT_LINES Tables with text lines for the BAPIs in PM/CS
CT_MESSAGES Application log: Table with messages
The table EXTENSION_IN corresponds to the standard structure for BAPI function enhancements. The usable structures can be seen in the documentation for the BAPIs.
Activities
The tables can be changed as you like in the BAdI. The BAPI then checks the data for consistency. You can also add additional methods from the methods table.
If processing should be terminated, then write a notification of category 'A' or 'E' in the table CT_MESSAGES.
Example
Business Attributes
| ASAP Roadmap ID | 153 | Design enhancements |
| 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 | IBAPI_ALM_ORD_MODIFY | 0 | HLA0006648 O | |
| SIMG | IBAPI_ALM_ORD_MODIFY | 1 | HLA0009595 | Service Processing |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020507 |
| SAP Release Created in | 110 |
