Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Jayesh Patel January 11, 2006 January 11, 2006 BR100-OM 1.0
Document Control
Change Record
1
Date 11-Jan-06
Author J Patel
Version Draft 1a
Reviewers
Name Position
Distribution
Copy No. 1 2 3 Name Library Master Location 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.
(v. 1 )
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 )
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 )
Responsibilities
Control Number:
System Admin
Priority (H, M, L):
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
Terex Corporation
Menu Exclusions
(v. )
System Administration>Profile>System
Profile Site Order Management Super User, DHM US Order Managemen t Super User, DHM CN
HR: Business Group HR: Security Profile HR: User Type MO: Operating Unit GL: Set Of Books Default Country Currency:Mixed Currency Precision Sequential Numbering
(v. )
Setup Task
Responsibility
Due Date
QA Responsibility
QA Due Date
Signature Approval
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
J Patel J Patel
J Patel
J Patel
(v. )
BR.100 Application Setup Workflow SubWorkflow Name Setup Task Responsibility Due Date QA Responsibility QA Due Date
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
J Patel J Patel
J Patel
(v. )
BR.100 Application Setup Workflow SubWorkflow Name Setup Task Responsibility Due Date QA Responsibility QA Due Date
OM: Assign Shipping Report Document Sequences OM: Assign Shipping Execution Grants
J Patel
J Patel
(v. )
Profile Options
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 GML: OM Integration OM: Activate Change Management System OM: Add Customer OM: Add Customer (Order Import) Description 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 Controls the level of access to the Add Customer form, which is available with OM Family Pack F onwards. This profile option determines which users can create new customers and customer details when importing order using the Order Import concurrent program. Select from: e All: Users can access the Add Customer window to create new customers, customer addresses, and customer contacts. e None: User is not given access to the Add Customer form. e 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. 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. Value Resp Level No Yes Address & Contact No
OM: Administer Public Queries. OM: Apply Automatic Attachments OM Available to Overide ATP OM: Auto Push Group Date
OM: AutoSchedule
Yes
(v. )
BR.100 Application Setup Profile Option Name Description Also to set BOM: Automatic Reservation to Yes OM: Branch Scheduling OM: Charges for Backorders OM: Charges for included item This profile option is for internal use only. Do not attempt to enter or modify the value of the profile option. To include Freight Charges for Backorder 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: e Yes: Calculate and return charges for included items. e 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: e Yes: Order Management populates the commitment applied and then will interface the commitment amount applied to Oracle Receivables. e 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.) 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 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. Yes Yes No
Yes
No
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. )
BR.100 Application Setup Profile Option Name OM: Cust Item Shows Matches Description 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. This profile option should not be set unless directed by an Oracle Representative. 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: e NULL: Do not print any debug messages e 1: Level 1; Print a limited subset of debug messages (level 1) e 2: Level 2; Print a limited subset of debug messages, including level 1 e 3: Level 3; Print a limited subset of debug messages, including levels 1,2 e 4: Level 4; Print a limited subset of debug messages, including levels 1,2 3 e 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
Yes
OM: DBI Installation OM: Deactivate Pricing at Scheduling OM: Debug Level
No Null 0
No
N/A
21 requires iPayment
(v. )
BR.100 Application Setup Profile Option Name Validity Period OM: GSA Discount Violation Action OM: Generic Update Constraints Apply to DFF Description valid. This profile is required and the default value is 21 days 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
lines; this profile option does not control order line fields other than the flexfield attributes. e If you select Yes' (the default), you cannot update processing-constrained flexfield attributes on closed orders. e If profile is set to 'No', you can update processing-constrained flexfield attributes on closed orders. e 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 OM: Included Item Freeze Method OM: Invoice Numbering Method OM: Invoice Source OM: Invoice Transaction Type OM: Item Change Honors Frozen Price No reference in OM Implementation Guide. Left as Blank No LOVs 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: e 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. e 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: e 1: Only return item descriptions, with child indentations. e 2: Only return item description without child indentations. e 3: Display the concatenated item segment values with child indentations. e 4: Display the concatenated segment values without indentation. 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 (v. ) Blank Booking Automatic Invoice Invoice No
OM Negative Pricing
BR.100 Application Setup Profile Option Name Description 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: e 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. e 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: e 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. e 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
No
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
No Need iPayment
Null
(v. )
BR.100 Application Setup Profile Option Name Description 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: e 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. e 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. e 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 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: e 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. e 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. 7
Warning
Null
OM: Risk Factor Threshold for Electronic Payments OM: Run Order Import for XML
50
Null
OM: Sales Order Form: Cascade Header Changes to Line OM: Sales Order Form: Restrict Customers
(v. )
BR.100 Application Setup Profile Option Name Description Note: Changed from Global to Current OM: Schedule Line on Hold OM: Set Receivalbes Transaction Date fro Non-Shippable Lines 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: e Yes: Populate the Oracle Receivables transaction date for non-shippable order or return lines with the current system date. e 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 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: e 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. e 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: e 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. e 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: e 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. e 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
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
Yes
Yes
(v. )
BR.100 Application Setup Profile Option Name QP: Accrual UOM Class Description 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 e 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 e Yes: Enables queries saved in Public folders to be deleted or renamed. e No: Queries saved in Public folders cannot be deleted or renamed. Future functionality Advance Pricing functionality 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 e Always expressed in days. This profile option is visible and can be updated at the site and application level. 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 1 or QP: Cross Order Volume Period 3. Value e Always expressed in days. This profile option is visible and can be updated at the site level. Default value: Blank 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 e This value is always expressed in days. This profile option is visible and can be updated at the site level. Default Value: No Value e 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. e 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 e 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. e 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: Allow Duplicate Modifiers QP: Cascade Asked for Promotion QP: Cross Order Volume Period1
Yes No Null
Null
Null
No
QP: Debug
(v. )
No
No
QP: Inventory Decimal Precision QP: Item Validation Organization QP: Limit Exceed Action
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 e Soft--Full Benefit Amount: Applies the full benefit to the order even if the transaction exceeds the defined limit. e 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
Null
(v. )
BR.100 Application Setup Profile Option Name Description 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 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 e 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 e 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 Default value: Blank 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. 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 e Yes: Enables the promotional limits features to be used. e 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! Null
YES
Yes
Null
Order Fulfillment No
(v. )
BR.100 Application Setup Profile Option Name QP: Return Manual Discounts Description 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: e Discounts e Surcharges e Price break lines e 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 e 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. e 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.
QP: Selling Price Rounding Option QP: Set Request Name Default value: Blank Values e Yes: The value of the Request Name field in the Pricing Engine Request window will be prefixed with the Order ID. e 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. 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.
Extended
(v. )
BR.100 Application Setup Profile Option Name QP: Valueset Lookup Filler Description 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 e Yes: The message displays. e 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. .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 e 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. e 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: e Period Start/End Dates e Ordered UOM (Time uom in which the price needs to be fetched) e Ordered quantity
No
Yes
Null
(v. )
Business Area:
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 Reference Field Context Field Values Code Name Desc. Enab led Comments VALUE SET NAME: SEE BELOW
Control Number:
Priority(H, M, L):
DFF Summary
(v. )
(v. )
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
(v. )
Value Sets
Value Set Name List Type Format Type Max Size Precision Numbers Only Uppe rcase Only Righ t Justi fy Validation Type Edit Table Appl. Table Name Value Meaning ID Where
(v. )
Organizations
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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 US OU OU - US Item Validation Organization IO - ITEM MASTER ORG Customer Relationships Related Customers Audit Trail Enabled when Order is Booked Margin Calc Cost Enabled
(v. )
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
Description: Use these forms to define Lookups for Order Management Lists. For CRP-1 Seeded data is accepted
QuickCode Type CANCEL_CODE Code User Name Cancel/Audi t Codes Meaning Application Oracle Order Management Tag Access Level Extensible Start date
To be maintained on going
Description Allow
(v. )
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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 AHL Automotive CRM Apps Contract Renewal Copy EDI Field Service Report IBU IStore Account IStore Oneclick IStore Walkin Internal Online Order Capture Quotes POL Sales and Marketing Collateral Sales and Marketing Quote Service Description Order Source for Advanced Service on Line Service Order source is any of the CRM applications Order created to renew contracts Copy EDI Field Service report for charging parts, labour and expenses from the field Order source for iSupport Order source for iStore account user Order created by iStore one click Order source for iStore walk in customer Web For Orders created Online Order source for Order Capture quoting module Partners Relationship Management Sales and Marketing Collateral Sales and Marketing Quote Service Y Application Set Up Control Sheet - Order Management Y Enabled Y/N
(v. )
BR.100 Application Setup Import Source Name Service Billing Service Request TeleSales Order Telesales Collateral Web XML Description Service Billing Service Request Order Source for TeleSales Order source for telesales Web Order Source for XML Messages Enabled Y/N Y Y
(v. )
Processing Constraints
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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
Y Conditions 101 Any Order Line Line No Booked No You can not update Request Date - Please Contact Customer Service
Applicable To All Responsibilities Authorized Responsibilities ORDER MANAGEMENT Resp (Various) Constrained Responsibilities
(v. )
Note: Build Attribute Mapping Program needs to be run after Price Lists created
Price List
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
tab
List Lines
Product Attribute Product Value UOM Primary UOM Value
Product Context
(v. )
Header
Name Standard Price List Corporate Price List Additional Price lists will be added as needed Currency USD Round To -5 Effective Date (from) Effective Date (to) Payment Terms Freight Terms Freight Carriers Description Standard Price List Corporate Prie List
Comments
tab
List Lines
Product Attribute Product Value UOM Primary UOM Value
(v. )
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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
(v. )
Define Modifier
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
<Priority (H, M, L)> Attention: Before you define discounts, enable your Pricing Attributes descriptive flexfields in the Enable Parameters window.
Description
tab
Modifiers
Level Modifiers Type Start date Print On Invoice Automatic Override
Modifier Number
tab
Modifiers (continued)
(v. ) Application Set Up Control Sheet - Order Management
BR.100 Application Setup Pricing Phase Incompatibility Phase Bucket Proration Type GL Value Product Attribute
tab
Discounts
Level Mod. Type Charge Name Includ e on Retur ns Formula Application Method Value Accrue
Modifier Number
(v. )
Transaction Types
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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 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 Description Effective Date Start Warehouse Transaction Type Code Order Order Order Order Order Mixed Return Line Line Line Line Line Line Line Order Category Order Workflow
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-Credit Only, No Receipt Return Line with Receipt, Approval
Order Order Order Return Order Order Order Order Return Order Order Order Order Order
Order Management January 11, 2006 Description Standard WarehoCNe Shipping Method Order Category Order Trans Type Code LINE Shipping IO - REDMOND BLDG1 MFG Invoicing Rule Standard Priority Prepay & Add Accounting Rule Finance Rule Advance Invoice Immediate Source Dates Order Workflow Comment
Customer Site
ORDER MANAGEMENT
Credit Method For Allow all scheduling actions Invoices With Rules Split Term Invoices Prorate Prorate
Transaction Type Return (Receipt & Approval) Main Document Agreement Type
Dates
Order Workflow
Comment
(v. )
BR.100 Application Setup Transaction Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Pricing Price List Enforce Price List Y/N Credit Check Rule Ordering Checking Description Shipment Priority Freight Terms Order Category Trans Type Code Dates Order Workflow Accounting Rule Immediate Source
FOB Ship Source Type Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For No Reservations Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type Prorate Prorate
Transaction Type ATO Model Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N
Description ATO Model WarehoCNe Shipping Method Shipment Priority Freight Terms
Dates
Order Workflow
Comment
Shipping IO - REDMOND BLDG1 MFG Invoicing Rule Standard Priority Prepay & Add Accounting Rule
FOB
Customer Site
Invoice Source
ORDER MANAGEMENT
(v. )
BR.100 Application Setup Transaction Type Purchase Order Required Y/N Pricing Price List Enforce Price List Y/N Credit Check Rule Ordering Checking Description Ship Source Type Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type Allow all scheduling actions Invoices With Rules Split Term Invoices Order Category Trans Type Code Dates Order Workflow Non-Delivery Invoice Source
Transaction Type Configured Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Pricing Price List Enforce Price List Y/N
Dates
Order Workflow
Comment
Shipping IO - REDMOND BLDG1 MFG Invoicing Rule Standard Priority Prepay & Add Accounting Rule
FOB Ship Source Type Demand Class Scheduling Level Auto Schedule Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For Allow all scheduling actions Invoices With Rules Split Term Invoices Prorate Prorate
(v. )
BR.100 Application Setup Transaction Type Credit Check Rule Ordering Checking Description Order Category Inspection Required Y/N Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type Trans Type Code Dates Order Workflow
Transaction Type Drop Shipment 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 Pricing Price List Enforce Price List Y/N Credit Check Rule Ordering Checking
Description Drop Shipment WarehoCNe Shipping Method Shipment Priority Freight Terms
Dates
Order Workflow
Comment
Shipping IO - REDMOND BLDG1 MFG Invoicing Rule Standard Priority Prepay & Add Accounting Rule
FOB Ship Source Type Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For Allow all scheduling actions Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Application Set Up Control Sheet - Order Management Prorate Prorate
(v. )
BR.100 Application Setup Transaction Type Description Order Category Trans Type Code Dates Currency Conversion Type Order Workflow
Transaction Type Return-Credit Only, No Receipt Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Pricing Price List Enforce Price List Y/N Credit Check Rule Ordering Checking
Description Return-Credit Only WarehoCNe Shipping Method Shipment Priority Freight Terms
Dates
Order Workflow
Comment
Shipping IO - REDMOND BLDG1 MFG Invoicing Rule Standard Priority Prepay & Add Accounting Rule
FOB Ship Source Type Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For No Reservations Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type Prorate Prorate
(v. )
BR.100 Application Setup Transaction Type Return Line, Receipt-Approval Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Pricing Price List Enforce Price List Y/N Credit Check Rule Ordering Checking WarehoCNe Shipping Method Shipment Priority Freight Terms Standard Priority Prepay & Add Description Return Line with Receipt, Approval Order Category Return Trans Type Code LINE Shipping IO - REDMOND BLDG1 MFG Invoicing Rule Accounting Rule Finance Rule Dates Order Workflow
FOB Ship Source Type Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For No Reservations Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type Prorate Prorate
(v. )
BR.100 Application Setup Transaction Type Standard Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Price List Enforce Price List Y/N Credit Check Rule Ordering Checking WarehoCNe Shipping Method Standard (Line Invoicing) Shipment Priority Freight Terms Standard Priority Prepay & Add Description Standard Order Category Order Trans Type Code ORDER Shipping IO - REDMOND BLDG1 MFG Invoicing Rule Accounting Rule Dates Order Workflow
Order Flow Check box Retain Generic Document Number Finance Rule Advance Invoice Immediate Source
FOB Ship Source Type Pricing Terex One Sales Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For Allow all scheduling actions Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Prorate Prorate
Description Internal
(v. )
BR.100 Application Setup Transaction Type Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Price List Enforce Price List Y/N Credit Check Rule Ordering Picking/Purchas e Release Credit Check - US Credit Check - US WarehoCNe Shipping Method Standard (Line Invoicing) Shipment Priority Freight Terms DHL-Air-2nd Day Air Standard Priority Invoicing Rule Accounting Rule Description Order Category Trans Type Code Dates Order Workflow Finance Rule
Shipping
FOB Ship Source Type Pricing Internal PL 2005 Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
Invoice Source Non-Delivery Invoice Source Credit Method For Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type INTERNAL INVOICE US10.03018.510000000.000000.00 0000.0000.00000.00000
(v. )
Transaction Type Quote Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Price List Enforce Price List Y/N Credit Check Rule Ordering Picking/Purchas e Release
Description Quote
Dates
Order Workflow
Comment
Order Flow Check box Retain Generic Document Number Finance Rule Advanced Invoice Immediate Source
Accounting Rule
FOB Ship Source Type Pricing Terex One Sales Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Invoice Source Non-Delivery Invoice Source Credit Method For Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type Invoice
(v. )
Transaction Type RMA - Credit Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Price List Enforce Price List Y/N Credit Check Rule Ordering Picking/Purchas e Release
Dates
Order Workflow
Comment
Order Flow Check box Retain Generic Document Number Finance Rule Advanced Invoice Immediate Source
Accounting Rule
Freight Terms
FOB Ship Source Type Pricing Terex One Sales Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Invoice Source Non-Delivery Invoice Source Credit Method For Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type Invoice US10.03018.510000000.000000.00 0000.0000.00000.00000
(v. )
Transaction Type Drop Shipment Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Price List Enforce Price List Y/N Credit Check Rule Ordering Picking/Purchas e Release
Dates
Order Workflow
Comment
Shipping WarehoCNe Shipping Method DHL-Air-Worldwide Express Standard Priority Prepay & Add Invoicing Rule
Order Flow Check box Retain Generic Document Number Finance Rule Advanced Invoice Immediate Source
Accounting Rule
FOB Ship Source Type Pricing Terex One Sales Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For Allow all scheduling actions Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type INVOICE US10.03018.510000000.000000.00 0000.0000.00000.00000
(v. )
Transaction Type Mixed Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Price List Enforce Price List Y/N Credit Check Rule Ordering Picking/Purchas e Release
Description Mixed
Dates
Order Workflow
Comment
Shipping WarehoCNe Shipping Method DHL-Air-Worldwide Express Standard Priority Prepay & Add Invoicing Rule
Order Flow Check box Retain Generic Document Number Finance Rule Advanced Invoice Immediate Source
Accounting Rule
FOB Ship Source Type Pricing Terex One Sales Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For No Reservations Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type INVOICE US10.03018.510000000.000000.00 0000.0000.00000.00000
(v. )
Transaction Type Return, Receipt Main Document Agreement Type Default Order Line Type Default Return Line Type Sales Document Type Agreement Required Y/N Purchase Order Required Y/N Price List Enforce Price List Y/N Credit Check Rule Ordering Picking/Purchas e Release
Dates
Order Workflow
Comment
Shipping WarehoCNe Shipping Method Shipment Priority DHL-Air-Worldwide Express Standard Priority Prepaid Invoicing Rule
Order Flow Check box Retain Generic Document Number Finance Rule Advanced Invoice Immediate Source
Accounting Rule
Freight Terms
FOB Ship Source Type Pricing Terex One Sales Demand Class Scheduling Level Auto Schedule Y/N Inspection Required Y/N
Customer Site
ORDER MANAGEMENT
Credit Method For No Reservations Invoices With Rules Split Term Invoices Receivables Transaction Type Cost of Goods Sold Account Tax Event Currency Conversion Type INVOICE US10.03018.510000000.000000.00 0000.0000.00000.00000
(v. )
(v. )
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 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
File Ref: 81761613.doc (v. )
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. 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
Application Set Up Control Sheet - Order Management
with Receipt Line Flow - Return for Credit with Receipt and Approval
sub-processes in it. This is identical to the Line Flow - Return for Credit with Receipt with Wait for Header Approval after Enter Line.
(v. )
Document Sequences
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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 DE Orders Order UK Orders UK Order Gapless RETURNS Application Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management From 15-Nov-2005 15-Nov-2005 15-Nov-2005 15-Nov-2005 30-Jun-2004 To Type Automatic Automatic Automatic Automatic Automatic Message Initial Value 1 1000000 1 1 1
(v. )
OM: Order Assign Document Sequences Setup>Documents>Assign (additional assignments will be required for Order Types)
Form N e am
Sequence Assignments
Documents To be documented as Order Transaction types have been defined
Category Standard Standard-Quote Internal Internal-Quote Quote Quote-Quote RMA - Credit RMA - Credit-Quote Drop Shipment Drop Shipment-Quote Mixed Mixed-Quote Return, Receipt Return, Receipt-Quote ADDITIONAL DHM ORDER TYPES WILL BE ADDED AS NEEDED FOR Orders Set of Books TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS TEREX US SET OF BOOKS ADDITIONAL DHM ORDER TYPES WILL BE ADDED AS NEEDED FOR Orders Method
tab
Application Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management
Automatic Automatic Automatic Automatic Automatic Automatic Automatic Automatic Automatic Automatic Automatic Automatic Automatic Automatic
ADDITIONAL DHM ORDER TYPES WILL BE ADDED AS NEEDED FOR Orders
tab
Assignment
Category Standard Standard-Quote Internal Internal-Quote Quote Quote-Quote Start Date <current date> <current date> <current date> <current date> <current date> <current date> End Date Sequence ORDERS ORDERS ORDERS ORDERS ORDERS ORDERS Application Set Up Control Sheet - Order Management
Application
(v. )
BR.100 Application Setup Application Category RMA - Credit RMA - Credit-Quote Drop Shipment Mixed Mixed-Quote Return, Receipt Return, Receipt-Quote ADDITIONAL DHM ORDER TYPES WILL BE ADDED AS NEEDED FOR Orders Start Date <current date> <current date> <current date> <current date> <current date> <current date> <current date> ADDITIONAL DHM ORDER TYPES WILL BE ADDED AS NEEDED FOR Orders ADDITIONAL DHM ORDER TYPES WILL BE ADDED AS NEEDED FOR Orders End Date Sequence ORDERS ORDERS ORDERS ORDERS ORDERS ORDERS ORDERS ADDITIONAL DHM ORDER TYPES WILL BE ADDED AS NEEDED FOR Orders
(v. )
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
Options
OCM Default Credit Check Rule Sales Order No Effective Dates Credit Hold Level Send Hold Notification Sales Order No Conversion Type Override Manual Release Corporate
tab
Exposure
OCM Default Credit Check Rule Use Pre-Calculated Exposure Include External Credit Exposure Include Open Receivables Balance Include Payments at Risk Y/N Open Receivables Days No No Yes Yes 90 Effective Dates Include Uninvoiced Orders Y/N Include Freight and Special Charges Include Tax Include Orders Currently On Hold Y/N Scheduled Shipping Horizon Date Yes Yes Yes Yes 365
Rule Name
365
(v. )
Holds
Business Area: Date:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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 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 Type Change Notification Hold for 3A7 Exception Hold Order Administration Hold OM Order Header Book Order Workflow Item Workflow Activity Effective Dates
Authorizations Responsibility Additional Resp TBD Authorized Action Effective Date From Effective Date To
(v. )
Document Categories
Business Area: Date:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
Description: Use this form to define Document Categories for use with Attachments.
<Document Categories>
Ref # Category Default Data Type Effective Dates: From Effective Dates: To
CN Printed Documents
(Document Category)
Name Blanket Sales Agreements Quick Sales Orders Sales Orders Format
(v. )
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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.
(v. )
Addition Rules
Entity Rules: Group Number Attribute Attribute Value
<Documents>
Category Description (Comment Name) Source: Data Type Source: File Usage Security: Type Security: Owner Effective Dates: From Effective Dates: To Magnification (Comment Text)
Addition Rules
Entity Rules: Group Number Attribute Attribute Value
(v. )
<Documents>
Category Description (Comment Name) Source: Data Type Source: File Usage Security: Type Security: Owner Effective Dates: From Effective Dates: To Magnification (Comment Text)
(v. )
Addition Rules
Entity Rules: Group Number Attribute Attribute Value
(v. )
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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.
Carrier DHL
(v. )
Process:
Order Fullfillment
Control Number:
<Priority (H, M, L)> Description: Use this form to define freight charges and freight carriers to specify on orders.
Freight Cost Freight Cost US Handling Charge US Packaging Charge US Freight Cost Type Freight Cost US Handling Charge US Packaging Charge US Charge Currency USD USD USD Freight Charge Amount Effective Dates Map to Charges
(v. )
Document Sets
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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.
(v. )
Description
(v. )
BR.100 Application Setup Effective Dates: From Effective Dates: To Printing Method Documents: Seq Application Report Name Description <Current Date>
(v. )
OM: Define Release Sequence Rules Shipping>Setup> Picking>Define Release Sequence Rules
Form N e am
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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
31-MAY-2002
(v. )
Release Rules
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number> <Priority (H, M, L)> 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.
(v. )
BR.100 Application Setup 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: Application Set Up Control Sheet - Order Management
(v. )
(v. )
OM: Define Pick Slip Grouping Rules Shipping>Setup>Picking>Define Pick Slip Grouping Rules
Form N e am
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number> <Priority (H, M, L)> 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.
(v. )
BR.100 Application Setup Rule Name Group By: Delivery Group By: Shipment Priority
(v. )
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number> <Priority (H, M, L)> Description: Use this form to define the default parameters used throughout a specific warehouse (organization).
(v. )
BR.100 Application Setup Parameter Default Delivery Document Set Weight / Volume Calculation Enforce Packing in Containers Auto Pack Option Value Ship Confirm Documents Manual No Yes Parameter Goods Dispatched Account Freight Class Category Set Commodity Code Category Set Enforce Ship Method Defer Interface Container Inventory Control Allow Future Ship Date Yes Value
US10.03018.537010000.000000.0 00000.US10.00000.00000
For CRP-1 all other Inventory Org shipping parameter is base on RD1
(v. )
Assign Calendars
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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)
Show Candidates
Site Calendars
Site Calendar Code Enabled
(v. )
(v. )
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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
Seeded Data
Description
Exception Type
Exception Handling
Manual Workflow Item Type Workflow Workflow Process Initiate Workflow Y/N No Action Required
(v. )
Document Categories
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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 Appearanc e
Category Name
Description
Document
Category Includes
Ship Methods
Locations
Sequence
Suffix US CN
Delimiter
Default Appearanc e
(v. )
Document Sequences
Business Area: Date: Process Owner:
Process:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
Description: Use this form to define AOL Document Sequences for automatic numbering of shipping documents.
Name Application From To Type Message Initial Value
(v. )
Sequence Assignments
Documents
Category Set of Books Method
tab
Name
tab
Assignment
Category Start Date End Date Sequence
(v. )
OM: Shipping Execution Grants Shipping>Setup>Grants and Role Definitions>Grants Shipping Execution Grants PROD
Process:
Form N e am
Busness Area:
Order Management
Control Number:
<Business Area>
Priority(H, M, L):
<Control Number>
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 Users added as needed. Role Upgrade Org Start Date <Current Date> End Date
(v. )
Order Management January 11, 2006 Order Management January 11, 2006
Closed Issues
ID Issue Resolution Responsibility Target Date Impact Date
(v. )