FNDPOMSV: How to Set Profile Options for Use With Advanced Pricing [ID 553399.

1] Modified 22-APR-2011 Type HOWTO Status MODERATED

In this Document Goal Solution OM: Charges For Backorders OM: Charges for included item OM: Charging Privilege OM: Credit Memo Transaction Type OM: Discounting Privileges OM: Enable Group pricing for DSP lines OM: GSA Discount Violation Action OM: Item Change Honors Frozen Price OM: Item Flexfield OM: List Price Override Privilege OM: Negative Pricing OM: Over Return Tolerance OM: Overshipment Invoice Basis OM: Promotion Limit Violation Action OM: Return Unfulfilled Referenced Line Action OM: Send Changed Lines to Pricing OM: Show Discount Details on Invoice OM: Under Return Tolerance OM:Unit Price Precision Type OM: UOM Class for Charge Periodic *New Profiles With R12 *QP: E-mail - From Address *QP: External Default Pricing Perspective *QP: Inbound XML Messaging Responsibility *QP: Internal Default Pricing Perspective *QP: Pricing Party Hierarchy Type *QP: Pricing Perspective Request Type QP: Accumulation Attributes Enabled QP: Accrual UOM Class QP: Administer Public Queries QP: Allow Buckets for Manual Modifiers QP: Allow Duplicate Modifiers QP: Batch Size for Bulk Import QP: Blind Discount Option QP: Break UOM Proration Allowed QP: Build Attributes Mapping Options QP: Consider Manual Linegroup Adjustments QP: Custom Ignore Pricing QP: Debug QP: Denormalize Qualifiers QP: Dynamic Sampling Level QP: Cross Order Volume Period1 QP: Cross Order Volume Period2 QP: Cross Order Volume Period3 QP: Custom Sourced QP: Get Custom Price Customized

QP: High Volume Order Processing Compliance QP: Insert Formula Step Values into Temp Table QP: Inventory Decimal Precision QP: Item Validation Organization QP: Licensed for Product QP: Limit Exceed Action QP: Line Volume UOM Code QP: Line Weight UOM Code QP: Modifier Find Window - Show records QP: Multi-Currency Installed Warning: For Multi-Currency Installed QP: Multi Currency Usage QP: Negative Pricing QP: Pass Qualifiers to Get_Custom_Price API QP: Price Rounding Warning: When QP: Price Rounding profile option is set to Enforce Currency Precision QP: Pricing Transaction Entity QP: Promotional Limits Installed Warning: Once the QP: Promotional Limits Installed profile option is enabled QP: Qualify Secondary Price Lists QP: Return Manual Discounts QP: Satisfied Qualifiers Option QP: Security Control Warning: For Oracle Applications Release 12 and Security Control QP: Security Default Maintain Privilege QP: Security Default ViewOnly Privilege QP: Selling Price Rounding Options QP: Set Request Name QP: Source System Code QP: Time UOM Conversion QP: Unit Price Precision Type QP: Valueset Lookup Filter QP: Verify GSA Violations Additional References: References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:
Oracle Advanced Pricing - Version: 11.5.1 to 12.1.3 - Release: 11.5 to 12.1 Oracle Advanced Pricing - Version: 11.5.10 to 12.1.3 [Release: 11.5 to 12.1] Information in this document applies to any platform. FORM:FNDPOMSV.FMB - Update Personal Profile Values

Goal
Assist with setup for profiles that influence advanced pricing.

Solution

OM: Charging Privilege This profile option controls your ability to manually apply freight and special charges on an order or order line. OM: Discounting Privileges . The profile option setting does not control the pricing of included items. then the calculate price flag will be Freeze price for the split line thus if freight is added at shipping. but you cannot modify non-overridable charges. Yes: The Calculate Price Flag will be set to Partial to enable charges to be calculated when shipping OM: Charges for included item This profile option determines if Order Management will calculate and return charges for included items. Default value is the name of the transaction type. Set at site level.it does not come over as an applied price adjustment. Freight is not applied to the split line.Order Management Profile Options OM: Charges For Backorders This profile controls the values of the calculate price flag on the order line for a manually split order line or a backordered order line which is partially picked or shipped. If the profile option is set to NO. View Only Access: You can only view charges. Select from: Yes: Calculate and return charges for included items. Select from: Full Access: You can modify and apply charges. No: Do not calculate charges for included items. only the calculation and return of charges associated with an order line containing an included item. and the pricing engine will not apply charges. Select from: No: or NULL: The Calculate Price Flag will be set to Freeze. Unlimited Access: You can modify and apply all charges including the non-overridable charges OM: Credit Memo Transaction Type This profile option value is transferred to Receivables if no value is defined for the credit memo transaction type.

None: No privileges. Note: A Null value for this profile option is handled as if you selected the value FULL. Note: When an order is copied and the item is changed on the order. * No: Order management will set the calculate price flag to Y. Select from: Full: Ability to apply any valid discount against an order or order line. whose original value is honored. the original value will control whether the order line gets repriced. regardless of whether the order type of the order enforces list prices. The default value is No. view-only access. Select from: Error: Provide error message Warning: Provide a warning message OM: Item Change Honors Frozen Price 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. You should only set this profile option to Yes when you want your orders created by demand interface qualify for Promotional Goods. OM: Enable Group pricing for DSP lines When demand interface appends order lines to an existing order. Non-Overridable Only: Ability to apply only non-overridable discounts against an order or order line. Setting this profile option to No improves demand interface performance. (Default value). Unlimited: Ability to apply any valid discount against any order or order line. . Select from: * Yes: Order Management will not change the value of the calculate price flag. this profile option controls whether other unchanged order lines should be sent to the Pricing Engine for repricing.This profile option provides the choice of controlling user's ability to apply discounts on an order or order line. OM: GSA Discount Violation Action This profile option determines how you want the user notified when you define a discount that results in an item price less than the price on a GSA discount for the same price list. as long as the order type of the order does not enforce list prices. and the order line will be repriced. the value of the Calculate Price Flag for the new order line is set dependent upon the value of the profile option OM: Item Change Honors Frozen Price. Other Item Discounts or other line group level modifiers defined in Advanced Pricing.

