Fusion PIM: Matching On GTIN Fails when EDQP active and if Spoke Reference Deleted (Doc ID 2079334.1)

Last updated on MARCH 11, 2016

Applies to:

Oracle Fusion Product Model - Version 11.1.9.2.0 and later
Oracle Fusion Product Hub Cloud Service - Version 11.1.9.2.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.9.2.0 version, Import Items

ACTUAL BEHAVIOR
---------------
GTIN matching capability having brought up EDQP server links if spoke reference deleted.

EXPECTED BEHAVIOR
-----------------------
GTIN matching should work per spec

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
PDM: data pool connector tool.
Product Source Doc: excel sheet that generate a XML that can be imported using import maps.
Import an item from the Product Source Doc.
This item is imported and created in the product hub.
Now we import an update to the same item from PDM. We expect that system uses the GTIN to find a match. However, the second batch contains items with a match status ‘No Match’.
For testing purposes site used the same XML message, but use different spoke systems for the import.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms