Last updated on AUGUST 18, 2016
Applies to:Oracle Fusion Product Hub - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
User is importing changes to the same item in master organization and child organizations. User has defined rules to put these changes on a change order.User expect that the system creates one change order with one line per item-organization combination during item import. But the system creates three change orders; one for each organization. The behaviour of the application has been changed since customer installed R8 patch bundle 10.
Before patch bundle, the system created one change order when the import option Change Order was set to . However, that seems to be changed.
Customer does not want to split change order. A change from the supplier should be verified in the context of the complete item. We are using the master organization for the common attributes and the child organization for the target market specific (country) attributes. When we receive a message from the supplier, we always get one record for the master and one record for the child org. It becomes very hard for Ahold to validate the changes when the changes are split per organization. There is no reason to do this because the data structure of the change order supports lines per organization.
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