Fix Oracle EBS Order Lines Stuck in Awaiting Shipping
EBS Order Management order line stuck in Awaiting Shipping workflow
Also searched as
- Oracle OM sales order line stuck in awaiting shipping
- OEOL workflow stuck order line Order Management R12
- order line not progressing workflow background process EBS
- Workflow Background Process OM deferred activities not running
Short answer
An OM order line sits at Awaiting Shipping because its OEOL workflow is waiting for Ship Confirm, or because the workflow is deferred, errored or never started. Check the line's workflow status in the Workflow Status Monitor, confirm Pick Release and Ship Confirm actually ran, make sure the Workflow Background Process for OEOL is running, and retry the errored activity.
Applies to: Oracle E-Business Suite R12.1 and R12.2 Order Management with Shipping Execution; the same OEOL and OEOH item types exist in 11i
How to diagnose and release the line
- 1Open the order in Order Management > Orders, Returns > Sales Orders, and select the line. Note the line status and use Tools > Workflow Status to see the current activity.
- 2If status is Awaiting Shipping, go to Shipping > Transactions and query the order number. Confirm a delivery line exists and its status (Ready to Release, Staged, Shipped).
- 3If no delivery line exists, the line never released to Shipping. Check holds (Actions > View Holds), then run Pick Release or Release Sales Orders for that order.
- 4If the delivery is Staged but not shipped, finish Ship Confirm. After ship confirm, the Interface Trip Stop SRS program and the OM workflow advance the line to Shipped.
- 5If Workflow Status shows an activity in Error, use the Workflow Status Monitor (Administrator Workflow responsibility) to open the item type OM Order Line, review the error message, and choose Retry.
- 6If the activity is Deferred, make sure a Workflow Background Process for item type OM Order Line is scheduled with Process Deferred = Yes and Process Timeout = Yes.
- 7Run the Workflow Background Process once manually with Item Type = OM Order Line and confirm the line status moves.
- 8Re-query the line and confirm its flow status changed in OE_ORDER_LINES_ALL.FLOW_STATUS_CODE.
How the OEOL workflow decides a line is Awaiting Shipping
Every order line runs a Workflow process from the item type OM Order Line (OEOL). Standard flows such as Order Flow - Generic with Header level invoicing have activities like Schedule - Line, Shipping - Line (Awaiting Shipping), Fulfill and Invoice Interface. A line shows Awaiting Shipping because the workflow is parked on a block activity, waiting for a notification from Shipping Execution that the delivery was ship confirmed.
That means the cause is rarely in OM itself. It is one of: the line was never released (backorder, hold, unscheduled), the delivery detail was released but not confirmed, Ship Confirm completed but the post-confirm programs failed, or the workflow engine is not processing deferred activities. Looking at each in order is faster than guessing.
SELECT l.line_id, l.line_number, l.flow_status_code, l.shipped_quantity,
d.delivery_detail_id, d.released_status
FROM oe_order_lines_all l
LEFT JOIN wsh_delivery_details d ON d.source_line_id = l.line_id
AND d.source_code = 'OE'
WHERE l.header_id = :header_id;Shipping side checks
WSH_DELIVERY_DETAILS.RELEASED_STATUS tells you where the physical process stands: R is ready to release, B backordered, S released to warehouse, Y staged, C shipped. A line stuck at Awaiting Shipping with released status B has been backordered, usually due to insufficient on-hand or an unreserved item. Fix availability, then run Pick Release again.
If released status is C but the OM line still says Awaiting Shipping, the shipping to OM handoff failed. Check the concurrent request log for Interface Trip Stop - SRS and for errors in the Workflow Status Monitor. Often the trip stop interface errored on inventory (see the open interface page on this site), so OM never received the shipped quantity.
Workflow engine health
OM relies on deferred workflow activities. If the Workflow Background Process concurrent program is not scheduled, or its parameters exclude OEOL, activities such as Schedule and Fulfill wait forever and nothing looks broken in the Orders form. Check Concurrent > Requests for scheduled Workflow Background Process runs and verify the last run completed normally.
Query WF_ITEM_ACTIVITY_STATUSES for ITEM_TYPE = 'OEOL' and ITEM_KEY = the line_id to see the activity status, result and error message. ACTIVITY_STATUS values of ERROR, DEFERRED and NOTIFIED each point to a different fix: retry, run the background engine, or respond to the notification.
SELECT a.item_key, pa.instance_label, s.activity_status, s.activity_result_code,
s.error_name, s.error_message
FROM wf_item_activity_statuses s
JOIN wf_process_activities pa ON pa.instance_id = s.process_activity
JOIN wf_items a ON a.item_type = s.item_type AND a.item_key = s.item_key
WHERE s.item_type = 'OEOL'
AND s.item_key = TO_CHAR(:line_id)
ORDER BY s.begin_date;Bulk cases and what not to do
When hundreds of lines are stuck, the cause is almost always one shared fault: the background engine down, a missing Interface Trip Stop run, or a bad setup change such as a deleted shipping parameter. Fix the shared cause and use the Retry Errored Workflow Activities concurrent program (WFRETRY) for the OEOL item type, rather than retrying lines one at a time.
Avoid updating FLOW_STATUS_CODE directly in OE_ORDER_LINES_ALL. It leaves the workflow, shipping and invoicing records out of step, and later steps then fail in new ways. Oracle Support has data fix patches and documented workflow skip procedures for genuine dead-ends; use those and keep a ticket reference.
Common pitfalls
- !Checking only the OM form and ignoring Shipping Transactions, where the real status lives.
- !Forgetting that Workflow Background Process needs separate runs for deferred and timed-out activities.
- !Retrying an activity in Error without reading the error, which loops the same failure.
- !Editing FLOW_STATUS_CODE in SQL, which breaks invoicing and the audit trail.
- !Ignoring holds: a credit check or custom hold stops release without any visible error on the line.
- !Closing inventory periods while ship-confirmed deliveries are still waiting to interface.
How an ERP-grounded AI assistant handles this
An assistant grounded in EBS through ERPray can take an order number, read OE_ORDER_LINES_ALL, WSH_DELIVERY_DETAILS and WF_ITEM_ACTIVITY_STATUSES in read-only mode and tell the order desk which of the four causes applies, showing the queries it ran. It follows your EBS responsibilities. Retrying workflow activities or releasing holds stays a human action with approval. It does not replace OM expertise for unusual flows.
Frequently asked questions
What does Awaiting Shipping actually mean in OM?
The line passed scheduling and is blocked on the Shipping activity in the OEOL workflow, waiting for Shipping Execution to ship confirm the delivery. Until the delivery ships and the result returns to OM, the line stays at that status.
How do I retry many errored OM workflow activities at once?
Run the Retry Errored Workflow Activities program (WFRETRY) from the Workflow Administrator responsibility, with Item Type set to OM Order Line. Fix the shared cause first, or the same activities will error again. For one line, use Workflow Status Monitor and choose Retry on the errored activity.
Why does the line show Awaiting Shipping when the delivery is shipped?
The interface from Shipping to OM did not complete. Check Interface Trip Stop - SRS for errors, check the inventory interface for failed rows, and look for a deferred or errored activity in the workflow. Once the interface succeeds, the line moves to Shipped.
Should I use SQL to move a line forward?
Not as a first choice. Directly changing statuses desynchronises the workflow, shipping and receivables data. Use supported Oracle procedures or Support-provided data fixes, and test on a cloned instance first.
Related
Fix Oracle EBS Workflow Notification Mailer Not Sending Emails
When EBS notifications stop reaching inboxes, check the mailer status in Oracle Applications Manager (OAM) Workflow Manager first - a Suspended or Error status almost always points at an SMTP or IMAP connectivity or credential problem introduced by a mail server change, not at Workflow itself. Fix the mail server configuration, restart the mailer component, and requeue the backlog.
Error fixOracle Workflow error: Attribute does not exist for item type
This Oracle Workflow error means a workflow activity, function, or notification message is referencing an item type attribute (via SetItemAttrText/GetItemAttrText or a &ATTRIBUTE token) that was never defined on that item type, was deleted, or is misspelled - almost always introduced by a custom workflow change that was not fully synchronized. Compare the attribute list in Workflow Builder against every reference to it in the process.
Error fixFix Oracle EBS MTL_TRANSACTIONS_INTERFACE Rows Stuck With PROCESS_FLAG = 3
A row in MTL_TRANSACTIONS_INTERFACE with PROCESS_FLAG = 3 failed validation or processing in the Inventory Transaction Manager. The reason is written to ERROR_CODE and ERROR_EXPLANATION on that row. Correct the data (item, subinventory, locator, period, lot or serial), set PROCESS_FLAG back to 1 and let the Process transaction interface program or the Transaction Manager pick it up again.
Error fixAutoInvoice import fails with invalid line/header exceptions
AutoInvoice rejects lines when the interface data references an invalid or inactive customer, transaction type, GL date outside an open period, currency, or accounting flexfield combination. The AutoInvoice Execution Report and RA_INTERFACE_ERRORS_ALL tell you exactly which interface line and which field failed validation, so start there rather than guessing at the source system feed.
Error fixFix FRM-40735: WHEN-VALIDATE-RECORD Trigger Raised Unhandled Exception ORA-06508
FRM-40735 with ORA-06508 almost always means a PL/SQL package used by the form was recompiled while your session still held the old cached state, or the trigger's own exception handling does not trap a real data error. Exit the form completely and re-enter it; if the error repeats for all users, recompile invalid objects on the database and check for a bad custom trigger.
Error fixOracle EBS Concurrent Manager Will Not Start: How to Fix It
A concurrent manager that will not start in Oracle EBS is almost always one of three things: the node registered in FND_NODES no longer matches the actual hostname (common after cloning), stale OS processes are blocking a fresh start, or the database and listener the manager connects to are unreachable. Check the internal manager log, verify the node name, clear stale processes, and restart with adcmctl.sh.
AI for ERPAI for Oracle E-Business Suite, Without Leaving On-Prem
Add AI to Oracle E-Business Suite 12.2 without moving off-prem. Query concurrent programs, interface tables, and AP/PO data with a private LLM. See how.
AI for ERPAI for Oracle EBS in Industrial Manufacturing: WIP, MRP, and BOM Questions Answered Directly
AI for Oracle E-Business Suite in industrial manufacturing: WIP jobs, BOMs, MRP, inventory and purchasing answered in plain English, private and read-only.
Stuck on Oracle E-Business Suite?
Talk to engineers who work inside Oracle E-Business Suite every week, and who build private AI that answers these questions from your own ERP data.