Siebel Business Process & Functionality (MOSC)

MOSC Banner

Asset Override eligibility issue with Account Type join field

edited Dec 16, 2016 12:13AM in Siebel Business Process & Functionality (MOSC) 2 commentsAnswered

Hi,


Customer is following the document Extending_Eligibility.pdf for the Asset Override functionality which is meant for the following requirement:

Extending Eligibility Rules: Asset Override

Requirement:
Existing assets shall always display in an eConfigurator session even though
an eligibility rule would make the product ineligible.

This is working fine if the Account Type is vanilla calculated field. But, customer is using a join as follows:

Asset Mgmt - Asset - Header

Name = Account Type
Join = S_ORG_EXT
Column = OU_TYPE_CD

After this change, it started throwing the eligibility error again, though the document steps are already used. Could you please kindly suggest a solution so that customer can avoid eligibility check on the existing products in the asset during modification.

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