Last updated on MARCH 11, 2016
Applies to:Oracle Fusion Product Model - Version 184.108.40.206.0 and later
Oracle Fusion Product and Catalog Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Manage Product/Service Data-Define Product
Change Order for pack changes does not use Change Order type effective Date setup (R9)
We defined a Change Order type “Change Order” in our setup that we use for all our changes that require approval (see screenshot). In the setup we have set the “Item Effective Date” option to “Effective immediately”. That does mean that on every Change Order we create the Effective Date attribute is not populated and as a result changes are applied upon approval. That is not working if we create CO’s for pack changes. These CO’s get their effective date populated with the date of tomorrow. That is not correct and as a result, changes are not implemented on the desired date. We expect that CO’s for pack changes will not populate the effective date.
CO’s for pack changes should not populate the effective date if CO type setup has “Item Effective Date” option to “Effective immediately”.
The issue can be reproduced at will with the following steps:
1. Setup CO type with effective immediately item effective date.
2. import pack
3. CO gets next day effective date
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