RMSAIASUB_SUPPLIER API Has Some Hardcoded Parameters Related to Supplier (Doc ID 2250585.1)

Last updated on APRIL 14, 2017

Applies to:

Oracle Retail Merchandising System - Version 14.1.2 and later
Information in this document applies to any platform.

Symptoms

When using RMSAIASUB_SUPPLIER API (meant for AIA/RFI integration from finance system like EBS) to create supplier in Oracle Retail Merchandising System (RMS) by populating the type RIB_SupAttr_REC with legacy data, results in different values as API RMSAIASUB_SUPPLIER_VALIDATE.CONSUME has a hard-coded values for certain columns.

Steps to Reproduce:

Prerequisite: PRODUCT_CONFIG_OPTIONS=A

  1. Use RMSAIASUB_SUPPLIER API and populate the type RIB_SupAttr_REC with legacy data for columns below:
    1. AUTO_APPR_INVC_IND
    2. FREIGHT_CHARGE_IND
    3. AUTO_APPR_DBT_MEMO_IND
    4. PREPAY_INVC_IND
    5. BACKORDER_IND
    6. SERVICE_PERF_REQ_IND
    7. BRACKET_COSTING_IND
    8. DSD_IND
    9. EDI_SALES_RPT_FREQ
    10. DELIVERY_POLICY
    11. VMI_ORDER_STATUS
  2. Observe hard-coded values are populated in respective columns in SUPS table in RMS.



Cause

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