Siebel Business Process & Functionality (MOSC)

MOSC Banner

Compatibility rule in modify order scenario

edited Dec 16, 2016 12:13AM in Siebel Business Process & Functionality (MOSC) 1 commentAnswered
Client have implemented catalog selection via catalog. They have a product compatibility rule where one product (Topper Pay Pack) excludes a second product (Topper Free) on version 7.8.2.2 SIA of the application. Have a order containing one of the existing products with action code as “-“(Topper Pay Pack). When you add the second product (Topper Free) to the order you find that the compatibility rule is not working the second product. The second product has an incorrect eligibility status showing as “Y" in the applet.
Note: If order containing one of the products with action code as “Add“(Topper Pay Pack). When you add the second product (Topper Free) to the order you find that the compatibility rule is working for the second product. The second product has a correct eligibility status showing as “N" and Eligibility message is Topper Free excludes Topper Pay Pack (via rule Topper Free excludes Topper Pay Pack) in the applet.

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