We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

EXIT_SAPLCRV5_001 -

EXIT_SAPLCRV5_001 -

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

This function module exit runs when reservation data is sent from SAP APO, immediately before the APO Core Interface (CIF) transfers the data to ERP processing. The exit has full control over all interface structures, which means that it can also add or delete lines. The data is not changed again after this exit has run.

This exit can be used in the following cases:

  1. You want to map ERP data in SAP APO in a different way to the mapping standard implemented in the APO Core Interface. You can use this exit to populate or delete certain fields for the APO interface differently from the CIF standard, for example. The exit can access all relevant interface data You can see the individual fields from the exit interface.
  2. You want to transfer data to the ERP system that does not exist in the standard or that is not transferred as standard. This exit allows you to contain processing this additional data in the ERP system.
You can enhance the interface individually by using the table parameter RVA, which is not used as standard. Create the customer include CI_APOINA with the relevant fields and populate this from SAP APO. For this, you need to create corresponding customer includes in SAP APO and provide the data by using an exit. To do this, use the BAdI /SAPAPO/SMOY_PUB_APP with method APPENDRESERVATION in SAP APO.





ROGBILLS - Synchronize billing plans   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 1447 Date: 20200923 Time: 053946     sap01-206 ( 53 ms )