Oracle R12 Advanced Pricing

Training
Part 3

📧[email protected] 📧[email protected]
 Session - 8
Attribute Management

📧[email protected] 📧[email protected]
 Agenda
Overview of Attribute Management
Creating Contexts and Attributes for Pricing Setup Windows
Deleting Contexts and Attributes
Linking Attributes to a Pricing Transaction Entity
Running the Build Attribute Mapping Rules Program (Attribute Mapping Only)
Creating a New Pricing Transaction Entity
Using Custom Sourced Attributes
Mapping of Seeded Request Types and Source Systems

📧[email protected] 📧[email protected]
 Overview of Attribute Management
Attribute mapping enables you to extend your pricing capabilities by using data from a wide variety of non-standard
sources to drive your pricing actions. The data sources for the qualifiers and pricing attributes can be from within or
outside of Oracle Applications.
Using the attribute management feature, you can complete the following tasks:

○ Create new contexts and attributes

Three methods to source data for an attribute are:

○ User Entered: Attribute value is entered by user.

📧[email protected] 📧[email protected]
 Attributes Types
Qualifier and pricing attributes are used to define customer or product attributes:

● A product attribute defines product pricing characteristics such as a product item, item number,
category, or brand.
● A customer attribute defines customer pricing characteristics such as customer name or customer
number.

📧[email protected] 📧[email protected]
 Terminology for Attribute Management
Pricing Transaction Entity (PTE)
A PTE is an ordering structure that has associated request types and source systems. Different
applications may have different request structures when they make requests to the pricing engine.
Source System
The source system is the application that captures the pricing setup data.
Request Type
The request type identifies the type of transaction that is being priced. Different applications make
requests to the pricing engine. Request types of these applications may be different. Some applications
may share their request types.
For example, iStore and Order Capture share the same request type. On the other hand, Order
Management and iStore have different request structures.

📧[email protected] 📧[email protected]
 Creating Contexts and Attributes for Pricing Setup Windows
First you create a context, then create its attributes to define specific values that define pricing rules. For example, a
context of Customer can include pricing attributes such as Customer Name or Customer Class.
● Qualifier Contexts
Used to create qualifiers that determine eligibility for a modifier (who is eligible to receive the modifier).
Qualifiers can be attached to price lists (only in Advanced Pricing) and modifiers.
● Product Contexts
○ Items that are used in price lists and modifiers are defined using the Product Context: Item. Oracle Advanced Pricing supports
price and modifier definitions at the following levels (or attributes of the context):
○ All Items
○ Item Number
○ Item Category
Note: You cannot add new contexts to the Product Context type. However, you can add attributes to the existing Product context
ITEM.
● Pricing Contexts
○ Define eligibility for a price list line or modifier and can be used for a price list line, as a formula component, or in modifiers.

📧[email protected] 📧[email protected]
 Creating contexts and attributes
● Create a new context, and then define the attributes for that context.
● Link the attribute to a PTE, and then define properties of the attribute for the given PTE.
○ Once you create the context-attribute grouping, you can link it to a specific PTE. For mapped
attributes, define Attribute Mapping Rules, and then run the Build Attribute Mapping Rules
Program.
● Run the Build Attribute Mapping Rules program.
○ This step applies only to attributes with the Attribute Mapping Method of Attribute Mapping.
Whenever you create or update these attributes or change attribute mapping rules, you
should run the Build Attribute Mapping Rules program.
● Use the attribute in a valid pricing setup.
● Enter an order. Verify that the mapped and user-enter attributes have been correctly passed to the
pricing engine from the Pricing Engine Request Viewer.

📧[email protected] 📧[email protected]
 What happens when the Build Attribute Mapping Rules program
is run?
● When you run the concurrent program Build Attribute Mapping Rules, it dynamically generates the
package QP_BUILD_SOURCING_PVT which contains attribute mapping calls to build attribute
mapping rules for attributes. This package contains only the rules of used attributes (Qualifiers and
Pricing Attributes that are used in any pricing setup) that can be mapped at run-time.
● The program generates the attribute mapping rules for all the attributes that have the Attribute
Mapping Enabled box selected. When the Build Attribute Mapping Rules program runs successfully,
the Attribute Mapping Status box is selected for those attributes for which an attribute mapping
rule is generated.
● The Build Attribute Mapping Rules program displays a status message to advise whether the
program finishes successfully. The window automatically re-queries the database if the Build
Attribute Mapping Rules process is successful and moves focus to the Attribute Mapping Status
box.
● Note: If an error in the build sourcing occurs, then all newly-created attribute mapping rules will fail
and continue to fail until the error is resolved.
📧[email protected] 📧[email protected]
 How attribute mapping works at run time
The calling application calls QP_Attr_Mapping_PUB.Build_Contexts, which starts the attribute mapping
routines and returns the attributes to the calling application.
● The calling application appends the user entered attributes and "asked for" qualifiers to this
request.
● The calling application then calls the pricing engine with these mapped attribute values.
● The pricing engine also appends a few internally mapped attributes to this request.
● The pricing engine processes the request and returns the results to the calling application
The PTE helps narrow the data that the search engine evaluates. The search engine evaluates only the
setup data that is generated by all the source systems that are defined for that PTE. It also makes
contexts of one PTE unavailable to other pricing applications families.

📧[email protected] 📧[email protected]
 Integration in the Order Management process
Channel Rev Advanced Pricing Order AR/AP
Management Management

Budget

Offer Modifiers
Sales Order
(View
Market
Budget Qualifiers Adjustments)
Eligibility

Limit
Quantity
Balances

Accrual
computation

Claim creation &

📧[email protected] 📧[email protected]
Thanks!
Contact us:
[email protected]
+44 207 101 9262
+ 1 212 404 1735

www.apps2fusion.com

📧[email protected] 📧[email protected]