Ansicht
Dokumentation
EXIT_SAPLF050_009 -
ROGBILLS - Synchronize billing plans ABAP Short ReferenceThis documentation is copyright by SAP AG.
Incoming IDoc: Changing fields in the structures for parking documents.
This exit can be called up by all IDocs with message types FIDCC1 and FIDCC2.
The prerequisite for this is that in the user-exit 004 and/or 006, it was decided that an IDoc should be posted as a parked document (Parameter POSTING_TYPE = '2').
If this is the case, in contrast to the usual process flow, the program does not post an FI document, but generates and posts a parked document.
The data for parking a document is created in the data structures designed for this, and then transferred to the function module for posting a parked document, PRELIMINARY_POSTING_DOC_WRITE.
Before a parked document is posted in the recipient system, all of the data structures created for it are transferred to user-exit 009. These are structures that roughly correspond to those for an FI document.
The complete IDoc is also transferred to the exit.
The user has the option of influencing the parked FI document that is to be posted by changing or expanding data fields.
Caution:
In the sender system, a complete FI document is sent using an IDoc. This is then usually posted as a complete FI document in the recipient system.
Alternatively, the user can control the processing so that the IDoc is posted as a parked document. This is done in the inbound IDoc using the enhancements F050S002, exit 004, and F050S004, exit 006 (POSTING_TYPE = '2').
This is only possible and relevant if the FI document only contains G/L account items and no automatically generated line items.
If this option is used, the note about the sender system and the original document is lost. An asssignment to the original document is no longer possible.
Addresses (Business Address Services) General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 1875 Date: 20240418 Time: 014615 sap01-206 ( 36 ms )