2Implement Business Process Flows

This chapter contains the following:

• Order-to-Cash

• Business-to-Business Messaging

• Drop Ship

• Various Setups

Order-to-Cash

Roadmap for Setting Up Order-to-Cash

Use this road map as the high-level procedure you use to implement order-to-cash.

• Do the tasks that this topic references in the same sequence that the topic displays them.

• Steps after step 3 primarily reference tasks in the Orders functional area. Do each of these tasks depending on your business requirements.

• To do a task, click each one in the Orders area. If the Orders area doesn't display a task, then search for it in the Search Tasks field.

• The set up you do depends on your business requirements. You typically do most or all of the tasks that integrate Order Management. Other tasks depend on your requirements, such as tasks that control order status, constrain changes, or modify an orchestration process.

• The Topic column references topics in Oracle SCM Cloud, Implementing Order Management. Use these topics to get help with the task.

• The Prepare column describes what you do to prepare for implementation. Do this set up before you administer order-to-cash. It will help to avoid interruption and downtime during administration. Use the Prepare column to check off preparation work as you finish it.

• To monitor progress, add a check mark to the Done column when you finish each functional area or task.

• To implement drop ship, see the Implement Drop Ship section in the Implementing Order Management book.

Implement order-to-cash.

1. Read the Guidelines for Implementing Order-to-Cash topic. It contains details that help to make the implementation go smoothly.

2. In the Navigator, click Setup and Maintenance.

3. On the Setup page, click Order Management.

   This topic assumes you will modify the predefined implementation that's available through Setup. For details about setting up a new implementation, see Points to Consider When Implementing Order-to-Cash.

4. Set up these functional areas.

   Functional Area	Done
   Initial Users	_____
   Enterprise Profile	_____
   Organization Structures	_____
   Users and Security	_____
   Items	_____
   Catalogs	_____
   Customers	_____

   These areas reference common tasks. A typical implementation requires that you complete most or all common tasks. For details about how to set them up, see the book titled Oracle SCM Cloud, Implementing Common Features for Oracle SCM Cloud.

5. In the Functional Areas list, click Orders.

6. In the Orders area, click Required Tasks > All Tasks

7. Integrate Order Management. For details, see the Integrate chapter in the Implementing Order Management book.

   Task	Topic	Prepare
   Manage Web Service Details	Create User Credential Keys	_____Gained access to the administrator privilege and administrator role so we can use Oracle Wallet Manager.
   Manage Trading Community Source Systems Manage Upstream and Fulfillment Source Systems Manage External Interface Web Service Details	Integrate Order Management with Source Systems	_____Located the time zone where the server that the source system uses is located. _____Identified the URL that locates the connector that resides on the source system. _____Identified the User Name and Password that the Status Update service requires.
   Manage Trading Community Source Systems Manage Item Relationships	Using Web Services to Integrate Order Management chapter, including Define Your Source System, and Create Cross-References in Order Management	_____Identified source system details _____Identified role and privilege requirements _____Identified cross-reference requirements
   Manage External Interface Web Service Details	Integrate Order Management with Fulfillment Systems	_____Identified an integrated development environment we can use to create a transformation style sheet. _____Acquired the user credentials that the service provider needs when calling their web service. _____Acquired contact details for the IT administrator who works for the service provider. _____Identified the URL that locates the web service that resides on the fulfillment system. _____Acquired the security certificate from the service provider.
   Manage External Interface Routing Rules	Route Requests from Order Management to Fulfillment Systems	_____Created a list that includes the names of the items we must route to fulfillment systems, the unique identifier for each item, and the name of each fulfillment system where Order Management must route the request.

8. Control application behavior. For details, see the Application Behavior section in the Implementing Order Management book.

   Task	Topic	Prepare
   Manage Order Management Parameters	Manage Order Management Parameters	_____ Determined whether our business requirements will allow or disallow the Configurator to choose items in a configuration and to modify a configuration after the user adds a configured item. _____ Determined the date that Order Management must use when it determines the configure options that it displays for a configured item. _____ Determined how Order Management will display the Ship-to Address and the Bill-to Location for each customer during order entry. _____ Determined whether the Configurator stops processing when it encounters an error. _____ Identified the item validation organization that Order Management must use to validate and display items. _____ Identified an Order Management user that the buyer can contact to resolve a problem that occurs with a drop ship. _____ Determined whether the Configurator validates each order that includes a configured item during order import.
   Manage Order Profiles	Manage Order Profiles	_____ Identified the value to use when converting a currency. _____ Identified the currency to display in the Order Management work area. _____ Identified the customer to use when filtering status data on the Overview page. _____ Determined whether use the source order number as the order number during transformation. _____ Determined the number of seconds to wait after an action finishes.

9. Administer pricing. For details, see the book titled Oracle SCM Cloud, Administering Pricing.

10. Import source orders. If you use a source system, then you must import source orders. For details, see the Import section in the Implementing Order Management guide.

    Task	Topic	Prepare
    Not applicable	Import Orders into Order Management	____ Acquired access to our source order data. ____ Identified a tool we can use to manipulate source order data, such as SQL (Structured Query Language), or ODI (Oracle Data Integrator).
    Create Source System Manage Upstream and Fulfillment Source Systems Manage Standard Lookups Manage Item Relationships	Use Web Services to Import Source Orders	____ Determined whether we will use the product model or the product hub. ____ Identified the attributes we will use in the Request Payload.

11. Transform source orders. If you use a source system, then you must transform source orders. For details, see the Transform section in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Product Transformation Rules	Set Up Transformation	____ Acquired user and password we need to sign into the Product Information Management work area.
    Manage Product Transformation Rules	Create Transformation Rules	____ Described the structure of the source order data. ____ Identified the type of transformation that must occur so Order Management can support our source data. ____ Described requirements for pretransformation rules. ____ Described requirements for transformation rules. ____ Described requirements for posttransformation rules.
    Manage Product Transformation Rules	Create Advanced Product Transformation Rules	____ Described requirements for advanced posttransformation rules, if necessary.

12. Set up statuses. For details, see the Sales Order Status section in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Task Status Conditions	Manage Task Status Conditions	____ Described our requirements for managing the statuses that our fulfillment systems provide.
    Manage Status Values Manage Orchestration Process Definitions	Set Up Fulfillment Lines Statuses Add Status Conditions to Fulfillment Lines	____ Described our requirements for managing the statuses for each fulfillment line.
    Manage Status Values	Create Orchestration Process Classes	____ Described our requirements for grouping orchestration process statuses so they're meaningful.
    Manage Orchestration Process Definitions	Add Status Conditions to Orchestration Processes	____ Described our requirements that specify when to set statuses for orchestration processes.

13. Set up processing constraints. For details, see the Constrain Sales Orders section in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Processing Constraints	Manage Processing Constraints	____ Described requirements regarding who can change a sales order, what can change in the sales order, and when the change can occur.
    Manage Constraint Entities	Constrain Changes to Attributes	____ Described requirements regarding the order attributes that can change.

14. Control change orders. For details, see the Change Orders section in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Order Attributes That Identify Change	Manage Order Attributes That Identify Change	____ Described our requirements regarding what changes Order Management will allow on an existing sales order, and when it allows the change, including order attributes, users, and timing.
    Manage Orchestration Process Definitions	Measure the Cost of Change	____ Estimated the business cost associated with each change.
    Manage Orchestration Process Definitions	Compensate Sales Orders That Change	____ Described our requirements regarding the order compensation we will allow Order Management to do.

15. Notify systems when orders change. For details, see the Notify Systems section in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Business Event Trigger Points	Send Notifications from Order Management to External Systems	____ Described our requirements regarding when Order Management must notify external systems that a sales order changed.

16. Use jeopardy to manage delays. For details, see Delays section in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Jeopardy Priorities Manage Orchestration Process Definitions Manage Jeopardy Thresholds	Set Up Jeopardy and Lead Time to Manage Delay	____ Described our requirements regarding when Order Management must notify an order manager that a sales order is in jeopardy, including the threshold when to notify for each step in an orchestration process. ____ Described requirements regarding the amount of lead time that Order Management must use to finish each orchestration process step.

17. Manage task types. For details, see the Task Types section in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Task Types	Set Up Task Types	____ Described our requirements regarding setting up task types.

18. Set up flexfields. For details, see the Flexfields section in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Order Extensible Flexfields	Deploy Extensible Flexfields in Order Management	____ Described our requirements regarding what details we must display in fields, including the data and location in the user interface.

19. Set up orchestration processes. For details, see the Orchestration Processes chapter in the Implementing Order Management book.

    Task	Topic	Prepare
    Manage Orchestration Process Definitions	Guidelines for Setting Up Orchestration Processes	____ Confirmed that the predefined orchestration processes don't meet our requirements. ____ Identified configuration details for each orchestration process that we must create, such as task type to use, change logic, process planning, jeopardy, statuses, and so on.
    Manage Orchestration Process Definitions	Set Up Orchestration Processes	____ Described the IF/THEN rules that we need for each orchestration process. ____ Described orchestration planning and replanning that we need for each orchestration process. ____ Specified the behavior that we need for each orchestration process step, such as the task type to use, the service to call, lead-times, and so on. ____ Created a flowchart mock-up for each orchestration process.
    Manage Orchestration Process Definitions	Deploy Orchestration Processes	Not applicable.
    Manage Orchestration Process Definitions	Set Up Lead-Times for Orchestration Process Steps	____ Described the IF/THEN rules and conditions that determine the lead-time to use for each orchestration process step.
    Manage Orchestration Process Definitions	Select the Fulfillment Lines That Run for Orchestration Process Steps	____ Described the IF/THEN rules that select the fulfillment line to run for each orchestration process step.
    Manage Orchestration Process Definitions	Add Branches to Orchestration Processes	____ Specified subprocesses and parallel processing that our orchestration process requires.
    Manage Orchestration Process Definitions	Pause Orchestration Processes	____ Specified the IF/Then rules that Order Management must use when it pauses each of our orchestration processes and each orchestration process step.
    Manage Orchestration Process Assignment Rules	Assign Orchestration Processes	____ Specified the IF/Then rules that Order Management must use when it assigns each of our orchestration processes and each orchestration process step.
    Not applicable	Automatically Resume Paused Orchestration Processes	____ Identified the pause tasks we will release to resume a paused orchestration process.

• Overview of Order Management Cloud

Guidelines for Setting Up Order-to-Cash

Identify the features you must set up to support the order-to-cash flow in your business environment, then estimate the effort required to set them up.

Consider Features You Must Set Up

Do the preparation described in the Roadmap to Implementing Order-to-Cash topic. This preparation will provide a solid understanding of the features you must implement, and the set up involved.

Estimate Effort Required to Set Up Features

Create a rough estimate of the amount of effort your set up will require. A predefined feature usually needs less set up than a feature that isn't predefined. For example, if you need the configurator and order import, then include the setup effort for them in your project plans, and consider whether you must administer job roles to support them.

Feature	Comes Predefined	Setup Required
Dashboard	Yes	No
Create Order	Yes	Yes
Revise Order	Yes	No
Return Order	Yes	Yes
Search and View Orders	Yes	No
Configurator	No	Yes
Order Import	No	Yes
Order Transformation	No	Yes
Order Status	No	Yes
Constraints	No	Yes
Change Order	No	Yes
Notifications	No	Yes
Jeopardy	No	Yes
Flexfield	No	Yes
Orchestration Process	No	Yes
Process Orders from Trading Partners	No	Yes
Advanced Shipment Notice	No	Yes
Collaboration Messaging Framework	No	Yes
Approve Sales Orders	No	Yes
Screen Orders for Trade Compliance	No	Yes
Integrate Order Management with Transportation Management	No	Yes
Credit Check	No	Yes
Credit Cards	Yes	No
Internal Sales Orders	Yes	No
Attachments	No	Yes

Modify the Predefined Offering or Set Up a New One

Modify the Predefined Offering

Order Management comes predefined with most setup tasks already done for you, but you can modify the predefined offering.

1. In the Navigator, click Setup and Maintenance.

2. In the Setup and Maintenance work area, go to the offering.

   • Offering: Order Management

3. Notice the functional areas that display above functional area Orders, such as Initial Users, Enterprise Profile, and so on. These areas are common areas. For details about how to set them up, see the Oracle SCM Cloud, Implementing Common Features for Oracle SCM Cloud book.

4. In the Functional Areas list, click Orders.

5. In the Orders area, click Required Tasks > All Tasks.

6. In the Orders list, drill into and finish each task as necessary, depending on your business requirements.

   If you find that modifying the predefined offering doesn't meet your business requirements, then create a new implementation.

Create a New Implementation Project

If the predefined offering doesn't meet your business requirements for some reason, then create a new implementation project.

1. In the Navigator, click Setup and Maintenance.

2. On the Setup page, click Tasks > Edit Implementation Projects.

3. On the Implementation Projects page, click Actions > Create.

4. On the Create Implementation Project page, modify the attribute values, as necessary, then click Next.

5. On the Select Offerings to Implement page, in the Name list, expand Order Management.

6. In the Order Management row, and in the Pricing row, enable the Include option, then click Save and Open Project.

   You can create one or more implementation projects for the offerings and options. Each Oracle application creates the task list you must finish for each project you create. An Application Implementation Manager can set up these task lists, and assign and track each task that these lists contain.

7. On the Implementation Project page, in the Task list, expand Order Management, then do the tasks that your business flow requires.

Consider Which Scheduled Processes You Must Run

Scheduled Process	Description	Help Topic
Perform Data Load from Staging Tables	You collect organization parameters from your source system and load them into staging tables. You use Perform Data Load from Staging Tables to process data in these tables.	Collect Data section in the Quick Start for Setting Up Order-to-Cash topic
Refresh and Start the Order Promising Server	Updates the Global Order Promising data.	Set Up Global Order Promising section in the Quick Start for Setting Up Order-to-Cash topic
Load Interface File for Import Import Sales Order Delete Orders From Interface Tables	Use these scheduled processes when you import source orders.	Import Orders into Order Management
Transfer Invoice Details to Supply Chain Financial Flow Orchestration Transfer Ownership Change Events to Receiving	Send details about validated invoices, canceled invoices, and corrected invoices to Financial Orchestration. Send details about the AP Invoice Match from Financial Orchestration to the receiving process.	Specify Events That Indicate an Ownership Change
Update or Close Sales Orders	Order Management might display sales orders and fulfillment lines as open even if it closed all fulfillment lines that these orders and lines reference. You can use Update or Close Sales Orders to fix this problem.	Close Fulfillment Lines That Remain Open
Generate Constraint Packages	Constrain changes your users can make.	Manage Processing Constraints
Publish Extensible Flexfield Attributes	Publish and deploy an extensible flexfield.	Deploy Extensible Flexfields in Order Management
Plan Orchestration Processes	Update an orchestration process plan at regular intervals according to the frequency that your deployment requires.	Set Up Orchestration Processes
Release Pause Tasks	Release a pause task so processing can continue.	Pause Orchestration Processes Until an Event Occurs Automatically Resume Paused Orchestration Processes
Generate Bucket Sets	Automatically keep bucket sets up to date with reference data and transactional data.	Use Decision Tables and Bucket Sets in Business Rules
Import AutoInvoice	Import and validate transaction data from Order Management or financial systems that reside outside of Oracle to create invoices, debit memos, credit memos, and account credits in Oracle Fusion Receivables.	AutoInvoice Import: How Data Is Processed

Consider How Processing Constraints Affect Your Setup

Order Management comes predefined with a variety of processing constraints that limit the changes you can make to attributes or what you can do in the Order Management work area. Examine them to make sure they won't cause problems with your custom set ups. For example, you can't write an order management extension that updates the Quantity attribute on a fulfillment line after Order Management already interfaces the line to billing.

Here are a few more examples of predefined constraints that might affect your custom set up.

Constraint	Description
Ordered Date Update	Prevent updates to the Ordered Date attribute on the order header.
Order Line Deletion	Prevent deleting an order line.
Fulfillment Line Bill-to Customer Update	Prevent updates to the Bill-to Customer attribute on the fulfillment line.
Payment Terms Are Missing	Prevent submitting a fulfillment line when the line doesn't have payment terms.

There are many predefined constraints, but you can filter them to reduce the ones you must examine.

1. In the Setup and Maintenance work area, go to the task.

   • Offering: Order Management

   • Functional Area: Orders

   • Task: Manage Processing Constraints

2. On the Manage Processing Constraints page, use Query by Example to filter the constraint entity. For example, if your set up affects something that happens.

   • On the order header before the user clicks Submit, set the filter for Constraint Entity to Order Header.

   • On the order line before the user clicks Submit, set the filter for Constraint Entity to Order Line.

   • After the user clicks Submit, set the filter for Constraint Entity to Order Fulfillment Line.

3. Refine the search results. Use Query by Example to filter the constrained operation. For example, if your set up.

   • Updates the value of an attribute, set the filter for Constrained Operation to Update.

   • Deletes something, set the filter for Constrained Operation to Delete.

4. Refine the search results. If you know the name of the attribute that your set up manipulates, use Query by Example to filter for it. For example, if your set up updates the value of the Ship-to Customer on the fulfillment line, then.

   • Set the filter for Constraint Entity to Order Fulfillment Line.

   • Set the filter for Constrained Operation to Update.

   • Set the filter for the Attribute Name to Ship-to Customer.

5. In the Details area, examine the conditions to determine whether one of them applies to the behavior you're encountering.

   Assume you create an order management extension that updates the Bill-to Customer attribute on the fulfillment line when the status is Awaiting Billing. At run time you encounter an error that prevents you from updating the line. You decide to examine the constraints.

   • Set the filter for Constraint Entity to Order Fulfillment Line.

   • Set the filter for Constrained Operation to Update.

   • Set the filter for the Attribute Name to Bill-to Customer.

   The Message attribute in the Details area describes that you can't update the Bill-to Customer because Order Management already fulfilled the fulfillment line.

Quick Start for Setting Up Order-to-Cash

Do the minimum steps needed to set up Order Management Cloud when you don't use all the tasks that are available in the Order Management offering, such as setting up a test instance of Order Management.

Caution: This topic doesn't include all the steps and security tasks that are required to fully set up Order Management. It includes only the steps needed so you can receive and fulfill test orders.

For details about how to use the predefined set up, see the Guidelines for Setting Up Order-to-Cash topic.

Summary of the Steps

1. Prepare.

2. Set up common components.

3. Set up item organizations and product models, and import items.

4. Connect source systems and set up customers.

5. Collect data.

6. Set up Global Order Promising.

7. Set up Order Management and Pricing, and test your set up.

Prepare

1. Consider the data you will use in your test environment.

   For example.

   • Items you will add to a sales order

   • Customers who will order the items

   • Item Organization you will use as the source to fulfill each item

   • Units of measure (UOM) you will use

   • Currency you will use in each sales order

   • Users who will create sales orders

   As part of planning your test, create a list for each of these data, such as a list of items, list of customers, and so on. You can then use these details later during set up.

2. Get the URLs, User IDs, and passwords you need to access Order Management Cloud and other applications, such as the Security Console.

   Get these details from the Oracle provisioning team.

3. Get the user name and password for each user. Contact the person who installed the systems to get the user names and passwords they used or specified when they installed and provisioned the application.

   User	Description
   Super user for Oracle Cloud Applications	The default user name is FAADMIN.
   System administrator for the Security Console	Not applicable.
   System administrator for Oracle Identity Manager	The default system administrator is XELSYSADM.

4. Identify details for your test orders.

   • Identify the items that the test orders will contain and the customers who will order them.

   • Identify the item organizations that you will associate with these items.

   • Identify the units of measure (UOMs) and currencies that these test orders will use.

Security Tasks You Might Need to Do

See the Overview of Security Console topic to get a list of tasks you might need to do.

Here are the tasks you can do in the Setup and Maintenance work area after you acquire the super user.

• Manage Job Roles

• Manage Data Security Policies

• Manage Data Access for Users

Set Up Common Components

1. Prepare the super user for user management and configuration.

2. Prepare the IT Security Manager Role.

3. Create the setup task list for the Order Management offering.

   This offering includes the tasks you must do.

   A large task list displays when you create the list for the Order Management offering. Make sure you do step 5, Set Up Enterprise Structures. Also do step 3, Set up Item Organizations, through step 10, Set up Pricing, then create or import orders.

4. Set up implementation users.

   For details, see the Set Up User Roles and Privileges in Order Management topic.

5. Set up the enterprise structure.

   • Use the default enterprise structure for a pilot set up.

   • The Order Management work area displays sales orders for the business units that the current user can access. You must create a separate business unit for each business unit that will receive sales orders.

   • A set is a collection of business units. Order Management uses sets to restrict access to holds and orchestration processes. You must specify a default set when you create a business unit. You can use the predefined Common Set for the default set.

6. Set up users who will do functional testing.

   An implementation user can access a wide range of privileges. To test with users who have fewer privileges, set up users with roles that are specific to Order Management.

   Role	Name
   Job	Order Entry Specialist
   Job	Order Manager
   Job	Order Administrator
   Job	Supply Chain Application Administrator
   Abstract	Error Recovery

   Examine how these roles implement security. Create at least one user for each of these roles.

   • Only the Order Manager role

   • The Order Manager role and the Error Recovery role

   • The Order Administrator role and the Supply Chain Application Administrator role

   The Supply Chain Application Administrator role provides the Order Administrator role.

   For details about job roles, see the Job Roles in Order Management topic.

Set Up Organizations and Product Models, and Import Items

1. Set up item organizations.

   • In the Setup and Maintenance work area, go to the task.

     • Offering: Order Management

     • Functional Area: Organization Structures

     • Task: Manage Item Organizations

   • On the Manage Item Organizations page, set up your item organizations so the Oracle Product Model can use them.

     • You need at least one organization that represents a warehouse where your implementation can collect the supply data it uses to fulfill each order.

     • You must set up each warehouse from a fulfillment system as an item organization in Oracle.

     • You must not associate an item organization with a business unit.

     For details, see these topics.

     • Item Organization

     • Item Master Organization

2. Set up your units of measure.

   • In the Setup and Maintenance work area, go to the task.

     • Offering: Order Management

     • Functional Area: Items

     • Task: Manage Units of Measure

   • Use the Manage Units of Measure page to set up your Units of Measure so the Product Information Management work area can use them.

     For details, see topic How Units of Measure, Unit of Measure Classes, and Base Units of Measure Relate to Each Other.

   • Set up Product Information Management.

     Product Information Management must contain the items that each test order references. For details, see the Define Product Information Management section in the Using Product Master Data Management book.

3. Define item classes, items, and catalogs according to your test requirements.

4. Optional. Use an order import template to import the items that your test orders will reference. Transform orders, as necessary.

   For details, see these references.

   • The Import and Transform chapter in the Implementing Order Management book.

   • The Item Imports topic.

   • The Define Product Information Management section in the Using Product Master Data Management book.

Connect Source Systems and Set Up Customers

1. Optional. Set up and connect the source system.

   Here's when you must set up and connect the source system.

   • You plan to use a source system. For details, see the Integrate Order Management with Source Systems topic.

   • You plan to import customer data from a source system.

   • You plan to use cross-references. For details, see the Cross-References in Order Management topic.

   If you will use only the Order Management work area to create sales orders, then you don't need to set up a source system.

2. Optional. Import customers.

   • In the Setup and Maintenance work area, go to the task.

     • Offering: Order Management

     • Functional Area: Customers

     • Task: Import Person and Organization

   • On the Manage Data Import Batches page, click Actions > Create to create an import batch.

   • Use an Extract, Transform, and Load tool to load your data into the interface tables.

   You can use this import process to import a batch from the interface tables into Trading Community Architecture. The batch you import must include the customers your orders will reference. For details, see topics Defining the Import Process for Customers and Consumers: Points to Consider, and Defining the Import Process for Customers and Consumers: Worked Example.

Get Customer Details when Not Integrating or Importing

If you don't integrate with a source system or fulfillment system, or if you don't import customers, then create customers in one of these ways.

• Create them in Oracle Fusion Financials.

  • In the Setup and Maintenance work area, go to the task.

    • Offering: Financials

    • Functional Area: Customers

    • Task: Create Customer

    For details, click the help icon on the Create Organization Customer page. Also, see the user book for Oracle Trading Community Architecture.

• Synchronize them in Trading Community Architecture. If the customer and customer entities that Order Management needs to fulfill the sales order don't exist, then Trading Community Architecture synchronizes the customer master with customer details from the sales order. Important details include sold-to party, ship-to party, and bill-to account.

Collect Data and Set Up Global Order Promising

For details, see these topics.

• Collect Planning Data for Order Management

• Set Up Promising and Sourcing Rules for Order Management

Set up Order Management and Pricing, and Test Your Set Up

You must set up connections to order capture systems and fulfillment systems, then deploy the predefined data that specifies how Order Management fulfills each order.

