96% found this document useful (24 votes)
41K views

Functionality Behind Rejection Reason (Reason For Rejection)

Reason for rejection (Or known as "Rejection reason") is a very commonly used functionality in SAP to specify whether a certain line item in the sales order is rejected (Blocked for further processing) or not. Based on how you have configured each rejection reason, system behaves differently.

Uploaded by

Anupa Wijesinghe
Copyright
© Attribution Non-Commercial (BY-NC)
96% found this document useful (24 votes)
41K views

Functionality Behind Rejection Reason (Reason For Rejection)

Reason for rejection (Or known as "Rejection reason") is a very commonly used functionality in SAP to specify whether a certain line item in the sales order is rejected (Blocked for further processing) or not. Based on how you have configured each rejection reason, system behaves differently.

Uploaded by

Anupa Wijesinghe
Copyright
© Attribution Non-Commercial (BY-NC)
You are on page 1/ 8

Contents

Introduction .................................................................................................................................................. 2
Configuration and analysis ............................................................................................................................ 2
Field "NRP" (Not relevant for printing) ............................................................................................... 3
Field "Stat" (Statistical values) .................................................................................................................. 4
Field "BIC" (Not relevant for billing) ......................................................................................................... 5
Field "OLI" (Resource Item Open Again) ................................................................................................... 7



Introduction
Reason for rejection (Or known as "Rejection reason") is a very commonly used functionality in SAP to
specify whether a certain line item in the sales order is rejected (Blocked for further processing) or not.
Based on how you have configured each rejection reason, system behaves differently.
Configuration and analysis
Reasons for rejection are configured under below IMG path;
IMG Path:

In order to create a new "Rejection reason" click on the button

Now let's see what the fields in this configuration node are and how system reacts in each case.
Field "NRP" (Not relevant for printing)
As the descriptions states, it is about how standard outputs reacts for sales order line items which has
this kind of a rejection reason assigned.
Let's first configure my rejection reason without this flag and see the standard order
confirmation output.

Line item 10 is assigned the rejection reason "ZA"

Net value in the sales order header considers the value of the rejected line item. (100+120=220)
Now let's print the order confirmation output "BA00" for this sales order

As you see above, it prints the rejected line item. And the total is calculated together with the rejected
line item value. (100+120=220)
Now let's configure my rejection reason with this flag and see the standard order confirmation
output.

Now when I generate the standard order confirmation output "BA00", we can see system ignores the
rejected line item for printing.

But if you look at carefully, the total value still considers the rejected line item value (100+120 =220)

Field "Stat" (Statistical values)
In order to avoid above mentioned issue in the sales document header total value as well as the total in
the order confirmation printout, you can use below field.

You can specify below values there;
Blank - Considered for cumulating
X - Not considered for cumulating - Values cannot be used statistically
Y - Not considered for cumulating - Values can be used statistically
Since I have specified "Blank" value against my rejection reason, System considers it for total calculation.
Now let's assign "Y" there and see how system reacts;

Now you should be able to see the "Net Value" is not considering the value of the line item 10.

Now let's generate the standard order confirmation output "BA00", As you see below, system now
ignores the rejected line for total calculation.

Field "BIC" (Not relevant for billing)
This field in the rejection reason is used to specify whether such items are considered for billing
document creation or not.
Let's assign a rejection reason which has not marked this tick box and see how system reacts
during billing

Credit memo created with 2 line items, which one is assigned to this rejection reason "ZA"

Let's create the credit invoice and see how system reacts;

System copies both line items to the billing document. Based on the net value in the sales order, credit
invoice net value is set correctly.
Now let's change the rejection reason configuration with the flag "Not relevant for billing) and
do same steps

Assign the rejection reason to a line item.

During billing, the rejected line item is not copied to the billing document.


Field "OLI" (Resource Item Open Again)
As far as I understood this field is used in CS module in SAP.

Author: Anupa Wijesinghe
E-Mail: [email protected] / [email protected]
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.

You might also like