BDI Merch Hierarchy Dataset ID Processed Without Requesting its Start
(Doc ID 2888971.1)
Last updated on AUGUST 17, 2022
Applies to:Oracle Retail Integration Cloud Service - Version NA and later
Information in this document applies to any platform.
BDI Merch Hierarchy dataset ID was getting processed without requesting its start
After the execution of BDI process "MerchHier_Fnd_ProcessFlow_From_RMS", the expectation is that a new datasetID is available to be then processed. This processing is split in 4 different steps using dedicated rest service calls:
1) Get DataSetID
2) Start Processing (for a given DataSetID fetched in step #1)
3) Get Data (for a given transactionID fetched in step #2)
4) Set Status as completed (for a given transactionID fetched in step #2)
After the BDI process is triggered, it generates a new dataset for EXTERNAL application's consumption and it is imediately available by executing the rest service responsible on the above step #1. However, when the BDI process is concluded, the same datasetID is no longer available. The expectation is that the datasetID should only be made unavailable once step #2 is performed, however this was not the case.
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