RTVReqToRTVReqLocTAFR

Overview

Return To Vendor Requests (RTVReq) messages are published by a merchandizing system (RMS) to return goods to the vendor. These messages are subscribed by the store inventory systems (SIM).

RTVReqToRTVReqLoc Tafr filteres the messages based on the configurations settings of StoreSystemActive and StoreSystemToLocLoc and routing info type To_Phys_loc_type. If To_phys_loc_type is not equal to “s” and the configured properties are not true, the message will be filtered.

In addition, this message is also responsible to “delete” items by setting them to a 0-shipped quantity.

Functional Requirements

routing info to_phys_loc: The routing information for the message is supposed to contain the to_phys_loc specification. The message is considered to be in error, if the message does not contain to_phys_loc specification in the routing info.

StoreSystemActive: Outbound messages are dependent upon a configuration setting for StoreSystemActive. Messages will not be published if the configuration property is set to false.

StoreSystemRouteToToLoc: Outbound messages are dependent upon a configuration setting for StoreSystemRouteToToLoc. Messages will not be published if the configuration property is set to false.

routing info detail value: The routing info of the input message, contains a routing info detail with a dtl_name equals “TO_PHYS_LOC_TYPE” and value equals “s”. The message will not be published if the routing info detail value is not “s”.

Disclaimer: This document is a general data mapping and reference guide for data coming in and out of Oracle Retail application systems via RIB messages; it is not meant to give detailed information about every possible data scenario.