Enhancement Request So REST APIs Only Update Attributes That Are Part of the Message (Doc ID 3052617.1)

Last updated on OCTOBER 09, 2024

Applies to:

Goal

Enhancement request:

1) Describe how the current product functionality is insufficient:
Some retailers have multiple systems and Oracle Retail is not the parent for all the product information, i.e., in some cases some attributes are maintained in Oracle Retail and some other attributes for the same products are maintained in a legacy system (and the respective updates are communicated/integrated to Oracle Retail).
Also, some Legacy systems only send the attributes that actually changed (and not the whole Item information, which is quite extensive).
Oracle Retail Items REST API use JSON messages and, for the mandatory attributes, they really must be part of the message. But, for the non-mandatory attributes (which don't really need to be part of the message) , if not provided in the message (which would happen if they didn't change), the REST APIs are wiping out these attributes from the Item information in MFCS, leading to loss of information.

2) Provide a detailed description of the Enhancement Request:
The Item REST APIs should only update the Item attributes which are part of the message - for the attributes which are not part of the message, they shouldn't be touched and the same values should continue in MFCS.

3) Describe how this Enhancement will benefit your business:
The customer will be able to update the Item information, only for the attributes that changed in the Legacy system, and integrate them to MFCS without wiping out all the other attributes that didn't change.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.