RIB PublishTime Field Validates More Than Three Characters Time Zone Formats
(Doc ID 2427388.1)
Last updated on MARCH 09, 2019
Applies to:Oracle Retail Integration Bus - Version 16.0 and later
Information in this document applies to any platform.
RIB Publish Time field in all the outbound messages from Oracle Retail Merchandising System (RMS) are produced with date timestamp and timezone and these are based on the data definitions (XSDs).
However, it appears that there is a validation on the Publish Time wherein when the message is published from RIB to JMS topic, it does not cause any issue, but it causes a validation issue when an external system consumes the message from JMS topic using the same XSD.
So can a modified XSDs be provided which will be in sync with the XML produced (that is without any validation XML produced with 4 char such as AEST)?
Or is it possible the when the message is published from RIB to topic the XSD is not referenced?
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