Shulou(Shulou.com)05/31 Report--

This article will explain in detail the example analysis of Order workflow in Oracle OM. The content of the article is of high quality, so the editor shares it for you as a reference. I hope you will have some understanding of the relevant knowledge after reading this article.

Oracle OM's setup work is not very complex, the main difficulty is the order header and line's different workflow settings.

The workflow of Order is defined by Transaction Type. In the difine interface of transaction type, we first give header the first workflow, and then assign a row flow in assign line flows.

For example:

1. Normal shipping order

Header: Order Flow-Generic

Line:Line Flow-Generic, Ship Only

two。 Returned order

Header: Order Flow-Generic

Line:Line Flow-Return for Credit Only

Here are the header and line workflow activities and process definitions in the OM module:

Populate the order stream:

General order flow:

This order flow has a subprocess of registering and closing orders. This stream can be used for both orders and returns.

General order flow with General title layer invoicing process

This process has a subprocess of registering, invoicing at the header level, and closing orders.

Order flow-returns that require approval

This process has a subprocess of enrolling, notifying, and closing orders.

Implant stream:

Note: unless explicitly specified, all transactions use the default results.

Flow-ATO Project

This stream supports only ATO project lines. It has input lines (waiting for enrollment), plans, create work order / flow plans, send runs, complete lines, invoice lines, and close line subprocesses.

Flow-ATO model

This stream supports only ATO model rows. It has input lines (waiting for enrollment), planning, creating configuration items, completing lines, invoicing lines, and closing line subprocesses.

Line flow-configuration

This stream applies only to configuration item lines that are automatically created when processing an ATO configuration. This flow has subprocesses for creating BOM/ process routes, work orders, and flow plans. In addition, it has a subprocess of launching a run, completing a line, and closing a line.

Flow-configuration that requires authorized shipping

This flow is the same as flow-configuration, except that it has an additional authorization process before the shipping process. This stream is used by users of the distribution management system.

Flow-generic

This flow is an outbound flow that handles all project types, including the configuration project. It has input lines (waiting for enrollment), planning, creating supplies, sending runs, completing lines, invoicing lines, and closing line subprocesses.

Flow-generic items that require authorization to ship

This flow is the same as line flow-generic, except that it has an additional authorization process before the shipping process. This stream is used by users of the distribution management system.

Flow-A general project that requires invoicing at the header level

An example of "Stream-General", which is combined with the implanted header stream to support the invoice at the header level.

Flow-generic, billing only

This stream has only input lines (waiting for enrollment), invoice connections, and closed line subprocesses.

Traffic flow-generic, shipping only

A version of "Stream-General projects that do not require invoicing". This stream can be used for internal orders.

Flow-Standard Service

This stream has an input line (waiting for enrollment), a completion line, an invoice line, and a closed line subprocess. This flow can be used for service lines.

Flow-credit returns only

This stream has an input line (waiting for enrollment), an invoice line, and a closed line subprocess.

Flow-return only for items that need approval

This flow is the same as the line flow-only items are returned, except that it has a process of waiting for header approval after the input line process.

Flow-return of credits to be received

This stream has input lines (waiting for enrollment), RMA receive, invoice lines, and close line subprocesses.

Flow-Credit returns that need to be received and approved

This flow is the same as Row flow-Credit returns to be received, except that it has a process waiting for header approval after the input Line process.

There is no workflow that supports both order and return lines in the system, but it can be defined by itself, but it is generally not recommended. This is the end of the sample analysis of Order workflow in Oracle OM. I hope the above content can be helpful to you and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.