OSP Job For Assembly With Lot Control And User-defined Expiration, Not Auto-completing
Last updated on MARCH 08, 2017
Applies to:Oracle Work in Process - Version 12.1.3 and later
Information in this document applies to any platform.
Our OSP assembly items are lot controlled, with lot-expiration as User-defined. The lots #s (for the item) with the expiration date are pre-created in the standard inventory lots table.
When we receive the labor, we input the supplier lot # and via a form personalization, copy this lot # into the OSP job lot #.
Even though the OSP job has a completion subinventory and locator, and has the pre-created lot # value, the job fails to complete automatically when we perform a receipt.
If the lot # expiration is not controlled, then the job does complete into the existing lot #. Is this Standard Functionality.
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