1. Set up order management parameters according to your testing requirements.

   For details, see the Manage Order Management Parameters topic.

2. Do the minimum setup tasks that a test environment requires.

   • In the Setup and Maintenance work area, go to the functional area.

     • Offering: Order Management

     • Functional Area: Orders

   • Do the setup tasks.

     Task	Description
     Manage Order Profiles	Set up values for these profile options. Display Currency Currency Conversion Type For details, see the Use Order Profiles to Control Order Management Behavior topic.
     Manage Orchestration Process Definitions	Set up and deploy these predefined orchestration processes. ShipOrderGenericProcess ReturnOrderGenericProcess For details, see the Setting Up Orchestration Processes topic.

     For a complete list of tasks, see the Roadmap to Setting Up Order-to-Cash topic.

3. Deploy the required processing constraints.

   • In the Setup and Maintenance work area, go to the task.

     • Offering: Order Management

     • Functional Area: Orders

     • Task: Manage Processing Constraints

   • On the Manage Processing Constraints, search for the constraint, then verify that the Enabled attribute for it contains a check mark.

     Attribute	Value
     Constraint Name	UPDATE SHIPPING REQUEST VALIDATION You must deploy this constraint.

     The validation rule sets in this constraint prevent Order Management from attempting to update the validation for each shipping request when certain conditions are true.

     Validation Rule Set	Makes Sure That
     Ordered Quantity Isn't Zero	The ordered quantity on the fulfillment line isn't zero. If its zero, then the line is in Canceled status and we don't want to process it.
     Update Shipping Request Validation	Data validation doesn't fail for the Update Shipping fulfillment service because the flow doesn't provide values for all the required attributes.
     Fulfillment Organization ID Is Null	The Warehouse attribute on the fulfillment line contains a value. Order Management uses the Warehouse attribute to populate the fulfillment organization ID.
     Fulfill Line Request Dates are Null	The requested ship date or the requested arrival date on the fulfillment line contains a value. We can't calculate shipping dates if we don't have a value in one of these attributes.
     Scheduled Ship Date on the Fulfillment Line Is Empty	The scheduled ship date on the fulfillment line contains a value. We can't calculate shipping dates if we don't have a value in this attribute.

   • Enable or add other constraints to meet your needs, as necessary. For details, see the Manage Processing Constraints topic.

   • Click Generate Packages.

     This action deploys all enabled constraints into your implementation.

4. Optional. Set up the orchestration that your test environment requires.

   • Set up and deploy orchestration processes.

   • Set up status codes.

   • Manage change orders.

   • Set up jeopardy and planning.

   • Release and deploy orchestration processes.

   • Create processing constraints.

   For details, see the chapters that describe controlling order processing and setting up orchestration processes in the Implementing Order Management book.

5. Set up pricing.

   If you use Order Management to create sales orders, and don't import them or integrate to a source system that contains price details, then you must set up pricing. Order Management requires details about pricing entities, such as the pricing strategy, to determine price for each item that you add to the sales order.

   You can't submit a sales order in Order Management without the price. For details about how to set up pricing, see the Oracle SCM Cloud, Administering Pricing book.

   In addition, it might be necessary to do this.

   • Set up the Item Validation Organization order management parameter.

   • Get access to pricing_mgr_operations, which is the job role you need to administer pricing segments, pricing strategies, price lists, and so on.

6. Test your set up.

   • Use a tool of your choice, such as SOAP (Simple Object Access Protocol), to simulate sending a test order. Note the order number.

   • In the Order Management work area, use the order number to search for the order.

   • Confirm that Order Management received the order and is processing it.

Setting Up Other Features

Feature	Description
Drop Ship	The set up for drop ship depends on your business requirements. For details, see the Drop Ship section in the Implementing Order Management book.
Internal Material Transfer	Internal Material Transfers comes predefined as available. The predefined job roles include this feature. No setup is required except that an option in Supply Chain Orchestration determines whether inventory routes the transfer order to Order Management. For details, see Supply Chain Orchestration: Overview.
Back-to-Back Shipping	Back-to-back shipping can create supply only after Order Management successfully submits the sales order to order fulfillment. Back-to-back shipping can then create supply in these ways. Procure supply from a supplier that resides outside of your organization. Produce or assemble supply at an in-house manufacturing location. Transfer material from another warehouse. Reserve on-hand supply. The fulfillment warehouse receives the supply, then back-to-back shipping ships it to the customer. For details, see Back-to-Back Fulfillment: Overview.
Configure to Order	Use Configure to Order to efficiently fulfill each configured item. Here are the order management parameters you can set to control the configurator. Allow Changes Through Configurator Validation Configuration Effective Date Halt Configurator Validation on First Error Use Configurator for Order Import Validation You can also use Configure to Order to set up a kit. A kit is a configured item that includes one or more configure options, but the Order Management work area doesn't allow the Order Entry Specialist to modify the configure options of a kit. You set the subtype for a kit to KIT-SMC when you set up the configuration model. Order Management sends the shippable lines of a kit as a shipment set to Global Order Promising. The Order Management work area doesn't display values for On Hand and Item Availability for kits because Global Order Promising doesn't support the quick availability check feature for kits. For details, see these resources. Configurator Modeling Guide Manage Order Management Parameters topic
Integrate Order Management with Upstream Source Systems	You use a file or web service to import source orders from a source system. For details, see these sections in the Implementing Order Management book. Import Web Services Upstream Source Systems
Integrate Order Management with Downstream Fulfillment Systems	Use a web service to allow Order Management to communicate with a fulfillment system. Use a predefined web service or create a new one. For details, see the Downstream Fulfillment Systems section of the Implementing Order Management book.

• How the Order Orchestration and Order Promising Processes Use the Collected Planning Data

• Overview of Security Console

• How Units of Measure, Unit of Measure Classes, and Base Units of Measure Relate to Each Other

Overview of Implementing Order Management Cloud

Get started with your Order Management Cloud implementation. Sign in with the Application Implementation Consultant role (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB), then opt into the offerings that meet your business requirements.

For details about how to manage the opt-in and set up offerings, see the Oracle Applications Cloud Using Functional Setup Manager book on My Oracle Support.

Order Management Cloud Offering

Use the Order Management Cloud offering to automate order fulfillment and process your sales orders so they're timely, complete, and accurate.

Here's the functional areas you can use with the offering.

Functional Area	Description
Orders	Do a wide variety of set up tasks for Order Management, from managing how you import your source orders, transforming source orders, integration, application behavior, business rules, orchestration, and so on.
Pricing	Set up pricing for Order Management. For example, define pricing parameters, totals, elements, bases, messages, matrix types, lookups, and so on.

To get the complete list of functional areas and features, use the Associated Features report when you plan your implementation.

Upgrade or Update

To upgrade or update your release, go to Performing Your Quarterly Update (Doc ID 2337485.1) on My Oracle Support to get important details.

• Plan Your Implementation

• Overview of Functional Setup Manager

Business-to-Business Messaging

Overview of Business-to-Business Messaging in Order Management

Use Order Management Cloud as your central location when you interact with more than one channel.

Improve order capture and order fulfillment in the order-to-cash flow when you communicate a sales order between businesses.

The business-to-business flow uses Collaboration Messaging Framework to automate message flow so Order Management can receive and process each source order from a trading partner, then reply with an advance shipment notice after shipping successfully finishes.

Web services use Open Applications Group Integration Specification (OAGIS) messages in the payload that it uses to handle interactions that occur between Oracle Cloud Applications and each trading partner. You can use your existing Electronic Data Interchange (EDI) infrastructure with OAGIS. Use this configuration to receive each source order, then your trading partner and supplier can process it through order fulfillment.

Use the business-to-business flow to achieve results.

• Process purchase order

• Change purchase order

• Cancel purchase order

• Acknowledge purchase order

• Acknowledge a change in the purchase order

Use the business-to-business flow to realize benefits.

• Reduce cost

• Increase processing speed and accuracy

• Improve relationships between business partners

• Simplify setup and management

Calculate Ship Dates

If a delay in supply occurs, then Supply Orchestration might send an update for the scheduled ship date to Order Management. Order Management updates the scheduled ship date but doesn't update the scheduled arrival date on the fulfillment line.

Order Management updates the scheduled ship date, scheduled arrival date, and shipping method only if you set up Global Order Promising to calculate shipping, such as how to calculate transit time. If you don't set it up, the scheduled dates and shipping method might not contain a value.

This behavior affects fulfillment, including choices that your end-users make when they override the schedule. For details, see the Schedule Fulfillment Lines Manually topic.

How Business-to-Business Messaging Works in Order Management

Collaboration Messaging Framework uses a web service to communicate sales order details between your trading partner and Order Management Cloud. It communicates these details in XML payloads.

Note.

1. A trading partner uses a web service endpoint that they set up and enabled on their server to send an XML document that contains source orders to the CollaborationMessage web service on Collaboration Messaging Framework.

2. Collaboration Messaging Framework converts each source order to a CSV format (comma separated value) that Order Management supports.

3. Collaboration Messaging Framework uses a web service to upload the CSV files to a folder in Oracle WebCenter Content.

4. You use the order import template and a scheduled process to convert CSV files into sales orders.

5. Collaboration Messaging Framework subscribes to a business event that the scheduled process raises when it finishes. Order Management recognizes the event, then sends an order acknowledgment in an OAGIS message (Open Applications Group Integration Specification) through Collaboration Messaging Framework to the trading partner.

6. Order Management processes the sales order, then sends it to shipping for order fulfillment.

7. Oracle Fusion Shipping creates and processes the shipment.

8. Shipping finishes delivery, then sends the ship confirm and advanced shipment notice in an OAGIS message, through Collaboration Messaging Framework, then in a reply to the trading partner.

Types of Messages That Collaboration Messaging Can Send and Receive

Collaboration Message	Description
OAGIS_10.1_ACK_PO_COLLAB_MSG_OUT	Send acknowledgment to the trading partner that Collaboration Messaging received the purchase order.
OAGIS_10.1_ACK_CHANGE_PO_COLLAB_MSG_OUT	Send acknowledgment to the trading partner that Collaboration Messaging received the purchase order change.
OAGIS_10.1_PROCESS_SHIPMENT_COLLAB_MSG_OUT	Send details to the trading partner about shipments.
OAGIS_10.1_PROCESS_RCV_DEL_COLLAB_MSG_OUT	Send details to the trading partner about purchase order deletions.

Here are the types of messages that Collaboration Messaging can receive from the trading partner.

Collaboration Message	Description
OAGIS_10.1_PROCESS_PO_COLLAB_MSG_IN	Process purchase orders.
OAGIS_10.1_CHANGE_PO_COLLAB_MSG_IN	Change purchase orders.
OAGIS_10.1_CANCEL_PO_COLLAB_MSG_IN	Cancel purchase orders.

Set Up Business-to-Business Messaging in Order Management

Use the Collaboration Messaging work area to set up the business-to-business flow in Order Management.

Assume you must create a relationship between customer Computer Service and Rentals, who resides in Oracle Cloud Applications, and trading partner Computer Associates.

• Allow Computer Service and Rentals to receive sales orders, updates, and cancellations from Computer Associates

• Allow Computer Service and Rentals to send acknowledgments and shipments to Computer Associates

Summary of the Steps

1. Identify the trading partner and messages to send and receive.

2. Create a relationship between trading partner and customer.

3. Simulate collaboration messaging.

4. Import source orders.

5. Process the sales order in shipping.

6. Examine the results.

This topic includes example values. You might use different values, depending on your business requirements.

Identify the Trading Partner and Messages to Send and Receive

1. Sign into Oracle Cloud Applications with a job role that includes the B2B Messaging Administration Duty role.

   Here are the job roles you can use.

   • Order Entry Specialist

   • Order Manager

   • Order Administrator

   • Supply Chain Application Administrator

   • Warehouse Manager

2. In the Navigator, click Collaboration Messaging.

3. Click Tasks > Manage Trading Partners.

4. On the Manage Trading Partners page, click Actions > Create.

   Use Manage Trading Partners to communicate with a trading partner directly or through a service provider. For example, communicate through a service provider to set up a solution where the trading partner must use EDI (Electronic Data Interchange), a modified XML format, a proprietary format, and so on.

   In this example, you set up the configuration to communicate directly with the trading partner.

5. In the Create Trading Partner dialog, set values, then click Save and Close.

   Attribute	Value
   Service Provider	None Computer Service and Rentals will communicate directly with Computer Associates instead of going through a service provider, so set this attribute to None.
   Trading Partner ID	ComputerAssociates
   Partner ID Type	Generic

6. Specify how to send messages to the trading partner.

   In the Delivery Methods tab, click Actions > Add Row, set values, then click Save and Close.

   Attribute	Value
   Name	CMKDelivery00
   Delivery Method	Web Service
   Service Name	CollaborationMessage.Process
   Not applicable	This integration uses the Process method of the CollaborationMessage web service. Make sure the trading partner already deployed this web service on their server.
   Security Policy	None
   Endpoint	Enter the URL that locates the server and port that the trading partner uses at their location as the end point for their web services. For example. http://ComputerAssociates.com:7012
   User Name	Enter the user name that the trading partner server requires to access the endpoint.
   Password	Enter the password that the trading partner server requires to access the endpoint.

7. Set up the messages that Collaboration Messaging sends to the trading partner.

   Click Outbound Collaboration Messages, then add these rows.

   Name	Collaboration Message
   CMKORDERACK001	OAGIS_10.1_ACK_PO_COLLAB_MSG_OUT
   CMKORDERACK002	OAGIS_10.1_ACK_CHANGE_PO_COLLAB_MSG_OUT
   CMKSHIPCONFIRM001	OAGIS_10.1_PROCESS_SHIPMENT_COLLAB_MSG_OUT

   Note.

   • Set the Status to Active for each message.

   • Enter text that describes the message contents.

8. Click Save

9. Set up the messages that Collaboration Messaging receives from the trading partner.

   Click Inbound Collaboration Messages, then add these messages.

   Name	Collaboration Message
   CMKORDERIN001	OAGIS_10.1_CANCEL_PO_COLLAB_MSG_IN
   CMKORDERIN002	OAGIS_10.1_CHANGE_PO_COLLAB_MSG_IN
   CMKORDERIN003	OAGIS_10.1_PROCESS_PO_COLLAB_MSG_IN

   Set the Status to Active for each message.

10. Click Save and Close.

Create a Relationship Between Trading Partner and Customer

You will create a relationship between customer Computer Service and Rentals and the trading partner, Computer Associates. You also identify the documents that you must enable for the partner.

1. On the Overview page, click Tasks > Manage Customer Collaboration Configuration.

2. On the Manage Customer Collaboration Configuration page, search for the customer who will receive communications from the trading partner.

   For this example, enter Computer Service and Rentals. Assume you already set up Computer Service and Rentals as a customer. If you haven't, then you must do so now. For details, see Customer Data Management Offering: Overview.

3. In the search results, if more than one row exists for this customer, then click the row that includes a check mark in the Ship to Party option and the Collaboration Configured option, then click Edit Collaboration Configuration.

4. On the Edit Customer Collaboration Configuration page, in the Associated Service Providers area, click Actions > Add Row, then set values.

   Attribute	Value
   Service Provider	None
   Trading Partner ID	ComputerAssociates Note that you specified this ID earlier in this topic when you identified the trading partner.
   Order Processing Business Unit	Specify the business unit that processes each sales order that Order Management Cloud receives. For this example, Computer Service and Rentals resides in the Vision Operations business unit, so choose Vision Operations.
   Application Partner Code	Accept the default value.

5. In the Collaboration Documents for Service Provider area, add these documents.

   • PROCESS_PO_IN

   • CHANGE_PO_IN

   • CANCEL_PO_IN

   • ACKNOWLEDGE_PO_OUT

   • ACKNOWLEDGE_CHANGE_PO_OUT

   • PROCESS_SHIPMENT_OUT

   Note.

   • You use this area to specify the documents that this customer will communicate with the trading partner.

   • Set the Association Status to Enabled for each document.

6. Click Save and Close, then click Done.

   The customer can now communicate with the trading partner.

Simulate Collaboration Messaging

1. Click Tasks > Validate Inbound Collaboration Messaging Setup.

2. On the Validate Inbound Collaboration Messaging Setup page, set values.

   Attribute	Value
   Service Provider	None
   From Partner ID	ComputerAssociates
   Not applicable	You will be testing a flow that sends a new source order from the trading partner, Computer Associates, so you use the Partner ID that you specified earlier in this topic.
   External Message ID	Enter the number that identifies the message you're testing, such as 08192016_001.
   External Message Name	OAGIS_10.1_PROCESS_PO_COLLAB_MSG_IN
   Processing Service	CollaborationMessage.Process

3. Click Create Message Payload.

   Notice that the Message Payload area uses the settings that you specified in step 2 to create, then display the XML that this test will use to communicate the message. You can modify the XML, if necessary.

4. Click Process.

   A separate web service in Collaboration Messaging simulates communication from the trading partner. It receives the XML document, validates it, then displays a Processing Confirmation dialog that includes the XML result of the test. If the test is successful, then the XML will include this code.

   <ProcessingResultCode><Success>/<ProcessingResultCode>

5. Make a note of the line that includes the message ID, such as.

   <BODID>IN_8001</BODID>

   In this example, IN_8001 is the message ID.

Import Source Orders

The simulation created a simulated source order. Next, you import it order into Order Management and view it.

1. Use a scheduled process to import the source orders. For details, see the Import Orders into Order Management topic.

   • When you run the Load Interface File for Import scheduled process, set the Data File to the file that Messaging Framework created when you simulated collaboration messaging. The data file will include a concatenation of the document name plus the message ID. For example.

     PROCESS_PO_IN-1.0-IN_8001
     

   • Set the Source System to ORA_ELECTRONIC_DOCUMENTS when you run the Import Sales Order scheduled process. Order Management uses this predefined source system for each source order it receives from the trading partner.

   • As an option, in the Batch Name parameter, specify the unique ID of the message you received, such as 08192016_001.

   • Order Management uses the setup from the Pricing work area to determine pricing. It will ignore any pricing data that the source order contains.

   • When the Import Sales Order scheduled process finishes, Order Management can process the sales orders through order fulfillment.

2. In the Order Management work area, on the Overview page, search for the simulated order, such as Demo_Order.

3. In the search results, note that the value in the Source Order attribute includes the order number you simulated, such as Demo_Order_0819_001.

4. In the Order column, click the order number.

5. On the Order page, notice that the order status is Processing, and the fulfillment line status is Awaiting Shipping, which indicates that Order Management released the sales order to order fulfillment.

   The messaging framework creates an acknowledgment message, then publishes it to the trading partner.

Process the Sales Order in Shipping

1. In the Shipments work area, on the Overview page, search for the sales order you noted in the Source Order attribute earlier, such as Demo_Order_0819_001.

2. On the Edit Shipment Line page, click Cancel.

3. On the Manage Shipment Lines page, click Actions > Pick Release, then click Save and Close.

4. On the Overview page, search for Demo_Order_0819_001.

5. On the Edit Shipment Line page, notice that the Line Status is Staged, then click the link next to Shipment.

6. On the Edit Shipment page, click Ship Confirm, then click Save and Close.

   Shipping creates an event. Collaboration Messaging subscribes to this event.

7. On the Manage Shipments page, in the row for your shipment, notice that the ASN Status is Sent.

   This status indicates that Shipping sent the ASN status to Collaboration Messaging.

Examine the Results in Collaboration Messaging

1. In the Collaboration Messaging work area, click Tasks, then click Manage Collaboration Messaging History.

2. In the Search area, set the value, then click Search.

   Attribute	Value
   Document	PROCESS_PO_IN

3. In the Messages area, in the External Message ID column, click the row that references the message you simulated earlier, such as 08192016_001.

4. Click Actions, then click a menu item.

   Menu Item	Description
   View Source Document	View the input XML that Collaboration Messaging received from the trading partner.
   View Output Document	View the output XML that Collaboration Messaging converted from the input XML, and then sent to Order Management.

5. Click Done.

6. Click Tasks > Manage Collaboration Messaging History.

7. Examine the results of the acknowledgment.

   In the Search area, set the value, then click Search.

   Attribute	Value
   Document	ACKNOWLEDGE_PO_OUT

8. Examine the results of the shipment.

   In the Search area, set the value, then click Search.

   Attribute	Value
   Document	PROCESS_SHIPMENT_OUT

• Import Orders into Order Management

Drop Ship

Overview of Drop Ship in Order Management

Drop ship is a supply chain management technique where the seller relies on a supplier or contract manufacturer to build, store, and ship an item to your customer. You can use Order Management Cloud to automate this process.

Note.

• Assume your customer places a sales order with you and you want to drop ship it.

• Order Management sends a purchase request to Oracle Procurement Cloud, which places a purchase order with your supplier, then your supplier ships directly to your customer.

• You provide a purchase order for the item and instructions that describe how to ship directly to the customer.

• The supplier or contract manufacturer ships the item, and your company earns a profit.

Use drop ship to get results.

• Reduce costs for holding inventory.

• Let you supplier manage part of the supply chain, such as fulfilling and shipping the item, instead of you having to do it.

• Forecast and plan for future demand.

• Let your customer place an order with you, and let you promise a ship date.

• Automatically place an order with your supplier.

• Let your supplier ship directly to your customer.

• Receive notification from your supplier when your shipment has shipped.

• Let the buyer modify the purchase order.

• Combine more than one sales order into a single purchase order, then fulfill them together.

• Modify a sales order after you create the purchase order.

• Manage change orders.

Note.

• You can drop ship a standard item, configured item, kit, configuration model, pick-to-order item, or assemble-to-order item.

• You can't drop ship an item that isn't shippable, such as a coverage item, subscription, or warranty.

• Your customer can return a drop ship order only to your warehouse. Your customer can't return a drop ship order directly to the supplier.

• You can't use a third party application in your drop ship flow.

• Schedule Fulfillment Lines Manually

How Drop Ship Works in Order Management

Use Order Management to manage your drop ship flow.

Note.

1. An order capture system captures a source order.

   • Each horizontal row in the diagram represents a system or application.

   • The drop ship flow is a variation of the order-to-cash flow.

   • Order Management comes predefined to capture sales orders in the Order Management work area. You can also capture source orders in an order capture system that resides outside of Order Management.

2. Order Management assigns an orchestration process to the sales order, uses the Schedule Order task to start scheduling the sales order, then sends a scheduling request to Global Order Promising.

3. Global Order Promising considers sourcing rules, supplier calendar, capacity, and so on to identify the supplier and supplier site that can fulfill the order in the most efficient way. If the sales order specifies a supplier, then Global Order Promising uses this supplier.

4. The orchestration process gets the requisition organization from Supply Chain Financial Orchestration so it can create a purchase request.

5. Order Management sends a purchase request to Oracle Procurement.

   Note.

   • Procurement doesn't use the Product Category or Product Fiscal Classification to create a purchase order.

   • Order Management doesn't set a default value for the Product Category attribute on the order line. The Order Entry Specialist can specify this value when setting tax determinants, but Order Management doesn't send it to Procurement, so the purchase order doesn't contain a value for Product Category. For details, see the Edit Tax on Order Lines topic.

   • Order Management sets a default value for the Product Fiscal Classification in the sales order. The purchase order in Procurement also has a Product Fiscal Classification attribute and Procurement sets it to the same value that's on the sales order, but it isn't required.

6. Procurement creates a purchase requisition, approves the requisition, creates a purchase order, then sends the purchase order to the supplier.

   

   Note.

   This Attribute. . .	. . . References This Attribute
   Customer Sales Order attribute in the Purchase Requisitions work area	Number attribute on the sales order in the Order Management work area
   Requisition attribute in the Purchase Orders work area	Requisition Number attribute in Purchase Requisitions
   Drop Shipment PO attribute on the Supply Details tab of the fulfillment line in the Order Management work area	Purchase order
   Requisition attribute on the Supply Details tab of the fulfillment line in the Order Management work area	Purchase requisition

   • Order Management sets the order line status when Procurement creates the requisition and the purchase order.

     What Procurement Does	Order Line Status
     Creates the requisition.	Requisition Created
     Creates the purchase order.	Awaiting Shipping Receiving can send advance shipment notice (ASN) details to Order Management after the status goes to Awaiting Shipping. Receiving can create an ASN for the entire quantity or for only part of the quantity.

   • If a blanket purchase agreement exists, then Procurement might source the requisition from the agreement.

   • Procurement sends responses to Order Management while the purchase order moves through its lifecycle.

     Response	What Procurement Did
     PO_IMPLEMENTED	Created the purchase order.
     PO_CO_IMPLEMENTED	Added a change to an existing purchase order.
     PO_CO_RESCINDED	Rejected a change in the purchase order.
     REQ_LINE_CANCEL	Canceled a line in the purchase requisition.

