Using Oracle Workflow with Oracle Shipping Execution

Overview of Using Oracle Workflow with Oracle Shipping Execution

Oracle Shipping Execution enables you to utilize Oracle Workflow to enhance your day-to-day business. Using Oracle Workflow with Oracle Shipping Execution is optional; however, if you choose to enable Oracle Workflow with Oracle Shipping Execution, specific tasks and output are enabled through the use of customized business objects. For example, the workflow can be configured so that specific users receive a notification email when an overship or backorder occurs.

The following list represents a few of the enhancements when Oracle Workflow is utilized with Oracle Shipping Execution:

• Workflow Monitor displays Oracle Shipping Execution delivery and trip workflows directly from the Shipping Transactions form or Quick Ship window. See:Viewing Workflow from Shipping Windows.

• Workflows are independent, enabling you to use only those processes, activities, and subprocesses that you need.

  The parameters to enable and disable workflows are located within the Shipping Parameters and Global Parameters. See Oracle Order Management Implementation Guide.

• Ease of communication with other Oracle and non-Oracle Applications

• Ability to print Oracle Shipping Execution documents at any point in the shipping process

• Notifications can be sent to users or external system components (3rd party warehouses, carrier manifest systems, and so on) upon activity completion, errors, or rejections.

Delivery Flow - Generic

This process is initiated when a delivery line is assigned to a delivery and completed when the delivery reaches its final drop-off location. This workflow applies to outbound deliveries, such as a delivery that is created with assigned delivery lines that are picked and ship confirmed. Delivery workflow is not raised for consolidation deliveries.

Delivery Flow - Generic

Trip Flow - Generic

This process is initiated when a trip is created and completed when the ultimate drop-off stop is closed. This workflow applies to trips that are created automatically or manually, such as a trip that is created automatically at ship confirmation.

Trip Flow - Generic

Ship to Deliver Process Workflow

This process models the ship confirm process through the Order Management and Inventory interfaces. This workflow is optional, therefore, Oracle Shipping Execution continues to function without the use of this workflow. This can be enabled if you need it for your business.

Ship to Delivery Process Workflow

Extending Workflows: You can modify or extend workflows through the use of the Oracle Workflow Builder. Certain processes, messages, functions, subprocesses, and properties may be customized. Delivery and Trip workflow offers limited extension capabilities. See Oracle Workflow User's Guideand Oracle Order Management Using Workflow in Oracle Order Management for more information on extending workflows.

Purging Workflows: Workflows are eligible for purging through the use of Oracle Workflow or when deliveries or trips are purged; using Shipping Purge.

Activities and Notifications

Oracle Shipping Execution offers a seeded activity and a seeded notification. Both are available to use in your custom workflows.

The seeded activity is Print Document Set. This activity enables you to print a document set at a specific time during the course of the workflow.

The seeded notification is Delivery is Ship Confirmed. This notification sends information to specified users when a delivery is ship confirmed. This notification can be customized and leveraged to be used in any part of the workflow.

Business Events

Business events are optional. They can be enabled or disabled through the Global Parameters and Shipping Parameters. In addition, individual Business Events can be enabled via the Business Events definition window. See: Oracle Order Management Implementation Manual and Oracle Workflow User's Guide.

The following business events are available for use in Oracle Shipping Execution:

• Delivery

  • Delivery Create: Records the delivery ID

  • Submit Manifest: Records the delivery ID

  • Manifest Response: Records the delivery ID

  • Submitted for ITM Screening: Records the delivery ID

  • ITM Response Received: Records the delivery ID

• Trip

  • Trip Ship Confirmed: Records the trip ID

  • Trip Create: Records the trip ID

• Trip Stop

  • Trip Stop Arrived: Records the trip stop ID

  • Trip Stop Closed: Records the trip stop ID

  • Trip Stop Create: Records the trip stop ID

• Delivery Line

  • Delivery Line Ready to Release: Records the delivery line ID

  • Delivery Line Release to Warehouse: Records the delivery line ID

  • Delivery Line Staged: Records the delivery line ID

  • Delivery Line Back-Ordered: Records the delivery line ID

Viewing Workflow from Shipping Windows

To view workflow status from the Shipping Transactions Form or Quick Ship window

1. Navigate to the Shipping Transactions Form or Quick Ship window.

2. Find and select your delivery or trip.

3. From the Tools menu, select Workflow Status.

   Oracle Workflow Status Monitor

   

4. Select, or deselect, any Activity Type and click Go to limit the activities displayed on the window.

5. Click any of the following links on the Workflow Status window to view the specific information or diagram:

   • Activity History: View the history of activities for the given delivery or trip.

   • Status Diagram: View the workflow status diagram for the given delivery or trip.

   • Participant Responses: View the responses of each participant (user on the notification list) for the given delivery or trip.

   • Workflow Details: View the details of the workflow for the given delivery or trip.

6. Click View Diagram to view the workflow in a graphic format.

   Status Diagram

   

7. Click the Definition, Usage, Status, or Notification tab to display specific information about the workflow.