My Oracle Support Banner

Eligibility & Compatibility Rules Not Recognizing Product With 'Delete' Action Code (Doc ID 1608442.1)

Last updated on AUGUST 09, 2020

Applies to:

Siebel Quotes - Version [IP2013] and later
Information in this document applies to any platform.
***Checked for relevance on 02-Sep-2016***
***Checked for relevance on 07-Sep-2018***
***Checked for relevance on 04-Aug-2020***


Compatibility rules are violated when you modify an asset and have 2 child items which are incompatible. One of them is the old one from the asset and was replaced by the new one. So we have 2 lines with action codes Add and Delete.

Verify on Order level generates a wrong compatibility message.

Create the following products:
Simple Products: SP1, SP2
Customizable Product: CP1
Promotional Product: Promo1

Where, SP1 & SP2 is a child of CP1.

Promo1 has min/max/default=1 of product CP1.

Structure is:

| |--SP1

On SP1, create a Compatibility Rule where "SP1 excludes SP2"

Steps to Reproduce Issue:

1. Create an Order and add Promo1 with CP1 and SP1, then Autoasset.
2. 'Modify' the promotion and product to create an Order.
3. In eConfigurator, remove SP1 and add SP2, then exit eConfigurator. We will see the Action Codes for SP1 and SP2 as 'Delete' and 'Add' respectively, which is correct.
4. 'Verify' the Order. UNEXPECTED behavior is if you check 'Eligibility Status' field it will be 'N' for both SP1 and SP2 which is incorrect. You also see Eligibility messages for both:

SP1: SP1 excludes SP2 (via rule SP1 excludes SP2)
SP2: SP2 excludes SP1 (via rule SP2 excludes SP1)

The elibility & compatibility engine does not seem to recognize that SP1 has an action code of 'Delete'.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.