My Oracle Support Banner

Product Constraints Not Working For Bulk Request While Updating Attribute Value (Doc ID 2369673.1)

Last updated on APRIL 24, 2018

Applies to:

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

Symptoms

On : 8.1.1.11.16 [IP2013] version, Order Management

ACTUAL BEHAVIOR
---------------
Attribute value is not being updated by Bulk request. 
However when configurator is launched and the attribute value is changed, it works. 


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Bulk Request with below details 

Users and Action 

Type = New 

Child Type = Service Id 

 

Action 

a) Sequence = 1 

Action = Add 

Base Product = MSISDN Number

 

b) Sequence  = 2 

Action = Update 

Base Product = MSISDN Number 

Attribute = Sub Category 

Value = 6

 

The base product MSISDN Number has a constraint which requires product A when the Attribute value is 6. 

However when then new order is created, the attribute value is not being set to 6. And the constraint is not being applied. 

If the constraint is inactivate then the attribute value is being set to 6.

 

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!


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