RMS RTV API - Incorrect Field Length for RTV_ID and RTV_ORDER_NO in the FM_STG_RTV_DESC Table
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Retail Merchandising System - Version 14.1.2 and later
Oracle Retail Fiscal Management - Version 14.1.2 and later
Information in this document applies to any platform.
Whenever using the RMS RTV API (RMSSUB_RTV.CONSUME) , the value sent as RTV_ID in the RIB_RTVDesc_REC is a varchar2(14).
In a BR localized environment, this field gets persisted in the FM_STG_RTV_DESC table , in the field RTV_ID. This field however is a number(7) , returning ERROR when calling RMSSUB_RTV.CONSUME.
The field RTV_ORDER_NO is a number(10) , which is also different then the length in RMS, which si varchar2(14) must be updated as well, as it is also used during this procedure call.
Steps to Reproduce:
1. In a BR localized environment, create an RTV thru the RMS RTV API (RMSSUB_RTV.CONSUME)
2. Provide full length values for the RTV_ID and RTV_ORDER_NO values; varchar2(14)
3. An error will be returned when the data is persisted to FM_STG_RTV_DESC , as they are number(7) and number(10) for the RTV_ID and RTV_ORDER_NO.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms