Table of Contents

ARun Drop Requirement ......................................................................................................... 2

Define rejection reasons ...................................................................................................................3
Define whether rejection code relevant for partial shipment / Drop requirements...........................3
Enable Partial quantity rejection per sales document type per sales area .........................................4
Enable Drop Open Requirements......................................................................................................5
Maintain Rejection Codes for Supply Assignment (ARun) .................................................................6
Scenario Testing ...............................................................................................................................7
Run - ARUN_DROP_REQ - Drop Open Requirements.........................................................................9
Further Notes: ................................................................................................................................ 12
Conclusion ...................................................................................................................................... 14
ARun Drop Requirement
This report drops / rejects open requirements for sales orders (SO) or stock transport orders
(STO). These can be:
• Non-allocated SO items
• Partially allocated SO items
• Non-allocated STO items
• Partially allocated STO items
Non-allocated sales order line items are completely rejected using the rejection code you have
defined in the customizing activity for that order type. For partially allocated sales orders, the
Order Quantity for the specific sales order item is adjusted to match the allocated quantity and
a new sales order item is created with the remaining units. This new sales order line item is then
rejected with the rejection code you have defined for that order type.

Please use F1 help to read about this report in the SAP Easy Access Menu.
Define rejection reasons

Define whether rejection code relevant for partial shipment / Drop requirements
Enable Partial quantity rejection per sales document type per sales area
Enable Drop Open Requirements
You will only see what’s flagged with Drop Open Requirement flag in the above configuration.

Maintain Rejection Codes for Supply Assignment (ARun)

This is an optional configuration node, where you can see the above configuration itself. Once
you flag in the “Maintain Rejection codes for Fashion Management”, it will appear in this node
as well.
Scenario Testing
SO – 106
Allocate 8 using ARUNITA
Run - ARUN_DROP_REQ - Drop Open Requirements

Run for sales order 106

Output:

Sales order 106 after execution:

New line item got added for the none-allocated quantity. i.e. 2 (10 – 8)
Therefore we can execute this transaction to drop (reject) any quantity that was not allocated.

Now let’s create a delivery for this sales order - 106.

Delivery – 80000067
Delivery got created for quantity – 8

Do a partial pick – For quantity 5.

And make sure delivery quantity = Pick quantity.
Now ran ARUN_DROP_REQ - Drop Open Requirements transaction with rejection reason “ZP”
in the selection screen.

Output:

Select and execute:

Output

Sales order after execution:

System adds a new line item for the none shipped quantity and add that rejection reason that
was specified in the selection screen (ZP)

Further Notes:

1 - ARUN_DROP_REQ - Drop Open Requirements transaction only shows rejection reason that
are flagged with “Relevant for Partial Quantity” in the below configuration.

Note: rejection reason 02 also flagged with same.

2 – Now we create a new sales order 107 and ran this transaction without allocating it.
We didn’t specify any rejection reason in the selection screen this time.
In that case, system reject the full quantity with the rejection reason “ZA”.
This means, that rejection reason that you have assigned for document type / sales area
combination will be used, only when you didn’t assign a rejection reason in the selection screen.
In order to assign it for document type / sales area combination, you need to flag as Drop Open
requirement relevant.

Now we remove that rejection reason in the sales order line item and ran the same transaction
with rejection reason “ZP” in the selection screen.
Now we can see that system reject that sales order with the rejection reason “ZP”

Conclusion

• In order to assign a default rejection code for drop open requirements, Rejection reason
should be marked with Drop Open requirement relevant.

• If you mark any rejection reason with “Partial Shipment relevant”, then you can use that
rejection reason for any case.

• If you don’t specify a rejection reason in the ARUN_DROP_REQ - Drop Open Requirements
selection screen, then system use the default rejection code assigned in the configuration.
 • For all cases, system adds a new line item and reject that line item.

Author: Anupa Wijesinghe

E-Mail: anupaw@gmail.com / anupaw@learnsaptips.com
Website: www.learnsaptips.com
View my profile in LinkedIn
Follow me on Twitter

Disclaimer

This article is done based on my research and readings, unless otherwise stated. The views
expressed are my own and not of anyone else.
Author accepts no liability for the content of the articles in this website or for the consequences
of any actions taken on the basis of the information provided. Using this information is at the
users own discretion and responsibility.