Attribute Management in Advanced Pricing for Oracle Applications 11.5.

10+
An Oracle White Paper

Attribute Management in Advanced Pricing

Introduction ........................................................................................................ 3 Defining Pricing Transaction Entity ............................................................... 5 Define a New Pricing Transaction Entity ................................................. 5 Pricing Transaction Entity Associations Setup Form .............................. 5 Profile Options ................................................................................................... 8 Concurrent Programs ........................................................................................ 9 Build Attribute Mapping Rules.................................................................... 9 Checklist for Building Attributes Mapping Rules .......................................10 Creating Contexts and Attributes to be Used in Pricing Setup Forms ....10 Creating Contexts ........................................................................................10 Creating Attributes ......................................................................................11 Pricing Attributes and Flex fields tables ..................................................13 Linking Attributes to a Pricing Transaction Entity.....................................13 To link attributes to a Pricing Transaction Entity ..................................14 Link Attributes Window.............................................................................15 Attribute Sourcing Rules .................................................................................17 Overview of Tasks Involved in Attribute Management ............................21 Create a Price List and add item to the Price list ....................................21 Create a Modifier for this item ..................................................................22 Create new attribute in qualifier context ..................................................22 Create attribute mapping for newly created attribute ............................23 Attach Qualifier using the new attribute to the Modifier ......................24 Test by creating a new order......................................................................25 Using Custom Sourced Attributes .................................................................26 Troubleshooting Custom sourced attributes ...........................................29 Pricing Engine Request Viewer .....................................................................29 Interpreting Attributes in PERV for attribute sourcing issues .............30 Pricing Engine Request Viewer Tables ....................................................32 Attribute Management Troubelshooting Notes ..........................................32 Recommended Patches .............................. Error! Bookmark not defined. Metalink Notes .................................................................................................41 Oracle Diagnostic Scripts for Attribute Mapping Issues ...........................41 Attribute Mapping Rules - Note:363052.1 ..............................................41 Conclusion ........................................................................................................41

Attribute Management in Advanced Pricing

Page 2

Attribute Management in Advanced Pricing
INTRODUCTION

Oracle Advanced Pricing offers flexibility and extensibility in terms of handling various pricing scenarios. Attribute management is one of the key components of Advanced Pricing and it provides the users of Advanced Pricing with the flexibility to take care of varied business scenarios by defining attributes of product, qualifier or pricing context type. This paper describes in detail the various functional aspects of Attribute management, profile options needed and the set up require for creating and mapping attributes and troubleshooting details as of 11.5.10 release. Please refer to Oracle Advanced Pricing implementation guide and user guide for Attribute Management details in latest release.
FUNCTIONAL ASPECTS Pricing Transaction Entity

A new entity has been created called a Pricing Transaction Entity. A Pricing Transaction Entity (PTE) is an ordering structure that has associated Request Types and Source Systems. The Source System is the application that captures the pricing setup data. The Request Type identifies the type of transaction that is being priced. Different applications may have different request structures when they make requests to the pricing engine. In the example below, the Pricing Transaction Entity is Order Fulfillment. Within this PTE, there are several source systems. iStore, Order Capture, and Order Management will be evaluating pricing data defined in all these source systems.

PRICING TRANSACTION ENTITY - FULFILLMENT

SOURCE SYSTEM Pricing data Marketing data Logistics data

REQUEST TYPES iStore Order Capture Order Management

When a new request type is created (i.e. a new ordering structure is developed), the business must decide if the request type will use the same set of source systems in the existing 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. Request types have to be unique across PTEs.

Attribute Management in Advanced Pricing

Page 3

Oracle Advanced Pricing has seeded 4 PTEs. They are Order Fulfillment, Inter-company Transaction, Logistics, and Demand Planning.
Context

Contexts are a group of related pricing elements that can have attributes linked to them. In Attribute Management, users can set up 3 types of contexts. Product context, Qualifier context, and Pricing context. Qualifier Contexts and its attributes allow for the creation of qualifiers, which determine eligibility. The attributes in the product context help to define the product hierarchy. Attributes within a pricing context enable users to further define eligibility for a line. We can add new contexts of Pricing and Qualifier Context type. However you cannot add new contexts of Product Context type. You can add attributes to the existing Product context ITEM. The Context-Attribute grouping is linked to a specific Pricing Transaction Entity. For a given PTE, this combination becomes available to use in a formula, qualifier, price list, or modifier. Each PTE will have its own unique combination of attributes.

Note:
You cannot delete a context, if it has one or more attributes. Attributes that are already used in Pricing Setup cannot be deleted. Please make sure to set QP: Pricing Transaction Entity profile option value appropriately before creating contexts/attributes. So, these contexts and attributes will be available in pricing setup forms in that PTE. If this profile is not set correctly, the contexts/attributes linked to the PTE will not be shown in LOVs in Pricing Setup Forms, and using contexts/attributes from incorrect PTE in pricing setup (Qualifier, Pricing attributes, etc) will give incorrect results during pricing call as the attribute(s) will not be sourced correctly.
Attributes

Attributes can be used as product, qualifier or pricing attributes. Attributes are linked to a Pricing Transaction Entity depending on the defined Request Types. Different request types may use the same attribute to source different data. The same attribute used in 2 different PTEs may be completely different in terms of the attribute mapping method, mapping level, and other controls. One attribute for 2 PTEs may be different. As mentioned before, these attributes are sources of data that can be used by the pricing engine in a pricing request. There are 4 methods to source data. They are,  User entered attributes: The attribute value is entered by the user at run time. Attribute mapping is not needed.  Attribute Mapping: User defines an attribute mapping rule  Custom sourcing: User provides a code to map an attribute. In this case attribute mapping is not needed.  Runtime Sourced: Sourced in the pricing engine by a Custom API. Attributes can be sourced at the header level, line level, or for both header and line levels.

Attribute Management in Advanced Pricing

Page 4

Attribute Management in Advanced Pricing Page 5 . add meaning and description. Query using Type as „QP_PTE_TYPE‟ and you should be able to view. Order Capture. there are several source systems. For example Order capture and Oracle Pricing can be a part of one Pricing Transaction Entity. Setting up a Pricing Transaction Entity includes defining sourcing systems and request types for a Pricing Transaction Entity. The Pricing Transaction Code. however. Navigation: Oracle Pricing Manager responsibility -> Setup -> Lookups Description: Figure 1. 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. Define a New Pricing Transaction Entity A new Pricing Transaction Entity can be setup using the Setup  Lookups Form. modify and add new Pricing Transaction Entity. This is a group of applications generating same setup data. In the example quoted earlier. In this PTE. is not modifiable. IStore. Request types have to be unique across PTEs.DEFINING PRICING TRANSACTION ENTITY When a new request type is created (i. and Order Management are the request types and they will be evaluating pricing data defined in the source systems. Pricing Transaction Entity Associations Setup Form This form is used to setup a Pricing Transaction Entity. displays the Pricing Lookups window where you can add a PTE. a new ordering structure is developed). When adding a new PTE. the Pricing Transaction Entity is Order Fulfillment. the business must decide if the request type will use the same set of source systems in the existing PTE.e.

Please refer to latest Advanced Pricing Implementation Guide for more details. To setup processing constraints to some extent. Note: This form is changed in R12 release. 2. Search engine will look at only the setup data generated by all the source systems defined for that Pricing Transaction Entity. Oracle Pricing and AMS generate modifiers. If these applications are sharing their setup data then they form one Pricing Transaction Entity.Pricing Transaction Entity will help 1. Description It is a description for a Pricing Transaction Entity. Navigation: Oracle Pricing Manager Responsibility > Setup > Attribute Management > Pricing Transaction Entity Description: Figure 2. Source Systems It is the application generating setup data. For example IStore. To make contexts of one Pricing Transaction Entity unavailable to other Pricing Applications families. displays the Pricing Transaction Entity Associations Setup window with source systems associated with Order Fulfillment PTE. Attribute Management in Advanced Pricing Page 6 . Hence these applications could be source system. Pricing Transaction Entity region Name It is a name for a Pricing Transaction Entity. To slice the data search engine needs to look at.

