RTV Data Requirements
Return to vendor data (RTV.csv
) is used to capture returns of inventory from your stores or warehouses
back to the original vendor. An RTV is a transaction that decreases your owned inventory at a location because you are shipping
units to a non-owned location. RTVs are used only in Planning and RI applications.
Rule | Explanation |
---|---|
Supplier IDs, Reason Codes, Status Codes |
All of the reason code, supplier number, and status code fields in an RTV record are optional and used only for RI reporting purposes, because planning applications do not report at those levels. If you are not specifying these values, leave the columns out of the file entirely, and a default value of -1 will be assigned to the record in those columns. |
Positive and Negative Values |
RTV transactions should always be positive values. Only send negative values to reverse a previously-sent transaction in order to zero it out from the database. |
In most cases, you will be providing the same set of RTV columns for any application. These columns are listed below with additional usage notes.
Column Header | Usage |
---|---|
ITEM |
Must be the transaction level item or SKU number and must have a record in the |
ORG_NUM |
Must be the location number where the RTV is being shipped out from. Must have a record in |
DAY_DT |
The date that the RTV occurred on. RTVs can occur on any date both in history and nightly batch files. |
RTV_QTY RTV_COST_AMT_LCL RTV_RTL_AMT_LCL |
The units and total cost/retail values for the returns to vendor. |
LOC_CURR_CODE DOC_CURR_CODE |
The currency codes linked to the cost and retail amounts on the RTV data. The values
in these fields will control how the system converts the amount (such as |