System Profile Option INV: Restrict Receipt Of Serials Is Not Working As Intended (Doc ID 746029.1)

Last updated on AUGUST 21, 2016

Applies to:

Oracle Inventory Management - Version 11.5.10.2 and later
Information in this document applies to any platform.

Symptoms

The Profile INV:Restrict Receipt of serials is not working as intended

INV: Restrict Receipt of serials is set to Yes
If one serial is issued to one job, the same serial could not be completed for a different job. Error is found. 'Invalid value for field FM_SERIAL_NUMBER' at WIP ASSY COMPLETION Transaction.

INV: Restrict Receipt of serials is set to No
If the serial is issued to one job,the same serial can be accepted and completed in the range of serials for a different job.

Steps to Reproduce:
a) Create serial controlled finished good and sub-assembly item. (Predefined Serial control)
b) Create component Item.
c) Create BOM for finished Good with Child item as sub-assembly.
d) Create BOM for Sub-assembly with Child item as component item
e) Create Routing for finished Good and Sub-assembly item.
f) Perform Miscellaneous receipt for sub-assembly item.
g) Create Discrete job for finished good and Perform the WIP component issue transaction which would issue sub-assembly serial to the finished good job.
h) Perform Miscellaneous receipt for component item and create Discrete job for Sub-assembly.
i) Perform WIP component issue,Move transactions for Sub-assembly Job.

d) If INV: Restrict Receipt of serials is set to NO,the same serial cannot be completed for the sub-assembly job and the error is found as

'Invalid value for field FM_SERIAL_NUMBER'.

(Note:In this Step, enter the same serial that is issued out to a finished good job already in the step g )

e) If INV: Restrict Receipt of serials is set to YES,the same serial can be accepted and completed
in the range of serials for the sub-assembly job.

(Note:In this Step, enter the same serial that is issued out to a finished good job already in the step g )

Changes

For 11.5.10, the issue began after INV RUP4 <Patch 5739724>.

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