Hence to avoid this. On the other hand. As a result of this. Description It is a description of a request type. Description It is a description for a source system. Request types The Request Type identifies the type of transaction that is being priced. displays the Pricing Transaction Entity window with request types associated with Order Fulfillment PTE. Some applications may share their request structures. Attribute Management in Advanced Pricing Page 7 . Request type codes will be unique across PTEs. Request structures of these applications may be different. Order Management and IStore have different request structures. Code It is a short name of a request type.Code It is a short name for the source system application. each integrating application will have to change its request structure. If request type codes are not unique then each request structure will have to provide PTE code to uniquely identify the request type. Different applications make requests to the pricing engine. Enabled Enable/disable source system association with PTE. They share same request structures. Description: Figure 3. For example IStore and Order capture.

All Pricing Setups entities created in the new system will be created for this Pricing Transaction Entity. Application and User level. QP: Pricing Transaction Entity This profile has the default value for the Pricing Transaction Entity. Please make sure to set QP: Pricing Transaction Entity profile option value appropriately before creating contexts/attributes. Header Global Structure It is a global structure for „Header‟. Values:   Map attributes used in active pricing setup: The Build Attribute Mapping Rules program will source the attributes that are used only in the active pricing setup. The default value for this profile at the time of installation at site level is „Oracle Pricing‟. Enabled Enable/disable request type association with PTE. This profile value identifies the source system of pricing setup data. QP: Build Attributes Mapping Options This profile option enables to set attribute mapping rules for attributes in both the active and inactive setups. Line Global Structure It is a global structure for „Line‟. This profile can be set at Site. Based on it user will either enter global structures for header and line or view names for header and line. PROFILE OPTIONS QP: Source System Code This profile can be set at Site. Map all attributes: This program will source the attributes that are used in both the active and inactive setups. Attribute Management in Advanced Pricing Page 8 . Application and user level. So. these contexts and attributes will be available in pricing setup forms in that PTE. Header View Name It is a view name for the „Header‟ Line View Name It is a view name for the „Line‟. The default value for this profile at the time of installation at site level is „Order Fulfillment‟.Header/Line structure/view A request type may have a global record structure or a view defined to map the data.

modifiers.Note: Please set this profile value to „Map attributes used in active pricing setup‟ to map only those attributes used in the active pricing setup to improve the performance of Build Attribute Mapping Rules program. the Attribute Mapping Status box is selected for attributes that were successfully mapped. it may be set to „Map all attributes‟. This program generates entries into the BUILD_CONTEXTS application program interface (API). The Build Attributes Mapping Rules program can be run during off-peak hours or whenever any downtime is planned so that the new attributes which are defined or used after the last run are included in the static package for better performance. If this profile value is set to „Map all attributes‟. The program gives warning when the program completes with Attribute Mapping errors and provides other status messages: Success: Program completes without Attribute Mapping errors. Any new attributes used after the last run of the program are mapped dynamically to prevent any attributes from not getting mapped. It pre-generates entries into this API so that the pricing engine evaluates only the qualifier and pricing attributes used in the price lists. Warning: Program completes with one or more Attribute Mapping errors. CONCURRENT PROGRAMS Build Attribute Mapping Rules Navigation: Oracle Pricing Manager responsibility > Reports The Build Attribute Mapping Rules program generates the attribute mapping rules for all attributes with the Attribute Mapping Enabled box selected. After the program is run. Error: Program cannot complete due to some exception/runtime error. this program sources the attributes that are used in both the active and inactive setup. Attribute Mapping Rules Error Report Navigation: Oracle Pricing Manager responsibility -> Reports This program produces a list of all attribute mapping rules that are invalid. The Build Attribute Mapping Rules program will source the attributes that are used only in the active pricing setup if the profile value QP: Build Attributes Mapping Options set to is set to „Map attributes used in active pricing setup‟. Attribute Management in Advanced Pricing Page 9 . The program need not be run if we create or update a new attribute where User Entered or Custom Source is the Attribute Mapping Method If an attribute is created with Attribute Mapping as the Attribute Mapping Method. For troubleshooting/debugging purpose. then Build Attribute Mapping Rules needs to be run. and formulas that are relevant to each call rather than all of the attribute mapping rules.

pricing type. Please ensure that this Sourcing Enabled box is selected. you must ensure that it is attached to at least one valid Pricing Setup such as a Modifier. you can set up the following contexts: Qualifier Contexts and its attributes: Used to create qualifiers that determine eligibility for a modifier (who is eligible to receive the modifier).5. Product Contexts and its attributes: Defines the product hierarchy related to product information. They can be used for a price list line. To create new contexts Navigate to the Setup -> Attribute Management -> Contexts and Attributes Setup window. CREATING CONTEXTS AND ATTRIBUTES TO BE USED IN PRICING SETUP FORMS The following sections describe how to setup contexts and attributes. Price List or Limit. Attributes with mapping method USER ENTERED and CUSTOM SOURCED are never meant to be created by the Build Attribute Mapping Rules program. Creating Contexts In Attribute Management.  If the attribute is newly created. request type.  In 11. Ensure that the PTE-Attribute link that was created has at least one attribute mapping rule. CHECKLIST FOR BUILDING ATTRIBUTES MAPPING RULES Sometimes users believe they have successfully mapped an attribute when they get the message Attribute Mapping Rule Generation is Successful. or in modifiers. The entry includes details such as the context. user can update (enable/disable) Sourcing Enabled box for the attribute sourcing rule. Pricing Contexts (associated with pricing attributes): Define eligibility for a price list line or modifier. attribute. for the sourcing rule to be active and for the attribute to be sourced by attribute mapping functionality. link it to a Pricing Transaction Entity successfully and then map it using the Build Attribute Mapping Rules from the Tools menu. and the error message produced by the invalid mapping. but find that the Attribute Mapping box for that attribute remains cleared when it should be selected.  The Attribute Mapping Method must be ATTRIBUTE MAPPING.The report displays an entry in the file log/output for every attribute mapping rule that is invalid. attribute mapping rule. Attribute Management in Advanced Pricing Page 10 .10 release. Qualifiers can be attached to price lists (only in Advanced Pricing) and modifiers. the product context Item may consist of attributes such as Item Number and Item Category. users must ensure the following conditions are met:  The Attribute Mapping Enabled box must be selected. For example. as a formula component. To ensure a successful mapping and to avoid the situation described above. This may occur when they create a new attribute.

Description It is a description of a context. Enabled Enable the context to make it available in Pricing Setup windows. Context Type Context type can be Qualifier. you can create its attributes. The pricing engine evaluates attributes during engine run time to determine which price lists and modifiers are eligible for the transaction. context will not be displayed in pricing setup windows. or Pricing Context. it cannot be updated. To create new attributes Attribute Management in Advanced Pricing Page 11 . or for both order and line levels. and all the attributes defined under this context will also be unavailable for setup. Attribute values can be derived at the order level. displays the Context Setup window with Customer Group context and the attributes created in this context. line level. Attributes determine the specific values in which you define pricing rules.Description: Figure 4. Name It is a name of a context. Seeded Seeded check box is selected for the seeded context. If disabled. Once created. Code It is a short name for the context. Creating Attributes Once the context is defined.

