Oracle Order Management Setup

This chapter covers the following topics:

Overview of Setup

This chapter explains how to set up and implement Oracle Order Management. The Oracle Order Management Application provides many flexible features enabling you to set up your system to begin processing order information. You must define your business order policies, such as how you classify your orders, as well as various control features prior to processing orders within the application.

Please refer to the Oracle Applications Multiple Organizations Implementation Guide for more information on setting up multi-org access control.

In addition to reading this chapter, please refer to the Using Oracle Workflow in Oracle Order Management manual for setup and implementation details for Order Management workflows.

Setup Steps

Oracle Order Management Recommended Implementation

Implementation involves several phases, including setting up other integrated applications, which include Multi-Org Access Control (MOAC), Oracle General Ledger, Oracle Receivables, and Oracle Inventory. Some setup steps are optional, depending on whether you have the integrating applications installed and whether you use the associated feature. For example, if your business supports drop shipments, you should also set up Oracle Purchasing. If you sell models and kits, set up Oracle Bills of Material and Oracle Configurator.

If you are using a multiple organization structure, your system administrator must set the parameter OM: Item Validation Organization. This enables Order Management to default code and revenue account information accurately.

Set Up Oracle Applications Technology

The setup steps in this chapter tell you how to implement the parts of Oracle Applications specific to Oracle Order Management. This includes:

Also, if your product uses Oracle Workflow, for example, to manage the approval of business documents or derive Accounting flexfield values via the Account Generator, you need to set up Oracle Workflow.

Order Management Setup Steps

The following table displays a list of all the implementation steps for Oracle Order Management and a reference to documentation that can help to accomplish the steps.

Step Document Optional or Required
1. Define multiple organizations in Oracle Inventory Oracle Inventory User's Guide required
2. Setup Multi-Org (Multiple Organization) Access Control Oracle Applications Multiple Organizations Implementation Guide optional
3. Define key and descriptive flexfields Oracle Order Management Implementation Manual required under certain conditions
4. Define inventory organizations (warehouses), parameters, subinventories, and picking rules in Oracle Inventory Oracle Inventory User's Guide required
5. Define Profiles Oracle Order Management Implementation Manual required
6. Setting OM System Parameters Oracle Order Management Implementation Manual required
7. Define invoicing information Oracle Order Management UserGuide required under certain conditions
8. Define your sales representatives Oracle Receivables Implementation Guide optional
9. Define Tax Features Current, Oracle Receivable's User's Guide required
10. Define Quickcodes Oracle Order Management Implementation Manual required under certain conditions
11. Define header and line processing flows Oracle Order Management required
12. Define Document Sequences for Order Numbering Oracle Order Management Implementation Manual required
13. Define Order Import Sources Oracle Order Management Implementation Manual required under certain conditions
14. Define the units of measure Oracle Inventory User's Guide required
15. Define item information Oracle Inventory User's Guide required
16. Define the items that you sell Oracle Inventory User's Guide required
17. Define the configurations that you sell Oracle Bills of Material User's Guide required under certain conditions
18. Define price lists Oracle Advanced Pricing Implementation Manual required
19. Define customer profile classes Oracle Receivables Implementation Guide required under certain conditions
20. Define information on your customers Oracle Receivables Implementation Guide required
21. Define item cross references current, Oracle Inventory User's Guide required under certain conditions
22. Define your sourcing rules Oracle Advanced Planning and Scheduling User's Guide optional
23. Define Order Management Transaction Types Oracle Order Management Implementation Manual required
24. Set up Cost of Goods Sold Accounting flexfield combination Order Inventory User's Guide required under certain conditions
25. Define Processing Constraints Oracle Order Management Implementation Manual optional
26. Define Defaulting Rules Oracle Order Management Implementation Manual optional
27. Define Credit Checking Rules Oracle Order Management Implementation Manual required under certain conditions
28. Define Automatic Holds Oracle Order Management Implementation Manual required under certain conditions
29. Define Attachments Oracle Order Management Implementation Manual optional
30. Define Freight and Special Charge Types Oracle Order Management Implementation Manual optional
31. Set up User Defined Attributes Oracle Order Management Implementation Manual optional
32. Define shipping parameters Oracle Shipping Execution User's Guide required
33. Define Repricing Preferences Oracle Order Management User's Guide optional

Setup Steps Defined in Detail

The following is a list of each setup step defined in detail.

Step 1: Multiple Organizations

Define multiple organizations in Oracle Inventory. This step is required.

Step 2: Multi-Org Access Control

The Multi-Org Access Control (MOAC) feature enables users to access to one or more Operating Units within one user responsibility. Please refer to the Oracle Applications Multiple Organizations Implementation Guide for more information.

Step 3: Flexfields

Define key and descriptive flexfields to capture additional information about orders and transactions.

This step is required for Key Flexfields, and optional if you plan on using the functionality surrounding Descriptive Flexfields. Several defaulting values are provided.

Step 4: Inventory Organizations

Define inventory organizations (warehouses), parameters, subinventories, and picking rules in Oracle Inventory.

You must define at least one item validation organization and at least one organization that acts as an inventory source for orders fulfilled internally. If you plan to drop ship some orders, you must also define at least one logical organization for receiving purposes. Your item validation organization can be the same as your inventory source or your logical receiving organization, but you cannot use one organization for all three purposes. See Step 5 for setting your item validation organization.

This step is required.

Step 5: Profile Options

Define profile options to specify certain implementation parameters, processing options, and system options.

This step is required.

Step 6: Parameters

Set your Order Management System Parameters to validate items, enable customer relationships, and operating unit defaults.

This step is required.

Step 7: Invoicing

Define invoicing information, including payment terms, invoicing and accounting rules, Autoaccounting parameters, territories, and invoice sources.

This step is required if you plan on transferring invoicing information to Oracle Receivables. Several defaulting values are provided.

Step 8: Salespersons

Define information on your sales representatives.

This step is optional.

Step 9: Tax

Define tax features, such as codes, rates, exceptions, and exemptions.

This step is required.

Step 10: QuickCodes

Define QuickCodes that provide custom values for many lists of values throughout Order Management.

This step is required if you plan on creating user defined Quickcodes for utilization within Order Management. Defaulting values are provided.

Step 11: Workflow

Define header and line processing flows to meet different header and line type requirements.

This step is required.

Step 12: Document Sequences (Order Numbering)

Define Document Sequences for automatic or manual numbering of orders.

This step is required.

Step 13: Order Import Sources

Define sources for importing orders into Order Management.

This step is required if you plan on importing orders or returns into Order Management.

Step 14: Units of Measure

Define the units of measure in which you supply items.

This step is required.

Step 15: Item Information

Define item information, including item attribute controls, categories, and statuses.

This step is required.

Step 16: Items

Define the items that you sell, as well as container items.

This step is required.

Step 17: Configurations

Define the configurations that you sell.

This step is required if you plan on generating orders or returns for configured items. Several defaulting values are provided.

Step 18: Pricing

Define price lists for each combination of item and unit of measure that you sell. Optionally, you can define pricing rules and parameters to add flexibility.

For more information about pricing setup and implementation, refer to the Oracle Advanced Pricing Implementation Manual.

This step is required.

Step 19: Customer Classes

Define customer profile classes.

This step is required if you plan on using the functionality surrounding Customer Profiles. Several defaulting values are provided.

Step 20: Customers

Define information on your customers.

This step is required.

Step 21: Item Cross References

Define item cross references for ordering by customer part number, UPC, or any generic item number.

This step is required if you plan on using the functionality surrounding item cross referencing. Several defaulting values have been provided.

Step 22: Sourcing

Define your sourcing rules for scheduling supply chain ATP functions.

This step is optional.

Step 23: Order Management Transaction Types (Sales Documents)

Define Order Management transaction types to classify sales documents. For each order type, you can assign a default price list, defaulting rules, order lines, return lines, line types, workflow assignments, payment terms, and freight terms.

Note: Order Management provides NO seeded OM transaction types. For existing Oracle Order Entry customers, Order Management will update existing Order Types to OM transaction type during the upgrade process.

This step is required.

Step 24: Cost of Goods Sold (COGS)

Set up your Cost of Goods Sold Accounting Flexfield combination (COGS Account) in Oracle Inventory.

This step is required if you plan on utilizing the functionality surrounding COGS. Optionally, you can change the default revenue event line for ATO model for the COGS functionality (DCOGS to COGS transfer process). In the custom hook API 'oe_cogs_extension.get_revenue_event_line' (extension of group API 'OE_COGS_GRP.get_revenue_event_line'), write the logic to return appropriate revenue line ID. If the hook does not return a value, then the application uses the default logic to derive the revenue line ID.

Step 25: Processing Constraints

Define processing constraints to prevent users from adding updating, deleting, splitting lines, and cancelling sales documents information beyond certain points in your business flows. Use the constraints Order Management provides, which prevent data integrity violations, or create your own.

This step is optional. Several default values for processing constraints have been defined.

Step 26: Defaulting Rules

Define defaulting rules to determine the source and prioritization for defaulting order information to reduce the amount of information you must enter manually in the Sales Orders window.

This step is optional. Several Defaulting rules and corresponding values for have been defined.

Step 27: Credit Checking

Define your credit checking rules.

This step is required if you plan on performing any type of order credit checking.

Step 28: Holds

Define automatic holds to apply to orders and returns.

This step is required if you plan on performing automatic hold for orders or returns.

Step 29: Attachments

Define standard documents to attach automatically to sales documents.

This step is optional.

Step 30: Freight Charges and Carriers

Define freight charges and freight carriers to specify on orders.

This step is required if you plan on charging customers for freight or additional order charges.

Step 31: Setting up User Defined Attributes

Using user defined attributes (UDA), define additional information that you can record at order and line levels

This step is optional.

Step 32: Shipping

Define shipping parameters in Oracle Shipping Execution.

This step is required.

Step 33: Define Repricing Preferences

Define repricing preferences to add attributes from a list of attributes provided and setup whether that attribute can trigger repricing.

This step is optional.

For more information on how to define repricing preferences, see Repricing Preferences Procedure in the Order Management User's Guide.

Oracle Training Administration Users

Please refer to the Oracle Training Administration User's Guide for additional Order Management Setup Steps.

Oracle Process Manufacturing Users

Please refer to the Oracle Process Manufacturing guides for additional Order Management Setup Steps.

Related Documents

  1. Oracle Shipping Execution User's Guide

  2. Oracle Inventory User's Guide

  3. Oracle Receivables User Guide

  4. Oracle Receivables Implementation Guide

  5. Oracle Receivables Reference Guide

  6. Oracle Bills of Material User's Guide

  7. Oracle Order Management User's Guide

  8. Oracle Applications Multiple Organizations Implementation Guide

  9. Using Oracle Training Administration

Related Topics

Holds and Releases

Profile Options

Setting OM System Parameters

Define Credit Checking Rules

Credit Checking

Define Defaulting Rules

Defaulting Rules

Define Processing Constraints

Processing Constraints

Define Order Management Transaction Types

Transaction Types

Setting up the Supply Chain

Setting Up Basic Pricing

Order Import

Define Document Sequences for Order Numbering

Using Workflow in Order Management

Define QuickCodes

Multi-Org Access Control

Please refer to the Oracle Applications Multiple Organizations Implementation Guide for general MOAC setup details.

To support Multi-Org Access Control the Operating Unit has been added to many of the Order Management windows. If you are enabling MOAC functionality for your implementation and you want to give your users the ability to enter and search sales order documents across Operating Units then you need to enable (make the field visible) the Operating Unit field in the various Order Management forms that are folder enabled.

It is recommended that the Operating Unit field should be the first visible field on a form, or the first field before an Operating Unit sensitive field. To make the hidden Operating Unit field visible in OA Framework (HTML) pages, you need to use the OA Framework Personalization feature.

The windows / OA pages where the Operating Unit is seeded as hidden:

The Order Management windows where the Operating Unit is added as visible:

In the windows where the Operating Unit can be specified, the list of values for the Operating Unit field is determined by the profile MO: Security Profile. The field will have a default value based on the profile MO: Default Operating Unit. For details on MOAC setup please refer to the Oracle Applications Multiple Organizations Implementation Guide.

Profile Options

During implementation, you set a value for each user profile option to specify how Order Management controls access to and processes data. This is step four of the Order Management Setup Steps.

Generally, the system administrator sets and updates profile values. See: Setting Profile Options, Oracle E-Business Suite Setup Guide.

Profile Categories

Profile options have been categorized so that they can be easily classified or grouped. This table displays the profile categories and the profile options that belong to each one. Some profile options belong to more than one category and are indicated in the table below.

Profile Category Name Profile Option(s)
Configurations OM: Allow model fulfillment without configuration
OM: Configuration Quick Save
OM: Copy Model dff to child lines
OM: Enable Configuration UI for RMA
OM: Included Item Freeze Method
OM: Party Totals Currency
OM: Use Configurator
Customer Usage OM: Add Customer
OM: Add Customer (Order Import)
OM: Create Account Information
OM: E-Mail Required on New Customers
OM: Party Totals Currency
OM: Sales Order Form: Restrict Customers
Debug OM: Debug Log Directory
OM: Debug Level
OM:Generate Diagnostics for Error Activities
Deployment OM: New EDI Acknowledgment Framework
OM: Orders Archival Per Commit
OM: Orders Purge Per Commit
OM: Printed Document Extension Class Name
OM: Use Configurator
Electronic Messaging OM: Change SO Response Required
OM: Electronic Message Integration Event Sources
OM: New EDI Acknowledgment Framework
OM: Order Accept State for XML
OM: Run Order Import for XML
OM: Send Acknowledgment for Change PO Response
Forms UI OM: Add Customer
OM: Administer Public Queries
OM: Automatically Open Related Items Window
OM: Contact Center Actions Menu Name
OM: Cust Item Shows Matches
OM: Display Actions Button vs. Poplist
OM: Display Current Selections in Pricing/Availability
OM: Enable Related Items and Manual Substitutions
OM: Item View Method
OM: Quick Sales Order Form: Auto Refresh
OM: Quick Sales Order Form: Defer Pricing
OM: Sales Order Form: Cascade Header Changes to Line
OM: Sales Order Form: Refresh Method (Query Coordination)
OM: Sales Order Form: Restrict Customers
OM: Sales Order navigation from Pricing/Availability form
OM: Sales Orders Form preference
OM: Scheduling Role
OM: Show Line Details
OM: Show Process Messages Flag
OM: Use Configurator
OM: Use Item Orderability Custom Hook
OM: View Cancel Lines
OM: View Closed Lines
OM: View Pricing & Availability Information in Related Items
Fulfillment OM: Allow model fulfillment without configuration
OM: Automatically Interface Lines to IB on Fulfillment
OM: Default Fulfillment Base
OM: Included Item Freeze Method
OM: Over Return Tolerance
OM: Over Shipment Tolerance
OM: Line Set for Promotional Items
OM: Population Of Buyer Code For Dropship Lines
OM: Source Code
OM: Under Return Tolerance
OM: Under Shipment Tolerance
OM: Use Materialized View for Items LOV (Honours Item Orderability Rules)
Holds OM: Modify Seeded Holds
OM: Prevent Booking for Line Generic Holds
Invoicing OM: Interface freight tax code from line
OM: Invoice Numbering Method
OM: Set Receivables Transaction Date as Current Date for Non-Shippable Lines
OM: View Intercompany AR Invoice
Item Usage OM: Cust Item Shows Matches
OM: Enable Related Items and Manual Substitutions
OM: Item Flexfield
OM: Restrict Customer Items for Line Level Ship To Address
Logistics OM: Sequence for TP Ship/Deliver Deadline
OM: Source for TP Early Ship/Deliver Date
Order Import OM: Add Customer (Order Import)
OM: Import Multiple Shipments
OM: Order Lines Threshold For Large Order Processing in Order Import
OM: Unique Order Source, Orig Sys Document Ref Combination For Each Customer
Payments OM: Commitment Sequencing
OM: Credit Card Privileges
OM: Preserve External Credit Balances
Portal UI OM: Customer Service Feedback
OM: Customer Service Report Defect
OM: Records On Summary Page For External Users
Pricing OM: Charges For Backorders
OM: Charges for included item
OM: Charging Privilege
OM: Discounting Privileges
OM: Display Qualified Ask for Modifiers (See: Setting up Non-Seeded Profiles, Oracle Advanced Pricing Implementation Guide)
OM: Enable Group pricing for DSP lines
OM: Enable Repricing Preferences
OM: Item Change Honors Frozen Price
OM: List Price Override Privilege
OM: Negative Pricing
OM: Price Adjustment Modifier for AIA Order Lines
OM: Price Adjustment Modifier for Reference RMA
OM: Price Adjustment Modifier for Spreadsheet Order Lines
OM: Price Included Items
OM: Promotion Limit Violation Action
OM: Send Changed Lines to Pricing
OM:Unit Price Precision Type
OM: UOM Class for Charge Periodicity
Returns OM: Customer Service Feedback
OM: Customer Service Report Defect
OM: Notification Approver
OM: Over Return Tolerance
OM: Return Item Mismatch Action
OM: Return Unfulfilled Referenced Line Action
OM: Under Return Tolerance
Scheduling OM: Assign New Set For Each Line
OM: Authorized To Override ATP
OM: Auto Push Group Date
OM: AutoSchedule
OM: Bypass ATP
OM: Enforce Shipping Method for Ship Sets
OM: Schedule ATO Item Without BOM
OM: Scheduling Role
Security OM: Add Customer
OM: Add Customer (Order Import)
OM: Administer Public Queries
OM: Authorized To Override ATP
OM: Cascade Service
OM: Charging Privilege
OM: Create Account Information
OM: Credit Card Privileges
OM: Discounting Privileges
OM: List Price Override Privilege
OM: Modify Seeded Holds
OM: Scheduling Role
OM: Send Notifications of Internal Order Change
Service OM: Cascade Service
Tax OM: Delayed Tax Calculation
Transaction Entry OM: Apply Automatic Attachments
OM: Cascade Service
OM: Configuration Quick Save
OM: Copy Model dff to child lines
OM: Default Blanket Agreement Type
OM: Default Blanket Transaction Phase
OM: Default Line Type from Model
OM: Default Sales Transaction Phase
OM: Default Salesrep
OM: Display New Order After Copy
OM:Enforce check for duplicate Purchase Orders
OM: Generic Update Constraints Apply to DFF?
OM: Prevent Booking for Line Generic Holds
OM: Return Item Mismatch Action
OM: Return Unfulfilled Referenced Line Action
Upgrade OM: Context Responsibility for Upgraded Orders
OM: Notification Approver

Implementing Profile Options Summary

The following table indicates whether you can view or update the profile options and the System Administrator level at which the profile options can be viewed and updated: Site, Application, Responsibility, or User. The short names and definitions used in the tables are described as follows:

Value Definition
User User level
SA User System Administrator: User level
SA Resp System Administrator: Responsibility level
SA App System Administrator: Application level
SA Site System Administrator: Site level
Yes You can update the profile option.
No You cannot change the profile option value.
Req? (Required)

  • Required (Req.): Requires you to provide a value for the profile option.

  • Optional: (Opt.) Already provides a default value, so you must change it only if you do not want to accept the default.

For the profile options table below, the following codes are used to denote profile options used within Order Management that are defined within other Oracle Applications. See the appropriate User Guide for additional details.

Profile Options
Profile Option User SA User SA Resp. SA App. SA Site Req? Default Value Profile Category
OM: Add Customer View Only Yes Yes - default is None Yes Yes - default is None Req NULL Customer Usage, Security, Forms UI
OM: Add Customer (Order Import) View Only Yes Yes Yes Yes Opt NULL Customer Usage, Security, Order Import
OM: Administer Public Queries No Yes Yes Yes Yes Req No Forms UI, Security
OM: Allow Model Fulfillment Without Configuration No No No No Yes Opt No Fulfillment, Configurations
OM: Allow Standard ATO Items as PTO/Kit Included Components No No No No Yes Opt No None
OM: Apply Automatic Attachments View Only No Yes Yes Yes Opt Yes Transaction Entry
OM: Assign New Set For Each Line No No No No Yes Opt NULL Scheduling
OM: Authorized to Override ATP View Only Yes Yes No Yes Opt NULL Scheduling, Security
OM: Automatically Interface Lines to IB on Fulfillment No No No No Yes Opt Yes Fulfillment
OM: Automatically Open Related Items Window Yes Yes Yes Yes Yes Opt No Forms UI
OM: Auto schedule View Only No Yes No Yes Opt NULL Scheduling
OM: Auto Push Group Date View Only No Yes No Yes Opt NULL Scheduling
OM: Bypass ATP No Yes Yes No Yes Opt Null Scheduling
OM: Cascade Service View Only View Only View Only Yes Yes Opt Null - equivalent to Yes Service, Transaction Entry
OM: Change SO Response Required View Only View Only View Only View Only Yes     Electronic Messaging
OM: Charges for Backorders View Only No No No Yes Opt NULL Pricing
OM: Charges for included item View Only No No No Yes Opt NULL Pricing
OM: Charging Privilege View Only Yes Yes Yes Yes Opt NULL Pricing, Security
OM: Commitment Sequencing No No No No Yes Opt No Payments
OM: Configuration Quick Save No No No No Yes Opt No Transaction Entry, Configurations
OM: Contact Center Actions Menu Name View Only Yes Yes Yes Yes No ONT_CONTACT_CENTER_SUB_MNU Forms UI
OM: Context Responsibility for Upgraded Orders View Only View Only Yes View Only View Only Opt No Default Upgrade
OM: Copy Model DFF To Child Lines No No No Yes Yes Opt No Transaction Entry, Configurations
OM: Create Account Information View Only Yes Yes Yes Yes Opt None Customer Usage, Security
OM: Credit Card Privileges View Only View Only Yes Yes Yes Opt None Payments, Security
OM: Credit Check Notification Recipient View Only Yes Yes Yes Yes Opt None None
OM: Cust Item Shows Matches View Only No Yes No Yes     Item Usage, Forms UI
OM: Customer Service Feedback View Only Yes Yes Yes Yes Opt NULL Returns, Portal UI
OM: Customer Service Report Defect View Only Yes Yes Yes Yes Opt N Returns, Portal UI
OM: Debug Level Yes Yes Yes Yes Yes Opt 0 Debug
OM: Debug log Directory View No Yes Yes Yes Opt NULL Debug
OM: Default Sales Transaction Phase Yes Yes Yes No Yes   NULL Transaction Entry
OM: Default Blanket Agreement Type No No Yes No Yes Opt NULL Transaction Entry
OM: Default Blanket Agreement Transaction Phase Yes Yes Yes No Yes Opt NULL Transaction Entry
OM: Default Fulfillment Base No No No No Yes No No value Fulfillment
OM: Default Line Type from Model No No No No No Req Yes Transaction Entry
OM: Default Salesrep Yes Yes Yes Yes Yes Opt NULL Transaction Entry
OM: Delayed Tax Calculation Yes Yes Yes Yes Yes No No Tax
OM: Discounting Privileges No Yes Yes Yes No Opt NULL Pricing, Security
OM: Display Actions Button vs. Pop list Yes Yes Yes Yes Yes Yes Button Forms UI
OM: Display Current Selections in Pricing and Availability Yes Yes Yes Yes Yes Opt No Forms UI
OM: Display New Order After Copy Yes Yes Yes Yes Yes Opt No Transaction Entry
OM: Electronic Message Integration Event Sources View Only View Only View Only View Only Yes   XML Electronic Messaging
OM: E-Mail Required On New Customers View Only No No No Yes Opt No Customer Usage
OM: Enable Configuration UI for RMA View Only No No No Yes Opt No Configurations
OM: Enable Group Pricing for DSP Lines View Only Yes Yes Yes Yes     Pricing
OM: Enable Related Items and Manual Substitutions View Only Yes Yes Yes Yes Opt No Item Usage, Forms UI
OM: Enable Repricing Preferences No No No No Yes Opt Null - equivalent to No Pricing
OM: Enforce Check For Duplicate Purchase Order View Only Yes Yes Yes Yes Req Yes Transaction Entry
OM: Enforce Shipping Method for Ship Sets No No No No Yes Opt NULL Scheduling
OM: Generate Diagnostics for Error Activities View Only No No No Yes No No Debug
OM: Generic Update Constraints Apply to DFF? View Only No No No Yes Opt NULL Transaction Entry
OM: Import Multiple Shipments Yes Yes Yes Yes Yes Opt Null - equivalent to No Order Import
OM: Included Item Freeze Method View Only No No No Yes Req NULL Fulfillment, Configurations
OM: Interface Freight Tax Classification Code From Line No No No No Yes Opt No Invoicing
OM: Invoice Numbering Method No No No No Yes Req Automatic Invoicing
OM: Item Change Honors Frozen Price View Only Yes Yes Yes Yes Opt NULL Pricing
OM: Item Flexfield No No No No Yes Req System items Item Usage
OM: Item View method Yes Yes Yes Yes Yes Opt NULL Forms UI
OM: Line Set for Promotional Items No No No No Yes Opt NULL Fulfillment
OM: List Price Override Privilege No Yes Yes No No Opt NULL Pricing, Security
OM: Modify Seeded Holds Internal Use Only Internal Use Only Internal Use Only Internal Use Only Internal Use Only Internal Use Only Internal Use Only Holds, Security
OM: Negative Pricing View Only No No Yes Yes Opt NULL Pricing
OM: New EDI Acknowledgment Framework No Yes Yes Yes Yes Opt No Deployment, Electronic Messaging
OM: Notification Approver View Only Yes Yes Yes Yes Opt NULL Upgrade, Returns
OM: Order Accept State For XML View Only View Only View Only View Only Yes Opt Null - equivalent to Entered Electronic Messaging
OM: Order Lines Threshold For Large Order Processing in Order Import No Yes Yes Yes Yes Opt Null Order Import
OM: Orders Archival Per Commit View Only No No No Yes Opt 100 Deployment
OM: Orders Purge Per Commit View Only No No No Yes Opt 100 Deployment
OM: Over Return Tolerance View Only No No No Yes Req 0 Returns, Fulfillment
OM: Over Shipment Tolerance View Only No No No Yes Req 0 Fulfillment
OM: Party Totals Currency View Only No No No Yes Req US Dollars Customer Usage
OM: Population Of Buyer Code For Dropship No No No No Yes Opt NULL Fulfillment
OM: Preserve External Credit Balances No No No No Yes Yes Yes Payments
OM: Prevent Booking for Line Generic Holds No No No No Yes Opt NULL Holds, Transaction Entry
OM: Price Adjustment Modifier for AIA Order Lines No No No No Yes Opt NULL Pricing
OM: Price Adjustment Modifier for Reference RMA View Only No No No Yes Yes NULL Pricing
OM: Price Adjustment Modifier for Spreadsheet Order Lines No No No No Yes Yes Blank Pricing
OM: Price Included Items VIew Only No No No Yes No Yes Pricing
OM: Printed Document Extension Class Name View Only No No No Yes Opt NULL Deployment
OM: Promotion Limit Violation Action View Only No No No Yes Opt NULL Pricing
OM: Quick Sales Order Form: Auto Refresh Yes Yes Yes Yes Yes Opt Application Forms UI
OM: Quick Sales Order Form: Defer Pricing Yes Yes Yes Yes Yes Opt No Forms UI
OM: Raise Status Change Business Event View Only No No No Yes Opt Null None
OM: Records on Summary Page for External Users Yes Yes Yes Yes Yes Opt NULL Portal UI
OM: Restrict Customer Items for Line Level Ship To Address No No No No Yes Opt NULL Item Usage
OM: Return Item Mismatch Action View Only Yes Yes Yes Yes Opt NULL Returns, Transaction Entry
OM: Return Unfulfilled Referenced Line Action View Only Yes Yes Yes Yes Opt NULL Returns, Transaction Entry
OM: Run Order Import for XML View Only View Only View Only View Only Yes Opt NULL Electronic Messaging
OM: Sales Order Form: Cascade Header Changes to Line No Yes Yes View Only View Only Opt Null Forms UI
OM: Sales Order Form Preference Yes Yes Yes Yes Yes Opt Sales Orders Forms UI
OM: Sales Order Form: Refresh Method (Query Co-ordination) Yes Yes Yes Yes Yes Opt Null - equivalent to Automatic Refresh with Repositioning of Cursor Forms UI
OM: Sales Order Form: Restrict Customers View Only View Only Yes Yes Yes Opt Global Forms UI, Customer Usage
OM: Sales Order Navigation From P&A form Yes Yes Yes Yes Yes Opt ASK Forms UI
OM: Schedule ATO Item Without BOM No No No No Yes Opt No Scheduling
OM: Scheduling Role No Yes Yes No No Opt NULL Scheduling, Forms UI, Security
OM: Send Acknowledgment for Change PO Response View Only View Only View Only View Only Yes Opt Null - equivalent to No Electronic Messaging
OM: Send Changed Lines to Pricing View Only No No No Yes Opt Yes Pricing
OM: Send Notifications of Internal Order Change View Only Yes Yes Yes Yes Yes Null Security
OM: Sequence for TP Ship/Deliver Deadline No No No No Yes Opt Null Logistics
OM: Set Receivables Transaction Date as Current Date for Non-Shippable lines View Only No No No Yes Opt No Invoicing
OM: Show Line Details Yes Yes Yes Yes Yes Opt NULL Forms UI
OM: Show Process Messages Flag Yes Yes Yes Yes Yes Opt NULL Forms UI
OM: Source Code No No No No Yes Req ORDER ENTRY Fulfillment
OM: Source for TP Early Ship / Deliver Date No No No No Yes Opt NULL Logistics
OM: Use Configurator No No No No Yes Opt Yes Deployment, Forms UI, Transaction Entry, Configurations
OM: Use Item Orderability Custom Hook No No No No Yes No NULL - equivalent to No Forms UI
OM: Use Materialized View for Items LOV (Honours Item Orderability Rules) No No No No Yes Yes No Fulfillment
OM: Under Return Tolerance View Only No No No Yes Req 0 Returns, Fulfillment
OM: Under Shipment Tolerance View Only No No No Yes Req 0 Fulfillment
OM: Unique Order Source, Orig Sys Document Ref Combination For Each Customer View Only View Only View Only View Only Yes Opt NULL Order Import
OM: Unit Price Precision Type Yes Yes Yes Yes Yes Opt NULL Pricing
OM: UOM Class For Charge Periodicity View Only View Only View Only View Only Yes     Pricing
OM: View Cancel Lines Yes Yes Yes Yes Yes Opt Yes Forms UI
OM: View Closed Lines Yes Yes Yes Yes Yes Opt Yes Forms UI
OM: View Intercompany AR invoice Yes Yes Yes Yes Yes Opt No Invoicing
OM: View Pricing/Availability Information in Related Items Yes Yes Yes Yes Yes Opt Both Forms UI
AR: Credit Limit Selection (AR) No No Yes Yes Yes      
AR: Item Flexfield Mode (AR) Yes Yes Yes Yes Yes Req NULL  
AR: Use Invoice Accounting for Credit Memos (AR) View Only Yes Yes Yes Yes Req No  
HZ: Generate Contact Number (AR) Yes Yes Yes Yes Yes Req NULL - equivalent to Yes  
HZ: Generate Party Number (AR) Yes Yes Yes Yes Yes Req NULL - equivalent to Yes  
HZ: Generate Party Site Number (AR) Yes Yes Yes Yes Yes Req NULL - equivalent to Yes  
Tax: Allow Ad Hoc Tax Changes (AR) View Only Yes Yes Yes Yes Req NULL  
Tax: Allow Manual Tax Lines (AR) View Only Yes Yes Yes Yes Req NULL  
EBTax: Allow Override of Customer Exemptions (AR) View Only Yes Yes Yes Yes Req NULL  
Tax: Allow Override of Tax Classification Code (AR) View Only Yes Yes Yes Yes Req NULL  
Tax: Calculate Tax on Credit Memos (AR) View Only No Yes Yes Yes Opt NULL  
Tax: Use Tax PL/SQL Vendor (AR) View Only No Yes Yes Yes   No  
Tax: Use Tax Vendor (AR) View Only No Yes Yes Yes Req No  
BOM: Check for Duplicate Configuration (BOM) View Only No No No Yes Opt No  
BOM: Component Item Sequence Increment (BOM) Yes Yes Yes Yes Yes Opt 10  
BOM: Configurator URL of UI Manager (BOM) Yes Yes Yes Yes Yes Req    
BOM: Default Bill of Material Levels (BOM) Yes Yes Yes Yes Yes Opt No  
Sequential Numbering (FND) View Only No Yes Yes Yes Req    
Default Country (FND) Yes Yes Yes Yes Yes Req NULL  
Flexfields: Open Descr Window (FND) Yes Yes Yes Yes Yes Opt Yes  
Journals: Display Inverse Rate (GL) Yes Yes Yes Yes Yes Opt At site level  
INV: Capable to Promise (INV) Yes Yes No No Yes Opt NULL  
OKC: Enable Sales Contracts (OKC) No No No Yes Yes Opt NULL  
QP: Accrual UOM Class (QP) View Only No No Yes Yes Opt No Default  
QP: Blind Discount Option (QP) View Only No No Yes Yes Req Yes  
QP: Item Validation Organization (QP) View Only No Yes No Yes Req No Default  
QP: High Volume Order Processing Compliance (QP) No No No No Yes      
QP: Line Volume UOM Code (QP) View Only No No Yes Yes Opt No Default  
QP: Line Weight UOM Code (QP) View Only No No Yes Yes Opt No Default  
QP: Negative Pricing (QP) View Only No No Yes Yes Req No Default  
QP: Return Manual Discounts (QP) Yes Yes Yes Yes Yes      
QP: Source System Code (QP) No No No Yes Yes Req No Default  
QP: Unit Price Precision Type (QP) No No No Yes Yes Req Standard  
QP: Verify GSA Violations (QP) No No No No Yes Req No  
WSH: Internet Proxy URL (WSH) Yes No No No No Opt NULL  