7. The supplier examines the purchase order and uses your shipping fulfillment system to ship the item to the customer. The enterprise supplier also communicates with the receiving part of Inventory Management to cost the shipment.

8. The supplier uses a supplier portal to enter an ASN. Order Management sends the notice to interested parties and Financial Orchestration. For details about the supplier portal, see the Supplier Portal topic.

9. The receiving part of Inventory Management creates a logical receipt in the receiving organization. It doesn't create a physical receipt because the supplier ships the item directly to your customer.

10. Financial Orchestration runs a financial flow that comes predefined to handle drop ships, and that specifies how to handle the flow that runs from the supplier to the customer.

11. Cost Management does receipt accounting and cost accounting.

12. Order Management waits to receive the advance shipment notice from receiving. The notice indicates that the item shipped and that the customer acknowledged receipt.

13. Order Management communicates with Oracle Receivables to create an invoice and process payments.

You can modify some of these steps. For example, use Manage Sourcing Rules to modify how Global Order Promising considers sourcing rules, or use Manage Drop Ship Financial Flows to modify how Supply Chain Financial Orchestration sets up a relationship between the selling business unit and the requisition organization. For details, see the Set Up Drop Ship in Order Management topic.

• How Order-to-Cash Works in Order Management

• How Order-to-Cash Works with Order Capture Systems

• Supplier Portal

Guidelines for Setting Up and Using Drop Ship

Use guidelines to help you set up drop ship in Order Management.

Set Up Features

Each feature comes predefined as already available except for Fulfill a Customer Order Through Drop Shipment and Handle Landed Cost Charges for Drop Ship Receipts. Each feature includes a predefined job role.

Feature	Setup Required
Fulfill a Customer Order Through Drop Shipment	Yes
Automatic Change Management on Drop Ship Orders	No
Change Drop Ship Orders from Check Availability Page	No
Partial Shipment on Drop Ship Orders	No
Analytics with Supplier Source	No
Create Relationship between Selling Business Unit and Requisition Business Unit	Yes
Automate Financial Flow	Yes
Order Promising for Drop Ship	Yes
Create ASNs for Drop Ship Receipts	Yes
Create Accounts Payable Invoices for Drop Ship Receipts	Yes
Process Accounting for Drop Ship Transactions	No
Handle Landed Cost Charges for Drop Ship Receipts	Yes
Report Gross Margins for Drop Ship Orders	No
Report In-transit Inventory for Drop Shipments	No

Create Sales Orders

You can use different technologies to provide supplier details when you create the sales order, depending on your implementation requirements.

Note.

• Specify a value in the Supplier attribute to implicitly start the drop ship flow.

• Manually set Supplier and Supplier Site attributes on the sales order, or create a sourcing rule that does it automatically.

Use REST API, file-based data import, or a web service to create the order.

Different technologies use different attribute names to represent the same data.

Technology	Description
Sales order in the Order Management work area	As an option, set the Order Type attribute to Drop Ship Orders on the order header. Set the Supplier attribute and Supplier Site attribute on the Supply tab of the order line. If you don't specify a value for supplier site, then Procurement sets it according to rules in Procurement.
Sourcing rule in the Order Promising work area	Use the Manage Sourcing Rules page in the Order Promising work area. Set the attributes. Supplier Supplier Site
REST API	Use the salesOrdersforOrderHub REST resource. In the request payload, provide. SupplierId SupplierName (optional) SupplierSiteId SupplierSiteName (optional) TransactionType or TransactionTypeCode For example. { "SourceTransactionNumber":"87956", "SourceTransactionSystem":"GPR", "SourceTransactionId":"87956", "BusinessUnitName":"Vision Operations", "BuyingPartyName":"Computer Service and Rentals", "BuyingPartyContactName":"Brian Smith", "TransactionType":"Standard Orders", "RequestedShipDate":"2019-10-19T20:49:12+00:00", . . . "SupplierId" : 11176859, "SupplierName" : "Green Bytes Inc.", "SupplierSiteId" : 76846573869, "SupplierSiteName" : "Denver Distribution Center" "TransactionType" : "Dropship Orders" "TransactionTypeCode" : "STD_DS" . . . }
File-Based Data Import	Use the SourceSalesOrderImportTemplate.xlsm file. On the DOO_ORDER_HEADERS_ALL_INT worksheet, set the Transaction Type Code to STD_DS. On the DOO_ORDER_ADDRESSES_INT worksheet. Set the Address Use Type attribute to SUPPLIER. Specify a value for at least one of these attributes. Requested Supplier Code Requested Supplier Number Requested Supplier Name Specify a value in the Requested Supplier Site Identifier attribute.
Web Service	Specify TransactionType or TransactionTypeCode on the order header in a web service payload. Specify RequestedSupplierName and SupplierSiteCode on the order line. Use the Create Order Operation of the OrderImportService web service. For example. <ns2:Order> . . . <ns2:TransactionType>Dropship Orders</ns2:TransactionType> . . . <ns2:Line> . . . <ns2:RequestedSupplierName>Green Bytes Inc.</ns2:RequestedSupplierName> <ns2:SupplierSiteCode>76846573869</ns2:SupplierSiteCode> . . .

Note.

• If you don't specify the supplier and supplier site in a sourcing rule, then you must include the Schedule Ship Date on the order line in the payload or FBDI template.

• To verify the values you must use for TransactionType or TransactionTypeCode, in the Navigator, click Setup and Maintenance, open the Manage Order Lookups task, then search for lookup type ORA_DOO_ORDER_TYPES. Use a value from the.

  • Meaning column for the TransactionType attribute.

  • Lookup Code column for the TransactionTypeCode attribute.

Integrate with Procurement

Send Shipping Instructions and Packing Instructions

If you use the predefined drop ship flow, then note these points.

• Order Management sends shipping instructions and packing instructions in one or more attachments on the fulfillment line because Procurement only accepts instructions in an attachment.

• Procurement only processes attachments that include an attachment category of MISC (Miscellaneous) on the fulfillment line. It ignores an attachment that contains any other value.

• An Order Entry Specialist can use the Create Order page in the Order Management work area to set the Category attribute in the Attachments dialog to any value that the drop down for the attribute displays when adding an attachment to an order line. However, Order Management sends a value of MISC to Procurement regardless of the value of Category.

• The user can enter text in the Shipping Instructions attribute and the Packing Instructions attribute in the Shipping Details area of the Create Order page. However, Order Management doesn't send this text to Procurement because Procurement only accepts them in an attachment.

• You must set the attachment category to MISC on the order line of each source order that you import.

For details about attachment categories and how to set them up, see the Overview of Integrating Attachments in Order Management topic.

Calculate Ship Dates

If a supplier sends updates to Procurement, then Procurement might send an update for the scheduled arrival date to Order Management. Order Management updates the scheduled arrival date but doesn't update the scheduled ship date on the fulfillment line.

Order Management updates the scheduled ship date, scheduled arrival date, and shipping method only if you set up Global Order Promising to calculate shipping, such as how to calculate transit time. If you don't set it up, the scheduled dates and shipping method might not contain a value.

This behavior affects fulfillment, including choices that your users make when they override the schedule. For details, see the Schedule Fulfillment Lines Manually topic.

Send Your Own Attribute

Use an extensible flexfield to send your own attribute to a descriptive flexfield on the purchase order in Procurement.

Here's an example payload that sends an extensible flexfield named ComplianceDetails to Procurement.

Note.

• Use web service Request Fulfill Order Orchestration Task Service to send your payload. For details, see the Overview of Using Extensible Flexfields in Order Management topic.

• Set up profile options in Procurement.

  • Copy the requisition for the purchase order to a descriptive flexfield.

  • Copy the requisition line for the purchase order to a descriptive flexfield.

  • Copy the order header for the purchase order to a descriptive flexfield.

  For details, see these topics.

  • Overview of Profile Options

  • Overview of Flexfields

Use Service Mappings

Use a service mapping to send data to Procurement, such as the supplier price or a note. For details, see the Use Service Mappings to Send Data to Procurement topic.

Manage Change

The aggregator aggregates change requests for each combination of sales order and its related purchase order. If the Order Entry Specialist modifies a fulfillment line during a drop ship, then the aggregator sends each combination as a single request to procurement. The aggregator sends these details when a time limit expires or when it aggregates a specific number of lines. For details, see these topics.

• Actions You Can Set When Routing Requests to Fulfillment Systems

• Aggregate Requests That Order Management Sends to Your Fulfillment System

If a sales order has a large number of order lines, then the aggregator only aggregates some of the changed lines according to a time limit. This behavior might cause the sales order to become stuck in Order Management because an error occurs during the change or the buyer in Procurement makes a change at the same time while the purchase order isn't on hold.

To avoid this problem in a drop ship flow, you can enable the Aggregate According to Number of Order Lines That Changed profile option, starting with Release 20C. If you enable the option, then the aggregator aggregates according to the number of order lines that have changed in the current revision of the sales order. For details, see the Use Order Profiles to Control the Order Management Work Area topic.

Predefined Processing Constraints

Order Management uses predefined constraints to prevent the Order Entry Specialist from changing the fulfillment line.

Constraint Display Name	Description
Update Fulfillment Line That Drop Ships Cancel Fulfillment Line That Drop Ships	Prevents the Order Entry Specialist from updating or canceling the fulfillment line when the purchase request in Procurement is at the Purchase Order stage. For example, if the user attempts to update, then a message displays. Order management can't update the fulfillment line because the purchase request in the procurement application is at the Purchase Order stage.
Cancel Fulfillment Line When Purchase Order Isn't Available	Prevents the he Order Entry Specialist from canceling a fulfillment line for the drop ship when the purchase order for the line is closed for receiving, is locked, or is on hold.
Update Purchase Request Validation	Makes sure. The ordered quantity on the fulfillment line is greater than zero. The Record Set contains the values that the Update Purchase Request fulfillment task requires. The requested arrival date or the scheduled arrival date on the fulfillment line contains a value.
Modify Extensible Flexfield when Line is in Requisition	Prevents the Order Entry Specialist from modifying an extensible flexfield on the fulfillment line when the line is at the requisition stage in the procurement application.

If you disable these constraints to meet your business requirements, then you must create your own constraints that prevent Order Management from accepting a sales order revision that Procurement rejects. For example, create a constraint that implements this logic.

• If the supplier can fulfill the change when it occurs two days or more before the ship date, then reject the change only if it occurs within two days before the ship date.

For details, see the Processing Constraints topic.

Modify Purchase Orders

Here's what you can and can't do.

Modification	Description
Ship a configured item, pick-to-order, or shipment set	If your sales order includes a configured item or a shipment set, and if your supplier already shipped some order lines but other lines are awaiting shipment, then you can cancel only the lines that the supplier hasn't shipped. Don't revise the purchase order in Procurement Cloud even if you intend to cancel the purchase order schedule. Don't change a configured item, pick-to-order item, or shipment set in Procurement Cloud. Don't use a shipment set to group sales order lines into a single purchase order. Procurement doesn't support shipment sets for this usage.
Modify purchase requisition	The buyer must not. Modify or split a requisition line. Modify a pick-to-order or assemble-to-order configured item. Modify a kit.
Assign supplier	Don't assign a new supplier on the requisition, then split the schedule on the draft purchase order.
Change on-hand flow to drop ship flow	If you scheduled a sales order line so your warehouse fulfills it, and you want to change the order to a drop ship. Go to the Order Management work area. Use the Edit Fulfillment Line action to remove the value from the Warehouse attribute. Add a value to the Supplier attribute and Supplier Site attribute. Enter a value in the Scheduled Arrival Date attribute. Removing a value from the warehouse and adding a value to the supplier and supplier site creates a drop ship flow. The flow needs the date so it can create the requisition.
Cancel order line	If the order line is in Requisition Created status, then you can cancel it in the Order Management work area, but you can't make any other changes. If Order Management sends a purchase request to Procurement Cloud, and if Procurement creates a purchase requisition for the request but hasn't created a purchase order for it, then you can only cancel the order line, and you can cancel the line only if it isn't part of a configured item or shipment set.
Remove a hold	If Order Management applies a hold on a sales order, then Procurement also applies a hold on the corresponding purchase order. However, a buyer can use the Purchase Orders work area to remove the hold.
Change other attributes	The buyer can change values in attributes that don't affect the drop ship flow.

Here's what you can and can't do regarding combining and splitting.

Modification	Description
Ship part of a fulfillment line or part of a sales order	If you drop ship. Part of an order line, then you can only cancel the quantity you haven't shipped. You can't cancel the quantity you already shipped. Part of a sales order, then you can cancel only the fulfillment lines you haven't shipped. And if you must cancel the shipment, then you must start the cancel from the upstream system, such as your order capture system or Order Management. Don't start the cancel from Procurement Cloud. Don't revise the purchase order in Procurement Cloud.
Split the schedule	The buyer can split the schedule, but don't split the schedule and also change the quantity or supplier at the same time.
Combine sales orders into one purchase order	If the flow creates one purchase order for requisition lines that reference more than one sales order, and if you revise these sales orders, then the flow places a hold on one of the sales orders and revises the purchase order. It doesn't revise the other sales orders and they fail. To fix this problem, go to the Order Management work area, delete the sales order revisions that failed, wait for Order Management to finish processing the sales order it placed on hold, then revise the other sales orders. You can only combine sales orders for the same customer or for the same supplier site. You can't consolidate sales orders across customers or across supplier sites.
Combine sales order lines into purchase orders	Manually combine sales order lines into one or more purchase orders. You can create one purchase order for each order line, resulting in several purchase orders for one sales order.

Here's what you can and can't do regarding quantity.

Modification	Description
Modify quantity	If you split the purchase order schedule across more than one delivery date, then make sure the total quantity across your split schedules equals the ordered quantity on the fulfillment line. If shipping has received the ASN, then you can't modify the quantity.
Set quantity for advance shipment notice	Make sure you use a single order line to specify the quantity for an Advance Shipment Notice. Don't split the quantity across more than one line.
Modify receipt quantity	The drop ship flow creates a receipt when it receives an invoice from accounts payable or an advance shipment notice. The flow then moves to the next orchestration process step in Order Management. Order Management won't display a subsequent change you make to the receipt quantity.

Other Setups

Here are some other set ups you can do.

• Create a separate requisition and purchase order for each order line.

• To improve performance, aggregate fulfillment lines before you send them to Procurement. For details, see the Actions You Can Set When Routing Requests to Fulfillment Systems topic.

Reports

Add drop ship details to a report.

1. In Oracle Transactional Business Intelligence, on the Catalog page, click New > Analysis.

2. In the Select Subject Area dialog, click Order Management - Fulfillment Lines Real Time.

3. On the Untitled page, in the Subject Areas tree, expand Drop Shipment Details.

4. Drag attributes from the Subject Areas tree and drop them onto the Selected Columns area.

For details, see the Create Your Own Report section in the Use Reports and Analytics with Order Management topic.

Reject an Over-Receipt

If the quantity on the advance shipment notice (ASN) exceeds the ordered quantity, then Oracle Fusion Receiving will reject the fulfillment request and display a message requesting the user to modify the quantity regardless of how you set the Over-Receipt Action attribute on the Manage Receiving Parameters page in the Setup and Maintenance work area. If receiving rejects the request, you must correct the quantity on the ASN or in receiving.

For details about this attribute, see the General Receiving Parameter Options topic.

• Processing Constraints

• Overview of Integrating Attachments in Order Management

• Schedule Fulfillment Lines Manually

• Overview of Using Extensible Flexfields in Order Management

• Overview of Profile Options

Set Up Drop Ship in Order Management

Set up Order Management so it supports your drop ship flow.

Summary of the Set Up

1. Set up Oracle Applications.

2. Enable features.

3. Manage items.

4. Manage sourcing rules.

5. Manage financial flows. For details, see the Set Up Financial Flows for Drop Ship topic.

6. Specify preparer for procurement.

7. Manage suppliers and supplier sites.

8. Manage agreements.

9. Manage orchestration processes.

10. Manage agreements, orchestration processes, and test.

Note.

• Each of these set ups are required except for Manage Agreements and Manage Orchestration Processes, which are optional.

• In this example, you enable the AS54888 Sentinel Desktop Computer for drop ship.

• This topic includes example values. You might use different values, depending on your business requirements.

Set Up Oracle Applications

Set up various Oracle applications so they support drop ship. For example, the Order Management offering references Global Order Promising to collect supply data from more than one source.

Here are the tasks you do to get started with setting up drop ship.

1. Define Blanket Agreement and ASL in Procurement. Sign in with a privilege that you can use to set up Procurement.

2. Create Drop-Ship Validation Org in Inventory Management. Sign in with a privilege that you can use to set up Inventory Management.

3. Do tasks in Global Order Promising.

   • Sign in with a privilege that you can use to set up Global Order Promising.

   • Manage Data Collections.

   • Define Item Processing Lead Times.

   • Manage Sourcing Rules and Manage ATP Rules. Set up sourcing rules and ATP rules so they support drop ship. For details, see the How Order Promising Rules Work Together topic.

4. Do tasks in the Manufacturing and Supply Chain Materials Management offering.

   • Manage Trade Operations

   • Define Shipping Network

   • Define Transit Lead Times

   • Manage Assignment Sets

   • Maintain Supply Network Model

For details, see the Implementing Common Features for Oracle SCM Cloud topic.

Enable Features

1. Implement the Order Management offering.

   For details, see the Implement chapter in the Implementing Order Management book.

2. Sign into Order Management with administrative privileges.

3. In the Navigator, click Setup and Maintenance.

4. In the Setup and Maintenance work area, go to the Order Management offering.

5. Click Actions > Change Feature Selection.

6. On the Edit Features page, in the Drop Ship row, add a check mark to Enable, then click Done.

   Enabling this feature lets you access various attributes and to do the setup tasks you need to implement drop ship, such as in Financial Orchestration.

7. Click Actions > Go to Offerings.

8. In the Setup and Maintenance work area, go to the Procurement offering.

9. Click Actions > Change Feature Selection.

10. On the Edit Features page, in the Customer Sales Order Fulfillment row, add a check mark to Enable, then click Done.

    This feature allows Oracle Procurement to accept purchase requests for sales orders that a drop ship supplier fulfills, and to display some of the attributes that you use to set up drop ship.

Manage Items

Set up items so they can participate in drop ship.

1. Sign in with a privilege that you can use to set up Product Information Management.

2. In the Navigator, click Product Information Management.

3. On the Overview page, click Tasks > Manage Items.

4. On the Manage Items page, search for the item you want to drop ship, such as Sentinel Desktop Computer.

5. In the search results, in the Item column for the item you must manage, click the link .

   For example, in the Sentinel Desktop Computer row, click AS54888.

6. On the Edit Item page, click Specifications, then click Purchasing.

7. In the Item Organization: Purchasing area, set the attribute.

   Attribute	Description
   Purchasable	Set to Yes. Allow this item to participate in a drop shipment.

8. If a blanket purchase agreement doesn't exist for the item, then, in the Pricing area, enter a number in the List Price attribute.

9. Click Save.

   Note.

   • You specify the item as purchasable in the organization that's responsible for purchasing the item.

   • The Product Information Management work area comes predefined to set the Purchasable attribute to Yes, so you modify it only if you previously set it No.

   • For details about how to make a large number of items purchasable, see the Implementing Product Management book.

Manage Sourcing Rules

Specify a sourcing rule that already includes details for the supplier and the supplier site. Global Order Promising evaluates the sourcing rule and considers the supplier calendar, supplier capacity, and supplier lead times when it promises the order.

1. Sign in with a privilege that you can use to access the Order Promising work area.

2. In the Navigator, click Order Promising.

3. On the Overview page, click Tasks > Manage Sourcing Rules.

4. On the Manage Sourcing Rules page, search for the sourcing rule you must modify, such as DOO-DS-Rule.

5. In the search results, click the sourcing rule, then click Actions > Edit.

6. On the Edit Sourcing Rule page, verify the value.

   Attribute	Description
   Organization Assignment Type	Make sure the type is Global. If it isn't Global, then you can't use this sourcing rule.

7. In the Effective Start Date area, to add a sourcing rule for your drop ship flow, click Actions > Add, then set values.

   Attribute	Description
   Organization	Leave empty. The Organization is typically the warehouse that stores inventory for a flow that doesn't include a drop ship.
   Type	Choose Buy From. Global Order Promising interprets Buy From to indicate that this value must come from a drop ship supplier.
   Supplier	Choose the supplier who will drop ship the item.
   Supplier Site	Choose the site that the supplier uses to store the drop ship item. The supplier ships the item from this site.

8. Click Save and Close.

9. Click View Assignment Sets.

10. In the Assignment Sets dialog, choose an assignment set, such as AYY-OP-ASET, then click Done.

11. On the Edit Assignment Set page, in the Sourcing Assignments area, click Actions > Add Row, then assign an item to the sourcing rule.

    Attribute	Description
    Assignment Level	Set to Item. This setting assigns the sourcing rule to the item.
    Item	Choose the item that the supplier you specified in step 6 supplies. For this example, choose AS54888.
    Sourcing Type	Set to Sourcing Rule. This value associates the sourcing rule with the assignment set so Order Management can use the rule to assign the item.
    Sourcing Rule or Bill of Distribution	Set to Drop Ship.

You can also specify other attributes for the supplier.

Attribute	Description
Supplier Calendar	Specify the working days for the supplier. Modify the calendar for each supplier site. The calendar you specify can be different from the calendar that the Supplier Site uses. Global Order Promising considers only working days when it calculates and incorporates lead times.
Supplier Capacity	Specify the supplier capacity according to item, supplier, and supplier site. Order Promising measures the supplier capacity that exists on the arrival date.
Supplier Lead Times	You specify and collect the lead times for item processing on the item master in Oracle Fusion Product Model. You can specify a lead time for each supplier in Global Order Promising.

Specify Preparer for Procurement

Specify an Order Management user who the buyer can contact to help resolve a problem that might occur with a fulfillment line that involves a drop ship supplier.

1. In the Setup and Maintenance work area, go to the task.

   • Offering: Order Management

   • Functional Area: Orders

   • Task: Manage Order Management Parameters

2. On the Manage Order Management Parameters page, click Preparer for Procurement.

3. In the Preparer for Procurement list, add a preparer, then click Save and Close.

   Order Management doesn't use the value for any other attribute as the preparer. For example, it doesn't use the Created By attribute on the order header or order line. It uses only the value you specify in Preparer for Procurement. For details about, see the Manage Order Management Parameters topic.

Manage Suppliers and Supplier Sites

Specify the client business unit that Procurement will use to requisition and process invoices for the supplier site. For details, see Supplier Sites and Supplier Site Assignments topic.

1. Sign in with a privilege that you can use to access the Suppliers work area.

2. In the Navigator, click Suppliers.

3. On the Overview page, click Tasks > Manage Suppliers.

4. On the Manage Suppliers page, search for the supplier you must manage, such as GVR_DS_SUPPLIER1.

5. In the search results, click the supplier you must manage, such as GVR_DS_SUPPLIER1.

6. On the Edit Supplier page, click Sites.

7. In the Site column, click a site, such as GVR_SUP1_SITE1.

   The supplier site you select must reference a procurement business unit. This business unit authorizes procurement services for the site.

8. On the Edit Site page, verify the value.

   Attribute	Value
   Purchasing	Contains a check mark.

   This option specifies that the supplier site fulfills a purchasing role for the client business unit.

9. Click Site Assignments, then set the value.

   Attribute	Value
   Client BU	Choose the client business unit that will requisition and process invoices for the supplier site.

   If necessary, click Actions > Create to add a client business unit.

10. Repeat step 9 for each requisition business unit that resides at the site that might request to purchase a drop ship item.

11. Click Save and Close.

12. Repeat steps 4 through 10 for each supplier that you must manage.

Manage Agreements, Orchestration Processes, and Test

Manage Agreements

Oracle Fusion Purchasing allows your buyer to create a blanket purchase agreement for items it will drop ship from the supplier. You must define an agreement for each supplier and supplier site, and associate one or more items with the agreement. You do this work when you set up purchasing.

This topic describes how to modify the setup so it supports drop ship. Purchasing uses the prices that the agreement specifies to set default values in the purchase documents. For details, see Blanket Purchase Agreement Lines topic.

You manage agreements differently for a drop ship that includes a configured item. For details, see the Set Up Drop Ship for Configured Items topic.

Manage agreements.

1. Sign in with a privilege that lets you access the Purchasing work area.

2. In the Navigator, click Purchasing.

3. Click Tasks > Manage Agreements.

4. On the Manage Agreements page, choose a value in the Procurement BU attribute, such as Vision Operations, then click Search.

5. In the search results, in a row that includes an agreement with a supplier who will drop ship your item, in the Agreement column, click the link.

6. On the Agreement page, click Actions > Edit.