the quantity received will be compared with the RMA. Messages are generated and can be viewed within the Process Messages Window. Select from: Place holds where violated (either Line or Order): If the pricing engine returns an initial promotional hold. you can override the unit list price field from the main tab and immediately see selling price adjusted accordingly. The default value is zero (0). . material is received at the receiving dock. Set OM: Item Flexfield = System Items. place a hold for the corresponding order or order line. If set to this value. within tolerance or greater than tolerance. and the default is Null. the current behavior is retained. which could be less than tolerance. For instance. OM: Overshipment Invoice Basis This profile determines when an over-shipment happens. another return line will be created so that Purchasing can match it against the unordered receipt. When the received quantity is greater than tolerance. should the invoicing module invoice the ordered quantity or the shipped quantity. OM: Over Return Tolerance This profile option indicates the percentage by which a return line can be over-received. Order Management will use the value of this profile option to determine the course of action for the order or line. This profile option is set at the site level.OM: Item Flexfield This profile option determines the structure of the Item Flexfield (System Items) used by Order Management. OM: Promotion Limit Violation Action This profile option is optional. The profile option QP: Negative Pricing is used for price lists. This structure should be the same across all applications in the same database. If the pricing engine returns a possible promotional hold for an order or order line. Any value greater than or equal to zero (0) is a valid value. OM: List Price Override Privilege View Only is the default value. and controls whether a negative unit price can be entered on a price list. OM: Negative Pricing This profile option controls whether Order Management allows a negative list price or negative selling price to be determined by the Pricing Engine or to be entered as an override by a user on a sales order. which means unit list price field is protected. Purchasing will create a receipt with the quantity on the return line and an unordered receipt for the remaining quantity. This system level profile option determines the hold action Order Management will take when encountering an initial promotional hold returned by the pricing engine. When Order Management is notified by the customer about the over-return. Unlimited Privilege: If set to this value.

The discount information gets printed on a separate invoice lines from the order information. send all lines. Allow the order or order line to continue processing within its associated workflow. Place order on hold when any violation occurs (both Line and Order): If the pricing engine returns an initial promotional hold. OM: Send Changed Lines to Pricing When this profile option is set to Yes. this would mean send only changed lines to Pricing when a line is changed. do not apply a hold for either an order or order line. OM:Unit Price Precision Type This profile option controls the display of Unit Selling Price field (and list price) for Order Management sales order lines only. OM: Return Unfulfilled Referenced Line Action This profile allows non-fulfilled lines to be used as referenced lines. The default value is zero (0). On Oracle Applications R12. this profile has been moved to an Order Management parameter.No holds applied: If the pricing engine returns an initial promotional hold. The product line and the associated discount lines roll into the same revenue account. Otherwise. then Extended Amounts will include discounts. irrespective of the hold level. in addition to any order lines that may be marked for promotional hold. One needs to set profile option OM: Show Discount Details on Invoice to YES to print detail discount information on the invoice. place the order on hold. Select from: . The seeded value is Allow or no profile option entry will be treated as Allow. use responsibility: Order Management Super User (or equivalent) Navigate to Setup > System Parameters > Values Arrow down to "Show Discount Details on Invoice" 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. This profile option is set at the site level. If you set this profile option to No. OM: Show Discount Details on Invoice Determines whether or not to print detail discount information on the invoice. To evaluate or change the value. Any value between zero (0) and 100 (both inclusive) is a valid value. The default is Yes.

select the Send Email option from the Create Price Book page. up to a total of 20 decimal places. Quarterly. The profile option is seeded with the value 'Period'. The QP: Unit Price Precision profile controls how many decimal points you can use on a Price List for a rounding factor. When the price book is e-mailed.From Address. The domain is a UOM class in Inventory. The default value is Blank. enter the return e-mail address such as joe. The default return e-mail address is used only when e-mailing from the price book feature not from a different e-mail application such as Outlook. To set the return e-mail address. Weekly. Inventory has seeded a UOM class called 'Period' that will hold UOMs: Daily. OM: UOM Class for Charge Periodic This profile option determines what domain will be used to hold the allowable charge periodicities.From Address to specify the From Email Address for any e-mails that are sent from the price book feature. * Extended: You see at least five decimal places.smith@vision. Note: To send the price book via e-mail. Monthly.com in the profile option QP: E-mail . Yearly and so on. Monthly. This serves as the return address when a price book is e-mailed from the price book feature. This profile option is visible and can be updated at the site and user level. Values You can enter any valid e-mail address.* Standard: You will see at least two decimal places. *QP: External Default Pricing Perspective . the recipient can identify the sender and respond to the sender's return e-mail address. Oracle Advanced Pricing Profile Options *New Profiles With R12 *QP: E-mail . ***Important*** Publishing a price book to a printer or as an e-mail attachment is dependent on the availability of the Delivery Manager Component of the Oracle XML Publisher (XDO) product. Inventory has further seeded a value set INV_CHARGE_PERIODICITY that will hold UOMs: Weekly. You need to set up the profile option QP: E-mail .From Address This profile option defines the sender's e-mail address when a price book is e-mailed from the price book feature. Quarterly and so on. up to a total of 20 decimal places.

