Why Is the Default RTV Location Not Used when Saving a Return to Vendor (RTV) in Purchasing and How To Resolve the Errors "Invalid location found. (10302,97)" and "The conversion rate for item XXXXX, UOM , and UOM type STCK does not exist. (11100,112)" (Doc ID 1344455.1)

Last updated on AUGUST 04, 2016

Applies to:

PeopleSoft Enterprise SCM Inventory - Version 8.9 and later
PeopleSoft Enterprise SCM Purchasing - Version 8.9 and later
Information in this document applies to any platform.

Goal

You can define a Default Return to Vendor Storage Location (navigation: Inventory, Maintain Storage Locations, Default RTV Location) and according to the PeopleBooks (see extract below), that default Storage Location should used by the system as the Picking Location when no Storage Location is defined on the RTV.

PeopleSoft Enterprise Inventory 9.1 PeopleBook > Structuring Inventory > Defining and Maintaining Material Storage Locations > Defining a Default Return to Vendor Location

Define a default return to vendor (RTV) location for a business unit. The system uses this material storage location as the picking location for the RTV stock requests when no picking location is defined on the RTV ID created in PeopleSoft Purchasing. In most cases, this default RTV location is defined as your inspection area or the location where you place rejected stock.


However, the below errors are issued when saving a Return to Vendor (RTV) (navigation: Purchasing, Return To Vendor, Add/Update RTV) and no Storage Location has been selected for a line:

Warning -- Invalid location found for Inv BU XXXXX and item XXXXX. (10302,97)

The distribution row value combination is invalid for the Inventory BU.

and 

The conversion rate for item XXXXX, UOM , and UOM type STCK does not exist. (11100,112)
The conversion rate for the specified item, unit of measure, and unit of measure type does not exist

  

Why is the Default RTV Location not used and how to resolve the above errors?


Note that similar errors are issued when the Item is not Staged Date Controlled and you leave the Stage Date field blank > this is being addressed by the fix for <Bug 20106239> > see Knowledge <Document 2028537.1>.

Solution

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