Br100 SCM - Om

AIM
BR.100 APPLICATION SETUP

ONETEREX
ORDER MANAGEMENT/SHIPPING
EXECUTION
Author:
Jayesh Patel
Creation Date:
January 11, 2006
Last Updated:
January 11, 2006
Document Ref.:
BR100-OM
Version:
1.0
Approvals:
BR.100 Application Setup
Order Management
January 11, 2006
Document Control
Change Record
1
Date
Author
Version
Change Reference
11-Jan-06
J Patel
Draft 1a
No Previous Document
Reviewers
Name
Position
Distribution
Copy
No.
Name
Location
1
2
3
Library Master
Project Library
Project Manager
Note To Holders:
If you receive an electronic copy of this document and print it out, please
write your name on the equivalent of the cover page, for document control
purposes.
If you receive a hard copy of this document, please write your name on the
front cover, for document control purposes.
File Ref: 81761613.doc
(v. 1 )
Application Set Up Control Sheet - Order Management
Order Management
January 11, 2006
Contents
Document Control.......................................................................................ii
Initial Tasks Setup/SA: Define Responsibilities..........................................1
Application Set Up Control Sheet - Order Management..............................3
OM: Define System Level Profile Options...................................................6
Initial Tasks Setup/OM: Define Descriptive Flexfields (DFFs)...................18
OM: Enable Parameters...........................................................................22
OM: Define QuickCodes...........................................................................23
OM: Define Order Import Sources ...........................................................24
OM: Define Processing Constraints .........................................................26
OM: Define Pricing ..................................................................................27
OM: Define Defaulting Rules ...................................................................29
OM: Define Modifiers (Discounts) ............................................................30
OM: Define Transaction Types.................................................................32
OM: Order AOL Document Sequences (Order Numbering).......................49
OM: Order Assign Document Sequences..................................................50
OM: Define Credit Checking ....................................................................52
OM: Define Holds.....................................................................................53
OM: Define Attachment Document Categories........................................54
OM: Define Attachments..........................................................................55
OM: Define Freight Carriers .....................................................................59
Additional Freight Carriers will be added as needed...........................59
OM: Define Freight Cost Types.................................................................60
OM: Define Shipping Documents.............................................................61
(v. 1 )
Order Management
January 11, 2006
OM: Define Release Sequence Rules.......................................................64

OM: Define Release Rules........................................................................65
OM: Define Pick Slip Grouping Rules........................................................68
OM: Define Shipping Parameters ............................................................70
OM: Define Transportation Calendars......................................................72
OM: Define Shipping Exceptions ...........................................................74
OM: Define Shipping Document Categories.............................................75
OM: Shipping Document Sequences ........................................................76
OM: Assign Shipping Report Document Sequences..................................77
OM: Shipping Execution Grants ...............................................................78
Open and Closed Issues for this Deliverable.............................................79
Open Issues.........................................................................................79
Closed Issues.......................................................................................79
(v. 1 )
Order Management
January 11, 2006
Initial Tasks Setup/SA: Define Responsibilities

System Administration>Security>Responsibilities>Define
Process:
Business Area:
Date:
System Admin
Responsibilities
Control Number:
Priority (H, M, L):
Process Owner:
Terex Corporation
H
Description: Use this form to define your unique responsibilities for each operating unit.
The following levels of OM responsibilities are needed:
OM Manager = Order Management Super User
OM User
Responsibility Name
Application
Resp Key
Data Group
Application
Menu
Req Group
Name
Applicatio
n
Order Management
Super User
Oracle Order
Management
Order
Management
Super User
Standard
Oracle Order
Management
ONT_SUPER_
USER
Oracle Order
Management
Oracle
Order
Managemen
t
(v. )
Menu
Exclusions
Order Management
January 11, 2006
System Administration>Profile>System
Profile
Site
HR: Business Group
Setup Business
Group
Setup Business
Group
HR: Security Profile

HR: User Type
Order
Management
Super User,
DHM US
Order
Managemen
t Super
User, DHM
CN
HR User
HR User
United States
United States
Partially Used
Partially Used
MO: Operating Unit

GL: Set Of Books
Default Country
United States
Currency:Mixed Currency Precision
Sequential Numbering
Not Used
(v. )
Order Management
January 11, 2006

Environment Name:
Workflow
SubWorkflow
Name
Machine:
Setup Task
OM: Define Profile Options

OM: Define Item Validation System
Parameter and Operating Unit
OM: Define Invoicing
OM: Define Salespersons
OM: Define Tax Features
OM: Define Quickcodes
OM: Define Freight Charges and
Freight Carriers
OM: Define Order Processing
Workflow
OM: Define AOL Document
Sequences (Order Numbering)
OM: Define Order Import Sources
OM: Define Processing Constraints
OM: Define Pricing
OM: Define Customer Agreement
OM: Define Defaulting Rules
(v. )
Responsibility
Type (definition, execution, or

both):
Due Date
QA Responsibility
QA Due Date
Signature Approval
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
N/A
J Patel

Workflow
SubWorkflow
Name
Setup Task
OM: Define Transaction Types

OM: Assign Workflows to
Transaction Types
OM: Define Discounts
OM: Define Credit Checking Rules
OM: Define Automatic Holds
OM: Define Attachments
OM: Define Freight Carriers
OM: Define Freight Carrier - Ship
Method Relationships
OM: Define Shipping Document Sets
OM: Define Release Sequence Rules
OM: Define Release Rules
OM: Define Pick Slip Grouping Rules
OM: Define Container-Load
Relationships
OM: Define Shipping Parameters
OM: Define Freight Cost Types
OM: Define Transportation Calendars
OM: Define Shipping Exceptions
OM: Define Shipping Document
Categories
OM: Define Shipping Sequences
(v. )
Order Management
January 11, 2006
Responsibility
Due Date
QA Responsibility
QA Due Date
Signature Approval
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
J Patel
N/A
J Patel
J Patel
N/A
N/A
J Patel
J Patel

Workflow
SubWorkflow
Name
Setup Task
OM: Assign Shipping Report

Document Sequences
OM: Assign Shipping Execution
Grants
(v. )
Order Management
January 11, 2006
Responsibility
Due Date
QA Responsibility
QA Due Date
Signature Approval
J Patel
J Patel
Order Management
January 11, 2006
OM: Define System Level Profile Options

Application Administrator>Profile Options
Form
Name
Profile Options
Process:
Order Management
Control Number:
<Control Number>
Business Area:
<Business Area>
Priority(H, M, L):
<Priority (H, M, L)>
Date:
January 12, 2006
Process Owner:
Description: Use this form to define profile options to specify certain implementation parameters, processing options, and system
options at the Site level, Application level or at the Responsibility level. Define User Profile Options in Order Management (see below).
Note: A O in a row means optional at that level
Application = Oracle Order Management
Responsibility = OM Super User
Profile Option Name
Description
Value Resp Level
GML: OM Integration
This profile option controls certain functionality when using OPM with Order Management. Set this profile option to Yes to continue
with the proper setup and enter transactions which are recognized from Order Management.
Default is Yes not updateable
No
Controls the level of access to the Add Customer form, which is available with OM Family Pack F onwards.
Address & Contact
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 access the Add Customer window to create new customers, customer addresses, and
customer contacts.
None: User is not given access to the Add Customer form.
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.
This profile option determines which responsibility is able to create and update public queries This profile
option is required.
This profile option determines whether rule-based attachments are applied without user intervention. This
profile is optional
Allows user to override the ATP date.
No
This profile option controls scheduling when a new line is inserted into an e existing set. If the new line
cannot be scheduled on the same date as the rest of the set, this profile is used . If this profile is set to Yes,
the entire set will be automatically rescheduled. If the profile is set to No, an error will occur. You can change
the dates or quantities to make scheduling succeed. This profile can be overridden for a parameter specific
to customers or customer sites by setting a value in the Customer window. The default value is null
This profile option determines the default setting of the use of autoscheduling
Yes- Order lines are scheduled automatically at the time of entry.
No-Order lines are not scheduled automatically at the time of entry.
Yes
OM: Activate Change Management

System
OM: Add Customer
OM: Add Customer (Order Import)
OM: Administer Public Queries.

OM: Apply Automatic Attachments
OM Available to Overide ATP
OM: Auto Push Group Date
OM: AutoSchedule
(v. )
Yes
No
Yes
Yes At Resp Level
Yes

Profile Option Name
Order Management
January 11, 2006
Description
Value Resp Level
Also to set BOM: Automatic Reservation to Yes

OM: Branch Scheduling
This profile option is for internal use only. Do not attempt to enter or modify the value of the profile option.
Yes
OM: Charges for Backorders
To include Freight Charges for Backorder
Yes
OM: 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 include 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.
Configuration.
This Profile option control your ability to manually apply freight and special charges on an order or order line.
Choose 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
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 commitment amount applied to Oracle Receivables.
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.
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
Receivables; no Warning or Error message is displayed.
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.
Configuration.
This profile option is used to set applications context for deferred activities on upgraded orders and order
lines. This profile is required. (The ability to enter any option in this field has been disabled. This profile
option may no longer be valid or used. Further Investigation with Development is recommended.)
No
OM: Charging Privilege
OM: Commitment Sequencing
OM: Configuration Quick Save
OM: Context Responsibility

OM: Copy Model dff to child lines
OM: Credit Card Privileges
OM: Credit Check Engine API Code

Flow
OM: Credit Memo Transaction Type
OM: Credit Salesperson for Freight
(v. )
Unlimited Access By
Responsibility
Yes
No
N/A
Yes
This profile limits the amount of credit card information displayed in the Sales Orders window and limits who
can perform manual or on-line authorizations. The authorization code and credit card number fields displays
only the last four digits if the profile option is set to None or Limited. On-line and manual authorizations are
allowed if this profile is set to All or Limited. Choose from All, Limited or None. This profile is optional.
Set to MULTI will switch the code to the new Multi currency API in Verify_paymentI
N/A
This profile option value is transferred to Receivables if no value is defined for the credit memo transaction
type This profile option is required
This profile option specifies whether to credit the Salesperson on the invoicing line
or order header for freight charges when the freight charges are treated as revenue.
Credit Memo
Multi
No
Order Management
January 11, 2006
Profile Option Name
Description
Value Resp Level
OM: Cust Item Shows Matches
This profile option determines whether Order Management defaults the item with the highest ranking item or
shows the list of all the matched Internal Items numbers when a customer item number is used and that
customer item is crossed referenced to more than on internal item. This profile option required. The default
value is No
This profile option determines whether Order Management honors customer relationships when entering bill
to and ship to locations for a customer on an order. (This profile option is currently used only in and is not
valid in any other Oracle Application) Order management honors customer relationships for agreements and
commitments regardless of this profile options setting. This profile option is optional and the default setting
is Yes.
No
OM: Customer Relationships
OM: DBI Installation
No
OM: Deactivate Pricing at

Scheduling
OM: Debug Level
OM: Debug Log Directory

OM: Discounting Privilege
OM: E-Mail Required on New

Customers
OM: Employee for Self-Service

Orders
OM: Estimated Authorization
Yes
(v. )
This profile option should not be set unless directed by an Oracle Representative.
Null
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 7a 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
This profile option determines the default directory used to store log file outputs when performing Order
Management debugging.
This profile option provides the choice of controlling users ability to apply discount on an order or order line.
This profile option is optional. The default value is Full.
The options are:
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
Non-Overridable only-Ability to apply on non-overridable discounts against an order or order line.
Unlimited- Ability to apply any valid discount against any order or order line regardless whether of the order
type of the order enforces list prices.
See NOTE <Note:152669.1>
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. Options are:
* Yes: E-mail address is required, for both the customer and customer contact, when defining or updating
a customer or customer contact.
* No: E-mail address is not required when defining or updating either a customer or customer contact.
The default for this profile option is Null. Can only be set at the site level under system administrator and is
optional. Not visible to any other level.
See NOTE <Note:152669.1>
This profile option acts as a "default" employee assignment for requisitions in the event that the user that
created the sales order does not have an associated employee. The profile option should be set only by a
system administrator (i.e., not settable by the user) and must be accessible at the site, application,
responsibility and user levels.
This profile option determines the estimated number of days a credit card authorization is assumed to be
/usr/tmp/obws1
(Instance Name)
Unlimited-to be set at
the resp Level
No
N/A
21 requires iPayment
Order Management
January 11, 2006
Profile Option Name
Description
Validity Period
valid. This profile is required and the default value is 21 days
OM: GSA Discount Violation Action
This profile 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 save price list. This profile option is optional and the
default value is Warning.
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
OM: Generic Update Constraints

Apply to DFF
Value Resp Level
No GSA not used

Yes
Order Management Profile Options
lines; this profile option does not control order line fields other than the flexfield
attributes.
If you select Yes' (the default), you cannot update processing-constrained
flexfield attributes on closed orders.
If profile is set to 'No', you can update processing-constrained flexfield
attributes on closed orders.
This profile option is updateable at the site level.
Regardless of this profile option, you can set up constraints specific to flexfield
attribute constraints.
OM: Import Multiple Shipments
No reference in OM Implementation Guide. Left as Blank No LOVs
Blank
OM: Included Item Freeze Method
This profile option determines the point in the orders status at which the included items from a
configurations bill of material are added as lines on the order. This profile option is Required and the
default value is Booking.
This profile option determines whether or not the Invoicing activity generates invoice numbers based on the
delivery name. This profile option is required and the default value is Automatic
This profile option value is transferred to Receivables if the value is null for your Transaction type. This
profile option is required and there is not default.
This profile option value is transferred to Receivables if no value is defined for the Transaction Type. This
profile option is Required and there is not default.
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 original value is honored; 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.
This profile option determines the structure of the Item Flexfield (System Items) used by Order Management .
This structure should be the same as across all applications in the same database. This profile option is
Required and there is not default.
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.
Booking
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
Yes Required for

Config extension
OM: Invoice Numbering Method

OM: Invoice Source
OM: Invoice Transaction Type
OM: Item Change Honors Frozen
Price
OM: Item Flexfield

OM: Item View Method
OM Negative Pricing
(v. )
Automatic
Invoice
Invoice
No
System Items
Null

Profile Option Name
Description
OM: Non-Delivery Invoice Source

OM: Notification Approver
OM: Order Infromation Regulatory

logging
OM: Orders Purge Per Commit

OM: Over Return Tolerance
OM: Over Shipment Tolerance
OM: Over Shipment Invoice Basis
OM: Party Totals Currency
OM: Payment method for Credit
Card Transactions
OM: Populations of Buyer code for
Dropship Lines
OM: Process Payment Immediately

at Booking
OM: Promotion Limit Violation
Order Management
January 11, 2006
(v. )
Value Resp Level
negative unit price can be entered on a price list

Note: Returns
This profile option value is transferred to the Receivables if the OM-Invoice Numbering Method profile is set
to Delivery and the line is non-shippable. This profile option is required and there is not default.
This profile option is used during upgrading Order Entry Order Cycle History to
Order Management Workflow History. Setting this profile option enables you to
send workflow Notifications (Approval or FYI notifications) to the Role that the
option is set to for the following Oracle Order Management seeded Workflow types:
NOTE: Does Not Apply to Bradford
This profile option is used to determine if you enable logging OPM Regulatory
history dispatching within the Order Information portal. Select from:
Yes: Enable logging OPM Regulatory history dispatching within the Order
Information portal. Document and user details are stored within the dispatch
histories using an API. MSDS document will be displayed to a user only if a
successful log for the request is created.
No: Do not enable the logging of OPM Regulatory history dispatching within
the Order Information portal.
The default for this profile is No.
This profile option determines how many order the purge process should purge before performing a commit.
This profile option is defaulted at 100
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. This profile option is
required and the default value is zero (0)
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. This profile option is
required and default value is zero (0)
This profile option determines whether to invoice the ordered quantity or the shipped quantity for an over
shipment. This profile option can be overridden for a parameter specific to customers or customer sites by
entering a value in the Customer window. This profile option is required and the default value is Shipped
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.
This profile option is used by the credit card authorization process as a default for the primary payment
method if a specific customer does not have one. This profile option is optional and there is no default.
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:
Order Creator: The suggested_buyer_id field in the po_requisitions_interface
table is populated with the buyer details (the employee_id of the person who
enters the sales order). Your sales people must be defined as a buyers in Oracle
Purchasing.
NULL: Oracle Purchasing will perform the Get_Suggested_Buyer_Id function
(retrieve the buyer information from the master item)
Note: If you set the value of this profile option to NULL, you will
be unable to select the value Buyer for the input parameter Group
prior to submission of the Oracle Purchasing Requisition Import
concurrent program.
This profile option is used by the credit card authorization process as a default for
the primary payment method if a specific customer does not have a primary
payment method defined.
This system level profile option determines the hold action Order Management will
Null
N/A Upgrades only
No
100
0
0
Invoiced Shipped Qty
US dollar
Null
Null
No Need iPayment
Null

Profile Option Name
Order Management
January 11, 2006
Description
Value Resp Level
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:
Place holds where violated (either Line or Order): If the pricing engine returns
an initial promotional hold, place a hold for the corresponding order or order
line.
No holds applied: If the pricing engine returns an initial promotional hold, do
not apply a hold for either an order or order line. Allow the order or order line
to continue processing within its associated workflow.
Place order on hold when any violation occurs (both Line and Order): If the
pricing engine returns an initial promotional hold, irrespective of the hold level,
place the order on hold, in addition to any order lines that may be marked for
promotional hold.
This profile option is optional, and the default is Null.
OM: Reservation Time Fence
OM: Return Item Mismatch Action
OM: Return Unfulfilled Referenced

Line Action
OM: Risk Factor Threshold for

Electronic Payments
OM: Run Order Import for XML
OM: Sales Order Form: Cascade

Header Changes to Line
OM: Sales Order Form: Restrict
Customers
(v. )
this profile option controls the automatic reservations during scheduling. This profile option represents the
number of days in to the future that scheduling will reserve. The profile default value is Null which means
that scheduling will not automatically reserve. This profile option is used during the autoscheduling and also
by the scheduling workflow activity and concurrent program to perform reservations. This profile option is
optional.
This profile option controls what should occur if you try to change the item ID of a referenced return line.
This profile option is required and the default value is Allow. The profile option values are:
Reject - Line processing is halted with an error message
Warning- Line processing is continued with a Warning.
Allow- Line processing continues with no warning or error.
This profile option is used for returns to control return of unfulfilled lines. This profile option is required and
default value is Allow.
The option Choice are:
Reject- Do not create return line if the referenced line is non-fulfilled.
Warning- Create a return line with a Warning if the referenced line is non-fulfilled.
Allow- Create return line without Warning if the referenced line is non-fulfilled.
This profile option set a threshold for determining whether a credit card authorization qualifies as a high risk.
Scores can range from 1 to 100, where 1 refers to a to a risk free authorization and 100 refers to a high risk
authorization. If the score for a transaction exceeds this threshold, Order management will put the order on
a High Risk Hold. This profile option is optional the default is 50.
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:
Asynchronous: Order Import will not automatically be submitted for execution once XML data has been
interfaced. You must manually submit the concurrent program after XML data has been interfaced to Order
Management.
Synchronous: Order Import will automatically be submitted for execution once XML data has been
interfaced to Order Management. The default for this option is NULL.
Note: Using XML
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.
Warning
Null
50
Null
All resp should be set

at ASK ME
Global Organization

Profile Option Name
Order Management
January 11, 2006
Description
Value Resp Level
Note: Changed from Global to Current

OM: Schedule Line on Hold
OM: Set Receivalbes Transaction
Date fro Non-Shippable Lines
OM: Show Discount Details on

Invoice
OM: Show Line Details
OM: Source Code
OM: Source Code2-1-1
OM: Under Return Tolerance
OM: Under Shipment Tolerance
OM: Use Configurator
OM: View Cancel Lines
OM: View Closed Line
OM: Under Shipment Tolerance
(v. )
This profile option controls whether scheduling will attempt to schedule line that are on hold. This profile
option is optional and the default value is Null, which is equivalent to Yes
This profile option determines if the Oracle Receivables transaction date will be populated with the system
date (SYSDATE) for non-shippable order or return lines.
Select from:
Yes: Populate the Oracle Receivables transaction date for non-shippable order or return lines with the
current system date.
No: Do not populate the Oracle Receivables transaction date for non-shippable order or return lines with
the current system date. Populate the Oracle Receivables transaction date for non-shippable order or return
lines with the corresponding line order date or line return date. This profile option is optional, and the default
is NO.
This profile option determines whether the discount details are passed to Oracle Receivables for printing on
an invoice. This profile option is Required and the default value is No
This profile option determines whether the line details of a model are displayed in Sales Order. You can
toggle the display of the line details using the Tools menu from the Sales Order Window. This profile option is
Optional and the default value is No
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. This profile option is required and there is not default.
Obsolete
Yes
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. This profile option is required and the default is zero (0).
This Profile Option indicates the percentage by which an order 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. This profile option is Required and the default value is zero (0)
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:
Yes: Use the Oracle Configurator application to enter you configurations via Oracle Configurator user
interfaces. Oracle Configurator should be installed and setup if you chose this value. See: Oracle Configurator
Installation Guide.
No: Use the Oracle Order Management application to enter your configurations via the Options window.
The default for this profile option is No.
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:
Yes: The Cancel check box will be automatically selected when sorting sales order lines within the Sales
Order Lines Tab, Sort window. Cancelled order lines will not be displayed once the sort completes.
No: The Cancel check box will not be selected when sorting sales order lines within the Sales Order
window, Lines Tab sort window. Cancelled order lines will be displayed once the sort completes if you do not
manually select the check box.
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:
Yes: The Closed check box will be automatically selected when sorting sales order lines within the Sales
Order Lines Tab, Sort window. Closed order lines will not be displayed once the sort completes.
No: The Closed check box will not be selected when sorting sales order lines within the Sales Order
window, Lines Tab sort window. Closed order lines will be displayed once the sort completes if you do not
manually select the check box.
This Profile Option indicates the percentage by which an order 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. This profile option is Required and the default value is zero (0)
Yes
Yes
No
Order Entry
Order Entry
0
Yes
Yes
Yes
Order Management
January 11, 2006
Profile Option Name
Description
Value Resp Level
QP: Accrual UOM Class
Null
QP: Allow Duplicate Modifiers
Default value: Null