Once created. displays the Context Setup window with Customer Group context and the attributes created in this context. enter the following fields: Code It is a short name of the attribute. Attribute Management in Advanced Pricing Page 12 . if two incompatible discounts qualify for the same item. Precedence It is a numeric precedence value. Description It is a description for the attribute. it cannot be updated. Application Name It is an Application name that created this attribute. Precedence numbers in the series of 5's and 10's are reserved for seeded qualifiers/pricing attributes and should not be used. In the Attributes region. Name It is a name of the Attribute. Select the context to which you want to link attributes: Description: Figure 5. For example. then the discount with the higher precedence is given. which decides the processing sequence of qualifier/ pricing attributes. If an Application name is not entered. This is an internal name that is unique for a given attribute. The precedence is restricted to a maximum of 3 digits (any number between 1 and 999). Oracle Pricing will be defaulted to the Application Name.Navigate to the Setup -> Attribute Management -> Contexts and Attributes window.

then attribute value is required and should be entered. Pricing Attributes and Flex fields tables When a Pricing Attribute is created using the Contexts and Attributes window Flex field Pricing Contexts is created in the Flex field. Required If Required check box is selected. the engine will never pick it. Columns QUALIFIER_ATTRIBUTE1 through QUALIFIER_ATTRIBUTE30 are reserved for seeded qualifier attributes. these definitions need to be in the flex field tables as well. Most important. the setup data will not be available in the QP tables. The Data type value indicates if the value set is numeric (Number) or alphabetic (char). and includes Request Types and Source Systems. The Request Type identifies the type of transaction that is being priced. Hence for pricing attributes to display on OM's windows.Column Mapped It is a pricing column mapped value to which an attribute will be mapped. this combination becomes available in the pricing setup windows. Pricing Attribute setup must always be done in the Context and Attributes setup menu. The Source System is the application that captures the pricing setup data. LINKING ATTRIBUTES TO A PRICING TRANSACTION ENTITY A Pricing Transaction Entity consists of a group of applications that point to the same setup data and attributes. Oracle Advanced Pricing provides the following seeded PTEs: Attribute Management in Advanced Pricing Page 13 . For a given PTE. click value sets. So even though the pricing attribute displays in OM windows. The definitions of contexts and attributes are stored in QP tables. you link the context/attributes grouping to a specific Pricing Transaction Entity (PTE). Each PTE has its own unique combination of attributes. Once you have created a context and its attributes. Seeded Seeded box is selected if the attribute is seeded. Once contexts and attributes are created. This occurs because Order Management (OM) uses flex field structure for pricing attributes. If user does a pricing attribute setup in flex field tables. as data is not copied from flex field tables to QP tables. you can link the attributes to a specific Pricing Transaction Entity (PTE). Also the same data will be stored in flex field tables as the context type is Pricing Attribute. Value Set Value set to define valid values for an attribute. to create a new value set or view an existing one. Alternately.

OKS.Pricing Transaction Entity Complex MRO Demand Planning Intercompany Transaction Logistics Order Fulfillment Procurement Code CMRO DEMAND INTCOM LOGSTX ORDFUL PO The following tables display the seeded Request Types and Source Systems for each PTE: Pricing Transaction Entity Complex MRO Demand Planning Intercompany Transaction Logistics Order Fulfillment Procurement Source Systems AHL QP INV. ASO. OKC. Attribute Management in Advanced Pricing Page 14 . ONT PO To link attributes to a Pricing Transaction Entity Navigate to the Setup – Attribute Management – Pricing Transaction Entity window. QP FTE AMS. QP PO Request Types AHL MSD IC FTE ASO. OKC. OKS.

Level This field indicates whether the attribute is at „Order‟ level or „Line‟ level or at „Both‟. Pricing Transaction Entity Select a Pricing Transaction Entity. Alternately.Description: Figure 6. you can search for a Pricing Transaction Entity by clicking the Find icon. Following fields are specific to define attribute mapping. Attribute Mapping Method There are four different ways to define how an attribute is mapped: Attribute Management in Advanced Pricing Page 15 . This „level‟ is also used to selectively display pricing attributes/qualifiers in the LOVs while setting up modifiers/formulas/price list/qualifier. Product Context. displays the Pricing Transaction Entity window with Order Fulfillment PTE and the contexts linked to this PTE. Context Type Select the Context Type such as Pricing Context. Link Attributes Window Description: Figure 7. Context Select a context whose attributes you want to link to a PTE. It means that only the header level „agreement_id‟ will be attribute mapped whereas agreement_id on order lines will not be attribute mapped. or Qualifier Context. attributes have not been created / selected for that context in the given PTE. displays the Attribute Mapping window and the various fields. the level is „Order‟ for an attribute „agreement_id‟. Show Linked Contexts Check box Select the Show Linked Contexts check box to display only those contexts assigned to the selected Pricing Transaction Entity. The context(s) matching the criteria for the selected PTE and Context Type will be displayed in the Contexts region. For example. If the Assigned to PTE box is not checked.

If „LOV Enabled‟ is checked and „Attribute Mapping Enabled‟ is unchecked. Attribute Mapping Enabled This checkbox should be checked. When unchecked. attribute will not be mapped. Column Mapped The column mapped value is the defaulted from Attributes setup. For additional information on custom attribute sourcing. the pricing engine calls the Runtime Sourcing API to acquire an accumulation value for the accumulation attribute (defined as RUNTIME SOURCE in Attribute Mapping setup). However we need to check the „Attribute Mapping Enabled‟ flag for the attributes. an error will be raised. please refer to Note 374963. However existing modifiers defined using that attribute. a mapping rule will not get created. Runtime Sourced: Sourced in the pricing engine by a Custom API. then in this case even though the attribute is available for setup.1 in MetaLink. All seeded attributes will have this flag „checked‟ so that as a „out of box‟ solution.    Attribute Mapping: Define an attribute mapping rule. Custom sourcing: User provides a code to source an attribute. if we want the attribute to be sourced from attribute mapping rules. User Entered: Attribute value is entered by user. which we want to be sourced from mapping rules defined and for which „Attribute Mapping Method‟ is „Attribute Mapping‟. This is used to source an accumulation attribute at runtime. If unchecked. Attribute mapping is needed. The Build Attribute Mapping Rules concurrent program generating the „Build context„ API will look at this field and will generate the code only for the attributes with this checkbox checked. Attribute mapping is not needed. attribute will not be available in setups of modifier/qualifier/formula. Attribute mapping is not needed as attribute will be sourced by „get custom attributes‟. This flag will be untouched whenever data upgrade scripts are run. attribute will be available in LOVs of modifier/qualifier/price list/formula screens. will behave the same way. Attribute Management in Advanced Pricing Page 16 . Hence whenever user uses such attribute in the setup screens of qualifier/modifier/pricelist/formula. Use in Limits User checks this checkbox if user wants the attribute to show up in the Attribute LOVs in Limits setup screens (including „Other Attributes‟ screen). all seeded attributes will be available in the LOVs of the setup screens (pricelist/qualifier/modifier/formula etc). LOV Enabled Only if LOV Enabled checkbox is checked. During accumulated range break calculations.

program to regenerate „Build Contexts‟ API. Navigation: Oracle Pricing Manager responsibility -> Setup -> Attribute Management -> Attribute Linking and Mapping Attribute Management in Advanced Pricing Page 17 . Attribute Mapping Status This checkbox is checked /unchecked automatically by the Build Attribute Mapping Rules concurrent program which generates the Build Contexts API for mapped attributes. formula. It is a non-navigable field.Used in Setup It indicates if the attribute is used in an active pricing setup such as a price list. Attribute Mapping Status is unchecked  For new attributes until concurrent program is run after defining the attribute mapping for it. then sourcing rule needs to be defined at appropriate levels (Header/Line/Both) from which the attribute will be sourced from or get the value. ATTRIBUTE SOURCING RULES If Attribute Mapping method is ATTRIBUTE MAPPING for an attribute. then no further attribute mapping is required. If „Attribute Mapping Status‟ is un-checked and „Attribute Mapping Method‟ is „Attribute Mapping‟ and „Attribute Mapping Enabled‟ is checked then it indicates the need to run the conc. modifier. If Attribute Mapping Method is USER ENTERED or CUSTOM SOURCED. qualifier. or limit. „Attribute Mapping Status‟ column is checked when the concurrent program is run successfully.  When an attribute mapping rule is modified. This section describes how to complete attribute mapping for attributes with Attribute Mapping selected as the Attribute Mapping Method.