7. On the Edit Document page, click Controls, then set values.

   Attribute	Description
   Automatically Generate Orders	Set to a value. Contains a check mark. Purchasing will automatically convert each requisition that it sources from the blanket purchase agreement. It will convert each requisition to a purchase order. Doesn't contain a check mark. Your buyer must do the conversion manually in the Purchasing work area. Purchasing examines eligibility according to the requisition to purchase order even if Automatically Generate Orders doesn't contain a check mark. For example, it makes sure each attribute is valid. Buyer Supplier Supplier site Source agreement Item is purchasable in the inventory organization of the procurement business unit
   Automatically Submit for Approval	Make sure this option contains a check mark. If it doesn't, then Order Management will create the order with an incomplete status, and the buyer must manually submit it for approval.
   Use Customer Sales Order	Set the value. Contains a check mark. Purchasing will group requisition lines that reference the same sales order number. It will group them on a single purchase order. Doesn't contain a check mark. Purchasing won't group.

8. Click Save > Save and Close.

9. Repeat steps 5 through 8 for each supplier who participates in your drop ship flow.

Manage Orchestration Processes

Order Management comes predefined with the DOO_OrderFulfillmentGenericProcess orchestration process.

It contains branches that run under conditions.

• If the shipment is a drop shipment, then run the Create Shipment Request branch.

• If you enable the item in the inventory organization for back-to-back shipping, then run the back-to-back branch.

• If the first two conditions are false, then run the Create Reservation branch.

Use this orchestration process as the default process assignment in your Assign and Launch rule. You can also create your own orchestration process that meets your business requirements. For details, see the Set Up Orchestration Processes topic.

Examine the predefined orchestration process.

1. Sign in with the Order Administrator privilege.

2. In the Setup and Maintenance work area, go to the task.

   • Offering: Order Management

   • Functional Area: Orders

   • Task: Manage Orchestration Process Definitions

3. On the Manage Orchestration Process Definitions page, search for DOO_OrderFulfillmentGenericProcess.

4. Examine the steps and branches.

5. If necessary, make a copy of this process, then modify it so it meets your business requirements, or create a new orchestration process and use DOO_OrderFulfillmentGenericProcess as a starting point.

Test Your Set Up

Create a sales order that uses drop ship.

• How Order Promising Rules Work Together

• Supplier Sites and Supplier Site Assignments

Set Up Financial Flows for Drop Ship

Set up your financial flow to create cost accounting distributions that track costs and ownership liability each time a transfer occurs between parties, including the supplier, one or more internal organizations, and the customer.

Financial Orchestration Cloud controls the change in ownership for each item that it processes during a drop ship flow. For example, to transfer ownership from the selling business unit to the requisition business unit. It also creates an intercompany invoice for each internal ownership transfer, when necessary.

You can specify more than one requisition business unit to manage and own more than one transaction that requests the item. You can also specify the selling business unit in the legal entity that sells the item.

Here's how it works.

1. Receive events. Financial Orchestration captures the physical supply chain event each time one occurs in the drop ship flow. For example, when the supplier sends the Advance Shipment Notice to indicate that they shipped the item.

2. Identify the financial flow to run. Financial Orchestration uses your set up details to identify the financial flow to use.

   • Purchase order for the drop ship

   • Sales order details that it gets from source documents

   • Selling business unit and buying business unit

   • Financial orchestration qualifiers

   • Priority of the financial orchestration flow

3. Run the financial flow.

The flows that Financial Orchestration runs depends on the number of business units that are involved.

Number of Business Units	Description
One	The selling business unit and the requisition business unit are the same unit, and Financial Orchestration uses only one financial flow for the drop ship.
More than one	Financial Orchestration might run through more than one business unit that involves procurement financial flows and shipment financial flows.

Set it Up

1. Sign in with Order Administrator privileges.

2. In the Navigator, click Setup and Maintenance.

3. In the Setup and Maintenance work area, go to the task.

   • Offering: Manufacturing and Supply Chain Materials Management

   • Functional Area: Supply Chain Financial Flows

   • Task: Manage Drop Ship Financial Flows

4. On the Manage Drop Ship Financial Flows page, in the search results, click Actions > Create.

5. On the Create Drop Ship Financial Flow page, set values.

   Attribute	Description
   Name	Drop Ship Flow for Vision Operations You can use any text.
   Priority	1

6. Set the attribute.

   Attribute	Description
   Supplier Ownership Change Event	Specify when to start the ownership change. ASN From Supplier. Change ownership when the supplier sends an advance shipment notice (ASN) to the financial flow for the drop ship order. AP Invoice Match. Change ownership when the supplier sends an invoice to the financial flow for the drop ship order. For details, see the Indicate an Ownership Change During Drop Ship topic.

7. In the Selling BU to Receiving BU Relationships area, click Actions > Add Row, then specify the relationship.

   For details, see the Specify Business Units for Drop Ship Flows topic.

8. Repeat these steps for each selling business unit that your enterprise contains.

9. Click Save and Close.

• Financial Orchestration Flows

Specify Business Units for Drop Ship Flows

Specify the relationship between the selling business unit, requisition business unit, supplier, and customer when you set up a financial flow that includes a drop ship.

Note.

• Red text indicates example values.

• Vision Operations is a legal entity. It contains a selling business unit that takes sales orders directly from your customer in its North American call center.

• Singapore Distribution Center.

  • Is the receiving trade organization. It receives the item from your supplier. The receiving trade organization also owns the requisition and receives the purchase order on behalf of the selling business unit.

  • Is the requisition business unit.

  • Supplies the item to customer Computer Service and Rentals, which is located in China.

• The supplier is a separate company and is also a legal entity.

The Create Drop Ship Financial Flow page sets the Receiving BU attribute and the Receiving Legal Entity attribute according to the value you set in the Receiving Trade Organization attribute.

Assume you set Receiving Trade Organization to Vision Operations, and you set up the application to create a requisition in the Vision Operations inventory organization for each sales order you drop ship that Vision Operations creates. Here are the attributes that will contain a value of Vision Operations.

• Selling BU

• Selling Legal Entity

• Receiving Trade Organization

• Receiving BU

• Receiving Legal Entity

• Requisition BU

Order Management Cloud gets the value for the Requisition Organization attribute and the Requisition BU attribute from the purchase requisition it creates for each drop ship order that involves a supplier, and that requires a requisition organization.

Specify the Receiving Trade Organization

Specify the Receiving Trade Organization attribute on the Create Drop Ship Financial Flow page. Choose the organization that does these tasks.

• Places the requisition for the goods

• Receives the purchase order for the drop ship

• Does the receipt accounting and shipment accounting for the drop ship

Set the Selling Business Unit and the Receiving Business Unit

Use Financial Orchestration to set up and run the financial flow according to the ownership transfer that occurs between the parties that are involved in the drop ship flow. Set up the relationship that exists between the selling business unit and the receiving business unit. Financial Orchestration uses this relationship when it creates a purchase requisition for the drop ship.

If you set the value for the Selling BU attribute to a value that's different from the value in the Receiving BU attribute, then Financial Orchestration determines whether it must do more financial and accounting transactions according to the procurement and shipping flows.

Set Up Different Requisition Trade Organizations

If you set the value in the Selling BU attribute to a value that's different from the value in the Receiving BU attribute, then a shipment financial flow must exist between the receiving business unit and the selling business unit. Financial Orchestration determines whether this flow exists when you create the relationship. If it doesn't, then Financial Orchestration displays an error message.

If a procurement financial flow exists in Financial Orchestration, and if Financial Orchestration can use it for the purchase order that the drop ship references, then Financial Orchestration uses the procurement financial flow when it orchestrates the drop ship.

For example, assume you must create a requisition that references the China inventory organization for each Metal item, and create a requisition that references the United States inventory organization for each Plastic item. Here's your set up.

Drop Ship Financial Flow	Inventory Organization	Financial Orchestration Qualifier
Flow 1	Resides in China as the receiving trade organization.	Use Metal as the item category.
Flow 2	Resides in the United States as the receiving trade organization.	Use Plastic as the item category.

Indicate an Ownership Change During Drop Ship

Specify when to change ownership during a drop ship flow.

• When Order Management receives the advanced shipment notice (ASN) from the supplier

• Or when Financial Orchestration receives the accounts payable invoice from the supplier

You use the Supplier Ownership Change Event attribute on the Manage Drop Ship Financial Flows page to specify when to change ownership.

ASN From Supplier

If the supplier sends an advanced shipment notice (ASN), then set Supplier Ownership Change Event to ASN From Supplier.

Here's the flow.

1. The supplier sends the ASN to Order Management.

2. Order Management copies the advanced shipment notice into receiving, which creates a type of drop ship flow known as receipt and delivery that records the event.

3. Order Management starts the downstream processes that cost and bill the shipment, including creating the drop ship receipt, starting the billing process, and starting the financial orchestration process for the drop ship order.

4. Receiving sends status and event details to Financial Orchestration and Order Management.

   • Financial Orchestration processes the trade transactions in costing, processes the receivable invoices between companies, processes payable invoices between companies, and so on.

   • Order Management sends status and event details to billing and order orchestration.

How to Communicate the ASN

The supplier can use actions on the supplier portal to create the advanced shipment notice.

• Create ASN

• Create ASBN

• Upload ASN

• Upload ASBN

If the supplier uses an informal communication, such as email, to report the shipment of a purchase order that references a drop shipment, then the warehouse manager can also use these features on the Receipts page in the Warehouse Operations work area to manually enter the advanced shipment notice. You can also upload an advanced shipment notice electronically through XML or EDI. For details, see these topics.

• Supplier Portal

• Overview of Creating ASNs and ASBNs

AP Invoice Match

What happens if the supplier doesn't send an advanced shipment notice, but instead sends an invoice?

1. The supplier sends an invoice to accounts payable in Financial Orchestration.

2. Financial Orchestration starts orchestration to receive costs and bill the shipment.

   The receiving process works the same way it does for ASN From Supplier, except the process doesn't create an advanced shipment notice.

3. Order Management receives and delivers the drop shipment when it creates the accounts payable invoice for the purchase order. Its the same purchase order that the drop ship references.

Scheduled processes automatically do the hard work for you.

Scheduled Process	Description
Transfer Invoice Details to Supply Chain Financial Flow Orchestration	Send details about validated invoices, canceled invoices, and corrected invoices to Financial Orchestration.
Transfer Ownership Change Events to Receiving	Send details about the AP invoice match from Financial Orchestration to the receiving process.

• Supplier Portal

• Overview of Creating ASNs and ASBNs

Set Up Drop Ship for Configured Items

Set up an agreement for the configuration model that specifies the configured item and the configure options that are part of the drop ship.

1. Sign in with a user role that you can use to edit values in the Procurement work area.

2. In the Navigator, click Purchasing.

3. Click Tasks > Manage Agreements.

4. Click Actions > Create.

5. In the Create Agreement dialog, set values, then click Create.

   Attribute	Value
   Style	Configure to Order Blanket Purchase Agreement You must use this value for an assemble-to-order configuration model. For details, see Supplier Agreement Creation: Points to Consider.
   Supplier	Select the supplier who will drop ship the configured item.

6. On the Edit Document page, in the Lines area, add at least one line, then click Submit.

Note.

• A hybrid configuration model is a type of configuration model that includes an assemble-to-order configuration model as the child and a purchase-to-order configuration model as the parent.

  Order Management Cloud uses one blanket purchase agreement to source the assemble-to-order options, and a different blanket purchase agreement to source the purchase-to-order options. So, Order Management issues separate purchase orders to the supplier.

• Use File-Based Data Import to import more than one agreement.

• How File-Based Data Import Works

Use a Service Mapping to Integrate Order Management with Procurement

Use a service mapping to send data from Order Management Cloud to Procurement Cloud.

Assume you need to send details about a sales order to Procurement so Procurement can process a purchase request.

• Indicate to Procurement that we negotiated the price when we created the sales order. We will use the NegotiatedByPreparerFlag attribute to send the indication as a Boolean value.

• Text note that we can send to the buyer. It includes details about the negotiated price, such as any discounts we provided, and why we provided them. We will use an extensible flexfield to capture these details.

• The price that we negotiated with the customer when we created the sales order. We will use the Price attribute to capture the negotiated price.

Summary of the Set Up

A. Add your entity to the integration service mapping.

B. Map your entity to the source.

C. Map entities to the service.

D. Modify the integration algorithm.

E. Test your set up.

A. Add Your Entity to the Integration Service Mapping

1. Sign in as the order administrator.

2. Create a sand box. For details, see the Create a Sandbox So You Can Edit Service Mappings topic.

3. In the Navigator, click Pricing Administration.

4. On the Overview page, click Tasks, and then, under Order Management Configuration, click Manage Service Mappings.

5. Open the FulfillmentIntegration service mapping for editing.

   For details, see the Integrate Order Management with Other Oracle Applications topic.

6. Add an entity. On the Entities tab, click Actions > Add Row, set values, then click Save.

   Attribute	Value
   Entity	FLinePackShip_EFF_Custom
   Description	Entity for an extensible flexfield that stores details on the fulfillment line. It describes the price we negotiated.

7. Add an attribute. In the Details area, click Actions > Add Row, then set values.

   Attribute	Value
   Attribute	FullfillLineId_Custom
   Type	Long
   Primary Key	Contains a check mark
   Alternate Key	Empty
   Allow Null	Contains a check mark

8. Add another attribute. In the Details area, click Actions > Add Row, set values, then click Save.

   Attribute	Value
   Attribute	ShippingCost_Custom
   Type	Double
   Primary Key	Empty
   Alternate Key	Empty
   Allow Null	Contains a check mark

9. On the Entities tab, in the Entity column, click PurchaseRequestLine.

10. In the Detail area, verify that the list contains the Price attribute.

    Attribute	Value
    Attribute	Price
    Type	Decimal
    Allow Null	Contains a check mark.

B. Map Your Entity to the Source

1. Click Sources.

2. In the Source column, click PurchaseRequestSource.

3. In the PurchaseRequestSource Details area, click View > Columns, then display columns.

   • Joined Entity

   • Joined Entity Attribute

4. Click Actions > Add Row, set values, then click Save.

   Attribute	Value
   Entity	FLinePackShip_EFF_Custom Its the entity you added earlier in this procedure.
   Type	View Object
   View Object	FulfillLineEffBPackShipInstructionprivateVO
   Query Type	Unique Identifier
   Query Attribute	FulfillLineId

5. Click Save, set values, then click Save again.

   Attribute	Value
   Joined Entity	FulfillLine
   Joined Entity Attribute	FulfillLineId

6. In the FLinePackShip_EFF_Custom Details area, add new attributes, then click Save.

   Attribute	View Object Attribute
   FulfillLineId_Custom	FulfillLineId
   ShippingCost_Custom	_ ShippingCost

7. Map attributes to the PurchaseRequestLine entity.

   • In the PurchaseRequestSource Details area, in the Entity column, click PurchaseRequestLine.

   • In the PurchaseRequestLine Details area, add attributes, then click Save.

     Attribute	View Object Attribute	Expression
     NegotiatedByPreparerFlag	Empty	True
     NoteToBuyer	Empty	Empty
     Price	Empty	Empty

C. Map Entities to the Service

1. Click Services.

2. Click Actions > Add Row, set values, then click Save.

   Attribute	Value
   Service	PriceRequestService_Custom
   Implementation Type	Algorithm
   Implementation	Dropship Price Mapping Custom

3. In the Details area, add entities, then click Save.

   • FLinePackShip_EFF_Custom

   • Header

   • FulfillLine

   • PurchaseRequestConfig

   • PurchaseRequestHeader

   • PurchaseRequestLine

   Note.

   • Click Actions > Add Row to add each entity.

   • Make sure the Read attribute and Write attribute contain a check mark for each entity.

   • Leave the other attributes empty.

4. Add attributes to the FLinePackShip_EFF_Custom entity.

   Attribute	Alias
   FulfillLineId_Custom	FulfillLineId
   ShippingCost_Custom	Leave Empty

5. Add attributes to the PurchaseRequestLine entity.

   • FulfillLineId

   • NegotiatedByPreparerFlag

   • NoteToBuyer

   • Price

   When you add attributes to these entities.

   • Make sure the Read attribute and Write attribute contain a check mark for each attribute.

   • Leave the other attributes empty.

D. Modify the Integration Algorithm

Modify the integration algorithm so it calls Procurement.

1. Click Tasks, and then, under Order Management Configuration, click Manage Algorithms.

2. On the Manage Algorithms page, in the Name column, click the row that contains the highest version of Dropship Price Mapping Custom.

3. Click Actions > Create Version.

4. In the Name column, click the row that contains the In Progress version of Dropship Price Mapping Custom.

5. On the Edit Algorithm page, click Step 1.

6. In the Step Details area, in the Default Action area, click Edit.

7. In the Edit Actions dialog, delete all the contents, then enter code.

   PRCLine.Price = PRCLineEff!= null? PRCLineEff.ShippingCost_Custom: null
   /*def LPurchaseRequestPrice = PRCLineEff!= null? PRCLineEff.ShippingCost_Custom: null
   if (LPurchaseRequestPrice != null) {
   PRCLine.Price = LPurchaseRequestPrice; 
   PRCLine.NegotiatedByPreparerFlag=true;
   } */
   

E. Test Your Set Up

Assume you're on a call with a preferred, long-term customer who orders a quantity of 10, A54888 desktop computers. To beat your competitor's price, you agree to provide a 20% discount on the order line. As part of the deal, you convince your customer to add 4 printers to the order.

1. Create a sales order in Order Management.

2. Add an order line, then set the attribute on it.

   Attribute	Value
   Your Price	Enter the negotiated price.

3. Submit the sales order.

4. Examine the details in Procurement.

• Integrate Order Management with Other Oracle Applications

• Create a Sandbox So You Can Edit Service Mappings

• Guidelines for Integrating Order Management with Other Oracle Applications

Various Setups

General

Opt Into Features in Order Management

Get details about features you can enable or disable according to your business requirements.

1. Go to the Setup and Maintenance work area, then go to the offering.

   • Offering: Order Management

2. Click Change Feature Opt In.

For more details about how to opt in to features, see the Configure Offerings topic.

Examine the features that you can use with Order Management.

Feature	Description	Detail
Maintain Common Reference Objects	Support common functionality, such as data security, reference data sets, and other preferences. Leave this feature enabled for most deployments.	Overview of Common Reference Objects topic
Governance, Risk, and Compliance	Manage governance, risk, and compliance across processes and systems.	Governance, Risk, and Compliance Management at http://www.oracle.com/us/solutions/corporate-governance/018760.htm
Local Installation of Help	Write your own help.	Define Help Configuration section in Implementing Common Features for SCM.
Transformation Rules	Transform source orders that you create in Order Management or that you import from a source system to optimize order fulfillment. For most implementations, leave this feature enabled.	Transformation Rules topic
Order Holds	Allow the Order Entry Specialist to place a hold on a sales order. For most implementations, leave this feature enabled.	Manage Hold Codes topic
Drop Ship	Leave this feature disabled unless you implement drop ship.	Implementing Drop Ship section in Implementing Order Management book
Enterprise Structures Guided Flow	Leave this feature disabled unless you implement enterprise structures.	Define Enterprise Structures chapter in Implementing Common Features for SCM
Application Toolkit Component Maintenance	Leave this feature disabled unless you use Application Toolkit to modify various components, such as application help, reports and analytics, the Watchlist, and so on.	Define Application Toolkit Configuration chapter in Implementing Common Features for SCM
Click to Dial	Use Click to Dial to place a call to a contact from a hyperlink on the phone number or phone icon.	Not applicable
Enterprise Scheduler Job Definitions and Job Sets	Leave disabled unless you run scheduled processes according to Oracle Enterprise Scheduler Services.	Define Custom Enterprise Scheduler Jobs chapter in Implementing Common Features for SCM
Enable Custom Payloads for Downstream Integration	Use view objects to integrate with systems that reside downstream of Order Management.	Integrate Order Management with Other Oracle Applications topic
Specify Business Unit for Selling Profit Center for Goods and Services Tax	Set the selling profit center on a sales order line that's different from the business unit on the order header.	Set Business Units for Selling Profit Centers topic
Enable Coverage and Subscription	Include coverage items and subscription items in sales orders.	Set Up Coverage for Sales Orders topic
Update Selected Lines in Sales Order	Allow the Order Entry Specialist to select one or more order lines in a sales order, specify the attributes and values to update, then update all selected lines. You must make sure the role that your users use, such as Order Entry Specialist, contains the privilege Update Selected Lines on Sales Orders.	Update More Than One Order Line topic
Return Items or Cancel Services Without a Reference Order	Allow the Order Entry Specialist to return an item without specifying the sales order that originally ordered the item.	Allow Users to Return Items Without Original Sales Orders topic

Enable or disable other features.

Feature	Description	Details
Pricing	Use the set up in the Pricing Administration work area to price items in Order Management. Leave this feature enabled unless you plan to use some other way to price your sales orders.	Administering Pricing book on Oracle Help Center
Order Management Business Intelligence Analytics	Enable analytic reporting in the Order Management work area. Leave this feature enabled.	Use Reports and Analytics with Order Management topic

• Plan Your Implementation

• Overview of Common Reference Objects

• Configure Offerings

Identify Hosts and Ports for Order Management

Identify the hosts and ports that Order Management Cloud uses to communicate data. You use these details during setup and maintenance.

1. In the Navigator, click Setup and Maintenance.

2. On the Setup page, click Tasks > Review Topology.

3. On the Review Topology page, click Detailed.

4. Get details for your service oriented architecture (SOA).

   • Expand SCMDomain.

   • In the SCM-SOA row, examine the values for External Server Host and External Server Port.

5. Get details for services you can use with Oracle Fusion Applications.

   • Expand FADomain, then examine values.

     Name	Values
     FSCMServices	Host and port for ADF services (Oracle Application Development Framework).
     FASOA	Host and port for SOA services.

   • In the SCM-SOA row, examine the values for External Server Host and External Server Port.

Manage Order Management Parameters

Set up order management parameters that affect behavior across Order Management Cloud.

1. In the Navigator, click Setup and Maintenance.

2. In the Setup and Maintenance work area, go to the task.

   • Offering: Order Management

   • Functional Area: Orders

   • Task: Manage Order Management Parameters

3. On the Manage Order Management Parameters page, set values.

