User Exits for SD Transport Processing
If a delivery is included in a shipment, this information is also reflected in the delivery since, for example, the so-called transportation planning status (VBUK-TRSTA) changes (it switches from 'A' to 'C', for example). This means, that data in the delivery is changed. When shipment processing is completed, the delivery must therefore be updated.
Starting with Release 4.5A, deliveries can be updated in two ways:
1. Using general delivery routines
2. Using a routine especially adapted for shipments If you choose option 1, various activities are carried out for each delivery:
- Update of the transportation planning status (VBUK-TRSTA)
- Update of the transportation planning index (table VTRDI)
- Update of the document flow (table VBFA)
- Output determination in the delivery
- Statistics in the delivery
- Change documents for the delivery
- User exits in program SAPMV50A are processed when the delivery is saved
Option 2, however, includes the first three points only: - Update of the transportation planning status (VBUK-TRSTA)
- Update of the transportation planning index (table VTRDI)
- Update of the document flow (table VBFA)
If you choose option 2, these tables are updated using mass processing (they are not updated individually, that means, delivery for delivery).
For performance reasons, option 2 is used in the standard system starting with release 4.5A. As a result, saving a shipment is faster, in particular, if many deliveries are assigned to the shipment. However, if you definitely need specific functions that are performed
with option 1, you can activate this enhancement. This can be the case, for example, if you want the user exits for the delivery to be processed when the shipment is saved. It is sufficient to activate this enhancement. The system then behaves as in release 3.0/3.1. No further programming is required.
Function/Program:- EXIT_SAPLV56U_006: Obsolete as of $.6C: Update Delivery by Delivery Routines
|