Why Enable Shipping Workflows?
Integrating workflows into your shipping process provides several enterprise-level advantages:
Process Automation: Automate standard shipping business processes and route activities based on specific business rules.
Enhanced Visibility: Use the Workflow Monitor to visualize the shipping process in real-time, providing an audit trail of all activities
. Proactive Notifications: Automatically notify users of critical events, such as backordered deliveries or high-value shipments.
Seamless Integration: Easily integrate 3rd-party APIs or custom activities, such as automated document printing, at specific points in the flow.
The Three Core Shipping Workflows
In R12, Oracle provides three primary seeded workflows:
Delivery Workflow: Triggered as soon as an order line requiring picking is assigned to a delivery. It manages activities from "Pick Initiated" through the "Ship-To-Delivery" subprocess.
Trip Workflow: Manages the high-level trip process, including "Set In Transit" and "Close" activities
. Ship-To-Delivery Workflow: Specifically models the Ship Confirm process. This is a subprocess of the Delivery workflow but can be managed and extended independentl
Note :Order Line workflows and Shipping workflows operate independently; you cannot drill down from one into the other
- Shipping Transaction Form
- Quick ship user Interface.
Limitations - Some of the limitation of shipping workflow as of now are – As of now this workflow is subject to limited extensions
- You can’t add an activity in this workflow that required response from user.
- Extension of a workflow Defer activity not supported in this workflow.
- These workflows are available for Individual delivery .
- Start
- Pick Initiated
- Ship-To-Delivery (Sub process for Ship Conform).
- End.

Please Note that Shipping workflow as of now available for outbound activities .
Delivery Workflow Triggering Events
This workflow will triggered as soon as an order line required picking is assign to a delivery.
Trip Workflow- Open
- Set in Transit
- Close
Please Note that Order line and Shipping workflow are 2 different things and not related to each other and it is not possible to drill down one flow from another.
As stated earlier advantages of the Oracle is everything is pick and choose , you can enable /disable this workflow as per your requirement , If you don’t want this workflow , just disable It.
Business Events
Please note that once we select any type of the workflow
3. Ship –To-Delivery
Shipping workflow Setup
- Global Parameters
- Shipping parameters
Shipping Parameters
Shipping Parameters will do the setup only for the Organization level, where as Global Parameter will do the setup at the Application level. Auto Sync between Global and Shipping parameters has been provided.
Override Ship To Deliver Workflow – Oracle is Provide this profile option and if mark Yes this will Process the Ship Confirm workflow , In case it got stuck because of some Technical reason.
Best Practices for Customization
While these workflows are highly flexible, there are specific constraints to keep in mind:
Do Not Modify Seeded Workflows: Always create a copy of the seeded workflow and use the provided Lookup setup to assign your custom version to specific organizations.
Avoid User-Response Activities: Shipping workflows currently do not support activities that require a direct response from a user.
Maintenance: Utilize the standard Oracle purging programs, alongside Shipping-specific programs, to clear obsolete workflows and maintain system performance.
Troubleshooting: If a Ship Confirm process becomes stuck due to technical issues, use the profile option "Override Ship To Deliver Workflow" to force processing
If you need More Info , Please let me know and I will send you COMPLETE article.

