扫二维码下载作业帮
拍照搜题，秒出答案，一键查看所有搜题记录
下载作业帮安装包
扫二维码下载作业帮
拍照搜题，秒出答案，一键查看所有搜题记录
The manger entered the office and was happy to learn that four-fifths of the tickets ________．A. was bookedB. had been bookedC. were bookedD. have been booked
扫二维码下载作业帮
拍照搜题，秒出答案，一键查看所有搜题记录
答案B因为分数作主语时谓语动词与of后的名词一致,本句与the tickets一致；又因book的动作在was happy之前,故应用过去完成时形式.
为您推荐：
其他类似问题
扫描下载二维码The manager entered the office and was happy to learn that four-fifths of the tickets . A. was booked B. had been booked C. were booked D. have been booked? 题目和参考答案——精英家教网——
暑假天气热？在家里学北京名师课程，
& 题目详情
The manager entered the office and was happy to learn that four-fifths of the tickets _______ . &&& A. was booked B. had been booked C. were booked&& D. have been booked?
科目：高中英语
1．Is this you p&&&&&& （永久的）address, or are you staying there for a very short period of time? 2．Newly arrived guests are required to r&&&&&&&& （登记，注册）at the hotel’s reception desk. 3．I recommended that each c&&&&&&&& （竞争者）should be praised for what they has done in the race. 4．A committee was a&&&&&&& （任命，委任）to look into the case and collect as much as information as possible. 5．It was now time to interview the farmer, for whom I had p&&&&&&&&& （先前，以前）worked. 6．If you could find some witnesses it would greatly s&&&&&&&&& （加强，巩固）your case. 7．They set up an i&&&&&&&&& （有影响力的）company to advise more people to make the best use of water. 8．If you cannot go yourself, why not find someone to s&&&&& （代替，替代）you? 9．It’s quite a&&&&&&&&& （显然的，显而易见的）that she has no intention of changing her mind. 10．The manage issued an order i&&&&&& （指令，吩咐）its members not to work overtime.
科目：高中英语
The manage________ it clear to us that he didn’t agree with us,left the meeting room.? A.who has made　　　　　　　　 B.having made? C.made　　　　　　　　　　　　 D.making
科目：高中英语
题型：阅读理解
&&&& When Johnson called again, the manager received him very politely. “That is a most remarkable oil you brought us, Mr Johnson,” he said. Johnson nodded his smooth, dark head. That was something he knew very well.“I've never seen anything like it,” the manager admitted. Johnson nodded again.“No?” he said politely. Then he added, “But I think you will, sir. A very great deal of it.” He appeared to think for a moment. “I think you will find it will be on sale seven, perhaps, eight years from now.” He smiled. The manager thought that was uncertain. He said, “It is better than our fish oils. I admit that.”“So I am told, sir,” agreed Johnson. “Have you any plans to produce it yourself, Mr Johnson?” Johnson smiled again. “Would I be showing it to you if I had?” “We might add some chemicals to one of our own fish oils,” said the manager.“It would be expensive to do that, even if you could,” Johnson said gently.“Besides,” he added,“I am told that this oil will be much cheaper than your best fish oils. Cheaper than any vegetalbe oil, in fact.” “Perhaps,” said the manage.“Well, I suppose you want to make an arrangement, Mr Johnson. Shall we discuss it?” “Of course,” said Johnson. “There are two ways of dealing with a situation of this sort. The usual one is to prevent it altogether or at least to delay it as long as possible. That is, of course, the best way.” The manager nodded. He knew plenty about all that. “But I am so sorry for you, because, you see, that is not possible this time.” The manager had his doubts, but all he said was an inquiring(asking), “Oh?” “The other way,” continued Johnson,“is to produce yourself before the trouble starts.” 49.The manager thought of adding chemicals to the fish oil to make it& ______. A.cheaper than the new oil&&&&&& &&&&&&&&B.more quickly C.more expensive&&&&&&&&&&&&&&&&&&&&& D.as good as the new oil 50.Johnson's new oil would be ______. A.more expensive than fish oil, but better&& &B.less expensive, and better C.less expensive, but not good&&&&&&&&&&& &D.more expensive, and not so good 51.Johnson expressed his regret that the manager ______. A.could not stop the new oil being made&&& B.would never know how to make it C.had spent a lot of money on it&&&&&&&&&& D.didn't know enough about it 52.Johnson showed his new oil to the manager because he wanted ______. A.to produce it himself&&&&&&&&&&&&&&&&&& B.to prevent it being produced C.to be paid not to produce it&&&&&&&&&&&&& D.the manager to produce it
科目：高中英语
John thought he was&&& when the manage asked him for the advice one the new product. && A.something&&&&&&&&&&& B.anything&&&&&&& C.somebody&&&&& D.anybody
科目：高中英语
John thought he was&&& when the manage asked him for the advice one the new product． A．something &&&&&& B．anything&& &&&&&C．somebody&&&& &&&D．anybody
精英家教网新版app上线啦！用app只需扫描书本条形码就能找到作业，家长给孩子检查作业更省心，同学们作业对答案更方便，扫描上方二维码立刻安装！
请输入姓名
请输入手机号Oracle Order Management Implementation Manual
Browser version script Oracle Order Management SetupThis 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
Order Management Setup Steps
Setup Steps Defined in Detail
Profile Options
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:
Performing system-wide setup tasks, such as configuring concurrent managers and printers
Managing data security, which includes setting up responsibilities to enable access to a specific set of business data and transactions, and assigning individual users to one or more of these responsibilities
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.
Optional or Required
1.Define multiple organizations in Oracle Inventory
Oracle Inventory User's Guide
2. Setup Multi-Org (Multiple Organization) Access Control
Oracle Applications Multiple Organizations Implementation Guide
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
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
7. Define invoicing information
Oracle Order Management UserGuide
required under certain conditions
8. Define your sales representatives
Oracle Receivables Implementation Guide
Current, Oracle Receivable's User's Guide
Oracle Order Management Implementation Manual
required under certain conditions
11. Define header and line processing flows
Oracle Order Management
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
required under certain conditions
14. Define the units of measure
Oracle Inventory User's Guide
15. Define item information
Oracle Inventory User's Guide
16. Define the items that you sell
Oracle Inventory User's Guide
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
19. Define customer profile classes
Oracle Receivables Implementation Guide
required under certain conditions
20.Define information on your customers
Oracle Receivables Implementation Guide
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
Oracle Order Management Implementation Manual
24. Set up Cost of Goods Sold Accounting flexfield combination
Order Inventory User's Guide
required under certain conditions
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
required under certain conditions
Oracle Order Management Implementation Manual
required under certain conditions
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
31. Define shipping parameters
Oracle Shipping Execution User's Guide
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.
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: Shipping
Define shipping parameters in Oracle Shipping Execution.
This step is required.
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
Oracle Shipping Execution User’s Guide
Oracle Inventory User’s Guide
Oracle Receivables User Guide
Oracle Receivables Implementation Guide
Oracle Receivables Reference Guide
Oracle Bills of Material User’s Guide
Oracle Order Management User’s Guide
Oracle Applications Multiple Organizations Implementation Guide
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:
Order Information Portal:
Sales Order Advanced Search and Results page
Order Status page
Deliveries Advanced Search
Delivery page
Sales Orders windows:
Sales Order window
Order Organizer Find window (All tabs)
Order Summary
Quick Sales Order window
Quick Sales Order Organizer
Quick Order Summary
Quote window
Quote Organizer
Quote Summary
Find Customer window
Sales Agreements windows:
Sales Agreements window
Sales Agreements Organizer
Sales Agreements Summary
Other windows:
Scheduling Organizer window
Pricing and Availability window
Order Import Corrections window
Open Interface Tracking window
Retrobill Organizer window, Retrobill Requests tab
The Order Management windows where the Operating Unit is added as visible:
Audit History Find, Audit History
Add Customer window
Apply Holds (Criteria tab) window
Approvals (to display Operating Unit of Transaction Type)
Export Compliance Find, Export Compliance Workbench
Order Import Corrections Find window
Open Interface Tracking Find window
Process Messages Find,
Process Messages window
Payment Types
System Parameters
Shipping Tolerances (to display Operating Unit of Customer Address)
Transaction Types
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 .
Generally, the system administrator sets and updates profile values. See: Setting Profile Options, Oracle E-Business Suite System Administrator's Guide - Maintenance.
Profile Categories
In the current release, profiles have been categorized so that they can be easily classified or grouped. The following 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 w OM: Configuration Quick S OM: Copy Model DFF OM: Included Item Freeze M OM: Party Totals C
Customer Usage
OM: Add Customer (Order Import);
OM: Create Account I
OM: E-Mail Required on New C
OM: Party Totals C OM: Sales Order Form: Restrict Customers
OM: Debug Log D
OM: Debug L
OM: Generate Diagnostics for Error A
Deployment
OM: Orders Purge Per C
OM: New EDI Acknowledgment F
OM: Printed Document Extension Class N
Electronic Messaging
OM: Change SO Response R
OM: Electronic Message Integration Event Sources OM: New EDI Acknowledgment F OM: Order Accept State for XML; OM: Run Order Import for XML;
OM: Send Acknowledgment for Change PO R
OM: Add C OM: Administer Public Q OM: Automatically Open Related Items W OM: Contact Center Actions Menu N OM: Cust Item Shows M OM: Display Actions Button vs. P OM: Display Current Selections in Pricing/A OM: Enable Related Items and Manual S OM: Item View M OM: Quick Sales Order Form: Auto R OM: Quick Sales Order Form: Defer P OM: Sales Order Form: Cascade Header Changes to L OM: Sales Order Form: Refresh Method (Query Coordination); OM: Sales Order Form: Restrict C OM: Sales Order navigation from Pricing/A OM: Sales Orders F OM: Scheduling R OM: Show Line D OM: Show Process Messages F OM: Use C OM: View Cancel L OM: View Closed L OM: View Pricing & Availability Information in Related I
Fulfillment
OM: Allow model fulfillment w OM: Included Item Freeze M OM: Over Return T OM: Over Shipment T OM: Population Of Buyer Code For Dropship L OM: Source C OM: Under Return T OM: Under Shipment T OM: Automatically Interface Lines to IB on Fulfillment
OM: Modify Seeded H OM: Prevent Booking for Line Generic H
OM: Interface freigh OM: Invoice Numbering M OM: Set Receivables Transaction Date as Current Date for Non-Shippable L OM: View Intercompany AR Invoice
Item Usage
OM: Customer Item Shows M OM: Enable Related Items and Manual S OM: Item F OM: Restrict Customer Items for Line Level Ship To A
OM: Sequence for TP Ship/Deliver D OM: Source for TP Early Ship/Deliver D
Order Import
OM: Add Customer (Order Import);
OM: Import Multiple S
OM: Unique Order Source, Orig Sys Document Ref Combination For Each C
OM: Commitment S OM: Credit Card P OM: Preserve External Credit Balances
OM: Customer Service F OM: Customer Service Report D OM: Records On Summary Page For External U
OM: Charges For B OM: Charg OM: Charging P OM: Discounting P OM: Enable Group pricing for DSP OM: Item Change Honors Frozen P OM: List Price Override P OM: Negative P OM: Promotion Limit Violation A OM: Send Changed Lines to P OM:Unit Price Precision T OM: UOM Class for Charge P OM: Price Adjustment Modifier for AIA Order Lines
OM: Customer Service F OM: Customer Service Report D OM: Over Return T OM: Notification A OM: Return Item Mismatch A OM: Return Unfulfilled Referenced Line A OM: Under Return T
Scheduling
OM: Assign New Set For Each L OM: Authorized To Override ATP; OM: Auto Push Group D OM: AutoS OM: Enforce Shipping Method for Ship S OM: Schedule ATO Item Without BOM; OM: Scheduling R
OM: Add C OM: Add Customer (Order Import); OM: Administer Public Q OM: Authorized To Override ATP; OM: Cascade S OM: Charging P OM: Create Account I OM: Credit Card P OM: Discounting P OM: List Price Override P OM: Modify Seeded H OM: Scheduling R OM: Authorized To Override ATP;
OM: Cascade S
Transaction Entry
OM: Apply Automatic A
OM: Cascade S
OM: Configuration Quick S
OM: Copy Mode
OM: Default Blanket Agreement T OM: Default Blanket Transaction P
OM: Default Sales Transaction P
OM: Default S
OM: Display New Order After Copy
OM:Enforce check for duplicate Purchase O
OM: Generic Update Constraints Apply to DFF?;
OM: Prevent Booking for Line Generic H
OM: Return Item Mismatch A
OM: Return Unfulfilled Referenced Line A
OM: Context Responsibility for Upgraded O OM: Notification A
Implementing Profile Options Summary
The following table indicates whether you can view or update the profile option and at which System Administrator level the profile options can be updated. The System Administrator level includes User, Responsibility, Application, and Site levels.
The table also displays if the profile option is Optional or Required:
Required: Requires you to provide a value
Optional: A default value is provided, so you only need to change it if you do not want to accept the default
If the profile option from the table is prefaced with an application short code, you can find additional information surrounding the profile option usage in the related Application User Guide.
The table also uses the following values to describe profile option controls for columns User, System Admin User, System Admin Resp, System Admin App, and System Admin Site:
Yes: You can update the profile option.
View Only: You can view the profile option value in the Profiles window, but you cannot change it.
No: You cannot view or change the profile option value.
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.
(AR) Oracle Receivables
(BOM) Oracle Bills of Material
(FND) Oracle Applications Foundations
(GL) Oracle General Ledger
(INV) Oracle Inventory
(QP) Oracle Advanced Pricing
(WSH) Oracle Shipping Execution
(OKC) Oracle Sales Contracts
The following table is a more in-depth description of each of the profile options.
Profile Options
Profile Option Name
System Admin. User
System Admin. Resp.
System Admin. App.
System Admin. Site
Default Value
Profile Category Names
OM: Add Customer
Yes - default is None
Yes - default is None
Customer Usage, Security, Forms UI
OM: Add Customer (Order Import)
Customer Usage, Security, Order Import
OM: Administer Public Queries
Forms UI, Security
OM: Allow Model Fulfillment Without Configuration
Fulfillment, Configurations
OM: Apply Automatic Attachments
Transaction Entry
OM: Assign New Set For Each Line
Scheduling
OM: Authorized to Override ATP
Scheduling, Security
OM: Automatically Interface Lines to IB on Fulfillment
Fulfillment
OM: Automatically Open Related Items Window
OM: Auto schedule
Scheduling
OM: Auto Push Group Date
Scheduling
OM: Cascade Service
Null - equivalent to Yes
Service, Transaction Entry
OM: Change SO Response Required
Electronic Messaging
OM: Charges for Backorders
OM: Charges for included item
OM: Charging Privilege
Pricing, Security
OM: Commitment Sequencing
OM: Configuration Quick Save
Transaction Entry, Configurations
OM: Contact Center Actions Menu Name
ONT_CONTACT_CENTER_SUB_MNU
OM: Context Responsibility for Upgraded Orders
No Default
OM: Copy Model DFF To Child Lines
Transaction Entry, Configurations
OM: Create Account Information
Customer Usage, Security
OM: Credit Card Privileges
Payments, Security
OM: Cust Item Shows Matches
Item Usage, Forms UI
OM: Customer Service Feedback
Returns, Portal UI
OM: Customer Service Report Defect
Returns, Portal UI
OM: DBI Installation
Deployment
OM: Debug Level
OM: Debug log Directory
OM: Default Sales Transaction Phase
Transaction Entry
OM: Default Blanket Agreement Type
Transaction Entry
OM: Default Blanket Agreement Transaction Phase
Transaction Entry
OM: Default Salesrep
Transaction Entry
OM: Discounting Privileges
Pricing, Security
OM: Display Actions Button vs. Pop list
OM: Display Current Selections in Pricing and Availability
OM: Display New Order After Copy
Transaction Entry
OM: Electronic Message Integration Event Sources
Electronic Messaging
OM: E-Mail Required On New Customers
Customer Usage
OM: Enable Group Pricing for DSP Lines
OM: Enable Related Items and Manual Substitutions
Item Usage,
OM: Enforce Check For Duplicate Purchase Order
Transaction Entry
OM: Enforce Shipping Method for Ship Sets
Scheduling
OM: Generate Diagnostics for Error Activities
OM: Generic Update Constraints Apply to DFF?
Transaction Entry
OM: Import Multiple Shipments
Null - equivalent to No
Order Import
OM: Included Item Freeze Method
Fulfillment, Configurations
OM: Interface Freight Tax Classification Code From Line
OM: Invoice Numbering Method
OM: Item Change Honors Frozen Price
OM: Item Flexfield
System items
Item Usage
OM: Item View method
OM: List Price Override Privilege
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
OM: New EDI Acknowledgment Framework
Deployment, Electronic Messaging
OM: Notification Approver
Upgrade, Returns
OM: Order Accept State For XML
Null - equivalent to Entered
Electronic Messaging
OM: Orders Purge Per Commit
Deployment
OM: Over Return Tolerance
Returns, Fulfillment
OM: Over Shipment Tolerance
Fulfillment
OM: Party Totals Currency
US Dollars
Customer Usage
OM: Population Of Buyer Code For Dropship
Fulfillment
OM: Preserve External Credit Balances
OM: Prevent Booking for Line Generic Holds
Holds, Transaction Entry
OM: Price Adjustment Modifier for AIA Order Lines
OM: Printed Document Extension Class Name
Deployment
OM: Promotion Limit Violation Action
OM: Quick Sales Order Form: Auto Refresh
Application
OM: Quick Sales Order Form: Defer Pricing
OM: Records on Summary Page for External Users
OM: Restrict Customer Items for Line Level Ship To Address
Item Usage
OM: Return Item Mismatch Action
Returns, Transaction Entry
OM: Return Unfulfilled Referenced Line Action
Returns, Transaction Entry
OM: Run Order Import for XML
Electronic Messaging
OM: Sales Order Form: Cascade Header Changes to Line
OM: Sales Order Form Preference
Sales Orders
OM: Sales Order Form: Refresh Method (Query Co-ordination)
Null - equivalent to Automatic Refresh with Repositioning of Cursor
OM: Sales Order Form: Restrict Customers
Customer Usage
OM: Sales Order Navigation From P&A form
OM: Schedule ATO Item Without BOM
Scheduling
OM: Scheduling Role
Scheduling, Forms UI, Security
OM: Send Acknowledgment for Change PO Response
Null - equivalent to No
Electronic Messaging
OM: Send Changed Lines to Pricing
OM: Sequence for TP Ship/Deliver Deadline
OM: Set Receivables Transaction Date as Current Date for Non-Shippable lines
OM: Show Line Details
OM: Show Process Messages Flag
OM: Source Code
ORDER ENTRY
Fulfillment
OM: Source for TP Early Ship / Deliver Date
OM: Use Configurator
Deployment, Forms UI,
Transaction Entry, Configurations
OM: Use Materialized
View for Items LoV (Honours Item Orderability Rules)
Fulfillment
OM: Under Return Tolerance
Returns, Fulfillment
OM: Under Shipment Tolerance
Fulfillment
OM: Unique Order Source, Orig Sys Document Ref Combination For Each Customer
Order Import
OM: Unit Price Precision Type
OM: UOM Class For Charge Periodicity
OM: View Cancel Lines
OM: View Closed Lines
OM: View Intercompany AR invoice
OM: View Pricing/Availability Information in Related Items
Credit Limit Selection
AR: Item Flexfield Mode (AR)
AR: Use Invoice Accounting for Credit Memos (AR)
HZ: Generate Contact Number (AR)
NULL - equivalent to Yes
HZ: Generate Party Number (AR)
NULL - equivalent to Yes
HZ: Generate Party Site Number (AR)
NULL - equivalent to Yes
Tax: Allow Ad Hoc Tax Changes (AR)
Tax: Allow Manual Tax Lines (AR)
EBTax: Allow Override of Customer Exemptions (AR)
Tax: Allow Override of Tax Classification Code (AR)
Tax: Calculate Tax on Credit Memos (AR)
Tax: Use Tax PL/SQL Vendor (AR)
Tax: Use Tax Vendor (AR)
BOM: Check for Duplicate Configuration (BOM)
BOM: Component Item Sequence Increment (BOM)
BOM: Configurator URL of UI Manager (BOM)
BOM: Default Bill of Material Levels (BOM)
Sequential Numbering (FND)
Default Country (FND)
Flexfields: Open Descr Window (FND)
Journals: Display Inverse Rate (GL)
At site level
INV: Capable to Promise (INV)
OKC: Enable Sales Contracts (OKC)
QP: Accrual UOM Class (QP)
No Default
QP: Blind Discount Option (QP)
QP: Item Validation Organization (QP)
No Default
QP: High Volume Order Processing Compliance (QP)
QP: Line Volume UOM Code (QP)
No Default
QP: Line Weight UOM Code (QP)
No Default
QP: Negative Pricing (QP)
No Default
QP: Return Manual Discounts (QP)
QP: Source System Code (QP)
No Default
QP: Unit Price Precision Type (QP)
QP: Verify GSA Violations (QP)
WSH: Internet Proxy URL (WSH)
Order Management Profile Option Descriptions and Settings
OM: Add Customer
ONT_ADD_CUSTOMER
This profile option determines which users who can access the Order Management Add Customer window to enter customers, customer addresses, and customer contact information. Select from:
All: Users can create new customers, customer addresses, and customer contacts.
None: User cannot create new customers, customer addresses, and customer contacts.
Address and Contact only: Users can access the Add Customer window to create both new customer addresses and/or customer contacts for existing customers only
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 allows you to define rules around who can create, update or delete customer data.For more information please refer to the Oracle Trading Community Architecture Administration Guide.
OM: Add Customer (Order Import)
ONT_ADD_CUSTOMER_OI
This profile option determines which users can create new customers and customer details when importing order using the Order Import concurrent program. Select from:
All: Users can create new customers, customer addresses, and customer contacts.
None: User cannot create new customers, customer addresses, and customer contacts.
Address and Contact only: Users can access the Add Customer window to create both new customer addresses and/or customer contacts for existing customers only
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 allows you to define rules around who can create, update or delete customer data. For more information please refer to the 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: 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_CHECK_WAIT_TO_FULFILL_LINE
The default is set to “N” which creating ONE Ship/Arrival Set per order. Set to 'Y' which creates a separate ship/arrival set per line, resulting in enforcing that each line is shipped complete.
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:
Yes: The entire set will be automatically rescheduled.
No or NULL: An error will occur. You can change the dates or quantities to make scheduling succeed.
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:
Yes: Order lines are scheduled automatically at the time of entry. Automatically display the Availability window within the Sales Order window when entering order line details.
No or NULL: Order lines are not scheduled automatically at the time of entry. Does not automatically display the Availability window within the Sales Order window when entering order line details.
Note: If the item or model is a standard item or has the item ATP flag enabled, ATP inquiry will automatically be performed on the item or model once it has been entered on an order line and a user exits the item field.
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: 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
This profile option controls the setting of the Calculate Price Flag when backorder lines are created.
Select from:
No or NULL: The Calculate Price Flag will be set to Freeze, and the pricing engine will not apply charges. Yes: The Calculate Price Flag will be set to Partial to enable charges to be calculated when the backordered item ultimately ships.
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:
Yes: Calculate and return charges for included items.
No: Do not calculate charges for included items.
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:
Full Access: You can modify and apply charges, but you cannot modify non-overridable charges.
View Only Access: You can only view charges.
Unlimited Access: You can modify and apply all charges including the non-overridable charges.
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:
Yes: Order Management populates the commitment applied and then will interface the applied commitment amount to Oracle Receivables.
Note: If you set this profile option to Yes, and you have not installed Bills Receivables for Oracle Receivables, Order Management will not capture the applied commitment amount and therefore will not relay commitment applied amounts to Oracle R no Warning or Error message is displayed.
No: Order Management does not calculate the exact commitment applied amount for an order line. Instead, the extended amount of the line is shown in the commitment applied field within the Sales Order Line, Pricing Tab window.
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 flexfie 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:
All: The user is permitted to create Accounts, Account Sites, Account Contracts, and related information
Account Site and Account Contact Only: The user is permitted to create Account Sites, Account Contracts, and related information only
None: The user is not permitted to create any of the above
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: Cust Item Shows Matches
OE_CUST_ITEM_SHOW_MATCHES
This profile option is obsolete.
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: DBI Installation
ONT_DBI_INSTALLED
This profile option is used to flag whether DBI has been installed. If the profile option is set to Yes, then data is collected for DBI usage. If the profile option is set to No, then data is not collected for DBI.
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 should be available in utl_file_dir parameter of the init.ora file (or check v$parameter) of the application database instance.
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 1,2 or 3 will be spooled out to the debug log.
Valid values for this profile option are:
NULL: Do not print any debug messages
1:Level 1; Print a limited subset of debug messages (level 1)
2:Level 2; Print a limited subset of debug messages, including level 1
3:Level 3; Print a limited subset of debug messages, including levels 1,2
4:Level 4; Print a limited subset of debug messages, including levels 1,2 3
5:Level 5; Print all debug messages
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 once 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.
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 should be allowed to setup only at the responsibility and site level.
OM: Default Sales Agreement Transaction Phase
ONT_DEF_BSA_TRANSACTION_PHASE
This profile to defaults the order type to generate sales agreement number. This profile should be allowed to setup only at the responsibility and site level.
OM: Default Salesrep
ONT_DEFAULT_PERSON_ID
A profile to default the dummy salesrep for the Telesales Order. The Telesales team will pass the salesrep_id for the order if that information is available in the eBusiness Center. If no salesrep is passed to the Sales Orders form, then Order Management will default the salesrep value from the 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: 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:
Full: Ability to apply any valid discount against an order or order line, as long as the order type of the order does not enforce list prices. (Default value).
Non-Overridable Only: Ability to apply only non-overridable discounts against an order or order line.
Unlimited: Ability to apply any valid discount against any order or order line, regardless of whether the order type of the order enforces list prices.
None: No privileges, view-only access.
Note: A Null value for this profile option is handled as if you selected the value FULL.
OM: Display Actions Button vs. Poplist
Controls whether the traditional button for Actions or a pop list will be used to display available Actions. Valid values are: Button and Pop list. The default value will be Button for backward compatibility.
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 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 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:
Yes: E-mail address is required, for both the customer and customer contact, when defining or updating a customer or customer contact.
No or NULL (the default): E-mail address is not required when defining or updating either a customer or customer contact.
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: 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 updatin this profile option does not control order line fields other than the flexfield attributes. Select from:
Yes: (the default): you cannot update processing-constrained flexfield attributes on closed orders.
No: you can update processing-constrained flexfield attributes on closed orders.
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 via Order Import. If this profile option is set to Yes, the orig_sys_shipment_ref will also be used in determining the uniqueness of the line record in combination with order_source_id, orig_sys_document_ref and orig_sys_line_ref.
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:
Ready to Pick/ Purchase Release: If the value for this profile option is set to Ready to Pick / Purchase Release, both the Inventory Interface and Purchase Release workflow activities will explode the included items when processed during pick release and purchase release, respectively.
Entry: If the value for this profile option is set to Entry, included items will explode on the sales order when moving to a new line or performing a save.
Note: If the Order Management profile option OM: Configuration Quick Save is set to Yes, you should not set the value of this profile option to Entry. If you do, the Quick Save functionality for streamlining model class order lines will be unavailable.
Booking: If the value for this profile option is set to Booking, The Booking Activity will explode included items when processed.
None: When the profile is set to this value, the included items will not be processed. Even if the model has included items defined in its BOM, these will not be reflected in Order Management. This value should not be used if you have included items defined in your BOM for models.
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:
Automatic: Choose this value if you want to create invoices with automatic numbering. Transaction numbering is controlled automatically by the Receivables AutoInvoice concurrent program. If you set the profile option to this value, you must use an invoice source with automatic transaction numbering.
Delivery Name: Choose this value if you want to create invoices for all shippable lines based on Delivery Name. If you process order lines in a delivery in more than one batch, then this function modifies the delivery name with a number to create a unique transaction number.
If you set the profile option to this value, you must use an invoice source without automatic transaction numbering.
Note: Delivery based invoicing is not supported if order lines within the delivery belong to different operating units.
Note: In some cases, you will require both options to be enabled as you may have both invoice source and non-delivery invoice source. Use the Transaction Type "Invoice Order" to specify both. You are allowed to choose invoice source regardless of the setting of the OM: Invoice Numbering
Method, to allow for those users who have customizations around invoice
numbering.
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:
Yes: Order Management will not change the value of the calculate price flag, whose origi the original value will control whether the order line gets repriced.
No: Order management will set the calculate price flag to Y, and the order line will be repriced.
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:
1: Only return item descriptions, with child indentations.
2: Only return item description without child indentations.
3: Display the concatenated item segment values with child indentations.
4: Display the concatenated segment values without indentation.
OM: Level of Credit Checking
This profile option is obsolete and no longer used.
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: Log Directory for Generated Packages
This profile option is no longer used by Oracle Order Management.
OM: Manual Linegroup Adjustment
This profile is no longer used by Oracle Order Management.
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.
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: Number of Days to Backdate Bank Account Creation
This profile is no longer used by Oracle.
OM Order Accept State For XML
ONT_XML_ACCEPT_STATE
OM: Order Information Regulatory logging
This profile is no longer used by Oracle Order Management.
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 Intialize 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 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 busine