Kontakt

Ansicht
Dokumentation

Optimization of Delivery Viability Set for Sales Orders ( RELNISMSD_402_K_DELIVOPT )

Optimization of Delivery Viability Set for Sales Orders ( RELNISMSD_402_K_DELIVOPT )

Vendor Master (General Section)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Optimization of Delivery Viability Set for Sales Orders

Description

Up to Release 4.02, delivery viability parameters (edition, mix type and delivery type) could only be determined automatically during certain procedures (fast subscription entry, WBZ inbound processing, voucher copy shipping).

As of Release 4.02, comprehensive delivery viability determination and optimization are possible. The system uses predefined optimization rules to determine the "optimum" framework for delivery and sets the delivery viability parameters in the order item accordingly.

The optimization rules can be defined separately for the following transaction types:

  • Creating and changing orders (01)
This transaction type includes order dialog (including fast entry) and data transfer. The following rules apply here:
  • Predefined delivery viability parameters remain unchanged

  • Missing delivery viability parameters are determined according to optimization rules

  • If you change fields that influence the delivery viability parameters (e.g. publication, address, ...), the previous delivery viability parameters are deleted and delivery viability determination is performed again.

  • Changing addresses for WBZ (02)
Optimization of delivery viability parameters is only supported together with WBZ inbound processing. An enhancement is planned for a later release.
  • Releasing a change number (03)
If the appropriate indicator is set in the master data on the change number, delivery viability optimization is performed for all orders affected by a change number. If delivery viability parameters are changed during this process, the system creates an unlimited change for the order item. Since this is only possible in the last time slice of a process, there may still be time slices in which delivery is not viable for the order item between the start of validity of the change number and any change made to the order. This must be corrected manually as before.
Note: It is not advisable to perform optimization of delivery viability parameters when releasing change numbers that affect a large number of orders, since this can lead to an extended runtime. In cases such as this, optimization should not be set up in the master record for the change number. You can edit the orders affected afterwards using an explicit optimization run if necessary.
  • Explicit optimization run (04)
To optimize delivery viability in certain areas of the orders on hand, you can use report RJKDELIV_OPT to check the delivery viability parameters and generate an unlimited change for an order item if necessary. In order to be able to target specific objects and restart processing at any time, you can use report RJKDELIV_TODO to create a worklist which is then processed sequentially.

Changes to the Interface

To maintain optimization rules, choose the following menu path:
Logistics -> Media sales and distribution -> Master data -> Distribution -> Delivery -> Delivery viability set -> Optimization rules and the report for explicit optimization: Logistics -> Media sales and distribution -> Sales -> Environment -> Optimize del. viability.

You can select an indicator in basic item data for an order to deactivate optimization of delivery viability parameters. This allows you to take special requests from a subscriber into account (e.g. delivery by post or no flyers) and to ensure that these special requests are not overwritten during delivery viability optimization.

Dependent functions

The previous delivery type prioritization (delivery type access sequence), used in fast subscription entry, WBZ inbound processing and voucher copy shipping, is no longer supported. Optimization rules for the new delivery type optimization functions are now required for all three of these procedures.

The previous default value for the delivery type in redirections in the general control parameters for sales has become obsolete, since this function was replaced by delivery viability determination or enhancement JK020002.

User exit EXIT_SAPLJK02_001 in enhancement JK020002 was replaced by user exit EXIT_SAPLJK00_001.
Enhancement JK020002 also contains further user exits for delivery viability optimization.






CL_GUI_FRONTEND_SERVICES - Frontend Services   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 5137 Date: 20240520 Time: 150030     sap01-206 ( 101 ms )