Order Management Profile Option Descriptions and Settings

OM: Add Customer

ONT_ADD_CUSTOMER

This profile option determines the users that can access the Order Management Add Customer window to enter customers, customer addresses, and customer contact information. Select from:

The default for this profile option is None.

Note: You cannot update existing customer information from the Add Customer window. However, if the e-mail address field is NULL for a customer and/or customer contact, you can update these fields.

Note: Oracle Trading Community Architecture provides a model for managing information about entities such as customers. The TCA Data Sharing and Security (DSS) feature enables you to define rules around who can create, update or delete customer data. For more information, see Oracle Trading Community Architecture Administration Guide.

OM: Add Customer (Order Import)

ONT_ADD_CUSTOMER_OI

This profile option determines the users that can create new customers and customer details when importing orders using the Order Import concurrent program. Select from:

The default for this profile option is None.

Note: Oracle Trading Community Architecture provides a model for managing information about entities such as customers. The TCA Data Sharing and Security (DSS) feature enables you to define rules around who can create, update or delete customer data. For more information, see Oracle Trading Community Architecture Administration Guide.

OM: Administer Public Queries

ONT_ADMINISTER_PUBLIC_QUERIES

This profile option determines which responsibility is able to create and update public queries within Order Management windows.

OM: Allow Standard ATO Items as PTO/Kit Included Components

ONT_HON_ATO_FOR_INC

This profile option enables ATO items to be processed as included/mandatory items in PTO Models and KITs. If the value of the profile option is set to Yes, then the application treats and fulfills ATO items that are part of a KIT as ATO items. If the value of the profile option is set to No, then the application treats the ATO items that are part of a KIT as standard included items. The default value of the profile option is No and if you do not set any value for this profile, then the application considers it as No. You can set this profile option only at the site level.

OM: Apply Automatic Attachments

OE_APPLY_AUTOMATIC_ATCHMT

This profile option determines whether rule-based attachments are applied without user intervention.

OM: Allow Model Fulfillment Without Configuration

ONT_ALLOW_MODEL_FULFILL_WITHOUT_CONFIG

In order to enable you to progress model lines which do not have child lines attached, the profile option OM: Allow Model Fulfillment without Configuration has been introduced. When you set this profile option to Yes, you are allowed to progress the model line and not wait at fulfillment any longer, even if you do not have a child line attached to it. If you set this profile option to No, which is the default value, the current functionality will be carried out: the model line will get fulfilled only if it does not have any child lines attached to it. If the model line is not configured, i.e. if it does not have any child lines attached to it, then the model line waits at fulfillment thus giving the user a chance to configure the model.

OM: Assign New Set For Each Line

ONT_SET_FOR_EACH_LINE

The default is set to “N” which creates one Ship/Arrival set per order. If the profile is set to Yes and the Line Set field on the order header is specified, the application:

The application creates and assigns set information for split standard lines, ATO Models, PTO Models, Kits, and Hybrid Models as follows:

If an order line is split into multiple lines, then the application assigns each split line with a distinct set. For example, if a standard line is split into four lines, then the application assigns each of the split lines with a distinct set. If a model (ATO/PTO/KIT/Hybrid) is split into multiple models, then the application assigns the top model line of each split model a distinct ship set and cascades the same set information to the associated classes, options, configs, and included items. Since the remnant split lines are assigned new sets, the set operations are enabled on such eligible lines. In the remnant part of a PTO Model/ Hybrid Model/KIT, the set operations are enabled on:

Note: This profile is not applicable for Services (Extended Warranty and Subscription).

OM: Authorized to Override ATP

ONT_OVERRIDE_ATP

This profile option controls which responsibilities or users have the authority to perform the ATP override. If YES, then the user or responsibility can override the ATP Schedule Date. Null is interpreted as No. This can be set at the site, responsibility, or user level.

OM: Automatically Interface Lines to IB on Fulfillment

ONT_AUTO_INTERFACE_LINES_TO_IB

This profile option enables you to control the interfacing of non-shippable items to Install Base (IB). The default value is Yes and if you have not set any value for this profile, then the application assumes the value to be Yes. The value Yes ensures that all non-shippable lines that reach fulfillment are automatically interfaced to IB. If you set No as the value, then the non-shippable items are not interfaced to IB automatically.

OM: Automatically Open Related Items Window

ONT_OPEN_RELATED_ITEMS

This profile option allows the user who does high volume up-selling and cross-selling to have the Related Items window open automatically for all items which have relationships defined. Options are Yes or No (default).

OM: Auto Push Group Date

ONT_AUTO_PUSH_GRP_DATE

This profile option controls scheduling when a new line is inserted into an existing set. If the new line cannot be scheduled on the same date as the rest of the set, this profile is used. Select from:

This profile option can be overridden for a parameter specific to customers or customer sites by setting a value in the Customer window.

The default is NULL.

OM: AutoSchedule

ONT_AUTOSCHEDULE

This profile option determines the default setting for autoscheduling orders, and also controls the display of the Availability window within the Sales Order Lines window. Please note that autoscheduling orders is only supported for orders that contain standard line items, not models or kits.

Select from:

The Line Generic workflow process sequences the line scheduling action to occur after you book the order. However, even if you have set this profile option to No and you indicate ship set or arrival set on a order line, the order entry processing schedules the line and sets the Visible Demand Flag.

To group lines into ship sets and arrival sets, order entry processing uses the warehouse, scheduled shipment date, ship to location, shipment priority, and shipment method. Therefore, it schedules the order lines with ship set values to obtain scheduled shipment date.

If you want the Line Generic workflow process to schedule an order line, you cannot specify a ship set or arrival set for it.

OM: Bypass ATP

ONT_BYPASS_ATP

If you are using a third planning system or do not want to call the ATP system, then set this profile value as Yes to check for availability. You can set it at Site and Responsibility levels.

OM: Cascade Service

ONT_CASCADE_SERVICE

If set to No, services will not be automatically cascaded from model to its options. When a service is added to a model, depending on the profile value the application will or will not automatically cascade the service to the options.

OM: Change SO Response Required

This profile option determines if a response is required to an outbound Change SO XML message. If a response is required, the order is put on hold until a response is received from the customer.

OM: Charges for Backorders

ONT_CHARGES_FOR_BACKORDERS

This profile option controls the setting of the Calculate Price Flag when backorder lines are created.

Select from the following values:

Depending on how you have set up the modifier for freight charges with a pricing phase and an associate pricing event, the application applies freight charges as follows when a partial quantity is shipped:

OM: Charges for included item

ONT_CHARGES_FOR_INCLUDED_ITEM

This profile option determines if Order Management will calculate and return charges for included items. The profile option setting does not control the pricing of included items, only the calculation and return of charges associated with an order line containing an included item.

Select from:

OM: Charging Privilege

OE_CHARGING_PRIVILEGE

This profile option controls your ability to manually apply freight and special charges on an order or order line.

Select from:

OM: Configuration Quick Save

ONT_CONFIG_QUICK_SAVE

This profile option determines how Order Management will save option or model class lines for unbooked sales orders from within the Sales Order window only.

If you set this profile option to Y, class lines will be saved by a direct database insert call with a minimum of order line defaulting values, unless the value of the Order Management profile option OM: Included Item Freeze Method is set to Entry. If the value of OM: Included Item Freeze Method is set to Entry, you cannot perform direct database inserts of model or class order lines with a minimum of defaulting.

OE: Commitment Balance Checking

OE_COMMITMENT_BAL_CHECK

This profile option is obsolete and no longer used by Order Management.

OM: Commitment Sequencing

OE_COMMITMENT_SEQUENCING

This profile option determines whether or not Oracle Order Management calculates and stores the amount of the line that can be paid using the commitment, and if commitments will be applied in Oracle Receivables in the same sequence that they are applied in Order Management. Select from:

OM: Contact Center Actions Menu Name

ONT_AGENT_ACTION_PROFILE

Agent actions are defined as functions. Depending on the functions that have been mapped to menus, the corresponding associated agent actions are available from the Line Items sub-tab page. This profile option holds the name of that menu. The default value will be the value of the Order Management seeded menu 'ONT_CONTACT_CENTER_SUB_MNU'.

OM: Context Responsibility for Upgraded Orders

OE_RESP_FOR_WF_UPGRADE

This profile option is used to flag certain responsibilities to be used when setting the applications context for deferred activities for upgraded orders and order lines. It is used for customers who are upgrading and only needs to be set if a user, who has created orders, (created_by column in Order Management schema) has multiple responsibilities that point to a single operating unit.

This profile option can only be set at the Responsibility level.

OM: Copy Model DFF to child lines

This profile option enables copying of all flexfields to the lines from the model line. Context sensitive flexfields are more popular; you may not want the same flexfields copied to all the child lines of a model. The default value is No. Set this parameter to 'Yes' in order for the values to copy.

OM: Create Account Information

ONT_CREATE_ACCOUNT_INFORMATION

This profile option is used to set the user's permissions to create accounts, sites, and contacts. It can be set at the Site, Application, Responsibility, and User levels.

The seeded profile values are:

The default value is None.

The Create Account Layer API will check this profile and create the account layer only if the user has the correct permissions. The calling application can pass a profile value to the API. It is useful if the calling application has already determined the user's privileges.

OM: Credit Card Privileges

ONT_CREDIT_CARD_PRIVILEGES

This profile option is used for controlling the entry of new credit card details, updating existing details, and allowing for manual authorization. The valid values for this profile option are Yes and No. This profile option has been modified, it's previous valid values were All, Limited and None and in the previous release, this profile option would additionally be used for controlling the card number display. The masking / display function for the credit card number is now controlled from Oracle Payments. Please visit Oracle Payments Implementation Manual for more details.

OM: Credit Check Notification Recipient

OE_CC_NTF_RECIPIENT

Use this profile option to specify the user or role assigned to users who will receive notifications when sales orders are placed on credit check hold. You can set this profile option value at Site, Application, Responsibility, and User levels. If you set the value to a user, then the applicable user receives the notification when the order is placed on credit check hold. If you set the value to a role, then the application sends the notification to all the users who are assigned to that particular role.

OM: Customer Service Feedback

ONT_FEEDBACK_PROFILE

This profile option indicates the Customer contact that a workflow notification will be sent to for RMA requests entered via the Order Information Portal. The values for the LOV for this profile option is all users defined to Oracle Applications via the System Administrator responsibility having no customer contacts.

The default for this profile option is Null.

OM: Customer Service Report Defect

ONT_REPORTDEFECT_PROFILE

This profile option indicates the Customer contact that will receive a workflow notification for any Report Defects submitted via the Order Information Portal. The values for the LOV for this profile option is all users defined to Oracle Applications via the System Administrator responsibility having no customer contacts.

The default for this profile option is Null.

OM: Default Blanket Transaction Phase

ONT_DEF_BSA_TRANSACTION_PHASE

Used for defaulting transaction phase (Negotiation/Fulfillment) on sales agreements. You can set this profile only at site, responsibility, and user level.

OM: Default Fulfillment Base

ONT_DEFAULT_FULFILLMENT_BASE

Set Yes as the value at Site level to enable order fulfillment based on the shipped quantity in secondary UOM of the item (secondary shipped quantity). Once the profile is set, the application can determine the fulfillment option based on the ordered, primary, and secondary UOMs of the Item. The application does not populate the fulfillment base field in the Shipping tab on the Sales Order window if you set the value as No or do not select any value. If you set the value to Yes, then Order Management does not calculate the shipped quantity and accepts the values passed by Oracle Shipping Execution. Shipping calculates the shipped quantities at the time of splitting delivery details and backordering, considering the picked and shipped quantities for a delivery detail.

This profile option enables Advanced Catch-Weight. For further information, see My Oracle Support Note 1551171.1 - 'Advanced Catch-Weight Solution in Oracle E-Business Suite Applications'

OM: Default Line Type from Model

This profile is end dated and no longer in use.

OM: Debug Level

ONT_DEBUG_LEVEL

This profile option is used to store debug messages to assist in problem identification. The OM: Debug profile option controls which debug messages get written to the debug log based on their assigned level. The directory to be specified for this profile must be a database directory defined for PL/SQL file I/O for the application database instance. See My Oracle Support Knowledge Document 2525754.1, Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2.

Assigning a value greater than 0 or NULL causes debugging to be turned on. The value of this option determines the level of debug messages printed within a log file. For example, if OM: Debug Level has a current value of 3, all debugging messages with a level of 0.5, 1, 2 or 3 will be spooled out to the debug log.

Values for this profile option are:

If you set this profile option to a value other than NULL, system performance may be affected, because creating and updating a debug log is a task that will consume a lot of system resources as you enter higher debug levels.

Order Management recommends you set this profile option only if you are attempting to gather additional details for unexpected application issues and then reset the value back to NULL after you have gathered the necessary debug details.

The default for this profile option is NULL.

OM: Debug Log directory

OE_DEBUG_LOG_DIRECTORY

This profile option determines the default directory used to store log file outputs when performing Order Management debugging. The specified value must be listed as one of the directories provided in the UTL_FILE_DIR database initialization parameter.

OM: Default Sales Agreement Type

OE_DEFAULT_BLANKET_ORDER_TYPE

This profile is the first preference to default the transaction phase, negotiation or fulfilment on Sales Agreements. This profile can be setup only at the responsibility and site level.

OM: Default Sales Agreement Transaction Phase

ONT_DEF_BSA_TRANSACTION_PHASE

This profile defaults the order type to generate sales agreement number. This profile can be setup only at the responsibility and site level.

OM: Default Salesrep

ONT_DEFAULT_PERSON_ID

This profile defaults the dummy sales representative for a Telesales Order. The Telesales team will pass the salesrep_id for the order if that information is available in the eBusiness Center. If no sales representative is passed to the Sales Orders window, then Order Management will default the sales representative value from this profile setup in Order Management. Integration with TeleSales is available with a TeleSales license.

OM: Default Sales Transaction Phase

ONT_DEF_TRANSACTION_PHASE

A default source for the transaction phase on the Quote Sales Order. The default is null for negotiation and fulfillment.

OM: Delay Scheduling

When the value of this profile option is set to Yes, then the scheduling of a line is performed only when the changes made are committed to the database, as opposed to simply navigating out of the line record.

OM: Delayed Tax Calculation

ONT_DELAY_TAXING

This profile option enables you to improve the time taken for tax calculation. If the profile option is set to Yes, then the application does not calculate tax when you navigate from a line after entering the line without saving it; it calculates tax when you save the line(s). If can keep on adding multiple lines without calculating tax for every line as the application calculates tax of all lines and header when you save all the lines. If the profile option is set to No, then the application calculates tax for every line while navigating from the line. The default value of the profile option is No.

OM: Discounting Privilege

ONT_DISCOUNTING_PRIVILEGE

This profile option provides the choice of controlling user's ability to apply discounts on an order or order line.

Select from:

OM: Display Actions Button vs. Poplist

Controls whether the traditional button for Actions or a pop list will be used to display available Actions. Values are: Button and Pop list. The default value is Button for backward compatibility.

Note: This profile option is only designed for the Order Information, Line Items, and Price Summary tabs in the Contact Center window. If you open the Sales Order or Quick Sales Order windows directly or from the Contact Center window, then the application displays the Actions button and not the pop list.

OM: Display Current Selections in Pricing and Availability

ONT_PANDA_DISPLAY

Yes or No - default is No. Determines whether or not to show the saved selections section of the P&A form

OM: Display New Order After Copy

You can choose to display the newly copied order depending on the value of this profile option. If the value of the profile option is set to Yes, the check box Display New Order after copy on the Copy Orders window (Quick Copy tab) will be selected and you can view an order that has been copied in the Sales Orders window. If the value of the profile option is set to No, the check box Display New Orders after copy will be unselected and the newly copied order will not display automatically in the Sales Orders window, you will need to query for it. However, you can override the selection of the check box Display New Order after Copy in the Copy window while copying.

OM: Electronic Message Integration Event Sources

ONT_EM_INTEG_SOURCES

Order Sources enabled for Integration Business Event. Based on the source, you can enable the History which will be maintained for that source in the Electronic Messaging history table.

OM: E-Mail Required on New Customers

ONT_MANDATE_CUSTOMER_EMAIL

This profile option determines whether the field E-mail address is required for any customer or customer contact you define within Order Management. Select from:

OM: Enable Configuration UI for RMA

The profile provides the option to configure PTO Models or Kits in RMAs that do not have a reference to a sales order. To enable this functionality, you must set the value as Yes. When the value in this profile option is set Yes:

When the OM: Enable Configuration UI for RMA profile value is Yes, after creating the configuration lines, the application marks them as 'remnant' and treats them as standard lines. This is consistent with the existing treatment of models and Kits in referenced RMAs.

OM: Enable Group Pricing For DSP Lines

ONT_GRP_PRICE_FOR_DSP

When demand interface appends order lines to an existing order, this profile option controls whether other unchanged order lines should be sent to the Pricing Engine for repricing. Setting this profile option to No improves demand interface performance. The default value is No. You should only set this profile option to Yes when you want your orders created by demand interface qualify for Promotional Goods, Other Item Discounts or other line group level modifiers defined in Advanced Pricing.

OM: Enable Related Items and Manual Substitutions

ONT_OPEN_RELATED_ITEMS

Values: Yes or No

Default Value: No

Usage: This option enables you to turn on Related Items. APS users should not turn on Related Items because the forecast demand consumption would be incorrect. Options are Yes or No (default).

Default Levels: Viewable and updatable at all levels.

OM: Enable Repricing Preferences

ONT_REPRICING_PREFERENCES

Values : Yes or No

Default Value: Null - equivalent to No

When you set the profile to Yes, setup done for the attributes in the Repricing Preferences page will trigger repricing accordingly. If this profile is set to null or to No, then any change to standard repricing attributes will trigger repricing automatically, irrespective of setup created in the Repricing Preferences page

For information on about the standard repricing attributes, see Repricing Preferences Procedure, Oracle Order Management User's Guide.

OM: Enforce Check For Duplicate Purchase Order

ONT_ENFORCE_DUP_PO

When this profile option is set to Yes or is blank, a check will be made to verify if the entered PO number is duplicate or not. It will display a warning if a duplicate number is found. When the profile option is set to No, a check to verify for duplicate PO number will not be carried out.

OM: Enforce Shipping Method for Ship Sets

ONT_SHIP_METHOD_FOR_SHIP_SET

Determines whether Shipping Method is a set attribute. If set to Yes, all lines in a set must have the same Shipping Method. Site level only.

OM: Estimated Authorization Validity Period

ONT_EST_AUTH_VALID_DAYS

This profile is no longer used . The associated functionality is now controlled by Oracle Payments. Please refer to the Oracle Payments Implementation Guide for more details.

OM: Generate Diagnostics for Error Activities

This profile determines whether the OM Standard Error Process with Retry workflow process automatically triggers the Diagnostics: OM Order Information concurrent program.

Possible values are No (default) or Yes

OM: Generic Update Constraints Apply to DFF?

This profile option determines whether you can update processing-constrained descriptive flexfield attributes on closed orders. There is a seeded processing constraint against updating closed order lines; this profile option does not control order line fields other than the flexfield attributes. Select from:

This profile option is updatable at the site level.

Regardless of this profile option, you can set up constraints specific to flexfield attribute constraints.

OM: Import Multiple Shipments

This profile option is used to import multiple shipments through the Order Import concurrent program. If you set the profile to Yes, then the Order Import concurrent program can create multiple shipments in the following two ways:

Note: To link the two lines for multiple shipment lines,split_from_line_ref and split_from_shipment_ref of the child line or split line respectively are populated with orig_sys_line_ref and orig_sys_shipment_ref of the parent line.

The uniqueness of the line record is determined using orig_sys_shipment_ref in combination with order_source_id, orig_sys_document_ref, and orig_sys_line_ref.

To create lines with multiple shipments or split lines, enter the following parameters for the Order Import process:

Order Import creates lines with multiple shipments, for example, 1.1, 1.2 when these interface fields are passed to the order line interface.

Note: The fields, line_number and shipment_number are optional.

OM: Included Item Freeze Method

ONT_INCLUDED_ITEM_FREEZE_METHOD

This profile option determines the date and time Order Management uses to determine when included items for a configuration's bill of material are added as lines on the order. Included items for a PTO Model/Class/Kit will also be exploded based on the profile option.

Select from:

Note: When the value of the profile option is Booking or Ready to Pick / Purchase Release, security-invoked behavior (Versioning, Audit Trail, Acknowledgements) will not take place.

OM: Interface freight tax classification code from line

ONT_TAX_CODE_FOR_FREIGHT

The default value set at site level is No (so that existing customers are not impacted due to the change). Tax_code is now interfaced to AR for freight lines that are interfaced as revenue lines when the profile is set to Yes. Tax code is populated in the same way as the sales order line along with which this freight line is interfaced.

OM: Invoice Numbering Method

WSH_INVOICE_NUMBERING_METHOD

This profile option determines whether or not the Invoicing activity generates invoice numbers based on the delivery name or automatically.

Select from:

OM: Item Change Honors Frozen Price

ONT_HONOR_ITEM_CHANGE

This profile option determines whether Order Management will change the value of calculate price flag when an item is changed on an unbooked order line.

Select from:

OM: Item Flexfield

OE_ID_FLEX_CODE

This profile option determines the structure of the Item Flexfield (System Items) used by Order Management. This structure should be the same across all applications in the same database.

OM: Item View Method

ONT_ITEM_VIEW_METHOD

This profile option determines the display method of data retrieved within the LOV for the Item field within the Order Management Options Window. Valid values are:

OM: Line Set for Promotional Items

OM_LINE_SET_FOR_PROMO_ITEMS

If the value of the profile option is Modifier Setup, pricing modifier setup will be referred for evaluation on an item to item basis, and the following scenarios may occur for all operating units:

