Guidelines for Setting Up Order-to-Cash

Estimate Effort Required to Set Up Features

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

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 need the privileges 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
Advance 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.

Go to the Setup and Maintenance work area, then select the Order Management offering.
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 Implementing Common Features for Oracle SCM.
In the Functional Areas list, click Orders.
In the Orders area, click Required Tasks > All Tasks.
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.

Go to the Setup and Maintenance work area.
On the Setup page, click Tasks > Edit Implementation Projects.
On the Implementation Projects page, click Actions > Create.
On the Create Implementation Project page, modify the attribute values, as necessary, then click Next.
On the Select Offerings to Implement page, in the Name list, expand Order Management.
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.
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	Get Details
Collection Job Set	You collect organization information from your source system.	Collect Data section in Quick Start for Setting Up Order-to-Cash
Refresh and Start the Order Promising Server	Updates the Global Order Promising data.	Set Up Global Order Promising section in Quick Start for Setting Up Order-to-Cash
Load Interface File for Import Import Sales Orders 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.	Indicate an Ownership Change During Drop Ship
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.	Update or Close Fulfillment Lines That Remain Open
Generate Constraint Packages	Constrain the changes that your users can make.	Manage Processing Constraints
Publish Extensible Flexfield Attributes	Publish and deploy an extensible flexfield.	Guidelines for Setting Up Extensible Flexfields in Order Management
Plan Orchestration Processes	Update an orchestration process plan at regular intervals according to the frequency that your deployment requires.	Guidelines for Setting Up Orchestration Processes
Release Pause Tasks	Release a pause task so processing can continue.	Pause Orchestration Processes for Events 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
Update Sales Order Search Indexes	Keep your implementation running smoothly.	-
Import AutoInvoice. For details, see Update Intercompany Receivables Invoice Import Details.	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 Receivables.	Create One Invoice for Sales Orders with Items That Can and Can't Ship

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.

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 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 you click Submit, set the filter for Constraint Entity to Order Line.
- After you click Submit, set the filter for Constraint Entity to Order Fulfillment Line.
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.
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.
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.

Consider Which Licenses You Need

You need different licenses to access different set up tasks. For example, you need one license to set up Oracle Financials and a different license to set up Oracle CX Sales. Learn how to get the licenses that you need. For details, see Whom To Contact For Licensing Queries? (Doc ID 1391957.1).