My Oracle Support Banner

ISS Promotion Asset Membership Compatibility Workflow Does Not Raise Compatibility Violation (Doc ID 2525943.1)

Last updated on MAY 06, 2019

Applies to:

Siebel CRM - Version 15.4 [IP2015] and later
Information in this document applies to any platform.

Symptoms

On : 15.4 [IP2015] version, Order Management

ACTUAL BEHAVIOR
---------------
ISS Promotion Asset Membership Compatibility Workflow does not raise Compatibility violation if there are multiple Member Instances within an Order.

EXPECTED BEHAVIOR
-----------------------
Raise Compatibility violation if there are multiple member instances within an order.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Setup Promotion Group as follows:

Promotion Group = PG Test Validate Member

|__Membership = PG Test Member Instance (Min 1, Max 1, Default 1)

   |__ Member = CP Test 1 (Min1, Max 1): Asset Member Compatibility = Y

|__Membership = PG Test Member Extension (Min 0, Max 5, Default 1)

   |__Member = CP Test 2 (Min 1, Max 1): Asset Member Compatibility = Y

   |__Member = CP Test 3 (Min 1, Max1) : Asset Member Compatibility = Y

 

1. Create Line Item for Member = CP Test 1

2. Create Line Item for Member = CP Test 2

3. Click Verify, which triggers Signal = QuotesAndOrdersValidate, which internal runs ISS Promotion Asset Membership Compatibility Workflow.

- Note that at this point those Line Items that have `Asset Member Compatibility = Y, are incompatible since they are not associated with any membership.

4. Create Line Item for Promotion Group = PG Test Validate Member. Line Items for memberships are created due to Default Cardinality

5. Associate CP Test 1 to PG Test Member Instance

6. Associate CP Test 2 to PG Test Member Extension

7. Click Verify >> Eligibility Reason is set to NULL for those line items that were created until step #3. This is now correct

8. Create Line Item for Member = CP Test 3, and click verify.

ISSUE: CP Test 3 should be incompatible at this point due to the following reasons:

i. Asset Member Compatibility = Y

ii. No association has been performed to a membership

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
 Input Arguments
 Output Arguments
References


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