My Oracle Support Banner

Field EXT_REF_NO In RTV_HEAD Is Up To 30 Chars But RTV Manage Webservice Is Up To 14 Chars (Doc ID 2962143.1)

Last updated on JULY 19, 2023

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version 23.1 to 23.1 [Release 23.1]
Information in this document applies to any platform.

Symptoms

When trying to send a RTV payload to MFCS the response says the externalReferenceNo field should be up to 14 chars but RTV_HEAD.EXT_REF_NO supports up to 30 chars.

Steps to reproduce:
----------------------
1. Create a simple payload (sample json file will be uploaded) where the "externalReferenceNo" attribute is bigger than 14 chars.
2. Send the payload (we are using suagger) /services/inventory/returnsToVendor/manage.
3. The response will say:
{
  "status": "VALIDATION_ERROR",
  "message": "Error found in validation of input payload",
  "validationErrors": [
  {
  "error": "size must be between 1 and 14 bytes",
  "field": "manage.arg0.items[0].externalReferenceNo",
  "inputValue": "12345678901234567"
  }
  ]
}

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


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