This is required if your business gives non-monetary accruals as benefits. Specifies the unit of measure class
to be used for defining accrual units of measure. The Modifier Setup window displays all units of measure in
this class when entering the Benefit UOM for an accrual.
Values
All UOM classes defined to Oracle Applications. This profile option is visible and can be updated at site and
application levels.
Default value: Null
Query saved in Public folders can be deleted or renamed only if the value of the profile QP: Administer Public
Queries is set to Yes.
Values
Yes: Enables queries saved in Public folders to be deleted or renamed.
No: Queries saved in Public folders cannot be deleted or renamed.
Future functionality
QP: Cascade Asked for Promotion
Advance Pricing functionality
No
QP: Cross Order Volume Period1
Default value: Blank

This is required if you will be running the cross order volume load program. This defines the number of days
of order lines that the load program will accumulate and total. This value must not be the same as the value
in QP: Cross Order Volume
Period 2 or QP: Cross Order Volume Period 3.
Values
Always expressed in days.
This profile option is visible and can be updated at the site and application level.
This is required if you will be running the cross order volume load program. This defines the number of days
of order lines that the load program will accumulate and total. This value must not be the same as the value
in QP: Cross Order Volume
Period 1 or QP: Cross Order Volume Period 3.
Value
Always expressed in days.
This profile option is visible and can be updated at the site level.
This is required if you run the cross order volume load program. This defines the number of days of order
lines that the load program will accumulate and total. This value must not be the same as the value in QP:
Cross Order Volume Period 1 or QP: Cross Order Volume Period 2.
Value
This value is always expressed in days.
This profile option is visible and can be updated at the site level.
Default Value: No
Value
Yes: When this profile is set to Yes, the Build Contexts program builds the contexts from the dynamic
package generated by the Build Attribute Mapping Rules program and from the custom package created by
the customers.
No: When this profile is set to No, the Build Contexts program builds the contexts only from the dynamic
package generated by the Build Attribute Mapping Rules program.
Default value: Request Viewer Off
Value
Request Viewer On: When set to on, the Request Viewer captures pricing request details into the pricing
debug tables and debug log information into the debug log table. The debug log text file is also created.
Request Viewer Off: When set to off, nothing is written into pricing debug tables and debug log table. The
debug log text file will not be created.
Null
QP: Administer Public Queries
QP: Cross Order Valume Period2
QP: Cross Order Valume Period3
QP: Custom Sourced
QP: Debug
(v. )
Null
Yes
Null
Null
No
Request Viewer Off

Profile Option Name
Description
QP: Get custom Price Customized
QP: Insert Formula Step Values

into Temp Table
QP: Inventory Decimal Precision

QP: Item Validation Organization
QP: Limit Exceed Action
QP: Line Volume UOM Code
Order Management
January 11, 2006
(v. )
Value Resp Level
Request Viewer On, but Debug Log is not visible in Viewer: When this is set, the Request Viewer captures
pricing request details into the pricing debug tables, but debug log information is not written into the debug
log table. The debug
log text file will be created.
Another profile option, QP: Set Request Name, can be used in conjunction with the QP: Debug profile option.
When the QP: Set Request Name is set to Yes, the Request Name field will be prefixed with the Order ID.
This profile option can be updated at the user level and is active for the transactions of the user who set this
Profile optionother users transactions are not affected.
Default value: No
Indicates if, when processing formulas, the pricing engine evaluates the line type function. If your
organization wants to use this formula line type, you must: Customize the GET_CUSTOM_PRICE function.
Set this profile option to Yes.
Values
Yes: When processing formulas, the pricing engine evaluates the line type function. This profile option must
be set as Yes if the package body for QP_CUSTOM is coded.
No: When processing formulas, the pricing engine does not evaluate the line type function.
This profile option can only be updated at the site level.
This profile is required if your business needs more pricing formulas than are provided in basic pricing. A
pricing formula consists of a formula expression (mathematical expression) consisting of step-numbers and formula lines that
correspond to each step-number in the formula expression. Each formula line associates with a formula line type. There are six
formula line types in Oracle Advanced Pricing (three in basic pricing). One type is function. Oracle Advanced Pricing provides a
function called Get_Custom_Price with a standard set of input parameters. The user is provided the flexibility of writing any custom
code in the function body and use the input parameters supplied by the pricing engine. The value returned by the Get_Custom_Price
function can be used in a formula expression. To use the customized Get_Custom_Price functions return value in a formula, the user
must set up a formula with a line type of function (the formula may or may not have other formula lines). The Get_Custom_Price
function can be used in any number of formulas at the same time because the formula ID is an input parameter to the function and
assists the user differentiate code logic.
Default value: No
This profile option can be set only at the site level using the System Administrator responsibility.
Values
Yes: If set to Yes, the step values of each formula attached to a price list line is evaluated by the Pricing
Engine and inserted into the temporary table QP_FORMULA_STEP_VALUES_TMP. This can be referenced by
customized code.
No: If set to No, the step values are not inserted into the temporary table described above.
Future Use.
This profile indicates the Oracle Manufacturing Organization that Items are validated and view against when
entering Item in the price List and Modifier user interface. This profile option is required and there is no
default vale
Default value: Hard - Adjust Benefit Amount
This profile option defines the default action codes for promotion and modifier limits. It specifies the action
for the pricing engine if a pricing request exceeds a promotional limit. This profile option is based on the
lookup type Limit Exceed Action.
Values
Soft--Full Benefit Amount: Applies the full benefit to the order even if the transaction exceeds the defined
limit.
Hard--Adjust Benefit Amount: Adjusts the order benefit amount so that the order meets but does not
exceed the promotional limit. A status message is sent to the calling application such as Order Management
to place a promotional hold on the order.
This profile option is visible and can be updated site level using the System Administrator responsibility.
Required if your business needs to define Qualifiers Rules which include the seeded Qualifier Line Volume.
Specifies the unit of measure of the Line Volume Qualifier. The attribute sourcing API converts the item on
the request line into its primary UOM and then uses the Volume attribute of the Item to derive the Line
No
No
10
OU Item Validation Org
Hard-Adjust Benefit
Amount
Null

Profile Option Name
Order Management
January 11, 2006
Description
Value Resp Level
Volume UOM specified in this profile option

QP: Line Weight UOM
QP: Multi Currency Installed
QP: Negative Pricing
QP: Price Rounding
Required if your business needs to define Qualifiers Rules which include the seeded Qualifier Line Weight
Specifies the unit of measure of the Line Weight Qualifier. The attribute sourcing API converts the item on the
request line into its primary UOM and then uses the Weight attribute of the Item to derive the Line Weight
UOM specified in this profile option
This profile option is optional and there is no default value.
Default value: No
If you have global customers or do pricing in different currencies, the multi-currency feature enables you to
maintain a single price list for multiple currencies. Once the profile option is set to Yes, the concurrent
program Update Price Lists with Multi-Currency Conversion Criteria must be run to enable the price list
windows for multi-currency usage.
Values
Yes: If the profile QP: Multi-Currency-Installed is Yes, the incoming pricing request will send order currency,
pricing date, product attributes, pricing attributes and qualifier attributes. The pricing engine matches the
order currency with the price list's Base Currency or Conversion Criteria To-Currency
No: When the profile QP: Multi-Currency-Installed is No, the order currency is matched with the price list
base currency, which is the current behavior.
Warning: Once the concurrent program has been run successfully, all existing price list and
agreement windows are converted to multi-currency price lists. Users should not return to NON
multi-currency price lists. Changing the profile option back to No may cause undesired results if
conversion criteria have been used. Oracle does not support changing the setting back to No.
The program must be run initially only once to activate the multi-currency feature; otherwise,
data corruption may result.
This profile option is visible and can be updated at the site and application level.
The Default value should only be changed if your business needs to define a negative price on a Price List
This profile controls whether a negative price can be entered on a Price List. This profile option is required
and default value No. The options are:
Yes- Allow Negative pricing
No- Do not allow Negative Pricing
This profile option controls how the value for the rounding factor is derived and how it is used in price lists;
for example, Price List Rounding Factor, Currency Precision or none. The Advanced Pricing - Price Lists
window rounds, stores and
displays the list price after applying the Precision/Rounding Factor based on the profile option setting. The
Round To value in the Advanced Pricing - Price Lists window cannot be updated if the profile option is set to
Enforce Currency Precision. Also, allowed values for rounding factor will be limited to the price list currency
precision. The Rounding Factor value entered in the price list is used to store the rounded value. for storing
and Currency Precision for displaying list price.
QP: Pricing Transaction Entity

