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 ManagementJanuary 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 Library Master Project Library2 Project Manager3

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


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

File Ref: 81761613.doc (v. 1 )



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.........................................................................................79Closed Issues.......................................................................................79

File Ref: 81761613.doc (v. 1 )



Initial Tasks Setup/SA: Define Responsibilities

System Administration>Security>Responsibilities>DefineProcess:

ResponsibilitiesBusiness Area:

System AdminDate:

Control Number: Priority (H, M, L): H

Process Owner: Terex Corporation

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 UserOM User

Responsibility Name Application Resp Key Data Group Application Menu Req Group Name

Application

Menu Exclusions

Order Management Super User

Oracle Order Management

Order Management Super User

Standard Oracle Order Management

ONT_SUPER_USER



File Ref: 81761613.doc (v. )



System Administration>Profile>System

Profile SiteOrder Management Super User, DHM US

Order Management Super User, DHM CN

HR: Business Group Setup Business Group

HR: Security Profile Setup Business Group

HR: User Type HR User HR User

MO: Operating Unit

GL: Set Of Books

Default Country United States United States United States

Currency:Mixed Currency Precision 2

Sequential Numbering Not Used Partially Used Partially Used

File Ref: 81761613.doc (v. )




Environment Name: Machine: Type (definition, execution, or both):

WorkflowSubWorkflow Name

Setup Task Responsibility Due Date QA Responsibility QA Due Date Signature Approval

OM: Define Profile OptionsJ Patel

OM: Define Item Validation System Parameter and Operating Unit

J Patel

OM: Define InvoicingJ Patel

OM: Define SalespersonsJ Patel

OM: Define Tax FeaturesJ Patel

OM: Define QuickcodesJ Patel

OM: Define Freight Charges and Freight Carriers

J Patel

OM: Define Order Processing Workflow

J Patel

OM: Define AOL Document Sequences (Order Numbering)

J Patel

OM: Define Order Import SourcesJ Patel

OM: Define Processing ConstraintsJ Patel

OM: Define PricingJ Patel

OM: Define Customer AgreementN/A

OM: Define Defaulting RulesJ Patel

File Ref: 81761613.doc (v. )





OM: Define Transaction TypesJ Patel

OM: Assign Workflows to Transaction Types

J Patel

OM: Define DiscountsJ Patel

OM: Define Credit Checking RulesJ Patel

OM: Define Automatic HoldsJ Patel

OM: Define AttachmentsJ Patel

OM: Define Freight CarriersJ Patel

OM: Define Freight Carrier - Ship Method Relationships

J Patel

OM: Define Shipping Document SetsJ Patel

OM: Define Release Sequence RulesJ Patel

OM: Define Release RulesJ Patel

OM: Define Pick Slip Grouping RulesJ Patel

OM: Define Container-Load Relationships

N/A

OM: Define Shipping ParametersJ Patel

OM: Define Freight Cost TypesJ Patel

OM: Define Transportation CalendarsN/A

OM: Define Shipping ExceptionsN/A

OM: Define Shipping Document Categories

J Patel

OM: Define Shipping SequencesJ Patel

File Ref: 81761613.doc (v. )





OM: Assign Shipping Report Document Sequences

J Patel

OM: Assign Shipping Execution Grants

J Patel

File Ref: 81761613.doc (v. )



OM: Define System Level Profile Options

Application Administrator>Profile OptionsFormName Profile Options Process:

Order ManagementBusiness Area:

<Business Area>Date:

January 12, 2006Control Number:

<Control Number>Priority(H, M, L):

<Priority (H, M, L)>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 ManagementResponsibility = 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.

No

OM: Activate Change Management System

Default is Yes – not updateable Yes

OM: Add Customer Controls the level of access to the Add Customer form, which is available with OM Family Pack F onwards. Address & Contact

OM: Add Customer (Order Import) 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.

No

OM: Administer Public Queries. This profile option determines which responsibility is able to create and update public queries This profile option is required.

No

OM: Apply Automatic Attachments This profile option determines whether rule-based attachments are applied without user intervention. This profile is optional

Yes

OM Available to Overide ATP Allows user to override the ATP date. Yes – At Resp Level

OM: Auto Push Group Date 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

Yes

OM: AutoSchedule This profile option determines the default setting of the use of autoschedulingYes- Order lines are scheduled automatically at the time of entry.No-Order lines are not scheduled automatically at the time of entry.

Yes

File Ref: 81761613.doc (v. )




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.

No

OM: Charging Privilege 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 chargesUnlimited Access You can modify and apply all charges including the non-overridable charges

Unlimited Access – By Responsibility

OM: Commitment Sequencing This profile option determines whether or not Oracle Order Management calculatesand stores the amount of the line that can be paid using the commitment, and ifcommitments will be applied in Oracle Receivables in the same sequence that theyare applied in Order Management. Select from:❩❡ Yes: Order Management populates the commitment applied and then willinterface the commitment amount applied to Oracle Receivables.❩❡ No: Order Management does not calculate the exact commitment appliedamount for an order line. Instead, the extended amount of the line is shown inthe commitment applied field within the Sales Order Line, Pricing Tab window.Note: If you set this profile option to Yes, and you have notinstalled Bills Receivables for Oracle Receivables, OrderManagement will not capture the applied commitment amount andtherefore will not relay commitment applied amounts to OracleReceivables; no Warning or Error message is displayed.

Yes

