Ansicht
Dokumentation

/CEM/EE_INBADAP_CUST - BAdI: Enhancement of Inbound Document Processing

/CEM/EE_INBADAP_CUST - BAdI: Enhancement of Inbound Document Processing

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Entitlement Management (CRM-EM) component.

This BAdI enables you to modify and populate the inbound due-list record with field values from the incoming billing document. You will typically use this feature in conjunction with extensions to both the inbound data structure as well as the entitlement structure.

The implementations are filter dependent; filter values are the entitlement program types.

The following methods are available as part of this BAdI:

  • EXT_DOC_BASED_CHECK
Checks whether the document should be processed further or not (e. g., checks whether this is an error in account posting (within CRM system))
  • EXT_DOC_ITM_BASED_CHECK
Checks whether the document item should be processed or not (Checks whether the item is relevant for deposit entitlements)
  • EXT_DOC_MAPPING_CEMI_DATA
Map the document + item to inbound structure
  • EE_APPL_BASED_CHECK
Another check at application level can be performed here (Check whether the billing document is already processed by entitlements, and are there any duplication in the inbound records)
  • EE_BEFORE_CEMI_CALL
Any last changes to the inbound records

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.






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

Length: 3654 Date: 20240616 Time: 195949     sap01-206 ( 71 ms )