Oracle BRM - my understanding

Oracle BRM is more of a tool utilized by a communication industry to
bill their customers based on the usage of the services they offer.3

Unlike oracle application, BRM has separate tool like for each operations (like Customer Centre, Payment Centre).
BRM is a 4 tier architecture and needs more of technical intervention to understand the product.

Originally it was called as Portal, and after Oracle bought it renamed to "Oracle BRM".

Oracle BRM has standard adapter to Seible CRM for Customer centre, and can be integrated to other CRM using AIA.
so most of the BRM users do not use BRM's Customer centre.

My understanding is any customer based organization needs to address their customer complaints (like iSupport module in Oracle) so mostly they always have a very powerfull CRM tool, so having a separate customer centre does not solve their purpose. So most of the customer implements BRM with the integration with their CRM.
::::::::::::::::: Continues....

iSupplier Registration - Table

The table that stores the newly registered Supplier through iSupplier registration link is POS_SUPPLIER_REGISTRATION.

I guess this table has some extra columns in R12. Please check in metalink.

OA - Enabling 'About this Page' Link

Setting the profile FND: Diagnostics to Yes enables the About this Page link in any OA Page.

iSupplier Registration Error - POS_REG_UNEXPECTED_ERR

In iSupplier portal, I have tried to register the Supplier User using Supplier Profile Administrator and faced the below error,

We're sorry, but the service you requrested is not available at this time. Please take down the following error message and contact your system administrator: POS_REG_UNEXPECTED_ERR0_11_1_4
I was very confused by the above error, did metalink search. Got 6-7 hits.
and finally the below set up has resolved the error.

'HZ: Generate Party number' to Yes at the responsibility level has resolved the error.

Advanced Pricing - Attribute Management

I have got a requirement which forced me to learn about the Attribute management in Oracle Advanced Pricing.

There is Qualifier context for Item Name and Item Category. Our issue was, we had two different set of items in the same category and the intention is to apply the modifier to one set of items and not to the other.

But the good thing is the naming convention differenciates the item types. i.e one set of item has '_L' in its name.

For example PR and PR_L. PR belongs to one set and PR_L belongs to the other.
For any attribute mapping, you should be sure under which context you have create the new attribute, and obviously in this case it has to be Qualifier Attribute.

So Create a new Qualifier Context,
Oracle Advanced Pricing --> Set Up --> Attribute Management --> Context and Attributes.


Context :
Type : Qualifier Context
Code : User Defined Value
Attribute :
Code : Qualifier Attribute Code
Name : Qualifier Attribute Name
Column Mapped : Select the available Attribute Column.
Valueset : If you want the user to restrict the values to be entered.

Now the Attribute is ready and now comes the attribute Mapping.
Oracle Advanced Pricing --> Set Up --> Attribute Management --> Attribute Linking and Mapping.
Pricing Transaction Entity : Order Fulfillment
Context Type : Qualifier Context
Select the context that you have created in the above steps --> Link Attributes.
Select the Level ( Line or Header or Both), The attribute Mapping method is : Attribute Mapping.

Once you have selected the Attribute Mapping, the Attribute Mapping button is enabled.Click on it.

Select your Application name and request type.
I am concentration on OM, as my pricing call will be made from there.
Select the User Source Type as PL/SQL API and User Value string as the call to your custom package.

In my case, XXX_RETRIEVE_ITEM.GET_BASE_ITEM(OE_ORDER_PUB.G_LINE.ordered_item)
Peseudo Code for XXX_RETRIEVE_ITEM.GET_BASE_ITEM(OE_ORDER_PUB.G_LINE.ordered_item)
If (OE_ORDER_PUB.G_LINE.ordered_item has '_L' in its name )
RETURN 'FALSE'
ELSE
RETURN 'TRUE'

The very mandatory and important step after all this is, running the Build Attribute Mapping concurrent program.

So all my new Qualifier is ready to use now.

To make sure that the modifier is getting applied only to the non '_L' item, I have to define qualifier like this