Cross Reference is not created when collecting data - Returned Cross Reference Target value is the same as the Source value.
(Doc ID 1382821.1)
Last updated on JANUARY 11, 2017
Applies to:Oracle Fusion Global Order Promising - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 1.0]
Oracle Fusion Distributed Order Orchestration - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 1.0]
Oracle Fusion Planning Common - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 1.0]
Information in this document applies to any platform.
***KM Review - Dec 2016 - Checked for Relevance - Release 9 Specific***
We have attempted to perform a collection with cross referencing to existing data using Collections Web Service - mscCollConfigurationPublicService/CollDataLoadService. The data is collected, but this is not cross referenced, the source and target value are identical, and is the same as source Value submitted in the Collection payload
Instructions described in the following notes have been executed:
NOTE: 1684214.1 - How to perform GOP Collection For Shipping Service Levels
NOTE: 1525902.1 - How to perform GOP Collection For Unit of Measure (UOM) Cross Referencing
NOTE: 1540895.1 - How to perform GOP Collection For Payment Terms Cross Referencing
NOTE: 1521533.1 - How to perform GOP Collection For Currency Cross Referencing
NOTE: 1525491.1 - How to perform GOP Collection For Return Reason Cross Referencing
NOTE: 1525543.1 - How to perform GOP Collection For Invoicing and Accounting Rules
NOTE: 1514670.1 - How to perform GOP Collection For Freight Terms Cross Referencing
Followng the instructions in NOTE: 1525902.1 - How to perform GOP Collection For Unit of Measure (UOM) Cross Referencing, we observe that the following data is populated in the collected and cross reference tables:
We are expecting that the following data should be loaded into the collected and cross reference tables:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!