This program is only relevant for customers who created additional account
assignments in Release 2.1 / 2.2 per Note 22204. To be able to use the
complete 3.0 functionality also for the additional account assignments created
in Release 2.1 / 2.2 according to Note 22204, you have to store append
structures for the required areas in the Dictionary:
- Accounting interface
- Batch input for finacial accounting
- FI: SAPF181 subsequent debit to profit and loss statement
- FI fast entry
- preliminary entry (FI/MM)
- Purchasing (MM-PUR)
- Inventory management (MM-IM)
- Invoice verification (MM-IV)
- FI document changes for CO
- CO archiving
- CO line-item reporting
- ALE: user fields for distribution
The program RGUCBL00 enables you to create automatic customer append structures for the reports selected for execution.
The following structures are affected:
- Accounting interface : ACCIT, ACCTIT
- Batch input financial accounting : Z(BBSEG)
- FI: SAPF181-Subsequent debit to P&L statement : COBL_CUST
- FI fast entry : SAPOS
- Preliminary posting (FI/MM) : VBSEG, VBSEGS
- Purchasing (MM-PUR) : ESKN, VSEBKN_CN
- Inventory Management (MM-IM) : ACCIT_MB, IMSEG
- Invoice Verification (MM-IV) : COBL_08,EK08BN,EK08RN,DRSEG,RBSEG
- FI document changes for CO : BSEGCO, BSEGCO,
- CO archiving : COEP_ONLY
- CO line item reporting : RKPOS
- ALE: User fields for distribution : SAP_COBL.
The program makes a test run possible; the test run can be executed first to display the current system status.
You can execute the program any number of times.
The connection to the Workbench organizer/transport system exists.
Errors may occur during import of the generated transport request to the target system, if the structures/tables affected have a different status from that in the source system.
In the worst cases, data may be lost if there is already an append in the target system with the same name but different fields. Such an append will be overwritten by the import; the original fields will be replaced by the new ones.
If the fields for an imported append already exists in the active structure/table in the target system, activation errors occur.
You must check the situation in your target system before releasing the target request. If the structures/tables affected differ from those in the source system, delete the transport request and run this program in the target system instead.