Rejecting Open Quantities 

Use

You can configure the allocation run (ARun) to drop unallocated quantities on release and assign a rejection code. You can also do this in the ARun Optimizer, where you have some additional options.

·        ARun

You can only flag schedule lines for rejection. You subsequently run the SD Mass Document Change Report (/AFS/RVMDCD) to reject the schedule lines.

·        ARun Optimizer

You can flag orders, deflag them subsequently or reject the quantities immediately. In case of flagging and deflagging orders, the results have to be saved. However in case the reject immediate option is used, rejection takes place prior to saving and the process cannot be undone thereafter.

Each rejection code is configured to reject one of the following:

o        Complete quantity

o        Quantity not delivered

o        Quantity not allocated  

In case the rejection code is configured for Quantity not allocated the rejection would work in the following manner. A partially allocated schedule line would be divided as the allocated and unallocated portions. Further on, the unallocated portion would get rejected.

You have an order for 10 pieces. You only have 8 in inventory. The customer tells you to ship the 8 available pieces and drop the rest. The system creates two schedule lines:

·         The first schedule line contains the 8 pieces to be allocated.

·         The second schedule line contains 2 pieces, plus a rejection code indicating that the customer considers the shipment of 8 as complete.

Prerequisites

In standard SD Customizing, you create rejection codes and assign your own text to them, indicating the reason for rejection. You can then apply these rejection codes to release rules in Customizing for the ARun Optimizer. The Reason for Rejection field is only valid if the Open Quantity field contains X (“rejected”). In ARun release Customizing, you must specify a rejection code if the Open Quantity field contains X.

Activities

You can reject open quantities using either a one-step or two-step process:

·        One-step process

You select a range of orders in the ARun Optimizer and reject them immediately. The system then drops all unallocated quantities and updates the affected sales orders. You cannot undo the rejections within the ARun Optimizer; if you need to undo a rejection, you must do this directly in sales order maintenance.

·        Two-step process

...

...

1.       You select a range of orders in the ARun Optimizer. You can flag all orders having unallocated quantities. This has no actual effect on the orders; it merely marks them for subsequent action.

2.       You subsequently run the SD Mass Document Change Report to reject the schedule lines.