SAP ABAP IMG Activity FDM_COLL_POST_DATA (BAdI: Post and Change in Substitute System)
Hierarchy
SAP_FIN (Software Component) SAP_FIN
   FIN-FSCM-COL-AR (Application Component) Accounts Receivable Accounting Process Integration
     FDM_AR_COLL_MIRROR (Package) SAP Collections Management - Data from Non-SAP System
IMG Activity
ID FDM_COLL_POST_DATA BAdI: Post and Change in Substitute System  
Transaction Code S_EB5_05000159   (empty) 
Created on 20090223    
Customizing Attributes FDM_COLL_POST_DATA   BAdI: Post and Change in Substitute System 
Customizing Activity FDM_COLL_POST_DATA   BAdI: Post and Change in Substitute System 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FDM_COLL_POST_DATA    

Use

You use this Business Add-In (BAdI) in the component SAP Collections Management (FIN-FSCM-COL). With this BAdI, you can change the system behavior for a customer that is defined in the substitute system when posting documents for document data from non-SAP systems or SAP systems. You can use the following three methods:

  • In method PAIRING you define for the repeated loading from the original system which pairs of document data (old/new) are mapped.
  • In method COMPARE you specify the result of comparing old and new document data.
  • In method DOC_TO_ACC you define how the transferred data is transferred to the FI documents of the substitute system.

Requirements

You have defined and implemented a procedure with which the program for Transferring Document Data from Original Systems (FDM_COLL_GET_DOCUMENTS) loads the transaction data into the substitute system.

Standard settings

The system uses the fallback class CL_FDM_COLL_POST_FB.

Activities

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

If you create your own implementation of the BAdI, you are advised to copy and adapt the fallback class. It uses methods with the same names from a service class that are independent of each other. You should re-use these if possible.

Example

Transfer of Additional Document Information.

See also:

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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 FDM_COLL_POST_DATA 0 AXA0000106 O  
SIMG FDM_COLL_POST_DATA 1 XBI0000001 Accounts Receivable Accounting Process Integration 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20090614 
SAP Release Created in 605