Quick Start for Setting Up Order-to-Cash

Do the minimum steps needed to set up Oracle Order Management 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 Guidelines for Setting Up Order-to-Cash.

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 and set up Global Order Promising.

  6. 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 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 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

Get a list of the tasks you might need to do. For details, see Securing SCM.

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

This topic uses predefined job roles. You must create your own job roles, depending on your security requirements. For details, see Privileges That You Need to Implement Order Management.

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 Set Up User Roles and Privileges in Order Management.

  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 job roles that are specific to Order Management.

    Role

    Name

    Job

    Order Entry Specialist

    Job

    Order Manager

    Job

    Order 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

    For details, see Privileges That You Need to Implement Order Management.

Set Up Organizations and Items, 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 Product Information Management 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 What's an item organization? and How can I create items in both master and child organizations?.

  2. Set up your units of measure.

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

  4. Use an order import template to import the items that your test orders will reference. Transform orders, as necessary. For details, see Import Orders Into Order Management.

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.

    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, go to Implementing Receivables Credit to Cash, then search for Data Import for Customers and Consumers.

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 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 Oracle Trading Community Architecture User Guide.

  • 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 Collect Planning Data for Order Management and Set Up Promising Rules 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 parameters according to your testing requirements.

    For details, see Manage Order Management Parameters.

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

  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 Manage Processing Constraints.

    • 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 start with Overview of Orchestration Processes and Use Order Profiles to Control Order Management Behavior.

  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, Overview of Oracle Pricing.

    In addition, it might be necessary to:

    • Set up the Item Validation Organization parameter.

    • Get the privileges that 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 section that starts with Overview of Drop Ship in Order Management.

Internal Material Transfer

Internal Material Transfers comes predefined as available. The predefined job roles provide access to this feature, but you must set up your own job roles. You can set an option in Supply Chain Orchestration that determines whether inventory routes the transfer order to Order Management. For details, see Overview of Supply Chain Orchestration.

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 your customer.

For details, see Overview of Back-to-Back Fulfillment.

Configure to Order

Use Configure to Order to efficiently fulfill each configured item. Here are the parameters that 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 Modeling Configurations for SCM and Manage Order Management Parameters.

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 the sections that start with:

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 section that starts with Overview of Connecting Order Management to Your Fulfillment System.