Ansicht
Dokumentation
ROIGMS01 - Check Inconsistency in Bulk Shipments
RFUMSV00 - Advance Return for Tax on Sales/Purchases Addresses (Business Address Services)This documentation is copyright by SAP AG.
Description
This report is an emergency report which should only be used with a detailed knowledge about the TD bulk shipment database or after contacting the development support of IS-Oil TD in Walldorf.
The user only needs to run the report if there is an indication of damaged TD bulk shipment data.
It runs against selected bulk shipments and deletes/corrects the data in the shipment database. After running the report it can be necessary to carry out additional transactions to achieve complete consistency in all SAP documents.
The program can run with different options. The user has to choose one run option on the selection screen. The option decides which data is to be corrected.
If shipments have been dedicated for correction and the program does not run in test mode, a popup forces the user to confirm the correction process. Thus there is a chance to leave the process. If the program runs in TEST mode the update function is NOT started and no database changes take place. This enables the user to analyse the list and avoid unintended updates.
1. Run option: Correct OIGSVMQ-MAT_ITM
Wrong OIGSVMQ-MAT_ITM for schedule records (TD_ACTION=1) caused by deletion of shipment item and new allocation of one having the same material.
2. Run option: Correct LIPS-LGMNG from OIGSVMQ
Wrong quantity in store keeping UoM in LIPS caused by deliveries having the same material in different items (and availability on).
The run is made only against completed shipments (status = 6).
3. Run option: Correct OIGSH from OIGSVMQ-HIS_ITM
Missing shipment history records (OIGSH) are created according to the data of the quantity item (OIGSVMQ).
The run is made against all shipments. It is recommended to select only completed shipments (status=6) or select the shipment numbers which are known to be damaged.
4. Run option: Reset status for goods issue
If posting of goods issue is recorded in VBUK-OIG_SSTSF without posting goods issue for the delivery the TD bulk shipment is stuck. The current option can be used to reset VBUK-OIG_SSTSF which allows the to continue with the shipping process.
The run is made against all shipments. Shipments which are already confirmed cannot be corrected automatically. Then goods issue needs to be posted via VL02.
It is recommended to select only loaded shipments (status=4 and 5) or select the shipment numbers which are known as damaged.
5. Run option: Correct shipment stock OIGSM/MV-LABST,-GLQTY
The system calculates the intransit stock and gains/losses from the quantity items (OIGSVMQ). In case of differences it lists the current and the calculated figures for stock in decimal and for gains/losses in floating point format (as stored in the database). In non-test mode the system updates OIGSM and OIGSMV accordingly. The package size can be used to improve performance in case of a big workload or running in batch (increase the number of shipments in one package).
The system lists shipments which have open postings to be checked by the user. Open posting could be: Data saved but not confirmed; Delivery on several vehicles in different status; Recovery function missing for Delivery; ... It does not mean that the shipment data is inconsistent. The user just needs to confirm the missing postings to enable the check report to calculate correctly.
Requirements
Detailed problem analysis and contact development support.
Output
The system lists all shipments with inconsistent data. Depending on the run option additional data is displayed.
At the bottom the system indicates whether the run was in test mode. If updates have been made, the user, date and time are listed. In this case it is highly recommended to have a printout of the run.
Example
rdisp/max_wprun_time - Maximum work process run time CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 4095 Date: 20240601 Time: 114852 sap01-206 ( 85 ms )
