Invalid Database Field Type on RMS Future Delivery Allocation/Transfer/Order
Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Advanced Inventory Planning - Version 14.1 and later
Information in this document applies to any platform.
Interfaces that feed the tables I_RMSE_FUT_DELIV_ALLOC, I_RMSE_FUT_DELIV_TSF, and I_RMSE_FUT_DELIV_ORDER are expecting to receive as SUPPLIER and DESTINATION_CODE a number. In reality it should expect to be VARCHAR field as similar to what is defined in the SUPPLIER and STOCKING_POINT table. There is a misalignment between foundation data and those three interface tables. This is causing the batch to not pick the data and load it into the EXPECTED_RECEIPTS table.
Steps to Reproduce:
- Load the interface rmse_aip_future_delivery_order.dat by using the shellscript $INTEGRATION_HOME/scripts/import/ord_imp_rmse_fut_deliv_order_in.sh
- It will fail if the fields Source and/or Destination contain any character besides numbers as the schema file has defined those fields as just containing numbers:
[oretail@logicpt25 schema]$ cat ord_imp_rmse_fut_deliv_order.xml
- Tables are also expecting numbers on those fields, which is wrong.
The following errors are from the ord_imp_rmse_fut_deliv_order_in.log:
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