When migrating from Release 2.1 or 2.2 to Release 3.0, what do you need to pay attention to if you added customer specific additional account assignments to SAP tables according to Note 22204?
In this note a detailed description of the procedures involved as agreed with the Basis department will be described and updated continuously.
Additions
02/20/96: Include customer append with 2.1/2.2 fields in ACCIT (1)
03/15/96: If required, include entry in TMODU per 2.1/2.2 customer field (2)
03/19/96: Include customer append with 2.1/2.2 fields in COBL_08 (3)
07/19/96: Addtnl customer append structures for 3.0 functionality (4)
08/23/96: Upgrade to 3.0D/3.0E does not activate append structures (5)
Beginning with Release 3.0D the manual additions (1)-(3) are no longer applicable.
The program RGUCBL01 is started in the FI-SL XPRAs and transfers the above described additions (1)-(3).
Beginning with Release 3.0E, the program RGUCBL00 exists. This program selectively stores and activates append structures with the migrated account assignment dimensions for the selected areas in the Repository.
The program RGUCBL00 is available on sapserv3 for Release 3.0D. Please see note 43077.
The note 39278 is only relevant for Releases 3.0A/B/C.
Coding block, ZA includes, CI includes, CI_COBL, CI_COBL_BI,
Additional account assignments, migration
Solution
With regards to the migration, you should always accept the suggestions from SAP and -as suggested- create your own append structure per table for the customer-specific fields during a SPDD comparison.
The names of the append structures should always be in the customer name range. As a suggestion for an append to table
I M P O R T A N T! ------------------------------- Addition 02/20/96
You MUST manually include the customer-specific fields defined in 2.1/2.2 as an append structure (suggestion: ZAACCIT) in the structure ACCIT (= RW interface, item information), so that the information for the update is made generally available.
The log of the XPRA RGUXI30A also tells you if ACCIT fields are missing; the XPRA RGUXI30A, amongst other things, converts the field movements from BSEG to ACCIT.
If the fields are not included in ACCIT, the FI-SL update cannot take into account all the dimensions you require; that is, the level of detail does not meet your requirements.
I M P O R T A N T! --------------------------------- Addition 02/20/96
---------------------------------------------------- Addition 03/15/96
If necessary include an entry in table TMODU per 2.1/2.2 customer field.
TMODU is the table for the where-used list of field names - MODIF1.
The table TMODU is used in the FI interface to interpret the field selection. If entries are missing there, the required entries are not checked. If you depend on this validation of the data, subsequently maintain the entries with the following content:
TMODU-FAUNA = 'SKB1-FAUS1',
TMODU-MODIF =
TMODU-TABNM = 'BSEG',
TMODU-FELDN =
TMODU-KOART = 'S',
TMODU-UMSKS = ' ',
TMODU-XRELE = 'X'.
--------------------------------------------------- Addition 03/15/1996
--------------------------------------------------- Addition 03/19/1996
You should also manually include the customer fields defined in 2.1/2.2 as an append structure in the structure COBL_O8 (suggestion ZACOBL_08), so that the information based on the invoice verification can be taken automatically from the purchase order.
You will be made aware of the effect during the migration when you compare the old and new status of program MM08RFK0. Select the SAP standard in the program MM08RFK0 and limit the structure COBL_08 with a new customer append structure.
If you do not include the fields in a COBL_08 append structure, an automatic transfer of the customer-defined account assignment fields from the purchase order to the invoice verification does not take place.
--------------------------------------------------- Addition 03/19/1996
--------------------------------------------------- Addition 07/19/1996
Detailed analysis has shown that in Release 3.0 there is approximately twenty structures which contain the customer include CI_COBL, but not the migrated customer defined account assignment dimensions from 2.1/2.2.
To ensure that the entire 3.0 functionality also exists for the (after the migration to 3.0) additional account assignments defined in Release 2.1/2.2 according to note 22204, you must store append structures in the dictionary for the required areas:
- Accounting interface : ACCIT, ACCTIT
- Batch input FI-Accounting : ZBSEG (BBSEG), see note 44920
- FI: SAPF181-Profit. seg. adj. : COBL_CUST
- FI Fast entry : SAPOS
- Parking documents (FI/MM) : VBSEG, VBSEGS
- Purchasing (MM-PUR) : ESKN, VSEBKN_CN
- Ivntry Mgmt (MM-IM) : ACCIT_MB, IMSEG
- Invoic verification (MM-IV) : COBL_08,EK08BN,EK08RN,DRSEG,RBSEG
- FI Document changes for CO : BSEGCO, BSEGCO_CHG
- CO-Archiving : COEP_ONLY
- CO-Line item reporting : RKPOS, see note 33846
- ALE: User fields for distrbtn : SAP_COBL.
Beginning with Release 3.0E, the program RGUCBL00 offers the possibility of automatically creating the customer append structures for the selected areas during execution.
Additional documentation can be found in:
- Note 43077 (=migrated customer-defined account assignment dimensions missing in 3.0
- 3.0e Release Note FI_GLX_30E_RGUCBL00
- Documentation on report RGUCBL00
--------------------------------------------------- Addition 19.07.1996
--------------------------------------------------- Addition 19.07.1996
During the upgrade to 3.0D/3.0E, the append structures written from "XPRA" RGUXI30A/RGUCBL01 are unfortunately not activated. Therefore, you must manually maintain the FI-SL field movements in order to permit the data to be updated at the required level of detail.
You must carry out the following steps:
1.) Transaction SE11: Maintain an active append structure for ACCIT
2.) Transaction GCF2: Maintain FI-SL field movements
Additional details -> see note 47482 (Upgrade: Upgrade...)
--------------------------------------------------- Addition 23.08.1996
The user can continue to work as usual after the migration.
Short-term strategy:
In order to use the complete 3.0 range of functionality for migrated fields, all required append structures (see Note 43077) must have been created.
Long-term strategy:
In Release 3.0, a procedure is offered which allows the user to transfer coding block enhancements (quality: modification) made in Release 2.1/ 2.2 to the 3.0 SAP standard.
More information pertaining to this will be found in this note - as soon as it is available.
No comments:
Post a Comment