G_LINE. Attribute Management in Advanced Pricing Page 18 . We are expected to enter the Application. displays window for attribute linking and mapping and the various values available for source types. a warning message will appear. The user value string will have a value as OE_ORDER_PUB. This region will be grayed out if the level is „Line‟. Header level region We can enter data here if the Attribute Mapping level (defined in „Link attributes‟ screen) of the attribute is „Order‟ or „Both‟. the system defaults „Oracle Pricing‟ as the creator of the mapping rule. Request types For PTE region It shows the entire „enabled‟ Request types defined for given PTE. before creating a mapping rule. Application Name This column indicates the Application that created the mapping rule. Description It is a description of Request type.Description: Figure 8.XXX_XXX where XXX_XXX is the column name in Order lines table. In case we do not enter an Application name. Request Type It is a Request type associated to PTE. If attribute sourcing rule(s) are not defined for all request types. Details of each of the fields in the form have been explained below.

Attribute Management in Advanced Pricing Page 19 . The output of our function can only be a table of VARCHAR2‟s. It will show the value defined in „Request type‟ tab of the „Pricing Transaction entity setup‟ form. OE_ORDER_PUB. OE_ORDER_PUB. sourcing rule like CUSTOM_PKG.G_LINE.Global structure/View Name This is a display only field. Structure of the Line_rec_type and header_rec_type can be obtained from the Manufacturing Open Interface Manual. You have two record structures available. PL/SQL API Multi-Record: We can write a custom API (must be a function) that returns multiple values. SYSDATE Navigation: Oracle Pricing Manager responsibility -> Setup -> Attribute Management -> Attribute Linking and Mapping.G_LINE contains all the possible values of a sales order line. For Order Management all the record structures are defined in the package OE_ORDER_PUB. The parameters passed to the PL/SQL API should be valid columns and we cannot pass the entire structure. Enter a constant value that will always be mapped to this attribute for the given condition.100 System Variable: System Variable. Enter the system variable that will be mapped to the attribute for the given condition. (For I*Store/OC the equivalent global structures are defined in the package ASO_PRICING_INT. For example. PL/SQL API: Attribute can be sourced directly from a global structure defined for the given source system or can be sourced from seeded or custom PL/SQL API. Constant Value: Constant value. For example. enter OE_ORDER_PUB. Ex. if you want to use payment term id as the source value for the new segment that you have defined.G_HDR contains fields from Order header. A LOV will provide a list of valid profile options such as OE: Item Validation Organization.payment_term_id in the function name. User Source type The possible values of source type are  Application Profile  PL/SQL API  PL/SQL API Multi-Record  Constant Value  System Variable Application Profile: Select the profile option from where you want to get the default value for this attribute. Ex.CUSTOM_API (OE_ORDER_PUB) is invalid.

Restore Defaults button For all seeded Attribute Mapping rules. This field is protected against update. the „Restore Defaults‟ button will be grayed out. whether the sourcing rule is seeded or not. If we want to modify seeded mapping. Enabled Enable/Disable sourcing rule at Order/Line level for one or more request types under a PTE. If we want to modify seeded mapping. Attribute Management in Advanced Pricing Page 20 . This region will be grayed out if the Attribute Level in the previous screen is „Order‟. Value String (user & seeded) It is a value of the source type. This field is protected against update. Seeded Source Type It will have value if the sourcing rule is seeded. „Restore Defaults‟ button will restore back the seeded source type and the seeded value string as user source type and user value string respectively. If the seeded source type and the seeded value string are same as user source type and user value string. Seeded This is a non-navigable field indicating.Description: Figure 9. Line level region We can enter data here if the level (defined in „Link attribute‟ form) of the attribute is „Line‟ or „Both‟. (user value string). then we can enter data into corresponding „user‟ field. Rests of the fields are the same as the Header level region. then we can enter data into corresponding „user‟ field (user source type). Seeded value string will have seeded value. displays window for attribute linking and mapping and the various values available for source types.

 Create new attribute in qualifier context.Note: It is strongly advised to not to change or remove the seeded PTE/Source System/Request Type/Contexts.  Attach Qualifier using the new attribute to the Modifier.Site Use Level Attribute Management in Advanced Pricing Page 21 . Create a Price List and add item to the Price list Customers are defined and maintained primarily by Accounts Receivables responsibility. and will do attribute mapping and will use it in modifier. displays the item AS54999 being added to the Price List Corporate Customer . However. OVERVIEW OF TASKS INVOLVED IN ATTRIBUTE MANAGEMENT We will take a scenario where we will create a new qualifier attribute.  Create attribute mapping for newly created attribute. Then we will create a new sales order to see if the modifier is getting applied and qualifier is satisfied. Below are the key steps in this task:  Create a Price List and add item to the Price list.  Test by creating a new order. mapping rules. and new PTE/source system and request types for their business needs.  Create a Modifier for this item. Navigation: Oracle Pricing Manager responsibility -> Price Lists -> Price List Setup Description: Figure 10. user can create custom context/attributes. Attributes and attribute mapping rules setup.

Create new attribute in qualifier context Navigation: Oracle Pricing Manager responsibility -> Setup -> Attribute Management -> Contexts and Attributes. displays the item AS54999 being added to the Price List Corporate with Unit price as USD 1900 Create a Modifier for this item Navigation: Oracle Pricing Manager responsibility -> Modifiers -> Modifier Setup Description: Figure 12. displays modifier Line Dis being created. Attribute Management in Advanced Pricing Page 22 .Description: Figure 11.

displays creation of a new attribute ORDERED_QUANTITY being created in context Order. Navigation: Oracle Pricing Manager responsibility -> Setup -> Attribute Management-> Contexts and Attributes Description: Figure 14. displays creation of a new context of type Qualifier Context in context Order. Create attribute mapping for newly created attribute Navigation: Oracle Pricing Manager responsibility -> Setup -> Attribute Management -> Attribute Linking and Mapping Attribute Management in Advanced Pricing Page 23 .Description: Figure 13.

displays window for attribute linking.Description: Figure 15. Attach Qualifier using the new attribute to the Modifier Navigation: Oracle Pricing Manager responsibility -> Modifiers -> Modifier setup Attribute Management in Advanced Pricing Page 24 . displays window for attribute linking and mapping. Navigation: Oracle Pricing Manager responsibility -> Setup -> Attribute Management -> Attribute Linking and Mapping -> Link Attributes Description: Figure 16.

Description: Figure 17. Returns -> Sales order Description: Figure 18. displays adding newly created qualifier attribute to the existing modifier Test by creating a new order Navigation: Order Management super user responsibility -> Orders. displays the sales order creation Attribute Management in Advanced Pricing Page 25 .

the user can control how the attributes are sourced based on the PTE of the calling application. ASO. which defines the level of the attribute mapping rule. Typical values of Request Type Codes that can be passed are ONT. By using the Request_Type_Code. without the need for an attribute mapping rule. qualifier has qualifier the modifier application and the unit price has changed. QP_CUSTOM_SOURCE. FTE or MSD. The Pricing Type can be H (Header) or L (Line). Return ->Sales order Description: Figure 19. OKC. calls this procedure to pick up customsourced attributes if the profile option QP: Custom Sourced is set to yes.Get_Custom_Attribute_Values.Navigation: Order Management super user responsibility -> Orders. USING CUSTOM SOURCED ATTRIBUTES Attributes can also be passed to the pricing engine directly. the Attribute Manager API calls a custom API. The modifier details can be seen. These attributes and their values are passed to the pricing engine in the same manner as the attributes sourced through attribute mapping rules. The input parameters to QP_CUSTOM_SOURCE are Request Type code and Pricing Type. IC. PO. The user code will be written in the package procedure QP_CUSTOM_SOURCE. The Attribute Manager API program (Build Contexts). Profile option: QP: Custom Sourced – YES Attribute Management in Advanced Pricing Page 26 . where the user has manually defined the attributes being passed and coded the sourcing of their values. In such cases.

The user must ensure that the Attribute Mapping method for both these PTE-Attribute links is CUSTOM SOURCED in the 'Attribute Linking and Mapping' setup window. Customer has to implement the Package Body in QPXCSOUB.QP_CUSTOM_SOURCE package specification contains the following procedure declaration. two segment mapping columns.Get_Custom_Attribute_Values procedure to source custom mapped attributes. x_qual_ctxts_result_tbl . p_pricing_type_code . will have Custom Sourced values as 10 for ORDER as well as LINE Attribute Mapping levels.'L' for Line and 'H' for Header Level attribute mapping rule. If profile option QP: Custom Sourced is set to Yes. x_price_ctxts_result_tbl . ONT.QP_CUSTOM_SOURCE Package Body. x_qual_ctxts_result_tbl OUT QP_ATTR_MAPPING_PUB.pls .Files:   QPXCSOUS. attributes with attribute Attribute Mapping Method=CUSTOM SOURCED. In this case. x_price_ctxts_result_tbl OUT QP_ATTR_MAPPING_PUB.pls (for example) to source custom mapped qualifier/pricing attributes in Get_Custom_Attribute_Values procedure and need to set QP: Custom Sourced profile option to Yes..pls . Ex. p_pricing_type_code IN VARCHAR2 . CREATE or REPLACE PACKAGE body QP_CUSTOM_SOURCE AS Attribute Management in Advanced Pricing Page 27 . Attribute Manager API Build_Contexts will call QP_CUSTOM_SOURCE. 'QUALIFIER_ATTRIBUTE31' and 'PRICING_ATTRIBUTE31' that belong to contexts CUST_SOURCE_QUAL_CON and CUST_SOURCE_PRIC_CON respectively and linked to PTE 'Order Fulfillment'. Example code: The following example explains how a customer may code the body of QP_CUSTOM_SOURCE for a particular case.Qualifier attributes result table.e.QP_CUSTOM_SOURCE Package Specification. Procedure Get_Custom_Attribute_Values: QPXCSOUS.CONTEXTS_RESULT_TBL_TYPE .pls . Parameters: p_req_type_code Request Type Code.CONTEXTS_RESULT_TBL_TYPE ). PROCEDURE Get_Custom_Attribute_Values (p_req_type_code IN VARCHAR2 .Pricing attributes result table. QPXCSOUB. i.

attribute_name:= 'PRICING_ATTRIBUTE31'. -.‟H‟) then -.attribute_value:= '10'. / Please note that. context_name is actually the context code and not the name of the context. -.select value -. c) Ensure that attribute_value is assigned to NOT NULL value.CONTEXTS_RESULT_TBL_TYPE ) is Begin /* Note: a) Assign Context Code to context_name parameter and not the name of the context.add ('In Get_Custom_Attribute_Values').This might return multiple values. -. If p_req_type_code = „ONT‟ and p_pricing_type_code in („L‟.CONTEXTS_RESULT_TBL_TYPE ./*Customizable Public Procedure*/ PROCEDURE Get_Custom_Attribute_Values (p_req_type_code IN VARCHAR2 .attribute_value := '10'.The statements below help the user in turning debug on. x_qual_ctxts_result_tbl (1).oe_debug_pub. attribute_name is the column mapped for the attribute and not the attribute name.context_name := 'CUST_SOURCE_QUAL_CON'.from v$parameter -. -.G_DIR value.where name like 'utl_file_dir%'.context_name:= 'CUST_SOURCE_PRIC_CON'. Also.attribute_name := 'QUALIFIER_ATTRIBUTE31'. end if. */ -.The user needs to set the oe_debug_pub. -. b) Assign Column Mapped for the attribute to attribute_name parameter and not the attribute name.Sample debug message. -. x_price_ctxts_result_tbl OUT QP_ATTR_MAPPING_PUB. Attribute Management in Advanced Pricing Page 28 . END QP_CUSTOM_SOURCE. x_qual_ctxts_result_tbl (1). x_price_ctxts_result_tbl (1).Sourcing qualifier attributes.Sourcing pricing attributes. End Get_Custom_Attribute_Values. x_price_ctxts_result_tbl (1). -. x_qual_ctxts_result_tbl (1). and any one of the values can be taken.Make sure that the value of the directory specified. otherwise the attribute will not get sourced and not used by pricing engine for calculation. x_price_ctxts_result_tbl (1). actually exists. x_qual_ctxts_result_tbl OUT QP_ATTR_MAPPING_PUB.This value can be found by executing the following statement -. p_pricing_type_code IN VARCHAR2 .