The default value is Order Management. An external user cannot view the Pricing Perspective field or change its value. This profile option is used by the price book feature to set the responsibility context for an inbound XML message request for a price book. Note: External users cannot view or change the Pricing Perspective field. for example. This profile option is used for the price book feature and defines the mapping between the Pricing Perspective and Request Type. The value Purchasing is valid for internal users but not external users. Values The following lists the values for the request type to pricing perspective mappings: Complex Maintenance Repair and Overhaul: Complex CMRO . an internal user can override this value by selecting a different pricing perspective. The default value is Blank. Default at the site level is Order Management Order. A value must be assigned to this profile before you can select the Party Hierarchy Enabled check box for TCA Party qualifier attributes. The default value is Order Management *QP: Pricing Party Hierarchy Type This profile option specifies the hierarchical party relationship type from Trading Community Architecture (TCA) to be used in pricing. Each relevant (valid pricing perspective) application level has a different default. This value defaults to the Pricing Perspective field in the Create Price Book page. However.This profile option is used for the price book feature and sets the default pricing perspective for all external users. an internal user can override the defaulted value by selecting a different pricing perspective. The default value is None. *QP: Pricing Perspective Request Type Note: For each application. a Get Catalog XML message. The following is a list of seeded TCA Party attributes: Customer Party (qualifier context = Party Information (ASOPARTYINFO) Party Id (qualifier context = Customer (CUSTOMER) Buying Groups (qualifier context = Customer Group (CUSTOMER GROUP) Supplier (qualifier context = Party Information (PARTY) Buyer (qualifier context = Party Information (PARTY) It can be set at the Site level. however. These values can be applications such as Oracle Order Management and Oracle Purchasing that request information from the pricing application. It can be set only at the System Administrator (SA) Application level and by the user. Note: Oracle Advanced Pricing is not one of the valid values for this profile option. Note: The Application corresponds to the pricing perspective of the price book request. It can be set at SA Site and SA Application levels. This value defaults to the Pricing Perspective field in the Create Price Book page. there is a separate default value. *QP: Internal Default Pricing Perspective Sets the default value for the pricing perspective for all internal users using the price book feature. *QP: Inbound XML Messaging Responsibility This profile option defines the responsibility (at the Application or User level) for inbound XML messages.

Order Capture: Order Capture Transportation Execution: Oracle Transportation Shipment Inventory: Inter Company Invoicing Demand Planning: Demand Planning Contracts Core: Oracle Contracts Service Contracts: Oracle Contracts for Service Order Management: Order Management Order Purchasing: Purchase Order The default value is Order Management Order. To use the accumulation attribute feature. QP: Accrual UOM Class This is required if your business gives non-monetary accruals as benefits. Values All UOM classes defined to Oracle Applications. The profile option also enables the Accumulation Attribute field in the Price Breaks tab on the Define Modifier window. The default value is Null. The Modifier Setup window displays all units of measure in this class when entering the Benefit UOM for an accrual. QP: Accumulation Attributes Enabled Default value: No This profile option enables the use of accumulation attributes for modifiers. No:: Cannot use the accumulation attribute feature. QP: Administer Public Queries 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. Specifies the unit of measure class to be used for defining accrual units of measure. Values Yes: Enables the use of accumulation attributes for modifiers. The value of the accumulation attribute is sourced from the pricing request when evaluating accumulated range price breaks for modifiers. This profile option is visible and can be updated at site and application levels. QP: Allow Buckets for Manual Modifiers . the profile QP: Accumulation Attributes Enabled must be set to Yes. This profile option can be set at the Site and/or Application level. No:: Queries saved in Public folders cannot be deleted or renamed. Values Yes: Enables queries saved in Public folders to be deleted or renamed. The Accumulation Attribute field in the Price Breaks tab does not display in the Define Modifier window.

Note: Advanced Pricing allows duplicate modifier lines within a modifier list. This profile option is visible and can be updated at the site level. If the profile value is changed from Yes to No and there are manual modifiers defined with buckets. No:: You cannot define buckets for manual line or group of line level modifiers. If set to Yes (the default). The pricing engine will return the manual bucketed adjustment even if the profile is set to No. Values Yes: Enables you to define buckets for manual line or group of line level modifiers. the manual modifiers defined with buckets need to be end-dated or deactivated. Page 1-21 Enhancement Request Bug 5629486 has been logged to request similar functionality that may be enabled in Advanced Pricing as desired. A modifier line is considered a duplicate if any of the following attributes of the original and duplicated line match within the same modifier list: List Line Start Date Active List Line End Date Active (Lines with overlapping dates are considered duplicates) Modifier Level Code (Order/Line) Automatic Flag (Selected/Cleared) Product UOM code Product Attribute Product Attribute Value Pricing Attributes Set of Qualifiers Values * Yes: Duplicate modifiers can be copied within the same modifier list for Basic Pricing. B31440-01. which is typically set by the System Administrator. The profile option QP: Allow Duplicate Modifiers. This profile option is set at the site level. If set to No. QP: Allow Duplicate Modifiers Default Value: Yes Used by Basic Pricing Only. Reference:Oracle Advanced Pricing Implementation Manual Release 12 Part No. * No: Duplicate modifiers cannot be copied within the same modifier list for Basic Pricing. you must change the new modifier line before you can save it. determines if duplicate modifiers are permitted. QP: Batch Size for Bulk Import .Default Value: No This profile option enables you to define buckets for manual line or group of line level modifiers. an existing modifier can be duplicated.

the system may "hang" if the profile value is set too high. This profile option can be updated at the site and application levels. * Map all attributes: This program will source the attributes that are used in both . however. which bypasses part of the search engine processing. This profile option is visible and can be updated at the site and application levels. * No: The pricing engine does not prorate the break ranges before evaluating which break is satisfied. QP: Build Attributes Mapping Options Default value: No This profile option enables you to set attribute mapping rules for attributes in both the active and inactive setups. Setting an appropriate value for this profile based on hardware configuration improves performance. A blind discount is defined as a modifier that has all of the following: No list qualifiers on the modifier list header No line qualifiers on the modifier No products or pricing attributes Note: If your business must define a modifier as previously described. bypass blind discount processing in search engine. * No: Blind discounts are disabled. Values * Yes: The pricing engine prorates the break ranges before evaluating which break is satisfied. QP: Blind Discount Option Default value: Yes The default value for this profile option should only be changed if you never define blind discounts. set this profile option to No. verify that this profile option is set to Yes.Default value: 1000 This profile option value determines the number of records loaded into the memory for bulk import processing. the modifiers will not be selected by the search engine Note 435422. Values * Map attributes used in active pricing setup: The Build Attribute Mapping Rules concurrent program will source the attributes that are used only in the active pricing setup. If this is not done. This profile is useful for service usage pricing engine calls. If you never define blind discounts.1 . QP: Break UOM Proration Allowed Default value: Blank This profile option controls whether break ranges for price lists need to be prorated or not.How to Identify Blind Modifiers and Make Changes to Setup for Improving Performance Values * Yes: Blind discounts are enabled.

the timings sqlsare not executed. nothing is written into pricing debug tables and debug log table.1 Oracle Advanced Pricing Whitepapers. If not set. The debug log text file is also created. show Diagnostic details in Trace: Some pricing timings sql are controlled by this value. * Request Viewer Off.5. When set to "Request Viewer Off. under Note 136687. the Request Viewer captures pricing request details into the pricing debug tables and debug log information into the debug log table. * Request Viewer On. QP: Debug Default value: Request Viewer Off Value * Request Viewer On: When set to on. Please refer to the white paper. as an enhancement to Oracle Advanced Pricing functionality." the pricing timing sqls are executed. . but Debug Log is not visible in Viewer: When this is set. Default value is NULL which is similar to value 'Yes' QP: Custom Ignore Pricing This is a new profile option added in mid 2009.the active and inactive setups. Performance will improve if you do not use manual modifiers nor manual freight charges assigned to level = group of lines and this profile is set to Yes. The debug log text file will not be created. This enhancement is released as a part of 11. Value 'Yes'-. show Diagnostic details in Trace. * Request Viewer Off: When set to off. Value 'No'-. The debuglog text file will be created. QP: Consider Manual Linegroup Adjustments This is a new profile added through patch 8642882.Line group modifiers will not be considered for manual modifier pricing engine call. the Request Viewer captures pricing request details into the pricing debug tables. This profile option is to ignore group of lines modifiers while making pricing engine call for getting manual modifiers.Line group modifiers will be considered for manual modifier pricing engine call. It will impact selection of manual modifiers and selecting of manual freight charges. The motive of this enhancement is driven by the performance gain that is desired by the users if the majority of the order lines are not significant to pricing and can carry a zero price. Titled "Ignore Pricing for Order Lines .10 and R12 releases of Oracle Applications.but debug log information is not written into the debug log table.Custom Hook".

Value * Always expressed in days. This value must not be the same as the value in QP: Cross Order Volume Period 1 or QP: Cross Order Volume Period 3. Additional references: Note 604550. . This profile option is visible and can be updated at the site and application level. On encountering performance issues on RDBMS 10G database. This will execute the queries using GTT(Global Temporary Tables) efficiently. this profile value should be set to 'Dynamic Sampling Level 1'. the Request Name field will be prefixed with the Order ID. Values * Always expressed in days.QPXPRMLS: Performance Updating Modifier W/65k Qualifiers For Field "End Date" is Poor.Note: The profile option. QP: Cross Order Volume Period2 Default value: Blank This is required if you will be running the cross order volume load program. for details on this profile option. 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.1 .Clarification about the "QP: Debug" profile option QP: Denormalize Qualifiers This is a new profile option added at the end of 2008. This profile option is visible and can be updated at the site level. This profile has been added to assist with performance when updating a modifier with thousands of qualifiers. QP: Set Request Name can be used in conjunction with the QP: Debug profile option. Valid values are Yes or No.1 . When the QP: Set Request Name is set to Yes. This defines the number of days of order lines that the load program will accumulate and total. Reference Note 552468. QP: Cross Order Volume Period1 Default value: Blank This is required if you will be running the cross order volume load program. Due to this queries using Global Temporary tables were very expensive in RDBMS 10G. This defines the number of days of order lines that the load program will accumulate and total. QP: Dynamic Sampling Level This is a new profile added through patch 7293628 In 10G database the default Dynamic Sampling Level is 2 by default while in 9i it was level 1. This value must not be the same as the value in QP: Cross Order Volume Period 2 or QP: Cross Order Volume Period 3.

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. Oracle Advanced Pricing provides a function called Get_Custom_Price with a standard set of input parameters. the pricing engine evaluates the line type function. 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. This defines the number of days of order lines that the load program will accumulate and total. If your organization wants to use this formula line type. QP: Custom Sourced Default Value: No Value * Yes: When this profile is set to Yes. the user must set up a formula with a line type of function (the formula may or may not . This profile option is visible and can be updated at the site level. * Set this profile option to Yes. that the pricing engine evaluates the line type function. This profile is required if your business needs more pricing formulas than are provided in basic pricing. To use the customized Get_Custom_Price functionâ  s return value in a formula. the pricing engine does not evaluate the line type function. * No: When this profile is set to No. Value * This value is always expressed in days.QP: Cross Order Volume Period3 Default value: Blank This is required if you run the cross order volume load program. * No:: When processing formulas. The value returned by the Get_Custom_Price function can be used in a formula expression. This value must not be the same as the value in QP: Cross Order Volume Period 1 or QP: Cross Order Volume Period 2. QP: Get Custom Price Customized Default value: No This profile option indicates. 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. This profile option can only be updated at the site level. Values * Yes: When processing formulas. you must: * Customize the GET_CUSTOM_PRICE function. 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. when processing formulas. the Build Contexts program builds the contexts only from the dynamic package generated by the Build Attribute Mapping Rules program. This profile option must be set as Yes if the package body for QP_ CUSTOM is coded.

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. HVOP is still supported. 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. Example 2 Consider the following set up: . QP: High Volume Order Processing Compliance Default value: Blank This profile option indicates if the pricing setup is compliant with the optimized pricing path when High Volume Order Processing Compliance (HVOP) is used.999999999999â ¦the number will be rounded to 1YR. which indicates that HVOP takes the optimized path which improves the performance. QP: Inventory Decimal Precision Default value: 10 Used to set maximum decimal precision for uom conversion when calculating pricing quantity. the step values are not inserted into the temporary table described above. Example 1 Consider the following set up: * Primary UOM = YR (year) * Order UOM = MTH (month) * Order Quantity = 12 The pricing engine rounds the pricing quantity based on the decimal precision setting. but the pricing is not optimized: * Coupon Issue modifier * Item Upgrade modifier * Promotional Goods modifier * Promotional limits * Terms Substitution modifier For more information on HVOP. If not set. If the default precision is 10 digits. It can be set only at the site level using the System Administrator responsibility. it is defaulted to 10 digits decimal precision. This can be referenced by customized code. Values * Yes: If no active modifiers of the preceding type are found in the pricing setup. see Overview of High Volume Order Processing (HVOP) in the Pricing Implementation Manual. this profile will have a value Yes. then the resulting pricing quantity will be 12 * (1/12) = 0. * No:: If set to No.have other formula lines). Values * Yes: If set to Yes. QP: Insert Formula Step Values into Temp Table Default value: No This profile option can be set only at the site level using the System Administrator responsibility. * No: If any of the following modifiers or features are active in the pricing setup.

you must be licensed to use Oracle Pricing and set the value of this profile to PO (Oracle Procurement). QP: Licensed for Product Default value: Blank This profile option identifies which Oracle software application can use Oracle Pricing. you need to set up values for: HR: Security profile HR: Business Group profile options Valid inventory master organizations will be available based on values of HRMS profile settings. to an organization at the level in your organization hierarchy at which you set prices for items. For example. Values * The value of this profile need to be set to the Oracle Application which is planning to use Oracle Pricing.* Primary UOM = DZ * Order UOM = EA * Order Quantity = 16 The pricing engine rounds the pricing quantity based on the decimal precision setting. Values This profile option is visible and can be updated at the site and responsibility levels Note: Before setting this profile option. then the resulting pricing quantity is calculated as follows: 16 * (1/12) = 1. This profile option can be updated at the application and user levels. to use Oracle Pricing for Oracle Procurement applications.333333 DZ. please refer to Note 460458. If a user sets the Profile QP: Inventory Decimal Precision to 6 digits. by site or responsibility. For more information on these profiles. . Can Not Update Profile Option Qp: Licensed For Product? If so.33333333333333â ¦ which is rounded to 1. see: Configuring. The value can be set after you buy the license to use Oracle Pricing along with other Oracle Applications.1 QP: Limit Exceed Action 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. QP: Item Validation Organization Default value: None Set this profile. Reporting and System Administration in Oracle HRMS. Security chapter.

QP: Line Weight UOM Code Default value: Blank This profile option specifies the unit of measure for the line weight qualifier. and then uses the weight attributes of the item to derive the line weight of the item in the UOM specified in this profile option. The attribute sourcing API converts the item on the request line to its primary UOM. The calculation of Order Volume: Each order line will be converted into the line volume (order_quantity * uom_conversion_rate) and the line volumes will be totaled to get the Order Volume. Values All units of measure currently defined to Oracle. must be set to the correct volume uom code. Values * Soft--Full Benefit Amount: Applies the full benefit to the order even if the transaction exceeds the defined limit. there must be a conversion set up from Ea to CBM for the item. In order to use this qualifier the following must be set up: a. This profile option specifies the unit of measure of the line volume qualifier. QP: Line Volume UOM Code Default value: Blank Required if your business must define qualifier rules which include the seeded qualifier line volume. The profile. The profile QP: Line Weight UOM Code must be set to the correct weight uom code. then uses the volume attributes of the item to derive the line volume of the item in the UOM specified in the profile option. This profile option is visible and can be updated at the site and application levels. QP: Line Volume UOM Code. This is required if your business needs to define qualifier rules which includes the seeded qualifier line weight. . * Hard--Adjust Benefit Amount: Adjusts the order benefit amount so that the order meets but does not exceed the promotional limit. A uom conversion must be set up to convert from the ordered_uom for each order line to the weight uom specified in the profile. This uom code is the uom for the total order weight. For example. The attribute sourcing API converts the item on the request line to its primary UOM. there must be a conversion set up from KGM to LBS for the item. if line 1 of your order is in KGM and the profile is set to LBS. This profile option is visible and can be updated site level using the System Administrator responsibility. Order Volume: The Order Weight qualifier is calculated as the total volume of all the order lines for the order. A status message is sent to the calling application such as Order Management to place a promotional hold on the order. b. For example if line 1 of your order is in Ea and the profile is set to CBM. This uom code is the uom for the total order volume. In order to use this qualifier the following must be set up: 1. There must be a uom conversion set up to convert from the ordered_uom for each order line to the volume uom specified in the profile. 2. The Order Weight qualifier is calculated as the total weight of all the order lines for the order.This profile option is based on the lookup type Limit Exceed Action.

Warning: For Multi-Currency Installed Once the concurrent program has been run successfully. the modifier Find Window does not display. the incoming pricing request will send order currency.How order weight is calculated: Each order line will be converted into the line weight (order_quantity * uom_conversion_rate) and the line weights will be totaled to get the Order Weight. This profile option is visible and can be updated at the site and application level. QP: Multi Currency Usage . pricing date. QP: Modifier Find Window . otherwise. you would use the Pricing Organizer feature to find modifiers and modifier information. This profile option is visible and can be updated at the site and application levels. Values * Yes: If the profile QP: Multi-Currency-Installed is Yes. Changing the profile option back to No may cause undesired results if conversion criteria have been used. the concurrent program Update Price Lists with Multi-Currency Conversion Criteria must be run to enable the price list windows for multi-currency usage. pricing attributes and qualifier attributes. all existing price list and agreement windows are converted to multi-currency price lists. the multi-currency feature enables you to maintain a single price list for multiple currencies. Values * Yes: Enables you to use modifier Find window. product attributes. * No: When set to No. The program must be run initially only once to activate the multi-currency feature. 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. Once the profile option is set to Yes. data corruption may result. QP: Multi-Currency Installed Default value: No If you have global customers or do pricing in different currencies. the order currency is matched with the price list base currency. Oracle does not support changing the setting back to No. the Pricing Organizer window displays. However. typically.Show records Default value: No This profile option enables you to use a Find window in the Modifiers window to query modifier records. which is the current behavior. Values All units of measure currently defined to Oracle. Instead. Users should not return to NON multi-currency price lists. This is similar to the Line Weight qualifier setup.

the following occurs: * No limit is imposed on the number of places that can be entered on the price list . and displays the list price based on the profile option setting. * No: If selected. the following list prices display: 115. Controls whether a negative price can be entered in the Price List setup window. Also.24000 9. while currency precision determines the displayed list price. stores. An error message only displays when you try to save the price list. then the value in the Round To field in the Advanced Pricing . responsibility and application levels. * No: Does not allow a negative price to be entered.23000 100. you will be unable to save the price list. The Advanced Pricing . Values * Yes: Allows a negative price to be entered. QP: Pass Qualifiers to Get_Custom_Price API Default value: Blank Values * Yes: If selected.00000 If the QP: Price Rounding profile option is set to Enforce Currency Precision. The value entered in the Round To field from the price list is used to store the rounded value. not when you first enter the list price. Values Blank (Default): If this option is selected. if the Round To value is -2 and the currency precision is -5.Price Lists window cannot be updated. then only the qualifiers are passed to Get_Custom_Price. For example. This profile option can be updated at the site. qualifiers will not be passed to Get_Custom_Price.Price Lists window rounds. Warning: When QP: Price Rounding profile option is set to Enforce Currency Precision If the QP: Price Rounding profile option is set to Enforce Currency Precision and you enter a list price greater than the precision amount allows. * No: Do not use multi currency price lists. This profile option is visible and can be updated at the site and application levels. Values * Yes: Enables an application to use multi-currency price lists. QP: Negative Pricing Default value: No The default value should only be changed if your business needs to define a negative price on a price list line.Default value: Blank This profile option determines if the calling application can use multi-currency price lists. QP: Price Rounding Default value: Blank This profile option controls how the value for the rounding factor is derived and used in price lists and related windows. the values permitted for the rounding factor will be limited to the price list currency precision.

Note: The currency precision setting determines the display of the list price. * Static formula calculation results will not be rounded.after the decimal point. * Calculating the results for static formula calculations. the calling application passes the rounding factor and the resulting rounding factor displays regardless of the profile setting. * The value for a price list line is not rounded. the calling application passes the rounding factor and the resulting rounding factor displays regardless of the profile setting. Adjust Price List The list price. * The Round To can not be modified if profile option QP:Price Rounding is set to Enforce Currency Precision. Add Items to Price List The list price will be rounded and stored using Rounding Factor if the profile option QP:Price Rounding is set to Enforce Rounding Factor or Enforce Currency Precision and Set List Price Equal to Cost From is checked on the window. Enforce Price List Rounding Factor: If this option is selected. Rounding Behavior The profile option settings for QP: Price Rounding affect the rounding behavior as described below: Formula Prices For dynamic formulas. * Rounding the pricing engine calculation results. The decimal places that display for the list price is determined by the Currency Precision. the Rounding Factor field on the price list cannot be updated by the user. * The Round To value specified for the price list rounds the pricing engine results. Instead the Rounding Factor value defaults from the profile QP: Unit Price Precision Type (either Standard/Extended precision) for the price list currency.Price Lists window is used for: * Rounding the value on the price list line. after adjustment by amount or percent. * The list price that displays will not be rounded by either Currency Precision or the Round To value. Price List * The Round To value is used to round and store the list price if the profile option QP:Price Rounding is set to Enforce Rounding Factor or Enforce Currency Precision. Enforce Currency Precision: If selected. the value entered in the Round To field of the Advanced Pricing . Formula Prices: For dynamic formulas. will be rounded and stored using Rounding Factor if the profile option QP:Price Rounding is set to Enforce Rounding Factor or Enforce Currency Precision. Update Formula Prices . * Currency Precision is used to display the list price if profile option QP:Price Rounding is set to Enforce Rounding Factor or Enforce Currency Precision.

* No: Disables the promotional limits features. * Currency Precision displays the list price if the profile option QP:Price Rounding is set to Enforce Rounding Factor or Enforce Currency Precision. Other users can view the profile only. Additional References: Note 578687. you will see the internal ID code.. and user levels. and qualifiers. * The Round To cannot be modified if the profile option QP:Price Rounding is set to Enforce Currency Precision. etc. QP: Promotional Limits Installed 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. Values * Yes: Enables the promotional limits features to be used. This profile can be set at the site. If this happens. modifiers. Warning: Once the QP: Promotional Limits Installed profile option is enabled . will cause the description to be shown only for those contexts and attributes that are assigned to the current Pricing Transaction Entity. application. The System Administrator must change this value to Y for Yes to be able to use limits. Only those contexts and attributes assigned to the current Pricing Transaction Entity will be available in the list of values on the setup forms. Therefore it is important to set this profile option to the correct value before creating or querying any setup data in the Pricing Application. It is not a good idea to changes this profile often as you will see the other context-attributes combinations for a different PTE when querying on the pricing setup forms.Range Price Break Does Not Calculate Price Correctly Due to Rounding Precision QP: Pricing Transaction Entity Default value: Order Fulfillment This profile option indicates the current Pricing Transaction Entity (PTE) in use. Values The valid values for this profile are all the Pricing Transaction Entities that belong to QP Lookup type QP_PTE_TYPE. Agreement The Round To is used to round and store the list price if the profile option QP:Price Rounding is set to Enforce Rounding Factor or Enforce Currency Precision.1 .The list price will be rounded and stored using Round To if the profile option QP:Price Rounding is set to Enforce Rounding Factor or Enforce Currency Precision. Only the System Administrator can change the value of this profile at site and application levels only. querying up setup data for price list lines. Likewise. The initial default value is N for No which means the limit feature is not active.

QP: Return Manual Discounts Default value: No 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. If the Manual Discount Flag box is selected. this indicates that the QP: Return Manual Discounts is set to Yes. each for a product family with a qualifier that identifies the distributor by name or type. then the list of values (LOV) will show both Manual_1 and Manual 2. In the Pricing Engine Request Viewer window. the Manual Discount Flag box reflects the setting of the profile QP: Return Manual Discounts. This means that one automatic discount is applied. It determines if a price list item from a non-validated line can be selected from the related secondary price list. you can have a single parent price list with multiple secondary price lists. Without qualifiers being checked on secondary lists. suppose you have distributors who can only buy certain product families. When QP: Return Manual Discounts = No. and all manual discounts are returned for user selection. The following modifiers types can be manual: * Discounts * Surcharges * Price break lines * Freight Charges Manual adjustments can be overridden. Values * Yes: Qualifiers for the secondary price list are evaluated by the pricing engine when the primary price list is not validated. * No: Secondary price lists will not be checked for qualifiers when the primary price list is not validated. Do not disable the QP: Promotional Limits Installed profile option once it has been enabled! QP: Qualify Secondary Price Lists Default value: Yes This profile option enables secondary price lists to be checked for qualifiers when the primary price list is not validated. so that users can choose adjustments to be applied on the order line. Y is the default and should not be changed. With this profile change. Values * Yes: In basic pricing. then the LOV will show Manual_1 since it has the highest precedence (determined by the lower precedence number). assume the following setup: Modifier Name Incompatibility Level Precedence Manual_1 Incompatibility 1 100 Manual_2 Incompatibility 1 200 When QP: Return Manual Discounts = Yes.Leave the promotional limits active with the value of Y. For example. For example. All the automatic discounts that are deleted as part of incompatibility processing return as manual discounts available for user selection All unapplied manual . The profile option settings determine which modifier is evaluated by the pricing engine. you must create one price list for each possible combination of product family.

each newly created price list and modifier form will be assigned a unique system-generated operating unit identifier. Oracle Advanced Pricing Implementation Manual Values * Off: After initial upgrading to security. . one should review and complete the required setup steps for implementing pricing security. pricing users may be unable to query any price lists or modifiers in the pricing windows. All functional users require access privileges to view or maintain their pricing entities. the QP: Security Control is set to Off which maintains the pre-upgrade functionality. When the profile QP: Security Control is turned on. Warning: For Oracle Applications Release 12 and Security Control BEFORE turning on pricing security. QP: Security Control Default value: Off This profile option controls the activation of the pricing security feature for your entire installation. It controls whether satisfied qualifiers are returned to the calling application or not. Do not change profile QP: Security Control manually. This means any user with functional access to the Pricing Manager responsibility has full access to maintain and update all pricing entities regardless of operating unit. see: Pricing Security. * On: The Security Control profile should not be turned on until all mapping has been completed. Before turning this profile option on. * No: All automatic and manual discounts run through incompatibility processing and one from each incompatibility group is returned. otherwise. It can be set On or Off.discounts are returned and all automatic discounts not considered are returned as manual discount. For more information. An automatic discount may be deleted and a manual discount may be selected. This increases pricing engine processing time. Chapter 5 Pricing Security for detailed steps. Discounts (automatic or manual) deleted as part of incompatibility processing are not returned as manual discounts. Values * Yes: The pricing engine returns all the satisfied qualifiers to the calling application. Discounts (automatic or manual) deleted as part of incompatibility processing will not be returned as manual discounts. Refer to the Oracle® Advanced Pricing Implementation Guide. QP: Satisfied Qualifiers Option Default value: Yes The profile option QP: Satisfied Qualifiers Option influences performance when entering and booking an order. ensure that you have completed all the set up and implementation steps. The Pricing Engine does not consider applied manual modifiers during incompatibility processing. * No: Processing time is reduced because the pricing engine does not return the satisfied qualifiers to the calling applications. but run the concurrent program: Security Control to change the security profile's value.

This controls which users (if any) have access to view specific price lists and modifiers. Responsibility. This controls which users (if any) have access to maintain specific price lists and modifiers.Security Control 4) Pass the Parameter security control on. User. Responsibility. QP: Security Default ViewOnly Privilege Default value: Global This profile option determines the default view-only privileges for NEWLY CREATED price lists and modifiers after security is turned on. This setting shows on the Diagnostics: Apps Check Report as NO_ROUND_ADJ Freight Charge Rounding: If the QP: Selling Price Rounding Options profile is set . then the maintain privileges for that price list or modifier are restricted to the operating unit where the price list or modifier was created. Values * Global. or None. User. View and maintain responsibilities are controlled separately by different profile options. * Additive: Selling Price = round(listprice + adjustments). For example. if the profile option is set to Operating Unit.1) Responsibility = Oracle Pricing Administrator 2) Navigate to: Run Requests. View and maintain responsibilities are controlled separately by different profile options. 5) Submit the Request. Values * Global. This setting shows on the Diagnostics: Apps Check Report as ROUND_ADJ. Values * No Rounding: Selling Price = unrounded listprice + unrounded adjustments: No rounding. Operating Unit. QP: Selling Price Rounding Options Default value: Individual: = round(listprice) + round(adj) This rounding option rounds the selling price after adding unrounded list price and adjustments: selling price = round (list price + adjustments This profile option can be viewed and updated at the site level. or None. QP: Security Default Maintain Privilege Default value: Global This profile option controls the default maintain privileges for NEWLY CREATED price lists and modifiers after security is turned on. 3) Program . * Individual: Selling Price = round(listprice) + round(adjustments): Rounds the selling price and adjustments. Operating Unit. unrounded Freight: Rounds the selling price after adding unrounded list price and adjustments.

If the profile is set to INDIVIDUAL then freight charges will be rounded. * Q: Behavior depends on the profile setting for QP: Selling Price Rounding (NO.1 for Rounding with Pricing . INDIVIDUAL. . then no specific setup is required. but QP: Selling Price Rounding Options is NULL. In this case. Order Management. ADDITIVE). or deleting modifier lines. to differentiate between applications and prevent update of modifiers among several applications. Values * Any valid values such as the Name or User ID of the user submitting the price request. This profile option can be updated at the site and responsibility levels. If rounding flag is passed as Q. all modifiers are created with same value for source system code (assuming the value of this profile is set only at site level by default or same value if set for all applications which create modifiers). the default behavior is no rounding. pricing attributes. responsibility. If you do not want to differentiate between applications or prevent update of modifiers created by different applications.to NO or ADDITIVE then freight charges will not be rounded. If modifiers are created in different applications such as Oracle Advanced Pricing. the value of this profile can be set up at the Application level. * Null: Rounds selling price and adjustments Refer to Note 466505. Set QP: Set Request Name to Yes if you want the value in the Request Name field prefixed to the OrderID. Values QP: Oracle Pricing (and other source system lookup codes of related applications). or Trade Management. The QP: Set Request Name profile option is visible and can be updated at the site.Frequently Asked Questions QP: Set Request Name Default value: Blank This profile option is used in conjunction with the QP: Debug profile option. This source system code is held on all price and modifier lists to identify the origin of the data. By default. the pricing engine may restrict its search to pricing information which originated from a particular application depending on the request type to source system setup. QP: Source System Code Default value: Oracle Pricing This profile option is used in all pricing setup windows to identify the application through which the pricing information is being entered. then changes to the modifier can only be made in the application where the modifier was originally created. At the time of pricing. * N (No): No rounding. The rounding flag in the control record passed by calling application may have one of the following values: * Y (Yes): Rounds selling price and adjustments. the value of the profile option QP_SOURCE_SYSTEM_CODE is QP (Oracle Pricing) at the Site level. updating. However. and qualifiers. application. and user levels. These changes include changes to the modifier header (as deleting is already prevented) or changes such as inserting.

suppose that in a price list.) If an order line is entered with the unit of measure as Dozen. 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 QP: Unit Price Precision Type Default value: Standard This profile option determines the Round To value that is defaulted on the price list. When the QP: Time UOM Conversion profile is set to Oracle Contracts. Since days are set as the base UOM. (Responsibility: Service Contracts Manager or Corporate Contracts Manager). then the updated value is applied only to new price lists but not existing price lists. * Oracle Contracts: When set to Oracle Contracts.16666666666666666666666667 months. For Oracle Contracts. confirm that the UOM conversion for month = 730. Advanced Pricing uses the inventory UOM conversion APIs. This result is obtained by dividing 365 days by 30 days rather than one year being converted to 12 months. pricing takes the duration into consideration but converts the hours for 12 months to be 12. confirm the setup in Oracle Contracts: SetUp > Contract > UOM > UOM Classes > Unit of Measure Classes > select Time. For example. the pricing engine use the APIs provided by Oracle Contracts to convert the date and time. one year is converted to 12. Otherwise. . the following values from each request line processed need to be passed by the calling applications (such as Order Management.016667 hours * Month = 730 Hours * Quarter = 2190 Hours * Week = 168 Hours * Year = 8760 Hours Values * Standard: When set to Standard. the UOM selected is EA (each) and that the Primary UOM box is selected. the duration is not considered in the pricing.QP: Time UOM Conversion 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. Note: If you update either the extended or standard precision value for a currency. To do the conversion. 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. If the Oracle Contracts API does the uom conversion. if the price list does not calculate correctly when the Period type = Year. the existing method of passing the uom quantity to the pricing engine API can be used by the calling applications. As for time periods.16666â ¦ months by the inventory uom APIs. (The primary uom in the price list could be different from the primary uom set in Oracle Inventory for the item. when the QP: Time UOM Conversion profile is set to Standard. To confirm that month = 730. the inventory UOM conversion uses a static conversion factor of 30 days per month. The following is an example of the Unit of Measure Conversions you may have set up for Time: * Day = 24 Hours * Hour = 1 Hour * Minute = . The rounding factor is limited by the number of positions allowed in the standard or extended precision format of the price list currency.

* Standard: Rounding factor defaults to the currencyâ  s standard precision. Responsibility = System Administrator (One must use this responsibility). and user levels. responsibility. price lists. you can enter search criteria. and modifiers. 1. Review the setup for the currency used on the price list to ensure the extended precision is large enough to include the value desired for the round to factor on the price list Responsibility: General Ledger Super User Navigate to: setup > currencies > define Query the currency that is on the price list Ensure that the extended precision is set to an appropriate value. * No: The message does not display. Retest the issue. This profile option is visible and can be updated at the site.Values * Extended: Rounding factor defaults to the currencyâ  s extended precision. If you want to reduce the number of items that display in the list of values. . Navigate to: profile > system Query QP: Unit Precision Type from this form for both site and for the Application = Oracle Order Management. Migrate the solution as appropriate to other environments QP: Valueset Lookup Filter Default value: Yes Use this profile option to enable or disable a search criteria window for qualifier value lookups in qualifiers. Responsibility: general ledger super user Navigate to: setup > currencies > define Query the multi-currency conversion that is on the price list Make sure that the Base Round to is set to the value you plan on using in the price list. Values * Yes: The message displays. 3. application. 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. Some qualifiers use large valuesets. 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. for example. Please set the value to Extended and save. review the Base Round To in the Multi-Currency Conversion. If 'Multi-Currency Conversion Setup' is used on the price list. Set profile QP: Unit Price Precision Type = Extended at both site and the Order Management application level. 2. and searches may take a long time. This profile option can be updated at the site and application levels. 5. Take the following actions if one cannot update the round to factor on a Price List. 4. those based on all customers.

FNDPOMSV: Can Not Update Profile Option Qp: Licensed For Product Related Products y Oracle E-Business Suite > Order Management > Price Management > Oracle Advanced Pricing y Oracle E-Business Suite > Order Management > Price Management > Oracle Advanced Pricing Keywords ADJUSTMENT. Values * Yes: Pricing engine tests for GSA violations. see Oracle Applications System Administrator's Guide. ADVANCED PRICING.1 Oracle Applications Documentation References NOTE:435422. and 2) GSA rules are violated if the selling price of an item is calculated to be less than the price of the item on any GSA price list. PROFILE. application.How to Identify Blind Modifiers and Make Changes to Setup for Improving Performance NOTE:460458. and user levels. PRICING. * No: Does not test for GSA violations. This profile option can be updated at the site. responsibility. You can change the value to Yes if you require GSA pricing functionality. and any violating request lines are returned to the calling application with GSA violation status.1 .1 . PERSONAL PROFILES. The evaluation is performed if: 1) a request is for a non-GSA customer.QP: Verify GSA Violations Default value: No This profile option indicates whether the pricing calculation engine should test for GSA violations. Additional References: For more information on setting profile options. and Oracle Advanced Pricing Implementation Guide. PROFILE OPTION VALUE. Note 790942. ORDERED QUANTITY. setting User Profile Options. Profile Options. QUANTITY .

Sign up to vote on this title
UsefulNot useful