PJM: Error 'Picking rule fails to find a source locator ...' in Transact Move Orders form (INVTOTRX) (Doc ID 1993958.1)

Last updated on DECEMBER 02, 2016

Applies to:

Oracle Inventory Management - Version 12.1.1 and later
Oracle Warehouse Management - Version 12.1.1 and later
Oracle Project Manufacturing - Version 12.1.1 and later
Information in this document applies to any platform.
Form: INVTOTRX.FMB - Transact Move Orders

Symptoms

When attempting to transact / allocate Requisition move orders through the Transact Move Orders form (INVTOTRX), the following error #1 and #2 get raised whereas there is enough available quantity for the item.

The issue is intermittent. Per users' perception it occurs randomly with no common pattern.

SETUP DETAILS
-----------------------
The issue has been reported with the following setup:
Organization is Project Manufacturing (PJM) enabled. It is not WMS enabled.
Locator Control is set to 'Dynamic entry' at organization level.
Allow Cross Project Issues option is enabled in PJM Organization Parameters form.
End Assembly Pegging is set to 'Hard Pegging'. (eg item is hard pegged)
Move Order Transaction Type is 'Move Order Transfer'.
Source and Destination Locators are entered when creating the move order through the Move Orders form. (INVTOMAI) These are both project locators for same project / task.

WHAT IS WORKING
-----------------------
The problem does not occur when disabling the Allow Cross Project Issues option.

ERROR #1
-----------------------
[
Error: The requested quantity could not be fulfilled by the location detailing process.

Action: Make sure there is onhand quantity for item before attempting to detailed these items.
]

ERROR #2
-----------------------
[
Picking rule fails to find a source locator that meets the rules restrictions.
]

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create and approve a Requisition move order
2. Query the same in Transact Move Orders form
3. Click Transact

Changes

The problem may surface after patching or after upgrading. (typically after upgrading from R12.1 to R12.2)
 

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