E1: 42W: Auto Fulfillment (R4277701) Not Allocating Inventory Due to Record Reservations
(Doc ID 2908677.1)
Last updated on NOVEMBER 10, 2022
Applies to:
JD Edwards EnterpriseOne Fulfillment Management - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
After introducing Fulfillment Load Balance (R4277711) program into production there were many record reservations created. This prevented many orders from being shipped the next day because inventory was not allocated and orders were not released.
Steps to Reproduce
- Setup a version of Fulfillment Load Balance (R4277711) program
- Set Process Tab Option #1 (Number of Concurrent Jobs) to 8
- Add the Fulfillment Load Balance (R4277711) program to the JDE Scheduler in the production (live) environment
- Data selection was over three branch plants
- Fulfillment Load Balance (R4277711) program ran overnight
- Execution detail shows over 80,000 order lines were in the data selection
- There were 8 Auto Fulfillment (R4277701) jobs launched.
- PDF report showed the first job processed 32,000 lines the other 48,000 lines were apportioned over 7 other jobs.
- Many messages were sent to the Work Center messages indicating inventory could not be allocated because of record reservations
- Three Fulfillment Release jobs (R4277703) were launched (one for each branch)
- Most lines in the report showed quantity released of Zero
- Many messages were sent to the Work Center because of record reservations
- The next morning users complained there were no orders ready for shipment when they knew there was inventory available in the warehouse.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |