Depot Repair Does Not Enforce Locator Uniqueness For Dynamically Created Locators (Doc ID 2072004.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Depot Repair - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Setup of orgs, subs, locators

ACTUAL BEHAVIOR
---------------
Locator Field allows to enter segments+ Slashes and save to create Locator Records

This issue occurs with Project Manufacturing enabled in EBS. So the Stock Locators KFF has ROW/RACK/BIN/PROJECT/Task segments.

The 'Locator' Fields are available across modules,e.g. Inventory, Field Service, Depot Repair, etc. When entering Locator values, normally it will pop up a Locator window and force you enter Row/Rack/Bin/Project/Task segment values Separately and then there is validation against the Locator value
uniqueness. With Locator Uniqueness, The first 3 segments of the locator (row/rack/bin) have to be unique across subinventories. If the combination of these 3 segments already exists in one subinventory, it cannot exist in another.

But in this case, Depot Repair (logistics) allow to enter Row number+ slash + Rack number + Slash + Bin number + Slash+ Project name + Slash + Task number and save.
The Locator PopUp window is NOT opened and no validation takes place that says the physical locator (first 3 segments) already exists in another subinventory.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
enter Row number+ slash + Rack number + Slash + Bin number + Slash+ Project
name + Slash + Task number and save. The Locator Pop windows is NOT open.

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