OM: List Price Override Privilege

ONT_LIST_PRICE_OVERRIDE_PRIV

View Only is the default value. If set to this value, the current behavior is retained, which means unit list price field is protected. Unlimited Privilege: If set to this value, you can override the unit list price field from the main tab and immediately see selling price adjusted accordingly.

OM: Modify Seeded Holds

ONT_MODIFY_SEEDED_HOLDS

Internal Use Only. Enables you to modify seeded hold attributes. Options are Yes or No. The default is No or Null.

OM: Negative Pricing

ONT_NEGATIVE_PRICING

This profile option controls whether Order Management allows a negative list price or negative selling price to be determined by the Pricing Engine or to be entered as an override by a user on a sales order.

The profile option QP: Negative Pricing is used for price lists, and controls whether a negative unit price can be entered on a price list.

OM: New EDI Acknowledgment Framework

ONT_NEW_EDI_ACK_FWK

The new framework is used to generate EDI Acknowledgments. When this profile option is set to Yes, the derivation of the values for the ids for the EDI acknowledgement will be postponed. If you use EDI Transactions (855 and 856) and set this profile option to Yes, there will be better performance of the process order.

OM: Notification Approver

OE_NOTIFICATION_APPROVER

This profile option is used during upgrading Order Entry Order Cycle History to Order Management Workflow History.

This profile option can be optionally set. Valid values for this profile are based upon a Value Set that uses the seeded view WF_ROLES. The seeded Return Approval flow also sends approval notifications to the role set by this profile.

If the profile option is NULL, then notifications for this role value will go to the user SYSADMIN.

Note: The application retrieves the value for this profile option based on the applications context (User, Responsibility, Application) that was in effect when the transaction was created.

All upgraded approvals are sent to this role value of this Profile option.

OM: Order Accept State For XML

ONT_XML_ACCEPT_STATE

OM: Order Lines Threshold For Large Order Processing in Order Import

ONT_LARGE_ORDER_SIZE

This profile option indicates the minimum number of lines in an order that are considered for large order processing in Order Import. Any order that contains order lines greater than or equal to the value entered in this profile option is considered a large order.

The default is NULL.

The default value is NULL and it indicates that large order processing in Order Import is not being implemented.

OM: Orders Archival Per Commit

OM_ORDER_ARCHIVE_PER_COMMIT

This profile option determines how many orders the archival process must archive before saving it to the database.

OM: Orders Purge Per Commit

OM_ORDERS_PURGE_PER_COMMIT

This profile option determines how many orders the purge process should purge before performing a commit to the database.

OM: Over Return Tolerance

OM_OVER_RETURN_TOLERANCE

This profile option indicates the percentage by which a return line can be over-received. Any value greater than or equal to zero (0) is a valid value. This profile option is set at the site level. Default value is zero (0).

OM: Over Shipment Tolerance

OM_OVER_SHIPMENT_TOLERANCE

This profile option indicates the percentage by which an order line can be over-shipped. Any value greater than or equal to zero (0) is a valid value. This profile option is set at the site level. Default value is zero (0).

This profile is also applicable to Inbound Lines (RMA).

OM: Preserve External Credit Balances

ONT_PRESERVE_EXT_CR_BAL

If this is set to Yes, external exposure data is not deleted during Initialize Credit Summaries concurrent program. The value of the profile option can be Yes or No, Initialize Credit Summaries program will use to decide whether to use DELETE or TRUNCATE. The profile can be at site level, and the default value is Yes. With the default value, there will not be any change in behavior as the application will use delete and preserve external credit exposure. When this profile is set to 'No', application will truncate the table before populating the credit exposure.

OM: Price Adjustment Modifier for AIA Order Lines

ONT_O2C_MANUAL_MODIFIER

This profile option assumes significance in installations where you have configured Order Management to provide fulfillment services via Oracle Order To Cash Process Integration Pack.

If you are not implementing Order To Cash Process Integration Pack, then you need not set this profile. If you are implementing Oracle Order To Cash Integration pack, and in case your business scenarios include importing order lines with differing unit list price and unit selling price, then set this profile value to a manual, over-rideable, line level, amount based pricing modifier defined in Oracle Pricing. It may be noted that this modifier continues to be effective, irrespective of the date range specified on the modifier definition user interface.

OM: Price Adjustment Modifier for Reference RMA

ONT_RMA_MANUAL_MODIFIER

The OM: Price Adjustment Modifier for Reference RMA profile enables you to retain the original price on RMA lines, when you create it using the Copy functionality or with reference to an existing sales order line. The list of values of this system profile displays all the active line level, discount/surcharge, no currency, global, manual, overrideable, zero valued amount-pricing modifiers present on the system. This profile applies the price adjustment modifier that you select on the Return/RMA Order line to account for the difference between the USP and ULP only in the following case:

If you select no value, then Oracle Order Management retains the existing behavior on RMA lines, when you create it using the Copy functionality or with reference to an existing sales order line.

OM: Price Adjustment Modifier for Spreadsheet Order Lines

ONT_SPU_MANUAL_MODIFIER

This profile option enables the Spreadsheet orders processing in Order Management to apply a manual modifier, when the Unit  List Price and Unit Selling Price are different with Calculate Price Flag is Partial.

The list of values of this system profile option displays all the active line level, discount/surcharge, no currency, global, manual, overrideable, zero valued amount-pricing modifiers present on the system. This profile applies the price adjustment modifier on the Sales Order line created via Spreadsheet to account for the difference between the USP and ULP only in the following case:

If you select no value, then the Orders processed by Spreadsheet in Oracle Order Management creates order lines with the same Unit List Price, Unit Selling Price and Calculate Price Flag as Partial, as passed in the Spreadsheet, however there will be no modifier accounting for the difference.

OM: Price Included Items

ONT_PRICE_INCLUDED_ITEM

The site level system profile option OM: Price Included Items has two values. If the value is set to Yes, included items are priced and invoiced; also, charges on included items are calculated, regardless of the value of the profile option OM: Charges for Included Item.

OM: Party Totals Currency

OM_CUST_TOTAL_CURRENCY

This profile option determines the currency used by the Calculate Party Totals current program which sums order totals by Party. Order Management recommends that you set this profile option at the Site level only.

OM: Population Of Buyer Code For Dropship

ONT_POPULATE_BUYER

This profile option is used to control how Order Management will populate buyer details when sending sales order data to Oracle Purchasing for requisition processing during requisition import. Select from:

OM: Prevent Booking for Line Generic Holds

ONT_PREVENT_BOOKING

If a generic hold has been applied the transaction will fail booking.

OM: Printed Document Extension Class Name

ONT_PRINT_CUSTOMER_EXTN_OBJECT

This profile allows you to update with a custom java code class path that would have been created to print user hooks. The printing API reads the profile class path and executes the java function. Example: You have a custom table and would like data from this table to appear on the Ordering Document.

OM: Promotion Limit Violation Action

ONT_PROMOTION_LIMIT_VIOLATION_ACTION

This system level profile option determines the hold action Order Management will take when encountering a initial promotional hold returned by the pricing engine. If the pricing engine returns a possible promotional hold for an order or order line, Order Management will use the value of this profile option to determine the course of action for the order or line. Messages are generated and can be viewed within the Process Messages Window.

Select from:

This profile option is optional, and the default is Null.

OM: Quick Sales Order Form: Auto Refresh

ONT_QUICK_OE_AUTO_REFRESH

This profile allows you to control if the active line detail region displays data instantly corresponding to the line when navigating between lines and without the detail blocks instantiated/navigated. Also, with the toggle query coordination check box unchecked, you have to navigate to the detail regions to display the information corresponding to each of the detail regions. When a new session begins, the value will be read from the profile to control the instant automatic refresh of the form when changes have occurred.

Values for LOV: Line/Line Details/Both - Site, Application, Responsibility, User.

OM: Quick Sales Order Form: Defer Pricing

OE_UI_DEFER_PRICING

This profile will control the default setting although users will be able to activate it from the form. When a new session begins value will be read from the profile.

The default value is No.

OM: Defer Pricing. Values: Yes/No

Values at Site, Applications, Responsibility, and User Level.

OM: Raise Status Change Business Event

ONT_RAISE_STATUS_CHANGE_BUSINESS_EVENT

This profile determines whether status change business events can be raised by Oracle Order Management for line status changes. Select from:

The default value is NULL.

This value is set at the Site level.

OM: Records on Summary Page for External Users

ONT_ICP_DEFAULT_RECORDS

This profile option indicates the default query (for external users) called when a user requests either the Orders or Delivery summary pages available from the Order Information Portal. Valid values for this option are any positive, whole integer.

For external users, if you set this profile option to some value other than zero, the Order Information Home page and the Order Status page in Order Information will run a default query to show most recent open orders based upon the numeric value of the profile option. If you set the profile option to zero, the default query is not executed when displaying the Order Information Home page or the Order Status page.

OM: Restrict Customer Items for Line Level Ship To Address

ONT_RESTRICT_CUST_ITEMS

This profile option enables users to either use the current functionality or use of the new enhancement to view the Customer Items LOV. If the profile Option is set to YES, then the line level Ship To address displays only the customer items pertaining to that address. If the profile is set to NO, then all customer items are displayed.

OM: Return Item Mismatch Action

ONT_RETURN_ITEM_MISMATCH_ACTION

This profile option controls what should occur if you try to change the item ID of a referenced return line. Select from:

The default for this profile option is Allow.

OM: Return Unfulfilled Referenced Line Action

ONT_RETURN_FULFILLED_LINE_ACTION

This profile option is used for returns to control return of unfulfilled lines. Default value is Allow.

Select from:

OM: Run Order Import for XML

ONT_TRANSACTION_PROCESSING

This profile option determines if the Oracle Order Import concurrent program is automatically submitted after the successful import of XML data into Order Management interface tables. Select from:

The default for this option is NULL.

Note: A NULL value for this profile option is equivalent to setting the profile option to Asynchronous.

OM: Sales Agreement Default Order Type

OE_DEFAULT_BLANKET_ORDER_TYPE

If you plan to use the Sales Agreements feature, then create a sales agreement sales order and set the profile option to default the above setup order type. This will be used to generate Sales Agreement number. This is not mandatory. The user can select order type from the list of values on the Sales Agreement window.

OM: Sales Order Form: Cascade Header Changes to Line

OM_UI_CASCADE_HEADER_ATTRIBUTES

A predefined list of attributes will cascade from the sales order header to the line when a change is made during data entry. The profile option has three possible values:

OM: Sales Orders Form Preference

ONT_SALES_ORDER_FORM_REFERENCE

Order Management will provide two wrapper functions which will be packaged in a form library and do not have other dependencies. External products like TeleSales can determine which Sales Order UI to be invoked based on the return value from the function. The wrapper function will look at a OM profile to be seeded by OM and will call the classic Sales Order window or the new Quick Sales Order window. This profile can be set at all levels. The default value is Classic Sales Order window.

OM: Sales Order Form: Refresh Method (Query Coordination)

OM_UI_REFRESH_METHOD

This profile option determines whether the screen is refreshed after every save. There are four options available:

OM: Sales Order Form: Restrict Customers

ONT_UI_RESTRICT_CUSTOMERS

The value of this profile option determines if all customers are displayed within the Customer field on the Sales Order Header, Main Tab or only customers who have addresses in the organization the order is defined for. This profile is applicable only for the Sales Order Header Main Tab.

Customers are visible across all operating units; Customer Addresses are Organization specific.

The default for this profile option is Global.

OM: Sales Order Navigation From Pricing/Availability Form

Controls navigation to the Sales Order form. Based on the value (Always, Ask, Never) the user is always, asked, or never navigated to the Sales Order form when an order is created.

OM: Schedule ATO Item without BOM

You now have the option to schedule ATO items even without a Bill of Materials (BOM) attached to the ATO item, either in the Ship From warehouse or in the item validation organization. Formerly the ATO Items required an attached Bill of Materials in either the Ship-from organization or the item validation organization for performing scheduling actions on them in Operational Data Store (ODS) mode.The profile related to this functionality is enabled at the site level. When set to Yes, the profile enables scheduling actions on ATO items where there is no BOM attached. When set to No, a check for the BOM is made. The default value for the profile is No.

Note: This applies only when the mode is set to ODS (Profile INV: Capable to Promise set to ATP based on collected data). For Planning Data Store (PDS) mode OM: Schedule ATO Item Without BOM has no effect. For ATO-Buy Items, no BOM is required in the warehouse or item validation organization regardless of the mode (ODS or PDS) or OM: Schedule ATO Item Without BOM.

OM: Scheduling Role

ONT_SCHEDULING_ROLE

Values are CSR Only, CSR and Scheduler, Scheduler Only

Values can be set at Responsibility or User Level.

Only System Administrator can set this at the user level, Not user controlled.

OM: Send Acknowledgment For Change PO Response

This profile option determines whether an acknowledgement will be sent for the Change PO Response.

OM: Send Changed Lines to Pricing

ONT_SEND_CHANGED_LINES_PRICING

Set this profile to Yes if you want the system to send only changed lines to Pricing when a line is changed. Otherwise, send all lines. The default is Yes.

OM: Send Notifications of Internal Order Change

ONT_SEND_ISO_NOTIFICATION

This profile determines whether a notification needs to be sent for internal order changes. You can select from the following values:

The following table provides details of the internal order changes and the notification that the application sends:

Case No. Internal Order Change OM: Send Notifications for Internal Order Change Value Outcome
1 Schedule Arrival Date Null Application sends 1 notification indicating schedule arrival date change
2 Ordered Quantity Null Application sends 1 notification indicating ordered quantity change
3 Secondary Quantity Null Application sends 1 notification indicating secondary quantity change
4 Ordered Item Null Application does not send any notification
5 Schedule Arrival Date and Ordered Quantity Null Application sends 1 notification indicating schedule arrival date and ordered quantity change
6 Schedule Arrival Date and Secondary Quantity Null Application sends 1 notification indicating schedule arrival date and secondary quantity change
7 Schedule Arrival Date and Ordered Item Null Application sends 1 notification indicating schedule arrival date change
8 Schedule Arrival Date, Ordered Quantity, and Secondary Quantity Null Application sends 1 notification indicating schedule arrival date, ordered quantity change, and secondary quantity change
9 Schedule Arrival Date, Ordered Quantity, and Ordered Item Null Application sends 1 notification indicating schedule arrival date and ordered quantity change
10 Schedule Arrival Date, Secondary Quantity, and Ordered Item Null Application sends 1 notification indicating schedule arrival date and secondary quantity change
11 Schedule Arrival Date, Ordered Quantity, Secondary Quantity, and Ordered Item Null Application sends 1 notification indicating schedule arrival date, ordered quantity change, and secondary quantity change
12 Ordered Quantity and Secondary Quantity Null Application sends 1 notification indicating ordered quantity change and secondary quantity change
13 Ordered Quantity and Ordered Item Null Application sends 1 notification indicating ordered quantity change
14 Ordered Quantity, Secondary Quantity, and Ordered Item Null Application sends 1 notification indicating ordered quantity change and secondary quantity change
15 Secondary Quantity and Ordered Item Null Application sends 1 notification indicating secondary quantity change
16 Any Change No Application does not send notification for any change
17 Schedule Arrival Date Yes Application sends 1 notification indicating schedule arrival date change
18 Ordered Quantity Yes Application sends 1 notification indicating ordered quantity change
19 Secondary Quantity Yes Application sends 1 notification indicating secondary quantity change
20 Ordered Item Yes Application sends 1 notification indicating ordered item change
21 Schedule Arrival Date and Ordered Quantity Yes Application sends 1 notification indicating schedule arrival date and ordered quantity change
22 Schedule Arrival Date and Secondary Quantity Yes Application sends 1 notification indicating schedule arrival date and secondary quantity change
23 Schedule Arrival Date and Ordered Item Yes Application sends 2 notifications - one for schedule arrival date and one for ordered item change
24 Schedule Arrival Date, Ordered Quantity, and Secondary Quantity Yes Application sends 1 notification indicating schedule arrival date, ordered quantity change, and secondary quantity change
25 Schedule Arrival Date, Ordered Quantity, and Ordered Item Yes Application sends 2 notifications - one for schedule arrival date plus ordered quantity change and one for ordered item change
26 Schedule Arrival Date, Secondary Quantity, and Ordered Item Yes Application sends 2 notifications - one for schedule arrival date plus secondary quantity change and one for ordered item change
27 Schedule Arrival Date, Ordered Quantity, Secondary Quantity, and Ordered Item Yes Application sends 2 notifications - one for schedule arrival date plus ordered quantity change plus secondary quantity change and one for ordered item change
28 Ordered Quantity and Secondary Quantity Yes Application sends 1 notification indicating ordered quantity change and secondary quantity change
29 Ordered Quantity and Ordered Item Yes Application sends 2 notifications - one for ordered quantity and one for ordered item change
30 Ordered Quantity, Secondary Quantity, and Ordered Item Yes Application sends 2 notifications - one indicating ordered quantity change plus secondary quantity change and one for ordered item change
31 Secondary Quantity and Ordered Item Yes Application sends 2 notifications - one indicating secondary quantity change and one for ordered item change

OM: Sequence for TP Ship/Deliver Deadline

This profile populates the Latest Ship Date field for the delivery. This value maps to the late pick-up date field on the order release of Oracle Transportation Management. Values are:

OM: Set Receivables Transaction Date as Current Date for Non-Shippable lines

OE_RECEIVABLES_DATE_FOR_NONSHIP_LINES

This profile option determines if the Receivables transaction date (actual ship date in invoice interface tables) will be populated with the system date (SYSDATE) for non-shippable order or return lines.

Select from:

This profile option is optional, and the default value is No.

Note: Order Management populates actual ship date and sales order date while interfacing the line to Receivables. Order Management does not populate the transaction date and GL date. These dates are derived by Receivables depending on whether you use invoice rule and based on your batch source options. Please see Oracle Receivables user guide (determining dates section) for the information on how the invoice date is derived for your transaction.

OM: Show Line Details

ONT_SHOW_LINE_DETAILS

This profile option determines whether the line details of a model are displayed in the Sales Orders window. You can also toggle the display of line details using the Tools menu from the Sales Orders window.

OM: Show Process Messages Flag

This profile can be used to view which orders have associated Process Messages. By setting the above profile to Y, the Messages check box will be checked in the Order Summary Window, if there are any messages associated for the queried order.

OM: Source Code

ONT_SOURCE_CODE

This profile option identifies the source code that Order Management passes to Oracle Inventory during scheduling. The source code should be defined as the third segment of the Sales Order Flexfield to guarantee that each transaction is unique.

OM: Source for TP Early Ship/Deliver Date

This profile option populates the Earliest Ship Date on the delivery and maps to the Early Pick Up Date field on the Release Sales Order window. Values are:

Same Date as Ship / Deliver Deadline: Uses the earliest ship date from the order lines or the latest pick-up date (the Latest Ship Date value calculated from the profile option OM: Sequence for TP Ship/Deliver Deadline above) to populate the Earliest Ship Date on the delivery. This value populates the Early Pick Up date on the Order Transportation Manager Order Release window.

OM: Unique Order Source, Orig Sys Document Ref Combination For Each Customer

This profile option determines if customer information is to be included in the order import key. If it is set to Yes, then Order Import will check the uniqueness based on customer number, order_source_id and orig_sys_document_ref, otherwise customer information will not be included in the order import key.

OM: UOM Class For Charge Periodicity

This profile option determines what domain will be used to hold the allowable charge periodicities. The domain is a UOM class in Inventory. Inventory has seeded a UOM class called "Period" that will hold UOMs: Daily, Weekly, Monthly, Quarterly and so on. The profile option is seeded with the value "Period". Inventory has further seeded a value set INV_CHARGE_PERIODICITY that will hold UOMs: Weekly, Monthly, Quarterly, Yearly and so on.

OM: Use Configurator

ONT_USE_CONFIGURATOR

This profile option indicates which Oracle application software is launched to enter configuration information when selecting the Configurator button from the Sales Order window. Valid values are:

The default for this profile option is No.

OM: Under Return Tolerance

OM_UNDER_RETURN_TOLERANCE

This profile option indicates the percentage by which a return line can be under-received for it to be considered fulfilled. Any value between zero (0) and 100 (both inclusive) is a valid value. This profile option is set at the site level. Default value is zero (0).

OM: Under Shipment Tolerance

OM_UNDER_SHIPMENT_TOLERANCE

This profile option indicates the percentage by which an order line can be under-shipped for it to be considered fulfilled. Any value between zero (0) and 100 (both inclusive) is a valid value. This profile option can be set only at the site level. Default value is zero (0).

For additional information on profile option descriptions and setting for products other than Order Management, please refer to the product specific users guide.

OM: Unit Price Precision Type

ONT_UNIT_PRICE_PRECISION_TYPE

This profile option controls the display of Unit Selling Price field for sales order lines only.

Select from:

The QP: Unit Price Precision profile controls how many decimal points you can use on a Price List for a rounding factor.

OM: Use Item Orderability Custom Hook

The system profile option OM: Use Item Orderability Custom Hook enables users to invoke the custom hook (OE_ITORD_EXTN.Validate_Item_Orderability) for item validation during item orderability check at sales order line level. The default value is Null. If the value is set to Yes, the custom hook is initiated during item orderability. If the value is set to No or Null, the custom hook is not initiated during item orderability validation.

OM: Use Materialized View for Items LOV (Honours Item Orderability Rules)

If the value of this profile option is set to No, then the Items LOV lists all the items available in the item Validation Organization of the current operating unit irrespective of any item orderability rules defined.

If the value of the profile option is set to Yes, then the Items LOV is intelligent enough to display only those items which the current context is eligible to order: The Items LOV is dynamically built based on the item orderability rules and the current attribute values on the line.

This profile can be set to Yes or No at site level only. The default value is No.

OM: View Cancel Lines

ONT_SHOW_CANCEL_LINES

This profile option controls the default value of the Cancel check box when sorting sales order lines within the Sales Order Lines Tab, Sort window. The default value is Yes. Select from:

OM: View Closed Lines

ONT_VIEW_CLOSED_LINES

This profile option controls the default value of the Closed check box when sorting sales order lines within the Sales Order Lines Tab, Sort window. The default value is Yes. Select from:

OM: View Intercompany AR invoice

If this profile option is set to Yes, you will be able to view Intercompany invoices for internal sales orders. The other options are No or Null.

OM: View Pricing/Availability Information in Related Items

This profile option controls the amount of information shown in the Related Items and Manual Substitutions window. The available options are: Pricing only, Availability only. Pricing and Availability, and None.

OKC: Enable Sales Contracts

OKC_ENABLE_SALES_CONTRACTS

In order to leverage the functionality of Sales Contracts with Order Management, Sales Contracts must be installed and this profile must be set to YES. This profile can be set at the Application or Site levels.

QP: High Volume Order Processing Compliance

The value is set programmatically, and cannot be updated by users. If No, the pricing setup uses modifiers that will prevent using the optimized pricing code path. If Yes, the pricing setup is suitable for HVOP optimized pricing code. However, you should ensure that custom sourcing rules do not directly access G_HDR or G_LINE. If they do, modify the custom sourcing rules so that directly accessed fields are passed as parameters.

Related Topics

Oracle Workflow User's Guide

Oracle E-Business Suite system administration guides

Using Workflow in Oracle Order Management

Selected Oracle Application Profile Option Descriptions

(General Ledger) Journals: Display Inverse Rate

DISPLAY_INVERSE_RATE

Tip: Base currency is sometimes referred to as functional currency. Transactional currency is referrred to as foreign currency.

The application always stores the currency rate in foreign to base format irrespective of the profile.

For example, if the base currency is USD and the foreign currency is CAD.

If the profile option Journals: Display Inverse Rate is set toYes, when you navigate to the Conversion Rate field in the Sales Order window and have entered the Conversion Type as User, the message is displayed as: Enter the rate for USD to CAD.

If the profile option Journals: Display Inverse Rate is set to No, and when you navigate to the field in the Sales Orders window and have entered the Conversion Type as User, the following message is displayed as: Enter the rate for CAD to USD.

Conversion Rate(Inventory) INV: Capable to Promise

This profile option determines which planning data store availability checking is performed against when submitting an ATP inquiry. Select from:

Operating Unit

In Order Management, the Operating Unit profile MO: Operating Unit determines the operating unit the transaction gets created in. If you enable Multi-Org Access Control, then you can specify the Operating Unit (from those that are accessible to you via your MO: Security Profile) in the various transaction forms.

Setting Order Management System Parameters

System parameters in the Define OM System Parameters window can be functionally grouped, and you can define controls as easily as defining profile options. The Define OM System Parameters window enables you to define new parameters and set the values for the parameters using different sources like SQL and constant values. This is step six of the Order Management Setup Steps.

Defining Parameters

Create and define parameters using these fields:

To Define Order Management System Parameters:

  1. Navigate to the Define OM System Parameters window. Order Management > Setup > System Parameters > Define

    Define OM System Parameters window

    the picture is described in the document text

    Warning: You cannot have any open orders when performing updates to the Oracle Order Management system parameters. If open orders are found, a warning message displays. Select the OK button to ignore the Warning or select the Cancel button to not commit changes.

  2. Enter a unique code in the Parameter Code field.

  3. Enter a name for the parameter in the Name field.

  4. Enter a description of the parameter in the Description field.

  5. Select the category from the Category field that the parameter belongs to. This is controlled with a lookup. To create a new category, add the lookup code in the lookup type “OM_PARAMETER_CATEGORY” and then enter that lookup type in the parameter definition window.

  6. In the Value Set field, enter a value set associated as the source of values. The possible value sets can have validation types of NONE or TABLE. For seeded parameters, use a value set that begins with “ONT.”

  7. Select a value in the Open Orders Check field. This provides a control to allow or restrict changes to the parameter value once it is set for a given operating unit. Available options are Allow, Give error, or Give warning.

  8. When the Enabled check box is selected the parameter is available to use. For seeded parameters this field is active only for internal users.

  9. The Seeded check box indicates if the parameter is a seeded parameter or a user defined parameter. This is active only for internal users.

  10. Save the changes and click the OK button. To cancel without saving any changes, click the Cancel button.

Setting Parameter Values

You can set up parameter values at the operating unit level by entering these fields:

Note: If Multi-Org Access Control is enabled, you can manage system parameter values across all Operating Units accessible to you through the MO: Security Profile.

To Set Up Order Management System Parameter Values:

  1. Navigate to the OM System Parameters window. Order Management > Setup > System Parameters > Values

    OM System Parameters window

    the picture is described in the document text

  2. Select the operating unit from the available list of values. The Operating Unit field displays your default Operating Unit, however you can pick a different one from the list of values to manage parameters in it.

  3. The Category field identifies the category to which the parameter belongs. The available parameters and their currently selected values display. Select the Show All check box to display all the parameters for all categories.

  4. In the value field next to the parameter you want to set, select a value. The Value field displays a list of values available for each respective parameter. The Description field displays the descriptions for the currently selected parameter.

  5. Save the changes and click the OK button. To cancel without saving any changes, click the Cancel button.

For more information, see Defining Processing Constraints and Multiple and Partial Payments.

Seeded System Parameters

Approval Parameters

No Response From The Approver

By default, if an approver does not respond, the transaction will be rejected. When the parameter is set to continue, the transaction will progress to the next approver. The approval notification process waits for three days and then sends a reminder. It waits for another three days after the reminder before rejecting/continuing.

Default value: Blank

Alternate values: Reject (same as Blank) or Continue

Note: If the approver is the final approver on the list and does not respond, the transaction will be rejected regardless of the parameter value.

Treat AME Exception As

If you set the system parameter value as Approval and if the approver list generation process fail due to an error, then Order Management considers the transaction as approved. If you set the value as Rejection, then the application rejects the approval of the transaction in case of an error. The default value is Null. The application considers having no value as Rejection.

