om pricing setup

Upload: raje0303

Post on 07-Apr-2018

215 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/3/2019 OM Pricing Setup

    1/6

    Step 1: Perform System Administration Steps

    Default: None

    Assign users who set up Oracle Advanced Pricing to the Oracle Pricing Manager

    responsibility.

    Step 2: Set Profile Options

    Required

    You set a value for each user profile option to specify how Oracle Advanced Pricing controls

    access to and processes data.

    Step 3: Set Multi-Currency Profile Options

    Default: None

    The profile option QP: Multi-Currency Installed enables the multi-currency price list feature.

    Multi Currency Price Lists enables you to maintain a single price list for multiple currencies.

    Step 4: Perform System Sourcing

    Default: Predefined Oracle Advanced Pricing record

    This step is required if:

    Your pricing data application source is anything other than Oracle Advanced Pricing.

    You are integrating Oracle Advanced Pricing with an application other than Oracle Order

    Management.

    Warning: Changing the system source code can severely affect pricing engine behavior.

    Step 5: Verify or Create PTE

    Default: Order Fulfillment

    Required

    A Pricing Transaction Entity (PTE) is an ordering structure that has associated Request

    Types and Source Systems. Request Types and Source Systems in the same PTE share

    pricing setup data. Additional Source System and Request Types can be added to existing

    PTE's.

    There are very rare instances where it is necessary to create a new PTE. A new PTE needs

    to be created only if the new request type uses a different ordering structure and a different

    set of source systems that is not already predefined.

    Step 6: Create Qualifier Contexts and Qualifier Attributes

    Default: Predefined Oracle Advanced Pricing qualifier contexts

    Optional

  • 8/3/2019 OM Pricing Setup

    2/6

    If you skip this step, users will be able to chose only predefined Oracle qualifier contexts

    and qualifier attributes for price and modifier eligibility.

    Qualifiers provide a highly configurable and flexible method of defining the rules which your

    business uses to manage pricing. Qualifiers are used by the pricing engine to determineeligibility for price lists and modifiers.

    Step 7: Create Pricing Contexts, Pricing Attributes, and Product Attributes

    Default: Predefined Oracle Advanced Pricing/Product attribute contexts

    Optional

    Pricing/Product attributes are a feature of Oracle Advanced Pricing which enables you to

    define necessary item attributes in order to price or apply a modifier and attributes used in

    formulas.

    If you do not perform this step, users will be able to select only predefined Oracle AdvancedPricing contexts and associated attribute values for benefit options.

    Step 8: Perform Attribute Mapping

    Default: Predefined Oracle Advanced Pricing attribute mapping rules.

    Optional

    Step 9: Define Unit of Measure

    Default: None

    Optional

    Units of measure (UOM) are used in Oracle Advanced Pricing to determine the unit value forwhat thepricing engine is pricing, modifying, returning a benefit, or creating an accrual.

    Do this step if you have not installed and set up Oracle Inventory or performed this

    common-applications setup for another Oracle Product.

    Step 10: Define Unit of Measure Conversions

    Default: None

    Optional

    You must define conversion rates between the base unit of measure and other units of

    measure within a UOM class if you want to price and discount an item in a UOM other thanits primary UOM. Oracle Advanced Pricing uses these conversions to automatically convert

    transaction quantities to the primary pricing unit of measure defined on the price list when

    pricing cannot find a price in the transaction unit of measure. In addition, all price

    adjustments, benefits, and charges need to be defined in the same unit of measure as the

    unit of measure used on the price list.

    Step 11: Define Item Category Sets and Item Categories

  • 8/3/2019 OM Pricing Setup

    3/6

    Default: Seeded structure name of item categories, category set inventory items, and

    associated default seeded category code combination MISC

    Optional

    Step 12: Set Up Inventory Organization

    Default: NoneRequired with defaults

    You must define at least one item validation organization in Oracle Inventory. This is the

    organization that items are validated and viewed against when entering items in the Price

    List and Modifier Setup forms.

    Perform this step if you have not installed and set up Oracle Inventory or performed a

    common-applications setup.

    Step 13: Define Item Information

    Default: NoneOptional

    Define the items that you wish to price and discount and assign them to the validation

    organizations defined in step 10. If you want to define qualifier rules which include the

    seeded qualifiers Line Volume or Line Weight you must set the

    volume or weight attributes of each item as this is used by attribute mapping to derive the

    transaction line, weight, or volume.

    Perform this step if you have not installed and set up Oracle Inventory or performed this

    common-applications setup for another Oracle product.

    Step 14: Create Item Relationships

    Default: None

    Optional

    This step is required if you wish to give item upgrade benefits. You must define a

    Promotional Upgrade item relationship from the ordered item to the item you wish to give

    as an upgrade. Define your item relationships for the item validation organization.

    Set up promotional upgrade items as follows:

    The ordered item and the promotional item need to have the same base unit of measureand unit of measure conversions.

    The modifier unit of measure and the pricing unit of measure on the order line need to be

    the same.

    If those entities are not the same, the substitution can fail.

  • 8/3/2019 OM Pricing Setup

    4/6

    Step 15: Define Pricing Lookups

    Default: Lookup type dependent

    Optional

    Lookup codes supply many of the lists of values in Oracle Advanced Pricing. Lookup code

    values are the valid entries that appear in the list of values. They simplify informationselection, and ensure that users enter only valid data into

    Oracle Advanced Pricing. You can add new lookup values at any time. You can set the

    Enable flag to No so that it will no longer appear in the list of values, or you can use start

    and end dates to control when a value will appear in a list.

    Step 16: Define Oracle Order Management Lookups

    Default: Lookup type dependent

    Optional

    Perform this step if you have not installed and set up Oracle Order Management or

    performed a common-applications setup.

    Step 17: Define Shipping Lookups

    Default: Lookup type dependent

    Optional

    Perform this step if you have not installed and set up Oracle Order Management or

    performed a common-applications setup.

    Step 18: Set Up Customer Class and Profile Class

    Set Up Customer Class

    Default: None

    Required if you price, give benefits or charge by customer class.

    Do this step if you have not installed and set up Oracle Receivables or performed a

    common-applications setup.

    Set Up Profile Classes

    Default: None

    Required if you price, give benefits or charge by customer account type.

    Perform this step if you have not installed and set up Oracle Receivables or performed acommon-applications setup.

    Step 19: Define Customers and Customer Sites

    Default: None

    Required if you price, give benefits or charge by customer.

    Perform this step if you have not installed and set up Oracle Receivables or performed a

  • 8/3/2019 OM Pricing Setup

    5/6

    common-applications setup.

    Define Customer Sites

    Default: None

    Required if you price, give benefits or charge by customer site.

    Perform this step if you have not installed and set up Oracle Receivables or performed a

    common-applications setup

    Step 20: Define Order Type

    Default: None

    Required if you price, give benefits or charge by order type.

    Step 21: Define Line Type

    Default: None

    Required if you price, give benefits, or charge by order line type.

    Step 22: Define Freight Terms

    Default: None

    Required if you price, give benefits, including upgrading freight terms, or charge by freight

    terms.

    Step 23: Define Freight Cost Type

    Default: None

    Required if you price, give benefits or calculate charges using freight cost types.

    Step 24: Define Payment Terms

    Default: None

    This step is required if you price, give benefits, or charge by payment terms.

    Perform this step if you have not installed and set up Oracle Receivables or performed a

    common-applications setup.

    Step 25: Enable Currencies

    Default: All major currencies predefined with Oracle ApplicationsOptional

    The system administrator performs this step. The codes are ISO standard codes for

    currencies. You must enable the specific currencies you want to use on your price and

    modifier lists.

    Perform this step if you have not installed and set up Oracle General Ledger or performed a

  • 8/3/2019 OM Pricing Setup

    6/6

    common-applications setup.

    Step 26: Perform System Sourcing

    Default: Predefined Oracle Advanced Pricing record

    This step is required if:

    Your pricing data application source is anything other than Oracle Advanced Pricing.

    You are integrating Oracle Advanced Pricing with an application other than Oracle Order

    Management.

    Step 27: Create Events and Phases

    Default: Seeded Oracle Advanced Pricing phases

    Step 28: Set Profile Options

    Required