Ansicht
Dokumentation

ROIGMS00 - Delete Bulk Shipment after Loading

ROIGMS00 - Delete Bulk Shipment after Loading

Addresses (Business Address Services)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This report is an emergency report and should only be used if you have a a detailed knowledge of the TD bulk shipment database or after contacting development support at SAP (IBU Oil & Gas, TD) in Walldorf, Germany.

It runs for a selected bulk shipment and deletes/corrects the data in the shipment database. After running the report, it may be necessary to carry out additional transactions to achieve complete consistency in all documents.

The program can be run with different options. You will have to choose one run option on the selection screen. The option decides what data is to be corrected.

At the beginning, the document flow is displayed, providing a chance to leave the process. The system creates a list of all deliveries and the material movements which are directly related to the shipment, and starts the update. If the program runs in the TEST mode, the update function is NOT started, and no database changes take place. This enables you to analyze the list and avoid unintended deletion.

After the correction, the allocated shipment items (deliveries,...) remain in the current status. All shipment-specific data (scheduled, loaded, delivered quantities, meter readings ...) and document flow will be deleted.

You should print out the list to record the process. The list can be used to correct the in-transit stock. It will be your job to create the right reversal transactions to correct the material movements and set up proper in-transit stock quantities. If a goods issue has been posted for the deliveries, the in-transit stock will be already completely or partially discharged. The back-out of the loaded quantity should take this into account.

First Run Option: Delete the shipment

This option deletes a specified bulk shipment.

As the program deletes all shipment-related data, it should only be used in an 'emergency'. For example, if a delivery is wrong and should not or cannot be used for a goods issue. The further handling of the deliveries can be done according to the standard SD functionality (for example: deletion).

Second Run Option: Release the shipment item.

In this option, one shipment item is removed from the shipment. You will have to select the item in a dialog box that displays the document numbers and the document types (delivery=J, shipping notification=7, reservation=w). The shipment will remain in the shipment database. Only the data with reference to the selected item will be deleted in the shipment database. The original document is kept and can be administrated further on by the SAP standard transactions. The item is released from the bulk shipment.

Requirements

Confirmed loading at least at one plant. If no loading has taken place, the shipment can be deleted in the scheduling function.

Output

Regarding database updates, see above. The list displays the deliveries removed from the shipment and the material documents which were created to set up the in-transit stock. Again, you will have to reverse the material movements manually!






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3272 Date: 20240520 Time: 122535     sap01-206 ( 79 ms )