Consider Tax and Freight Charges in Sales Agreement Releases

ONT_CONSIDER_TAX_FRT_BSA_AMT

Set the system parameter to Yes to consider tax and freight on releases in BSA amounts. If you set the system parameter to Yes, then the application considers the freight charge and tax amounts to calculate the released amount, fulfilled amount, and returned amount on the BSA header and BSA lines along with the extended price when you create releases from BSA.

If you set the system parameter to No or NULL, then the application does not consider tax and freight charges to calculate the released amount in a BSA. The released amount is equal to the sum of the extended price on the corresponding sales order lines referencing this BSA.

Copy Parameters

Call line DFF extension API in COPY

Default value is No

Drop Shipment Parameters

Group Requisitions By Sales Order

This system parameter determines whether the Requisition Import process will import all the drop ship sales order lines into a single purchase requisition even though the lines belong to multiple sales orders or whether the process will group all drop ship sales orders lines by sales order and then import them into separate purchase requisitions. Multiple purchase requisitions are created with each purchase requisition having the lines corresponding to the drop ship lines of one sales order. This enables buyers to easily create one purchase order for each sales order.

If this system parameter is set to Yes and the drop ship lines are released to purchasing through the open interface, then the GROUP_CODE field is populated with the order header_id while populating the requisitions interface. The GROUP_CODE field takes precedence over the Group By parameter passed to the Requisition Import program. If the system parameter Group Requisitions By Sales Order is set to Yes, the Group By parameter is ignored and the requisitions are grouped by sales order only. Hence, the purchasing requisitions are created such that all the drop ship lines of one sales order are placed in one purchase requisition. If, however, a new drop ship line is added to a booked sales order after releasing the current lines to purchasing and importing the requisitions, that line is added to a new purchase requisition.

This system parameter can be set to Yes, No, or Null. The default value is Null. A Null value is treated as No.

Requestor For Drop Ship Orders Created By External Users

This system parameter indicates the employee who will be the requestor on the requisition generated to fulfill drop-ship orders that have been created by external users (for example, through iStore).

Requestor For Drop Ship Orders Created By Inactive Users

The value of this system parameter serves as the default employee for drop ship orders. During the course of Purchase Release, if the application finds that the employee who created the drop ship order line is no longer an active user, then the application checks the value of this system parameter. If the value of this parameter is an active user, then the application progresses the Purchase Release process and passes the relevant information into the Oracle Purchasing interface tables. In the case where the value of the system parameter is a non-current employee, then the Purchase Release process displays an error.

Note: Though this is an initial implementation task, a periodic review of this system parameter's value is useful for successful completion of the Purchase Release process.

Generic Parameters

Assign New Ship Set for Each Warehouse

Use this parameter for ship sets. This parameter enables you to assign a new ship set for each warehouse during order entry. The default value of this system parameter is no value and is equivalent to the profile set to a value of No. If you set this system parameter to N and the line set field on the Others tab on sales order header is set to Ship, then the application puts all the lines in the sales order into a single ship set, restricting all the lines to a single warehouse. For example,

Line Number Warehouse Ship Set
1.1 M1 1
2.1 M1 1
3.1 M1 1

When the system parameter value is Y and the line set field on Others tab on sales order header is set to Ship, then the application creates ship sets based on the warehouse entered on the respective sales order line. For example,

Line Number Warehouse Ship Set
1.1 M1 1
2.1 V1 2
3.1 DC1 3
4.1 M1 1
5.1 V1 2

If you update the warehouse information, then the application changes the corresponding ship set attached to it. For example,

Line Number Old Warehouse Old Ship Set New Warehouse New Ship Set
1.1 M1 1 M1 1
2.1 V1 2 V1 2
3.1 DC1 3 DC1 3
4.1 M1 1 M1 1
5.1 V1 2 DC1 3

Note: The application does not generate a new ship set name whenever you change the warehouse on the line when this parameter is set to Yes. Instead, when you save the updates to the warehouse, the application uses the unique default ship set name present for each warehouse in a given order. For example, in the above table, for line 5.1, the application uses the unique default ship set for warehouse DC1.

Additionally, the application does not consider the value of this system parameter if you have set the OM: Assign New Set For Each Line profile option to Y as the profile ensures that every line has a different set. Additionally, if you have set the system parameter to Y, then you can override the default generated ship set value for the applicable line by entering your value. For example,

Line Number Warehouse Ship Set
1.1 M1 1 (default)
2.1 V1 2 (default)
3.1 DC1 3 (default)
4.1 M1 USERSET (user entered)
5.1 V1 2 (default)

Audit Trail

The audit trail parameter is used in order to capture audit history at either order entry or booking. You can select either Disable, Enable when Order is Entered or Enable when Order is Booked. The default is Null - Disabled. When the default is set, then the you can also capture cancellation history of entered orders. Previously, the processing constraint used to maintain a history of cancellations of orders when the Require Reason action was selected.

Cascade hold to Option Items for Non SMC models

If the value of this parameter is Yes, then the option item is put on hold if the top model is placed on hold. If the value of this parameter is No, then only the top model is put on hold, The Cascaded Hold box in the sales orders line thus remains unselected.

Customer Relationships

The default value is Single Customer.

Customer Relationship Parameter Setting Examples

The table below lists sample customers, their sites and business purposes.

Sample Customers, Sites, and Business Purpose
Customer Site Bill-to Ship-to Deliver-to
A X Yes Yes Yes
B Y Yes No No
B Z No Yes Yes
C W Yes Yes Yes

The table below lists the relationships that exist between these sample customers. The data within the table will be used to describe how each of the profile option settings control the list of values for available for order data fields when placing an order.

Relationships Between Sample Customers
Customer Related To Customer Bill To Relationship Flag Ship To Relationship Flag
A None    
B A Yes Yes
C None    

If the parameter for Customer Relationships is set to Single, using the data within the second table, when placing an order for Customer A:

If the parameter for Customer Relationships is set to Related Customers, using the data within the second table, when placing an order for Customer A:

If the parameter for Customer Relationships is set to All Customers, when placing an order for Customer A:

Customer Relationships (Service)

If the value of the parameter is set to Single Customer, the shippable products originally installed for the sold-to-customer of the service line is displayed in the LOVs of the fields Service Reference Customer Product and Service Ref Order Number.

If the value of the parameter is set to Related Customers, the shippable products installed for the sold-to-customer in addition to the ones installed for the related customers of sold-to-customer is displayed in the LOVs of the fields Service Ref Cust Product and Service Ref Order Number.

If the value of the parameter is set to All Customers, the shippable products installed for all customers is displayed in the LOVs of the fields Service Ref Cust Product and Service Ref Order Number.

Default Behavior for Subscription Item on Order Line

Use this parameter to define the default behavior of subscriptions when ordering through the Order Organizer and Quick Sales Order windows in Order Management. You can specify that Order Management must process subscriptions as:

Note: This parameter is applicable only for orders that you create using the Sales Order windows.

Default Hint for Pricing and Availability

Enable Freight Ratings

The default value is No.

Enable Ship Method

The default value is Yes.

Item Validation Organization

In Order Management, the Item Validation Organization parameter indicates the Oracle Manufacturing organization against which items are validated. Organization is synonymous with warehouse in Order Management. You set the Item Validation Organization parameter in the Parameters window, and can only set the value to the operating unit associated with your current sign on responsibility. You must also define all transactable items in this organization.

Note: Before setting this parameter, you should first setup values for: HR: Security Profile HR: Business Group profile options. Valid inventory master organizations will be available based on values of HRMS profile settings.

For further information on these profiles please refer to Configuring, Reporting and System Administration in Oracle HRMS.

For a list of item attributes, please refer to the Item Attributes appendix in this guide.

Margin Calculation

The margin calculation parameter indicates the basis for the gross margin calculation in Oracle Order Management. Options are:

The default value is Price Based.

When the system parameter value is Cost Based, Cost Modifiers Only, Cost Based, Cost Modifiers and Rebates, Price Based, Cost Modifiers Only, or Price Based, Cost Modifiers and Rebates the system will calculate cost modifier amount and/or rebate amount to get the "Adjusted Unit Cost" and will use this adjusted unit cost instead of unit cost in margin calculations.

For more information on gross margin, see Setting Up Gross Margin and Overview of Gross Margin Display in the Oracle Order Management User's Guide.

Configuration Effective Dates

This system parameter is set at the organization (OU) level and determines which date is used to filter effective components in the model BOM. Options are:

Default value of Null retains existing behavior as seen in prior releases.

Enable Fulfillment Acceptance

This system parameter is used to enable the customer acceptance functionality. The possible values are Yes or No. The default value is No. Once this parameter is enabled, you call the Accounts Receivables API to invoke the rules engine to validate customer acceptance on every order line

Honor ATO Item Setup at Warehouse Level

The value of this parameter determines whether the application must honor the ATO flag at the warehouse level or item validation organization level. If you set the value to Yes, then the application treats the item as ATO/Non ATO, depending on the "Assemble to Order" flag corresponding to the warehouse entered on the sales order line. If you set the value as No, then the application treats the item as ATO/Non ATO, depending on the "Assemble to Order" flag corresponding to the item validation organization. If you do not set any value, then the application treats the item as ATO/Non ATO, depending on the "Assemble to Order" flag corresponding to the item validation organization. This parameter is applicable only to ATO items and not to ATO Models. However, the ATO item can be part of a KIT or a PTO model.

For existing order lines:

If you set this parameter to Yes, then the application does not allow changing of warehouse on the sales order line if:

Consequently, if you intend to set the parameter to Yes and use custom or extended sales order line workflows, then you must ensure that the above activity is present in them.

Source Line for deriving COGS account on referenced RMA

Use this parameter to derive the COGS account from the attributes on the current return line of a referenced RMA. To enable this functionality, ensure to select 'Return Line to be used as Source' as the parameter value. If you select 'Referenced Sales Line to be used as Source' or do not select any value, then the application derives the COGS account for a referenced RMA line from the attributes on the original sales order line.

You can set the value to 'Return Line to be used as Source' so that the COGS account is derived based on the Return Line in the following case:

For the following cases even if the system parameter is set to 'Return Line to be used as Source', the application uses the referenced sales order line as source:

Note: The application uses this system parameter not only for determining the warehouse from original sales order or RMA Line, but for deriving all attributes related to COGS workflow. In fact, the application uses this parameter to derive which line ID is used to trigger the COGS workflow. If parameter is set to 'Return Line to be used as Source' then from COGS derivation perspective, the behavior is same as if the RMA is non-referenced one.

Transaction Date for Inventory Interface Non Ship Process

You can select one of the following dates as the Transaction Date for order lines using Bill Only Inventory Interface flow:

Invoicing Parameters

Credit Memo Transaction Type

This value is transferred to Receivables if no value is defined for the credit memo Receivables transaction type associated with the Inbound Order Line OM transaction type and either: The Order Header has an OM transaction type of Mixed or The Receivables transaction type associated with the Order Header OM transaction type is NULL.

Credit Salesperson For Freight On Sales

This parameter determines whether to credit the salesperson on the invoicing line or order header for freight charges when the freight charges are treated as revenue. The default value is No.

Enable Recurring Billing

This parameter enables recurring billing in the environment. The default value is Null which is equivalent to No.

For more information on recurring billing, see:

GSA Discount Violation Action

This parameter determines how you want the user notified when you define a discount that results in an item price less than the price on a GSA discount for the same price list. Select from:

Inventory Item For Freight

This parameter is used only when the freight item is passed as revenue line. If you set the value to Inventory Item then the Invoicing module passes this item for freight charges, which will be treated as revenue lines.

Invoice Freight As Revenue

If the Receivables profile option TAX: Allow Tax Code Override is set to YES, and this parameter value is also set to YES, then freight charges are treated as revenue lines, and the Invoicing module will pass VAT tax and associated sales credits for processing. The default value is No.

Invoice Source

This parameter value is transferred to Receivables if the Invoice Source value is null for your transaction type at Order Line and null at the Order Header level.

Invoice Transaction Type

This parameter value is transferred to Receivables if no value is defined for the Receivables transaction type associated with the Outbound OM order line transaction type and OM order Header transaction type.

Non-Delivery Invoice Source

This system parameter value is transferred to Receivables if the OM: Invoice Numbering Method profile option is set to Delivery and the line is non-shippable.

Over Shipment Invoice Basis

This parameter determines whether to invoice the ordered quantity or the shipped quantity for an over shipment. This parameter can be overridden for the parameter specific to customers or customer sites by setting a value in the Customer window.

If the value of the parameter is Invoice Shipped Quantity, and if original (outbound) Sales Order is not invoiced, then the ordered quantity for RMA is the ordered quantity of the original (outbound) Sales Order. If the original (outbound) sales order has been invoiced, then the ordered quantity for RMA is the shipped quantity of the original (outbound) sales order.

If the value of the parameter is set to Invoice Ordered Quantity, the ordered quantity for RMA is the ordered quantity of the original (outbound) Sales Order.

Show Discount Details On Invoice

This parameter determines whether the discount details are passed to Oracle Receivables for printing on an invoice. Default value is No. If you set this parameter to No, then Extended Amounts will includes discounts.

Overshipment or Undershipment Invoice Basis for Charges

This parameter determines whether to calculate the freight charges based on the shipped quantity or the ordered quantity when you enter the tolerance for the sales order line and when the shipped quantity is not equal to the ordered quantity; but within the tolerance provided. The options are Shipped Quantity and Ordered Quantity.

Set the parameter to Shipped Quantity, to calculate the freight charge based on the shipped quantity. Quantity and UOM fields display the shipped quantity and UOM in the Sales Orders window at line level, in the Actions, Charges and Freight Costs window. The freight charge that is calculated based on the shipped quantity is displayed in the Charge field.

Set the system parameter to Ordered Quantity or to No Value to calculate the freight charge based on the ordered quantity. Quantity and UOM fields display the ordered quantity and UOM in the Sales Orders window at line level, in the Actions, Charges and Freight Costs window. The freight charge that is calculated based on the ordered quantity is displayed in the Charge field.

Payments Parameters

Apply Credit Hold on Zero Value Order

If you set No as the value of this system parameter, then credit checking does not happen on orders with zero amount. If you set Yes as the value, then credit checking happens on orders with zero amount. This is useful if you want credit checking to happen on orders with overdue invoices.

Credit Hold Sequence for Order Lines

This parameter is effective for line level credit checking at Picking/Packing. This system parameter has five options:

  1. All Lines (Default )

  2. The sequence in which lines will be taken into consideration for placing on hold are: Schedule Ship Date / Request Date, Shipment Priority Code, Line Number

  3. The sequence in which lines will be taken into consideration for placing on hold are: Shipment Priority Code, Schedule Ship Date / Request Date, Line Number

  4. Uninvoiced line amount ascending

  5. Uninvoiced line amount descending

Enable Multiple Payments

This parameter is always set to Yes by default and it is not visible in the System Parameters window. It allows multiple payments per order AND to use the full/partial down payment feature. Enables navigation to the Payments window from the Sale Order form using the Payments Action.

Installment Options

This system parameter has three options:

Authorize First InstallmentOnly the first installment of a payment is authorized.

In this case amount authorized will be total of the first installment less down payment, if applicable.

Enable Pay Now:The entire amount of the order is authorized.

Payment Due with Order functionality is enabled.

None:

The entire order amount will be authorized.

Default value for this parameter is None (same as Null).

Initiate Credit check at Cancellation

If this system parameter has the value Yes, then the application initiates credit checking when you cancel a line. If the value is No or there is no value, then the application does not initiate credit checking when you cancel a line.

Reversal of Credit Card Authorization and Re-authorization

Use this parameter to indicate when to perform reversal of authorization and re-authorization. You can select the following options:

Retrobilling Parameters

Default Order Type

The default value is Mixed.

Enable Retrobilling

The default value is No.

Retrobill Reason Code

The default value is Credit and Rebill.

Scheduling Parameters

Allow Partial Reservation

Set to yes if you want right-mouse reserving and the reservation time fence to support partial reservations. The default value is No.

Auto Schedule Sets

The value of this system parameter decides whether lines, which are getting added to a set, should be automatically scheduled or not, at the time of set creation. If the system parameter value is set to No, then the lines are not scheduled automatically, when they are added to a new set. However, you can schedule the lines manually whenever it is required. If you set the value to Yes, then the lines are scheduled as and when they are added to a set. The default value of the system parameter is Yes and the application treats no value as Yes.

Firm Demand Events

If you are publishing Plan results to Order Management, this parameter allows you to firm demanded lines at different event points within the line flow. Once firmed, ASCP cannot update the warehouse.

Schedule. Lines are firmed when scheduled.

Shipping Interfaced. Lines are firmed be when interfaced to shipping.

None/Null. Lines are not firmed by an event. Default value.

Item Substitution on Internal Order

Use this parameter to specify whether item substitution is allowed for internal sales orders. You can select from the following values:

The parameter is also used in conjunction with the Scheduling Auto Split Criteria when scheduling internal sales orders lines based on GOP recommendations.

Latest Acceptable Date

System scheduling always honors the Latest Acceptable Date. This parameter provides choices for using the Latest Acceptable Date with manual scheduling. You can control whether manual scheduling honors the Latest Acceptable Date, ignores the Latest Acceptable Date but provide a warning, or ignores the Latest Acceptable Date without warning (default value).

Promise Date Setup

The parameter allows you to control the behavior of the Promise Date.

First Request Date - Select this if you want the Promise Date to be the first Request Date.

First Schedule Ship / Arrival Date - Select this if you want the Promise Date to be the first Schedule Ship / Arrival Date.

Manual Entry - This allows you to enter manually or to default the Promise Date. Default value.

Request Date - Select this if you want the Promise Date to be dependent on the Request Date. If the Request Date is changed, the Promise Date will also change.

Schedule Ship / Arrival Date - Select this if you want the Promise Date to be dependent on the Schedule Ship / Arrival Date. If the Schedule Ship / Arrival Date changes, the Promise Date will also change.

Reschedule with Request Date Change

Set this parameter to No if you do not want a line to reschedule if the Request Date is changed. The default value is Yes.

Reschedule with Ship Method Change

Setting this parameter to No allows you to change the Ship Method without triggering rescheduling. The default value is Yes. Recommendation: do not set to No if using lead time scheduling.

Reservation Time Fence

This parameter controls automatic reservations during scheduling. The parameter represents the number of days into the future that scheduling will reserve. The default value is NULL which means that scheduling will not automatically reserve. This parameter is used during autoscheduling and also by the scheduling workflow activity and concurrent program to perform reservations.

Schedule Lines On Hold

This parameter controls whether scheduling will attempt to schedule lines that are on hold. The default value is NULL, which is the equivalent to Yes.

Scheduling Auto Split Criteria

This parameter applies to standard sales order and internal sales orders. If you set the value to Without Substitution, then during scheduling, if a partial quantity is available on the requested date, the application splits the order line. It updates and schedules the original line with available quantity on the requested date and updates the new line with the remaining quantity. The two lines have the same line number, but different shipment numbers, for example, 1.1 and 1.2.

If you set the value to With Partial Substitution, then during scheduling, if original item is available partially and substitute item is available completely on the requested date, the application splits the original line. It updates and schedules the original line with available quantity on requested date and the new line with the substitute item and the remaining quantity. The two lines have different line numbers, for example, 1.1 and 2.1. For an item to be substituted on an internal sales order line during ATP, the system parameter Item Substitution on Internal Order must be set to either Automatic or Manual and Automatic.

If you set the value to With Full Substitution, then during scheduling, if the original item is not available at request date in full quantity and substitute item is, then the application replaces original item with substitute item and schedules. If, however, substitute item is also not available, then the behavior is the same as for Without Substitution value. For an item to be substituted on an internal sales order line during ATP, the system parameter Item Substitution on Internal Order must be set to either Automatic or Manual and Automatic.

If you set the value to None or do not select any value, then during scheduling if the entire quantity is not available on the requested date, the application automatically schedules the order line with a schedule ship date on which the entire order quantity is available.

The following table discusses the effects on scheduling based on the four options of this system parameter:

Data returned from GOP after Scheduling Null/None With Full Substitution With Partial Substitution Without Substitution
For requested item, complete quantity is available on requested date. No change in current behavior. Order line will get scheduled on the requested date. No change in current behavior. Order line will get scheduled on the requested date. No change in current behavior. Order line will get scheduled on the requested date. No change in current behavior. Order line will get scheduled on the requested date.
For requested item, only partial quantity is available on requested date.

Note: Substitute item is not available on requested date.

 No change in the current behavior. Order line will be scheduled on available date. Split with first line with quantity available on request date and second line with remaining quantity. Split with first line with quantity available on request date and second line with remaining quantity. Split with first line with quantity available on request date and second line with remaining quantity.
For the requested item, there is no quantity available on request date but complete quantity is available on a future date.

Note: Substitute item is not available on requested date.

 No change in the current behavior. Order line will be scheduled on available date. No change in the current behavior. Order line will be scheduled on available date. No change in the current behavior. Order line will be scheduled on available date. No change in the current behavior. Order line will be scheduled on available date.
For requested item, there is no quantity available on requested date, but substitute item is available for requested date. No change in current behavior. Item substitution will take place on the order line. No change in current behavior. Item substitution will take place on the order line. No change in current behavior. Item substitution will take place on the order line. No change in current behavior. Item substitution will take place on the order line.
Original item is only available partially on requested date but substitute item is available completely for requested date. No change in current behavior. Item substitution will take place on the order line. No change in current behavior. Item substitution will take place on the order line. Split the first line with quantity available on request date and second line with substitute item with remaining quantity Split with first line with quantity available on request date and second line with remaining quantity

Note: This feature is not available for Models (ATO, PTO, Hybrid), Kit, non-ATP enabled items or lines which belong to a set (Ship Set or Arrival Set) and also not available through the HVOP functionality.

Use Reservation Removal Sequence

The Use Reservation Removal Sequence parameter gives you the ability to control the sequence of supply sources from which reservations are removed, if the quantity on the order line is reduced and if the line is reserved against multiple supply sources. If you enter Yes, the system uses the reservation removal sequences defined in the ONT_RESERVATION_REM_SEQUENCE (OM: Reservation Removal Sequence) lookup type and decrements the quantity accordingly when removing reservations against a sales order for the organization. If you enter No or Null, the system always decrements against the supply source that has the earliest need-by date.

For more information about how to set up the ONT_RESERVATION_REM_SEQUENCE lookup type, see Changing Scheduled Lines, Oracle Order Management Implementation Manual.

Accessing the Installation Details Window

If you want to access the Installation Detail window in Order Management, you must attach it to the Actions menu by using the user-defined menu option. If you do not attach the window, you will get an Forms Error Message "This function is not available for your responsibility".

  1. Using the System Administrator responsibility, go to Application > Menu and query for the ONT_SUPER_USER menu.

  2. Insert a new record keeping the Prompt and Submenu fields blank.

  3. In the Function field, select Installation Details from the LOV (the actual function name in the LOV is ASOCSINS). Enter a description for the function in the Description field such as, Installation Details window.

  4. Save your work and verify that the Installation Details option is available through the Actions menu of the Sales Order window and that it opens up the Installation Details window.

Define Tax Features

Order Management enables you to quote an estimated tax for orders at the time of order entry. This is step eight of the Order Management Setup Steps. The tax estimate can be based on the tax status; address information, and VAT (Value Added Tax) codes assigned to items, ship to sites, and customers. The actual tax value that appears on the customer's invoice in Oracle Receivables may vary.

See: Oracle Receivables Implementation Guide.

Credit Check

Tax amount for each line will be stored on the order line. You can control whether the tax amount is included in credit checking while specifying the credit checking rules.

Multiple Tax Amounts on an Order Line

You can specify a tax group for an order line. You can view multiple taxes applied to an order line at the time of entry and query, or on the acknowledgement and notification of shipment. Oracle Receivables allows each invoice line to be taxed automatically with one or more taxes.

Tax Related Processing Constraints

Through the use of seeded processing constraints, Order Management does not allow a user to:

If your business process allows tax information to be updated after an invoice has been created, you must modify the seeded processing constraints that affect updating tax information.

Tax Calculation

You can calculate tax by selecting a Tax Date to base your tax rates on, choosing the tax, the tax schedule, requested, promise, and system dates. You cannot set a value for the Tax Date field within the Sales Order window, but you can decide to change or update the existing seeded Defaulting Rule for Tax Date.

Tax calculation in Order Management can occur at one of the following events:

Tax calculation for the above events can only be controlled at the order level (not at the order line level). You specify when to calculate the tax for an entire order when you create Order Types within the Order Management Transaction Types window.

The default value for Tax Calculation Event Code is null. Null Tax Calculation Event is same as Entry. For payment verification purposes (to include tax in the total authorized amount), specify Entry or Booking as your Tax Event.

Note: The Copy Order functionality does not copy tax amounts; tax is recalculated for the new order.

For return orders (referenced or non-referenced returns), tax calculation occurs at the tax event defined for the associated Order Management transaction type. To calculate tax at any time, select Calculate Tax from the Actions button menu within the Sales Order or Order Organizer windows.

Tax amounts are displayed:

Additionally, tax is always recalculated when tax-dependent attributes change on the order line.

Tax Calculation at Entry

With tax calculation at Entry, tax is calculated as each order line is entered. This tax calculation is used, for example, in businesses that requires the user performing order entry to view the total of the order, including tax, so it can be quoted to a customer.

To include tax in Commitment Applied Amount, set the tax event to Entry.

Tax Calculation at Booking

When tax calculation occurs at Booking, tax is calculated on each of the booked order lines. This tax calculation option is used, for example, in business that require tax visibility for booked orders, but who want to increase order entry input times by not calculating tax at entry.

Tax Calculation at Invoicing

When tax calculation occurs at Invoicing, no tax calculations will occur within Order Management. Tax calculation will occur in Oracle Receivables when the order or order line is invoiced.

For maximum performance, set the Tax Event as Invoicing.

Inclusive Taxes

When you create your tax codes, you can specify that the taxes are inclusive taxes (the tax amounts are already included in the price of the item).

When the Tax Engine is called to calculate taxes, it will return inclusive taxes as well as exclusive taxes. Any inclusive taxes returned are not added to the extended amount of the order line or displayed within the Tax column of an order line. Order Management displays the estimated tax amount based on the tax date on the order line. However, inclusive taxes are displayed when you View Tax Details from the Action button menu within the Sales Orders Lines window.

You can perform a credit check including or excluding the estimated tax amount.

Tax Method Options

Order Management enables you to specify the tax method for your company or installation as a Oracle Receivables system option. The tax method determines how taxes are calculated. Tax methods include the following:

Tax Security

Order Management enables you to update the tax security information on an order or return by setting the eBTax: Allow Override of Customer Exemption profile option. This profile option controls the modification of the Tax Handling Status, Reason & Certificate fields at the order header and order line levels. Standard tax calculations can be overridden by setting the profile option to Yes. The eBTax: Allow Override of Tax Classification Code profile option determines whether the defaulted tax classification code on an order line can be updated.

Non-Taxable Transaction Types

Order Management enables you to define whether Oracle Receivables will automatically calculate taxes for a given OM order line type. You will need to associate a Receivables Transaction Type with the OM Transaction Type for this to occur.

This will determine if tax is required on an order. This option (tax calculation flag) is set in Oracle Receivables. You can specify whether a transaction type is taxable in the Receivables Transaction Types window. See: Transaction Types, Oracle Receivables User's Guide.

Related Topics

Oracle Receivables User Guide

Oracle Receivables Implementation Guide

Define QuickCodes

You can create QuickCodes for Order Management. QuickCode types that you can define include:

You can create as many quickcodes as you need. You can also disable QuickCodes.

The Access Level options determine whether you can define new lookup codes. You can modify User and Extensible lookup codes, however, System codes cannot be modified. Contact your system administrator.

