E1: 31: 32: 34: 40: 41: 42: 43: 46: 47: 49: Location on Hold Enhancement in JD Edwards EnterpriseOne 9.2 (Doc ID 2992554.1)

Last updated on MARCH 15, 2024

Applies to:

Goal

Inventory management and control is made much more efficient and flexible by enabling availability and movement to be determined by a Location Hold field in the Location Master that defines what kind of transactions are allowed and takes precedence over the Lot Status in the Item Location table. This eliminates the need to update individual item/lot/location record.

The location hold is supported for different processes and transactions in JD Edwards EnterpriseOne Inventory, Sales, Procurement, Warehouse, Transportation, MRP, and Work Orders modules.

The enhancement for Location Hold Status provides the ability to put a location on hold independent of items and disallow movement of inventory to/from the held location. 

What is being announced?

Oracle JD Edwards has announced an enhancement to Location on Hold in JDE Edwards EnterpriseOne Release 9.2: 

• Functionality added to the Location Master (P4100/F4100) for field Location Hold (LHLD) to add a specific location on hold independent of item functionality. 
• New UDC Code table 41/LS, processing options, and errors have been added to support the functionality to Manufacturing & Distribution (M&D) programs.
• Numerous programs in Inventory, Sales, Procurement, Warehouse, Transportation, MRP, and Work Orders modules support the Location on Hold functionality.

Important
Now inventory movement and availability can be controlled at the location level and not the item level via Lot Status codes. 

Considerations

• Location on Hold functionality takes precedence over Lot Status Codes but Lot Status remains unaffected.
• Locations may be completely disabled from being used in inventory commitments. 
• Added UDC 41/LS values = blank, 1, 2, 3, 4 which indicate if a location is unrestricted (=blank), restricted = 1, 2, 3, 4 for to/from movement for a location.  
• Processing options for Location on Hold added to programs.
• New Errors LH22, LHCD22, and 3456 (Location on Hold and Location on Hold for Cross-Docking) were added noting a Location is on Hold and it either needs to be released or another location used.
• Availability Checking will consider the Location on Hold based on the Location Hold (LHLD) field value and will be grayed out if on hold.
• Commitment program will omit the locations with special values in the LHLD field.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.