Parameter	Description
Activate Credit Check on Order Submit	Specify whether to run credit check when the Order Entry Specialist submits the sales order. For details, see the Manage Credit Check in Order Management topic.
Allow Changes Through Configurator Validation	Allow the configurator to choose items in a configuration and to modify configuration options after the Order Entry Specialist adds a configured item to a sales order, and then save the sales order as a draft, but before the Order Entry Specialist submits the sales order. For example. The Order Entry Specialist adds a configured item to a sales order, then saves the sales order as a draft. A configuration manager modifies the configuration model and configuration rules for the configured item in such a way that it affects the configuration that the Order Entry Specialist added. The Order Entry Specialist returns to the draft several days later, then submits the sales order. In this example, if you set Allow Changes Through Configurator Validation to. Yes. The configurator uses the modified configuration model and configuration rules to update the configuration that the Order Entry Specialist specified. It allows the submit to proceed. It doesn't report these modifications to the Order Entry Specialist. This setting is useful when your business process doesn't require the Order Entry Specialist to understand and agree to modifications that the configurator makes. No. The configurator doesn't modify the configuration that the Order Entry Specialist specified. Instead, it doesn't allow the submit to proceed, and displays a validation error when the Order Entry Specialist attempts to submit or validate the sales order. This setting is useful when your business process requires that the Order Entry Specialist understand and agree to modifications that the configurator makes. Note. This parameter doesn't apply to a source order that includes a configured item. For details about importing source orders, see the Use Files to Import Orders into Order Management topic. This parameter affects all business units. For details about the configurator, see the Oracle SCM Cloud, Configurator Modeling book on My Oracle Support.
Automatically Set Values on Sales Agreement Attributes	Control default values that Order Management sets for sales agreement attributes when the user creates or updates the sales order. If you set this parameter to Yes. If only one sales agreement exists for the customer and business unit, then Order Management sets the agreement on the order header to this one sales agreement. If more than one agreement exists, then Order Management leaves the agreement on the order header empty. If the agreement on the order header is empty, and if only one sales agreement exists for the item on the order line, then Order Management sets order line attributes Sales Agreement, Sales Agreement Line, and Sales Agreement to the order line agreement. Otherwise, it leaves these order line attributes empty. If you set this parameter to No, then Order Management doesn't set any default values. It leaves them all empty. Order Management constrains the customer, business unit, and currency on the order header. It also constrains the item on the order line.
Business Unit for Selling Profit Center	See the Set Business Units for Selling Profit Centers topic.
Check for Trade Compliance When User Submits Sales Order	Set a value. Yes. Order Management will verify each sales order that the Order Entry Specialist submits in Order Management or that you import from a source system. No. Order Management won't verify any sales orders. For details, see the Manage Trade Compliance topic.
Compare Change Order to Fulfillment Values	See the section at the end of this topic.
Configuration Effective Date	Specify the date that Order Management uses to determine the configure options to display for a configured item. The configure options might vary depending on the ones that exist in the configuration model on a given date. Set a value. Ordered Date. Use the options that exist according to the Ordered Date attribute that displays on the Create Order page. Configuration Date. Use the options that exist when you create the model. Current Date. Use the options that exist as of today. Requested Date. Use the options that exist according to the requested date. If you don't set a value, then Order Management uses Current Date.
Configuration Effective Date for Exploding Included Items	Use this parameter with or without setting Configuration Effective Date. For details, see the Control Explosion Dates for Configuration Models topic.
Coverage Start Date	Choose a value. Shipment Date. Set the start date of the coverage to the date that Order Management ships the covered item. Delivery Date. Set the start date of the coverage to the date that Transportation Management sends to Order Management when Transportation Management delivers the covered item. For details, see the Set Up Coverage for Sales Orders topic.
Credit Check Failure at Order Submit	Specify how to proceed if credit check fails. Save Order in Draft Status. Save the sales order in Draft status and don't proceed to fulfillment. Submit the Order with Hold on Lines That Failed Credit Check. Save the sales order in Submitted status, place a hold on each order line that fails credit check, then proceed with fulfillment for order lines that aren't on hold. For details, see the Manage Credit Check in Order Management topic.
Customer Relationship Type	Specify values that the Order Entry Specialist can set for the Ship-to Customer attribute and the Bill-to Customer attribute. Set a value. Single Customer. Allow the Order Entry Specialist to select only the bill-to customer and ship-to customer that's the same as the sold-to customer. For example, if the Order Entry Specialist creates a sales order for Company x, then Order Management sets Ship-to Customer and Bill-to Customer to Company x. The Order Entry Specialist can't modify these values. All Customers. Allow the Order Entry Specialist to select any bill-to customer or ship-to address, regardless of sold-to customer. For example, if the Order Entry Specialist creates a sales order for Company x, then Order Management sets Bill-to Customer and Ship-to Customer to Company x, by default, and allows the Order Entry Specialist to search and select any bill-to customer, or any ship-to customer and address.
Enable Orchestration Process Planning and Calculate Jeopardy	Specify whether to do orchestration process planning and to calculate jeopardy on each sales order during order processing. For details, see the Orchestration Processes topic.
Filter Ship-To Addresses	Filter addresses that the Order Entry Specialist can choose when setting the Ship-to Address attribute on the order header. Set a value. Yes. Display only ship-to addresses. No. Display all addresses. Order Management comes predefined to use No, by default. Examine the behavior when Filter Ship-To Addresses is No. Create a sales order in the Order Management work area. On the order header, click Ship-To Address, then click Search. In the Search and Select dialog, don't set any values, then click Search. Notice that the search returns addresses that include Ship-to and Bill-to values in the Usage attribute. Note. In some situations, you might need to prevent the Order Entry Specialist from using a Ship-to Address when Usage for the address is Bill-to. For example, if you use Oracle Fusion Receivables, then you must set Filter Ship-To Addresses to Yes because Receivables comes predefined to ship only to a ship-to address. In another example, it might not be appropriate for a bill-to location in your deployment, such as an accounting center, to receive shipment. If you import a source order, and if the Filter Ship-To Addresses parameter is Yes, and if the value of the Site Usage attribute for the ship-to address in Trading Community Architecture isn't Ship-to, then the import will fail. To specify the value that the Usage attribute displays, navigate to Trading Community Architecture, then set the Site Usage attribute to one of these values. Ship-to Bill-to Ship-to and Bill-to For details, see the Oracle Trading Community Architecture book.
From Address for Email Messages	Specify the From email address that the Universal Messaging Service uses when it sends an email from the order document or from an automatic notification. The From address comes predefined as [e-mail]. You can modify this value to use an address in the domain that your company uses. You must use a valid email address format. For example, [e-mail]. For details, see the Email Formats in Order Management topic.
Halt Configurator Validation on First Error	Set a value. True. Stop processing on the first error that the configurator encounters during order entry. False. Don't stop processing if the configurator encounters an error during order entry. Instead, allow the configurator to continue to run until it finishes processing. This setting allows the configurator to identify and report all errors that the configuration contains. Halt Configurator Validation on First Error affects only order entry. It doesn't affect order import.
Item Validation Organization	Specify the item validation organization that Order Management uses to validate and display items for each sales order the Order Entry Specialist creates, according to business unit. Order Management will display only the items that it associates with the item validation organization you specify. For example, assume you create a record in the Item Validation Organization list, you set the Business Unit attribute for this record to Vision Operations, and the Organization attribute to Denver Manufacturing. Order Management will display only the items that it associates with Denver Manufacturing when the Order Entry Specialist creates a sales order for Vision Operations. It displays these items when the Order Entry Specialist searches for items on the Order Lines tab of the Create Order page. You must specify an item validation organization for each business unit. If you don't, then Order Management disables search for the item in each sales order that references a business unit that you don't specify. As an alternative, if you use the same master organization for every business unit, then you can specify this organization in the Item Validation Organization parameter, then set the Business Unit attribute for this parameter to All Business Units. You can set Item Validation Organization only for business units that Order Management associates with your sign in responsibility. If it associates your sign in responsibility with only one business unit, then it uses this business unit as the item validation organization. The Product Information Management work area associates inventory organizations with business units. If you don't set Item Validation Organization, and if Product Information Management associates more than one inventory organization with the same business unit, then Order Management does one of these actions. If Product Information Management associates the same item master organization with these inventory organizations, then Order Management sets Item Validation Organization to this item master organization, then informs the Order Entry Specialist of this setting. The Order Entry Specialist can accept this value and continue entering the sales order, or reject it and contact the order administrator with a request to use Item Validation Organization to set up the inventory organization. If Product Information Management associates different item master organizations with these inventory organizations, then Order Management informs the Order Entry Specialist that the order administrator must first set up the inventory organization before the Order Entry Specialist can enter the sales order. Order Management displays only inventory organizations in the Organization attribute that Product Information Management associates with the business unit you choose in the Business Unit attribute. You can use Product Information Management to set up an inventory organization and create these associations. For details, see topic Inventory Organizations: Explained.
Notify Frequency	Specify an integer that represents the number of hours to wait before consolidating, and then sending a notification. Notify Frequency comes predefined with a value of 1. You can set it to any value that's greater than or equal to 0 (zero). If you set it to 0, then Order Management won't consolidate notifications, and will send each notification when the event that it references occurs. For details, see the Send Notifications from Order Management to External Systems topic.
Number of Processes for Order Import	Set the maximum number of scheduled processes that can run concurrently for one set of source orders. Adjust this value as necessary depending on how it impacts performance. For details, see the Import Orders into Order Management topic.
Number of Times to Retry Pause	Specify the number of times to retry a pause task that pauses until time elapses. Adjust this value according to performance. For details, see the Pause Orchestration Processes Until Time Elapses topic.
Preparer for Procurement	Specify an Order Management user who the buyer can contact to help resolve a problem that occurs with a fulfillment line that involves a drop ship supplier. The buyer is a procurement application user. Order Management sends these details to purchasing. If you don't specify Preparer for Procurement, and if an error occurs, then the procurement system will reply with an error that the preparer is missing. You must specify at least one value so Order Management can successfully send a purchase request to Oracle Procurement Cloud. The default value applies across all business units. You can specify a separate preparer for each selling business unit. You can specify a preparer as the default value for all business units. Order Management will use this default value only for business units where you don't specify a preparer. Order Management doesn't use the value for any other attribute as the preparer. For example, it doesn't use the Created By attribute. It uses only the value you specify in Preparer for Procurement. For details, see the Set Up Drop Ship in Order Management topic.
Send Discount Details to Billing Systems	Specify whether to send the list price and discounts, or only the net price, to your downstream billing system.
Start Approval Process for Sales Orders	Specify whether to get sales order approval. If you must enable approval, then you must set this parameter to Yes even if you must enable approval only for Order Management. If you set this parameter to No, then Order Management won't route sales orders for approval even if you define and activate an approval rule. If you set this parameter to Yes but you don't define and activate an approval rule, then Order Management won't route the sales order for approval, but will instead send it to order fulfillment. For details about this parameter, see the How Managing Approval Rules for Sales Orders Works topic.
Use Configurator for Order Import Validation	Set a value. True. The configurator will validate each source order that includes a configured item during order import. False. The configurator won't validate.

Compare Change Order to Fulfillment Values

Set a value.

• Yes. Allow a web service or file-based data import to change fulfillment line values even after the Order Entry Specialist revises the sales order in the Order Management work area.

• No. Don't allow.

If you set it to Yes.

• Order Management compares attribute values in the revision to attribute values in the import data to determine whether the user revised the order.

• If the user revised the order, then Order Management will replace the user's revisions with values from the imported data.

• Make sure your import data includes values for attributes the user didn't revise. You must get these values from the orchestration process that's currently processing the order.

  Use the getOrderDetails operation of web service Order Information Service or use Oracle Transactional Business Intelligence (OTBI) to get attribute values from the sales order that Order Management is currently processing. Create a new payload for the order revision, change attribute values in the payload to reflect the revision, then send the payload to Order Management.

Set the value for this parameter only one time. For example, if you set it to Yes during set up, then don't set it to No after you deploy your set up.

Example

Assume you set this parameter to Yes.

Step 1. Your user creates a sales order, doesn't set a value for the Warehouse attribute, submits the order, and Order Promising schedules it.

Order Number	Order Line	Quantity	Warehouse
37564	1	10	Not applicable

Step 2. Your user creates an order revision, sets the Warehouse to M1, then submits the order.

Order Number	Order Line	Quantity	Warehouse
37564	1	10	M1

Step 3. Here's the original payload.

Order Number	Order Line	Quantity	Warehouse
37564	1	10	Not applicable

Here's how Order Management processes the change.

• Compares the payload in step 3 to the payload in step 2 to identify attributes that changed.

• The warehouse in step 2 is M1 buts its empty in step 3, so Order Management detects a change on the order line.

• Order Management updates your fulfillment system to process the change.

Note.

• If the line already shipped, then Order Management rejects the change.

• If your user makes another revision before step 3, then you can use a web service or order import to process it.

• What You Can Do in Product Master Data Management

• Inventory Organizations

• Administer Email Format in Order Management

• Overview of Sending Notifications from Order Management to Other Systems

• Overview of Setting Up Trade Compliance

Time Zone Differences in Order Management

Global Order Promising uses the time zone where the inventory organization resides when it calculates promising for the supply that Order Management requires to fulfill each sales order, then sends the scheduled ship date and scheduled arrival date to Order Management.

Global Order Promising uses date attributes from Order Management to optimize supply. For example.

• Requested ship date or requested arrival date

• Earliest acceptable ship date or earliest acceptable arrival date

• Latest acceptable ship date or latest acceptable arrival date

Using the time zone where the inventory organization resides provides more accurate values in date fields, and helps to avoid undesirable time shifts between demand and supply. For example, to prevent the scheduled ship date from occurring before the requested date or the ordered date.

Note.

• Order Management applies this behavior for sales orders that the Order Entry Specialist creates in work area Order Management and for source orders that you import order from a source system.

• This behavior doesn't apply for drop ship.

Example of Calculating Time Zone Differences

Here's the scenario.

• The Order Entry Specialist is located in Denver, Colorado, USA, in Mountain Standard Time (MST), which is UTC (Coordinated Universal Time) minus 7.

• The inventory organization also uses UTC minus 7.

• The scheduling calendar that the warehouse uses is open Monday through Friday, so Global Order Promising can set the Scheduled Ship Date attribute for the shipment on any weekday, but not on the weekend.

• The on-hand supply is always available.

For example.

1. The Order Entry Specialist sets the requested date on the sales order to 3/2/18 5:00 PM, which is a Friday, then submits the sales order.

2. Order Management interacts with Global Order Promising in UTC, so it sends 3/3/18 00:00AM (UTC) as the requested date.

3. Global Order Promising converts the requested date to the time zone where the inventory organization resides, which is 2/3/18, Friday, 05:00 PM (UTC minus 7).

4. Global Order Promising schedules the shipment at the inventory organization to the end of the day, which is 2/3/18, 11:59 PM local time (UTC minus 7), because this day is a working day.

5. Global Order Promising sends schedule details to Order Management as Saturday, 3/3/18, 6:59 AM (UTC).

   06:59 is a seven hour offset from UTC. The calculation is Friday, 11:59 PM local time (UTC minus 7) plus seven hours equals Saturday, 3/3/18 06:59 AM (UTC).

6. The Order Management work area now displays the scheduled ship date in UPTZ, which is UTC minus 7.

   The scheduled ship date in UTC was 3/3/18 minus 06:59AM (UTC). The time and date in UPTZ is 2/3/18 minus 11:59 PM (UTC-7).

   Global Order Promising uses UTC. Order Management displays dates in UPTZ (User Preference Time Zone) so they're meaningful to the person who uses the Order Management work area.

Handling Time Zone Differences During Order Import

Use the DooDecompReceiveOrderComposite web service to import a source order from your source system. Use various date attributes in the web service payload, such as requested ship date, requested arrival date, expected arrival date, and so on.

Here's the format for each date attribute.

yyyy-mm-ddTHH:mi:ssZ

Requirements for how you format dates are different depending on how you import your source order.

How You Import	Description
You use web service ReceiveOrder. For details, see the Overview of Using Web Services with Order Management topic.	Dates in your import payload can use UTC with or without a negative or positive offset.
You use the order import template. For details, see the Use Files to Import Orders into Order Management topic. You use the business-to-business flow. For details, see the Overview of Business-to-Business in Order Management topic.	Dates in your import payload must use UTC.

Here's an example payload of the ReceiveOrder web service. It includes a UTC offset for the Earliest Acceptable Ship Date attribute. This value indicates that the end of day is April 3, 2018, and the time is 1:10:10 AM in the time zone that's 8 hours behind UTC.

You must use this date format.

yyyy-mm-ddThh:mi:ssz

where

This Variable	Specifies This Value
yyyy	Calendar year.
mm	Month of the calendar year.
dd	Numeric day of the month.
T	Time designator.
hh	Number of hours after midnight, in the 24 hour format.
mi	Minutes after the beginning of the hour.
ss	Seconds after the beginning of the minute.
z	Time zone indicator with or without a UTC offset. For example, 0-8.00 is eight hours behind UTC.

Consider an example.

2018-04-03T01:10:10.0-08:00

where

Value	Variable
2018	Calendar year.
04	Month of the calendar year, which is April.
03	Numeric day of the month, which is April 3rd.
t	Time designator.
01	One hour after midnight.
10	Ten minutes after the beginning of the hour.
10	Ten seconds after the beginning of the minute.
0-08:00	where 0. Specifies 0 UTC. -. Delimiter between 0 UTC and the UTC offset. 08:00. Specifies 8 hours after 0 UTC.

Guidelines for Setting Up Units of Measure

Use guidelines to help you set up the units of measure that you use in Order Management.

• Set the Primary Unit of Measure attribute and Secondary Unit of Measure attribute when you create the item in the Product Information Management work area. Order Management uses the values you specify to set default values for each attribute during order capture.

• Make sure the unit of measure is appropriate for the item. For example, Quart is appropriate for a liquid, but Amperage isn't because amperage measures electrical current.

Import

If you import a source order through FBDI or a web service.

• Collect units of measure from your order capture system so Order Management can validate the units of measure it receives later when you import source orders from your capture system. For details, see the Collect Data subtopic in the Quick Start for Setting Up Order-to-Cash topic.

• Use the Ordered UOM attribute to specify the unit of measure. Use the OrderedUOMCode attribute to specify the abbreviation for the measure. For example, Ea is an abbreviation for Each.

• The import uses the value you import instead of the value you specify in Product Information Management.

• If you use the Pricing Administration work area to set up pricing for your item, then the import validates the unit of measure according to how you set up the price list. For example, if you set the Pricing UOM attribute for the item on the price list to Ea, and if your import doesn't use Ea for the unit of measure, then the import fails and displays an error message.

• If you encounter an error during order import, like Cross-Referenced Value Not Found for UOM_CODE, see the Cross-Reference Error subtopic in the Troubleshoot Problems With Order Import topic.

Fulfill

• If you don't encounter an error during import but the order gets stuck during fulfillment, then create a conversion rule.

• If your shipping system uses a unit of measure to represent shipping that's different from the unit of measure that Order Management uses in the sales order, then the shipment service converts the unit of measure back to the unit of measure that the sales order uses, then communicates the shipped quantity to Order Management. For details, see the Task Services topic.

• If you use the Create Inventory Reservations fulfillment task to reserve supply, then you must provide the item, quantity, unit of measure, and warehouse. For details, see the Guidelines for Reserving Inventory topic.

• If you use an Oracle Fusion inventory system, then create a conversion rule that converts the UOM from the sales order into a UOM that the inventory system can understand. If you use your own fulfillment system, then make sure it accepts the UOM that the sales order specifies.

• Troubleshoot Problems With Order Import

• Task Services

• Guidelines for Reserving Inventory

• How Units of Measure, Unit of Measure Classes, and Base Units of Measure Relate to Each Other

Display Data from Different Offerings

Display data from different offerings on the Overview page in the Order Management work area.

The Overview page displays data in infolets. An infolet is a graphic representation of data, such as a bar chart or pie chart. It displays order status, such as the number of orders on backorder, orders past due, orders on hold, orders in jeopardy, and so on.

The Overview page comes predefined to only display data from the Order Management offering. However, you can set it up so it displays data from other offerings.

1. In the Setup and Maintenance work area, go to the Order Management offering.

2. Click Actions > Edit Implementation Status, set status to Implemented, then click Done.

3. Repeat steps 1 and 2 for each offering that must display data in infolets.

   For example.

   • Order Promising is part of Supply Chain Planning. To display promising data, in step 1, go to Supply Chain Planning.

   • Shipping is part of Manufacturing and Supply Chain Materials Management. To display ship data, in step 1, go to Manufacturing and Supply Chain Materials Management.

Your users must sign in with the FOM_VIEW_ORDER_TO_CASH_INFOLET_PAGE privilege to view infolets.

Here are more privileges you need to view infolets from each offering.

Infolet	Offering	Privilege
Order Exceptions Orders in Process Order Billing Status	Order Management	FOM_VIEW_ORDERS_PRIV
Scheduling Performance	Supply Chain Planning	MSP_VIEW_PLANNING_SUPPLY_AVAILABILITY_PRIV
Inventory Valuation	Manufacturing and Supply Chain Materials Management	CST_RUN_INVENTORY_VALUATION_REPORT_PRIV
Open Shipments Open Shipments by Priority Shipment Exceptions	Manufacturing and Supply Chain Materials Management	WSH_MANAGE_DELIVERY_PRIV

Collect Data

Collect Planning Data for Order Management

Collect planning data at various points of your set up process, and also after you finish set up.

Global Order Promising promises orders that it receives from Order Management Cloud. It uses data from your supply chain network and supplies that you collect. You set up rules in Promising that specify how to plan and promise.

You collect data into the Global Order Promising repository. The repository also stores setups that you make in the Global Order Promising work area, such as rules for sourcing, available-to-promise, and supply allocation. Promising and sourcing work together to determine what to deliver to your customer within the time frame that the sales order requests.

Collect Setup Data

You collect organizations, items, structures, routings, suppliers, transit times, and so on. For example, collect the catalog you assign on you item in the Product Information Management work area so you can use it in an available-to-promise rule in Global Order Promising.

1. Do your setups in various work areas.

   For example, use the Setup and Maintenance work area.

   • Use the Create Workday Pattern task and the Create Work Schedule task to set up calendar data.

   • Use the Manage Units of Measure task to set up units of measure.

   Use the Product Information Management work area.

   • Use the Manage Items task and Create Item Structure task to set up your item, such as the AS54888.

   • Use the Manage Catalogs task to set up catalogs.

   Use the Manage Work Definitions task in the Work Definition work area to set up work definitions.

2. Use the Collect Planning Data task in the Plan Inputs work area to collect the set ups you made in step 1.

   The Collect Planning Data task makes the objects you set up available to other Oracle Fusion work areas and applications.

3. Use Oracle Fusion work areas and applications to continue your set up.

   For example, use the Create Assignment Set task in the Global Order Promising work area to specify the AS54888 item that you set up in the Product Information Management work area.

You collect setup data so you can choose the data you need during set up. Assume you create a new item, the AS54888, and you must add the AS54888 to the Item attribute in your Sourcing Rule, but how do you get the AS54888 to show up in the pick list you use when you set the Item attribute? You must collect it first.

You must collect data several times during setup. Collect each time you.

• Create or modify an item in the Product Information Management work area.

• Modify the item, item structure, catalog, or work definition.

For more details, see the Complete List of Data You Can Collect section at the end of this topic.

For more background details, see the Overview of Data Collections for Supply Chain Planning topic.

Try it.

1. Go to the Plan Inputs work area.

   Don't use the Plan Inputs task that's available in the Setup and Maintenance work area. Use the Plan Inputs work area instead.

2. In the Plan Inputs work area, click Tasks > Collect Planning Data.

3. In the Collect Planning Data dialog, set the value.

   Templates are available, such as Static Data for Supply Planning. For this set up, do the steps instead so you can more clearly visualize the flow.

   Attribute	Value
   Source System	Choose the source system that your implementation uses for planning, such as OPS (Oracle Fusion Order Orchestration and Planning). Identify the source system that your implementation uses. Go to the Manage Upstream and Fulfillment Source Systems task in the Setup and Maintenance work area. On the Manage Upstream and Fulfillment Source Systems page, in the Destination System area, notice that you can use a destination system where the Enable for Oracle Fusion Distributed Order Orchestration option contains a check mark. In the Source Systems area, notice that the Collect Planning Data dialog gets values for the Source System attribute from source systems where the Order Orchestration attribute contains Order Orchestration.
   Collection Type	Set a value. Targeted. Delete all data in the repository for the entities that you select, collect new data for these entities, then save it in the repository. Net Change. Collect data in increments, and collect only changed or new data. This choice is faster than using Targeted. Use Net Change when you already performed a targeted collection and now must keep your planning data current with data in your run time environment. Automatic Selection. Let the server decide.

4. On the Reference Data tab, move entities from the Supply Entities list to the Selected Entities list.

   Choose the entities you need. You typically choose these entities for an Order Management implementation. For the complete list, see the section at the end of this topic.

   • Calendars

   • Currencies

   • Items

   • Item Structures

   • Order Orchestration Reference Objects

   • Organizations

   • Sub Inventories

   • Units Of Measure

5. Click Submit.

   The Plan Inputs work area automatically starts a scheduled process named Collection Job Set.

6. In the Status dialog, note the process number. For this example, assume its 50465.

7. Go to the Scheduled Processes work area.

8. On the Overview page, locate 50465 in the Process ID column. Monitor the process until the Status column displays Succeeded.

Collect Data From Source Systems

Order Management uses units of measure, currency, and currency conversions from the Order Orchestration and Planning Data repository. You must collect data for these entities so your set up can receive source orders. Sourcing rules in Global Order Promising reference the Organization Parameter entity. You must collect organization parameters before you set up your sourcing rules.

1. Collect data from your source system.

   • In the Setup and Maintenance work area, go to the task.

     • Offering: Supply Chain Planning

     • Functional Area: Supply Chain Planning Configuration

     • Task: Manage Planning Source Systems

   • On the Manage Planning Source Systems page, in the Source Systems list, locate your Oracle system, then set values.

     Attribute	Value
     Version	Fusion
     Collections Allowed	Contains a check mark
     Order Orchestration Type	Order Orchestration
     Enable Data Cross-Reference	Contains a check mark

   • Set values for each system that your set up must integrate, such as an order capture system or fulfillment system.

     Attribute	Value
     Version	Others
     Collections Allowed	Contains a check mark
     Enable Data Cross-Reference	Contains a check mark

   For details, see the Manage Planning Source Systems for Data Collections topic.

2. Cross-reference data for your currencies and units of measure. Use the Manage Planning Source Systems page.

   For details, see the How You Collect Different Data Types for Supply Chain Planning topic.

3. Collect organization parameters from your source system.

   To identify your organization, the collected data concatenates the source system to the organization ID. Other entities, such as Sourcing Rules, also use this identification.