To Define Quickcodes:

  1. Navigate to the Oracle Order Management Lookups window. Order Management > Setup > QuickCodes > Order Management.

    Order Management Lookups

    the picture is described in the document text

  2. Query the Lookup Code Type.

  3. Enter the Access Level - User, Extensible, System.

  4. Select the Application you want to use to define QuickCodes.

  5. Enter a description of the code.

  6. Enter the effective dates for the Lookup Code.

  7. Check Enabled to activate the Lookup Code.

  8. To inactivate the Lookup Code, deselect the Enabled box.

  9. Save your work.

Related Topics

Lookups - Defining Receivables Lookups, Oracle Receivables Implementation Guide.

Viewing Notifications

Single Notification Viewer

You can use a single mechanism for receiving all of your notifications, as opposed to different review facilities for different types of messages. This viewer is provided with Oracle Workflow.

Customizable Notification Viewer

You can view notifications and take the appropriate action to resolve each one quickly and easily. You can define selection and sorting criteria that let you manage your notification list so you see the most critical notifications first or can view different types of notifications on demand.

Notification Context

Given this universal Inbox of exceptions, you can see the context of each notification. For notifications where you need no additional information, you can choose a button to take the suitable action.

If you require additional information, you can open the appropriate Order Management window. For example, if you must approve or reject an order, you can view the order header and lines easily. The notification can either be a URL message or an attachment.

Related Topics

Using Oracle Workflow in Oracle Order Management

Exception Management

Function Security Options

Sales Orders: View Open Messages

Function: ONT_OEXOEORD_PROCESS_MESSAGES

Description: View Open Messages

This function seeds a new Action available from the Sales Orders windows. The action is accessed from the Actions button or the mouse right-click menu.

Sales Orders: Retry Activities in Error

Function: ONT_OEXOEORD_RETRY_WF

Description: Retry Activities in Error

This function seeds a new Action available from the Sales Orders windows. The action is accessed from the Actions button or the mouse right-click menu.

Exception Management Setup

To setup Exception Management

  1. Set the profile OM: Show Process Messages Flag to Yes to enable the Open Flag to be populated in the Order Organizer.

  2. Set the profile OM: Generate Diagnostics for Error Activities to Yes to enable the Diagnostics: OM Order Information concurrent program to be run automatically when there is an error in a workflow activity. Currently Exception Management automatically submits the Diagnostics: OM Order Information concurrent program via the Order Management Error flow if the profile option OM: Generate Diagnostics for Error Activities is set to Yes. In the event that activities are retried and failed multiple times, the concurrent program does not run again and again as this could result in performance issues.

  3. Define any custom message statuses desired by editing the seeded lookup type ONT_MESSAGE_STATUS.

Error Messages

These messages display when you try to launch the Process Messages window with no open messages:

OE_NO_ERROR_MESSAGES

There are no open messages. This message displays when you try to view the workflow activities in error, but the transaction does not have any activities in error.

OE_NO_ERRORED_ACTIVITIES

There are no workflow activities in error for this transaction. Please see the Workflow Monitor or status window for more information.

ONT_CONC_MSG

Diagnostic: OM Order Information Request ID: Message displayed if there are any error messages on the stack.

OE_WF_ACTIVITY_ERROR

Workflow activity has failed. Please fix the errors and retry the activity from the Order window or the Workflow Monitor. Message displays if there are no error messages on the stack.

OE_WF_ACTIVITY_UNEXP_ERROR

Workflow activity has failed due to an unexpected error. Please retry the activity from the Order window or the Workflow Monitor. If it fails again, then contact your System Administrator. Message used to display the concatenated line number in the workflow notification for normal orders.

OE_WF_CONCAT_LINE

Message displays the concatenated line number in the workflow notification for return orders.

OE_WF_CONCAT_RETURN_LINE

Message displayed after an activity in error is retried successfully.

OE_RETRY_SUCCESSFUL

Retrying the activity in error completed successfully. Please look at the flow status or workflow monitor for more information.

OE_EM_NO_WF

There is no workflow associated with this transaction.

Define Document Sequences for Order Numbering

Order Management uses AOL Document Sequence functionality for order numbering. This is step eleven of the Order Management Setup Steps. You can define document sequences that automatically generate numbers for your sales documents as you enter them. You can define a single document sequence to assign unique consecutive numbers to all your sales documents, or you can define multiple document sequences that are assigned to different order types. In the latter case, an order or return is uniquely identified by its type and its number, since sales documents of different types may share numbers. Sales document numbers cannot contain alphabetic characters.

Gapless Order Number Source

Many countries have legal and audit requirements for order numbers to be contiguous. You can set up a document sequence as gapless through the Define Documents Sequences window. You can set up a gapless sequence for quotes, sales orders and Sales Agreements. In addition, Order Management prevents deletion of orders that have been numbered using the gapless numbering sequence. The application uses locks to ensure gapless numbering. If you are using gapless sequences, please save your changes frequently to minimize lock contention issues.

Note: Transactions may be gapless, however if all quotes do not become orders, the order numbers will not appear gapless.

Manual Order Numbers

Order Management enables you to enter the order numbers for certain types of orders. You can define a document sequence as manual and assign it to a desired order type. This order type can be used on orders that you want to manually enter order numbers. When an order number is specified for such an order, Order Management validates that it is unique for a given order type.

Prerequisites

To define document sequences for order numbering:

  1. Navigate to the Document Sequences window. Order Management > Setup > Documents > Define.

    Order Management Document Sequences Window

    the picture is described in the document text

  2. You can define the sequence to be Automatic, Gapless or Manual.

    • Automatic: The system automatically increment document numbers. Automatic sequences do not guarantee contiguous numbering.

    • Gapless: The system guarantees that the numbers returned are contiguous.

    • Manual: The user must specify a unique document number.

    For all types of numbering, Order Management validates that the number specified by you is unique for a given order type.

    For more information on AOL Document Sequences, see the Oracle E-Business Suite Setup Guide, Defining Document Sequences.

  3. Enter a name for the document sequence. Specify Oracle Order Management as the Application.

  4. Enter a starting number.

  5. Optionally, enter effective dates for the document sequence.

  6. Save your work.

    Note: When sales document Types are defined, a corresponding Document Sequence Category will automatically be created for order types and not for line types. The category created has the same name as the order type. You must navigate to the AOL Assign Document Sequence window to assign a sequence to the newly created category. If the Document Descriptive Flexfield is enabled, you need to specify the governing ledger. The Document Method code should be left blank.

Related Topics

Profile Options

Define Order Management Transaction Types

Define Order Management transaction types to classify sales documents. As an example, for each order type, you can assign a default price list, defaulting rules, order lines, return lines, line types, workflow assignments, payment terms, and freight terms.

Prerequisites

Defining Order Management Transaction Types

If Multi-Org Access Control is enabled, you can manage Transaction Types across all Operating Units accessible to you via your MO: Security Profile.

To define transaction types:

  1. Navigate to the Transaction Types window.

    Order Management Transaction Types Window

    the picture is described in the document text

  2. In the Operating Unit field, select an operating unit from the list of values. The field displays your default Operating Unit, however you can pick any other value from the LOV. Operating Unit sensitive fields on the form are disabled until an Operating Unit is specified. If you specify values for these fields and then change the Operating Unit, those fields will be cleared.

  3. Enter the name of the transaction type in the Transaction Type field.

  4. Enter a description in the Description field.

  5. In the Sales Document Type field, select Sales Agreement or Sales Order from the list of values (for Quotes, Returns and Releases, choose Sales Order).

  6. In the Order Category field, select a category from the list of values. For Order Types, you can specify a value of Order, Return, or Mixed. For Line Types you can specify Order or Return. When an order type is assigned to an order, the category determines whether both order and return lines can go on the order. A category of Mixed enables an order to have both kinds of lines. For Sales Agreements, select Order.

    For Order Lines, the Sales Orders window automatically sets the category to Order. Order Management seeds defaulting rules to get the appropriate default outbound or inbound line transaction type from an order type to a line based on its category code.

  7. In the Transaction Type Code field, select order or line from the list of values to specify whether this is an order or line transaction type. Select "order" for Sales Agreements.

  8. In the Fulfillment Flow field, select a flow from the list of values. For more information on Fulfillment Flows, see the following topics in the Oracle Order Management Implementation Guide:

    • Using Workflow in Order Management

    • Negotiation in Order Management

    • Sales Agreements

  9. If a negotiation flow is needed, select it in the Negotiation Flow field from the list of values. .

  10. Enter an effective date for the transaction type in the Effective Dates field.

  11. Select the default transaction phase, Fulfillment or Negotiation, in the Default Transaction Phase field from the list of values. Transaction phase determines where in the workflow the transaction begins, and can be used in defaulting rules. This field defaults to Fulfillment—a fulfillment phase must be defined; Negotiation is optional.

  12. Enter a value in the Layout Templates field. This field is optional. For more information, see Preview and Print Sales Documents, Oracle Order Management Implementation Manual.

  13. Enter a value in the Contract Template field. This field is optional. For more information, see Authoring and Negotiating Contract Terms, Oracle Order Management Implementation Manual.

  14. In order for the Quote number to become the Sales Order number, define the transaction type with Retain Document Number checked. This is not applicable for Sales Orders or Sales Agreements. If the transaction type is associated with a negotiation flow and fulfillment flow, the document number can be retained when the document transitions to fulfillment.

    Note: If you need different sequences for quote and sales order, then you must ensure that the two sequences do not overlap. This prevents the two sequences from having the same initial value and enables you to reconfigure the sequences and assignments when it is necessary.

  15. Select the Approvals button if you want to assign a list of approvers for the transaction flow. See: Defining Approvals. Alternately, if you want the Oracle Approvals Management (AME) to generate the list based on your set up in AME, then select this check box. See: Approvals Management in the Order Management Integration chapter.

  16. Use the Validate Workflow button to verify the workflow assigned at the header transaction type. This action enables you to ensure that a customized workflow is relatively error free and compatible with the applicable child workflows (and the child workflows are compatible with the header workflow). On clicking this button, Order Management submits the Validate OM Workflow concurrent program with the Order Type as parameter to perform full validation of the fulfillment, negotiation, and line flows assigned to the order type. The information about probable workflow errors and warnings that you must correct to use the workflow effectively are available in the concurrent program output file after the program runs to completion.

  17. Click Assign Line Flows button to assign the appropriate line workflows. Note: Sales agreement only uses the header flow and it does not take advantage of defaulting rules - there are no line level workflows for sales agreements. See: 'To assign workflows to transaction types' section in this topic.

  18. On the Main Tab in the Document Region:

    In the Agreement Type field, select a pricing agreement type from the list of values. This field is optional.

    If you enter an agreement type here, you can choose only agreements with this agreement type when using this order type. Define agreement types using Order Management QuickCodes. For more information, see Define QuickCodes, Oracle Order Management Implementation Manual.

  19. In the Default Return Line Type field, select a return line type from the list of values.

  20. In the Default Order Line Type field, select an order line type from the list of values.

  21. Select the Agreement Required check box if a pricing agreement is required. This is only applicable to order transaction types.

  22. Select the Purchase Order Required check box check to require purchase order numbers during order entry for orders and returns with this Order type. This is only applicable to order transaction types.

  23. On the Main Tab in the Pricing Region:

    Select the Enforce List Price check box to prevent discounts and overriding the selling price. If this is selected, you cannot apply discounts to the order line list price when you use this order type and you cannot override the selling price, unless the profile option OM: Discounting Privilege is set at the appropriate level.

  24. In the Price List field select a price list from the list of values to serve as a defaulting source. The list of values displays global price lists and price lists defined for the Operating Unit selected.

  25. Enter a minimum margin in the Minimum Margin Percent field. This field is optional.

  26. On the Main Tab in the Credit Check Rule Region:

    In the Ordering field, select an ordering credit check rule from the list of values. This field is optional.

  27. In the Packing field, select a packing credit check rule from the list of values.

  28. In the Picking/Purchase Release field, select a picking credit check rule from the list of values. .

  29. In the Shipping field, select a shipping credit check rule from the list of values. This field is optional.

    Select credit check rules to use when performing checking credit at either Booking, Pick Release and Purchase Release (for drop shipments), Packing, or Shipping within the corresponding Credit Check Rule fields.

    You can select a credit check rule for each field within the Credit Check Rule region, or choose to select combinations that suit your business purposes. For example, you can choose to select a credit check rule for booking only, or booking and shipping.

    If you leave any of the Credit Check Rule fields blank, no credit checking will occur when an order or order line reaches the corresponding workflow activity within the order or line flow, using the order or order line type specified.

  30. In the Credit Card region, select from the following credit card authorization reversal and reauthorization options:

    • Immediate - Order Management immediately invokes the IBY API 'IBY_FNDCPT_TRXN_PUB.Create_Reversal()' for reversal or re-authorization if there is a change in order or line amount or credit card information.

    • Picking or Purchase Release - Order Management performs re-authorization or reversal of authorization, based on the change in the previously authorized data, after completion of picking (order line changed to 'picked' status) or before purchase release.

    • Place Order or Line on Hold - This option enables the application to place order or line hold whenever payment entered is authorized and re-authorization or reversal of authorization is required, based on the change in the previously authorized data .

    • Re-pricing at Fulfillment - Order Management performs re-authorization or reversal of authorization, based on the change in the previously authorized data, after completion of Re-price at fulfillment activity.

    • Ship Confirmation - Order Management performs re-authorization or reversal of authorization, based on the change in the previously authorized data, after completion of shipment confirmation (order line changed to 'shipped' status).

    For further details, see description of Reversal of Credit Card Authorization and Re-authorization system parameter in Seeded Parameters, Oracle Order Management Implementation Manual. Additionally, ensure that you select applicable values in the Credit Card Authorization Reversal field on the Payment System Setup page for credit card and Authorization Reversal field on the Credit Card Brand Setup page in Oracle Payments. See: Oracle Payments guides.

    Note: When a transaction is created, Order Management automatically creates a Document Sequence Category of the same name for you. You can then go and assign a document sequence that you have defined for order numbering to this document sequence category. Document sequence categories are not MLS Compliant. Order Management recommends that you create your transaction types in the base language of your installation to minimize potential confusion. Two document sequence categories are created - one, with the same name as that of the transaction type and the other with the same name as transaction type but appended with the string '-quote.'

    Workflow assignments are required for order types to support the creation of quotes and sales orders as well as for types to support the creation of Sales Agreements.

To define Shipping Related Attributes for Order Management order and line transaction types:

  1. Navigate to the Transaction Types window. Order Management > Setup > Transaction Types > Define

    Note: None of the fields in the Shipping tab are applicable to Sales Agreements.

  2. Select the Shipping tab.

  3. Warehouses are synonymous with inventory organizations in Oracle Manufacturing.

  4. Select the appropriate Shipping Method from the list of values.

  5. The Shipment Priority field gets its values from Quick Codes.

  6. Freight Terms are defined using Order Management QuickCodes.

  7. In the FOB field, enter the FOB point. Define FOB points using Receivables QuickCodes.

  8. In the Shipping Source Type field, select the ship source type, internal or external, from the list of values. This determines if the order line is sourced externally through Drop Shipment, or sourced internally. This field is optional and applicable only to Line Transaction Types.

  9. In the Demand Class field, select a region from the list of values. Define demand classes using Manufacturing QuickCodes.

  10. In the Scheduling Level field, select one of the following options from the list of values:

    • Inactive Demand without Reservations (this functionality is only for standard items, and it does not support model, ship, or arrival sets)

    • Inactive Demand with Reservations (this functionality is only for standard items, and it does not support model, ship, or arrival sets)

    • ATP Only

    • Allow all scheduling actions

    • No Reservations

      Note: If you do not specify a value for an Order Transaction type, the application interprets the null value as Complete Scheduling. If you do not specify a value for a Line Transaction Type the application uses the value from the Order Type on the Order.

  11. Select the Inspection Required check box if an inspection is necessary. This is applicable only to return line transaction types.

  12. Select the Auto Schedule check box if you want automatic scheduling for this order type. This is applicable only to order transaction types.

  13. In the Line Set field, select Arrival or Ship from the list of values. This field is optional.

  14. Select the Fulfillment Set check box to apply a fulfillment set. Selecting this enables fulfilling all of the lines of an order at the same time. If you put the lines in a fulfillment set, you cannot fulfill (invoice) the lines until all of the lines are ready.

  15. Select the Bill Only check box to prevent order lines that do not require shipping and are part of 'bill only' workflows to be added to ship or arrival sets.

    When the system applies the Ship-Line activity hold on an order line automatically via a hold source: if the Bill Only checkbox of the line type of the order line is selected, the hold will not be applied to that line.

To define Financial attributes for Order Management order or line transaction types

  1. Navigate to the Transaction Types window.

    Note: None of the fields on the Finance tab are applicable to Sales Agreements, the regions are Rule, Source and Credit Method For.

  2. Select the Finance tab.

    In the Rule region on the Finance Tab:

  3. The Invoicing Rule controls the amount and timing of your invoices.

  4. An Accounting Rule controls the amount and timing of when you recognize revenue for this order.

  5. In the Source Region on the Finance tab, within the Invoice Source field, select a Source from the list of values.

  6. In the Non Delivery Invoice Source field, select a source from the list of values.

  7. In the Credit Method For region on the Finance tab, select a credit method for invoices from the Invoices With Rules pop up menu.

    Oracle Receivables uses these accounting credit methods when adjusting the revenue account assignments of invoices using multi-period invoicing and accounting rules. See: Crediting Transactions, Oracle Receivables Implementation Guide.

    • LIFO (Last In First Out): Backs out revenue starting with the last general ledger period, and reverses all prior periods until it has used up the credit memo

    • Prorate: Credits an equal percentage to all account assignments for that invoice

    • Unit: Reverses the revenue for the number of units you specify from an original line of the invoice

  8. Select a credit method for invoices from the Split Term Invoices pop up menu.

    Oracle Receivables uses the following the Invoicing credit methods when crediting the installments of invoices that have multiple installments (split term invoices). Crediting Transactions, Oracle Receivables Implementation Guide.

    • LIFO (Last In First Out): Credits the last installment to be credited first and then credits all prior installments until all of the credit is used

    • FIFO (First In First Out): Credits the first installment first and then credits all subsequent installments until all of the credit is used

    • Prorate: Prorates the credit received by the installments of invoices by the amount remaining on their installments

    Also on the Finance Tab:

    In the Receivables Transaction Type, select a value from the list of values. This is applicable if you use Oracle Receivables. Invoice types designate invoice status, invoice printing options, credit memo type, and whether the invoice posts to General Ledger or creates an open receivable. Ensure the Tax Calculation Flag for the Receivables transaction type you choose is set accordingly as this will determine whether Tax is calculated for the order line.

  9. The Tax Event determines when Order Management calculates the estimated tax amount for a transaction.

  10. In the Cost of Goods Sold Account field, select and account from the list of values

    This is applicable only for order transaction types.

  11. In the Conversion Type field, select a conversion from the list of values. In the Currency field, select a currency from the list of values. If you choose User as the currency conversion type, the Sales Orders window requires you to enter the conversion rate and date. This is applicable only for order transaction types.

To assign workflows to transaction types:

Use this procedure to assign workflows to line transaction types. The combination of the order type, the line type, and the item type determines the line workflow.

Line flows are required for Sales Orders but not for quotes. Once you have created a document using an order type you cannot change the existing line workflow assignments. Instead, enter an end date for the existing assignment and enter a new assignment for the for the new workflow.

Note: This is not applicable to Sales Agreements.

  1. Navigate to the Transaction Types window and query the desired transaction type.

  2. Click Assign Line Flows.

    Line Workflow Assignments Window

    the picture is described in the document text

  3. In this window, select the order type/line type/item type combination to which you want to assign a workflow.

    If you leave Item Type blank, the workflow applies to all item types for the line type (unless they have a specific assignment in this form).

    If you use line type ATO Models, use item type Configured Item and return line types use item type Standard even if they are for configurations.

  4. In Process Name, select the workflow that Oracle Order Management should use for the order type/line type/item type combination.

    If you do not assign a workflow to a configured item type, the configured item does not use a workflow.

  5. In Start Date and End Date, select the time period during which the assignment is effective.

  6. Save your work.

Defining Approvals

To define Order Management Approvals:

  1. Navigate to the Approvals window.

    Order Management Approvals Window

    the picture is described in the document text

  2. Enter a name in the List Name field.

  3. Enter a description of the approval in the Description field. This field is optional.

  4. In the Transaction Type field, select the transaction type that the approval applies to, from the list of values. You can pick a Transaction Type from any of the Operating Units you have access to via your MO: Security Profile.

  5. In the Transaction Phase field, select Negotiation or Fulfillment from the list of values. Ensure that the workflow assigned to the transaction includes the Approval activity and the phase assigned corresponds. For example, Workflow: Negotiation with Approval; Transaction Phase: Negotiation.

  6. Select an effective date in the Effective Dates fields.

  7. In the List Members region, select the members in the Role fields, assign a sequence, and indicate if they are active by selecting the Active check box next to their name.

  8. Save your work.

Define Order Import Sources

You can define Order Import Sources from which to import order information. You can import historical orders, orders from other quote or sales systems, and changes to orders. Oracle Order Management recommends that you define a unique name for each source of order information you are importing. When you run the Order Import program, you can enter the source or sources for each execution. You can run Order Import for multiple sources at one time. This is step twelve of the Order Management Setup Steps.

Internal Sales Orders

If you are importing internal sales orders from Oracle Purchasing, you need to define an Order Import source to be used when you transfer the internal requisition information from Oracle Purchasing to create an internal sales order in Order Management.

You need to choose an Order Import source for internal requisitions/internal sales orders when you define purchasing options in Oracle Purchasing. You choose this same Order Import source as a parameter when you run the Order Import program in Order Management. See: Integrating Oracle Order Management Using Order Import, Oracle Manufacturing, Distribution, Sales and Service Open Interfaces Manual.

To define an Order Import source:

  1. Navigate to the Order Import Sources window.

    Order Import Sources Window

    the picture is described in the document text

  2. Enter the Order Import source name and a description.

  3. Check Enabled to activate the Order Import source.

  4. Select AIA Enabled to indicate that the details of orders belonging to this order source are synchronizable to third party systems via AIA process integration packs.

  5. Save your work.

Defining Processing Constraints

Processing constraints are rules that control who can change what and when they can change it. Processing constraints can prevent certain changes, but can also be set up to perform actions based on those changes. They can define actions that can result from these changes, such as requiring a reason for the change, triggering an action in Audit Trail or Versioning, or raising an Integration Event. This is step twenty-four of the Order Management Setup Steps.

This section describes how to set up your processing constraints based on validation conditions in validation templates (for example, Booked = Yes) which are evaluated for groups of records (record sets).

Prerequisites

Become familiar with the Processing Constraints that are delivered with the Order Management Application.

Note: After updating constraints and/or conditions, close and reopen the Sales Agreements or Sales Orders window for the updated constraints to apply correctly.

To set up processing constraints:

  1. Navigate to the Define Processing Constraints window.

    Order Management Processing Constraints Window

    the picture is described in the document text

  2. Query Application for Oracle Order Management and Entity for the entity for which you want the processing constraint, for example, Order Header or Order Line.

  3. Move to Constraints. In the top area of the region, enter each constraint in a line.

  4. In Operation, select the operation that you want to constrain.

  5. Select an Attribute to constraint, based upon the operation selected.

    • If you select the value UPDATE for the Operation field and you do not select an Attribute value, the constraint allows no update to any field of the entity, by any user.

  6. In User Action, select one of the following:

    • Not Allowed: You cannot perform the constrained operation

    • Require Reason and History: You can perform the operation only if you enter a reason. Use this with Operation CANCEL, Operation UPDATE if the constrained attribute is Ordered Quantity only, and for recording Audit Trail history when requiring a reason for an attribute change

    • Requires History: You can perform the operation and will not be prompted to enter a Reason. You still have the option to enter both a Reason and Comment, and if you do so, the information is recorded. Use the value for enabling Audit Trail history to be recorded without a reason for an attribute change

  7. Select a value for the System Changes field. The value selected in this field determines if system changes are allowed, despite the constraint. Choose from:

    • Always: System changes allowed

    • Never after Insert: System changes allowed if the entry has not been saved to the database

  8. Select a value for the User Changes Field. Choose from:

    • Never: The user is always constrained

    • Never after Insert: The user is constrained after the entry is saved to the database

      Note: Once you move from one line to another, the data is posted in the database but it is not saved (committed) until you click the Save button. This means the values will not be visible for other sessions, but for the current session it is posted to the database and thereafter either it will be committed once you click the Save button or will be rolled back if you cancel. Any change after you move from the line is after INSERT.

  9. The Enabled field indicates whether the current constraint is active. This allows constraints to be temporarily disabled if necessary.

  10. System check box - If a Constraint has the System check box selected, you cannot update the constraint definition.

  11. Move to the Conditions tab. Enter a constraining condition for the selected constraint. The selected constraint is determined by the previous cursor position prior to moving to the Conditions tab region.

  12. In the Group Number field, enter a numeric value according to the following principles:

    • For conditions that should together evaluate to TRUE (AND conditions), enter the same group number. The constraint applies if the entity in question meets all of the conditions defined.

    • For conditions that should together evaluate to OR (OR conditions), enter a different number for each record. The constraint applies if the entity in question meets any one of the conditions defined.

  13. In Scope, if the record set applies to multiple records, indicate the scope of evaluation of the record set for this condition. An example of a record set that applies to multiple records is the record set of all of the lines of a sales order. Select one of the following:

    • Any: The condition is satisfied if one of the records meets it, for example, the condition is satisfied if one of the sales order lines is booked

    • All: The condition is satisfied if all of the records meet it, for example, the condition is satisfied if all of the sales order lines are booked

  14. In Validation Entity, enter the entity for which the condition is validated. You can enter the same entity as the constraint (at the top of the Constraints region) or you can enter an entity related to the constraint. For example, if the constraint is against Order Header, Validation Entity can be Order Line.

  15. In Record Set, select the record set that corresponds to the entities to which the constraints process should apply the condition. For example, if you enter the order line record set Line, the condition is evaluated against the order line in question. If you enter the order line record set Order, the condition is evaluated against any or all (depending on the scope) lines of the order in question.

    If Validation Entity is different from Entity (at the top of the form), you can only select record sets based on the primary key of the validation entity.

  16. Select the Not check box (the negative condition modifier) to direct the constraints processing to evaluate the NOT condition of Validation Template. For example, if you expect to select Validation Template Booked, selecting NOT creates the condition of not booked for the constraint.

  17. In Validation, select a validation template. This item specifies the condition being evaluated.

  18. Enabled- The Enabled field indicates whether the current constraint is active. This allows constraints to be temporarily disabled if necessary.

  19. System check box:

    • If a Constraint has the seeded check box selected, and the constraint condition check box is also selected, you cannot update the constraint condition.

    • If a Constraint has the seeded check box selected, and the constraint condition check box is not selected, you can update the constraint condition.

  20. In User Message, enter the trailing portion of the error message that the constraint processing should display when the user violates the constraint.

    For example, if the constraint was to not allow an update of the item field on the order line if the line has been previously booked, constraints processing displays the error message You are not allowed to update the item; the item is booked.

  21. Move to the Applicable To tab and specify who the constraint applies to.

    Processing Constraints Window

    the picture is described in the document text

  22. Select one of the following:

    • All responsibilities: The constraint applies to all responsibilities.

    • Authorized responsibilities: The constraint applies to all responsibilities except ones that you specify. Specify the excepted responsibilities in the untitled lines below your selection.

    • Constrained responsibilities: The constraint applies to the responsibilities that you specify. Specify the excepted responsibilities in the untitled lines below your selection.

  23. Save your work.

    Note: Please ensure that when you are creating or updating Processing Constraints, the window that will be using the constraints (e.g. Sales Order, Sales Agreement) is closed. The constraints are cached and if they are updated while a sales transaction window is open, the updated constraints may not function according to the updates. Therefore it is advisable to close all sales transaction windows before updating Processing Constraints.

    Processing Constraints Example

    To set up a processing constraint that forbids update of the sales order header order type when there are order lines created or when the order is booked, do the following after navigating to the Define Processing Constraints form:

    • Query in the top of the form:

      • Application: Oracle Order Management

      • Entity: Order Header

    • Enter on a new line at top of the Constraints region:

      • Operation: Update

      • Attribute: Order Type

      • User Action: Not allowed

      • Leave System Changes, User Changes blank

      • Clear Seeded check box

    • Enter in the first line of the Conditions tabbed region:

      • Group Number: 1

      • Scope: Any

      • Validation Entity: Order Header

      • Record Set: Order

      • Clear NOT check box

      • Validation Template: Booked

      • Clear Seeded check box

      • User Message: the order is booked

    • Enter in the second line of the Conditions tabbed region:

      • Group Number 2

      • Scope: Any

      • Validation Entity: Order Header

      • Record Set: Order

      • Clear NOT check box

      • Validation Template: Lines Exist

      • Clear Seeded check box

      • User Message: the order has lines

