Retail Publisher – Requirements For Error Code & Description
(Doc ID 2965180.1)
Last updated on AUGUST 01, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version NA and laterInformation in this document applies to any platform.
Symptoms
version 19.3.012
DESCRIBE THE PROBLEM (INCLUDE STEPS TO REPRODUCE).
==================================================
Retail Publisher API responds back with HTTP 200 with Syntactical check such
as envelope, rib-family, message characters and it does not provide detailed
information regarding the functional errors (if any). This becomes a
cumbersome and manual operation to identify any functional errors.
Current REST API exposed for RIB-EXT publisher does not provide any detailed
ERROR / Description in case of functional Errors
Once the API responds for example
https://<customer>-stage-ribcs-rib.oracleindustry.com/
/rib-ext-services-web/resources/publisher/publish - Response {"message":
"Publish done"}. It does not mean the message is Functionally Right with all
Business Validations, it merely states the message has been successfully
PUBLISHED. For example, if SupplierId or any other mandatory terms or other
missing inside the RIB-Message Envelope, currently the Integration team
relies on Manually checking it in RIB-Error Hospital in the UI and notifying
the publisher application team.
This does not help in communicating the remedial measure to the Publishing
application to correct the message for re-submission. It becomes a manual
task and not viable for Production volumes.
The above API should provide detailed information in case any Business Errors
while Inserting/Updating the message in the MoM tables.
Or
Above message should provide the identifier for response that can be queried
back with another Interface to know its actual functional status.
PROVIDE DETAILS ON WHAT IS BEING REQUESTED OF DEVELOPMENT OR PRODUCT
MANAGEMENT.
====================================================
Is is possible to provide a functional error or integration just pull and
push the data . main functional validations will be done at rib-rms
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 |