OM: Configuration Quick Save This profile option determines how Order Management will save option or model class lines for unbooked sales orders from within the Sales Order window only. If you set this profile option to Y, class lines will be saved by a direct database insert call with a minimum of order line defaulting values, unless the value of the Order Management profile option OM: Included Item Freeze Method is set to Entry. If the value of OM: Included Item Freeze Method is set to Entry, you cannot perform direct database inserts of model or class order lines with a minimum of defaulting.Configuration.

No

OM: Context Responsibility 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.)

N/A

OM: Copy Model dff to child lines Yes

OM: Credit Card Privileges 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.

N/A

OM: Credit Check Engine API Code Flow

Set to MULTI will switch the code to the new Multi currency API in Verify_paymentI Multi

OM: Credit Memo Transaction Type This profile option value is transferred to Receivables if no value is defined for the credit memo transaction type This profile option is required

Credit Memo

OM: Credit Salesperson for Freight This profile option specifies whether to credit the Salesperson on the invoicing lineor order header for freight charges when the freight charges are treated as revenue.

No

File Ref: 81761613.doc (v. )




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

No

OM: Customer Relationships 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 option’s setting. This profile option is optional and the default setting is Yes.

Yes

OM: DBI Installation No

OM: Deactivate Pricing at Scheduling

This profile option should not be set unless directed by an Oracle Representative. Null

OM: Debug Level This profile option is used to store debug messages to assist in problem identification. The OM: Debug profile option controls which debug messages get written to the debug log based on their assigned level. The directory to be specifiedfor 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

0

OM: Debug Log Directory This profile option determines the default directory used to store log file outputs when performing Order Management debugging.

/usr/tmp/obws1(Instance Name)

OM: Discounting Privilege 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.

Unlimited-to be set at the resp Level

OM: E-Mail Required on New Customers

See NOTE <Note:152669.1> ONT_MANDATE_CUSTOMER_EMAILThis 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.

No

OM: Employee for Self-Service Orders

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.

N/A

OM: Estimated Authorization This profile option determines the estimated number of days a credit card authorization is assumed to be 21 – requires iPayment

File Ref: 81761613.doc (v. )


http://metalink.oracle.com/metalink/plsql/showdoc?db=Not&id=152669.1

http://metalink.oracle.com/metalink/plsql/showdoc?db=Not&id=152669.1



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.

No – GSA not used

OM: Generic Update Constraints Apply to DFF

This profile option determineswhether you can update processing-constrained descriptive flexfield attributes onclosed orders. There is a seeded processing constraint against updating closed orderOrder Management Profile Optionslines; this profile option does not control order line fields other than the flexfieldattributes.❩❡ If you select Yes' (the default), you cannot update processing-constrainedflexfield attributes on closed orders.❩❡ If profile is set to 'No', you can update processing-constrained flexfieldattributes on closed orders.❩❡ This profile option is updateable at the site level.Regardless of this profile option, you can set up constraints specific to flexfieldattribute constraints.

Yes

OM: Import Multiple Shipments No reference in OM Implementation Guide. Left as Blank – No LOV’s Blank

OM: Included Item Freeze Method This profile option determines the point in the order’s status at which the included items from a configuration’s bill of material are added as lines on the order. This profile option is Required and the default value is Booking.

Booking

OM: Invoice Numbering Method 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

Automatic

OM: Invoice Source 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.

Invoice

OM: Invoice Transaction Type 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.

Invoice

OM: Item Change Honors Frozen Price

This profile option determines whether Order Management will change the value ofcalculate 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 theorder line gets repriced.❩❡ No: Order management will set the calculate price flag to Y, and the order linewill be repriced.

No

OM: Item Flexfield 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.

System Items

OM: Item View Method This profile option determines the display method of data retrieved within the LOVfor 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.

Null

OM Negative Pricing This profile option controls whether Order Management allows a negative list priceor negative selling price to be determined by the Pricing Engine or to be entered asan 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

File Ref: 81761613.doc (v. )




negative unit price can be entered on a price listNote: Returns

OM: Non-Delivery Invoice Source 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.

Null

OM: Notification Approver This profile option is used during upgrading Order Entry Order Cycle History toOrder Management Workflow History. Setting this profile option enables you tosend workflow Notifications (Approval or FYI notifications) to the Role that theoption is set to for the following Oracle Order Management seeded Workflow types:NOTE: Does Not Apply to Bradford

N/A – Upgrades only

OM: Order Infromation Regulatory logging

This profile option is used to determine if you enable logging OPM Regulatoryhistory dispatching within the Order Information portal. Select from:❩❡ Yes: Enable logging OPM Regulatory history dispatching within the OrderInformation portal. Document and user details are stored within the dispatchhistories using an API. MSDS document will be displayed to a user only if asuccessful log for the request is created.❩❡ No: Do not enable the logging of OPM Regulatory history dispatching withinthe Order Information portal.The default for this profile is No.

No

OM: Orders Purge Per Commit This profile option determines how many order the purge process should purge before performing a commit. This profile option is defaulted at 100

100

OM: Over Return Tolerance This profile option indicates the percentage by which a return line can be over received. Any value greater than or equal to zero (0) is a valid value. This profile option is set at the site level. This profile option is required and the default value is zero (0)

0

OM: Over Shipment Tolerance This profile option indicates the percentage by which an order line can be over-shipped. Any value greater than or equal to zero (0) is a valid value. This profile option is set at the site level. This profile option is required and default value is zero (0)

0

OM: Over Shipment Invoice Basis 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

Invoiced Shipped Qty

OM: Party Totals Currency This profile option determines the currency used by the Calculate Party Totals currentprogram which sums order totals by Party. Order Management recommends thatyou set this profile option at the Site level only.

US dollar

