Ansicht
Dokumentation

CRM_BADI_ORDERSAVE - BAdI: Transfer Customer-Specific Fields to Middleware

CRM_BADI_ORDERSAVE - BAdI: Transfer Customer-Specific Fields to Middleware

General Material Data   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is called during saving of a transaction, before the objects are transferred to CRM Middleware. If you have created your own data tables for the transactions, you can modify this BAdI so that the system also uploads your specific data when it saves the transaction.

Performance Considerations

Since the UI waits for the save to be completed, you should keep performance in mind, especially when reading document data, when you only have the GUID as a parameter. Since this BAdI is called for each transaction category, avoid unnecessary code for transaction categories.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Modify the method CHANGE_BEFORE_UPDATE.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

The standard activity does not contain a field for product information but your company requires that the product number be entered in the activity. You have created a table so that the product number is included in the activity. To ensure that this data is saved and transferred to CRM Middleware, you need to modify this business add-on.

You can find example implementations in the BAdI Builder on the Enhancement Spot Element Definitions tab in the Implementation Example Classes section.






Fill RESBD Structure from EBP Component Structure   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 2238 Date: 20240523 Time: 172544     sap01-206 ( 108 ms )