Siebel Business Process & Functionality (MOSC)

MOSC Banner

Attribute Values wrongly being stored with the OLD Language Independent Codes. How can it be fixed?

edited Dec 16, 2016 12:09AM in Siebel Business Process & Functionality (MOSC) 5 commentsAnswered ✓

Hi,

After succesfully configuring Pricing with the use of Attribute Adjustments, I've come across an issue.

Please stick around and join me in this challenge.

The details:

I'm using 9 Attribute Definitions.

Those Attribute Definitions are being put to work in 3 Product Classes.

1 as the Grantparent Productclass (A),

1 as the Parent Productclass (B) and

1 as the Child Productclass (C).

The Attribute Values of an Attribute Definition are defined by/with the Language-Independent Code (LIC).

Each value then can be translated in the Attribute Value Display Names applet where you would define the Display Name/Display Value and Language.

Due to earlier design choices, the Attribute Values have to be overwritten with the Attribute Value Display Names. Thus making the Value the same as the Display Value.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center