Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Targeting the specific item definition with the help of the pricing
attribute.
Making our own rules using the qualifier. For example, if today is
Saturday then there will be 15 percent discount on the product.
the final price of items. If a formula is associated with any price list then we
cannot use the constant and absolute values for that particular item.
Integration of Oracle Advanced Pricing with other modules
Oracle Advanced Pricing is fully integrated with other Oracle E-Business Suite
modules. The following are the modules that are integrated with Oracle
Advanced Pricing:
Oracle Purchasing
Oracle iStore
Oracle Transportation
The steps required to set up Oracle Advanced Pricing are shown in the
following figure:
Profile options
In order to set up Oracle Advanced Pricing, there are many profile options
that are required to enable the product to work properly. An important profile
is QP: Multi Currency Installed. When this profile is enabled we can use a
price list in multiple currency rather than online in functional currency.
QP: Multi Currency Usage, which elaborates the application that calls the
pricelist, can also have multiple currencies available in it.
To set up the profile options, navigate to System Administration | Profile |
System.
We can also use other profile options such as "allow duplicate modifiers",
"size of bulk import", and so on. There are many other profile options that
are available in the system in order to give a better solution for our business
scenarios.
Price Transaction Entity (PTE)
PTE stands for Price Transaction Entity. PTE is the required setup for
Oracle Advanced Pricing. However, there is a default available for order
fulfillment, logistics, procurement, and so on. PTE is the combination of a
request type and source system. To query the PTE, navigate to Setup |
Attribute Management | Price Transaction Entity.
If we select Order Fulfillment PTE in the Source System, there are default
codes such as AMS, QP, OKS, and so on; against them we have Request
Types that detail the header and line structure.
In the same manner, we have Functional Areas for Source System. For
example, in the previous screenshot, the Advanced Pricing functional areas
are highlighted along with the Category Set associated with them.
Qualifier
As we have already defined, qualifiers are the set of rules and conditions that
actually help us analyze the eligibility of the price list that should be applied,
and the modifier to be selected. We can select a different qualifier context
such as order, customer, and so on. The qualifier attribute is dependent on
the qualifier context. Therefore, we will be only offered relevant information.
To create a qualifier for a specific product context and product attribute, we
need to navigate to Price List | Price List Setup.
Now we will query the price at which we need to apply the qualifier. We will
navigate to the Qualifiers tab and select the Qualifier Context and
Qualifier Attribute as per our requirement. We can select Customer,
Territories, and other values at the qualifier context.
In Context & Attribute, we can create context for the qualifier, product, and
price. They should have a unique code and description to distinguish them
from the other contexts. Each context has its attributes. These attributes can
be altered but if they are attached to a price list or modifier, they cannot be
altered or deleted.
For example, here we can create a modifier list type, which we can use to
create the price adjustments and amendments.
Summary
In this article, we have seen the functionality of Oracle Advanced Pricing and
why it is used. We have also seen how to set up the Oracle Advanced Pricing,
and have learnt the different terminologies, capabilities, and limitations of
the product. Moreover, we have seen how to use Qualifiers, Attributes,
Contexts, UOMs, lookups, and PTE, and how they work. We have also seen
how an item is priced for sales orders from a predefined price list.