OM: Payment method for Credit Card Transactions

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.

Null

OM: Populations of Buyer code for Dropship Lines

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_interfacetable is populated with the buyer details (the employee_id of the person whoenters the sales order). Your sales people must be defined as a buyers in OraclePurchasing.❩❡ 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 willbe unable to select the value Buyer for the input parameter Groupprior to submission of the Oracle Purchasing Requisition Importconcurrent program.

Null

OM: Process Payment Immediately at Booking

This profile option is used by the credit card authorization process as a default forthe primary payment method if a specific customer does not have a primarypayment method defined.

No – Need iPayment

OM: Promotion Limit Violation This system level profile option determines the hold action Order Management will Null

File Ref: 81761613.doc (v. )




take when encountering a initial promotional hold returned by the pricing engine. Ifthe 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 courseof action for the order or line. Messages are generated and can be viewed within theProcess Messages Window.Select from:❩❡ Place holds where violated (either Line or Order): If the pricing engine returnsan initial promotional hold, place a hold for the corresponding order or orderline.❩❡ No holds applied: If the pricing engine returns an initial promotional hold, donot apply a hold for either an order or order line. Allow the order or order lineto continue processing within its’ associated workflow.❩❡ Place order on hold when any violation occurs (both Line and Order): If thepricing 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 forpromotional hold.This profile option is optional, and the default is Null.

OM: Reservation Time Fence 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.

7

OM: Return Item Mismatch Action 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 messageWarning- Line processing is continued with a Warning.Allow- Line processing continues with no warning or error.

Warning

OM: Return Unfulfilled Referenced Line Action

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.

Null

OM: Risk Factor Threshold for Electronic Payments

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.

50

OM: Run Order Import for XML 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

Null

OM: Sales Order Form: Cascade Header Changes to Line

All resp should be set at ASK ME

OM: Sales Order Form: Restrict Customers

The value of this profile option determines if all customers are displayed within the Customer field on the Sales Order Header, Main Tab or only customers who have addresses in the organization the order is defined for. This profile is applicable only for the Sales Order Header Main Tab. Customers are visible across all operating units; Customer Addresses are Organization specific. The default for this profile option is Global.

Global Organization

File Ref: 81761613.doc (v. )




Note: Changed from Global to Current

OM: Schedule Line on Hold 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

Yes

OM: Set Receivalbes Transaction Date fro Non-Shippable Lines

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.

Yes

OM: Show Discount Details on Invoice

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

Yes

OM: Show Line Details 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

No

OM: Source Code This profile option identifies the source code that Order Management passes to Oracle Inventory during scheduling. The source code should be defined as the third segment of the Sales Order Flexfield to guarantee that each transaction is unique. This profile option is required and there is not default.

Order Entry

OM: Source Code2-1-1 Obsolete Order Entry

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

0

OM: Under Shipment Tolerance 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)

0

OM: Use Configurator This profile option indicates which Oracle application software is launched to enter configuration information when selecting the Configurator button from the Sales Order window. Valid values are:❩❡ 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.

Yes

OM: View Cancel Lines This profile option controls the default value of the Cancel check box when sorting sales order lines within the Sales Order Lines Tab, Sort window. The default value is Yes. Select from:❩❡ 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.

Yes

OM: View Closed Line 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.

Yes

OM: Under Shipment Tolerance 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)

0

File Ref: 81761613.doc (v. )




QP: Accrual UOM Class Default value: NullThis 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.

Null

QP: Administer Public Queries Default value: NullQuery 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.

Null

QP: Allow Duplicate Modifiers Future functionality Yes

QP: Cascade Asked for Promotion Advance Pricing functionality No

QP: Cross Order Volume Period1 Default value: BlankThis 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 VolumePeriod 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.

Null

QP: Cross Order Valume Period2 Default value: BlankThis 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 VolumePeriod 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.

Null

QP: Cross Order Valume Period3 Default value: BlankThis 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.

Null

QP: Custom Sourced Default Value: NoValue❩❡ 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.

No

QP: Debug Default value: Request Viewer OffValue❩❡ 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.

Request Viewer Off

File Ref: 81761613.doc (v. )




❩❡ 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 debuglog 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 option—other users’ transactions are not affected.

QP: Get custom Price Customized Default value: NoIndicates 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 function’s 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.

No

QP: Insert Formula Step Values into Temp Table

Default value: NoThis 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.

No

QP: Inventory Decimal Precision Future Use. 10

QP: Item Validation Organization 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

OU Item Validation Org

QP: Limit Exceed Action Default value: Hard - Adjust Benefit AmountThis 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.

Hard-Adjust Benefit Amount

QP: Line Volume UOM Code 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 it’s primary UOM and then uses the Volume attribute of the Item to derive the Line

Null

File Ref: 81761613.doc (v. )




Volume UOM specified in this profile option

QP: Line Weight UOM Required if your business needs to define Qualifiers Rules which include the seeded Qualifier Line WeightSpecifies the unit of measure of the Line Weight Qualifier. The attribute sourcing API converts the item on the request line into it’s primary UOM and then uses the Weight attribute of the Item to derive the Line Weight UOM specified in this profile optionThis profile option is optional and there is no default value.

Null

QP: Multi Currency Installed Default value: NoIf 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.

YES

QP: Negative Pricing 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 pricingNo- Do not allow Negative Pricing

Yes

QP: Price Rounding Default value: BlankThis 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 anddisplays 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.

Null

QP: Pricing Transaction Entity Order Fulfillment

QP: Promotional Limits Installed Default value: NoThis 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

File Ref: 81761613.doc (v. )




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 ChargesManual 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 Individual:=Round(listprice) + round(adj)

QP: Set Request Name Default value: BlankValues❩❡ 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.

Null

QP: System Source Code 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 it’s search to pricing information which originated form a particular application depending on the Request type to Source System Setup.

This profile option is Required and the default value is QP: Oracle Pricing

QP: Oracle Pricing

QP: Unit Price Precision Type 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.

Extended

File Ref: 81761613.doc (v. )




QP: Valueset Lookup Filler Default value: YesUse 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 longtime. 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 whichadvises 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

No

QP: Blind Discount Option 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 AttributesThis profile option is required and the default value is YesNote: 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.

Yes

QP: Time UOM Conversion Default value: QP: Oracle PricingThis 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 theconversion, 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 requestline 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

Null

File Ref: 81761613.doc (v. )



Initial Tasks Setup/OM: Define Descriptive Flexfields (DFFs)

Order Management>Setup>Financials>Flexfields>Descriptive>SegmentsProcess:

Descriptive Flexfields (DFFs)Business Area:

Order ManagementDate:

Control Number: Priority(H, M, L): H

Process Owner:

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 item’s 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 Reference Field

Context Field Values

Code Name Desc. Enabled

Comments VALUE SET NAME:

SEE BELOW

DFF Summary

File Ref: 81761613.doc (v. )



Application Title

File Ref: 81761613.doc (v. )



DFF Segments Summary & Segments (Detail)

OPERATING UNIT

DFF Number

Segments Summary Number

Name / Window Prompt

Column Value Set Displayed Enabled

Open:

Required

Value Set Default Type Default Value Display Size

Desc Size

Conc. Desc Size

ORDER HEADER1 – US

ORDER LINE2-US

Address Info4-US Only

File Ref: 81761613.doc (v. )



Value Sets

Value Set Name List Type Format Type

Max Size Precision Numbers Only

Uppercase Only

Right Justify

Validation Type

Edit

Table Appl. Table Name Value Meaning ID Where…

File Ref: 81761613.doc (v. )



OM: Enable Parameters

OM>Setup>Parameters

FormName OrganizationsProcess:



Control Number: <Control Number>

Priority(H, M, L): <Priority (H, M, L)>

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

File Ref: 81761613.doc (v. )



OM: Define QuickCodes

Setup>QuickCodes>Order Management

FormName Oracle Order Management LookupsProcess:





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/Audit Codes

Oracle Order Management Extensible Cancel/Audit Codes

Code Meaning Description Tag Start date End Date Enabled

Allow YY

File Ref: 81761613.doc (v. )



OM: Define Order Import Sources

Setup>Orders>Import Sources – Seeded.

FormName Order Import SourcesProcess:





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 Enabled Y/N

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 Y

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 Y

File Ref: 81761613.doc (v. )



Import Source Name Description Enabled Y/N

Service Billing Service Billing Y

Service Request Service Request Y

TeleSales Order Order Source for TeleSales

Telesales Collateral Order source for telesales

Web Web

XML Order Source for XML Messages

File Ref: 81761613.doc (v. )



OM: Define Processing Constraints

Setup>Rules>Security>Processing Constraints

FormName Processing Constraints Process:





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: Oracle Order Management Entity: Order Line

Constraints

Operation UpdateAttribute Request DateUser Action Not AllowedSystem ChangesUser ChangesSeeded? Y

Conditions Applicable ToGroup # 101 All ResponsibilitiesScope Any Authorized Responsibilities ORDER MANAGEMENT Resp (Various)Validation Entity Order Line Constrained

ResponsibilitiesRecord Set LineNot NoValidation Template BookedSeeded? NoUser Message You can not update Request Date - Please Contact

Customer Service

File Ref: 81761613.doc (v. )



OM: Define Pricing

Pricing>Price Lists>Price List SetupNote: Build Attribute Mapping Program needs to be run after Price Lists created

FormName Price ListProcess:





Process Owner:

Description: Use this form to define price lists

Header: Internal Price List requires only Header Level informationName Description

Internal Intercompany Price List Internal Intercompany Price List

Currency Round To Effective Date (from)

Effective Date (to)

Payment Terms Freight Terms Freight Carriers Comments

USD -5

tab List LinesProduct Context Product Attribute Product Value UOM Primary UOM Value

File Ref: 81761613.doc (v. )



HeaderName Description

Standard Price ListCorporate Price List

Additional Price lists will be added as needed

Standard Price ListCorporate Prie List

Currency Round To Effective Date (from)

Effective Date (to)

Payment Terms Freight Terms Freight Carriers Comments

USD -5

tab List LinesProduct Context Product Attribute Product Value UOM Primary UOM Value

Item to be added later

File Ref: 81761613.doc (v. )



OM: Define Defaulting Rules

Setup>Rules>Defaulting>Defaulting Rules

FormName Attribute Defaulting RulesProcess:





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 TemplatesValidation Templates Validation Rules

Application Entity Condition Name

Condition Description

Group # Attribute Validation Operation

Value String

Attribute Defaulting RulesDefaulting Conditions Defaulting Sourcing Rules

Application Entity Attribute Condition Precedence Defaulting Condition

Rule Sequence Source Type

Default Source /Value

File Ref: 81761613.doc (v. )



OM: Define Modifiers (Discounts)

Pricing>Modifiers

FormName Define ModifierProcess:





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 DISCOUNTStab Main

Type Number Active Name Version Automatic Currency Start Date End Date

Description

List Qualifiers (main tab) Group Grouping

NumberQualifier Context

Qualifier Attribute

Precedence Value From Value To Start Date End Date

tab ModifiersModifier Number Level Modifiers Type Start date Print On Invoice Automatic Override

tab Modifiers (continued)

File Ref: 81761613.doc (v. )



Pricing Phase Incompatibility Phase Bucket Proration Type GL Value Product Attribute

Product Attribute Value

tab DiscountsModifier Number

Level Mod. Type Charge Name Include on Returns

Formula Application Method Value Accrue

File Ref: 81761613.doc (v. )



OM: Define Transaction Types

Setup>Transaction Types>Define

FormName Transaction Types Process:





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 Effective Date Start

Warehouse Transaction Type Code

Order Category Order Workflow

UNITED STATESStandardInternalQuoteRMA - CreditDrop ShipmentMixedReturn, ReceiptStandard (Line Invoicing)Return (Receipt & Approval)

ATO ModelConfiguredDrop Shipment LineReturn-Credit Only, No ReceiptReturn Line, Receipt-Approval

Standard OrderInternalQuoteRMA - CreditDrop ShipmentMixedReturn with ReceiptStandardReturn for Credit with Receipt and ApprovalATO ModelConfiguredDrop Shipment LineReturn-Credit Only, No ReceiptReturn Line with Receipt, Approval

OrderOrderOrderOrderOrderMixedReturnLineLine

LineLineLineLineLine

OrderOrderOrderReturnOrderOrderOrderOrderReturn

OrderOrderOrderOrderOrder

Order Line Level Transaction Types

File Ref: 81761613.doc (v. )



Header Transaction Types - US

Transaction Type Description Order Category

Trans Type Code Dates Order Workflow

Comment

Standard (Line Invoicing) Standard Order LINE

Main Shipping Finance

Document WarehoCNe IO - REDMOND BLDG1 MFG Rule

Agreement Type

Shipping Method Invoicing Rule Advance Invoice

Default Order Line Type

Standard (Line Invoicing) Shipment Priority Standard Priority Accounting Rule Immediate

Default Return Line Type

Freight Terms Prepay & Add Source

Sales Document TypeAgreement Required Y/N

FOB Customer Site Invoice Source ORDER MANAGEMENT

Purchase Order Required Y/N

Ship Source Type Non-Delivery Invoice Source

Pricing Demand Class Credit Method For

Price ListTerex One Sales

Scheduling Level Allow all scheduling actions Invoices With Rules

Prorate

Enforce Price List Y/N

Auto Schedule Y/N Split Term Invoices

Prorate

Credit Check Rule Inspection Required Y/N

Ordering Receivables Transaction Type

Checking Cost of Goods Sold Account

Tax Event

Currency

Conversion Type



Comment

Return (Receipt & Approval) Standard Return LINE



Agreement Type


File Ref: 81761613.doc (v. )





Comment


Shipment Priority Standard Priority Accounting Rule Immediate








Price List Scheduling Level No Reservations Invoices With Rules

Prorate



Prorate




Tax Event

Currency

Conversion Type



Comment

ATO Model ATO Model Order LINE



Agreement Type








File Ref: 81761613.doc (v. )





Comment




Price List Scheduling Level Allow all scheduling actions Invoices With Rules

Prorate



Prorate




Tax Event

Currency

Conversion Type



Comment

Configured Configured Order LINE



Agreement Type












Prorate



Prorate

File Ref: 81761613.doc (v. )





Comment




Tax Event

Currency

Conversion Type



Comment

Drop Shipment Line Drop Shipment Order LINE



Agreement Type












Prorate



Prorate




Tax Event

File Ref: 81761613.doc (v. )





Comment

Currency

Conversion Type



Comment

Return-Credit Only, No Receipt Return-Credit Only Return LINE



Agreement Type












Prorate



Prorate




Tax Event

Currency

Conversion Type

File Ref: 81761613.doc (v. )





Comment

Return Line, Receipt-Approval Return Line with Receipt, Approval

Return LINE



Agreement Type












Prorate



Prorate




Tax Event

Currency

Conversion Type

Order Header Level Transaction TypesHeader Transaction Types - US

File Ref: 81761613.doc (v. )





Comment

Standard Standard Order ORDER Order Flow - Generic

Check box Retain Document Number



Agreement Type












Scheduling Level Allow all scheduling actions Invoices With Rules

Prorate



Prorate



Invoice


US10.03018.510000000.000000.000000.0000.00000.00000

Assign Line FlowsLine Type Item Type Process Name Start Date End Date

Standard (Line Invoicing) Configured Item Line Flow - Configuration eneric

29-NOV-2005

Standard (Line Invoicing) Line Flow - Generic 29-NOV-2005

Drop Shipment Line Line Flow - Generic 29-NOV-2005



Comment

Internal Internal Order ORDER 17-Mar-2004 to05-OCT-2004

Order Flow - Generic


File Ref: 81761613.doc (v. )





Comment


Document WarehoCNe Rule

Agreement Type

Shipping Method DHL-Air-2nd Day Air Invoicing Rule Advanced Invoice




Freight Terms Source


FOB Customer Site Invoice Source




Price ListInternal PL 2005

Scheduling Level Invoices With Rules




Ordering Credit Check - US Receivables Transaction Type

INTERNAL INVOICE

Picking/Purchase Release

Credit Check - US Cost of Goods Sold Account

Tax Event

Currency

Conversion Type

US10.03018.510000000.000000.000000.0000.00000.00000


Standard (Line Invoicing) Configured Item Line Flow - Configuration

21-NOV-2005

Standard (Line Invoicing) ATO Model Line Flow - ATO Model 21-NOV-2005


File Ref: 81761613.doc (v. )





Comment

Quote Quote Order ORDER Order Flow - Generic




Agreement Type

Shipping Method Invoicing Rule Advanced Invoice


Standard (Line Invoicing) Shipment Priority Accounting Rule Immediate


Freight Terms Source


FOB Invoice Source




Price List Terex One Sales Scheduling Level Invoices With Rules





Invoice


Cost of Goods Sold Account

Tax Event

Currency

Conversion Type



File Ref: 81761613.doc (v. )





Comment

RMA - Credit RMA - Credit Order ORDER Order Flow – Generic




Agreement Type

Shipping Method Invoicing Rule Advanced Invoice


Shipment Priority Accounting Rule Immediate


Return-Credit Only, No Receipt Freight Terms Source


FOB Invoice Source





Scheduling Level Invoices With Rules





Invoice



Tax Event

Currency

Conversion Type

US10.03018.510000000.000000.000000.0000.00000.00000


Return-Credit Only, No Receipt Line Flow - Return for Credit Only

19-NOV-2005

File Ref: 81761613.doc (v. )





Comment

Drop Shipment Drop Shipment Order ORDER Order Flow – Generic




Agreement Type

Shipping Method DHL-Air-Worldwide Express Invoicing Rule Advanced Invoice


Drop Shipment Line Shipment Priority Standard Priority Accounting Rule Immediate








Price List Terex One Sales Scheduling Level Allow all scheduling actions Invoices With Rules





INVOICE



Tax Event

Currency

Conversion Type

US10.03018.510000000.000000.000000.0000.00000.00000


Standard (Line Invoicing) Line Flow - Generic 10-JAN-2006

File Ref: 81761613.doc (v. )





Comment

Mixed Mixed Mixed ORDER Order Flow – Generic




Agreement Type





Return-Credit Only, No Receipt Freight Terms Prepay & Add Source






Price List Terex One Sales Scheduling Level No Reservations Invoices With Rules





INVOICE



Tax Event

Currency

Conversion Type

US10.03018.510000000.000000.000000.0000.00000.00000


Standard (Line Invoicing) Line Flow - Generic 10-JAN-2006

Standard (Line Invoicing) Configured Item Line Flow - Configuration

29-NOV-2005

Return-Credit Only, No Receipt Line Flow - Return for Credit Only

29-NOV-2005

Return Line, Receipt-Approval Line Flow - Return for Credit with Receipt

29-NOV-2005

File Ref: 81761613.doc (v. )





Comment

Return, Receipt Return with Receipt Return ORDER Order Flow – Generic




Agreement Type





Return Line, Receipt-Approval Freight Terms Prepaid Source






Price List Terex One Sales Scheduling Level No Reservations Invoices With Rules





INVOICE



Tax Event

Currency

Conversion Type

US10.03018.510000000.000000.000000.0000.00000.00000


Return Line, Receipt-Approval Line Flow - Return for Credit with Receipt

13-DEC-2005

File Ref: 81761613.doc (v. )



File Ref: 81761613.doc (v. )



<Seeded Workflows for Transaction Types Table>

Header Workflows

Name Description

Order Flow - Generic This has Booking and Close Order sub-processes in it. This can be used both by Orders and returns.Order Flow - Generic with Header level Invoicing

This has Booking, Header Level Invoicing and Close Order sub-processes in it.

Order Flow - Return with Approval

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.

Line Flow - ATO Model 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.

Line Flow - Configuration 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.

Line Flow - Configuration with Authorize to Ship

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

Line Flow - Generic 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.

Line Flow - Generic with Authorize to Ship

This is identical to the ‘Line Flow - Generic’ except that it also has an additional authorization process before Shipping. This is for RLM users.

Line Flow - Generic with Header Level Invoicing

A version of the ‘Line Flow - Generic’ that works with the seeded Header Flow to support Header Level Invoice Interface.

Line Flow- Generic, Bill Only This only has Enter Line (wait for Booking), Invoice Interface Line and Close Line sub-processes in it.Line Flow - Generic, Ship Only

A version of the ‘Line Flow - Generic’ without Invoicing. This can be used for Internal Orders.

Line Flow - Standard Service 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.

Line Flow - Return for Credit Only

This has Enter Line (wait for Booking), Invoice Interface Line and Close Line sub-processes in it.

Line Flow - Return for Credit only with Approval

This is identical to the ‘Line Flow - Return for Credit Only’ with a Wait for a Header Approval after ‘Enter Line’.

Line Flow - Return for Credit This has Enter Line (wait for Booking), RMA Receiving, Fulfill Line, Invoice Interface line and Close Line

File Ref: 81761613.doc (v. )



with Receipt sub-processes in it.Line Flow - Return for Credit with Receipt and Approval

This is identical to the ‘Line Flow - Return for Credit with Receipt’ with Wait for Header Approval after ‘Enter Line’.

File Ref: 81761613.doc (v. )



OM: Order AOL Document Sequences (Order Numbering)

Setup>Documents>Define

FormName Document SequencesProcess:





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 To Type Message Initial Value

DE Orders Oracle Order Management

15-Nov-2005 Automatic √ 1

Order Oracle Order Management

15-Nov-2005 Automatic √ 1000000

UK Orders Oracle Order Management


UK Order Gapless Oracle Order Management


RETURNS Oracle Order Management

30-Jun-2004 Automatic √ 1

File Ref: 81761613.doc (v. )



OM: Order Assign Document Sequences

Setup>Documents>Assign (additional assignments will be required for Order Types)

FormName Sequence Assignments