4. Collect units of measure, currencies, and currency conversions from your order capture system.

   • Order Management validates the units measures and currencies against data that it already collected from your order capture system when it receives source orders from this system.

   • You must collect calendars from your fulfillment system so Order Management can use them during scheduling. A calendar specifies when a facility, such as a warehouse, is open or closed.

   • To collect data, you load it into staging tables, then use the Perform Data Load from Staging Tables scheduled process.

   • Use the review pages to verify the data you collect.

   • A pilot set up expects your test orders to use the same values for the unit of measure, currency, and currency conversion you collect into the data repository.

     During a full set up, if more than one order capture system uses different values for these entities, then you must do more set up. For example, if one order capture system uses Ea for each item, and if another order capture system uses Each for each item, then you must set up cross-references for these order capture systems.

   • Your set up can collect reference data from more than one system. However, a reference data entity is a global object, so Order Management and Global Order Promising use the most recent data that your set up collects.

     So, identify the source system that contains the master data list, then collect data from the source system after you collect data from all other source systems. For example, if source system x contains the master list of currencies, then collect currencies from source system y so Order Management can cross-reference currencies to system y, then collect currencies from system x.

   • If Order Promising must consider the transit time that occurs during shipping between the warehouse and a destination, then you must collect shipping methods. If you don't, then Order Management uses a transit time of zero days.

Collect Runtime Data

Collect dynamic data at run time, such as on-hand supply and purchase orders.

Global Order Promising makes availability-to-promise and sourcing decisions when your user creates a sales order at run time. It allows the user to explore different scenarios to increase margin, improve delivery, and so on. Promising needs the most up-to-date supply and demand data to make these decisions.

Its important to periodically collect data for each new item your users add when they create a sales order because collection gets the on-hand quantity for return orders and canceled order. The quantity affects planning.

Try it.

1. Click Supply Planning Data, then move entities from the Supply Entities list to the Selected Entities list.

   Attribute	Value
   On Hand	Promising uses this entity to get the inventory that's in stock for the item.
   Purchase Orders and Requisitions Transfer Orders Work Order Supplies	Add these entities so Global Order Promising can get availability across the entire supply chain.

2. Click Submit.

3. Refresh the server.

Refresh the Server

You must refresh the server each time you collect data. You must also refresh each time you create or update a promising rule or sourcing rule.

1. Go to the Scheduled Processes work area, then click Action > Schedule New Process.

2. In the Schedule New Process dialog, set the value.

   Attribute	Value
   Name	Refresh and Start the Order Promising Server

3. Add a check mark to the parameters you must update, then click Submit.

   Here are the parameters you refresh for most set ups.

   • On Hand. You need the on-hand inventory to replenish each item in an inventory transaction or to process a return order.

   • ATP Rules.

   • Sourcing.

   • Items.

   • Organizations. Include only when you create a new inventory organization.

   • Resources. Include only when you create a new resource.

4. Click Actions > Refresh, then verify the status is Succeeded. Repeat, as necessary.

Complete List of Data You Can Collect

Here are the entities you can collect when you do the Collect Planning Data task. If you do a set up in the work area described in the Source column, then you must collect the entity listed in the Entity column.

Source	Entity
Manage Suppliers task in the Suppliers work area.	Approved Supplier List
Create Workday Pattern task and Create Work Schedule task in the Setup and Maintenance work area.	Calendars
Manage Catalogs task in the Product Information Management work area.	Catalogs
Manage Currencies task in the Setup and Maintenance work area.	Currencies
Manage Customers task in the Setup and Maintenance work area.	Customer
-	Demand Class
Manage Geographies task in the Setup and Maintenance work area.	Geographies
Manage Items task in the Product Information Management work area.	Items
Create Item Structure task in the Product Information Management work area.	Item Structures
Manage Subinventories task in the Product Information Management work area.	Item Subinventories
Manage Item Relationships task in the Product Information Management work area.	Item Substitution Relationships
This entity includes. Freight terms FOB points Invoicing rules Accounting rules Shipment priorities Payment terms Return reason Tax classification code Tax exemption reason Sales credit type Activity type Document categories Payment methods Receipt methods	Order Orchestration Reference Objects
Item Organization area of the Manage Items task in the Product Information Management work area.	Organizations
Manage Resources task in the Work Definition work area.	Resources
Manage Carriers task in the Setup and Maintenance work area.	Shipping Methods
-	Subinventories
Manage Suppliers task in the Suppliers work area.	Suppliers
Manage Units of Measure task in the Setup and Maintenance work area.	Units of Measure
Manage Work Definitions task in the Work Definition work area. You must include this entity for a make flow. If you don't, then Global Order Promising won't provide a recommendation for the make flow, and Supply Orchestration won't create a supply order. Order Management still processes the order but fulfillment won't benefit from the recommendation and supply order.	Work Definitions

• Refresh the Global Order Promising Server

• Overview of Data Collections for Supply Chain Planning

• Manage Planning Source Systems for Data Collections

• How You Collect Different Data Types for Supply Chain Planning

Set Up Promising and Sourcing Rules for Order Management

Use an available-to-promise (ATP) rule and sourcing rule to promise your sales order in different ways.

Global Order Promising uses sourcing rules, assignment sets, and available-to-promise rules when it determines availability and schedules an order line for Order Management.

Note.

1. Your customer places a sales order that includes the item and requested delivery date.

2. You create an available-to-promise rule, which is a set of instructions you specify that tells Order Promising how to analyze supply that's available in your supply chain so it can promise the item and meet the delivery date. You specify the supply type to consider, such as supply that's on hand or in transit, supply that various documents create, such as purchase orders, requisitions, or work orders.

3. You create a sourcing rule that specifies the supply sources to consider when promising, such as whether to consider make, buy, or transfer sources. You can also specify the optimal location that can supply the demand.

Summary of the Setup

1. Create your sourcing rule.

2. Assign your sourcing rule.

3. Create your available-to-promise rule.

4. Manage the administrator profile.

5. Refresh the server.

This topic includes example values. You might use different values, depending on your business requirements.

Create Your Sourcing Rule

In this example, you set up a relatively simple sourcing rule for the AS54888 item. You transfer it from an organization that stores inventory, such as Vision Manufacturing. For details about how to set up sourcing in other contexts, see the Manage Sourcing Rules section in the Set Up Drop Ship in Order Management topic and the Create Sourcing Rules for Configured Items topic.

1. Go to the Global Order Promising work area, then click Tasks > Manage Sourcing Rules.

2. On the Manage Sourcing Rules page, Click Actions > Create, then set values.

   Attribute	Value
   Name	Sourcing Rule for the AS54888 Item You can use any text.
   Organization Assignment Type	Global Set to. Global when you must specify where to fulfill and ship the sales orders. You don't specify an organization to create supply. Instead, you specify a transfer or buy source. Local when you must specify how to create supply and the organization that creates it. You create a global sourcing rule that specifies the warehouse that Order Management uses when it fulfills the sales order. For details, see the Overview of Sourcing Rules and Bills of Distribution topic.

3. In the Sourcing Rule Effective Dates area, click Actions > Add Row, then set the start date.

4. In the Sources area, Click Actions > Add Row, then set values.

   Attribute	Value
   Type	Transfer From Use Transfer From to transfer from an inventory organization. Global Order Promising enables Make At only when you set assignment type to Local.
   Organization	Vision Manufacturing
   Allocation Percent	100 In this example, you add only one source, so specify 100%. If you add more than one source, then you can allocate demand across sources. For example, if you add a row for Vision Manufacturing and set allocation to 70%, add another row for Vision Distribution and set allocation to 30%, then Promising will use Vision Manufacturing to promise 70% of the orders.
   Rank	1 If you add more than one source, then you can specify the rank order to use for sources. For example, if you add a row for Vision Manufacturing and set Rank to 1, add another row for Vision Distribution and set Rank to 2, then Promising will use Vision Manufacturing to promise the order first. If Promising determines that Vision Manufacturing can't fulfill the order, then Promising will consider Vision Distribution.
   Shipping Method	Global Order Promising disables Shipping Method for a local rule. You can't edit it. Leave it empty for a global rule. If you set a value for a global rule, you might get an error. The value provided for the Shipping Method attribute is invalid. Don't set shipping method in this context because it specifies where supply originates, not how to ship it to the customer.
   Exclude for Options and Option Classes	Exclude options and option classes when promising a sales order. Exclude them for a Make At or Buy From sourcing type. For example, exclude an item from planning when you know your source can't make it because it includes toxic chemicals that the source isn't authorized to handle, or your company limits production to only one specific site. For another example, assume you know Seattle Manufacturing created a large oversupply of the CTO_474100 screen option class from a prior marketing campaign. You already know supply is available. To improve planning performance, you decide to exclude it from planning.

5. Click Save > Save and Close.

Assign Your Sourcing Rule

1. Click Tasks > Manage Assignment Sets.

2. On the Manage Assignment Sets page, click Actions > Create.

3. On the Create Assignment Set page, set values.

   Attribute	Value
   Name	Assignment Set for Sourcing Rules
   Catalog	GOP_Catalog Use the same catalog that you use for your item in Production Information Management and in your available-to-promise rule.

4. In the Sourcing Assignments area, click Actions > Add Row, then set values.

   Attribute	Value
   Assignment Level	Item Note. Promising fulfills your sales order only from the source that you assign to the assignment set. Assign at least one sourcing rule at the global level so Global Order Promising can use it to identify a ship-from location. If you don't, then your users must specify the warehouse in every sales order.
   Item	AS54888
   Sourcing Type	Sourcing Rule
   Sourcing Rule or Bill of Distribution	Sourcing Rule for the AS54888 Item

For details, see the Sourcing Assignment Levels topic.

Create Your Available-To-Promise Rule

1. Click Tasks > Manage ATP Rules.

2. On the Create ATP Rule page, set values.

   Attribute	Value
   Name	ATP Rule for the AS54888 Item
   Description	Rule that specifies how to determine availability for the AS54888 item.
   Promising Mode	Infinite Availability

3. Click ATP Rule Assignment, click Actions > Add Row, set values, then click Save.

   Attribute	Value
   Assignment Basis	Item and Organization
   Assigned-to Organization	Vision Manufacturing Use the same value that you use in the Organization attribute in your sourcing rule.
   Assigned-to Item	AS54888

Manage the Administrator Profile

1. In the Setup and Maintenance work area, click Search, search for, then open the Manage Administrator Profile Values page.

2. On the Manage Administrator Profile Values page, set value, then click Search.

   Attribute	Value
   Application	Global Order Promising

3. In the search results, click that row that has MSP_DEFAULT_ASSIGNMENT_SET in the Profile Option Code column.

4. In the Profile Values area, click Actions > New, set values, then click Save and Close.

   Attribute	Value
   Profile Level	Site
   Profile Value	Pick the name of the assignment set that you created earlier in this topic. In this example, pick Assignment Set for Sourcing Rules.

Refresh the Server

For details see the Collect Planning Data for Order Management topic.

• How the Order Orchestration and Order Promising Processes Use the Collected Planning Data

• Overview of Security Console

• How Order Promising Rules Work Together

• Create Sourcing Rules for Configured Items

Display Customer Details

Overview of Displaying Customer Details on Sales Orders

Control how Order Management displays customer details on sales orders, such as ship-to address, bill-to address, contacts, and payment terms.

For example.

• Set the default value that the Order Management work area displays for each customer attribute and address attribute.

• Use an address from a related customer to set the default value for ship-to address.

• Use data from the customer master to set the default value for preferences on each sales order.

Order Management gets customer details from Oracle Trading Community Architecture (TCA). Trading Community Architecture is a data model you can use to manage details about customers who belong to your community, such as organizations, locations, and the relationships that define your community. For details, see Oracle Trading Community Architecture User Guide on My Oracle Support.

Party Object

The party object in Trading Community Architecture contains customer data. Order Management uses it to get the customer data it displays.

Note.

Object	Description
1. Party.	A trading partner. Each party can reference one or more party usages.
2. Party Usage.	How you use the party, such as customer, supplier, prospect, and so on. Order Management uses only the customer party usage. For example, searches and lists of values in the Order Management work area display only customer party usage.
3. Party Site.	An address that the party uses. Each party can reference one or more party sites.
4. Party Site Use.	How the party uses the address. For example, ship-to, bill-to, and so on. Each party site can reference one or more party site usages.
5. Location.	Physical address where the party site resides. Each party site can reference only one location.
6. Party Relationship.	Each party can reference one or more other parties. You can use the party relationship to establish a relationship between two different parties.

Account Object

Order Management uses the customer account object from Trading Community Architecture.

Note.

Object	Description
1. Customer Account.	The customer account is a child of the party. It includes financial details that Order Management uses to communicate with a financial application. Each party can reference one or more customer accounts, however each party typically references only one customer account.
2. Account Site.	Set of party addresses that the account uses. Each customer account can reference one or more account sites.
3. Account Site Use.	How the account site uses the address. Each account site can reference one or more account site usages.
4. Account Contact.	Person in the account. Each account can reference one or more contacts. Account contact is a subset of party contacts.

Where Order Management Displays Customer Details

Here's how Order Management displays customer data.

• Uses the party object to display data for customer attributes, such as Customer, Bill-to Customer, or Ship-to Customer.

• Uses the account object to display data for account attributes, such as Bill-to Account or Bill-to Address.

If the Order Entry Specialist sets the value for the Customer attribute on the order header, then Order Management automatically sets the value for other attributes to the data it gets from the party and account, such as contact, ship-to customer, address, bill-to customer, account, payment terms, and so on.

Note.

• In Oracle Fusion, the party object contains data for each customer, and the account object contains data for the bill-to account and bill-to address.

• In Oracle eBusiness Suite, the account object contains data for each customer. For example, the account contains the ship-to address, sold-to address, and bill-to address.

Display Account Details on Sales Orders

Control how Order Management displays account details on a sales order.

1. Get the license you need to use Oracle Fusion Financials.

2. Go to the Setup and Maintenance work area, then open the task.

   • Offering: Financials

   • Functional Area: Customers

   • Task: Manage Customers

3. On the Manage Customers page, search for a customer or create a new one.

   If you create a new account site, then the application also creates a party site that includes objects from the account site. This behavior helps to maintain the relationship between the party and the account.

Note.

• Don't delete a contact or address or set the end date for a contact or address. If you delete a contact or address, then sales orders that already exist might not display the correct data.

• Each account is a child of a party. If you add a contact, account site, or account site usage in the account, then Manage Customers adds objects in the party that correspond to the contact, account site, or account site usage that you added.

• If you delete or end date an object in a child contact, account site, or account site usage, then Manage Customers doesn't update the corresponding object in the parent party.

  For example, if you delete the ship-to address of a contact, then Manage Customers doesn't delete the corresponding ship-to address of the party. Manage Customers uses this functionality to maintain the relationship between party and customer account, which is one to many. Some other account might reference the ship-to address of the party.

Display Party Details on Sales Orders

Set up the party details that display on a sales order in Order Management.

You can't use the Manage Customers page to manage the parent party. Instead, do these steps.

1. Get the license you need to use Oracle CX Sales.

2. Sign in with a user you can use to administer customer data, such as TC_DATA_STEWARD.

3. In the Navigator, click Organizations > Customer Data Management.

4. On the Organizations page, search for your party according to organization name.

5. Use the Organization Details page to manage the party profile, party address, and party usage.

Note.

• Modify the value in the Purpose attribute to control site usage. For example, Order Management uses Ship-to purpose to filter the list of values that it displays for ship-to address.

• Add a check mark to the Primary attribute to specify the address that Order Management displays as the default value.

• You can't use the Manage Organization page to manage accounts.

To get details about how to manage an organization, go to Oracle Help Center at https://docs.oracle.com/en/cloud/saas/index.html. Under Customer Experience, click Customer Data Management > Books, then find Implementing Customer Data Management or Using Customer Data Management.

Display Default Values for Customer Attributes

Control how Order Management displays default values for customer attributes on sales orders.

If the Order Entry Specialist sets the Customer attribute on the order header, then Order Management automatically sets Bill-to Customer and Ship-to Customer to the same value that Customer contains, by default. You can modify this behavior.

To control the values that the user can choose, set the Customer Relationship Type order management parameter.

Value	Description
All Customers	Allow the user to choose any customer for Bill-to Customer and Ship-to Customer.
Single Customer	Allow the user to choose only the same value that the Customer attribute references for Bill-to Customer and Ship-to Customer.
Business Unit	Specify the business unit where this behavior applies. Use All Business Units to apply behavior to all sales orders.

Note.

• Order Management applies the behavior you specify to sales orders in the Order Management work area and to sales orders that you import.

• Order Management doesn't use relationships that you set up in Trading Community Architecture. If you must create a relationship, then set Customer Relationship Type to All Customers, and write an order management extension that enforces ship-to or bill-to customer for each party that Trading Community Architecture defines. For details, see the Define Extensions That Modify Order Management topic.

• For other relevant details, see the Manage Order Management Parameters topic.

Display Ship-to Addresses On Sales Orders

Control how Order Management displays the ship-to address on a sales order.

Set Default Value for Ship-to Address

If the Order Entry Specialist sets the value for Customer on the order header, then Order Management sets the value for Ship-to Address to the party site of the ship-to customer, by default.

You can use the Organization Details page to set the default value for Ship-to Address.

Note.

• Add a check mark to the Primary attribute on the address.

• If you don't specify the Purpose on the Organization Details page, and if you do specify a Primary, then Order Management sets ship-to address to the primary, by default.

Control Drop Down for Ship-to Address

On the Organization Details page, set Purpose to Ship-to for each address you must display in the Ship-to Address drop down in Order Management.

Control Search for Ship-to Address

Order Management returns all party sites in Ship-to Address regardless of usage when the user clicks Search, by default. For example, it returns ship-to usages and bill-to usages.

If you use Oracle Fusion Financials, then set order management parameter Filter Ship-to Address According to Ship-to Usage to Yes. This setting makes sure your users select only ship-to sites to avoid an error from occurring when the import automatically invoices the transaction.

Allow Users to Search Ship-to Address According to Party Site

Your users can use advanced search in the Search and Select dialog to search for ship-to addresses according to the name of the ship-to party site. This dialog displays the name you specify when you set up your ship-to party site. This feature is useful when your deployment uses a large set of addresses. It allows your users to search when they don't know the mailing address of the site.

For example, assume you support a retailer named Computer Service and Rentals who sells at 200 separate physical locations. You can allow your users to search on the text Computer Service to return all locations that begin with the text Computer Service.

Use a Web Service to Set Ship-to Address

The Organization Details page restricts the sites you can set as the primary according to the party object hierarchy. Instead, you can use the OrganizationService web service to specify the ship-to address. For example.

https://server:port/crmService/FoundationPartiesOrganizationService
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/cdm/foundation/parties/organizationService/applicationModule/types/" xmlns:org="http://xmlns.oracle.com/apps/cdm/foundation/parties/organizationService/" xmlns:par="http://xmlns.oracle.com/apps/cdm/foundation/parties/partyService/" xmlns:sour="http://xmlns.oracle.com/apps/cdm/foundation/parties/flex/sourceSystemRef/" xmlns:con="http://xmlns.oracle.com/apps/cdm/foundation/parties/contactPointService/" xmlns:con1="http://xmlns.oracle.com/apps/cdm/foundation/parties/flex/contactPoint/" xmlns:org1="http://xmlns.oracle.com/apps/cdm/foundation/parties/flex/organization/" xmlns:par1="http://xmlns.oracle.com/apps/cdm/foundation/parties/flex/partySite/" xmlns:rel="http://xmlns.oracle.com/apps/cdm/foundation/parties/relationshipService/" xmlns:org2="http://xmlns.oracle.com/apps/cdm/foundation/parties/flex/orgContact/" xmlns:rel1="http://xmlns.oracle.com/apps/cdm/foundation/parties/flex/relationship/"> 
    <soapenv:Header/>
    <soapenv:Body>
       <typ:mergeOrganization>
          <typ:organizationParty>
             <org:PartyId>300100178657728</org:PartyId>
            <org:PartySite>
<par:PartySiteId>300100178657747</par:PartySiteId>
                <par:PartySiteUse>
<par:PartySiteUseId>300100178657752</par:PartySiteUseId>
<par:PrimaryPerType>Y</par:PrimaryPerType>
                </par:PartySiteUse>
             </org:PartySite>
          </typ:organizationParty>
       </typ:mergeOrganization>
    </soapenv:Body>
 </soapenv:Envelope>

where

Code	Description
server:port	Address to the server that hosts your Oracle Fusion deployment.
PartyId	Value that uniquely identifies the party, such as 300100178657728.
PartySiteId	Value that uniquely identifies the party site, such as 300100178657747.
PartySiteUseId	Value that uniquely identifies the party site use, such as 300100178657752. You specify the Id of the ship-to site use.
PrimaryPerType Y	Sets the site use to the primary site.

You replace the values for PartyId, PartySiteId, and PartySiteUseId with values that identify the party, the address, and the site use Id that identifies the address to set as the default ship-to address on each sales order for the party.

To set the primary ship to site, use findOrganization to get the identifiers for mergeOrganization.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body xmlns:ns1="http://xmlns.oracle.com/apps/cdm/foundation/parties/organizationService/applicationModule/types/">
        <ns1:findOrganization>
            <ns1:findCriteria xmlns:ns2="http://xmlns.oracle.com/adf/svc/types/">
                <ns2:fetchStart>0</ns2:fetchStart>
                <ns2:fetchSize>-1</ns2:fetchSize>
                <ns2:filter>
                    <ns2:conjunction>And</ns2:conjunction>
                    <ns2:group>
                        <ns2:conjunction>And</ns2:conjunction>
                        <ns2:upperCaseCompare>false</ns2:upperCaseCompare>
                        <ns2:item>
                            <ns2:conjunction>And</ns2:conjunction>
                            <ns2:upperCaseCompare></ns2:upperCaseCompare>
                            <ns2:attribute>PartyNumber</ns2:attribute>
                            <ns2:operator>=</ns2:operator>
                            <ns2:value>1001</ns2:value>
                        </ns2:item>
                    </ns2:group>
                </ns2:filter>
                <ns2:excludeAttribute>false</ns2:excludeAttribute>
            </ns1:findCriteria>
            <ns1:findControl xmlns:ns3="http://xmlns.oracle.com/adf/svc/types/">
                <ns3:retrieveAllTranslations>false</ns3:retrieveAllTranslations>
            </ns1:findControl>
        </ns1:findOrganization>
    </soap:Body>
</soap:Envelope>

For details about how to use web services with Trading Community Architecture, see SOAP Web Services for Oracle Sales Cloud on My Oracle Support at https://docs.oracle.com/en/cloud/saas/sales/r13-update17d/oesws/toc.htm.

Set Default Value for Contact Method

The Contact Method describes how to contact the person that you set in the Contact attribute on the sales order. Assume Tang Taizong is a contact for your Computer Service and Rentals customer. if Contact contains Tang Taizong, and Contact Method contains [e-mail], then you can use the [e-mail] email address to contact Taizong.

Assume you need to set Taizong's site to 1800 Satellite Drive, Distribution Center, and you need to set the default value for the Contact Method to Taizong's email address, but you haven't yet specified a contact point for Taizong.

You edit Taizong's contact details in the Setup and Maintenance work area at design time to specify the contact point. Order Management then displays the contact point in the Contact Method on the sales order at run time.

To set the default value that displays at run time in the Contact Method attribute, make sure you have only one contact point on the Edit Contacts page. For example, if you have an email contact point and a phone contact point, then no value will display in the Contact Method attribute, by default.

Try it.

1. Go to the Setup and Maintenance work area, then open the task.

   • Offering: Financials

   • Functional Area: Manage Customers

   • Task: Manage Customers

2. On the Manage Customers page, search for the value.

   Attribute	Value
   Organization Name	Computer Service and Rentals

3. Scroll down to the Sites area, then click the link in the Site Number column in the row that contains the address you're looking for.

   Attribute	Value
   Address	1800 Satellite Drive, Distribution Center,CHATTANOOGA, TN 37401

   For this example, assume the Site Number is 1222.

4. On the Edit Site page, click Communication, then click Edit Contact.

5. On the Edit Contacts page, in the Contact Points area, click Actions > Create.

6. In the Create Contact Point dialog set values, then click OK.

   Attribute	Value
   Contact Point Type	Email
   Email Format	Plain Text Email
   Email	[e-mail]

   Make sure the Contact Points list contains only one row. If it has more than one row, then Order Management won't set a default value for the Contact Method attribute on the sales order.

7. Click Save and Close.

8. On the Manage Customers page, click Done.

Test Your Set Up

1. Go to the Order Management work area, then create a sales order.

   Attribute	Value
   Customer	Computer Service and Rentals

2. Verify the attributes values.

   Attribute	Value
   Contact	Tang Taizong
   Contact Method	[e-mail]

Display Bill-to Addresses On Sales Orders

Control how Order Management displays the bill-to address on a sales order.

Set Default Value for Bill-to Address

Order Management can set the Bill-to Address to the account site that the bill-to account references. You can edit the site to control this behavior.

Navigate to the Manage Customers page, then edit the site.

If . . .	. . . Then
Only one site specifies bill-to usage.	Order Management defaults the address to this one site.
More than one site specifies bill-to usage.	Use the Address Purposes area to set the Primary. Order Management will use the primary as the default value for Bill-to Address.

