PIM : Multiple items created with the same GTIN when running multiple item import jobs for the same item at the same time
Last updated on MARCH 08, 2017
Applies to:Oracle Fusion Product Model - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Multiple Items created that have the same GTIN
According GDSN standards, every item is uniquely identified by the GTIN. It turns out that if the same GTIN is received twice at the same time during import, the system is creating 2 separate items with the same GTIN. Currently several occurrences of this situation have been identified in test environment for which the same GTIN is used for multiple items. That is of course an undesired situation.
This issue seem to be caused by imports for the same GTINs that run simultaneously. Situations like this could occur if a supplier publishes an item through the data pool and directly decides to make a small correction to the information that he just published. In situations like that we trigger 2 imports for the same GTIN at the same time.
Expectation in situations like this is that 1 of the 2 items is created and that the other item results in a user error explaining why the item was not imported. Need an option to (automatically) re-process the file in order to update the existing item.
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