Processing Constraints Usage

As you use Order Management, processing constraints are evaluated for any entity you try to cancel, delete, create, split, or update. If you are trying to modify an order line, Order Management evaluates the processing constraints for the Line entity.

Using Processing Constraints

Versioning

To set up Automatic Versioning, you must set up processing constraints to enable a select attribute update to autogenerate versioning

Defining Validation Templates

Order Management provides you the ability to define your own validation conditions by the use of validation templates. A validation template names a condition and defines the semantics of how to validate that condition. Validation templates can be used in the processing constraints framework to specify the constraining conditions for a given constraint. These conditions are based on:

API based validation templates are not available if constrained entity is different from the entity for which the validation template has been defined (or the Validation templates are not available even if the record set being used is anything other than the primary key record set).

For example, API based Validation template Pick Released has been set up for entity Order Line. If you set up a constraint for attribute Ship To on Order Line, the validation template Pick Released is available but for a constraint on attribute Ship To on Order Header, Pick Released will not be available.

For attribute Ship To on Order Line, if the constraint condition uses any record set (ATO Configuration, for example) other than the primary key record set Order Line, the validation template Pick Released will not be available.

To define a validation template:

  1. Navigate to the Validation Templates window.

    Validation Templates Window

    the picture is described in the document text

  2. Select an entity the condition is defined for in the Entity field.

  3. Enter a Template Name for the condition.

  4. Enter a name in the Short Name field for the condition.

  5. Optionally, enter a Description for the constraint condition.

  6. Select the Validation Type to be performed by the condition. Select from:

    1. WF: (validation is based on the workflow status of this entity):

    • Select the Activity for the condition

    • Select the Activity Status for the condition. Select from: Active, Complete, Error, Notified, and Suspended

    • Select the activity Result for the condition

    • Save your work

    1. API (validation is completed through an Application Program Interface):

    • Select the PL/SQL Package you wish to interface with the constraint condition

    • Enter the Procedure name of the API

    • Save your work

    1. TBL (validation is based on the values of database columns on this entity):

    • Select the Attribute Column name on the entity for the constraint condition

    • Select the Validation Operation for the constraint condition. Select from: = (Equal To), <> (Not Equal To), Is NULL, Is Not NULL

    • Select the Value String you want to validate against the value of the column

    Note: You can add more than one attribute, value pair, otherwise all pairs will be added together in the validation.

  7. Save your work.

  8. When you have created new validation templates or record sets, you will need to submit the Create Validation Packages concurrent program from the Tools menu to submit a concurrent request to create a validation package for all new or modified validation templates and record sets that may constitute a permitted validation combination. After the request completes, all validation templates that processed successfully will be visible in the list of values in the Processing Constraints window.

    For information on Seeded validation templates, please see appendix E for a complete listing.

Defining Record Sets

The Records Sets feature in Order Management is used to define and maintain record set definitions for processing constraints. A record set is a set of records that are bound by common attributes such as ship sets. You can define constraining conditions and specify a record set to be validated for a given condition as defined by its validation template.

To define a record set:

  1. Navigate to the Record Sets window.

    Order Management Record Sets

    the picture is described in the document text

  2. Select the Entity for which you are defining a record set.

    The Seeded check box is enabled if the system automatically defines the name of the record set. This check box is non updatable.

  3. Enter the name of the Record Set.

  4. Enter the Short Name for the record set.

    Note: You cannot modify the Short Name once it has been entered.

  5. Optionally, enter a Description for the record set.

    The Based On Primary Key check box is used to indicate the record set that is based on the primary key columns for the entity. There can only be one primary record set per entity. These records are seeded and cannot be updated.

  6. Select the name of the columns that should be matched from the validated record in the Matched Columns For Record Selection region.

    For example, if you define a Ship Set record set, the matching columns will be the Header ID and the Ship Set number.

  7. Save your work.

  8. Select the Create Validation Packages concurrent program from the Tools menu to submit a concurrent request to create a validation package for all modified validation templates and record sets that may constitute a permitted validation combination.

    Only after the request completes, the created validation template is visible in the list of values in the Processing Constraints window.

  9. Save your work.

Define Defaulting Rules

You can create and modify defaulting rules to improve the efficiency and accuracy with which you enter orders. You can define the rules to determine the source and prioritization for defaulting order information to reduce the amount of information you must enter manually in the Sales Orders window. For most fields, you can assign one or more defaulting sources in a priority sequence, or, if the default is always the same, you can define a constant value. This is step twenty-five of the Order Management Setup Steps.

Updates to defaulting rules take effect once the Defaulting Generator concurrent program has been submitted for the application and the program successfully completes for the entity combination modified. Existing orders are only affected by updates to defaulting rules if you update an attribute on an order that was included in the modified defaulting rule. If you do not perform a change to an existing order that uses the modified defaulting rules, thus activating validation of defaulting, the order is not affected by the modification.

Note: Seeded defaulting rules can be disabled, but not modified.

If you wish to modify a seeded defaulting rule, disable the seeded defaulting rule condition, and then create a copy of the seeded defaulting rule and include your changes in the copied defaulting rule.

To query entities and attributes:

  1. Navigate to the Defaulting Setup - Entity Attributes window.

    Defaulting Setup-Entity Attributes window

    the picture is described in the document text

    Entity Region

  2. Application: The Application field displays the application context for the entity displayed. For Oracle Order Management, the value is “Oracle Order Management”. This field is non updatable.

  3. Entity: The Entity field displays the name of the object for which defaulting rules and conditions are being defined such as the order line. For Order Management you have the following options:

    • Order Header

    • Order Line

    • Order Payment

    • Line Payment

    Note: Defaulting rule creation is not supported for the sales credit entity and the price adjustment entity.

    Note: Defaulting rules can be created for Releases only. Sales Agreements have several hard coded defaults in place but does not support the defaulting framework.

    Attribute Region

    The Attributes Region displays all the entity attributes for which defaulting rules can be defined. You are NOT allowed to enter new records here.

  4. The Defaulting Sequence field enables a user to assign the sequence (priority) number in which this attribute should be defaulted.

    Note: Attributes with identical sequence numbers are defaulted in alphabetical order.

    e.g. If the attribute Contact has a sequence number of 1 and the price list has a sequence number of 1, then the Contact defaults before the price list.

  5. The Attribute field stores the name of available attributes. Values are currently displayed based upon the entity selected.

  6. The Include in Building Defaulting Conditions check box indicates whether an attribute can be used in defining conditions for the entity selected.

    Note: The Include in Building Defaulting Conditions check box is for display purposes only, and is not available for update.

  7. Save your work.

    The Defaulting Condition Templates button enables you to define defaulting template and conditions for the application/entity combination displayed on the defaulting rules setup window. Selecting this button will take you to the Defaulting Condition Validation Templates window.

    The Defaulting Rules button enables users to define defaulting rules for the attribute selected. Selecting this button will take you to the Attribute Defaulting Rules window. For more information on defining or updating defaulting sourcing rules, see the Define Defaulting Rules section.

    Select the Defaulting Condition Templates button to define the defaulting condition for this entity.

    Note: The template that appears after selecting the Default Condition Template button is based upon current values displayed in the Application and Entity field on the Defaulting Setup window.

To define Defaulting Condition Templates:

  1. Navigate to the Defaulting Conditions Validation Templates window.

    Defaulting Condition Validation Templates Window

    the picture is described in the document text

  2. Defaulting conditions enable you to define conditions that can be used to dictate when an attribute is sourced and defaulted. Select an existing condition name if you wish to update the associated validation rules or add a new condition name with associated validation rules.

  3. In the Description field, enter a brief description of the condition.

    Note: A generic condition of Always is seeded for each entity. Use this condition to define generic defaulting rules

  4. The Seeded check box will be checked for seeded conditions. This field is protected against update. You cannot update seeded conditions or validation rules associated with seeded conditions, however, you can disable seeded conditions and create your own.

    In the Validation Rules Region, enter the validation rules based on the attribute values of the above entity. For example, standard orders could have the order type Standard. Order type = Standard.

  5. In the Group Number field:

    • For conditions that should together evaluate to TRUE (AND conditions), enter the same group number

    • For conditions that should together evaluate to OR (OR conditions), enter a different number for each record

  6. Select the Attribute name, such as Contact.

  7. Select the validation operation: Select from:

    • (>) Greater Than

    • (<) Less Than

    • (>=) Greater than or Equal to

    • (<=) Less than or Equal to

    • (=) Equal

    • (!=) Not Equal

  8. Enter the Value String of the attribute that you want to validate against.

  9. Navigate to the Defaulting Setup - Entity Attributes window.

    The Attribute name displays in the Attribute field. Descriptive Flexfield attributes will not be displayed.

  10. Save your work.

    Select the Defaulting Rules button to define your defaulting rules.

To define defaulting rules:

  1. Navigate to the Attribute Defaulting Rules window.

    Attribute Defaulting Rules Window

    the picture is described in the document text

    Defaulting Conditions Region

  2. Enter a value in the Precedence field to determine the precedence when resolving multiple TRUE defaulting conditions.

    Note: If more than one defaulting condition is valid, the conflict is resolved by internally ranking conditions using the Precedence value.

    For example, defaulting condition Standard Order has a precedence value of two and Copied Order has a precedence value of one. If an order is standard and a copied order, then the defaulting condition with higher priority, Copied Order, is used initially. If your conditions for Copy Order do not return a default, conditions for Standard Order will be evaluated.

  3. Select a Defaulting Condition from the List of Values and then enter the defaulting rules to be used if this defaulting condition is TRUE.

    Note: The Always condition should be the last in this sequence as it would always evaluate to True and no other defaulting conditions would be evaluated.

  4. Select the Enable check box if you wish to enable the defaulting condition. If this check box is not selected, the defaulting condition is disabled and the rules and condition associated with this condition are not used in default possessing.

  5. The check box for the field Seeded cannot be updated. This value is seeded by Order Management. For seeded Order Management defaulting conditions, you are unable to update or delete any fields except:

    • The Precedence field on the defaulting rule condition

    • The Enable check box. You can disable seeded Order Management defaulting rules.

  6. Within the Default Sourcing Rules region, select the priority sequence in which you want to retrieve the default for this attribute.

    The defaulting process searches for a default for your attribute by evaluating defaulting rules in ascending order.

  7. Select the defaulting source type. The defaulting source type determines data entry in the Default Source/Value field.

  8. Based on the default source type selected, either select the default sources or enter default values in the Default Source/Value field.

    The table below describes Order Management Source Types and the appropriate action required by a user.

    Order Management Source Types and Actions
    Source Type Action required
    Constant Value Enter the default constant value.
    Application Profile Select the profile option from where you want to retrieve the default value.
    Same Record Select the attribute on the same record from where you want to retrieve the default value.
    Related Record Object--Select the related object.
    Attribute--Select the attribute on the related object from where you want to retrieve the default value.
    System Variable Expression--Enter the system expression to be evaluated to obtain the default value. (E.g. System Date.)
    PL/SQL API You can write a custom API to obtain a default value if the value cannot be obtained using other source types such as, the default order number from a sequence.
    Package--Enter the PL/SQL package name.
    Function--Enter the function name.
    Object--Optionally, enter the name of an object to be passed to this API.
    Attribute--Optionally, you can also enter the name of an attribute to be passed to this API. (See the PL/SQL API Procedure below.)
    WAD Attribute
    WAD Object Attribute

  9. Save your work.

Caution

If defaulting rules or conditions are updated, the Defaulting Generator concurrent program must be run to generate new defaulting packages.

You may execute the Defaulting Generator concurrent program while users are still on the system, although the defaulting package may not generate successfully. This can be due to the package currently being called by other users who are processing orders on the system. Common errors within the output log file for this concurrent program may contain text that a time-out occurred while waiting to lock object.

If defaulting packages do not generate successfully, you must choose to run the program at a later time, or to have users briefly log off the system while defaulting packages are regenerated.

Note: When you are creating or updating defaulting rules while online patching is in progress, the application may display an error message such as - This feature is not available during online patching. Please wait until the current online patch has completed and then try again. If this happens, then you must abort the change and try creating or updating the defaulting rule after the current online patching cycle has completed. This prevents data corruption.

Defaulting Rule Example

Here is an example of a defaulting rule that you can define so that a specific Price List will default to the Sales Order Header window. You may also define a sequence (priority) in which you want Order Management to search for a Price List.

The default sequence can also be complex.

For example, look on an Agreement for a Price List, followed by the Invoice To Location, then the Ship To Location, then the Customer, and finally, the Order Type. If Order Management still does not find a price list for any of the source locations listed (Invoice-To, Ship To, Customer, Order Type), you can have a Constant Value default, such as 1998 USA Prices, which you enter in the Value field of the Attribute Defaulting Rules window.

The table below corresponds to the example stated above.

Example of Complex Default Sequence
Sequence Defaulting Sources Source Field or Value
1 Related Record Agreement.Price List
2 Related Record Invoice To Location.Price List
3 Related Record Ship To Location.Price List
4 Related Record Customer.Price List
5 Related Record Order Type.Price List
6 Constant Value 1998 USA Prices

Note: Oracle Order Management does not recommend that you define any overly complex or recurring defaulting rules.

PL/SQL API Procedure

The signature of the PL/SQL API is:

 (p_database_object_name VARCHAR2


,p_attribute_code VARCHAR2)


return VARCHAR2

The table below describes Order Management entities, their associated entity code, and the database object called when the entity is processed within Order Management.

Order Management Entities, Entity Code, and Database Objects Called
Entity Entity Code Database Object
Order Header HEADER OE_AK_ORDER_HEADERS_V
Order Line LINE OE_AK_ORDER_LINES_V

For example:

Function to default order number from a sequence based on the order type:

Function Get_Order_Number(p_database_object_name IN VARCHAR2,

p_attribute_code IN VARCHAR2)

return varchar2

IS

l_header_rec OE_AK_ORDER_HEADERS_V%ROWTYPE;

BEGIN

-- Getting the defaulting global record

l_header_rec: <= ONT_Header_Def_Hdlr.g_record;

-- for internal orders, use this sequence but for all other order types use the -- sequence for STANDARD orders.

if l_header_rec.order_type_id = 1 then

return to_char(OE_INTERNAL_ORDERS_S.nextval);

else

return to_char(OE_STANDARD_ORDERS_S.nextval);

end if;

END;

Note: The PL/SQL API should only access global record for entity being defaulted else rules might not work as expected. For e.g. API should not access values on ONT_Header_Def_Hdlr.g_record if rule is for an order line attribute. Instead reference values from ONT_Line_Def_Hdlr.g_record.

Deleted Seeded Defaulting Rules

In a multi-org environment, you can no longer specify Order Type and Salesrep at the Customer Account using the Receivables Customer Form. The multi-org upgrade copies the values for these attributes from the customer account to the site use (provided there is no value there) and clears them from the account level.

Therefore Order Management seeded defaulting rules which defaulted Order Type and Salesrep from the Customer are deleted. The sources (Customer.Order Type and Customer.Salesrep) are now disabled. To view the deleted defaulting rules, run the Upgrade Script Report, ontexc16.sql, to get the ontexc16.lst output.

Related Topics

Defaulting Rules

Cascading

Define Credit Checking Rules

Define your credit checking rules. This is required if you plan on performing any type of order credit checking. This is step twenty-six of the Order Management Setup Steps.

Defining Credit Profiles

Organization Credit Profiles are a set of criteria that define an operating unit's credit policy for credit control and order credit checking. Credit Profiles include the credit limit and pertinent data needed to determine total credit exposure for orders undergoing credit checking.

Credit Profile Limits Hierarchy when performing credit checking:

The Credit Profile window enables users to create and maintain credit information for Operating Units and Item Categories.

Operating Unit Default Credit Profiles can assist in further defining your credit policies by providing global defaults if no other information is present during credit checking.

To create a new credit profile, users must specify what type of credit profile to create, and depending on the credit profile type chosen, appropriate fields within the window become updatable or non-updatable.

Credit Profile Types

To Define Credit Profiles:

  1. Navigate to the Define Credit Profiles window.

    Credit Profiles Window

    the picture is described in the document text

  2. . Valid Values for Credit Profile Type are:

    • Item Category

    • Operating Unit Default

    Based upon the Credit Profile Type you chose, certain fields become protected or non-updatable.

    Note: If Credit Profile Type = Operating Unit Default, the Item Category field is disabled.

    If Credit Profile Type = Item Category, the Overall Credit Limit field is disabled.

    Enter remaining fields that require a value, or update any fields that contain a default value based upon the Credit Profile Type selected:

    • Operating Unit:

      Select an Operating Unit name from a list of values if you are defining a Operating Unit Default Credit Profile.

    • Item Category:

      Select an Item Category name from a list of values if you are defining an Item Category Credit Profile.

    • Effective Date From/ Effective Date To:

      Select the Effective Date From and Effective Date To for your Credit Profile.

      Note: When defining Credit Profiles for Operating Unit Default and Item Category, the Effective Dates From/To cannot overlap previously defined Credit Profiles for the same Operating Unit Default or Item Category, regardless of the currency.

    • Tolerance:

      Enter a numeric value in the Tolerance field. Tolerance values are used to calculate extended exposure limits during credit checking.

      For example, supposed you enter a value of 5 for Tolerance, and an Credit Limit of $10,000 USD. During credit checking, the exposure credit limit would actually be $10,500 USD. ((Tolerance + 100)* Credit Limit / 100).

    • Currency:

      Select a value in the Currency field to limit the Credit Profile to a specific currency.

    • Order Credit Limit:

      Enter a value in the Order Credit Limit field, based upon the Credit Profile Type. New orders may not exceed the value entered in the Order Credit Limit field if the checking processing defaults to the operating unit level.

    • Overall Credit Limit: Enter a value in the Overall Credit Limit field for a Operating Unit Default Credit Profile Type. Total exposure within an operating unit for the particular customer may not exceed the value entered in the Overall Credit Limit field if credit checking processing defaults to the operating unit level.

    The following fields are for future use and are for information purposes only. Values that are ignored during the credit checking process are:

    • Credit Check

    • Credit Hold

    • Credit Rating

    • Next Review Date

  3. If you wish to enable multi currency credit check, you must assign Credit Usage Rule Sets to your Credit Profile. Select the Assign Rule Set button. The Assign Rule Set button is only enabled for the following Credit Profile Types:

    • Item Category

    • Operating Unit Default

    To assign Credit Usage Rules to Customer or Customer Sites Credit Profile Types, you must use the Assign Credit Usage Rules window.

  4. Save your work.

Defining Credit Usage Rule Sets

The Define Credit Usage Rules window enables a user to create and maintain credit usage rule sets that can be assigned to Credit Profiles.

Credit Usage Rule Sets define the set of currencies that will share a predefined credit limit during the credit checking process, and enable the grouping of currencies for global credit checking. Usage Rules Sets ensure that if credit checking is enabled, that all transactions for specified currencies go through the currency conversion process and are summarized by currency prior to the credit checking process.

Usage rule sets consist of at least one usage rule/currency combination, and once a rule set is assigned to an Oracle Entity, the rule set provides processing defaults for determining credit availability during multiple currency credit checking processing routines.

To define credit usage rule sets:

  1. Navigate to the Define Credit Usage Rules window.

    Define Credit Check Usage Rules Window

    the picture is described in the document text

  2. Enter a name for your rule set in the Usage Rule Set Name field.

  3. Select the Global Exposure box if you wish to enable the Usage Rule Set for global exposure (across operating units). By default, this box is unchecked (do not enable Global Exposure for the usage rule set).

    If you are unable to select the Global Exposure check box, submit the Credit Limit Usages Report. Review the report output and un-assign any usage rule sets with different Global Exposure options for the same credit profile.

  4. Select the value Currency in the Usage Type field.

  5. Enter a currency in the Currency field.

    The Currency field can contain any Currency Code currently defined. The Currency field may also use the lookup All Currencies to indicate the usage rule is for all currencies defined.

  6. Chose to exclude a specific currency for your usage rule by selecting the Exclude check box. The default is unchecked, or No.

    Note: If the field Currency has value of All, the Exclude check box is non-updateable.

  7. Save your work.

Warning: Given a customer with the following credit profiles:

The credit checking process for a transaction in FRF is determined by the credit check engine; perform multi-currency credit check if a Credit Usage Rule Set assignment has been defined.

Assigning Credit Usage Rule Sets

The Assign Credit Usage Rules window enables a user to assign credit usage rules sets for multiple currency credit checking to Credit Profiles.

To assign credit usage rules:

  1. Navigate to the Assign Usage Rules window. Order Management > Setup > Credit > Assign Usage Rules.

    Find Credit Profiles Window

    the picture is described in the document text

    Find Credit Profiles Window

    Before you can assign a Usage Rule Set to a Credit Profile, you must first select the Credit Profile Type and then locate the corresponding Credit Profiles.

    Certain query processing logic has been disabled within the Find Credit Profiles window;

    • If the value of the Credit Profile Type field is Profile Class, then the Operating Unit, Customer, Bill To Site, and Item Category fields are disabled.

    • If the value of the Credit Profile Type field is Customer, then the Profile Class, Operating Unit, and Item Category fields are disabled.

    • If the value of the Credit Profile Type field is Operating Unit Default, then the Profile Class, Customer, Bill To Site, and Item Category fields are disabled.

    • If the value of the Credit Profile Type field is Item Category, then the Profile Class, Operating Unit, Customer, Bill To Site, and Overall Credit Limit fields are disabled.

    Once you have entered your search criteria, select the Find button to either locate your existing credit profile usage rules or to define new usage rules for an existing profile.

    Assign Credit Usage Rules Window

    the picture is described in the document text

  2. The data appearing in the upper region of the window defaults from the Credit Profile you have queried. This information is protected against update.

  3. The multi-row section of the Assign Usage Rules widow enables you to select Credit Usage Rule Sets to use with the credit profile.

    You select a Name from the List of Values, and the included and excluded currencies fields will display currencies that the usage rule set consists of. These values are protected against update from this window.

    For detailed field information, see Defining Credit Profiles, Step 3 and 4.

  4. Save your work.

Defining Credit Check Rules

Overview

Oracle Order Management credit check rules enable you to determine what credit checking criteria is used for credit exposure during the credit checking process. The transaction types determine when credit checking actually occurs, and when used in conjunction with credit checking rules, define your credit checking process.

For example, you can define credit checking rules that utilize pre-calculated exposure information when comparing a customer's current order amount against their overall exposure. If the order transaction type utilizes this rule, and the order fails during the credit check process, then it is automatically placed on credit check hold. You can define as many credit checking rules as you need, and if you inactivate a credit checking rule, then you must also remove it from any order types that use it.

Additionally, you can include in or exclude from your credit check rule some or all of your open accounts receivable balances, and some or all of your uninvoiced orders.

Oracle Order Management uses the currency of the order you are credit checking to determine which credit limits to use in credit checking calculations. Oracle Order Management only includes orders and invoices in the same currency as the order you are credit checking when calculating a customer's outstanding credit balance, unless you have set up multiple currency credit checking.

You can also include or exclude returns based on your credit check rule definition. However, this should be used only if you are using return lines with credit memos.

You can define credit tolerance limits for order and line level credit checking rules to honor manually released holds of booked orders for example holds released using the Sales Order window in Oracle Order Management or released by credit manager using Oracle Credit Management. See: Releasing Holds, Oracle Order Management User's Guide.

If the increase in order amount is within the credit tolerance limits, then the application skips credit checking for the booked orders on which holds were previously released manually and no active credit check failure hold exists on the order at the time of update. Additionally, for these orders, if you change the Bill to Site, keeping the selected site for the same customer and if you have not defined the credit limits for the new site, then the application honors the tolerance limits and does not redo credit checking. When you manually release the hold on any line of the order, the application honors the tolerance limits for all lines of that order irrespective of hold or release status of other lines in the order. The credit check process considers the tolerance limits over the value of the Initiate Credit Check at Cancellation system parameter. It does not consider the value of this system parameter for credit check rules when you specify the tolerance limit.

If you are an existing user, then you can modify your existing credit check rules to include the Tolerance fields or create new credit check rules with these Tolerance fields.

Besides defining your credit exposure composition, the credit check rule also determines:

Credit Limits for Credit Checking and Rules Summary

  1. When the Credit Check flag is turned off at the site level that pertains to the Bill-To address, there will be no credit checking for orders for this Bill-To site. It does not roll up to the next level to get the credit limits.

  2. If the Credit Check flag is turned on at the site level, and both overall credit limits and order credit limits are all NULL or BLANK, then the limits for a customer who owns that Bill-To site will be automatically considered.

  3. If the Credit Check flag is turned on at the customer level, and both overall credit limits and order credit limits are all NULL or BLANK, then the application rolls up to the next level in the party hierarchy (if any). Otherwise, use the Operating Unit Credit profile option. Note that party profiles are used only if Oracle Credit Management is set up. If not, from the customer level navigate to the Operating Unit.

  4. If the Credit Check flag is turned on at each level, and there is only one field left NULL or BLANK (for example, Order Limit is null but overall exposure has a value), then this NULL or BLANK field is treated as unlimited and it does not roll up to next level.

  5. If the last level reached with the Credit Check flag enabled has both overall and order credit limits set as NULL or BLANK, it means no credit checking should be performed. If the Credit Check flag is enabled and order credit limit is not NULL or BLANK, then a credit check will be performed at the item category level.

  6. If the Credit Check flag is disabled for item category or if it is enabled and both order credit limit and overall credit limit are NULL or BLANK for item category, then there is no credit checking at the item category level, but credit checking is performed for the site-customer-(party)-OU level based on the rules. If the Credit Check flag is enabled and at least one of the order credit limit and overall credit limit fields are not NULL or BLANK, then a credit check is performed at the item category level.

Performance Note

To improve performance you can enable the use of pre-calculated exposure. By utilizing this option, the credit check engine uses summary balance details stored in a periodically updated summary table.

The update is done by running a concurrent program which accesses Oracle Order Management and Oracle Account Receivable transactional tables. This program should be scheduled to run periodically based on your specific business needs. You should also run this concurrent program when you have done major changes in your set up or transactional data (for example merge customers, incorporate transactions from external systems, change transaction status using customized programs, etc.).

To define a credit check rule:

  1. Navigate to the Credit Check Rules window.

    Credit Check Rules Window

    the picture is described in the document text

  2. Enter a name for your credit check rule.

  3. Optional. Enter the relevant dates in the Effective Start Date and Effective End Date fields.

    Options Tab

  4. Select from the following entities to perform credit checking.

    • Sales Order

    • Sales Order Line

      Note: If you select Sales Order Line, the Use Pre-calculated Exposure check box will be selected and protected against update

      If you select Sales Order Line, you are limited to the system generating header level credit holds only. The Credit Hold Level field will default to the sales order and is protected against update.

  5. Select the credit hold level for your credit rule:

    • Sales Order: Sales Order (order level) credit check is performed for the header Bill To site. Sales Order level credit checking provides backward compatibility with previous credit check versions. When credit checking rules are defined using Sales Order at the credit check level, the credit check engine will examine order totals and evaluate credit exposure against the credit profile attached at header level.

      Holds will always be applied at header level.

      Use order level credit check when order lines always have the same Bill To Site as the order header.

    • Sales Order Line: Sales Order Line (line level) credit check is performed for the order line Bill To Sites. The credit check engine will group all order lines belonging to the same Bill To Site and check available credit for each Bill To Site. When an order line fails credit check, any remaining lines grouped with the same Bill To Site are placed on hold.

      Holds can be placed at either the order or the order line level when you use line level credit checking.

      Use line level credit check when sales order lines are attached to different Bill To Sites and you want to use the credit profile defined at that level. Additionally, you can use line level credit check when you have defined customer relationships in your system and actively use them within Oracle Order Management. Using customer relationships, you can create sales orders with order lines attached to different Bill To Sites owned by different customers.

      Order header level credit check uses header level information ignoring different bill-to sites detailed at the line. Credit check uses the credit profile attached to the customer Bill-to site defined at order (header) level. Credit check at the order header level will use order totals and will evaluate credit exposure for the credit profile attached at header level, and holds are always applied at header level.

    Special Considerations for Credit Hold Level

    • If you update the Credit Hold Level from Sales Order to Sales Order Line, a message appears indicating that existing sales order credit holds will need to be released manually. Select Yes to continue or No to not commit the update.

    • If you update the Credit Hold Level from Sales Order Line to Sales Order, a message appears indicating that existing sales order line credit holds will not be released automatically. Select Yes to continue or No to not commit the update.

  6. Override Manual Release: This check box enables an order or line which had failed credit checking and then was manually released to become eligible for additional credit check processing. The options are Yes or No:

    • Yes: If you select Yes, manually released holds will be overridden. You must also enter a value in the field Days to Honor Manual Release.

    • No: If you select No, manually released holds will be honored. The field Days to Honor Manual Release is non-updatable.

  7. If you select the Override Manual Release check box, then you must specify a value in at least one of the following fields:

    • Days to Honor Manual Release: If you enter a value in this field, then the credit check process validates if the release date is within the interval defined by the value in Days to Honor Manual Release. If the value is within the defined range, then the application honors the manually released holds and does not perform additional credit checking. If the value is not within the defined range, then credit check can occur again and credit check holds can be applied if the order or lines fails the credit check process.

    • Tolerance Percentage: This field enables you to define the tolerance threshold in percentage terms within which an increase in order amount does not retrigger credit checking if the order was previously placed on credit check hold and then the hold was released manually. In this case, the application calculates the tolerance amount at runtime from the released order amount and tolerance percentage specified in the credit check rule.

    • Tolerance Currency and Tolerance Amount: If you enter the currency, then you must enter the tolerance amount. These fields enable you to define the absolute tolerance threshold amount within which an increase in order amount does not retrigger credit checking if the order was previously placed on credit check hold and then the hold was released manually. If you enter tolerance percentage and tolerance amount, then the application considers the lesser of the two values. For example, if the tolerance percentage is 10% and the tolerance currency and tolerance amount is USD 1000, then the application does not redo credit checking for an order that was previously placed on credit check hold and then manually released as long as the increase in the order amount is lesser than 10% of the order amount or USD 1000.

      Note: If you are using different currencies for tolerance amount and order currency, then ensure to set up currency conversion rates between the credit tolerance amount currency and order currency.

    Note: If you specify the Number of Days to Honor Release and the tolerance limit, then the application considers the appropriate field for validation based on the activity. For example, when the order is being updated, the application considers tolerance values and during picking, packing, or shipping activities, the application considers the number of days to honor hold release. You can define a credit check rule that meets booking and shipping validations.

  8. Select the conversion type to perform credit check using your credit rule. The list of values depends on the values that you define in Oracle General Ledger Conversion Rate Types window.

  9. Select the Check Item Categories check box for your credit rule to perform credit check for sales orders by Item Categories defined for Oracle Order Management.

  10. Select the Send Hold Notifications check box to send hold notifications whenever a credit hold is placed for a sales order or order line. The notification is sent to the creator of the order.

    Determine the type of credit exposure to use when defining your credit check rules by selecting the Exposure tab in the Credit Check Rules window.

    Exposure tab in the Credit Check Rules Window

    the picture is described in the document text

    Exposure Tab

  11. Select the Use Pre-calculated Exposure check box for your credit rule to perform credit checking against pre-calculated exposure summary tables. Additionally, party level credit checking is supported only when the Use Pre-calculated Exposure check box is selected in the credit check rule. Run the Initialize Credit Summaries concurrent program periodically to get the correct exposure values for the party. See: Initialize Credit Summaries Table Concurrent Program, Oracle Order Management User Guide.

    • When the first credit check rule that has the Use Pre-Calculated Exposure check box selected is successfully saved, the following message will display:

      This credit check rule uses pre-calculated exposure. Please run the Initialize Credit Summaries program to update the pre-calculated data.

    • If the Use Pre-calculated Exposure check box is selected and the Include Open Receivables Balance check box is selected, then Open Receivables Days is protected against update and is NULL.

    • If the Use Pre-calculated Exposure check box is selected and the Include Uninvoiced Orders check box is selected, then Scheduled Shipping Horizon Days is protected against update and is NULL.

    • To enable online credit checking, ensure that the Use Pre-Calculated Exposure check box is not selected. Online line level credit checking considers current order amount while calculating exposure based on real time data. Additionally, the application considers party and party hierarchy credit checking for line level online credit checking.

  12. Select the Include External Credit Exposure check box to include external exposure details imported into Oracle Order Management during the credit checking process.

    When an Oracle Order Management sales order is credit checked, the exposure data from the external system is included in the overall exposure check. The default value for this check box is deselected (exclude external exposure details when performing credit checks).

    Receivables Balance Region

  13. Select the Include Open Receivables Balance check box for your credit rule if you want to include open receivables balances.

    You must enable either the Include Open Receivables Balance check box or the Include Uninvoiced Orders check box in your credit check rule. You can activate both, but you cannot toggle both.

    If you select both the Pre-calculated Exposure and Open Receivables Balance check boxes, then you cannot specify the number of days in the field Open Receivables Days.

  14. If you enabled Include Open Receivables Balance in your credit check rule, then you can indicate whether to Include Payments at Risk when calculating a customer's outstanding balance.

    Receipts at risk are remitted receipts that have not been cleared, or discounted (factored) receipts that have not been risk eliminated. If the performance of credit check requires improvement you can toggle this option off.

  15. If you enabled Include Open Receivables Balance, then enter a value to indicate the range of dates for open receivables you want to include for your credit check rule.

    • Negative Number: Includes past due, current, and future open receivables up to X days beyond the current date

    • Positive Number: Includes open receivables with invoice dates X days earlier than the current date

    • No Value: Includes all open receivables

    Uninvoiced Orders Region

    If you do not select the Include Uninvoiced Orders check box, then you cannot select any check boxes within the region.

    Important: If an order line has been interfaced to the Receivables interface table but hasn't been invoiced yet, the Order Management credit check engine will include this line amount as part of the uninvoiced order amount. If your system enables credit checking and your Receivables Interface table can potentially contain large volume of data, it is recommended that you create a custom index on RA_INTERFACE_LINES_ALL table ORIG_SYSTEM_BILL_CUSTOMER_ID column.

  16. Select the Include Uninvoiced Orders check box to include uninvoiced orders for your credit rule.

    If you enabled Include Uninvoiced Orders:

    • Select the Include Freight and Special Charges check box to include them for uninvoiced orders when performing credit checks.

    • Select the Include Tax check box to include tax information for uninvoiced orders. Credit checking calculations on open receivables always include tax amounts and are not affected by the Include Tax option. If the performance of credit checking requires improvement, then you can toggle off this option.

    • Enter the number of scheduled shipping horizon days (SSHD) for your credit rule for uninvoiced orders that must be included in your total credit exposure when performing credit checking.

      For example, if you enter 45, then the total exposure includes only uninvoiced orders scheduled to ship within 45 days of the current date. Orders scheduled to ship after 45 days are not included when calculating exposure.

      Note: If the Include Uninvoiced Orders check box is not selected, then you cannot update the Scheduled Shipping Horizon Days.

    • Select the Scheduled Lines Only check box to include only the scheduled lines to calculate exposure.

      Note: The application also calculates the exposure for bill only lines, service lines, and drop ship lines irrespective of the selection of the Scheduled Lines Only check box.

    • Select the Scheduled Lines Only check box and enter a value in the Scheduled Shipping Horizon Days (SSHD) field to calculate the exposure within the specified SSHD days. Because you cannot schedule the bill only lines and the return order lines, the exposure for these lines is calculated when the Scheduled Lines Only or the Shipped Lines Only check box are selected.

    • Select the Shipped Lines Only check box to include only the shipped lines during the credit check process of uninvoiced orders. For the lines that are not eligible for shipping, the application considers fulfilled lines when calculating exposure.

      Note: If you select the Scheduled Lines Only check box, then you cannot select the Shipped Lines Only check box and vice versa.

    • Select the Include Orders Currently On Hold check box to include orders on hold within the exposure calculation for your credit rule.

  17. Enter the number of days in the field Maximum Days Past Due to allow an invoice to be past due before holding the customers' orders. During the credit checking process, Oracle Order Management will verify that no invoices for the customer have been past due beyond the number of days you specified in this field. If there are any such past due invoices, then the order is placed on credit hold.

  18. Save your work.

Deactivating Credit Checking

There are three ways to deactivate Credit Checking on an order:

Deactivating Credit Checking does not automatically release orders previously on credit hold. However, the next time you attempt to Book, Pick Release or Purchase Release (for drop shipments), Pack, or Ship Confirm an order which utilizes a Order Management Transaction type that enables credit checking to occur at the specified order points, or you perform an order change that trigger credit checking in the Sales Orders window, Order Management will releases the credit check hold if the order or line meets the requirements for successful credit check.

Related Topics

Payment

Sales Orders

Holds and Releases

Oracle Payments Processing

Order Management provides you with the ability to record credit card information through the Sales Orders window and obtain authorizations for credit card transactions using Oracle Payments. You can also set up the security feature to mask confidential card holder information.

Order Management tracks the following credit card information at the order header:

Warning: Oracle Payments processing can only occur if you are using an order type that has a credit checking rule and the rule will perform the authorization at Booking or Shipping.

Risk Management

Oracle Payments offers a risk management feature to identify high risk transactions by Oracle Risk Management. This feature enables merchants and e-commerce service providers to manage the risk when processing transaction through the internet. Oracle Risk Management enables you to define any number of risk factors to verify the identity of your customers, assess their credit rating, and manage risk in a secure on-line environment.

You will receive the customer's risk score, which is based on the risk factors, scores, and formulas that are setup in Oracle Risk Management.

If the risk factor score exceeds the risk score threshold, the order is automatically placed on hold. High risk holds include credit card authorization and high risk failures. If a customer's transaction receives both authorization failures, the authorization failure hold will be applied. Both hold types can be removed manually and the order will continue through the order cycle process.

Order Management authorizations use the default risk formula that you have set up in Oracle Payments. Below is a list of risk factors that can be used by Oracle Payments:

Quantity Changes and Cancellations

Authorizations occur at the sales order header for the total order amount less any amounts covered by commitments. Return lines are not included in the order amount to be authorized.

When an authorized order is changed, Oracle Payments Processing re-authorizes the credit card if the existing authorization has expired. Estimated expiration of the authorization is calculated by Oracle Payments. Actual expiration of authorization varies by card issuer. Because these incremental amounts may not be authorized, you might not be able to collect those funds.

To perform authorization of these incremental amounts, do either of the following:

Manual and Online Authorizations

You can choose to obtain manual authorizations and enter the authorization code in the Authorization Code field in the Sales Orders window.

Security

Order Management enables you to mask cardholder information including credit card numbers and authorization codes by setting the OM: Credit Card Privileges profile option. Only the last four digits of the credit card number are displayed if the profile option is set to Limited or None. If the profile option is set to All, the full credit card number is displayed.

Drop Shipments

Order Management provides the ability to obtain credit card authorizations for drop shipments. Authorizations are obtained at the booking and purchase release activity of the drop shipment order.

Related Topics

Drop Shipments

Payment

Define Automatic Holds

You can define holds to halt processing of your sales documents as well as order and return lines. This is step twenty-seven of the Order Management Setup Steps. Because orders and returns are not affected by holds until they are applied, you can define all the holds you use in your business at once. You can define holds that are effective only at certain steps of the order or line workflow and holds that apply regardless of the stage in the order's flow.

For example, you may want to apply an item hold to prevent order lines for a particular item to be released for shipment. Any orders that are not ready for shipment or any orders that have already been shipped are not affected by this hold. You can also define a hold that affects all orders, no matter where the order is in its flow. When this type of hold is applied, it is effective regardless of the order's position in the flow.

For each hold, you can specify hold security by responsibility to control which responsibilities have authority to apply and/or remove the holds you define. Holds can be defined to be specific to pick, pack, ship, or invoice interface activities.

Order Management Hold database tables are striped by organization ID. Therefore, you will need to define holds for each operating unit within your enterprise structure. However, hold type quickcodes only need to be defined once.

The table below describes Order Management seeded Hold Names, the associated Hold Type, and a description of the hold source.

Order Management Seeded Hold Names and Associated Hold Type and Description of the Source
Hold Name Hold Type Description
Configurator Validation Hold Configurator Validation Automatically applied to order lines that fail Configurator Validation.
Credit Card Authorization Failure Electronic Payment Automatically applied to orders if credit card authorization request to Oracle Payment fails.
Credit Card High Risk Electronic Payment Automatically applied to orders if risk score determined by Oracle Payments is greater than the value of the risk factor threshold.
Credit Check Failure Credit Check Automatically placed if credit check rule evaluation fails on orders setup to be credit checked.
Credit Check Failure Credit Check Automatically placed if the Credit Hold box is selected on the customer record in AR.
GSA Violation GSA Violation Automatically placed on orders which are in violation of GSA.
NO pre-defined hold name for this hold type Order Administration Hold Reserved for you to define administration holds based on your business processes.
ePayment Failure Hold Electronic Payment This is for expected errors returned by Oracle Payments like invalid data
ePayment server Failure Hold Electronic Payment This is for unexpected errors returned by Oracle Payments, for example a failure to connect to the server.
Export Compliance Hold Import/Export Compliance This hold is applied when an order fails export compliance screening.
Pending Process Payment Hold Electronic Payment This is applied when process payments is deferred.
Promotional Line Promotional Hold Automatically placed on lines which exceed a soft modifier promotional limit.
Promotional Order Promotional Hold Automatically placed on orders which exceed a soft modifier promotional limit.

Note: Promotional Line/Order Holds functionality is only available if you have licensed and installed Oracle Advanced Pricing.

To define a generic hold:

  1. Navigate to the Holds window. Order Management > Setup > Orders > Holds

    Holds Window

    the picture is described in the document text

    Generic holds are placed at the order level. Order lines are considered implicitly on hold for an order that has a generic hold against it.

    You will not see hold information for generic holds at the order line level, only at the order header. The Apply to Order and Line check box is enabled if you enter a line level workflow activity. If you select the check box, then the application applies this line level hold at the header level also. The default value of this check box is unchecked so that existing behavior is maintained.

  2. Enter the Name and Description for the hold you want to create.

  3. Select a valid Hold Type. Hold Types are defined using the Order Management Quickcodes window. See: Quickcodes

  4. Workflow Item: Leave this field blank for generic holds.

  5. Workflow Activity: Leave this field blank for generic holds.

  6. Optionally, enter the Effective Dates for the hold to control when you can use this hold.

  7. Optionally, determine which user responsibilities have authority to apply and/or release holds by entering combinations of responsibilities, authorized actions, and effective dates.

    You can give some responsibilities the authority to apply a hold, other responsibilities the authority to release it, and others the authority to do both. If you do not specify a responsibility for a hold, any responsibility can apply or release it.

  8. Save your work.

To define an activity-specific hold

  1. Navigate to the Holds window. Order Management > Setup > Orders > Holds

  2. Enter the Name and Description of the activity-specific hold you want to create.

  3. Select a valid activity-specific hold Type.

    Order Management provides two standard hold types that are used for the GSA and Credit Checking features: GSA Violation Failure and Credit Check Failure. Order Management also provides the Configurator Validation hold type, which is used if you invalidate a configuration after booking and an order administration hold. Hold types are also provided for import/export compliance, ePayment and promotional limits. Define other hold types using quickcodes.

  4. Select the Workflow Activity for the hold.

    The workflow activity determines where in the order process the hold will be applied. At the line level, All other lines will be processed except for the line for which the hold is effective.

    The LOV for this field is determined by the value selected for the field Workflow Item. This field is required if you have entered or selected a value within the Workflow Item field only.

    For example, you can define a hold that prevents an order line from being released for picking by entering Pick Release in this field. The hold takes effect as soon as an order line that meets your hold criteria is eligible for Pick Release.

  5. If you want included items of a configurations option class the included items may have had a hold placed against it to be included in the applied hold. This is an optional feature based on your specific business requirements.

  6. Optionally, enter the Effective Dates for the activity-specific hold to control when you can use this hold.

  7. Optionally, determine which user responsibilities have authority to apply or release activity-specific holds by entering combinations of responsibilities, authorized actions, and effective dates.

    You can give some responsibilities the authority to apply a hold, other responsibilities the authority to release it, and others the authority to do both. If you do not specify a responsibility for an activity-specific hold, anyone can apply or release it.

  8. You can choose to progress the workflow if you select the Progress Workflow on Release checkbox. In such a situation, the workflow activity is progressed for single order lines that are released and it is deferred for multiple order lines. For multiple order lines, you can use the Workflow Background Process to progress the lines in batch.

  9. Save your work.

Define Attachments

Oracle Order Management provides you with attachments features to:

This is step twenty-eight of the Order Management Setup Steps.

Defining Documents for use by the Attachment feature

Using standard Oracle Application Attachment functionality, you can define and set up standard or one time documents with or without attachment addition rules. These documents can later be attached to your sales documents using the Attachments window or automatically by specifying attachment addition rules. You can add free-form text to your orders, order lines, returns, and return lines as attachments, and you can also copy standard documents and modify them into one time document attachments. You may also translate documents to the language of your choice.

Applying Attachments

You can automatically apply standard attachments to orders and returns based on the attachment addition rules you define. You can also apply attachments manually by selecting the Actions button and then selecting Apply Automatic Attachments in the Sales Orders window orOrder Organizer window.

To enable the automatic attachment functionality, you must set the profile option OM: Apply Automatic Attachments to Yes. However, if an order or return is modified, attachments must be reapplied manually.

Editing Attachments

You can edit existing attachments by either clicking the Attachments (paperclip) icon on the toolbar or search for your document and edit in the Documents window.

Viewing Attachments

You can view the attached documents in the Order Organizer, Sales Orders, Sales Agreement Organizer, Sales Agreement, Quick Sales Orders, Quick Order Organizer, Quote, and Quick Quote windows. Within these windows, you can view attachments as follows:

Copying Orders

You can copy document attachments to a new order or to a return when you copy an order by using the Copy orders feature. In the Copy Orders window you can include or exclude manual attachments when copying orders, order lines, returns, and return lines. Sales Agreements do not copy attachments or contract documents.

You can also copy user defined attributes (UDA). Use this option to ensure that the UDA fields are copied to the destination order or lines.

Order Import

When an order has been imported through Order Import into Order Management, you can apply your attachments. You can automatically apply attachments to imported orders based on your attachment addition rules. When creating the order or order line through Order Import, automatic attachments are applied if the profile option OM: Apply Automatic Attachments is set to Yes.

Report Assignment

Order Management currently utilizes Oracle Attachments functionality for the Sales Order Acknowledgement Report. You can choose to attach a document of type Text to be printed on the report for either the order header, the order body, or the order footer.

Security

When viewing order and returns, you can specify which user responsibility can apply and update attachments or simply view attachments. The function security feature available from the Oracle System Administrator responsibility can also be applied to attachments. If you set the function security to view orders and returns, you can view attachments only without the ability to apply or update the attachment.

Application Object Library Profile Option Setting for Attachments

Attachment File Directory

ATTACHMENT_FILE_DIRECTORY

The directory in which file type attachments data is stored. The system administrator sets this profile option during the install process. Users can view, but not update this profile option.

This profile option is visible and updatable at all levels.

Attachment File Directory
Profile Level Setting Visible Allow user Update?
System Administrator: Site Yes Yes
System Administrator: Application Yes Yes
System Administrator: Responsibility Yes Yes
System Administrator: User Yes Yes
User Yes No

Indicate Attachments

ATCHMT_SET_INDICATOR.

This profile option allows you to turn off indication of attachments when querying records (for performance reasons). Users can see and update this profile option.

This profile option is visible and updatable at all four levels.

Indicate Attachments
Profile Level Setting Visible Allow user Update?
System Administrator: Site Yes Yes
System Administrator: Application Yes Yes
System Administrator: Responsibility Yes Yes
System Administrator: User Yes Yes
User Yes Yes

Defining Documents in Advance

You can predefine standard, template, and one-time documents to attach to your orders or returns and additionally, order and return lines, also Quote and Quote lines as well as Sales Agreements (not for SA lines).

The only prerequisite is to define your document categories.

Defining Attachment Addition Rules

Using standard Oracle Attachment functionality, you can specify rules for automatically attaching of all types of documents to orders and order lines. You can specify that documents be applied to orders or lines for a certain customer, Bill To customer, Ship To customer, item, order type, and/or purchase order. For Order Management, you can specify attachment addition rules at the order level for the following attributes for orders, quotes, or returns:

At the order line level, you can specify your attachment addition rules by specifying values for the following attributes on the order, order line, quote line, or return line:

Note: When you define Attachment Rules, the list of values for the fields Bill To and Ship To show the column Status to indicate whether the address is active or inactive. This helps you to identify the correct customer address to send the information.

Note: SA does not support rule based attachments.

Defining Document Categories

Using the functionality of Document Categories within the Oracle Applications Documents feature, you specify document categories to define Order Management attachment definition rules. You can choose to use the following Document types as attachments:

Once you have defined your document Category, you can then perform Category Assignments to enable Oracle Applications functionality for the following entities:

To define document categories:

  1. Navigate to the Document Categories window.

    Document Categories Window

    the picture is described in the document text

    Note: Ensure that you navigate to the Document Categories window available from the Order Management Super User Responsibility, Attachments submenu (Setup->Sales Order/Returns->Attachments->Document Categories) when defining attachments for Order Management reports or windows.

    The Document Categories window available from the Order Management Super User Responsibility, Documents submenu (Setup->Documents->Categories) is for creating document categories to assign document sequence rules.

  2. Enter a value for your category name in the Category field.

  3. Select the default attachment datatype in the Default Datatype field.

    The default Datatype can be overridden when you create documents. If you are creating a document category for Order Management reports, you must choose either Short Text or Long Text.

  4. Optionally, enter an effective date range for your attachment category.

  5. Save your work.

To assign document categories to functions, forms, or report

  1. Navigate to the Document Categories window. Order Management > Setup > Documents > Categories

  2. Either enter a new Document Category and save your work, or select a Document Category previously defined, and click Assignments.

    Category Assignments Window

    the picture is described in the document text

  3. Select the entity type you wish to enable document category attachments for. Select from:

    • Forms

    • Functions

    • Reports

      Order Management enables Oracle Application Attachment functionality for the following entities:

    • The Sales Order and Order Organizer Window (form)

    • The Sales Order Acknowledgement Report

      If you choose to include an Attachment for printing on the Sales Order Acknowledgement Report, you are currently limited to selecting a data type of Short or Long Text. Additionally, order-level attachments print only at the order header or order footer within the output, and order line-level attachments print only in the report body (within the body of each record displayed).

      You can associate as many reports as you need with a single category. If you customize your own reports to include documents, you can specify your own as well as Order Management's default reports in this field. Only text documents can print on reports.

      Oracle Shipping Execution enables Oracle Application Attachment functionality for entities such as Bill of Lading, Commercial Invoice, Pack Slip, and Pick Slip. See Oracle Shipping Execution User's Guide.

      Oracle Pricing enables Oracle Application Attachment functionality for entities such as Agreements and Price Lists. See Oracle Advanced Pricing User's Guide.

  4. Select a Format. Select from:

    • Header

    • Body

    • Footer

      The Format value determines where documents in this category will appear on the report. You can add your own formats for selection within the Category Assignment window by adding values to the Order Management QuickCode NOTE_FORMAT type. However, standard reports support only the seeded format of Header, Body, and Footer.

    Warning: In standard reports, order-level notes print only at the header and footer levels; line-level notes print only in the report body.

  5. Save your work.

Related Topics

Oracle E-Business Suite User's Guide.

Define Freight and Special Charge Types

Order Management enables you to charge for freight and special charges to meet your business needs. The full charge to your customer is visible at the time of order entry and can be communicated to the customer. The freight and special charge amounts can be estimated or final. The actual costs incurred are captured at Ship Confirmation and can be converted to charges based on freight terms and other rules you define. Freight and Special Charges are created and enabled using pricing Modifiers. This is step twenty-nine of the Order Management Setup Steps.

Order Management captures the freight and special charges information and Shipping Execution captures all costs incurred on the shipment of goods. Once ship confirmation completes, the costs are transferred to Order Management and may be used to convert the costs into charges. You can set up your different freight costs in Shipping Execution.

Order Management's freight and special charge feature enables you to:

Freight Terms

You can choose the freight terms for an order line depending on the Customer Contracts (agreements), Customer, Ship To, and Ship-From locations. Freight Terms can be used as Qualifiers to apply freight & special charges, although no such functionality is seeded with the application. Freight terms can include the following:

Prepaid

You (the shipper) take responsibility for paying the freight costs. The costs are recorded in Shipping Execution.

Prepay and add with fixed charges

You can prepay the freight costs and charge your customer a fixed amount. The costs are recorded in Shipping Execution and transferred to Order Management.

Prepay and add with cost converted to charge

You can prepay the freight costs and pass it on to your customer as a charge with a markup or markdown or a direct pass through. The costs are recorded in Shipping Execution and transferred to Order Management.

A pricing formula and pricing modifier are used to calculate the markup/markdown and apply the charge to the customer invoice.

Collect

The freight carrier bills the customer directly; not you. The costs are not recorded in Shipping Execution or Order Management.

Third Party Billing

The freight carrier bills a third party, not the seller or buyer. The costs are not recorded in Shipping Execution or Order Management.

Freight and Special Charge Types

Order Management provides you with the ability to setup and capture different charge types and sub type including (but not limited to):

Grouping of Freight and Special Charges

You can setup different sub-types under a give charge type, such as, if the freight or special charge type is Miscellaneous, you can group the following different charges:

The following Charge Types and sub-types have been predefined by Oracle Advanced Pricing under the Oracle Shipping Execution lookup for FREIGHT_COST_TYPE:

Order Management shares these Freight Cost Types with Shipping Execution for the COST to CHARGE conversion.

Note: You cannot define sub-types for the Shipping Execution Charge Types lookups.

Additionally, you can only receive cost to charge conversions for auto configured items.

Additionally, Oracle Advanced Pricing has its own lookup type, also called FREIGHT_CHARGES_TYPE. You are allowed to add charge types codes to the Advanced Pricing lookup FREIGHT_CHARGES_TYPE. The following charge type code is predefined for this lookup:

Definition Data Elements

You can define different attributes for setting your charges including the following elements:

Calculation Method

Various common methods of calculating charges are supported. Examples of calculation methods include:

Qualifier and Pricing Attributes for Freight and Special Charges

The tables indicate both Qualifier Attributes and Pricing Attributes that have been predefined for Freight and Special Charges.

Note: You can also make use of any other qualifier or pricing attributes that are set up in the pricing for freight and special charges.

Freight and Special Charges Qualifier Attributes
Context Attribute
ORDER SHIPPABLE_FLAG
ORDER SHIPPED_FLAG
ORDER FREIGHT_COST_TYPE_CODE
VOLUME LINE_WEIGHT
VOLUME LINE_VOLUME
Freight and Special Charges Pricing Attributes
Context Attribute
PRICING ATTRIBUTES INSURANCE_COST
PRICING ATTRIBUTES HANDLING_COST
PRICING ATTRIBUTES DUTY_COST
PRICING ATTRIBUTES EXPORT_COST
PRICING ATTRIBUTES FREIGHT_COST
PRICING ATTRIBUTES ADMINISTRATIVE_COST

For more information on Freight and Special Charges using qualifiers within Order Management, refer to the Oracle Order Management Implementation Manual, Freight and Special Charges Examples.

Application of Charges

You can have freight and special charges applied to an order in the following ways:

Order or Order Line Charges

You can enter charges for order or order line levels. The Freight and Special Charges are returned by the Pricing Engine and if there are multiple automatic charges of same charge type and subtype then Order Management applies the one with Maximum amount. If you want the charge to be applied in preference then you may need to set them up with incompatibility group and precedence as described in the Modifier Setup section.

Note: If there is an applied charge of a Charge Type/Subtype then the LOV for Charge Name field in Charges window will not show any manual charges for the same type/subtype. The Charge Name is always derived from the meaning for the charge sub-type lookup code. If the charge sub-type is NULL then the name is derived from the meaning for the charge type lookup code

Estimate or Actual

The estimated or fixed charge is displayed in the Charges user interface. You can set the amount as Estimated or Fixed.

Note: You can set estimated or fixed charges only after a charge has been applied on an order or order line.

Multiple Unlimited Charges

You can enter an unlimited number of charges at each level with unique combination of Charge Type and Charge Sub-Type.

Timing of Charges Entry

You can enter freight and special charges at any event point or activity, up to the point where the order and line is invoiced. At the point of invoicing the charge will be fixed and no more charges can be added after the line is invoiced.

Changing and Deleting of Charges

Based on your processing constraints, you have the ability to manually change the amount, delete, or cancel charges applied to an order or order line until invoicing. You can enter a reason code if the charge is being changed, however, the history will not be maintained. In addition, you can add processing constraints to prevent charges from deletion or cancellation after a user-definable point in the order's process.

Freight Charges and Included Items

In order to apply any eligible freight charges for an Included Item, the profile option OM: Charges for Included Item should be set to Y.

When this profile option is set to Y, and the calculate price flag of the order line with an included item is either Calculate Price (Y) or Partial Price (P), then the eligible freight charges are applied to the order line.

For backordered lines within Included Items, both the profile options OM: Charges for backorders and OM: Charges for Included Item need to be set to Y to view and apply any freight charges.

Any freight charge modifiers you define for included item should be within a pricing phase that is included within the Order Management 'LINE' or 'SHIP' workflow event.

Freight Charges for Backordered Lines

The Order Management profile option OM: Charges for Backorders controls how the system will set the value of the calculate price flag for backordered lines.

Rounding of Freight charges

The Oracle Advanced Pricing profile option QP: Selling Price Rounding Options determines if your freight charges are rounded. See: Oracle Advance Pricing Implementation Guide, Profile Options.

To define Order Management Freight Cost Type Names

  1. Navigate to the Oracle Order Management Freight Cost Types window. Order Management > Setup > Shipping > Freight Carriers, Cost Types > Freight Cost Types.

    Order Management Freight Cost Types Window

    the picture is described in the document text

  2. Enter a name for your Freight Cost type in the Name field.

    The value entered in this field is the value a Shipping Clerk will see on within the Oracle Shipping Execution Transactions window when entering Freight Costs during the shipping process.

  3. Choose a type for your Freight Cost Name from the LOV in the Type field.

  4. Select a currency that the Freight Cost Type will use in the Currency field.

  5. Enter the default value for your Freight Cost Type in the Amount field. The amount will be defaulted in the Freight Cost window when you enter or select the Freight Cost Name during the shipping process.

  6. Enter effective dates for you Freight Cost Name in the Effective Date From/To fields.

  7. Save your work.

Setting up Freight Rates and Charges

Oracle Order Management displays the freight rates and charges for shippable and non-shippable items. For example, when you choose ship method for an 'assemble to order' (ATO) item using the Sales Order window, the application displays the ship method rate and calculates the charges based on the pricing setup.

Note: You must have Oracle Advanced Pricing installed to set up freight rates and charges.

To set up freight rates and charges

  1. Navigate to the Advanced Pricing – Pricing Transaction Entity – Attribute Linking window (Pricing -> Setup -> Attribute Management -> Attribute Linking and Mapping).

  2. Select Order Fulfillment as the pricing transaction entity and Pricing Context as the context type. The application displays a list of contexts.

  3. Select Pricing Attribute and click Link Attributes to open the Link Attributes window.

  4. Select the Estimated Transportation Price (ESTIMATED_FTEPRICE) attribute and click Attribute Mapping to open the Attribute Mapping window.

  5. Select the request type with the following details:

    • Application Name: Advanced Pricing

    • Request Type: ONT

    • Description: Order Management Order

  6. Optionally, replace the default user value string in the line level section as follows: Replace 'OE_FREIGHT_RATING_UTIL.GET_ESTIMATED_COST_AMOUNT ('FTEPRICE')' with 'OE_FREIGHT_RATING_UTIL.GET_ESTIMATED_COST_AMOUNT_NS('FTEPRICE')'

    Note: The default value only considers shippable items for freight rates and charge calculation. If you need to include the non-shippable lines also for the calculations, then you must replace the default user value string.

  7. Save the changes.

  8. Without closing this window, click the Tools option on the top menu bar.

  9. Click Build Attribute Mapping Rules to generate the attribute mapping rule. The application displays a message indicating the successful generation of the attribute mapping rule. The application uses this attribute mapping rule to calculate and display the freight rates and charges for shippable and non shippable items as applicable.

Setting Up User-Defined Attributes

Oracle Order Management enables you to record additional information at the order level and the line levels with user-defined attributes (UDA). These attributes are aggregated in user-defined attribute groups. Each group can have several attributes. You must associate each attribute group with a particular business classification. For Oracle Order Management this is the predefined classification ADMIN_DEFINED. An attribute group can have a maximum of 40 character fields, 20 number fields, and 10 date fields. However, you can associate as many attribute groups as you want with a UDA page. which means that the number of additional attributes for an order or line is unlimited.

For each user-defined attribute, you can choose to specify a value set with data type and validation rules to be applied when the user enters data. Once you create a value set, you can reuse it for different attributes. It is recommended that you create value sets before you define attribute groups. An attribute group can be multi-row or single-row. Multi-row attribute groups enable the association of multiple sets of attribute values with the same attribute group, whereas single-row attribute groups enable a single attribute value for the attribute group.

For example, for a motherboard item, you might create a single-row attribute group called "Motherboard Specification" with a single value. Similarly, for a supplier, you can create a single-row attribute group called "Registration Number" that has a single value.

For a motherboard item, you could also create a multi-row attribute group called "Operating Systems", with the attributes "OS Name", "Version", and "Service Pack". You can associate multiple rows of operating systems with the motherboard item. Similarly, for a supplier, you could create a multi-row attribute group called "Services", with the attributes "Service Name", "Service Type", and "Service Frequency". You can associate multiple rows of services with the supplier.

You can create attribute pages to capture details of each attribute group. The attribute pages enable you to view or edit data of attribute groups for a selected object instance based on access permissions. Along with the UDAs, you can record additional information for orders and lines using the existing descriptive flexfields.

An attribute group can also raise change-attribute business events from a UDA page. Oracle Order Management provides two seeded change business events that you can use with the user defined attributes functionality. These seeded business events are:

Before the attribute group can raise the change attribute business events from a UDA page, you must create an event subscription for one or both of the oracle.apps.ont.document.preAttributeChange and oracle.apps.ont.document.post.AttributeChange business events. You must select the subscription processing you want the system to perform when the triggering event occurs, which is the recording of the user defined attributes. For example, you may want the system to launch Workflow, send a notification, or execute custom business logic.

For information about how to create an event subscription, see Oracle Workflow Developer's Guide.

Prior to recording the user-defined attributes from the Sales Order window, you must do the following:

  1. Create attribute group information.

  2. (Optional) Select whether you want the attribute group to raise one or both of the attribute change business events.

  3. Add attributes to the attribute group.

  4. Associate attribute group to the predefined classification ADMIN_DEFINED.

  5. Create UDA pages.

To Create an Attribute Group

  1. Navigate to the OM UDA Setup Page.

  2. In the Entities field, select either Order Header or Order Line as the attribute group entity type.

  3. Click Go.

    The Admin Page appears. This page contains the Attribute Group, Association, and Page tabs.

    In the Attribute Group tab, the Search page displays the available attribute groups for the type of entity you selected.

  4. Click Create.

    Depending on the type of entity you selected, either the Create Attribute Group for Additional Order Header Information Extension page or the Create Attribute Group for Additional Order Line Information Extension page appears. These pages function the same except one is for the order header and the other is for the order line.

  5. Enter an Internal Name and Display Name for the attribute group.

  6. (Optional) Enter a Description for the attribute group.

  7. In the Behavior field, select either Single-Row or Multi-Row.

    • If you selected Single-Row, enter a value in the Number of columns in the page layout field. The default number of columns is 2.

    • If you selected Multi-Row:

      1. Enter a value in the Number of columns shown in the table field. The default value is 5.

      2. Enter a value in the Number of rows shown in the table field. The default value is 5.

  8. (Optional) In the Business Entities region:

    • Select the Pre check box if you want to raise the oracle.apps.ont.document.preAttributeChange business event for this attribute group.

    • Select the Post check box if you want to raise the oracle.apps.ont.document.postAttributeChange business event for this attribute group.

  9. Click Apply and Add Attributes to add attributes to the attribute group.

    The Create Attribute page appears.

  10. Enter the following information for the attribute:

    Field Description
    Internal Name Enter the internal name for the attribute.
    Display Name Enter the display name for the attribute. This is the name that appears on the UDA page.
    Sequence Enter the sequence number for the attribute. This sequence determines how the attributes are displayed within the attribute group on the UDA page.
    Tip (Optional) Enter tip text for the description of the attribute.
    This text displays below the attribute on the UDA page.
    Data Type Select the attribute data type from the following types:

    • Char (Character)

    • Number

    • Standard Date

    • Standard Date Time

    • Translatable Text
    Column Select the attribute column.
    For header-level attributes, select from the table OE_ORDER_HEADERS_ALL_EXT_B. For line-level attributes, select from the table OE_ORDER_LINES_ALL_EXT_B.
    Enabled Select the Enabled check box if you want to enable this attribute.
    Required Select the Required check box if this attribute is required.
    Display As Select how this attribute is displayed. The options are:

    • Check box

    • Dynamic URL

    • Hidden

    • Radio Group

    • Static URL

    • Text Area

    • Text Field
    Indexed Oracle Order Management does not use this field.

  11. Select the Value Set Name for the attribute.

  12. Enter the Default Value for the attribute.

  13. Click Apply or Apply and Add Another if you want to add another attribute to the attribute group.

To Associate Attribute Group with a Classification

  1. Click Add Attribute Groups in the Associations page under the Association tab to select the attribute groups from the list of available attribute groups.

  2. Click Apply.

    Clicking Apply adds the attribute groups to the predefined classification, ADMIN_DEFINED.

To Create UDA Pages

  1. In the OM UDA Page Setup page under the Page tab, select Create Page to create pages for a particular Classification. An UDA page is a group of attribute groups associated to a classification.

  2. In the Page Details page, add the page information and add the required attribute groups.

  3. Click Apply.

    Note: If you want the additional attributes to appear in different regions, then create multiple attribute groups and associate them to the predefined classification, and then to an UDA page. If different regions are not required and your list of additional attributes falls below the number of attributes supported by a attribute group, then you can create one attribute group, associate it with the predefined classification, and assign it to the UDA page.

To Import User Defined Attributes

You can add and associate UDA to the orders created through Order Import/HVOP using order interface tables and the Import User Defined Attributes concurrent program.

  1. Create the order using Order Import/HVOP.

  2. Populate data into the following UDA interface tables:

    • OE_HEADERS_EXT_IFACE_ALL

    • OE_LINES_EXT_IFACE_ALL

    Populate the following columns in the interface tables to meet your business requirements:

    Columns in Interface Tables to Import UDA
    Column Name Description
    TRANSACTION_ID Unique ID for each record.
    DATA_SET_ID An identifier for the collection of rows to be processed together. Usually it's an unique value per concurrent request.
    ROW_IDENTIFIER An identifier for the collection of rows that make up one logical attribute group row. Usually it's a unique value per attribute group.
    ATTR_GROUP_TYPE For Order Header - OE_HEADER_ATTRIBUTES_EXT
    For Order Line - OE_LINE_ATTRIBUTES_EXT
    ATTR_GROUP_INT_NAME Attribute group internal name.
    ATTR_GROUP_ID Unique ID for attribute group.
    ATTR_INT_NAME Attribute internal name.
    ATTR_VALUE_STR The attribute value, if its data type is Char.
    ATTR_VALUE_NUM The attribute value, if its data type is Number.
    ATTR_VALUE_DATE The attribute value, if its data type is Date.
    TRANSACTION_TYPE Create/Update and Delete in case of deleting multi row UDA values.
    DATA_LEVEL_ID Unique data_level_id for order header/line.
    If you do not know the data level ID, then you can populate Data_Level_Name.
    DATA_LEVEL_NAME ORDER_HEADER/ORDER_LINE.
    PROCESS_STATUS Values are:

    1. To Be Process

    2. In Process

    3. Rejected Record

    4. Success
    ENTITY Classification code "ADMIN_DEFINED".
    ORDER_SOURCE_ID The order source ID.
    ORIG_SYS_DOCUMENT_REF Reference of the sales order header/line.
    ORIG_SYS_SHIPMENT_REF Reference of sales order line shipment.
    SOLD_TO_ORG_ID The sold to organization ID.
    HEADER_ID The header ID.
    LINE_ID The line ID.
    ORG_ID Operating unit ID.
    ORIG_SYS_LINE_REF Reference of sales order line.

  3. After data is populated in the UDA interface tables, submit the Import User Defined Attributes concurrent program by providing the Data Set ID parameter to import data into the following Order Extension base tables:

    • OE_ORDER_HEADERS_ALL_EXT_B

    • OE_ORDER_LINES_ALL_EXT_B

    The import program reports errors in the MTL_INTERFACE_ERRORS table.

    After completing these steps, you can record information in the user defined attributes from the Sales Order window. See: Entering User Defined Attributes, Oracle Order Management User's Guide

Overview of Shipping Tolerances

Oracle Order Management provides you with the ability to capture shipping tolerance levels for over and under shipments recorded during ship confirmation. The shipping tolerance feature enables you to define various shipping tolerance levels for ordered and expected return quantities. Order Management shipping tolerances are used to validate the percentage of the ordered quantity. Once shipping tolerances have been defined, Order Management then automatically fulfills order lines using the tolerances you defined.

Order Management's shipping tolerances feature captures the following:

Over Shipments

When Oracle Shipping Execution attempts to over ship an order, Order Management processes the order based on the shipping tolerances you define. In order to perform an over shipment, Order Management:

Under Shipments

When Oracle Shipping Execution attempts to under ship an order, Order Management processes the order based on the shipping tolerances you define. In order to perform an under shipment, you must:

Under Shipment tolerances greater than 100% are treated as the equivalent of a 100% tolerance; to close order lines a shipment of a non-zero quantity is required, even if the under shipment tolerance is set to 100%.

Note: If a zero quantity is entered at shipment, the system will process the transaction. However, zero quantity shipments are not allowed; Order Management will therefore perform a backorder for the zero quantity shipment line at ship confirm.

Note: A shipment of a quantity other than zero is needed in order to enable order lines to progress to closure.

Over Shipments Report

Oracle Shipping Execution provides the Over Shipments Report for displaying shipping tolerances. This report displays shipping tolerance information based on the customer, site, item, warehouse, ship date, and order type.

Related Topics

Profile Options

Oracle Shipping Execution User's Guide

Defining Shipping Tolerances

Defining shipping tolerances are based on your customers and items or your customer site and item tolerances.

Prerequisites

To define shipping tolerances for orders or returns:

  1. Navigate to the Setup Tolerance window.

    Setup Tolerance Window

    the picture is described in the document text

  2. Select the Customer name for the shipping tolerance.

  3. Select the customer Address for the shipping tolerance. You can pick a customer address in any Operating Unit accessible to you via your MO: Security Profile.

  4. Select the Item Number for the shipping tolerance.

  5. Enter the Over Shipment Tolerance percentage.

    The over shipment tolerance percentage determines the amount of the shipment you can exceed at the time of ship confirmation.

  6. Enter the Under Shipment Tolerance percentage.

    The under shipment tolerance percentage determines the minimums amount of the shipment at the time of ship confirmation. If you enter more than 100, the shipping process will use 100.

    Note: Order Management currently does not support over and under shipment tolerances for ATOs (Model, Kit and all children). Updates to shipment tolerances for PTOs is currently not allowed.

    If you have defined non-zero tolerances within either the Item Form, Customer Form, Shipping Tolerances Form, or the profile option value, the values are ignored for PTOs; the over and under shipment tolerance for PTOs will always default to 0.

    If the tolerances are defined with unequal values for a combination of Ship_To with an item, the Ship_To field is not updated.

  7. Enter the Over Return Tolerance percentage for return receipts.

    The over return tolerance percentage determines the amount of the return you can accept above.

  8. Enter the Under Return Tolerance percentage for return receipts.

    The under return tolerance percentage determines the amount of the return you can accept below.

  9. Save your work.

Release Management Integration Setup for Sales Agreements

Oracle Release Management

Oracle Release Management locates the releases against a Sales Agreement, and uses this information to determine the current picture of demand. In the past, Release Management looked at only one sales order to determine demand (this sales order is identified in the Release Management Processing Rules). Release Management uses the Sales Agreement number in the processing rules, and determines all releases against the Sales Agreements to define the current demand.

See the Oracle Release Management User's Guide, Oracle Release Management Implementation Manual, and Sales Agreements in the Oracle Order Management User's Guide and Implementation Manual.

Scheduling Across Orders Setup

Setting Up

You can control access for the appropriate role.

To Set Up the Appropriate Role:

  1. Set the profile option OM: Scheduling Role:

    • CSR only: Will not be able to access the Scheduling Find tab and Scheduling Organizer window. All other functionality for the Order Organizer and Sales Order Pad will remain unchanged.

    • Scheduler only: Will be able to access Scheduling Find tab and Scheduling Organizer window, but not other tabs within the Order Organizer, i.e. Order Information, Line Information, Advanced, and Holds Information.

      Note: Scheduler-only users should have their own Menu which should not have access to functionality such as the Sales Orders window, Price Lists, etc.

    • CSR and Scheduler: Will be able to access both the Order tabs (Order Information, Line Information, Advanced, and Holds Information) and the Scheduling tab within the Find Orders window as well as the Scheduling Organizer window.

  2. Save your work.

Setting Up Gross Margin

To Set Up Gross Margin:

  1. Navigate to the Define OM System Parameters window. The default for the Margin Calculation system parameter is No. To use gross margin, you must select a value for the Margin Calculation system parameter that is anything other than "Do not calculate". Select whether to perform the calculation based on one of the following and then save your work:

    • Cost Based, Cost Modifiers Only

    • Cost Based, Cost Modifiers and Rebates

    • Cost based

    • Price Based, Cost Modifiers Only

    • Price Based, Cost Modifiers and Rebates

    • Price based

  2. If you selected any option involving cost modifiers for the Margin Calculation system parameter then you will need to determine the cost adders that will affect the cost calculation. After the cost adders are known you will then need to execute a custom hook (oe_cost_hook.get_cost_adders()) provided by Oracle Order Management to pass the set of cost adders that will impact the cost calculation. Oracle Order Management only provides the specification for this hook. Following is the details for this hook (API):

         CREATE OR REPLACE PACKAGE oe_cost_hook IS
        TYPE Cost_Rec_Type IS RECORD
        (  AMOUNT_PER_QTY        NUMBER           --per qty amount
        ,COST_ADDER_CODE        VARCHAR2(240)    --cost adder
        );
        TYPE Cost_Tbl_Type IS  TABLE OF Cost_Rec_Type
            INDEX BY BINARY_INTEGER;
        PROCEDURE GET_COST_ADDERS(p_header_rec   IN OE_Order_PUB.Header_Rec_Type,
                                  p_line_rec   IN OE_Order_PUB.Line_Rec_Type,
                                  x_cost_tbl  OUT NOCOPY Cost_Tbl_Type
                                 )  ;
        END OE_COST_HOOK ;

    You can use header or line level attributes to derive a set of cost adders as per your business requirements and return the details of cost adders in x_cost_tbl. To maintain data consistency, a quick code ONT_COST_ADDERS has been created which will be used to store the name and description of the Cost Adders. You will need to use this quick code to define type of cost adder details.

    This cost hook is called whenever the “get cost” API is called and/or when any of the following fields are changed:

    • Ordered Item

    • Warehouse

    • Item Quantity

    • UOM

    • Sold to Customer

  3. Decide if you want to hold orders that do not meet minimum margin percentages. If you do, decide which order types you want to do this for. Go to the Order Management Transaction Type window and query up each Order Type record and enter the minimum margin percentage. Save each record.

  4. Determine which responsibilities do NOT need to be able to view gross margin information in the Sales Orders window and the Pricing and Availability window. Using the System Administrator responsibility, navigate to Applications > Responsibility, define or query up a responsibility with “Orders, Returns Main Menu” attached, and exclude the View Margin function from those responsibilities.

  5. Create a folder for the Sales Orders window, Order Information tab, Other sub-tab to display both or either Margin Amount and Order Margin %, and a folder for the Line Items tab to display any or all of the Unit Cost, Adjusted Unit Cost, Margin Amount and Margin % fields on the Main sub-tab or the Pricing sub-tab. Assign that folder to be the default folder for those responsibilities who can view gross margin.

    Create a folder for the Pricing and Availability window Pricing sub tab to display any or all of the Unit Cost, Margin Amount, and Margin % fields and assign that folder for those responsibilities who are allowed to view gross margin. The Pricing and Availability window displays margin calculations using item cost only.

    Note: N/A will display in the Margin Amount and Margin % fields in the Pricing and Availability window if you have selected "Cost Based, Cost Modifiers Only", "Cost Based, Cost Modifiers and Rebates", "Price Based, Cost Modifiers Only", or "Price Based, Cost Modifiers and Rebates" for the Margin Calculation system parameter.

Setting Up User Item Description

To Set Up the User Item Description:

To set up the Oracle Order Management system to use the User Item Description for invoicing purposes or for ad hoc item entry, perform the following:

  1. Create a folder for the Line Items tab to display the User Item Description on the Main sub-tab. Assign that folder to be the default folder for those responsibilities who need to be able to enter or view the User Item Description. Save your work.

  2. To create a generic item to be used for drop shipping miscellaneous items that you do not typically sell or stock, create a dummy item in the Inventory Master Items window. Set the item attribute Default Source Type to External, so that the item will be always be drop shipped. Select the item attribute "Allow Description Update check box" on the Purchasing tab, so that the purchase order will not reject the user item description.

Setup for Related Items

To Set Up the Related Items Feature:

Set the profile OM: Enable Related Items and Manual Substitutions to Yes.

Note: Release 12.0 and lower APS customers should not use this feature as there is an impact on collections and forecast consumption that APS has provided in Release 12.1.

To Set Up the Item Relationships Using Oracle Inventory:

  1. Navigate to the Item Relationships window. This window can be accessed from Inventory > Items > Item Relationships.

  2. Define the relationships between items by selecting the Type of relationship, the most commonly used relationship types are:

    Substitute: One item is a substitute for another (alternate item)

    Superseded: One item is replacing another, probably older version

    Up-sell: Selling an improved version of the item originally ordered

    Cross-Sell: Selling additional items that go along with the item originally ordered

    Item Relationships window

    the picture is described in the document text

    In the above window, the item AS54888 is setup with different related items of different relationship types like Cross-Sell, Up-Sell, Superseded, and Substitute.

    Current Relationship Types

    • Related

    • Substitute

    • Cross-Sell

    • Up-Sell

    • Service

    • Prerequisite

    • Collateral

    • Superseded

    • Complimentary

    • Impact

    • Conflict

    • Mandatory Charge

    • Optional Charge

    • Promotional Upgrade

    • Split

    • Merge

    • Migration

      Note: The relationship type 14 (Promotional Upgrade) is used by Advanced Pricing for Item Upgrade setup. So on the Related Items window, the items that are setup with relationship type 14 are not shown.

  3. Save your work.

Setup of Recurring Charges

Charges are classified into 3 types: One-time, Recurring, and Usage for service items. Order Management now provides the Recurring Charges functionality to order and price products with recurring and one-time charges. The MACD (Move Add Change Disconnect) feature of Order Management has been enhanced with the addition of the Recurring Charges functionality, and is now referred to as TSO (Telecommunications Service Ordering).

The following are the setup steps to be carried out for Recurring Charges:

If MACD is already installed, you only need to set up the following:

If MACD is not installed, you require to install it first and then setup the Recurring Charges features.

Trading Community Usage Within Order Management

In general, previous releases of Order Applications and initial releases of Oracle CRM products utilized the Oracle Receivables Customer Model for storing and retrieving customer information.

You can model customers and customer details using Oracle's Trading Community model. Oracle's Trading Community customer model is a powerful customer architectural design, building on the Receivables Customer model, enabling users to now define and maintain customer hierarchies and relationships between customers and sites. If a CRM or ERP application maintains customer information, the application is using the Trading Community customer model.

Trading Community enables you to:

Terminology

Trading Community

Mapping Order Management terminology to Trading Community terminology

The following figure describes the conceptual usage of the Trading Community model as utilized currently within Order Management.

Trading Community Model

the picture is described in the document text

The figure above conceptually represents the Trading Community customer model and how Trading Community has been integrated within the Order Management Application. When defining a customer, you are defining a Trading Community account, which can be linked to a new or existing Party. Accounts have at least one address and each address may have one or more site uses. You can also create new relationships among accounts across parties.

Within Order Management, each account belongs to a party. These parties may have additional relationships and details defined, but Order Management currently only utilizes a limited subset of the party data (accounts, addresses, and sites usages).

The Trading Community model includes all the information which was previously stored in the Receivables customer model. This includes information such as:

In order to maintain backward compatibility for the Oracle Receivables customer model, Order Management currently accesses data stored in Trading Community database tables via Order Management database views. Future development projects are in progress to update Order Management applications code to retrieve Trading Community details directly from Trading Community base tables rather than utilizing Order Management views.

As Order Management adds new features and additional functionality to its core application, users will begin to see Trading Community terminology incorporated into Order Management Forms (windows), Reports, Concurrent Programs, and product documentation. Until these project are completed, Order Management forms will continue to use names of entities as they existed in the Receivables customer database tables. The following table provides a mapping of these field names.

Mapping of Entities in Receivables Customer Database Tables
Order Management Form (window) Entity Name Trading Community Base Table Entity Name
Customer Number Account Number
Customer Name Party Name

For more information on Trading Community and the new Trading Community customer model, see :Oracle Receivables User Guide, Customers.