tab Documents – To be documented as Order Transaction types have been definedApplication Category Set of Books Method

Oracle Order Management Standard TEREX US SET OF BOOKS AutomaticOracle Order Management Standard-Quote TEREX US SET OF BOOKS AutomaticOracle Order Management Internal TEREX US SET OF BOOKS AutomaticOracle Order Management Internal-Quote TEREX US SET OF BOOKS AutomaticOracle Order Management Quote TEREX US SET OF BOOKS AutomaticOracle Order Management Quote-Quote TEREX US SET OF BOOKS AutomaticOracle Order Management RMA - Credit TEREX US SET OF BOOKS AutomaticOracle Order Management RMA - Credit-Quote TEREX US SET OF BOOKS AutomaticOracle Order Management Drop Shipment TEREX US SET OF BOOKS AutomaticOracle Order Management Drop Shipment-Quote TEREX US SET OF BOOKS AutomaticOracle Order Management Mixed TEREX US SET OF BOOKS AutomaticOracle Order Management Mixed-Quote TEREX US SET OF BOOKS Automatic

Oracle Order Management Return, Receipt TEREX US SET OF BOOKS AutomaticOracle Order Management Return, Receipt-Quote TEREX US SET OF BOOKS Automatic

ADDITIONAL DHM ORDER TYPES WILL BE ADDED AS NEEDED FOR Orders



tab AssignmentApplication Category Start Date End Date Sequence

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

File Ref: 81761613.doc (v. )



Application Category Start Date End Date Sequence

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> ORDERS





File Ref: 81761613.doc (v. )



OM: Define Credit Checking

Setup>Rules>Credit

FormName Credit Check RulesProcess:






Description: Use this form to define your credit checking rules.

tab OptionsRule Name OCM Default Credit

Check RuleEffective Dates

Credit Check Level Sales Order Credit Hold Level Sales Order Conversion Type CorporateCheck Item Categories No Send Hold Notification No Override Manual Release

tab ExposureRule Name OCM Default Credit Check Rule 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

Maximum Days Past Due365

File Ref: 81761613.doc (v. )



OM: Define Holds

Setup>Orders>Holds

FormName HoldsProcess:






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 Description Type Workflow Item

Workflow Activity Effective Dates

3A7 Change Notification Hold

Autocreate Config Exception

Booking Hold

Line level hold - Waiting for a response on 3A7This hold is automatically placed when BOM created by Autocreate Config needs user verificationHold to Prevent Booking of Orders

Change Notification Hold for 3A7Exception Hold

Order Administration Hold OM Order Header

Book Order

Authorizations

Responsibility Authorized Action Effective Date From Effective Date To

Additional Resp TBD

File Ref: 81761613.doc (v. )



OM: Define Attachment Document Categories

Setup>Orders>Attachments>Document Categories

FormName Document CategoriesProcess:






Description: Use this form to define Document Categories for use with Attachments.

<Document Categories>Ref # Category Default Data Type Effective Dates:

FromEffective Dates:To

CN 1 Printed Documents

Assignements

<Category Assignments> (Document Category)Category Type Name Format

Printed Documents Form Blanket Sales Agreements

Form Quick Sales Orders

Form Sales Orders

For Future the document category setups needs to be re-valuated

File Ref: 81761613.doc (v. )



OM: Define Attachments

Setup>Orders>Attachments>Documents

FormName Attachments (will be added after conversions)Process:





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)

File Ref: 81761613.doc (v. )



Addition RulesEntity Rules: Group Number Attribute Attribute Value

<Documents>Category


Source: Data Type

Source: File

Usage

Security: Type

Security: Owner


Effective Dates: To

Magnification

(Comment Text)


File Ref: 81761613.doc (v. )



<Documents>Category


Source: Data Type

Source: File

Usage

Security: Type

Security: Owner


Effective Dates: To

Magnification

(Comment Text)

File Ref: 81761613.doc (v. )




File Ref: 81761613.doc (v. )



OM: Define Freight Carriers

Shipping>Setup>Freight Carriers, Cost Types>Freight Carriers

FormName Freight Carriers - Additional Freight Carriers to be added during PROD SetupsProcess:





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 Enable Manifesting

Comments – Address Info/Contacts/Telephones

DHL DHL YES

Redmond - TRUCK RED-TRK USD YES

Southaven Truck STH-TRK USD YES

Carrier Service Mode Ship Method Org

DHL Worldwide Express

AIR DHL-Air-Worldwide Express US Operating Orgs

2nd Day Air AIR DHL-Air-2nd Day Air US Operating Orgs

Redmond - TRUCK

Ground LTL RED-TRK-LTL-Ground US Operating Orgs

Southaven Truck

Ground LTL STH-TRK-LTL-Ground US Operating Orgs

File Ref: 81761613.doc (v. )



OM: Define Freight Cost Types

Setup>Shipping>Freight>Freight Cost Types

FormName Freight Cost Types Process:

Order FullfillmentBusiness Area: Order Management Setup

Date:

Control Number:


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 Charge Amount Effective Dates

Map to Charges

Freight Cost – US Freight Cost – US USD

Handling Charge – US Handling Charge – US USD

Packaging Charge – US Packaging Charge – US USD

File Ref: 81761613.doc (v. )



OM: Define Shipping Documents

Shipping>Setup>Documents>Document Sets

FormName Document Sets Process:





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> (All Pick Release Documents)Document Set

Seed Data only

File Ref: 81761613.doc (v. )



Description

Usage


Effective Dates: To

Printing Method

Documents:

Seq Application Report Name Description

