Inventory Commitment Method

marcoh

Member
Hi

We have an increasing problem within our warehouse which is caused by what i believe is a fundamental flaw in Commitment logic provided by E1 (at least i cannot explain the logic used by E1 in relation to our business process). We are using E1 8.12 using standard inventory/sales module i.e. we do not have advanced warehousing installed. On our branch plant constants we are given 3 options when it comes to Inventory commitment (1/ Location with most qty - 2/ Lowest lot number - 3/ using lot date)
We dont use lots within our business so we only had the option of using 'Location with most Qty' this is casuing us problems in our BP by the fact that we are left with multiple locations with part pallets all over the BP.
In our system we can have up to 50 valid locations for a part number, say we started today with the maximum 216 of these parts to each pallet.
We get an order in the system for a qty of 300.
216 of these get commited to the primary location
The other 84 will get committed to a secondary location
this leaves a qty on hand of 132 in the secondary location
that night we replenish primary back to qty 216
next day another orer comes in for 300
again 216 get commited to primary
however this tiem the 84 gets committed to a different secondary, we end up with 123 at this location as well.

This goes on and on and we end up with part pallets in our warehouse.

To me it would make more sense for JDE to commit inventory form the location with the lowest qty on hand this way all the part pallets would be consumed until they are at zero and then move on to next secondary.

Does anybody else have this situation and how are you overcoming this problem?

thanks in advance for any help on this matter.
 

Guy Robert

Well Known Member
The situation you are discribing in your warehouse can be solved by the
warehouse management module. The basic inventory system does not do what
you are asking for because the solution resides in an other module. Get
the proper solution before attempting to re-invent the inventory system.

Guy Robert
Syntax.Net
 

jfevans

Member
Your requirement is the same as most, or at least many JDE clients. No com pany wants an item's inventory scattered around multiple locations. Unfort uately after several requests for a modification to JDE (returned reconside r for the future), we had to change the logic and add another B/P constants option. Of course this is a lot of overhead when it comes to an upgrade, but it was determined to be easier than buying, implementing, and maintaini ng Warehouse Management. Other more sophisticated functionality of WMS was not required in our situation.
 

marcoh

Member
Thank you



It is a small comfort to know that we are not alone with this problem,
(From talking to Oracle they cannot see that this is an issue at
all!!!!). We also want to avoid implementing warehouse management as we
do not require 99% of the functionality it provides. Looks like we will
have to go down the road of modifying our system to cope with this
process issue.



Regards



Mark Hayes

Business Applications Co-ordinator

Donaldson Australasia Pty Ltd

Direct Tel (02) 43502049

Main Switch (02) 43502000

[email protected] <mailto:[email protected]>

Please note the new Donaldson email address



From: [email protected] [mailto:[email protected]]
On Behalf Of jfevans
Sent: Tuesday, 27 January 2009 11:57 AM
To: [email protected]
Subject: Re: Inventory Commitment Method



Your requirement is the same as most, or at least many JDE clients. No
com pany wants an item's inventory scattered around multiple locations.
Unfort uately after several requests for a modification to JDE (returned
reconside r for the future), we had to change the logic and add another
B/P constants option. Of course this is a lot of overhead when it comes
to an upgrade, but it was determined to be easier than buying,
implementing, and maintaini ng Warehouse Management. Other more
sophisticated functionality of WMS was not required in our situation.
 
I have a similar problem, in my case, I have a BP several lots, these are as high locacion, as part have a main location, is that when I make a sales order, should only engage in soft commit the main location and then on the confirmation to confirm existence of a lot with, but it turns out compromises on sale across locations-lots
 

mouly

Member
We had the similar situation and we managed to customize the ‘pick slip report – R42520’ where we hard commit the inventory. We did specifically because client doesn’t want to use ‘Advanced Warehouse Management’. If you want to customize R42520 you have to customize at least four business functions responsible for inventory commitment.

PickSlipInventoryCommitment – N4201360
F42UI130F4211SODetailLineSplit – B4201300
InventoryAvailAndCommitment – B4200380
GetItmLocByCommitment - B4000780

B4000780 is the crucial BSFN which determines the order in which the location quantities are hard committed. We managed to build a query in B4000780 like below where PQOH is in Ascending Order which will cover the process. We done this in 8.12 version & 8.98.4 tools release

[SELECT * FROM QADTA.F41021 WHERE ( LIITM = 1234 AND LIMCU = ' 30' )
ORDER BY LIITM ASC,LIMCU ASC,LIPBIN ASC, LIPQOH ASC;]
 
Top