Look at the Pricing Engine Request Viewer and see the custom sourced attribute is sourced correctly and the value assigned to the attribute is matched with the setup value in the pricelist/modifier/formula setup. or Oracle Contracts Core. Also. Order Capture. Previous pricing requests are saved in pricing tables.  Please check the string 'Before Calling Custom Sourcing Package' in the debug log and make sure that there is no exception/error message thrown in custom API call and check the number of custom attributes sourced. Rounding Flag.  Please put debug messages in Get_Custom_Attribute_Values procedure using oe_debug_pub. you can do the following:   View the controls passed by the calling application to the pricing engine such as Events. View price request line passed in by the calling application. such as OM. PRICING ENGINE REQUEST VIEWER (PERV) The Pricing Engine Request Viewer window captures and displays the inputs and outputs of the pricing call.add API and verify that the debug messages are printed in the debug log to diagnose the issue in the custom procedure implementation. check the output of the following SQL to determine the error message thrown in the custom package: SELECT line || „/‟ position POS. Search and Calculate Flag.  Please set QP: Debug profile to „Request Viewer On‟ and reproduce the issue. GSA Flag. Please see 'Pricing Engine Request Viewer – Attributes section‟ in Advanced Pricing implementation guide on how to use Pricing Engine Request Viewer for attribute sourcing issues. text from DBA_ERRORS WHERE NAME =‟QP_CUSTOM_SOURCE‟. Attribute Management in Advanced Pricing Page 29 . It captures the pricing engine call from any calling application.  Please note that the value assigned to the attribute in Get_Custom_Attribute_Values procedure should not be NULL. otherwise the attribute will not get sourced.Troubleshooting Custom sourced attributes  Please check QP: Custom Sourced profile is set to Yes for the Attribute Manager API Build_Contexts to call QP_CUSTOM_SOURCE. The Pricing Engine Request Viewer window displays the latest pricing request and updates the display information each time the pricing engine captures a new transaction. Using the Pricing Engine Request Viewer window. iStore.Get_Custom_Attribute_Values procedure to source custom mapped attributes. The information displayed by the Pricing Engine Request Viewer enables you to diagnose which lines were selected or rejected by the pricing engine to determine why certain prices and adjustments were or were not applied.