<Shipping Document Sets> Document Set

Description

CNage

File Ref: 81761613.doc (v. )



Effective Dates: From<Current Date>

Effective Dates: To

Printing Method

Documents:

Seq Application Report Name Description

File Ref: 81761613.doc (v. )



OM: Define Release Sequence Rules

Shipping>Setup> Picking>Define Release Sequence Rules

FormName Release Sequence RulesProcess:





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 NumberRule

DescriptionThis is the default Pick Sequence Rule for Shipping Execution Description

Effective Dates: From 31-MAY-2002 Effective Dates: From

Effective Dates: To Effective Dates: To

Release Priority Priority Ascending Descending Release Priority Priority Ascending Descending

Order1 Y

Order

Outstanding Invoice Value

Outstanding Invoice Value

Schedule DateY

Schedule Date

Departure DateY

Departure Date

Shipment PriorityY

Shipment Priority

File Ref: 81761613.doc (v. )



OM: Define Release Rules

Shipping>Setup>Picking>Define Release Rules Form

FormName Release Rules Process:





Process Owner:

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

File Ref: 81761613.doc (v. )



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:

File Ref: 81761613.doc (v. )



Rule

Subinventory

Inventory: Default Stage: Locator

File Ref: 81761613.doc (v. )



OM: Define Pick Slip Grouping Rules

Shipping>Setup>Picking>Define Pick Slip Grouping Rules

FormName Pick Slip Grouping RulesProcess:





Process Owner:

Description: Use this form to define grouping rules to determine how released picking lines are grouped onto pick slips. Grouping rules allow you tospecify 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

File Ref: 81761613.doc (v. )



Rule Name

Group By: Delivery

Group By: Shipment Priority

File Ref: 81761613.doc (v. )



OM: Define Shipping Parameters

Shipping>Setup>Shipping Parameters

FormName Shipping Parameters – Need to setup for all shipping Organizations.Process:





Process Owner:

Description: Use this form to define the default parameters used throughout a specific warehouse (organization).

<Shipping Parameters> V01 Parameter Value

Weight UOM ClassWEIGHT

Volume UOM ClassVOLUME

Percent Fill BasisWEIGHT

Secondary Export Country Screening

CN

Not required

<Shipping Parameters> (Pick Release)Parameter Value Parameter Value

Release Sequence RuleDefault: Order Number

Default Stage SubinventoryStage

Pick Slip Grouping RuleDefault: Order Number

Default Stage Locator

Print Pick SlipAt the End

Number of Pick Slip Lines

Default Pick Release Document SetAll Pick Release Documents

Auto DetailYes

Autocreate Delivery CriteriaWithin Order

Autocreate DeliveriesYes

<Shipping Parameters> (Shipping Transaction – RD1)

File Ref: 81761613.doc (v. )



Parameter Value Parameter Value

Default Delivery Document SetShip Confirm Documents

Goods Dispatched AccountUS10.03018.537010000.000000.000000.US10.00000.00000

Weight / Volume CalculationManual

Freight Class Category Set

Enforce Packing in ContainersNo

Commodity Code Category Set

Auto Pack OptionYes

Enforce Ship MethodYes

Defer Interface

Container Inventory Control Allow Future Ship Date

<Shipping Parameters> (Delivery Grouping)Parameter Value Parameter Value

Ship From LocationYes

Ship To LocationYes

CustomerYes

Intermediate Ship To LocationNo

Freight TermsNo

Ship MethodYes

FOB CodeNo

For CRP-1 all other Inventory Org shipping parameter is base on RD1

File Ref: 81761613.doc (v. )



OM: Define Transportation Calendars

Shipping>Setup>Calendars>Assign

FormName Assign Calendars Process:





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, customer’s sites, supplier, supplier’s 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 Enabled

File Ref: 81761613.doc (v. )



File Ref: 81761613.doc (v. )



OM: Define Shipping Exceptions –

Shipping>Setup>Define Exceptions

FormName Define Shipping Exceptions - Process:





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 No Action Required

Workflow Item Type Workflow Process Initiate Workflow Y/N

Will update all exceptions to Low Severity Level

File Ref: 81761613.doc (v. )



OM: Define Shipping Document Categories

Shipping>Setup>Documents>Document Categories

FormName Document CategoriesProcess:





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 Delimiter Default Appearance

Category Name Description Document

Category Includes Ship Methods Locations

Sequence Prefix

DHM

DHM

Suffix

US

CN

Delimiter Default Appearance

File Ref: 81761613.doc (v. )



OM: Shipping Document Sequences

Shipping>Setup>Documents>Document Sequences

FormName Document SequencesProcess:





Process Owner:

Description: Use this form to define AOL Document Sequences for automatic numbering of shipping documents.

Name Application From To Type Message Initial Value

File Ref: 81761613.doc (v. )



OM: Assign Shipping Report Document Sequences

Shipping>Setup>Documents>Assign SequencesFormName Sequence Assignments

tab DocumentsName Category Set of Books Method

tab AssignmentApplication Category Start Date End Date Sequence

Oracle Shipping

Oracle Shipping

Oracle Shipping

Oracle Shipping

File Ref: 81761613.doc (v. )



OM: Shipping Execution Grants

Shipping>Setup>Grants and Role Definitions>Grants

FormName Shipping Execution Grants - Additional Users will be added as they are created in

PRODProcess:

Order ManagementBusness Area:




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 Org Start Date End Date

Users added as needed.

Upgrade <Current Date>

File Ref: 81761613.doc (v. )



Order Management

January 11, 2006

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

File Ref: 81761613.doc (v. )