QP: Promotional Limits Installed
(v. )
Null
YES
Yes
Null
Order Fulfillment
Default value: No
This profile option activates the promotional limits feature in Oracle Advanced Pricing to enable users to
manage promotional limits and related functions. The initial default value is N for No which means the limit
feature is not active. The System Administrator must change this value to Y for Yes to be able to use limits.
Only the System Administrator can change the value of this profile at site and application levels only. Other
users can view the profile only.
Values
Yes: Enables the promotional limits features to be used.
No: Disables the promotional limits features.
Warning: Once the QP: Promotional Limits Installed profile option is enabled, leave the promotional limits
active with the value of Y. Do not disable the QP: Promotional Limits Installed profile option once it has been
enabled!
No
Order Management
January 11, 2006
Profile Option Name
Description
Value Resp Level
QP: Return Manual Discounts
A modifier can be applied to the order automatically at the time of pricing or can be returned to the calling
application (Oracle Order Management) and stored in price adjustments table, so that users can choose
adjustments to be applied on the order line.
The following modifiers types can be manual:
Discounts
Surcharges
Price break lines
Freight Charges
Manual modifiers can be set at all levels (line, group of lines, and order), and always be in the null bucket.
Manual adjustments can be overrideable.
Values
Yes: In basic pricing, Y is the default and should not be changed (this duplicates R11 functionality). One automatic discount is
applied. All manual discounts are returned for user selection. All the automatic discounts that are deleted as part of incompatibility
processing return as manual discounts available for user selection.
No: All automatic and manual discounts run through incompatibility processing and one from each incompatibility group is
returned. An automatic discount may be deleted and a manual discount may be selected. Discounts (automatic or manual) deleted as
part of incompatibility processing are not returned as manual discounts.
No
QP: Selling Price Rounding Option

QP: Set Request Name

Values
Yes: The value of the Request Name field in the Pricing Engine Request window will be prefixed with the
Order ID.
No: Only the Request ID is stored in Request ID field of the Pricing Engine Request window.
The profile option QP: Set Request Name can be used in conjunction with the QP: Debug profile option so that
the Request Name field will be prefixed with the Order ID. The QP: Set Request Name profile option is visible
and can be updated at the site, application, responsibility, and user levels.
The default value should only be changed if the source of the pricing data is any application other than
Oracle Pricing . Set this to the source system lookup code of the application interfacing the pricing
information. Used on all setup user interfaces to identify the application through which the pricing
information is being entered, The Source System Code is held on all Price and Modifier Lists to identify the
origin of the data at the time of pricing, the pricing engine may restrict its search to pricing information
which originated form a particular application depending on the Request type to Source System Setup.
QP: System Source Code
QP: Unit Price Precision Type
(v. )
This profile option is Required and the default value is QP: Oracle Pricing
Used to determine the value for the rounding factor which is defaulted on the Price List. The rounding factor
is limited by the number of positions allowed in the standard or extended precision format of the price list
currency.
This is a required profile and the default value is standard. The options are:
Standard-Rounding Factor is defaulted to the currencies standard precision
Extended-Rounding Factor is defaulted to the currencies extended precision.
This Profile option is required and the default value is Standard.
Individual:=Round(listp
rice) + round(adj)
Null
QP: Oracle Pricing
Extended
Order Management
January 11, 2006
Profile Option Name
Description
Value Resp Level
QP: Valueset Lookup Filler
Default value: Yes

Use this profile option to enable or disable a search criteria window for qualifier value lookups in qualifiers,
price lists, and modifiers. Some qualifiers use large valuesets, for example, those based on all customers, and
searches may take a long
time. If you want to reduce the number of items that display in the list of values, you can enter search
criteria. If you do not enter search criteria and click the list of values indicator for the fields Value From or
Value To, you see a window which
advises that you have not entered search criteria and that the search may take a long time.
Values
Yes: The message displays.
No: The message does not display. Use this value is you do not expect to have large qualifier valuesets and
do not need to enter search criteria to reduce the display.
This profile option is visible and can be updated at the site, application, responsibility, and user levels.
Yes
QP: Verify GSA
.Indicates whether the pricing calculation engine should test for GSA violations. The Evaluation is performed
if a request is for a non-GSA customer, and GSA Rules are violated if the selling price of am item is calculates
to be less than the price on any GSA price List.
This profile option is optional and the default value is No
This profile is used for tuning purposes. If you never define a Blind Discounts set this profile to No. This
will bypass part of the Search Engine processing. A blind Discount is defined as a Modifier that has:
No List Qualifier on the Modifier List Header and
No Line Qualifier and
No Products or Pricing Attributes
This profile option is required and the default value is Yes
Note: If your business needs to define a Modifier as described above, make sure that this profile option is set
to Yes otherwise these modifiers will not be selected by the Search Engine.
Default value: QP: Oracle Pricing
This profile option enforces the unit of measure (UOM) conversion for price lists when the Primary UOM box in
a price list is selected. For example, suppose that in a price list, the UOM selected is EA (each) and that the
Primary UOM box is selected. (The primary uom in the price list could be different from the primary uom set
in Oracle Inventory for the item.)
If an order line is entered with the unit of measure as Dozen, the pricing engine would convert the order
quantity to EA and provide a price in EA This occurs only if no eligible price lists are found with Dozen as the
unit of measure. To do the
conversion, Advanced Pricing uses the inve ntory UOM conversion APIs. As for time periods, the inventory
uom conversion holds a static conversion factor of 30 days per month. Since days are set as the base UOM,
one year is converted to 12.16666 months by the inventory uom APIs. This result is obtained by dividing
365 days by 30days rather than one year being converted to 12 months.
Values
Standard: When set to Standard, the existing method of passing the uom quantity to the pricing engine API
can be used by the calling applications.
Oracle Contracts: When set to Oracle Contracts, the pricing engine use the APIs provided by Oracle
Contracts to convert the date and time. To use the "Oracle Contracts" API to do the uom conversion,
following values from each request
line processed need to be passed by the calling applications (such as Order Management, Order Capture or
Oracle Contracts) to the pricing engine:
Period Start/End Dates
Ordered UOM (Time uom in which the price needs to be fetched)
Ordered quantity
No
QP: Blind Discount Option
QP: Time UOM Conversion
(v. )
Yes
Null
Order Management
January 11, 2006
Initial Tasks Setup/OM: Define Descriptive Flexfields (DFFs)

Order Management>Setup>Financials>Flexfields>Descriptive>Segments
Process:
Business Area:
Date:
Control Number:
Priority(H, M, L):
Process Owner:
Descriptive Flexfields (DFFs)
Order Management
H
Description: Use this form to define Descriptive Flexfields (DFFs) for Order Management, Shipping Execution, and Advanced Pricing.
Additional Line Detail Information (Oracle Order Management)
This descriptive flexfield displays any additional line detail information at the time of order entry.
Industry Attribute (Oracle Order Management)
This descriptive flexfield records industry-specific information for items in your order.
Pricing Attributes (Oracle Order Mgt. and Oracle Adv. Pricing)
Pricing attributes modify an items price without requiring that you create a new item. For example, you sell computer software and the price of the software is different
depending on the number of users. You define a pricing attribute called Number Of Users. When you enter an order line, the Pricing Attributes flexfield opens a window to
capture the number of users. Order Management uses this information along with the item and unit of measure to derive the item list price.
The Pricing Attributes descriptive flexfield contains 15 user-definable flexfield segments to be used as pricing attributes. Once defined, the attributes can be used in the
lines block of the Sales Orders window, the Line Options window, the Shipment Schedules window, the lines block of the Price Lists window, and the Item Groups window
in Order Management; and in the Services and Renew Service windows in Oracle Service.
Application
Title
Context Field
Prompt
Context Field Values

Reference Field
Code
Comments
Name
Desc.
Enab
led
VALUE SET
NAME:
SEE BELOW
DFF Summary
(v. )

Application
Order Management
January 11, 2006
Title
(v. )
Order Management
January 11, 2006
DFF Segments Summary & Segments (Detail)

OPERATING UNIT
DFF
Number
Segmen
ts
Summa
ry
Numbe
r
Open:
Name / Window
Prompt
Column
Value Set
Displayed
Enabled
Require
d
Value Set
Default Type
Default Value
Display
Size
Desc
Size
Conc.
Desc
Size
ORDER
HEADER
1 US
ORDER
LINE
2-US
Address
Info
4-US Only
(v. )
Order Management
January 11, 2006
Value Sets
Value Set Name
List Type
Format
Type
(v. )
Max Size
Precision
Numbers
Only
Uppe
rcase
Only
Righ
t
Justi
fy
Validation
Type
Edit
Table Appl.
Table Name
Value
Meaning
ID
Where
Order Management
January 11, 2006
OM: Enable Parameters

OM>Setup>Parameters
Form
Name
Organizations
Process:
Business Area:
Order Management
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
Process Owner:
Description: Use this form to set the Order Management Application to the Operating Unit and the Item Validation Organization.
United States Operating Unit
Operating Unit
Item Validation Organization
Customer Relationships
Audit Trail
Margin Calc
US
OU OU
- US
IO - ITEM MASTER ORG
Related Customers
Enabled
when Order
is Booked
Cost Enabled
(v. )
Order Management
January 11, 2006
OM: Define QuickCodes

Setup>QuickCodes>Order Management
Form
Name
Oracle Order Management Lookups
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use these forms to define Lookups for Order Management Lists.
To be maintained on going
For CRP-1 Seeded data is accepted

QuickCode Type
User Name
Application
Access Level
Description
CANCEL_CODE
Cancel/Audi
t Codes
Oracle Order Management
Extensible
Cancel/Audit Codes
Code
Meaning
Description
Allow
(v. )
Tag
Start date
End Date
Enabled
YY
Order Management
January 11, 2006
OM: Define Order Import Sources

