Please consider the environment before printing this Page. Go Eco.
Powered by MaxBlogPress 
Home » Order Management, Siebel Pricing

Basics of Variable Maps

18 November 2009 428 views One Comment



I am back with yet another post and this time it’s Variable Maps :-) Variable Maps are nothing but the property sets that define the structure of data to be passed to the Pricing Procedures; based on which the price calculation is done. Variable maps are used by the PSP engine to build the context and Row Sets.

Img1

A variable map is defined under Administration -> Order Management in the application.

It consists of a list of variables

Each variable has one or more variable sources that define how to retrieve the variable value in a given mode (such as Quote, Order, or Any).

The source type of a variable source can be a business object query, the active business component instance, a business service, a profile attribute, a system preference, or a server parameter.

Img2

The Pricing Procedures are built to be used in a reusable fashion hence are designed to be invoked from multiple active business components. To get aligned with this at runtime, the variable is mapped with multiple sources with different modes.

Img3

Mode in a variable source indicates the source business component. The value “Any” for mode indicates the default variable source to use for a business component

Path entry in the variable source indicates the integration component and field

Img4

To modify an existing variable map or to add a new variable to it, user needs to first lock the variable map record, drilldown on the Workspace hyperlink. Make changes as desired like either change something in the existing record or add a new record by clicking on New button. Add mode, path and source type in the variable source section for the variable. Once you are done with the changes then release the next version to apply the changes made to the variable map.

SocialTwist Tell-a-Friend

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Your Ad Here

Your Ad Here
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

One Comment »

  • Elizabeth Hodges said:

    You have not covered how the user should discover which IO they need to change for which BC (Mode) , perhaps it would be helpful to include a reference to the BC user property “Instance Uniform Name EAI Object:” and the BC user property “Mode”, as ISS Quote shown in your screenshot is not the only IO used.

Leave your response!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <font color="" face="" size=""> <span style="">

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.