regarding Backorder Processing (BOP)

[#1]

Hi Experts!

I have a question regarding Backorder Processing (BOP).

Please see the scenario below:

* **Inventory:** 3,000 kg
* **Sales Orders (SOs):**
* SO 1: 1,000 kg (**Credit Blocked**)
* SO 2: 1,000 kg (**Credit Blocked**)
* SO 3: 1,000 kg (**Credit Blocked**)

*Note: When SOs 1 through 3 were initially created, stock was unavailable, resulting in a **zero confirmed quantity** in VA03.*

When **BOP** is executed in this state, the log shows a **Credit Warning and Saved** status for SOs 1 through 3.
However, when checking the schedule lines in **VA03**, the confirmed quantity remains zero.
In contrast, the **Product Available Stock Inquiry App (F7884)** shows 3,000 kg as **Reserved** for future requirements.

The next day, when Sales Order 4 (1,000 kg) is created, it also fails to obtain a confirmed quantity.

We would like to understand the technical reason for this behavior: why is the stock internally reserved or consumed (preventing SO 4 from obtaining it), yet the confirmed quantity remains zero in VA03?

Best Regards,
S-O

[Chris1973 · Accepted solution]

Good day @S-O 

This Blog has some good insights: Backorder Processing in advanced ATP

In summary, BOP does not perform a final ATP confirmation for orders that are credit-blocked in public cloud and the reason is:

• When you create a sales order and it exceeds your credit limit, the system blocks the order from ATP confirmation and thereby no delivery process is triggered.
• Even if stock then becomes available at a later time, BOP will still consider the blocked Sales orders as a valid demand when the simulation runs and may then reserve inventory for them.
• However, because the credit block is not changed, the system does not update the quantities confirmed in VA03, even if your BOP shows “Credit Warning and Saved”

Technically the system tries to differentiate the various scenarios.

Step 1: You create Sales Orders e.g., in your case 1 through to 3, without stock, the system technically does not confirm due to the lack of material/stock availability.

Step 2: In a situation where Order are Credit blocked; the system suspends the ATP check and applies the credit block.

Step 3: In a situation when inventory becomes available; the BOP still includes blocked Sos in the demand.

Step 4: Then, the BOP run process Sales Orders; the logs may show Credit Warning and the system simulates reservation.

Step 5: In this case VA03 will still show 0 confirmed quantity because the credit block is still in place.

Step 6: Thereafter the Product Availability App shows that you reserved, which means BOP has reserved inventory virtually.

Step 7: Now your new SO4 sees no stock because inventory appears consumed by earlier blocked Sales Orders.

So, while technically there is no confirmation in the system, BOP holds inventory virtually for the credit-blocked orders until you either unblock or reject them.

Based on your description, I understand your goal is to free up stock for new orders. If that assumption is correct then my suggestion is to:

1. Either release the Credit Block in your system (Once you have released the system, it will trigger a new ATP check and the system will confirm available quantities.) or,
2. You exclude Blocked Orders from your BOP (This will prevent BOP from reserving stock for orders that are not eligible for confirmation)

Here is a insightful answer to a similar community question: https://community.sap.com/t5/enterprise-resource-planning-q-a/credit-blocks-after-atp-bop-run/qaa-p/...

Best regards

Chris

[S-O · Accepted solution]

Hi! @Chris1973,

[S-O · Accepted solution]

Hi! @Chris1973, Thank you for your response! I largely understand the content now. I would like to ask one more follow-up question. For Sales Order 3, which did not get a confirmed quantity updated by BOP, the confirmed quantity *was* updated when I executed the **Availability Check** in **VA02**. What is the reason for this difference in behavior?

[ki2003 · Accepted solution]

Hi! @Chris1973,

Thank you for your response!
I largely understand the content now. I would like to ask one more follow-up question.
For Sales Order 3, which did not get a confirmed quantity updated by BOP, the confirmed quantity *was* updated when I executed the **Availability Check** in **VA02**.
What is the reason for this difference in behavior?

[Chris1973 · Accepted solution]

Hello @S-O

Thank you for the follow-up question.

The reason for that is, BOP runs background reallocation and no produces schedule-line update for credit-blocked items, while the manual availability check in VA02 is a full ATP check and it also commits its result to the order even if the credit status is still blocked.

Best regards

Chris

[S-O · Accepted solution]

Hello @Chris1973,

[S-O · Accepted solution]

Hi! @Chris1973, Thank you for your answer to the follow-up question! I understand that the content you provided describes the standard SAP behavior.