GLEI Issue in MD04

[former_member224727]

Hi,

As per our business design we are running single process order for multiple days. To distribute order qty between diff days we use GLEI key, which equally distribute qty between days.

Example: I'm starting my order at 1st Aug - 12pm running for 12 hr, next on 2nd Aug - running for 24 hrs, Next on 3rd Aug closing at 12pm - 12 hr.

My total order qty is 100 KG. Resource is running 24 * 7.

So in above example actually business is producing material on 1st Aug - 25 KG, 2nd Aug - 50 KG, 3rd Aug - 25 KG, but because we are using GLEI key it is equally distributing qty between days - 100 KG/ 3 days = 33.33 KG per day.

And sawing 33.33 KG qty against 1st, 2nd, 3rd Aug in MD04 transaction. I understood this GLEI standard functionality to equally distribute qty bet'n days, but our business wants to see actual qty in MD04.

Is there any possibility to do so? What about user exit/ BADI/ Enhancement to write some logic to pull correct qty in MD04 screen?

[Caetano · Accepted solution]

Hello

The distribution on MD04 can only consider dates, not times. Also, there is no BAdI that allows you to make the distribution to consider the times.

You can try to develop something using BAdI MD_CHANGE_MRP_DATA, but I'm affraid that it is a very complex development.

BR

Caetano

[former_member224727 · Accepted solution]

Thanks Almeida for reply. Here my resource is running for 24 x 7 hrs and it's capacity is 50 KG per 24 hr but because of GLEI MD04 does not consider resorce capacity & saw 40 KG per day. Do you know some place where we make change which saws correct qty in MD04?

I want when MD04 distributing amount between days it should come & see mt resource capacity first. If it does that way MD04 will saw correct qty & ATP works perfectly.

[Caetano · Accepted solution]

Hello

The distribution on MD04 does not consider capactiy restrictions. The quantity will be distributed between the basic dates, according to the factory calendar working days.

BR

Caetano

[former_member224727 · Accepted solution]

We resolved this using custom development at MD04.