Display Only Bill-to Usages in Bill-to Address

Order Management includes each account site that uses bill-to usage in the drop down for Bill-to Address, by default. Bill-to Address filters account sites according to the business unit that the sales order references. The user can't search this attribute. The user can only choose values from the list.

To control the addresses that display, set the Purpose on the account site to bill-to usage when you set up your account.

Display Contacts on Sales Orders

Control how Order Management displays contacts on sales orders.

Set Default Value for Contact on Order Header

The Order Entry Specialist can choose a contact from the sold-to customer or the ship-to site in attribute Contact on the order header, by default.

If the Order Entry Specialist clicks Search, then the Contact attribute displays all contacts that reference a sold-to or ship-to contact.

Note that Contact on the order header displays party contacts. It doesn't display account contacts.

If you set the primary contact on the account site, then Order Management populates the Contact attribute on the order header to this primary when the user sets the Customer attribute on the order header.

Set Primary Contact on Account Site

1. On the Manage Customers page, search for the party you must modify.

2. In the Sites area, click the Site Number for an account site.

3. On the Edit Site page, click Communication.

4. In the Account Site Contacts area, click Edit Contacts.

5. On the Edit Contacts page, click Actions > Set Primary Contact.

   

6. Click Save and Close.

Set Default Value for Contact in Billing and Payment Details

If you specify the primary account during set up, then Order Management populates the Contact attribute in the Billing and Payment Details area to the primary contact for this account when the user sets Customer on the order header.

If the user clicks Search, then the drop down for Contact displays each contact that references a bill-to address.

Note that Contact in the Billing and Payment Details area displays account contacts. It doesn't display party contacts.

Display Payment Terms on Sales Orders

Control how Order Management displays payment terms on sales orders.

Set Default Value for Payment Term

The payment term is a financial attribute on the account and account site. Order Management populates the Payment Term attribute when the Order Entry Specialist sets one of the following attributes in the Billing and Payment Details area.

Attribute	Description
From Bill-to Address	Get and display the payment term that you define on the bill-to address for the bill-to site during set up.
From Bill-to Contact	Get and display the payment term that you define on the bill-to account during set up.

Note.

• If you don't specify the payment term on the bill-to address or the bill-to account in Trading Community Architecture, then Order Management doesn't set any default value for the payment term, and the Order Entry Specialist must manually set it.

• The Order Entry Specialist can click Payment Terms to view all values that you collect during data collection, including values from Oracle Fusion, Oracle Advanced Supply Chain Planning, your channel systems, and so on. For details about data collection, see the How Order-to-Cash with Order Capture Systems Works topic.

Set Default Value to Payment Term from Account Site

Specify to use the payment term from the account site as the default value.

1. On the Manage Customers page, search for the party you must modify.

2. In the Sites area, click the Site Number for an account site.

3. On the Edit Site page, click Profile History.

4. In the Profile History area, click Actions > Correct Record.

5. On the Site Profile tab, in the Terms area, choose a value for the Payment Terms attribute.

6. Click Save and Close.

For example.

Make Sure User Sets Payment Term

If you use Oracle Fusion Financials, then Payment Term must contain a value. To meet this requirement, you can enable the Fulfillment Line Payment Term Update predefined constraint. If you enable it, and if Payment Term is empty, then the constraint prevents the Submit action.

This requirement helps to avoid problems when Financials invoices the fulfillment line. This constraint comes predefined as disabled. You can enable it.

Set values on the Managing Processing Constraints page. For details, see the Manage Processing Constraints topic.

Attribute	Description
Constraint Name	Search for DOO_FULFILLMENTLINE_PAYMENTTERMS_MISSING.
Enabled	Add a check mark.

Here's the logic that the constraint.

Attribute	Description
Constraint Name	DOO_FULFILLMENTLINE_PAYMENTTERMS_MISSING.
Constraint Entity	Prevent Order Management from performing the operation that Constrained Operation specifies on Order Fulfillment Line.
Constrained Operation	Submit.
Validation Entity	Specifies to perform the validation on Order Fulfillment Line.
Validation Rule Set	Specifies to use the Fulfillment Line Payment Term Is Null rule set to determine whether the Payment Term attribute on the fulfillment line contains a value.

Set Default Values for Other Attributes on Sales Orders

Here are some techniques you can consider when you set the default value for various attributes on sales orders.

• Set up a pretransformation rule. For example, set the default value for the customer contact according to business unit and customer.

  If business unit is y, and if customer is x, then set contact to z.
  

• Order Management runs pretransformation rules each time the user modifies the Customer attribute. This configuration makes sure Order Management updates default values according to rules you define. For details, see the Use Business Rules With Order Management topic.

• Set up an order management extension. For example, get data from a customer entity on the sales order, and then use this data as the default value.

  If customer class is x, then set order type to z.
  If descriptive flexfield on customer contains a, then set attribute b to c.
  

Import Customer Data for Your Sales Orders

Import customer data, then display it on your sales order.

Set Default Values During Order Import

Order import doesn't set the default value for an address, contact, or payment term. Your import payload or the order import template must specify them.

If you use order import template SourceSalesOrderImportTemplate.xlsm, then do these tasks.

• Use the DOO_ORDER_ADDRESSES_INT worksheet to specify default values for the order header and order lines.

• Set values depending on whether your import creates or updates.

  Create or Update	Description
  Create a new sales order	Send addresses on the order header, and the import will cascade order header data to the new order line.
  Update a sales order	To set the order header, leave these columns empty. Source Transaction Line Identifier Source Transaction Schedule Identifier To set order lines, make sure these columns contain values. An update must contain data for each order line.

• Use the instructions in the worksheet to set ship-to and bill-to values.

For details, see the Import Orders into Order Management topic.

Import Payment Terms

Note.

• Use the DOO_ORDER_LINES_ALL_INT worksheet of the order import template to import payment terms.

• Use the Payment Term Code or the Payment Term column.

• If you use Oracle Fusion Financials, then make sure you send payment terms for each order line in each imported order that you must invoice.

• Order import doesn't support payment terms on the order header so you can't cascade payment terms from the order header to order lines.

Create New Customers

Order Management doesn't provide an administrative interface you can use to create a new customer, but you can use the order import template instead.

1. Open the DOO_ORDER_HEADERS_ALL_INT worksheet.

2. Set the Create Customer Information Flag column to Y.

3. Position the cursor over the column header to view details.

4. Fill in all customer data on these worksheets.

   • DOO_ORDER_HEADERS_ALL_INT

   • DOO_ORDER_ADDRESSES_INT

Other Ways to Create Customer Data

Use the customer import services in Trading Community Architecture to bring customer data into Oracle from your channel system or legacy system.

Security

Set Up User Roles and Privileges in Order Management

Set up user roles and privileges to manage the authentication and authorization that Order Management uses to secure order management processing, including web service usage.

Here's how Order Management implements security.

• Uses authentication through a user name and password during sign in to allow each user to access the Order Management work area

• Uses authorization through user roles and privileges to allow each user to do different tasks according to job outcome in the Order Management work area

This topic describes how to examine privileges and job roles that come predefined to use with Order Management, and how to add an Order Management user. For background details, see the books on Oracle Help Center.

Book	Details
Securing Oracle SCM Cloud	Job roles, privileges, duty roles, and how to set up security, including values you set for each user.
Security Reference for Order Management	Job roles that come predefined to use with Order Management.

Here are some examples of roles you might need to set up.

Role	Description
Pricing Administrator- All Business Units, which is QP_PRICING_ADMINISTRATOR_ALL_BUSINESS_UNITS_DATA	Use this role to administer pricing. Add it when you do the Set up Pricing task.
Product Manager, which is EGP_PRODUCT_MANAGER_JOB	Use this role to set up organizations and items so you can add items to your sales orders.

Summary of the Set Up

1. Create users and assign job roles.

2. Create a job role.

3. Manage data access for users.

This topic includes example values. You might use different values, depending on your business requirements.

Create Users and Assign Job Roles

Create two users and assign job roles. One user can use administrative privileges. The other user can use only view privileges.

1. Sign into Oracle Fusion Applications as the it_security_manager or with a job role that you can use to manage job roles.

   If you don't sign in with a job role that you can use to manage job roles, then various actions will be grayed out when you do the Create Implementation Users task, such as copying a job role, and you won't be able to add privileges to a job role.

2. Go to the Setup and Maintenance work area, then go to the task.

   • Offering: Order Management

   • Functional Area: Initial Users

   • Task: Create Implementation Users

3. On the User Accounts page, click Add User Account, enter values, then click Add Role.

   Attribute	Value
   First Name	Diane
   Last Name	Cho
   Email	[e-mail]

4. In the Add Role Membership dialog, enter Order Manager, then click Search.

5. In the search results, click the row that contains the values.

   Attribute	Value
   Name	Order Manager
   Code	ORA_DOO_ORDER_MANAGER_JOB

6. In the Confirmation dialog, click Add Role Membership > OK, then click Done

7. On the Add User Account page, add passwords for the user, then click Save and Close.

   Each user can use these passwords the first time the user signs in. Instruct your users to change passwords immediately after sign in.

Create another user and assign a job role so the user can only view sales orders, but not create, update, or delete them.

1. Identify the role that provides only view access to sales orders.

   • On Oracle Help Center, locate the Security Reference for Order Management book.

   • Examine the roles, duties, privileges, and policies until you locate one that meets your needs. For this example, the Order Entry Specialist is the most likely role.

   • In the Order Entry Specialist section, scroll through the Privileges area until you locate the Item Inquiry granted role.

     Granted Role	Description	Privilege
     Item Inquiry	Queries and views items in the enterprise.	Manage Item Attachment
     Item Inquiry	Queries and views items in the enterprise.	Manage Item Catalog
     Item Inquiry	Queries and views items in the enterprise.	Manage Item Global Search
     Item Inquiry	Queries and views items in the enterprise.	Manage Trading Partner Item Reference
     Item Inquiry	Queries and views items in the enterprise.	View Item
     Item Inquiry	Queries and views items in the enterprise.	View Item Organization Association
     Item Inquiry	Queries and views items in the enterprise.	View Item Relationship

   • For this example, you must provide only read access, so you will use the View Item privilege.

2. On the User Accounts page, click Add User Account, set values, then click Add Role.

   Attribute	Value
   First Name	Yu
   Last Name	Li
   Email	[e-mail]

3. In the Add Role Membership dialog, enter the role you located earlier in this procedure, Order Entry Specialist, then click Search.

4. In the search results, click the row that contains the values.

   Attribute	Value
   Name	Order Entry Specialist
   Code	ORA_FOM_ORDER_ENTRY_SPECIALIST_JOB

5. In the Confirmation dialog, click Add Role Membership > OK , then click Done.

6. On the Add User Account page, add passwords for this user, then click Save and Close.

Create Job Role

As an option, you can create a job role to meet your business requirements. In this example, you create a job role that allows Yu to view sales orders but not edit them.

1. On the User Accounts page, click Roles.

2. On the Roles page, in the Search window, enter Order Entry, then click Search.

3. In the search results, in the row that contains these values, click Actions > Copy Role.

   Attribute	Value
   Name	Order Entry Specialist
   Code	ORA_FOM_ORDER_ENTRY_SPECIALIST_JOB

   Tip: Reduce your work load. Modify the copy of a predefined role rather than create a new one.

4. In the Copy Options dialog, choose Copy Top Role, then click Copy Role.

5. On the Basic Information page, enter values, then click Next.

   Attribute	Value
   Role Name	Order Entry Specialist View Only
   Role Code	FOM_ORDER_ENTRY_SPECIALIST_JOB_VIEW_ONLY
   Description	Search for and view sales orders, including sales order header, order lines, price details, and price totals. Don't allow user to create, update, or delete any part of the sales order.

6. On the Function Security Policies page, delete all rows except rows that contain these privileges.

   • Monitor Sales Order

   • View Customer Account

   • View Customer Account Contact

   • View Customer Account Contact Responsibility

   • View Customer Account Information

   • View Customer Account Site

   • View Customer Account Site Use

   • View Fulfillment Line Freight Charges and Cost

   • View Fulfillment Line Shipping and Tracking Details

   • View Item

   • View Item Organization Association

   • View Item Relationship

   • View Orchestration Infrastructure Messages

   • View Orchestration Order Fulfillment Line Hold

   • View Orchestration Order Hold

   • View Orchestration Order Line Hold

   • View Orchestration Process Details

   • View Orchestration Process Hold

   • View Order Orchestration Request Messages

   • View Orders

   • View Planning Supply Availability

   • View Supply Availability Report

   • View Supply Chain Financial Orchestration System Options

   • View Supply Orders

   For example.

   

   Note.

   • If you must add a privilege, then click Add Function Security Policy.

   • If you must add all privileges, for example you choose to not copy a predefined role, then, in the Add Function Security Policy dialog, enter the first characters that are similar across a group of privileges, such as View Customer, click Search, then add each privilege from the search results.

7. On the Data Security Policies page, delete each row that includes these values.

   Attribute	Values
   Policy Name	Grant on Collaboration Document Header Grant on Business Unit

   To delete a row, click the down arrow in the row, then click Remove Data Security Policy.

8. Verify that the Data Security Policies page displays these policies.

   Policy Name	Policy Description	Privilege
   Grant on Trading Community Customer Account Site Use	Order entry specialist can view customer account site use.	Read, View Customer Account Site Use
   Grant on Trading Community Relationship	Order entry specialist can view trading community relationship.	Read, View Trading Community Relationship
   Grant on Trading Community Organization Party	Order entry specialist can view trading community organization.	Read, View Trading Community Organization
   Grant on Application Reference Data Set	Order entry specialist can view customer account site use.	View Customer Account Site Use
   Grant on Application Reference Data Set	Order entry specialist can view customer account site.	View Customer Account Site,
   Grant on Trading Community Party	Order entry specialist can view trading community person.	Read, View Trading Community Person
   Grant on Trading Community Customer Account	Order entry specialist can view customer account.	Read, View Customer Account
   Grant on Application Reference Data Set	Order entry specialist can view customer account relationship.	View Customer Account Relationship
   Grant on Trading Community Customer Account Site	Order entry specialist can view customer account site.	Read, View Customer Account Site

   Specify the Create, Read, Update, and Delete Actions

   Specify the actions that each policy allows. For example.

   • In the Policy Name column, in the row that contains this value, click Actions > Edit Data Security Policy.

     Attribute	Value
     Policy Name	Grant on Trading Community Customer Account Site Use

   • In the Edit Data Security Policy dialog, next to Actions, click the down arrow, then add or remove the check mark next to each of the actions you will allow or disallow the user to do.

     For example, View Customer Account Site, Manage Customer Account Site, Read, Delete, Update, and so on. For this example, you're setting up a read-only view, so make sure only the view actions and read actions contain a check mark.

   Specify Access According to a Group of Business Units

   A business unit set as a group of business units that you can use for a specific setup. For example, assume you add business unit 1 and business unit 2 to business unit set x, and then attach Payment Term NET30 to set x. You can then use this payment term for business unit 1 and business unit 2.

   The Set Id identifies the business unit set. For details about the business unit set, see the Overview of Multiple Business Units in Sales topic.

   You can specify the actions that each policy allows according to Set Id. For example.

   • In the Policy Name column, in the row that contains this value, click Actions > Edit Data Security Policy.

     Attribute	Value
     Policy Name	Grant on Application Reference Data Set

   • In the Edit Data Security Policy dialog, next to Actions, click the down arrow, then notice you can specify a wide range of views and manage actions that the user can perform.

   Specify Access According to Business Unit

   You can specify the actions that each policy allows according to business unit. For example.

   • Click Create Data Security Policy.

   • In the Create Data Security Policy dialog, click Search.

   • In the Search Database Resources dialog, enter Business Unit, click Search, wait for the results to display, then click OK.

   • Set values.

     Attribute	Value
     Policy Name	Grant on Business Unit
     Data Set	Select by Instance Set You can also use Select by Key to specify the business unit according to BU_ID.
     Condition Name	Specify how to filter according to business unit. For most situation, choose Access the Business Unit for Which the User is Explicitly Authorized.
     Actions	Choose the actions that you must allow the user to do for the business unit.

9. Click Next.

10. On the Role Hierarchy page, delete all role hierarchies except for. . .

    Role Name	Role Code
    Item Inquiry	ora_egp_item_inquiry_duty
    Item Inquiry	ora_egp_item_inquiry_duty_hcm
    Item Inquiry	ora_egp_item_inquiry_duty_obi
    Item Inquiry	ora_egp_item_inquiry_duty_crm
    Manage Item Catalog	egp_manage_item_catalog_priv_obi
    Print Order	fom_print_order_priv_obi

    Use the Role Hierarchy page to specify other job roles that the job role you're creating can access. A role hierarchy is a hierarchy that specifies other job roles that a job role references.

    For example, here's the predefined role hierarchy that the Order Entry Specialist job role uses.

    Order Entry Specialist
    
              B2B Messaging Administration
    
                        Collaboration Messaging Manager
    
                        Collaboration Messaging Setup
    
                        SOA Infra Designer
    
              FSCM Load Interface Administration
    
              Item Inquiry
    
              Upload data for Source Sales Order Import
    

    For details about the role hierarchy that each predefined job role uses, see the Security Reference for Order Management book.

11. Click Next.

12. On the Users page, click Add User.

13. In the Add User dialog, search for Yu Li, wait for the results to display, click Add User to Role > OK in the confirmation dialog, then click Cancel.

14. Click Next > Save and Close.

Manage Data Access for Users

Manage data access for Yu.

1. Go to the Setup and Maintenance work area, then go to the task.

   • Offering: Order Management

   • Functional Area: Initial Users

   • Task: Manage Data Access for Users

   For details about this task, see the Implementing Common Features for Oracle SCM Cloud book on Oracle Help Center.

2. On the Manage Data Access for Users page, enter a value, then click Search.

   Attribute	Value
   User Name	yu.li You must search according to dot notation, which is firstName.lastName.

   The search results display the data access you set up for Yu, including for the Order Entry Specialist role where you added Yu as a user on the User Accounts page, and the other job roles you specified when you created the Order Entry Specialist View Only job role, and then assigned to Yu.

3. Click Authorize Data Access.

4. In the Opening SecurityDataAccessTemplate.xls dialog that displays, accept the Open With option, then click OK.

   Microsoft Excel opens.

5. Edit in Microsoft Excel.

   • In Microsoft Excel, in the Connect dialog, click Yes.

   • On the Login page, sign in with the IT Security Manager job role (ora_fnd_it_security_manager_job).

   • In the Authorize Data Access for Users template that displays, verify that the template includes the security contexts that Yu needs for view access.

     Security Context	User Name	Role
     Business unit	[e-mail]	Order Entry Specialist
     Data access set	[e-mail]	Order Entry Specialist View Only
     Asset book	[e-mail]	Order Entry Specialist View Only
     Business unit	[e-mail]	Order Entry Specialist View Only
     Control budget	[e-mail]	Order Entry Specialist View Only
     Cost organization	[e-mail]	Order Entry Specialist View Only
     Intercompany organization	[e-mail]	Order Entry Specialist View Only
     Ledger	[e-mail]	Order Entry Specialist View Only
     Manufacturing plant	[e-mail]	Order Entry Specialist View Only
     Inventory organization	[e-mail]	Order Entry Specialist View Only
     Project organization classification	[e-mail]	Order Entry Specialist View Only
     Reference data set	[e-mail]	Order Entry Specialist View Only

   • In the Security Context Value column, in the first row that contains data, right-click the cell, then click Invoke Action.

     Caution: Use this action instead of manually entering text. This action searches the Oracle database for the data access sets you can use. If you manually enter text, and if your text doesn't exactly match text that the database contains, then the upload will fail.

   • In the Select Security Context Value dialog, set the value, then click Search.

     Attribute	Value
     Business Unit	Vision Operations

   • In the search results, click the row that includes Vision Operations, then click OK.

     Notice that Excel adds Vision Operations to the cell you selected in the Security Context Value column.

   • Repeat the above steps for each of the other rows that contain data.

     For example, for the row that contains Asset Book, set value Security Context to an asset book.

   • In the command ribbon that displays across the top of Excel, click Authorize Data Access for Users > Upload.

   • Wait for the upload to finish, then verify that the Status column displays Successfully Uploaded for each row.

   • Click Status Viewer, then verify that the Status View displays No Error.

   • Sign out.

6. Go back to Oracle Fusion Applications.

7. In the Navigator, click Scheduled Processes

8. On the Scheduled Processes page, click Schedule New Process, then run the scheduled process.

   Scheduled Process Name	Description
   Retrieve Latest LDAP Changes	Synchronizes users, roles, and role grants with the definitions that exist in LDAP (Lightweight Directory Access Protocol ) that Order Management uses to determine who can access the Order Management work area.

Examine Role Usage in Your Implementation Project

Your implementation project specifies the roles that can do each task in the project. You will examine how a predefined implementation project allows the Order Administrator role to manage source systems where you typically use web services to communicate data.

1. Go to the Setup and Maintenance work area.

2. On the Setup page, click Tasks, then click Manage Implementation Projects.

3. On the Manage Implementation Projects page, click Actions > Create.

4. On the Create Implementation Project page, click Next.

5. In the Order Management row, add a check mark in the Include column, then click Save and Open Project.

6. In the Task list, expand Order Management > Define Orders, then, in the Manage Upstream and Fulfillment Source Systems row, in the Authorized Roles column, click Details.

7. Notice that the Authorized Roles dialog includes the Order Administrator role.

• Overview of Multiple Business Units in Sales

Assign Job Roles in Order Management

A duty role allows Order Management Cloud to access the web services it uses to communicate with an external system according to the user currently logged in. You must make sure any job roles you create can reference the duty roles that Order Management requires.

• A job role is the sign in that allows each user to access the application features that the user needs to do their job in their organization, and to access the data that these features reference. Example job roles in Order Management include Order Entry Specialist, Order Manager, Order Administrator, Supply Chain Application Administrator, and so on.

• A duty role is a group of function and data privileges that represent one duty of a job. Each duty role is specific to an application, stored in the policy store, and shared in an application instance.

Assume one of your users release a sales order for shipping. The job role that this user uses must reference the duty roles that allow Order Management to call the shipping system and to receive details about the shipment from the shipping system. In this example, you must assign a job role that references these duty roles.

• Shipment Request Processing Web Service Duty

• Orchestration Order Shipping Web Service Duty

For details about job roles, duties, and how to set them up, see Oracle SCM Cloud Security Reference for Order Management on Oracle Help Center at https://docs.oracle.com/en/cloud/saas.

Predefined Job Roles

Here are the job roles that come predefined with Order Management.

Job Role	Responsibilities
Order Entry Specialist	Create new sales orders, update existing sales orders, and create return sales order. Create sales orders in the Order Management work area or modify sales orders that you import from a source system. Monitor order fulfillment. Work directly with customers who purchase items. This job role includes these duty roles. FSCM Load Interface Administration Duty Item Inquiry Duty
Order Manager	Manage sales orders created in the Order Management work area or that you import from a source system. Makes sure Order Management books sales orders so they can proceed to order fulfillment. Approve sales orders that require approval. Work with other professionals in the organization, such as pricing administrator, customer contract manager, credit manager, and accounts receivable manager, to help determine set up requirements and troubleshoot problems. This job role includes these duty roles: Orchestration Order Monitoring Duty Orchestration Order Management Duty Orchestration Order Scheduling Duty
Order Administrator Supply Chain Application Administrator	Set up and maintain Order Management Cloud so it supports order entry and order fulfillment. Set up rules, policies, constraints, and so on. For example, set up defaulting rules, order entry preferences, order entry privileges, orchestration processes, change order rules, process planning, jeopardy conditions, order statuses, and hold definitions. Set up orchestration. Each of these job roles include these duty roles. Orchestration Order Administration Duty Orchestration Infrastructure Administration Duty

Duty Roles

Here are the duty roles that allow Order Management to communicate with a system that resides outside of Order Management Cloud. The Description column describes the communication that the web service provides.

Duty Role	Description
Order Orchestration Decomposition Web Service Duty	Communicate with source systems so Order Management can separate source orders during transformation.
Orchestration Order Activity Management Web Service Duty	Communicate with a fulfillment system that can process an activity.
Orchestration Order Billing Web Service Duty	Communicate with a system that processes the billing for each sales order.
Orchestration Order External Integration Web Service Duty	Allow a system that resides outside of Order Management Cloud to call Order Management Cloud.
Orchestration Order Fulfillment Web Service Duty	Allow a fulfillment system to send status updates to Order Management through a task service.
Orchestration Order Inquiry Web Service Duty	Extract order details from a sales order.
Orchestration Order Receiving Web Service Duty	Receive a return for a sales order.
Orchestration Order Shipping Web Service Duty	Process the shipment of a sales order.
Orchestration Order Template Web Service Duty	Allow a fulfillment system to send status updates for fulfillment tasks through a task service.

Integrate Social Objects from Order Management Into Oracle Social Network

Use the Order Manager or the Order Orchestration error recovery role.

Copy Setups

Copy Setups Between Instances of Order Management

Copy your setup from one instance of Order Management into another instance during the lifecycle of your Order Management deployment. For example, migrate your setup from a test environment to a production environment.

• Use the Manage Configuration Packages page in the Setup and Maintenance work area to export and import a configuration package.

• For the list of business rules that the copy migrates, see the Migrate Business Rules in Order Management topic.

• For details about migrating approval rules, see the Copy Approval Rules Between Instances of Order Management topic.

• You can use WebLogic Scripting Tool (WLST) commands to move order orchestration rules. Order Management stores order orchestration rules in the Metadata Services (MDS) Repository. You can also use data collection and interface tables to import your setup and your transaction data. For details, see the Importing and Exporting Setup Data section in Implementing Common Features for Oracle SCM Cloud on Oracle Help Center.

• The migration adds hold codes that you set up in the source instance to hold codes that exist in the target instance. If the same hold codes exist in the source and target, then the holds in the source replace the holds in the target.

• The migration doesn't migrate holds that apply a credit check hold or release a credit check hold.

• The migration migrates only your set ups. It doesn't migrate transactional data, such as sales orders.

• Don't modify the orchestration process name, task name in an orchestration process step, or the status rule set name in either environment. Modifying the name might prevent Order Management Cloud from updating references to other data in the orchestration process. For details, see these topics.

  • Guidelines for Setting Up Orchestration Processes

  • Guidelines for Setting Up Orchestration Process Steps

  • Fulfillment Line Status

• If you created an order management extension, then prepare it before you migrate. For details, see the Guidelines for Creating Order Management Extensions topic.

• If you migrate from a production environment to a test environment, and if your migration includes an orchestration process that's currently in progress, then the sales order that references the process will become stuck. It isn't possible to recover the stuck order.

• The migration migrates only your set ups. It doesn't migrate transactional data, such as sales orders.

Summary of the Steps

1. Export your setup.

2. Import your setup.

3. Deploy flexfields.

Export Your Setup

Export your setup from the source instance of Order Management.

1. Make sure the source instance and the target instance are at the same release level.

2. Sign into the source instance of Order Management with administrative privileges.

3. In the Navigator, click Setup and Maintenance.

4. On the Setup page, click Tasks > Manage Configuration Packages.

5. On the Manage Configuration Packages page, click Actions > Create.

6. On the Enter Basic Information page, set values, then click Next.

   Attribute	Value
   Name	Choose the name of the implementation project that defines the source instance.
   Export	Setup task list and setup data

7. On the Select Objects for Export page, accept default values, then click Next.

   The Select Objects for Export page comes predefined to select the objects that the export needs to support most instances of Order Management. For details about the objects you can export, see the Copy Setup Data Between Instances of Order Management topic.

8. On the Schedule and Notifications page, accept the default value, click Submit, then, in the Warning dialog, click Yes.

   Attribute	Value
   Run	As soon as possible

9. On the Manage Configuration Packages page, examine results in the elements, then sign out.

   Element	Description
   Export Setup Data button	Export a configuration package after you create it. The export identifies setup data according to the export definition and adds it to the configuration package. Export a configuration package more than one time. Each export creates a different configuration package version that you can manage individually.
   Download Latest Version	Download the most recent version of the configuration page.
   Export and Import Processes area	Get details of the export or import for each configuration package.
   Status	Examine the process status for each implementation project. Click the status to get details about each step of the export or import process.
   Download	Download a version so you can use it during an export or import.
   Setup Data Report	View or download a report that contains the setup data exported to the configuration package, including the business objects processed and details about errors that occurred.

Import Your Setup

Import your setup into the target instance of Order Management.

1. Sign into the target instance of Order Management with administrative privileges.

2. In the Navigator, click Setup and Maintenance.

3. On the Setup page, click Tasks > Manage Configuration Packages.

4. On the Manage Configuration Packages page, in the search results, click the row that contains the configuration package you must update.

5. In the Export and Import Processes area, click Import Setup Data.

6. On the Enter Basic Information page, accept default values, then click Next.

7. On the Select Pauses for External Import page, click Submit.

   The import process.

   • Adds setup data that doesn't already exist in the target configuration package. It adds setup data from the source configuration package into the target configuration package.

   • Updates setup data that already exists in the target package with modifications from the source package.

   • Doesn't delete existing setup.

   • Doesn't modify setup that exists in the target instance but not in the source instance.

8. Restart the server that hosts the target instance.

Deploy Flexfields

You must deploy each flexfield that you import.

Get details.

• How to handle objects that aren't flexfields after the import, see the Importing and Exporting Setup Data section in Implementing Common Features for Oracle SCM Cloud on Oracle Help Center.

• Flexfields, see the Deploy Extensible Flexfields in Order Management topic.

Deploy flexfields.

1. In the Setup and Maintenance work area, go to the task.

   • Offering: Order Management

   • Functional Area: Orders

   • Task: Manage Order Extensible Flexfields

2. On the Manage Order Extensible Flexfields page, identify each flexfield where the deployment status isn't Deployed, then deploy it.

3. Repeat steps 1 and 2 on each of these pages, as necessary.

   • Manage Item Revision Descriptive Flexfields

   • Manage Units of Measure Descriptive Flexfields

   • Manage Item Descriptive Flexfields

   • Manage Item Revision Descriptive Flexfields

   • Manage Item Relationship Descriptive Flexfields

   • Manage Trading Partner Item Descriptive Flexfields

   • Manage Catalog Descriptive Flexfields

   • Manage Category Descriptive Flexfields

   • Manage Source System Descriptive Flexfields

   • Manage Order Descriptive Flexfields

   • Manage Pricing Descriptive Flexfields

4. Sign into Oracle Enterprise Manager.

   For details about Oracle Enterprise Manager, see https://www.oracle.com/technetwork/oem/enterprise-manager/overview/index.html.

5. In the navigation tree, select SOA Infrastructure, then click UpdateSOAMDS.

6. On the UpdateSOAMDS page, set values.

   Attribute	Description
   Operation	Set to updateDuring.
   Value This Value attribute resides in a row in the Input Arguments area, in Tree View. The value for Name in the row is *payload, and the Type is duration.	Specify the time frame that has elapsed since the last time you deployed the flexfields. Use this format. PXMYD where X. Number of months that have elapsed. Y. Number of days that have elapsed. For example, if one month and one day have elapsed since the last time you deployed flexfields, then use this format. P1M1D You can specify only the month, only the days, or months and days.

7. Run the UpdateSOAMDS composite to synchronize SOA (Service Oriented Architecture) with flexfields in Order Management.

8. In Order Management, in the Navigator, click Scheduled Processes.

9. On the Scheduled Processes page, click Schedule New Process, then run the Publish Extensible Flexfield Attributes scheduled process.

• Deploy Extensible Flexfields

• Export Setup Data Using Implementation Project

• Import Setup Data Using Implementation Project

Reference for Copying Setup Data Between Instances of Order Management

Get the details you need when you copy setup data between instances of Order Management.

Collect Reference Data and Transaction Data for Order Orchestration and Order Promising

The order orchestration and planning data repository includes the data that Order Management needs to orchestrate sales order fulfillment and that Global Order Promising needs to promise sales orders. Use data from your source system or from an Oracle Fusion source system to populate the repository.

Specify the source system and maintain data collection parameters for the source system. Collect data from applications.

Application	Description
Order Management	Collect data. Oracle Fusion data. Including nonproduct and noncustomer reference entities for validation and cross-reference Order capture codes Accounts receivable codes Accounting terms and currencies Miscellaneous
Global Order Promising	Collect data. Existing supply, including on-hand, purchase orders, and work orders Capacity, including supplier capacity and resource capacity Related demands, including work order demands and work order resource requirements Planned supply, including planned buy and make orders Reference data, including calendars, transit items, and routing

You must refresh Global Order Promising after you collect data to make sure it uses the data you most recently collected.

Use pages in the Setup and Maintenance work area to manage source systems and collect data.

Page	Description
Manage Orchestration Source Systems	Manage an orchestration source system and collection parameters so you can use it to collect data.
Manage Orchestration Data Collection Processes	Manage orchestration reference data from other source systems. Specify whether to enable cross-referencing for various entities, such as Currencies, Units of Measure, and so on.
Review Orchestration Collected Data	Examine the data that you collected from other source systems for order orchestration.
Manage Planning Source Systems	Manage planning source systems and collection parameters so you can use it to collect data.
Manage Planning Data Collection Processes	Manage planning data from a source system.
Review Planning Collected Data	Examine the data that you collected from other source systems.
Monitor Planning Data Collection Process	Monitor the planning data collection work that's currently running or that completed.

For details, see these books on Oracle Help Center.

• Implementing Order Management

• Implementing Supply Chain Planning

• Using Order Promising

Copy Other Setup Data

Use set ups to copy your setup data from a source instance of Order Management to a target instance of Order Management.

Setup	Description
Item Setup	Export and import a configuration package to copy item setup data, such as item organization, item class, item catalog, item category, item lifecycle phase, and so on. Use item interface tables to copy items, item structures, and item relationships. Use the Import Items page and Monitor Item Imports page to manage item imports.
Party Setup	Export, then import a configuration package to copy party setup data, such as party relationship type, party classification, geography lookup, trading community source system, and so on. Use party interface tables to copy parties. Use the Import Persons and Organizations page to manage party imports.
Security Setup	Use commands in Lightweight Directory Access Protocol (LDAP) to copy job roles. For assumptions, prerequisites, and procedures, see Moving Security Artifacts in the Identity Store in Oracle Fusion Applications Administrator Guide.

Get More Documentation

See these books to get details about copying your setup data.

• Implementing Common Features for Oracle SCM

• Configuring and Extending Applications

• Using Order Promising

• Using Product Master Data Management

Search for these article Ids on My Oracle Support at https://support.oracle.com.

• Article Id 1334059.1 (Oracle Fusion PIM, Pros and Cons of Item Import Methods and Performance Considerations)

• Article Id 1279983.1 (Oracle Fusion PIM, Importing Data into PIM Hub, Generic Examples of Steps)

• Article Id 1299158.1 (Example SQL To Import Items into Oracle Fusion Product Information Management Using Open Interface Tables)

• Article Id 1393229.1 (Oracle Fusion PIM, Item Import, Example SQL Code Scripts)

• Article Id 1334525.1 (Oracle Fusion PIM: Explanation of Fields in ADFdi Template for Structure Import)

• Article Id 1383922.1 (Oracle Fusion Trading Community Bulk Import)

Business Objects You Can Export and Import

Specify business objects when you copy setup data for Order Management between configuration packages.

Supply Chain Management Family

Export and import business objects in the Supply Chain Management family.

Application	Page	Description	Business Object
Advanced Supply Chain Planning	Manage Enterprise Scheduler Jobs for Advanced Planning Applications	Manage Oracle Enterprise Scheduler jobs and their list of values sources for Advanced Planning applications, such as Global Order Promising.	Enterprise Scheduler Job List of Values Source
Advanced Supply Chain Planning	Manage Global Order Promising Profile Options	Manage profile options and values to control Oracle Fusion Global Order Promising, such as page display defaults or timeout parameters.	Application Profile Value
Order Management	Generate Constraint Package	Create a dynamic package that activates new validation rule sets for processing constraints.	Orchestration Change Constraint
Order Management	Manage Constraint Entities	Manage the entities to use when applying constraints.	Orchestration Change Constraints Object
Order Management	Manage Enterprise Scheduler Jobs for Order Orchestration	Manage jobs for Oracle Enterprise Scheduler and the sources that these jobs use for lists of values in Order Management.	Enterprise Scheduler Job List of Values Source
Order Management	Manage Hold Codes	Manage the abbreviations that Order Management uses to hold processing for a sales order or order line.	Orchestration Hold Code
Order Management	Manage Jeopardy Priorities	Manage score codes that indicate the severity of the delay of a task.	Orchestration Jeopardy Priority
Order Management	Manage Jeopardy Thresholds	Manage jeopardy threshold definitions that determine the degree of action to take when orchestration highlights potential or actual fulfillment issues because of delays.	Orchestration Jeopardy Threshold
Order Management	Manage Orchestration Attachment Categories	Manage attachment categories that group messages together.	Application Attachment Category
Order Management	Manage Orchestration Descriptive Flexfields	Manage validation and display properties of descriptive flexfields for order orchestration. Use descriptive flexfields to add modified attributes to entities.	Application Descriptive Flexfield
Order Management	Manage Orchestration Extensible Flexfields	Manage properties of extensible flexfields to extend attributes of transactional entities for orchestration. Use extensible flexfields to collect multiple contexts in the same flexfield.	Application Extensible Flexfield
Order Management	Manage Order Lookups	Manage lookup values for order orchestration, such as Return Reason Code or Activity Type.	Application Standard Lookup
Order Management	Manage Orchestration Process Definitions	Manage definitions that specify how to perform orchestration processing.	Orchestration Process
Order Management	Manage Orchestration Profiles	Manage profile definitions to specify how orchestration processes data.	Application Profile Value
Order Management	Manage Order Attributes That Identify Change	Manage the attributes necessary to identify changes in each sales order.	Orchestration Change Attribute
Order Management	Manage Processing Constraints	Manage the rules that control attempted changes to order orchestration.	Orchestration Change Constraint
Order Management	Manage Status Values	Manage status values for tasks.	Orchestration Status Code
Order Management	Manage Task Status Conditions	Manage the process status conditions that indicate when the process uses a status. Specify these conditions when you define the orchestration process.	Orchestration Status
Order Management	Manage Task Types	Manage the task types that group tasks and services for status management, jeopardy, orchestration processes, and run time behavior.	Orchestration Task
Global Order Promising	Manage Order Promising Server Profile Options	Manage profile option settings and values to control Oracle Order Promising Server, such as setting the sourcing assignment set or enabling an external ATP Web service.	Application Profile Value
Inventory Management	Manage Enterprise Scheduler Jobs for Logistics Common Applications	Manage Oracle Enterprise Scheduler jobs and their list of values sources for Logistics Common Components.	Enterprise Scheduler Job List of Values Source
Inventory Management	Manage Units of Measure	Manage units of measure that your organization uses to identify the quantity of an item.	Unit of Measure Unit of Measure Class Unit of Measure Interclass Conversion Unit of Measure Intraclass Conversion
Product Model	Create Catalog	Create an item catalog, and add attachments and images.	Item Catalog, Item Category
Product Model	Manage Enterprise Scheduler Jobs for Product Management Common Applications	Manage Oracle Enterprise Scheduler jobs and their list of values sources for Product Management Common Components.	Enterprise Scheduler Job List of Values Source
Product Model	Manage Default Catalogs	Manage catalog assignments for functional areas.	Functional Area Item Catalog
Product Model	Manage Default Item Class	Manage the root item class.	Item Class
Product Model	Manage Item Organizations	Manage item organization structures to use in standalone application deployments with Oracle Fusion Product Model. Each structure contains details about the parent item, components, attachments, and descriptive elements.	Item Organization
Product Model	Manage Key Flexfield for Catalogs	Manage key flexfield segments for each catalog and the validation to use for the catalog classification key. You must define the catalog key flexfield to make sure Oracle Fusion Product Model works as expected.	Application Key Flexfield
Product Model	Manage Lifecycle Phases	Manage the phases of each item lifecycle.	Item Lifecycle Phase
Supply Chain Management Common Components	Manage Data Security Policies	Manage grants of entitlement for each user or role on an object or attribute group according to a condition.	Application Data Security Policy

Common Family

Export and import business objects in Oracle Middleware Extensions for Applications in the Common family.

Page	Description	Business Object
Manage Administrator Profile Values	Manage profile option settings and values to control application behavior.	Application Profile Value
Manage Applications Core Administrator Profile Values	Manage profile option settings and values to control Oracle Middleware Extensions for Applications behavior.	Application Profile Value
Manage Applications Core Attachment Categories	Manage attachment categories for Oracle Middleware Extensions for Applications.	Application Attachment Category
Manage Applications Core Attachment Entities	Manage attachment entities for Oracle Middleware Extensions for Applications.	Application Attachment Entity
Manage Applications Core Descriptive Flexfields	Manage descriptive flexfields for Oracle Middleware Extensions for Applications.	Application Descriptive Flexfield
Manage Applications Core Messages	Manage messages for Oracle Middleware Extensions for Applications.	Application Message
Manage Applications Core Profile Categories	Manage categories to group profile options in Oracle Middleware Extensions for Applications according to their functional area. Use categories to search for related profiles and to define data security rules.	Application Profile Category
Manage Applications Core Profile Options	Manage profile options that affect Oracle Middleware Extensions for Applications behavior, and specify the levels at which they can be set.	Application Profile Value
Manage Applications Core Standard Lookups	Manage lookup values for Oracle Middleware Extensions for Applications.	Application Standard Lookup
Manage Applications Core Value Sets	Manage value sets for Oracle Middleware Extensions for Applications.	Application Flexfield Value Set
Manage Attachment Categories	Manage categories for attachments for security purposes.	Application Attachment Category
Manage Attachment Entities	Manage the default repository folders to use when storing attachments for each application entity.	Application Attachment Entity
Manage Common Lookups	Manage lookups that are common across applications and used in the common lookup views.	Application Common Lookup
Manage Currencies	Manage ISO standard currencies.	Application Reference Currency
Manage Data Security Policies	Manage grants of entitlement to each user or role on an object or attribute group according to a condition.	Application Data Security Policy
Manage Descriptive Flexfields	Manage segments, validation, and display properties of descriptive flexfields that you use to store details about an enterprise that Order Management doesn't typically store.	Application Descriptive Flexfield
Manage Document Sequence Categories	Manage categories that group documents for sequencing purposes.	Application Document Sequence Category
Manage Document Sequences	Manage document sequences to create an audit trail that identifies the application that created the transaction.	Application Document Sequence
Manage Extensible Flexfields	Manage segments, validation, and display properties of extensible flexfields that you use to store details about an enterprise that Order Management doesn't typically store.	Application Extensible Flexfield
Manage Industries	Manage ISO industries.	Application Reference Industry
Manage ISO Languages	Manage ISO languages.	Application Reference ISO Language
Manage Key Flexfields	Manage key flexfield segments and validation. You must define most key flexfields so that the applications work as expected.	Application Key Flexfield
Manage Languages	Manage installed languages.	Application Reference Language
Manage Messages	Manage messages that you use in each application.	Application Message
Manage Natural Languages	Manage natural, spoken languages.	Application Reference Natural Language
Manage Profile Categories	Manage categories that group profile options according to functional area. Use categories to search for profiles and to define data security rules.	Application Profile Category
Manage Profile Options	Manage profile options that affect application behavior, and specify the levels at which they can be set.	Application Profile Value
Manage Reference Data Sets	Manage sets for separating and sharing reference data across organizations.	Application Reference Data Set
Manage Set Assignments for Set Determinant Type	Manage reference data set assignments to determine the type of set.	Application Reference Data Set Assignment
Manage Set Enabled Lookups	Manage lookups with codes that vary depending on the value of the reference data set determinant and are exposed in the set-enabled lookups view.	Application Set-Enabled Lookup
Manage Standard Lookups	Manage lookups that are common across applications and used in the lookups view.	Application Standard Lookup
Manage Taxonomy Hierarchy	Manage the hierarchy of functional units that make up Oracle Fusion Applications, from product families and applications to functional components.	Application Taxonomy
Manage Territories	Manage ISO territories.	Application Reference Territory
Manage Time Zones	Manage time zones.	Application Reference Time Zone
Manage Tree Labels	Manage the labels to use as tags for tree nodes.	Application Tree Label
Manage Tree Structures	Manage tree structures to group common business rules for a family of trees.	Application Tree Structure
Manage Trees and Tree Versions	Manage trees to contain data in a hierarchy, allowing the user to group and consolidate details that already exist in an organization.	Application Tree
Manage Value Sets	Manage value sets to validate the content of a flexfield segment.	Application Flexfield Value Set
Register Descriptive Flexfields	Register the existence of descriptive flexfields on a table.	Application Descriptive Flexfield
Set Activity Stream Options	Set options that determine the types of activities to display in the Activity Stream regions in Oracle Fusion Applications.	Application Activity Stream Configuration

Business Intelligence Family

Export and import business objects in the Transactional Business Intelligence application in the Business Intelligence family.

Page	Description	Business Object
Configure Descriptive Flexfields for Transactional Business Intelligence	Specify validation and display descriptive flexfield properties for Transactional Business Intelligence. Use descriptive flexfields to add modified attributes to entities.	Application Descriptive Flexfield
Configure Key Flexfields for Transactional Business Intelligence	Specify the key flexfield segments and validation to use as classification keys for Transactional Business Intelligence. You must specify these flexfields so Transactional Business Intelligence works as expected.	Application Key Flexfield

Customer Relationship Management Family

Export and import business objects in the Customer Relationship Management family.

Application	Page	Description	Business Object
Marketing	Manage File Import Mappings	Manage mappings between columns in a source file in a source system and columns in a staging table in Order Management. Use these mappings when you import business objects, such as sales leads, customers, contacts, or sales catalogs.	File Import Mapping
Marketing	Manage File Import Objects	Manage business objects, such as sales leads and opportunities, that you can import from a file.	File Import Object
Trading Community Model	Enable Click to Dial	Enable automated dialing when clicking a phone number.	Application Profile Value
Trading Community Model	Manage Geography Lookups	Manage lookup values that provide choices related to geographies, such as different ways to validate an address.	Application Standard Lookup
Trading Community Model	Manage Import Lookups	Manage lookup values that provide choices about data import batch processing, such as batch status, batch identifier, batch configuration, or process status.	Application Standard Lookup
Trading Community Model	Manage Source System Descriptive Flexfields	Manage fields the user can use to enter details. Validate descriptive flexfields according to values that the user enters in other areas of the page.	Application Descriptive Flexfield
Trading Community Model	Manage Source System Entities	Manage entity associations for source systems. For example, use one source system to import customer data, and use another to import customers and contacts.	Trading Community Original System Mapping Trading Community Source System
Trading Community Model	Manage Source System Lookups	Manage lookup values that provide choices related to the source system model, such as original system type.	Application Standard Lookup
Trading Community Model	Manage Trading Community Source Systems	Manage the source system for a trading community.	Examine and define the types of information imported for each source system

Human Capital Management Family

Export and import business objects in the Human Capital Management family.

Application	Page	Description	Business Object
Global Human Resources	Manage Enterprise HCM Information	Manage details about the enterprise, such as details about the default work day.	Enterprise
Global Human Resources	Manage Locations	Manage locations for your enterprise. For example, create the locations where people work or the locations of your external organizations.	Location
HCM Configuration Workbench	Review Enterprise Configuration	Examine a functional summary or a detailed technical inventory of all objects.	Enterprise Configuration

Financials Family

Export and import business objects in the Financials Common Module application in the Financials family.

Page	Description	Business Object
Manage Business Unit	Manage details about enterprise units to provide a consistent entity so you can control and report on transactions, and to share reference data sets across applications.	Business Unit, Business Unit Detail
Manage Business Unit Set Assignment	Manage reference data that represents business rules and policies. Assign this data to business units.	Business Unit Set Assignment

ATF Family

Export and import business objects in the Application Toolkit application in the ATF family.

Page	Description	Business Object
Manage Help Security Groups	Manage security groups that you associate with help to determine who can access it. Associate each group with a duty role. This page creates lookup codes, database resource conditions, and data security policies that you can edit.	Application Data Security Policy Application Standard Lookup
Map Reports to Work Areas	Select the reports that display in the Reports and Analytics area in Oracle Fusion Applications work areas.	Reports and Analytics Mapping
Set Help Options	Set options for help features, such as collaboration, access to external web sites, settings for modified help content, or access to an Oracle User Productivity Kit library.	Help Configuration Help Topic
Set Watchlist Options	Specify the Watchlist categories and items that are available at your site.	Watchlist User and Site Preference

Governance Risk and Compliance Family

Export and import business objects in GRC Application Access Controls Governor application of the Governance Risk and Compliance family.

Page	Description	Business Object
Manage Application Access Controls	Manage rules and resolve issues regarding access in an application.	Governance Risk and Compliance Setup Configuration
Manage Application Configuration Controls	Manage rules and resolve issues regarding configurations in an application.	Governance Risk and Compliance Setup Configuration
Manage Application Preventive Controls	Manage rules regarding how users interact in an application.	Governance Risk and Compliance Setup Configuration
Manage Application Transaction Controls	Manage rules and resolve issues regarding transactions in an application.	Governance Risk and Compliance Setup Configuration