Last updated on MARCH 08, 2017
Applies to:Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Maintain Lot Numbers flexfield issue
The Maintain Lot Numbers flexfield is not editable for lots created on the Lot Entry form. For lots created on the main Misc Receipt form, or on the OPM Batch Material Transactions form, the DFFs are editable at a later time when drilling to Lot Entry on a Misc Issue or an OPM batch ingredient. If the user drilled down to the Lot Entry (Lot/Serial) form when creating the lot, however, whether from Misc Receipts or PO Receipts (and in PO Receipts this is the only way you can create a lot), the flexfields are later editable only on the Item Lots (lot master) form; they cannot be edited at a later time when drilling to Lot Entry on a Misc Issue or an OPM batch ingredient.
Customer has set up context-specific flexfields on the Maintain Lot Numbers flexfield, based on the value of $profiles$.org_id. This works fine when creating new lots, such as when accessing Lot Entry from Receipts, entering new lots for Products on OPM Batches, and Misc. Receipts. Based on internal testing, it also works fine in Batches, Misc Issue, etc., when using existing lots that were not created from the Lot Entry form, such as the main Misc Receipts form or the batch Material Transactions form. However, if you create the lot by drilling down to Lot Entry (Lot/Serial button) as you have to do on PO Receipts, or if you do this on Misc Receipts, the flexfields are grayed out and not editable on Misc Issues or Receipts and Batch ingredients. They are only editable on the Item Lots (lot master) form.
It seems that when the lot is created from Lot Entry, the context value gets saved in mtl_lot_numbers.attribute_category, and this prevents further editing. This has been confirmed by nulling out the value in mtl_lot_numbers.attribute_category and then the DFFs become editable again.
Note that the value of $profiles$.org_id is different from the value of organization_id based on the org in which one is working. Also, this issue is reported for Maintain Lot Numbers flexfield, not lot attributes flexfield.
Expect that the flexfields should be editable on Lot Entry when accessed from any form and regardless of where the lot was created, as long as the customer is in one of the orgs for which the flexfields are enabled based on context. Why does this not work?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms