3744361 - Goods Issue blocked with Error "Batch Not Released" during Intercompany Stock Transport Order Processing

• When processing an Intercompany Stock Transport Order (IC-STO) using document type NBIC in SAP S/4HANA Cloud Public Edition with Extended Warehouse Management (EWM). Picking completes successfully; however, when attempting to post the Goods Issue, the system throws error with the message "batch not released."
• Additionally, outbound delivery creation via the My Purchase Orders  Due for Delivery (VL10B) application fails in the background, displaying the following messages:

"Delivery cannot be executed in the background (see long text)"

"No schedule lines due for delivery up to the selected date"

• In the Monitor Value Chain application, the IC Purchase Order appears as completed, but the relevant item shows no committed quantity and will not be transferred to the sales order. The batch status is shown as Conditionally Released (Restricted), while the stock type at storage location level appears as Unrestricted-Use.
• Note: This behavior is specific to the NBIC document type. The same scenario using document type NB (intra-company STO) confirms quantity and creates outbound deliveries automatically.

SAP S/4HANA Cloud Public Edition

1. Create a material with batch management active and set the batch status to Restricted (Conditionally Released) for a specific batch.
2. Verify that the stock type at storage location level is Unrestricted-Use while the batch status remains Restricted.
3. Create an Intercompany Stock Transport Order (IC-STO) with document type NBIC referencing the material and batch.
4. Open the My Purchase Orders – Due for Delivery (VL10B) application.
5. Select the relevant delivery creation date and select the IC-STO document.
6. Click Background to trigger automatic outbound delivery creation.
7. Open the Monitor Value Chain application and observe that the IC Purchase Order item shows no committed quantity.
8. If an outbound delivery was created manually, navigate to the Warehouse Monitor and attempt to post the Goods Issue.

Result: Outbound delivery creation fails in the background. If attempted manually, Goods Issue posting is blocked with error "batch not released," even though the stock type appears as Unrestricted-Use at storage location level.

This is standard system behavior, not a defect.

Change Batch Status to Unrestricted Before IC-STO Creation (Recommended)

1. Open the Change Batch Fiori application (or process a QM Usage Decision if the batch is under Quality Management inspection).
2. Locate the restricted batch (e.g., CS26040L4, BA040226-1) and change the batch status to Unrestricted (Released).
3. After the batch status is updated, recreate the IC-STO or reschedule the existing delivery:
   • The ATP check will now confirm quantities in the delivery schedule.
   • Outbound delivery creation via VL10B will execute successfully in the background.
   • EWM Goods Issue will post without error.
4. Verify the result in the Monitor Value Chain application and on the History tab of the Display Purchase Order application.

Note: If the batch is under Quality Management control, the batch status transition from Restricted to Unrestricted must be performed via a QM Usage Decision (usage decision A – Accept) rather than direct batch master maintenance.

Resolve Stock Inconsistency Between IM and EWM (If Applicable)

If a stock inconsistency between Inventory Management and EWM is identified as a contributing factor:

1. Open the Compare Stock with Inventory Management (/SCWM/ERP_STOCKCHECK) application.
2. Execute the comparison for the affected material and warehouse number.
3. If differences are found, use the application to correct the inconsistency directly.
4. If the inconsistency cannot be resolved via the application, check:
   • Warehouse Monitor → Tools → Message Queue for any stuck queues; reprocess as needed.
   • Analyze Differences application for any unposted entries; post them to clear the discrepancy.
   • Warehouse Monitor → Stock and Bin → Physical Stock: uncheck the Exclude Resource option to verify if the product is assigned to a resource.
5. After resolving the inconsistency, reattempt Goods Issue posting.

Best Practice Recommendation

For business processes requiring conditional batch usability in intercompany transfers:

• Retain Restricted batch status until full business or Quality Assurance (QA) approval is obtained for the intercompany transfer.
• Use QM Inspection Lots and Usage Decisions to transition batches from Restricted to Unrestricted only when the batch is ready for IC-STO processing.

Plan Material Requirements Planning (MRP) demands on Released (Unrestricted) batches only to prevent ATP confirmation blocks and delivery creation failures.

• KBA 3504209 – Batch Status Management Active in SAP S/4HANA Cloud Public Edition
• KBA 3588458 – There are inconsistencies in stock between IM and EWM
• KBA 3027199 – Error VL248 given in Create Outbound Delivery App – SAP S/4HANA Cloud Public Edition
• KBA 3650873 – Outbound delivery cannot be created with error VL248 in VL10B – SAP S/4HANA Cloud Public Edition
• SAP Help Portal: Batch Status Management
• SAP Community Blog: Advanced Intercompany Stock Transfer (5HP) in SAP S/4HANA Cloud Public Edition

80053978, batch not released, conditionally released, restricted batch, ic-sto, nbic, ewm, goods issue blocked, no schedule lines due for delivery, delivery cannot be executed in the background, atp confirmation, batch status management, outbound delivery not created, intercompany sto, s/4hana cloud , KBA , MM-PUR-PO-IC-2CL , Purchase Orders Intercompany Processes (Public Cloud) , Problem