Fusion PIM: Matching Only In Product Hub Still Requires The Generation Of The Semantic Key In EDQP (EGP-2775859)
Last updated on MARCH 11, 2016
Applies to:Oracle Fusion Product Hub - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
We have just configured Enterprise Data Quality for Products (EDQP) to work with our Fusion Product Hub (FPH) environment.
FPH has been enhanced in R8 with matching capabilities. It allows you to use match on GTIN and trading partner items.
The matching is done FPH and it does not use EDQP. For Ahold it means that we will only use EDQ-P for standardization of the data, but not for matching.
However, the current integration still assumes that the semantic key is generated by EDQP resulting in a error condition. Is there a way to work around this ?
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