Ansicht
Dokumentation

RMCP6SOP - Conversion of SOP for 3.0 Planning

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

General Description

Program RMCP6SOP enables you to continue using the product groups and their planning versions which you created in Release 2.2. It converts table PGPL, the table used by SOP in Release 2.2, into the information structure S076.

In some cases, the program is executed automatically when you upgrade from Release 2.2 to Release 3.0. In other cases, you must execute it in the background. (Online processing is unsuitable because the program has a long runtime.)

Procedure

To schedule a background job for the program:

1. From anywhere in the R/3 System, select System -> Services -> Job ->Job definition.
2. On the screen Define Background Job, enter a job name.
3. Select Edit -> Steps.
4. In the window Create Step 1, click on the pushbutton ABAP/4.
5. Select Save.
6. Select Back.
7. On the screen Define Background Job, select Edit -> Start time.
8. In the window Start Time, click on the pushbutton Date/Time.
9. Enter the date and the time when you want the job to start. SAP advises that you schedule the program to run overnight.
10. Save these settings.
11. On the screen Define Background Job, select Job -> Save.

Technical Description

Program RMCP6SOP carries out the following steps:

1. Conversion and creation of data
1. Converts data from tables PGMI and PGZU to the table PGAN.
2. Creates entries in table S076E.
2. Transfers the records from table PGPL (used in Release 2.2) to information structure S076, on condition that a valid planning version for each product group record in table PGPL exists in table P445V. The program skips records without such a planning version.
3. Updates planning versions of product groups
1. Inactive versions:

An entry is made in table P445X for every entry in table P445V. Table S076E is read in this process.

If date on which the info structure planning version was created comes after the creation date of the product group planning version, or if the date on which the info structure planning version was last changed comes before the most recent change date of the product group planning version, table P44V (the table of information structure planning versions) is updated. This ensures that the oldest product group creation date and the most recent product group change date are written to table P44V for the information structure.

1. Active versions:

The same procedure is adopted as for inactive versions.

In addition, a copy of the record from table PGPL is created in tables P445V, P445X, and P44V for the active version '~00'.

1. Table SAUF is updated with the entry 'S076' instead of the entry 'PGPL'. The active version is also recorded here as '~00'.
2. Tables T445E, T445A, and T445I are updated.
1. Entries are made in table T445E for existing information structures and the field names of their units. Only the values of the units then have to be entered manually (in the Customizing step "Units of fields from info structures").
2. Planning method "D" for delta planning is set in table T445A for all existing information structures. The storage periodicity is the update period from the information structure. If the storage periodicity is "P", the fiscal year variant is also defined. (See the Customizing step "Planning parameters for info structures".)
3. The indicators in Table T445I are selected by default for key figures in existing information structures. (You check them in the Customizing step "Planning parameters for key figures".)

Requirements

Output

Example

ROGBILLS - Synchronize billing plans   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4640 Date: 20240520 Time: 095646     sap01-206 ( 75 ms )