Ansicht
Dokumentation
LCM_BOINT_LT_POSTCRT - Custom Implementation After Creating Legal Transaction
CPI1466 during Backup General Material DataThis documentation is copyright by SAP AG.
Use this Business Add-In in CM-LT component to implement any custom logic after creating a legal transaction from an integrated business object.
This BAdI is triggered after SAVE of Legal Transaction asynchronously. Hence logging of error messages or reprocessing is required explicitly.
To create a BAdI implementation, you can use the transactions SE18 or SE19, or you can use the Custom Logic app in the front-end system. If you use the Custom Logic app, the following applies:
- The app provides a special ABAP language version ABAP for Key Users. This makes the implementation of BAdIs for business experts and implementation consultants easier.
- The app ensures that you can use only released interfaces.
If you use the transactions SE19 or SE18 to create a BAdI implementation, the implementation is not visible in the Custom Logic app.
If several BAdI implementations exist, the system runs through the implementations in the following order:
- Implementations created in the transactions SE18 or SE19.
- Implementation created in the Custom Logic app.
You have a valid user with the required authorizations.
- In the standard system, the BAdI is not active.
- The BAdI is filter-independent.
- With the app Custom Fields and Logic, you can create exactly one active implementation.
BAdI method implementation:
Use this method to implement a custom logic for a legal transaction that is created through an integrated business object.
Importing Parameters: LGLCNTNTMINTEGRATIONVARIANT (Type - LCM_INTEGRATION_TYPE) - You can use this parameter to define the integration variant.
Importing Parameters: LEGALTRANSACTION (Type - LCM_LEGALTR_ID) - You can use this parameter to define the legal transaction ID.
Importing Parameters: LGLCNTNTMLINKDOBJ (Type - LCM_LINKEDOBJECT_ID) - You can use this parameter to define the linked object ID.
Importing Parameters: LGLCNTNTMKEYVALUEPAIR (Type - LCM_T_KEY_VALUE_PAIR) - This is the binding context or attributes that are passed from source application.
Importing Parameters: LGLCNTNTMINTEGMAPPINGVARIABLE (Type - LCM_S_BOINT_LT_MAPPING_VAR) - You can use this parameter to map the variable.
Changing Parameters: MESSAGES (Type - BAPIRETTAB) - You can use this parameter to add any type of messages (success or error) that might occur during the execution.
Please refer to the example class implementation CL_LCM_BOINT_EXMP_POST_UPDATE related to this BAdI.
Addresses (Business Address Services) ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 2978 Date: 20240523 Time: 190204 sap01-206 ( 35 ms )