Background
In SAP S/4HANA Cloud Public Edition, the flexible approval workflow allows companies to define business rules that route sales orders to approvers before they are confirmed. A common requirement is to hold logistics activities — such as ATP confirmation, Transfer of Requirement (ToR) to MRP, and purchase requisition (PR) creation — while an order is awaiting approval. Starting a procurement run or allocating stock for an order that has not yet been approved by management wastes planning resources and can be difficult to reverse.
In a previous blog, I explained how to stop the Transfer of Requirement to MRP when a sales order enters the approval workflow. That blog covered the configuration approach to prevent MRP requirement transfer for orders pending approval.
In SAP S/4HANA Cloud Public Edition 2608, a new feature called Supply Block extended this capability significantly. Supply Block provides item-level control over all three logistics activities simultaneously — ATP confirmation, ToR to MRP, and PR creation — with a single configuration flag. In this blog, I will explain how to configure Supply Block to work with the approval workflow, and demonstrate the end-to-end behavior with a test scenario.
Business Example
Supply company XYZ uses the flexible approval workflow to manage high-value sales orders. When an order exceeds a certain net value threshold — or when a specific order reason is selected by the sales representative — the order is automatically routed to a sales manager for approval. The sales manager has up to 24 hours to review and either approve or reject the order.
The challenge: between the time the order is saved and the time the manager acts, the system is already running ATP checks, creating MRP requirements, and — for third-party or make-to-order items — generating purchase requisitions. If the manager rejects the order, these logistics activities must be manually reversed. If the manager requests changes, the items may already have been committed to stock or production.
Company XYZ wants all logistics activities to be completely suspended while the approval is pending, and automatically resumed as soon as the order is approved. No manual intervention should be needed to “unblock” logistics after approval. This requirement can be fulfilled through configuration alone — no BAdI implementation is needed.
How Supply Block Integrates with Approval Workflow
Before covering the configuration steps, it is important to understand how Supply Block interacts with the approval workflow.
When a sales order enters the approval workflow, the system evaluates the approval request reason code assigned to the order. Each reason code can be individually configured to trigger Supply Block on all items of the order. When Supply Block is triggered this way, the Supply Block Status field on each item is set to “Blocked”. This stops ATP confirmation (confirmed quantity becomes zero), stops Transfer of Requirement to MRP, and prevents PR creation.
Critically, the Supply Block Reason field — the direct, manual supply block field on the item — remains empty. The block comes entirely from the approval workflow configuration. When the approver releases the approval request, the Supply Block Status is cleared automatically across all items, and all three logistics activities resume without any manual intervention.
This is different from a BAdI-driven supply block, where a custom reason code is written to the Supply Block Reason field directly. The distinction matters for troubleshooting: if an order has Supply Block Status = “Blocked” but Supply Block Reason is empty, the block source is either the approval workflow or credit management — not the BAdI.
Step 1: Configure the Approval Request Reasons
The approval workflow in SAP S/4HANA Cloud Public Edition uses approval request reason codes to classify why an order requires approval. Reason codes are customer-defined and can be created in the relevant SSCUI.
Go to SSCUI “Define Reasons for Approval Requests” to define a new approval request reason “ZSPB” for supply block.
Then go to SSCUI “Assign Reasons for Approval Requests” to assign this approval request reason to sales order, and check the indicator of “Supply Block”.
Save the configuration and move to BAdI implementation.
Step 2: Implement Approval BAdI
You can follow SAP help to set up the flexible approval workflow for sales order. Once the flexible approval workflow is configured, you can implement the BAdI SD_APM_SET_APPROVAL_REASON to set the relevant approval request reason based on certain criteria.
In the BAdI implementation, evaluate the relevant business condition — net value, order reason, profit margin, or any other field available in the sales document context — and assign the appropriate reason code to salesdocapprovalreason.
The following example sets reason code ZSPB when the order reason is “007” (Fast Delivery).
* Trigger approval if the order reason is “007”
if salesdocument-sddocumentcategory = ‘C' and salesdocument-salesdocumenttype=”TA” and salesdocument-sddocumentreason = ‘007'.
salesdocapprovalreason = ‘ZSPB'.
endif.
Save and publish the BAdI implementation.
Business Process Testing
Create a new standard sales order that meets the approval trigger condition.
Add the item and save the sales order.
Navigate to the Status and Blocks tab. The Overall Supply Block Status shows All Blocked and Approval Status shows In Approval.
Check the confirmed quantity on the order items. The confirmed quantity is zero — no ATP confirmation has been performed.
Go to app “Manage Material Coverage” and the sales order 11150 is not visible in the requirement list, which means no MRP requirement has been transferred.
Then approve the sales order.
After the approval is released, open the sales order 11150 and navigate back to the Status and Blocks tab. The Overall Supply Block Status is now Not Blocked and the Approval Status shows the approval is released.
The confirmed quantity is restored automatically — ATP has re-run.
MRP requirements are transferred, see screenshot below.
Connection to the Previous Blog
The previous blog showed how to stop Transfer of Requirement to MRP when a sales order enters the approval workflow. That approach covered one of the three logistics activities.
With the Supply Block feature in SAP S/4HANA Cloud Public Edition 2608, the same configuration mechanism now controls all three activities simultaneously:
| Activity | Previous Blog | CE2608 with Supply Block |
ATP confirmation (confirmed qty) | Stopped via SSCUI 102751 “Set Confirmed Quantities to Zero” | Stopped — same effect, no additional config |
Transfer of Requirement to MRP | Workaround only — required “Fixed Date and Qty” flag set manually per item (or via API at creation) | Stopped automatically — no manual steps |
Purchase Requisition creation | Not stopped | Stopped |
If you implemented the configuration covered in the previous blog, you can extend it by enabling the “Set Supply Block” flag on the same approval request reason codes. The ToR behavior you already have is preserved, and ATP confirmation and PR creation are now also held while approval is pending.
Conclusion
The Supply Block feature in SAP S/4HANA Cloud Public Edition 2608 provides a straightforward, configuration-only way to hold all logistics activities while a sales order awaits approval. By enabling the Supply Block in sales order approval workflow, companies can ensure that ATP confirmation, Transfer of Requirement to MRP, and purchase requisition creation are all suspended while the order is pending — and automatically resumed upon approval, with no manual intervention needed.
This builds on the standard flexible approval workflow and the previously available ToR-stop capability, filling the remaining gaps in logistics gating. For companies already using the configuration from the previous blog, upgrading to CE2608 and enabling the Supply Block flag on existing reason codes is all that is needed to gain the full three-activity protection.
Please feel free to submit your requirements through the Customer Influence Portal to help us prioritize our product roadmap.
Source link
