Ansicht
Dokumentation
CNV_CMIS_U_RLE_SHP_IDX_TABLE - XPRA Report for Filling Index Tables for Deliveries
Fill RESBD Structure from EBP Component Structure BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Title
XPRA Report for Filling Index Tables for Deliveries
Purpose
This report is used to initially construct the index tables for deliveries when you upgrade to Release 4.70 or higher.
Integration
Prerequisites
The XPRA report is only run if
- the source release of the upgrade is 3.0, 3.1, 4.0, 4.5, or 4.6
- the target release of the upgrade is 4.70 or higher
The report was programmed only to be carried out during the upgrade, and is aborted if you start the report online or in the course of normal background processing.
Features
Selection
Standard Variants
Output
Activities
The report reads the relevant matchcode tables for objects VMVL (outbound deliveries), VMVM (inbound deliveries), and VMVG (rough goods receipts) in each client in a system. It then copies the entries to the new index tables. Sometimes, data from the delivery header table LIKP and the header status table VBUK is added to the data from the matchcode tables. The following schema shows the data flow:
| Target table | Source table | Additional data from table |
|---|---|---|
| SHP_IDX_GDSI | M_VMVLA | LIKP, VBUK |
| SHP_IDX_PICK | M_VMVLB | LIKP |
| SHP_IDX_CRED | M_VMVLD | - |
| SHP_IDX_EXOB | M_VMVLI | - |
| SHP_IDX_GDRC )* | M_VMVME | VBUK |
| SHP_IDX_PUTA )* | M_VMVMF | VBUK |
| SHP_IDX_EXIB | M_VMVMA/M_VMVMD )** | - |
| SHP_IDX_ROGR )*** | M_VMVGA | - |
Note:
)*Conversion only for start release 4.5B and higher.
)**The source table used depends
on the start release of the upgrade. For releases 3.1I and 4.0B, table M_VMVMA is used and for release 4.5B and higher, table M_VMVMD.
)***Conversion only for start release 4.0B and higher.
After the target tables are filled, the entries from the matchcode tables are removed to make more storage space in the database. The report also deletes the entries from those tables that are not necessary for converting matchcode objects VMVL and VMVM.
After the data for all clients has been successfully converted, the system completely deletes the matchcode objects VMVL, VMVM, and VMVG.
Once the conversion has successfully finished, the matchcode tables for the objects VMVL, VMVM, and VMVG are empty in all clients in the system.
Restarting the Program
You can restart the XPRA report in the upgrade if you need to restart the upgrade. Processing is then continued using the not yet fully constructed index tables.
Procedure if Program Aborts
If the report is not successfully run, the worklists and search helps for deliveries are partially available, or not available at all.
In this case, you can proceed as follows to make the index tables function properly:
- Run program RLE_SHP_IDX_TABLE_MAINTAIN for each client where you require index tables. You can start this program parallel to your productive system if you need to. Before you start the program, read the relevant documentation.
- Delete any matchcode objects VMVL, VMVM, and VMVG that will not be used in future using the ABAP Dictionary (menu path: Utilities -> Other Dictionary Objects).
Note
You can test the report online in SAP-internal systems, if you set the user parameter LE_SHP_IDX_XPRA_TEST:
- ' ': The report runs as in the upgrade (meaning that it aborts during normal processing)
- 'D': The report runs in test mode and performs all database operations. The matchcode objects involved are kept. The report also issues a log and measures the runtime.
- 'E': As in option 'D', however the matchcode objects are physically deleted when the program ends. Use this variant of the user parameter very carefully, since you can only start the report once using this option.
- 'X' or any other value: The report runs in test mode, but does not make any changes to the database.
General Data in Customer Master CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 5786 Date: 20240531 Time: 062041 sap01-206 ( 75 ms )