and Service Items). View the relationship between order lines for promotional modifiers. select Request Viewer Off to turn the Request Viewer off. This profile option can be updated at the user level. The output qualifier and pricing attribute records would have the qualifiers and pricing attributes passed to the pricing engine for the line. The default value is set to Request Viewer Off. Attributes block shows all the attributes corresponding to that Line. only the profile QP: Debug needs to be set to either „Request Viewer On‟ or „Request Viewer On. otherwise it is always recommended to set the value to „Request Viewer Off‟ (default). price breaks. View the pricing. but the debug log information is not written into the debug log table.  Setting up the user profiles QP: Debug: To start the Pricing Engine Request viewer. Please set this profile value to „Request Viewer On‟ only for debugging purpose.    View which modifier lines the pricing engine applied or rejected for benefit adjustments along with the details of the modifier line. Navigation Path The Pricing Engine Request Viewer window is available from within Oracle Order Management. QP: Set Request Name: Set the value of the profile option QP: Set Request Name to append the value of the profile with Order ID to be stored in the Request Name field. and service lines (OID." then the Request Viewer captures pricing request details into the pricing debug tables. The default value is Null. other users' transactions are not affected.‟ The pricing engine request viewer is only active for the transactions of the user who set this profile option. If the profile is set to "Request Viewer On. The navigation path is: Sales Order window > Tools > Pricing Engine Request Viewer. but the Debug Log is not visible in the Request Viewer. PRG.  Attribute Management in Advanced Pricing Page 30 ." Alternately. Please see Pricing Engine Request Viewer window section In Oracle Advanced Pricing implementation guide for more information. Interpreting Attributes in PERV for attribute sourcing issues  To collect debug information in QP tables which is used by Pricing Engine Request Viewer. select Attributes button by placing the cursor in the Lines Block. View the formula step values generated by the pricing engine used in formula calculation. View and query fields in the Pricing Debug Log. It is also available on the menu for Pricing Manager Responsibility. The debug log text file will be created. and product attributes passed to the pricing engine along with the other data generated by the engine. set the profile QP: Debug to "Request Viewer On. qualifiers. PBH. but Debug Log is not visible in Viewer‟ option and OM: Debug Level profile option need not be set. From the „Pricing Engine Request Viewer‟ window.

The output qualifier and pricing attribute records would have the qualifiers and pricing attributes which qualified the price list line or modifier list line. Please set QP: Insert Formula Step Values into Temp Table profile to yes to insert the dynamic formula step values evaluated during runtime. The attributes of Line and Line details are stored in QP_DEBUG_REQ_LINE_ATTRS table. Periodically purging the historical data from the pricing debug tables will improve the performance of the „Pricing Engine Request Viewer‟ form. Attributes block shows all the attributes corresponding to that Line Detail. This program can be accessible from: o o Oracle Pricing Manager -> Reports -> Submit New Request (button). please see if any formula processing error is thrown in the debug log and set this profile to yes to see the formula step values. Name – QP: Purge Pricing Engine Requests. The data in QP_FORMULA_STEP_VALUES table is copied to debug table QP_FORMULA_STEP_VALUES_TMP that is used by Pricing Engine Request Viewer. formula step values for the dynamic formula attached to price list/modifier will be inserted into QP_FORMULA_STEP_VALUES_TMP table which can be used during runtime in custom code and „Step Values‟ button in the Pricing Engine Viewer will be enabled. Name – QP: Purge Pricing Engine Requests. From the „Pricing Engine Request Viewer‟ window. Please refer to Advanced Pricing Implementation guide> Pricing Engine Request Viewer window section for complete details on the columns in each region. For any formula sourcing issues.       Attribute Management in Advanced Pricing Page 31 . Choose – Single Request. Please run „Purge Pricing Engine Requests‟ concurrent program on a regular basis to purge the historical data from the pricing debug tables. Please refer to Pricing Engine Request Viewer tables section for more information. select Attributes button by placing the cursor in the Line Details block. Oracle Pricing Manager -> View Concurrent Requests -> Submit New Request (button). Only if this profile is set to yes. Please refer to Advanced Pricing Implementation guide >Pricing Engine Request Viewer window>Attributes window section for the information on the columns displayed in Qualifer Context/Product Context/Pricing Context to diagnose attribute sourcing issues. Please make sure that the all the required attributes have been sourced correctly and the values match with the qualifier/product/pricing attributes used in the pricelist/modifier/formula setup. Choose – Single Request.

No. Attribute Management in Advanced Pricing Page 32 . Please refer to Point 14 for Patches available for upgrade issues in seeded attribute sourcing rules. This table contains information about the related lines.Pricing Engine Request Viewer tables S. If this is a custom API then correct the API. including adjustments and discounts that the pricing engine eliminates. 4 5 6 QP_DEBUG_REQ_LINE_ATTRS QP_DEBUG_REQ_RLTD_LINES QP_FORMULA_STEP_VALUES ATTRIBUTE MANAGEMENT TROUBLESHOOTING NOTES S. Also. 1 Problem Description QP_Attr_Mapping_PUB package is invalid due to incorrect attributes mapping setup. If this is the seeded API then determine whether a correction patch is available. please execute the following SQL to get QP_BUILD_SOURCING_PVT_TMP package body and check the attribute mapping rule that might be causing syntax failure: > set head off 2 The concurrent program Build Attribute Mapping Rules failed with error. Execute the following statement and examine the output: Select line || „/‟ position POS. It has adjustment and discount details for lines. If this is the seeded API then determine whether a correction patch is available. The step values are inserted into the table during the evaluation of formula attached to the pricelist/modifier. Check which attribute mapping API is causing this error. This table contains details about the lines being priced. Solution Check dba_errors for this package to determine which attribute mapping API is causing the error. If this is a custom API then correct the API. This table contains information about the formula step values which are inserted into the table QP_FORMULA_STEP_VALUES. This table contains information on the pricing attributes that the attribute mapping functionality passed to the pricing engine. This table contains information about the line details being priced. text from dba_errors where name=‟QP_BUILD_SOURCING_PVT_TMP‟. No 1 2 3 Table Name QP_DEBUG_REQ QP_DEBUG_REQ_LINES QP_DEBUG_REQ_LDETS Description This table contains information about the pricing requests.

it must be used in at least one valid pricing setup. d) Attribute Sourcing Rules have been defined. Execute following statement and examine the output: select line || ‟/‟ || position POS. Please check Attribute Mapping Method is set to „ATTRIBUTE MAPPING‟. I run Build Attribute Mapping rules from the Tools bar. Please check the following pre-requisities: a) The Attribute Mapping Enabled checkbox was not checked. determine whether there is a patch available to correct the seeded rule. 4 5 b) Attribute is used in Pricing Setup. If the error is “Encountered the symbol _ when expecting…” then determine the relevant patch to be applied. Please note that „USER ENTERED‟ and „CUSTOM SOURCED‟ attributes will not be sourced by Build Mapping Rules program and need to be passed by the calling Attribute Management in Advanced Pricing Page 33 . The return message confirms that the Build Attribute Mapping program ran successfully. Do not run the Build Attribute Mapping Rules concurrent program when active users are calling pricing engine.> set pagesize 100 > spool pkg_body > select text from all_source > where name= 'QP_BUILD_SOURCING_PVT_TMP' > and type = 'PACKAGE BODY' > and owner = 'APPS' > order by line. Please check Used in Setup checkbox was not checked. text from dba_errors where name=‟QP_BUILD_SOURCING_PVT‟. Attribute Mapping Methods other than ATTRIBUTE MAPPING do not need to be mapped. While entering the order line in sales order Pad receives an error: END_AS_UNEXPECTED_ERROR (PKG_NAME=oe_order_adj_pvt) (PROCEDURE_NAME=oe_line_adj. c) The Attribute Mapping Method was not ATTRIBUTE MAPPING. but still Attribute is not sourced. If the attribute that is linked was a new one. 6 Attribute Mapping setup is correct and the flags are set. While in Attribute Linking and Mapping window. > spool off 3 The following error occurs while running Build Attribute Mapping Rules concurrent program: ORA-04021: timeout occurred while waiting. If the seeded sourcing rule causes this error. Determine whether any custom sourcing API causes the errors. This occurs when someone makes a pricing call while the concurrent program is running. But the Attribute Mapping status box of the attribute that I just linked is still unchecked.calculate _adjustments) (ERROR_TEXT=calculate_adjustments#130 ORA-06508: PL/SQL: could not find program unit being called).

This program will clear used in setup and attribute source status flags for the attributes which are not used in the setup. 9 Inactivated the Pricing setup. used in setup flag is still set. it will source all the attributes irrespective of the attribute is used in active pricing setup or not. but still Attribute Sourcing Status checkbox is not checked. But. Build Attribute Mapping Rules uses the profile option QP: Build Attributes Mapping Options. if attribute is not used in active pricing setup. If Attribute Mapping Method=‟ATTRIBUTE MAPPING‟. c) Attribute Mapping Status is set to yes. but still used in setup and attribute sourcing status flags are set for the attribute. Please run Build Attribute Mapping Rules concurrent program. You will need to run „Build Attribute Mapping Rules‟ concurrent program. Active Checkbox is checked for Price list/Modifier/Formulas setup. if the attribute is used in active pricing setup. please check the following: a) Used in Setup is set to yes. How do I source all attributes even if they are not used in active setup? Attribute Management in Advanced Pricing Page 34 . sourcing rules should be defined for both Header and Line level. please check the Custom Sourcing Package and API call defined in sourcing rule is valid and works fine and profile QP: Custom Sourced is set to Yes. User will need to run Build Attribute Mapping Rules concurrent program to set Attribute Mapping Status flag. and if profile option QP: Build Attribute Mapping Options is set to „Map attributes used in active pricing setup‟. If Level is BOTH. please check enabled flag is checked for attribute sourcing Rules and seeded value string and user value string are valid at Header and Line level depends on the mapping level defined. Build Attribute 8 I removed the attribute from Pricing setup. e) For the request type. 7 While pricing setup. ONT). If the value is set to „Map all attributes‟.e. If value is set to „Map attributes used in active pricing setup‟. f) Run Attribute Mapping Rules Error Report to check the Errors in sourcing rules. If Attribute Mapping Method is „CUSTOM SOURCED‟. It will clear used in setup and attribute source status flags. i..application and custom package respectively. b) Attribute Mapping Enabled is set to yes. the attribute is mapped dynamically. Dynamic attribute mapping sets the used_in_setup flag for the attribute in attribute mapping. 10 Running Build Attribute Mapping Rules concurrent program only sets attribute sourcing status flag for the attribute used in setup. d) Sourcing Rules have been defined for the request type (Ex.

/*The following is sample API call.Mapping Rules program will source only attributes which are used in the active setup. etc) and run Build Attribute Mapping Rules concurrent program. Please check the following: a) Check QP_BUILD_SOURCING_PVT package body source and check the problematic attribute is sourced. Attribute Management in Advanced Pricing Page 35 . c) Please check the sourcing rule is valid and the API returns the expected value for the input value passed from calling application in SQL Plus* prompt. This profile can be controlled only at the SITE level. please check Active flag is checked for the Pricing Setup (Price list/Modifier/Formula. If so. BEGIN --Please input appropriate values. 13 Attribute Mapping and Sourcing Rules setup are correct and ran Build Attribute Mapping Rules program. Please check the Custom attribute sourcing procedure QP_CUSTOM_SOURCE. For PL/SQL Multi-record API type. Please replace it with the API call you want to Validate and input appropriate values. Please check Profile option QP: Build Attribute Mapping Options value is set to „Map attributes used in active pricing setup‟. still attribute is not sourced. please use the anonymous PL/SQL block to check API as follows: //Block starts. 12 Attribute Mapping Method is set to „CUSTOM SOURCED‟ and Build Contexts failed during call to pricing engine. l_appl_id). but used in setup flag is not set. please verify the attributes have been passed to the pricing engine through Pricing Engine Request Viewer and the value passed for the attribute is correct and NOT NULL. 11 Attribute is used in pricing setup. FND_GLOBAL.t_multirecord. But. SET serveroutput ON DECLARE l_bg_tbl qp_attr_mapping_pub. l_resp_id.apps_initialize(l_user_id.Get_Custom_Attribute_Values is defined and is not throwing any exception/error. b) In calling application. Please also check OM debug log with level 5 and check any exception is thrown while invoking a call to the custom procedure.

Is there any standard patch available? Please apply Patch#2597461 and Patch#2603770.get_buying_groups (&party_id. and there are few corrupted seeded attributes. Attribute Management in Advanced Pricing Page 36 .first.SEGMENT_ID.PRC_CONTEXT_TYPE. If it is seeded.API does not return any value for the input Value. and seeded_value_string and user_value_string values.5. Also check the seeded attribute sourcing rules are enabled by executing the following query: select count(*) from qp_attribute_sourcing where seeded_flag='Y' and enabled_flag='N'. B. Please execute the following SQL to get attribute mapping and sourcing rule details of attributes defined in Qualifier/Pricing Attribute contexts and the Product context. please check API. A. &order_line_sold_to_org_id). END.USER_PRECEDENCE. 14 Customer upgraded to 11.7 and is on OM Family Pack H.SEGMENT_CODE CODE.PRC_CONTEXT_CODE. A.Check the value(s) returned from the API. B. //Block ends. Attribute Mapping Details :SELECT A. If it is custom API. IF l_bg_tbl. please log bug against appropriate product who owns the API.. END IF.SEEDED_FLAG SEEDED_CONTEXT.l_bg_tbl. END LOOP.*/ l_bg_tbl :=ams_qp_qual_pvt. ELSE -.ENABLED_FLAG CONTEXT_ENABLED. Please check Enabled_flag is set to Y for all the seeded sourcing rules.last LOOP -.count > 0 THEN FOR i in l_bg_tbl. A. 15 Need to check seeded/custom defined attribute mapping and sourcing rules are valid after upgrade. B.

C. 'PRICING_ATTRIBUTE') AND B. C.SOURCING_STATUS SOURCE_STATUS. A. C. Attribute Management in Advanced Pricing Page 37 .SOURCING_ENABLED SOURCING_ENABLED.PRC_CONTEXT_ID AND C.B.PTE_CODE = &pte_code ORDER BY PRC_CONTEXT_TYPE.SEEDED_FLAG SEEDED_ATTRIBUTE. C.PRC_CONTEXT_CODE. C. B. B. C.USER_SOURCING_METHOD SOURCING_METHOD.LIMITS_ENABLED LIMITS_ENABLED. 'QUALIFIER'. Attribute Sourcing Rules details :SELECT A.LOV_ENABLED LOV_ENABLED. QP_SEGMENTS_B B. A. A. C.USED_IN_SETUP USED_IN_SETUP.AVAILABILITY_IN_BASIC AVAIL_IN_BASIC FROM QP_PRC_CONTEXTS_B A. B.ENABLED_FLAG. C.REQUEST_TYPE_CODE.PRC_CONTEXT_TYPE. QP_PTE_SEGMENTS C WHERE A.PRC_CONTEXT_TYPE IN ('PRODUCT'.SEEDED_SOURCING_METHOD.SEGMENT_MAPPING_COLUMN COLUMN_MAPPED.SEGMENT_ID AND C.SEGMENT_CODE.SEGMENT_MAPPING_COLUMN.SEGMENT_LEVEL LEVEL_CODE. C. B.PRC_CONTEXT_ID = A.PRC_CONTEXT_CODE.SEGMENT_ID = B.

PRC_CONTEXT_TYPE IN („PRODUCT‟.USER_SOURCING_TYPE.PRC_CONTEXT_ID = A. Check the Concurrent Manager requests to see if the request was completed as Normal. QP_SEGMENTS_B B.SEEDED_SOURCING_TYPE.SEGMENT_ID = B. 'QUALIFIER'. One of the following solutions may resolve the issue:  The only contexts that will show up in the OM Sales Order Pad are the ones that have at least one attribute that is USER ENTERED.SEGMENT_CODE.SEGMENT_ID ORDER BY A. B. Remember. C.PRC_CONTEXT_TYPE. C. C. all attributes of type Pricing Attribute will get created in the OM Flex field and the flex field will get registered (if required). C.REQUEST_TYPE_CODE.USER_VALUE_STRING. Columns updated in Flex field window are also not supported in Pricing. 16 The context of an attribute that was successfully mapped did not show up in the Order management Sales Pad Pricing Context list of values. If the context has all its attributes as mapping method ATTRIBUTE MAPPING. QP_ATTRIBUTE_SOURCING C WHERE A.ENABLED_FLAG FROM QP_PRC_CONTEXTS_B A. A. C.  Attribute Management in Advanced Pricing Page 38 . this context will not show up Pricing Context List of values. An attribute created using the Flex field windows will not get created in the Attribute Manager tables.SEEDED_VALUE_STRING. 'PRICING_ATTRIBUTE') AND AND B. Using this method.C. the converse is not true. its definitions will freeze and then get compiled automatically. C.ATTRIBUTE_SOURCING_LEVEL.PRC_CONTEXT_ID C. You must create all new attributes using the new Attribute Manager Context and Attributes window.PRC_CONTEXT_CODE.

which has Attribute Mapping set to „ATTRIBUTE MAPPING‟.9 or later. If package does not recompile and it is oracle provided package. please recompile all INVALID objects. Please see Using Custom Sourced Attributes section for a sample custom sourcing procedure implementation.  Please run Attribute Mapping Rules Error report and verify if there are any errors.   18 Attribute Mapping of an attribute is „CUSTOM SOURCED‟. If QP: Custom Sourced profile is set to Yes and if the error occurs in Custom Procedure. Please check customer is using custom attributes and custom sourcing rules. but this attribute is not sourced correctly. please run „Attribute Mapping Rules Error Report‟ and specify request type optionally. Check report output for attribute sourcing rule errors if any.   19 Is there any report. please advice customer to verify and correct the error. where can I find the document details? 21 Build Attribute Mapping Rules concurrent program throws error with User Defined Exception. and recompile the package. This report will output errors in sourcing rules only for the attributes.5.17 PL/SQL: could not find program unit error message is recorded in OM Debug log file and no attributes sourced.9. please check if any patch is available to resolve the package error. For release prior to 11. Please check Profile QP: Customer Sourced is set to Yes for custom sourcing attributes. If any INVALID Objects found. Please check Custom Sourcing Procedure is valid and attributes have been sourced correctly.  Attribute Management in Advanced Pricing Page 39 . which identifies errors in Attribute sourcing rules? In Release 11. Please check dba_errors table for errors logged in one of the packages used in sourcing rules. Invalid HVOP Attribute: QP_BULK_PREQ_GRP. If not please log SR. please refer to „Intercompany Invoicing and Advance Pricing Integration‟ white paper in MetaLink. Check the error. For details on „Intercompany Integration with Advanced Pricing‟. Please refer to Pricing Implementation Guide on how to custom source attributes.  Please check all the database objects are valid.5. This report verifies the packages used in sourcing rules are valid in database and if any file dependencies are missing.G_LINE_REC. Please set QP: Pricing Transaction Entity and QP: Source System code correctly before creating pricelist/modifier so that the contexts/attributes linked to the „Intercompany Transaction‟ PTE will be available in LOVs in Pricing setup forms. please see the diagnostic script provided in Attribute Management Diagnostic scripts section. Please verify the custom sourcing rules are valid and the parameters passed to the custom souring rules. 20 For troubleshooting Intercompany invoicing with Advanced Pricing issues.

Please check if there are custom contexts attached to the PTE and verifies the sourcing rules of the custom attributes are valid. For troubleshooting. Locate the custom context in PTE and click on Link 23 How to exclude attributes being included in QP_BUILD_SOURCING_PVT package build by Build Attribute Mapping Rules concurrent program? Attribute Management in Advanced Pricing Page 40 . Responsibility Id (LOV) .Select responsibility id 2. Please refer to Bug# 4709496 for details.1 and run Oracle Advanced Pricing Attribute Mapping Rules Data Collection Test at the customer instance with following options: 1.INV OICE_TO_PARTY_ID Call AD_DDL to create BODY of package QP_BUILD_SOURCING_PVT_TMP Parameters should be valid columns and not the entire structure. Navigation: Pricing -> Setup -> Attribute Management -> Attribute Linking and Mapping. please uncheck „Attribute Mapping Enabled‟ checkbox for the custom attributes in the custom contexts attached to the PTE and run Build Attribute Mapping Rules concurrent program. Verify if the issue still exists. Request Type Code (LOV) -Select ONT (for ex.G_LINE_REC.No Check the report output for contexts/attributes have seeded value 'No'.Build_Contexts API in Custom Contexts attached to the PTE. Please perform the following steps: a) Identify Custom contexts/attributes: If context and attributes to be excluded are not known.INVOICE_TO_PARTY_ID Invalid HVOP Attribute: QP_BULK_PREQ_GRP. Please refer to Bug# 4709496 & 4887583 for more details.) 3. Show Rules With Errors Only (LOV) . ERROR in creating PACKAGE BODY: QP_BUILD_SOURCING_PVT_TMP 22 Problem in QP_Attr_Mapping_PUB. please see MetaLink note: 363052. b) Uncheck attribute mapping enabled checkbox for all problematic attributes in the problematic custom contexts manually.

1 This test provides details of attribute mapping rules. Uncheck Attribute Mapping Enabled checkbox for all custom attributes and save.Attributes button. the features and the required setup in the application.1 . Repeat step b for all other custom contexts and attributes.How To Know If Attribute Mapping Was Successfully Built? ORACLE DIAGNOSTIC SCRIPTS FOR ATTRIBUTE MAPPING ISSUES Attribute Mapping Rules – Note 363052. Using these features successfully requires an understanding of the business process. Attribute Management in Advanced Pricing Page 41 . Usage of attribute management for product.1 . d) Run Build Attribute Mapping Rules concurrent program and verify it is completed successfully. It can be run for a single request type such as ONT or for all request types. All details and link to download can be found on the Note 363052. Use this test to find the attribute mapping rules that are invalid.1 . In fact this feature is also called as an extension of Advanced pricing because of the flexibility it provides. qualifier and pricing attributes provides powerful and flexible capabilities within Advanced Pricing.How to custom source pricing attributes QP_CUSTOM_SOURCE. Attribute Management provides flexibility for Pricing setup for various business needs. NOTES 1) 374963.1 CONCLUSION As detailed above.1 .Get_Custom_Attribute_Values 2) 209471.Tables Associated with Attribute Mapping 3) 209407.How To Diagnose Attribute Mapping Issues 4) 209472. c) Run Attribute Mapping Rules Error report to see if there are any sourcing rule errors reported.

650.7200 www. All other product and service names mentioned may be trademarks of their respective owners.oracle.S.com Oracle is a registered trademark of Oracle Corporation. Worldwide Inquiries: Phone: +1.506.ORACLE Attribute Management in Advanced Pricing Revised May 2010 Author: Ananthalakshmi Anbuselvan Co-Author: Kelli Stone Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores.506. Various product and service names referenced herein may be trademarks of Oracle Corporation.650. . Copyright © 2002 Oracle Corporation All rights reserved. CA 94065 U.7000 Fax: +1.A.

Sign up to vote on this title
UsefulNot useful