Setup>Orders>Import Sources Seeded.
Form
Name
Order Import Sources
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define sources for importing orders into Order Management.
Attention: This is a Plus` process if additional Order Import
Sources are needed. See Oracle Applications Core/ Plus
functionality
Import Source Name
Description
AHL
Order Source for Advanced Service on Line
Automotive
Service
CRM Apps
Order source is any of the CRM applications
Contract Renewal
Order created to renew contracts
Copy
Copy
EDI
EDI
Field Service Report
Field Service report for charging parts, labour and expenses from the field
IBU
Order source for iSupport
IStore Account
Order source for iStore account user
IStore Oneclick
Order created by iStore one click
IStore Walkin
Order source for iStore walk in customer
Internal
Web
Online
For Orders created Online
Order Capture Quotes
Order source for Order Capture quoting module
POL
Partners Relationship Management
Sales and Marketing Collateral
Sales and Marketing Collateral
Sales and Marketing Quote
Sales and Marketing Quote
Service
Service
(v. )
Enabled Y/N
Y

Import Source Name
Order Management
January 11, 2006
Description
Enabled Y/N
Service Billing
Service Billing
Service Request
Service Request
TeleSales Order
Order Source for TeleSales
Telesales Collateral
Order source for telesales
Web
Web
XML
Order Source for XML Messages
(v. )
Order Management
January 11, 2006
OM: Define Processing Constraints

Setup>Rules>Security>Processing Constraints
Form
Name
Processing Constraints
Process:
Business Area:
Order Management
Control Number:
Date:
<Business Area>
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define processing constraints to prevent users from adding, updating, deleting, splitting lines, and
canceling order or return information beyond certain points in your order cycle.
Attention: Oracle supplies many seeded Processing Constraints. Supplemental Processing
Constraints are considered a Plus feature, see Oracle Applications Core/ Plus Functionality for details
<Processing Constraints> For CRP-1 accept all seeded Processing Constraints

Application:
Entity: Order Line
Constraints
Operation
Attribute
User Action
System Changes
User Changes
Seeded?
Group #
Scope
Validation Entity
Update
Request Date
Not Allowed
Y
Conditions
101
Any
Order Line
Record Set
Not
Validation Template
Seeded?
User Message
Applicable To
All Responsibilities
Authorized Responsibilities
ORDER MANAGEMENT Resp (Various)
Constrained
Responsibilities
Line
No
Booked
No
You can not update Request Date - Please Contact
Customer Service
(v. )
Order Management
January 11, 2006
OM: Define Pricing

Pricing>Price Lists>Price List Setup
Note: Build Attribute Mapping Program needs to be run after Price Lists created
Form
Name
Price List
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define price lists
Header: Internal Price List requires only Header Level information

Name
Description
Internal Intercompany Price List
Internal Intercompany Price List
Currency
Round To
USD
-5
tab
Effective Date
(from)
Effective Date
(to)
Payment Terms
Freight Terms
Freight Carriers
Comments
List Lines
Product Context
Product Attribute
(v. )
Product Value
UOM
Primary UOM
Value
Order Management
January 11, 2006
Header
Name
Description
Standard Price List

Corporate Price List
Standard Price List

Corporate Prie List
Additional Price lists will be added as needed

Currency
Round To
USD
-5
tab
Effective Date
(from)
Effective Date
(to)
Payment Terms
Freight Terms
Freight Carriers
Comments
List Lines
Product Context
Product Attribute
Product Value
UOM
Primary UOM
Value
Item to be added later
(v. )
Order Management
January 11, 2006
OM: Define Defaulting Rules

Setup>Rules>Defaulting>Defaulting Rules
Form
Name
Attribute Defaulting Rules
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to 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 Order window.
Attention: Oracle Order management supplies seeded Defaulting Rule, changes or additions to the
Defaulting Rules is considered a Plus feature. See Oracle Applications Core/ Plus Functionality for
details.
For CRP-1 Accept Seeded data
Defaulting Condition Validation Templates

Validation Templates
Application
Entity
Condition
Name
Validation Rules
Condition
Description
Group #
Attribute
Validation
Operation
Value String
Attribute Defaulting Rules

Defaulting Conditions
Application
Entity
(v. )
Attribute
Condition Precedence
Defaulting Sourcing Rules

Defaulting
Condition
Rule Sequence
Source
Type
Default Source
/Value
Order Management
January 11, 2006
OM: Define Modifiers (Discounts)

Pricing>Modifiers
Form
Name
Define Modifier
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:

Attention: Before you define discounts, enable your Pricing
Attributes descriptive flexfields in the Enable Parameters window.
For CRP-1 no modifiers are setup
Header - MANUAL DISCOUNTS

tab
Main
Type
Number
Active
Name
Version
Automatic
Value From
Value To
Currency
Start Date
End Date
Description
List Qualifiers (main tab)

Group
tab
Grouping
Number
Qualifier
Attribute
Precedence
Start Date
End Date
Modifiers
Modifier Number
tab
Qualifier
Context
Level
Modifiers Type
Start date
Print On Invoice
Automatic
Override
Modifiers (continued)
(v. )

Pricing Phase
tab
Order Management
January 11, 2006
Incompatibility Phase
Bucket
Proration Type
GL Value
Product
Attribute
Product
Attribute Value
Discounts
Modifier
Number
Level
Mod. Type
(v. )
Charge Name
Includ
e on
Retur
ns
Formula
Application Method
Value
Accrue
Order Management
January 11, 2006
OM: Define Transaction Types

Setup>Transaction Types>Define
Form
Name
Transaction Types
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define transaction types to classify orders and returns. For each order type, you can assign a default
price list, payment terms, freight terms, etc.
Attention: There are three steps for Transaction Types.
1. Create a Transaction Type for each Order Type. (Standard, International, Bill Only, etc.)
2. Create a Transaction Type for each Line Type. (Regular, Ship Only, RMA with Receipt, RMA credit
only, etc.)
3. For each Order Transaction Type created, assign the Line Types (and their linked Line
Workflows) through the Assign Line Flows button.
Transaction Types
Transaction Type
Description
UNITED STATES
Standard
Internal
Quote
RMA - Credit
Drop Shipment
Mixed
Return, Receipt
Standard (Line Invoicing)
Return (Receipt & Approval)
ATO Model
Configured
Drop Shipment Line
Return-Credit Only, No Receipt
Return Line, Receipt-Approval
Standard Order
Internal
Quote
RMA - Credit
Drop Shipment
Mixed
Return with Receipt
Standard
Return for Credit with Receipt
and Approval
ATO Model
Configured
Drop Shipment Line
Return Line with Receipt,
Approval
Effective
Date Start
Warehouse
Transaction
Type Code
Order Category
Order
Order
Order
Order
Order
Mixed
Return
Line
Line
Order
Order
Order
Return
Order
Order
Order
Order
Return
Line
Line
Line
Line
Line
Order
Order
Order
Order
Order
Order Workflow
Order Line Level Transaction Types

(v. )
Order Management
January 11, 2006
Header Transaction Types - US

Transaction Type
Description
Order
Category
Trans Type Code
Standard
Order
LINE
Main
Order
Workflow
Shipping
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Dates
WarehoCNe
Finance
IO - REDMOND BLDG1 MFG
Rule
Shipping Method
Shipment Priority
Standard Priority
Freight Terms
Prepay & Add
FOB
Customer Site
Invoicing Rule
Advance Invoice
Accounting Rule
Immediate
Source
Invoice Source
Ship Source Type

Pricing
Credit Method For
Scheduling Level
Allow all scheduling actions
Terex One Sales

Enforce Price
List Y/N
Auto Schedule Y/N

Credit Check Rule
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Price List
Comment
Invoices With
Rules
Prorate
Split Term
Invoices
Prorate
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Checking
Tax Event
Currency
Conversion Type
Transaction Type
Description
Order
Category
Trans Type Code
Return (Receipt & Approval)
Standard
Return
LINE
Main
Document
Agreement
Type
Order
Workflow
Shipping
WarehoCNe
Shipping Method
(v. )
Dates
Comment
Finance
Rule
Invoicing Rule
Advance Invoice

Transaction Type
Order Management
January 11, 2006
Description
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Order
Category
Trans Type Code
Shipment Priority
Standard Priority
Freight Terms
Prepay & Add
FOB
Customer Site
Dates
Accounting Rule
Invoice Source
Immediate
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Credit Method For
Price List
Scheduling Level
Enforce Price
List Y/N
Auto Schedule Y/N

Credit Check Rule
Comment
Source
Ship Source Type

Pricing
Order
Workflow
No Reservations
Invoices With
Rules
Prorate
Split Term
Invoices
Prorate
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Checking
Tax Event
Currency
Conversion Type
Transaction Type
ATO Model
Description
Order
Category
Trans Type Code
ATO Model
Order
LINE
Main
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Order
Workflow
Shipping
WarehoCNe
Shipment Priority
Standard Priority
Freight Terms
Prepay & Add
FOB
Customer Site
Comment
Finance
Shipping Method
(v. )
Dates
Rule
Invoicing Rule
Advance Invoice
Accounting Rule
Immediate
Source
Invoice Source
ORDER MANAGEMENT

Transaction Type
Order Management
January 11, 2006
Description
Purchase Order
Required Y/N
Order
Category
Trans Type Code
Dates
Ship Source Type

Pricing
Order
Workflow
Non-Delivery
Invoice Source
Demand Class
Credit Method For
Price List
Scheduling Level
Enforce Price
List Y/N
Auto Schedule Y/N

Credit Check Rule
Comment
Invoices With
Rules
Prorate
Split Term
Invoices
Prorate
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Checking
Tax Event
Currency
Conversion Type
Transaction Type
Configured
Description
Order
Category
Trans Type Code
Configured
Order
LINE
Main
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
WarehoCNe
Standard Priority
Freight Terms
Prepay & Add
FOB
Customer Site
Ship Source Type
Enforce Price
List Y/N
Auto Schedule Y/N
(v. )
Rule
Invoicing Rule
Advance Invoice
Accounting Rule
Immediate
Source
Invoice Source
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Scheduling Level
Comment
Finance
Shipment Priority
Price List
Order
Workflow
Shipping
Shipping Method
Pricing
Dates
Credit Method For

Invoices With
Rules
Prorate
Split Term
Invoices
Prorate

Transaction Type
Order Management
January 11, 2006
Description
Credit Check Rule
Order
Category
Trans Type Code
Dates
Order
Workflow
Comment
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Checking
Tax Event
Currency
Conversion Type
Transaction Type
Description
Order
Category
Trans Type Code
Drop Shipment Line
Drop Shipment
Order
LINE
Main
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Shipment Priority
Standard Priority
Freight Terms
Prepay & Add
FOB
Customer Site
Scheduling Level
Enforce Price
List Y/N
Auto Schedule Y/N
Ordering
Rule
Invoicing Rule
Advance Invoice
Accounting Rule
Immediate
Source
Invoice Source
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Price List
Comment
Finance
Ship Source Type
Credit Check Rule
Order
Workflow
Shipping
WarehoCNe
Shipping Method
Pricing
Dates
Credit Method For

Invoices With
Rules
Prorate
Split Term
Invoices
Prorate
Inspection Required
Y/N
Receivables
Transaction Type
Cost of Goods
Sold Account
Checking
Tax Event
(v. )

Transaction Type
Order Management
January 11, 2006
Description
Order
Category
Trans Type Code
Dates
Order
Workflow
Comment
Currency
Conversion Type
Transaction Type
Description
Order
Category
Trans Type Code
Return-Credit Only
Return
LINE
Main
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Shipment Priority
Standard Priority
Freight Terms
Prepay & Add
FOB
Customer Site
Scheduling Level
Enforce Price
List Y/N
Auto Schedule Y/N
Ordering
Rule
Invoicing Rule
Advance Invoice
Accounting Rule
Immediate
Source
Invoice Source
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Price List
Comment
Finance
Ship Source Type
Credit Check Rule
Order
Workflow
Shipping
WarehoCNe
Shipping Method
Pricing
Dates
Credit Method For

No Reservations
Invoices With
Rules
Prorate
Split Term
Invoices
Prorate
Inspection Required
Y/N
Receivables
Transaction Type
Cost of Goods
Sold Account
Checking
Tax Event
Currency
Conversion Type
(v. )
Order Management
January 11, 2006
Transaction Type
Description
Order
Category
Trans Type Code
Return Line with Receipt,

Approval
Return
LINE
Main
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
WarehoCNe
Shipment Priority
Standard Priority
Freight Terms
Prepay & Add
FOB
Customer Site
Rule
Invoicing Rule
Advance Invoice
Accounting Rule
Immediate
Source
Invoice Source
Scheduling Level
Enforce Price
List Y/N
Auto Schedule Y/N
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Price List
Comment
Finance
Ship Source Type
Credit Check Rule
Order
Workflow
Shipping
Shipping Method
Pricing
Dates
Credit Method For

No Reservations
Invoices With
Rules
Prorate
Split Term
Invoices
Prorate
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Checking
Tax Event
Currency
Conversion Type
Order Header Level Transaction Types

Header Transaction Types - US
(v. )

Transaction Type
Standard
Order Management
January 11, 2006
Description
Order
Category
Trans Type Code
Standard
Order
ORDER
Main
WarehoCNe
Shipment Priority
Standard Priority
Freight Terms
Prepay & Add
FOB
Customer Site
Rule
Invoicing Rule
Advance Invoice
Accounting Rule
Immediate
Source
Invoice Source
Ship Source Type
Credit Method For
Scheduling Level
Enforce Price
List Y/N
Auto Schedule Y/N

Credit Check Rule
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Terex One Sales
Comment
Order Flow Check box Retain

Generic
Document Number
Finance
Shipping Method
Pricing
Price List
Order
Workflow
Shipping
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Dates
Invoices With
Rules
Prorate
Split Term
Invoices
Prorate
Receivables
Transaction Type
Cost of Goods
Sold Account
Invoice
Inspection Required
Y/N
Ordering
Checking
US10.03018.510000000.000000.00
0000.0000.00000.00000
Assign Line Flows

Line Type
Item Type
Process Name
Start Date
Configured Item
Line Flow Configuration eneric

Line Flow - Generic
Drop Shipment Line
Line Flow - Generic
29-NOV2005
29-NOV2005
29-NOV2005
End Date
Transaction Type
Description
Order
Category
Trans Type Code
Dates
Order
Workflow
Comment
Internal
Internal
Order
ORDER
17-Mar-2004 to
05-OCT-2004
Order Flow Generic
Check box Retain

Document Number
(v. )

Transaction Type
Order Management
January 11, 2006
Description
Order
Category
Main
Order
Workflow
Rule
Shipping Method
DHL-Air-2nd Day Air
Invoicing Rule
Advanced Invoice
Shipment Priority
Standard Priority
Accounting Rule
Immediate
Freight Terms
Source
FOB
Customer Site
Invoice Source
Ship Source Type
Enforce Price
List Y/N
Credit Check Rule
Ordering
Credit Check - US
Picking/Purchas
e Release
Credit Check - US
Non-Delivery
Invoice Source
Demand Class
Internal PL 2005
Comment
Finance
WarehoCNe
Pricing
Price List
Dates
Shipping
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Trans Type Code
Credit Method For
Scheduling Level
Invoices With
Rules
Auto Schedule Y/N
Split Term
Invoices
Inspection Required
Y/N
Receivables
Transaction Type
Cost of Goods
Sold Account
INTERNAL INVOICE
US10.03018.510000000.000000.00
0000.0000.00000.00000
Tax Event
Currency
Conversion Type
Assign Line Flows

Line Type
Item Type
Process Name
Start Date
Configured Item
ATO Model
Line Flow Configuration

Line Flow - ATO Model
21-NOV2005
21-NOV2005
21-NOV2005
Line Flow - Generic
(v. )
End Date
Order Management
January 11, 2006
Transaction Type
Description
Order
Category
Trans Type Code
Quote
Quote
Order
ORDER
Main
Rule
Shipping Method
Invoicing Rule
Advanced Invoice
Shipment Priority
Accounting Rule
Immediate
Freight Terms
Source
FOB
Invoice Source
Ship Source Type
Non-Delivery
Invoice Source
Demand Class
Terex One Sales
Enforce Price
List Y/N
Credit Check Rule
Comment
Order Flow Check box Retain

Generic
Document Number
Finance
WarehoCNe
Pricing
Price List
Order
Workflow
Shipping
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Dates
Credit Method For
Scheduling Level
Invoices With
Rules
Auto Schedule Y/N
Split Term
Invoices
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Picking/Purchas
e Release
Invoice
Tax Event
Currency
Conversion Type
Assign Line Flows

Line Type
Item Type
(v. )
Process Name
Start Date
Line Flow - Generic
21-NOV2005
End Date
Order Management
January 11, 2006
Transaction Type
Description
Order
Category
Trans Type Code
RMA - Credit
RMA - Credit
Order
ORDER
Main
Rule
Shipping Method
Invoicing Rule
Advanced Invoice
Shipment Priority
Accounting Rule
Immediate
Freight Terms
Source
FOB
Invoice Source
Ship Source Type
Non-Delivery
Invoice Source
Demand Class
Terex One Sales
Enforce Price
List Y/N
Credit Check Rule
Comment
Order Flow
Check box Retain
Generic
Document Number
Finance
WarehoCNe
Pricing
Price List
Order
Workflow
Shipping
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Dates
Credit Method For
Scheduling Level
Invoices With
Rules
Auto Schedule Y/N
Split Term
Invoices
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Picking/Purchas
e Release
Invoice
US10.03018.510000000.000000.00
0000.0000.00000.00000
Tax Event
Currency
Conversion Type
Assign Line Flows

Line Type
Item Type
(v. )
Process Name
Start Date
Line Flow - Return for

Credit Only
19-NOV2005
End Date
Order Management
January 11, 2006
Transaction Type
Description
Order
Category
Trans Type Code
Drop Shipment
Drop Shipment
Order
ORDER
Main
Drop Shipment Line
Rule
Shipping Method
DHL-Air-Worldwide Express
Invoicing Rule
Advanced Invoice
Shipment Priority
Standard Priority
Accounting Rule
Immediate
Freight Terms
Prepay & Add
FOB
Customer Site
Source
Invoice Source
Ship Source Type
Credit Method For
Scheduling Level
Enforce Price
List Y/N
Auto Schedule Y/N

Credit Check Rule
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Terex One Sales
Comment
Order Flow
Check box Retain
Generic
Document Number
Finance
WarehoCNe
Pricing
Price List
Order
Workflow
Shipping
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Dates
Invoices With
Rules
Split Term
Invoices
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Picking/Purchas
e Release
INVOICE
US10.03018.510000000.000000.00
0000.0000.00000.00000
Tax Event
Currency
Conversion Type
Assign Line Flows

Line Type
Item Type
(v. )
Process Name
Start Date
Line Flow - Generic
10-JAN2006
End Date
Order Management
January 11, 2006
Transaction Type
Description
Order
Category
Trans Type Code
Mixed
Mixed
Mixed
ORDER
Main
Comment
Order Flow
Check box Retain
Generic
Document Number
Finance
WarehoCNe
Rule
Shipping Method
Invoicing Rule
Advanced Invoice
Shipment Priority
Standard Priority
Accounting Rule
Immediate
Freight Terms
Prepay & Add
FOB
Customer Site
Source
Invoice Source
Ship Source Type

Pricing
Price List
Order
Workflow
Shipping
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Dates
Non-Delivery
Invoice Source
Demand Class
Terex One Sales
Credit Method For
Scheduling Level
Enforce Price
List Y/N
No Reservations
Invoices With
Rules
Split Term
Invoices
Auto Schedule Y/N

Credit Check Rule
ORDER MANAGEMENT
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Picking/Purchas
e Release
INVOICE
US10.03018.510000000.000000.00
0000.0000.00000.00000
Tax Event
Currency
Conversion Type
Assign Line Flows

Line Type
Item Type

Configured Item

(v. )
Process Name
Start Date
Line Flow - Generic
10-JAN2006
29-NOV2005
29-NOV2005
29-NOV2005
Line Flow Configuration

Credit Only
Credit with Receipt
End Date
Order Management
January 11, 2006
Transaction Type
Description
Order
Category
Trans Type Code
Return, Receipt
Return with Receipt
Return
ORDER
Main
Rule
Shipping Method
Invoicing Rule
Advanced Invoice
Shipment Priority
Standard Priority
Accounting Rule
Immediate
Freight Terms
Prepaid
FOB
Customer Site
Source
Invoice Source
Ship Source Type
Credit Method For
Scheduling Level
Enforce Price
List Y/N
No Reservations
Invoices With
Rules
Split Term
Invoices
Auto Schedule Y/N

Credit Check Rule
ORDER MANAGEMENT
Non-Delivery
Invoice Source
Demand Class
Terex One Sales
Comment
Order Flow
Check box Retain
Generic
Document Number
Finance
WarehoCNe
Pricing
Price List
Order
Workflow
Shipping
Document
Agreement
Type
Default Order
Line Type
Default Return
Line Type
Sales Document
Type
Agreement
Required Y/N
Purchase Order
Required Y/N
Dates
Inspection Required
Y/N
Ordering
Receivables
Transaction Type
Cost of Goods
Sold Account
Picking/Purchas
e Release
INVOICE
US10.03018.510000000.000000.00
0000.0000.00000.00000
Tax Event
Currency
Conversion Type
Assign Line Flows

Line Type
Item Type
(v. )
Process Name
Start Date

Credit with Receipt
13-DEC2005
End Date
(v. )
Order Management
January 11, 2006
Order Management
January 11, 2006
<Seeded Workflows for Transaction Types Table>

Header Workflows
Name
Description
Order Flow - Generic

Order Flow - Generic with Header
level Invoicing
Order Flow - Return with
Approval
This has Booking and Close Order sub-processes in it. This can be used both by Orders and returns.
This has Booking, Header Level Invoicing and Close Order sub-processes in it.
This has Booking, a notification and Close Order sub-processes in it.
Line Workflows
Name
Description
Line Flow - ATO Item
This flow supports ATO item Lines only. It has Enter Line (wait for Booking), Scheduling, Creation of Work
Orders/Flow Schedules, Ship Line, Fulfill Line, Invoice Interface line and Close Line sub-processes in it.
This flow supports ATO Model Lines only. It has Enter Line (wait for Booking), Scheduling, Creation of
Configuration Item, Fulfill line, Invoice Interface Line, and Close Line sub-processes in it.
This flow is only for Configuration Item Lines that are automatically created when ATO configurations are
processed. It has sub-processes to create the BOM/Routings, Work Orders, Flow Schedules. It additionally
has Ship Line, Fulfill Line and Close Line sub-processes.
This flow is identical to the Line Flow - Configuration except that it also has an additional authorization
process before Shipping. This is for RLN users
This is an outbound flow that will handle all item types except the CONFIGURED Item. It has Enter Line
(wait for Booking), Scheduling, Create Supply, Ship line, Fulfill Line, Invoice Interface Line and Close Line
sub-processes in it.
This is identical to the Line Flow - Generic except that it also has an additional authorization process
before Shipping. This is for RLM users.
A version of the Line Flow - Generic that works with the seeded Header Flow to support Header Level
Invoice Interface.
This only has Enter Line (wait for Booking), Invoice Interface Line and Close Line sub-processes in it.
A version of the Line Flow - Generic without Invoicing. This can be used for Internal Orders.
Line Flow - ATO Model

Line Flow - Configuration
Line Flow - Configuration with
Authorize to Ship
Line Flow - Generic
Line Flow - Generic with
Authorize to Ship
Line Flow - Generic with Header
Level Invoicing
Line Flow- Generic, Bill Only
Line Flow - Generic, Ship
Only
Line Flow - Standard Service
Line Flow - Return for Credit
Only
Line Flow - Return for Credit only
with Approval
Line Flow - Return for Credit
(v. )
This has Enter Line (wait for Booking), Fulfill Line, Invoice Interface line and Close Line sub-processes in it.
This can be used for Service Lines.
This has Enter Line (wait for Booking), Invoice Interface Line and Close Line sub-processes in it.
This is identical to the Line Flow - Return for Credit Only with a Wait for a Header Approval after Enter
Line.
This has Enter Line (wait for Booking), RMA Receiving, Fulfill Line, Invoice Interface line and Close Line
with Receipt
Line Flow - Return for Credit with
Receipt and Approval
(v. )
Order Management
January 11, 2006
sub-processes in it.
This is identical to the Line Flow - Return for Credit with Receipt with Wait for Header Approval after
Enter Line.
Order Management
January 11, 2006
OM: Order AOL Document Sequences (Order Numbering)

Setup>Documents>Define
Form
Name
Document Sequences
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define AOL Document Sequences for automatic numbering of orders.
Attention: For Fast Forward implementations EDI is considered a P1US feature. See BR.030
Business Requirements Mapping (Core/PlUS) Functionality document for Fast Forward projects.
Name
Application
From
DE Orders
Oracle Order
Management
Oracle Order
Management
Oracle Order
Management
Oracle Order
Management
Oracle Order
Management
Order
UK Orders
UK Order Gapless
RETURNS
(v. )
To
Type
Message
Initial Value
15-Nov-2005
Automatic
15-Nov-2005
Automatic
1000000
15-Nov-2005
Automatic
15-Nov-2005
Automatic
30-Jun-2004
Automatic
Order Management
January 11, 2006
OM: Order Assign Document Sequences

Setup>Documents>Assign (additional assignments will be required for Order Types)
Form
Name
tab
Sequence Assignments
Documents To be documented as Order Transaction types have been defined
Application
Category
Set of Books
Method
Standard
TEREX US SET OF BOOKS
Standard-Quote
Internal
Internal-Quote
Quote
Quote-Quote
RMA - Credit
RMA - Credit-Quote
Drop Shipment
Drop Shipment-Quote
Mixed
Mixed-Quote
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Return, Receipt
Return, Receipt-Quote
Automatic
Automatic
ADDITIONAL DHM ORDER

TYPES WILL BE ADDED
AS NEEDED FOR Orders

TYPES WILL BE ADDED AS
NEEDED FOR Orders
ADDITIONAL DHM ORDER TYPES

WILL BE ADDED AS NEEDED FOR
Orders
tab
Assignment
Application
Category
Start Date
Standard
<current date>
ORDERS
Standard-Quote
<current date>
ORDERS
Internal
<current date>
ORDERS
Internal-Quote
<current date>
ORDERS
Quote
<current date>
ORDERS
Quote-Quote
<current date>
ORDERS
(v. )
End Date
Sequence

Application
Order Management
January 11, 2006
Category
Start Date
RMA - Credit
<current date>
ORDERS
RMA - Credit-Quote
<current date>
ORDERS
Drop Shipment
<current date>
ORDERS
Mixed
<current date>
ORDERS
Mixed-Quote
<current date>
ORDERS
Return, Receipt
<current date>
ORDERS
Return, Receipt-Quote
<current date>

NEEDED FOR Orders
ADDITIONAL DHM
ORDER TYPES WILL
BE ADDED AS
NEEDED FOR Orders
(v. )
End Date
Sequence
ORDERS
NEEDED FOR Orders

NEEDED FOR Orders
Order Management
January 11, 2006
OM: Define Credit Checking

Setup>Rules>Credit
Form
Name
Credit Check Rules
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
January 12, 2006
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define your credit checking rules.

tab
Options
Rule Name
OCM Default Credit

Check Rule
Effective Dates
Credit Check Level

Check Item Categories
Sales Order
No
Credit Hold Level

Send Hold Notification
tab
Sales Order
No
Conversion Type
Override Manual Release
Corporate
Exposure
Rule Name
OCM Default Credit Check Rule
Maximum Days Past Due
Effective Dates
Use Pre-Calculated Exposure
No
Include Uninvoiced Orders Y/N
Yes
Include External Credit Exposure
No
Include Freight and Special Charges
Yes
Include Open Receivables Balance
Yes
Include Tax
Yes
Include Payments at Risk Y/N
Yes
Include Orders Currently On Hold Y/N
Yes
Open Receivables Days
90
Scheduled Shipping Horizon Date
365
365
(v. )
Order Management
January 11, 2006
OM: Define Holds

Setup>Orders>Holds
Form
Name
Holds
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
January 12, 2006
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define automatic holds to apply to orders and returns.
Below are the sample of Seed Holds. For CRP-1no additional holds are defined
Name
3A7 Change Notification Hold
Autocreate Config Exception
Booking Hold
Description
Type
Line level hold - Waiting for a

response on 3A7
This hold is automatically
placed when BOM created by
Autocreate Config needs user
verification
Hold to Prevent Booking of
Orders
Change Notification Hold for

3A7
Exception Hold
Order Administration Hold
Workflow
Item
Workflow Activity
OM Order
Header
Book Order
Effective Dates
Authorizations
Responsibility
Authorized Action
Effective Date From
Effective Date To
Additional Resp TBD
(v. )
Order Management
January 11, 2006
OM: Define Attachment Document Categories

Setup>Orders>Attachments>Document Categories
Form
Name
Document Categories
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
January 12, 2006
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define Document Categories for use with Attachments.
<Document Categories>
Ref #
Category
Default Data Type
CN
Printed
Documents
Effective Dates:
From
Effective
Dates:
To
Assignements
<Category Assignments>
(Document Category)
Category
Type
Name
Printed Documents
Form
Blanket Sales Agreements
Form
Quick Sales Orders
Form
Sales Orders
Format
For Future the document category setups needs to be re-valuated
(v. )
Order Management
January 11, 2006
OM: Define Attachments

Setup>Orders>Attachments>Documents
Form
Name
Attachments (will be added after conversions)
Process:
Business Area:
Order Management
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
Process Owner:
Description: Use this form to define standard documents to attach automatically to orders and returns.
Attention: Before you define documents you must define at least
one document category to use attachments in Order Management.
<Documents> Documents will be defined & set up after go live!

Category
Description (Comment Name)
Source: Data Type
Source: File
Usage
Security: Type
Security: Owner
Effective Dates: From
Effective Dates: To
Magnification
(Comment Text)
(v. )
Order Management
January 11, 2006
Addition Rules
Entity
Rules: Group Number
Attribute
Attribute Value
<Documents>
Category
Source: Data Type
Source: File
Usage
Security: Type
Security: Owner
Effective Dates: To
Magnification
(Comment Text)
Addition Rules
Entity
Rules: Group Number
(v. )
Attribute
Attribute Value
<Documents>
Order Management
January 11, 2006
Category
Source: Data Type
Source: File
Usage
Security: Type
Security: Owner
Effective Dates: To
Magnification
(Comment Text)
(v. )
Order Management
January 11, 2006
Addition Rules
Entity
Rules: Group Number
(v. )
Attribute
Attribute Value
Order Management
January 11, 2006
OM: Define Freight Carriers

Shipping>Setup>Freight Carriers, Cost Types>Freight Carriers
Form
Name
Freight Carriers - Additional Freight Carriers to be added during PROD Setups
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description:. A freight carrier is a commercial company used for internal transfers between organizations, as well as shipments to and
from customers and suppliers. You must associate a general ledger account with each carrier to collect costs associated with using this
carrier. Assign a carrier to each inter-organization transaction.
Additional Freight Carriers will be added as needed.

Carrier Name
Short Name
SCAC
Code
Currency
Active
DHL
DHL
Redmond - TRUCK
RED-TRK
USD
YES
Southaven Truck
STH-TRK
USD
YES
Enable
Manifesting
YES
Carrier
Service
Mode
Ship Method
Org
DHL
Worldwide
Express
2nd Day Air
AIR
US Operating Orgs
AIR
DHL-Air-2nd Day Air
US Operating Orgs
Redmond TRUCK
Southaven
Truck
Ground
LTL
RED-TRK-LTL-Ground
US Operating Orgs
Ground
LTL
STH-TRK-LTL-Ground
US Operating Orgs
(v. )
Comments Address Info/Contacts/Telephones
Order Management
January 11, 2006
OM: Define Freight Cost Types

Setup>Shipping>Freight>Freight Cost Types
Form
Name
Freight Cost Types
Process:
Business Area:
Order Fullfillment
Date:
Order Management Setup
Control Number:
Priority(H, M, L):
Process Owner:

Description: Use this form to define freight charges and freight carriers to specify on orders.
Freight Cost
Freight Cost Type
Charge Currency
Freight Cost US
Freight Cost US
USD
Handling Charge US
Handling Charge US
USD
Packaging Charge US
Packaging Charge US
USD
(v. )
Freight Charge Amount
Effective
Dates
Map to
Charges
Order Management
January 11, 2006
OM: Define Shipping Documents

Shipping>Setup>Documents>Document Sets
Form
Name
Document Sets
Process:
Business Area:
Order Management
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
Process Owner:
Description: Use this form to group shipping documents and other reports in the Confirm Shipment window or the Release Sales Orders
For Picking window, depending on the option you select in the usage field. When you select a document set in either the Release Sales
Orders For Picking or Confirm Shipment windows, the documents print automatically when you save your actions.
<Shipping Document Sets>

Document Set
(All Pick Release Documents)
Seed Data only
(v. )
Order Management
January 11, 2006
Description
Usage
Effective Dates: To
Printing Method
Documents:
Seq
Application
Report Name
Description
<Shipping Document Sets>

Document Set
Description
CNage
(v. )

Order Management
January 11, 2006
<Current Date>
Effective Dates: To
Printing Method
Documents:
Seq
Application
(v. )
Report Name
Description
Order Management
January 11, 2006
OM: Define Release Sequence Rules

Shipping>Setup> Picking>Define Release Sequence Rules
Form
Name
Release Sequence Rules
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define valid Pick Release Sequencing Rules to be able to give critical customer orders a higher priority in
the warehouse pick release schedules
<Release Sequence Rules>

Rule
Default: Order Number
Rule
Description
This is the default Pick Sequence Rule for Shipping

Execution
Description
31-MAY-2002
Effective Dates: To
Release Priority
Order
Effective Dates: To
Priority
1
Ascending
Y
Outstanding Invoice
Value
Release Priority
Priority
Ascending
Descending
Order
Outstanding Invoice
Value
Schedule Date
Departure Date
Shipment Priority
Descending
(v. )
Schedule Date
Departure Date
Shipment Priority
Order Management
January 11, 2006
OM: Define Release Rules

Shipping>Setup>Picking>Define Release Rules Form
Form
Name
Release Rules
Process:
Business Area:
Order Management
Control Number:
Date:
<Business Area>
Priority(H, M, L):
Process Owner:
<Control Number>
Description: Use this form to define shipping release rules. The Release Rules window defines and saves picking criteria that can be
used when running Pick Release. Once you have created a release rule, you can select the rule from the Based On Rule list on the
Release Sales Orders For Picking window to automatically populate the fields on the window with the predefined picking criteria.
<Release Rules> (Distribution)

Rule
Effective: From
Effective: To
Release Criteria
Order: Order Type
Order: Orders
Order: Order Number
Order: Ship Set
Order: Customer
Order: Ship To
Order: Item
Order: Prior Reservations
Only
Order: Schedule Ship Dates:
From
(v. )
Order Management
January 11, 2006
Rule
Order: Schedule Ship Dates:
To
Order: Requested Dates: From
Order: Requested Dates: To
Shipping: Carrier
Shipping: Shipment Priority
Shipping: Ship From

Shipping: Release Sequence
Rule
Shipping: Include Assigned
Lines
Document Set
Shipping: Autocreate
Deliveries
Inventory: Warehouse
Inventory: Pick Slip Grouping
Rule
Inventory: Project
Inventory: Task
Inventory: Auto Detail
Inventory: Auto Pick Confirm
Inventory: Pick From:
Subinventory
Inventory: Pick From: Locator
Inventory: Default Stage:
(v. )
Order Management
January 11, 2006
Rule
Subinventory
Inventory: Default Stage:
Locator
(v. )
Order Management
January 11, 2006
OM: Define Pick Slip Grouping Rules

Shipping>Setup>Picking>Define Pick Slip Grouping Rules
Form
Name
Pick Slip Grouping Rules
Process:
Business Area:
Order Management
Control Number:
Date:
<Business Area>
Priority(H, M, L):
Process Owner:
<Control Number>
Description: Use this form to define grouping rules to determine how released picking lines are grouped onto pick slips. Grouping rules
allow you to
specify the criteria by which released picking lines are grouped. Select from the following criteria: order number, carrier, subinventory,
shipment priority, customer, departure, ship to, and delivery. If you select Order Number, for example, all picking lines with the same
order number are grouped on the same pick slip. If you pick Carrier and Customer, all picking lines with the same freight carrier and
customer are grouped on a pick slip.
<Pick Slip Grouping Rules>

Rule Name
Description
Effective Dates: To
Group By: Order
Number
Group By:
Subinventory
Group By: Customer
Group By: Ship To
Group By: Carrier
Group By: Trip Stop
(v. )
Order Management
January 11, 2006
Rule Name
Group By: Delivery
Group By: Shipment
Priority
(v. )
Order Management
January 11, 2006
OM: Define Shipping Parameters

Shipping>Setup>Shipping Parameters
Form
Name
Shipping Parameters Need to setup for all shipping Organizations.
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
Process Owner:
<Control Number>
Description: Use this form to define the default parameters used throughout a specific warehouse (organization).
<Shipping Parameters> V01

Parameter
Value
WEIGHT
Weight UOM Class
VOLUME
Volume UOM Class
WEIGHT
Percent Fill Basis

Secondary Export Country
Screening
C Not required
N
<Shipping Parameters> (Pick Release)

Parameter
Value
Release Sequence Rule

Pick Slip Grouping Rule

At the End
Print Pick Slip

Default Pick Release Document Set
Autocreate Delivery Criteria
All Pick Release Documents

Within Order
Parameter
Value
Default Stage Subinventory
Stage
Default Stage Locator

Number of Pick Slip Lines
Auto Detail
Autocreate Deliveries
Yes
Yes
<Shipping Parameters> (Shipping Transaction RD1)
(v. )

Parameter
Order Management
January 11, 2006
Value
Default Delivery Document Set

Weight / Volume Calculation
Enforce Packing in Containers
Ship Confirm Documents

Manual
No
Yes
Auto Pack Option
Parameter
Value
Goods Dispatched Account
US10.03018.537010000.000000.0
00000.US10.00000.00000
Freight Class Category Set

Commodity Code Category Set
Yes
Enforce Ship Method

Defer Interface
Container Inventory Control
Allow Future Ship Date
<Shipping Parameters> (Delivery Grouping)

Parameter
Value
Yes
Ship From Location
Yes
Customer
No
Freight Terms
Parameter
Value
Yes
Ship To Location
Intermediate Ship To Location
Ship Method
No
Yes
No
FOB Code
For CRP-1 all other Inventory Org shipping parameter is base on RD1
(v. )
Order Management
January 11, 2006
OM: Define Transportation Calendars

Shipping>Setup>Calendars>Assign
Form
Name
Assign Calendars
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to assign a transportation (workday) calendar to define valid shipping days and hours for a shipper,
receiver, and carrier. You can define both shipping and receiving calendars to designate when your customers, customers sites,
supplier, suppliers sites, and internal organizations can ship and/or receive.
Attention: Before you begin assignments you must create the workday calendars. This is done in BOM. However, Shipping
will want to have input on this as they may require special calendars.
<Assign Calendars>
Trading Partner
Supplier
Customer
Organization
Carrier
Trading Partner Name
Carrier: Used For

(Type)
Carrier: Used For (Name)
Calendar Usage
Default Calendar Code
Show Candidates
Site Calendars
Site
Calendar Code
(v. )
Enabled
(v. )
Order Management
January 11, 2006
Order Management
January 11, 2006
OM: Define Shipping Exceptions

Shipping>Setup>Define Exceptions
Form
Name
Define Shipping Exceptions -
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define the relationship between container items and load items to specify which items can be contained
with other items.
Exception Name
Description
Exception Type
Severity (high, med,

low)
Seeded Data
Exception Handling
Manual
Workflow
Workflow Item Type
Workflow Process
No Action Required
Initiate Workflow Y/N
Will update all exceptions to Low Severity Level
(v. )
Order Management
January 11, 2006
OM: Define Shipping Document Categories

Shipping>Setup>Documents>Document Categories
Form
Name
Document Categories
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to set up a Document Category for each of the shipping reports - Bill of Lading and Packing Slip.
Category Name
Description
Document
Category Includes
Ship Methods
Locations
Sequence
Prefix
Suffix
Category Name
Description
Document
Category Includes
Ship Methods
Locations
Sequence
Prefix
Suffix
DHM
US
DHM
CN
(v. )
Delimiter
Default
Appearanc
e
Delimiter
Default
Appearanc
e
Order Management
January 11, 2006
OM: Shipping Document Sequences

Shipping>Setup>Documents>Document Sequences
Form
Name
Document Sequences
Process:
Business Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to define AOL Document Sequences for automatic numbering of shipping documents.
Name
Application
(v. )
From
To
Type
Message
Initial Value
Order Management
January 11, 2006
OM: Assign Shipping Report Document Sequences

Shipping>Setup>Documents>Assign Sequences
Form
Name
Sequence Assignments
tab
Documents
Name
tab
Category
Set of Books
Method
Assignment
Application
Category
Start Date
End Date
Sequence
Oracle Shipping
Oracle Shipping
Oracle Shipping
Oracle Shipping
(v. )
Order Management
January 11, 2006
OM: Shipping Execution Grants

Shipping>Setup>Grants and Role Definitions>Grants
Form
Name
Shipping Execution Grants PROD

Process:
Additional Users will be added as they are created in
Busness Area:
Order Management
Date:
<Business Area>
Control Number:
Priority(H, M, L):
<Control Number>
Process Owner:
Description: Use this form to grant access to each userid that will be performing shipping transactions. Roles may be defined to limit
users to edit or view transactions related to Trips, Stops, Deliveries, and Lines/LPNs.
CNer
Role
Users added as
needed.
Upgrade
(v. )
Org
Start Date
End Date
<Current Date>
Order Management
January 11, 2006
Order Management
January 11, 2006
Open and Closed Issues for this Deliverable

Open Issues
ID
Issue
Resolution
Responsibility
Target Date
Impact Date
Resolution
Responsibility
Target Date
Impact Date
Closed Issues
ID
Issue
(v. )

Br100 SCM - Om

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Br100 SCM - Om

Uploaded by

Copyright:

Available Formats

AIM

BR.100 APPLICATION SETUP

January 11, 2006

January 11, 2006

BR.100 Application Setup

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

OM: Define Release Sequence Rules.......................................................64

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

Initial Tasks Setup/SA: Define Responsibilities

Priority (H, M, L):

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

HR: Business Group

HR: Security Profile

MO: Operating Unit

Currency:Mixed Currency Precision

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

Application Set Up Control Sheet - Order Management

OM: Define Profile Options

File Ref: 81761613.doc

Type (definition, execution, or

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

OM: Define Transaction Types

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

OM: Assign Shipping Report

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

OM: Define System Level Profile Options

Value Resp Level

Address & Contact

OM: Activate Change Management

OM: Administer Public Queries.

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup

Value Resp Level

Also to set BOM: Automatic Reservation to Yes

OM: Charges for Backorders

To include Freight Charges for Backorder

OM: Charges for included item

OM: Charging Privilege

OM: Commitment Sequencing

OM: Configuration Quick Save

OM: Context Responsibility

OM: Credit Check Engine API Code

File Ref: 81761613.doc

Application Set Up Control Sheet - Order Management

BR.100 Application Setup