Headless Configuration Business Service Method ApplyPromotionDefaults Does Not Do Same As When The UI Applies Promotion Defaults
Last updated on MARCH 02, 2017
Applies to:Siebel Communications - Version 184.108.40.206 SIA to 220.127.116.11 SIA  [Release V8]
Information in this document applies to any platform.
***Checked for relevance on 02-02-2016***
The “Headless Configuration" business service method "ApplyPromotionDefaults" produces different results when invoked by a script instead of the UI. The attributes are being set incorrectly.
For example, take the following:
Attribute: Test Attr
Enumerated with values A,B,C.
Class: Test1 with above attribute.
Simple Product: Child C1
Complex Product: Root with above product.
Promotion: Test Promo with above product. Set exclusions so attribute can only be C.
In the UI, add the promotion to an order. The attribute on the root is set to C.
Run script to add the promotion etc to an order (see example below), the attribute on the root is set to null.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms