Discrepancy In Creating The Partners From Front End And Loading Through DC Tool.
(Doc ID 2931532.1)
Last updated on FEBRUARY 28, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version NA and laterInformation in this document applies to any platform.
Symptoms
Discrepancy in creating the partners from front end and loading through DC Tool.
ACTUAL BEHAVIOR
---------------
The data conversion allows us to load the records into MFCS for mandatory address types -02,05 with primary address indicator as ‘N’.
While for records created from front end, we need a primary address invariably for each address type.
EXPECTED BEHAVIOR
-----------------------
DC tool to handle mandatory address for every address type
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Load the Partner via DC tool with mandatory address types -02,05 with primary address indicator as ‘N’.
2.Check if DC tool allows to load data with primary address indicator as ‘N’ for mandatory address types
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, loading partner via DC tool is different
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! |
In this Document
Symptoms |
Cause |
Solution |
References |