Problem in LIFO and FIFO during Batch Management

[Former Member]

Hello guys,

I am trying to do automatic batch determination by LIFO and FIFO logic,but somehow i am not able to do that.

For this i am using the std characteristics LOBM_VFDAT(Last goods receipt by delivery date).While creating the class i have assigned this characteristic inside it.

Inside the sort rule i have selected the ascending and descending respectively and have given no. of splits equal to 99 and have done all the remaining settings like to assign selection procedure to order type, create strategy type for the plant,material,and ordertype combination.

Now in production order when i select the component in component overview and do the batch determination, its not showing any batch for it, but when we check in mmbe its showing couple of batch is already there.

While doing this i have noticed one thing that its not giving any error regarding batch determination.So enable to understand what configuration i have missed out.

Its urgent guys.

[Former Member]

i am closing this thread.

[Former Member]

Hello guys,

I tried by the procedure you explained than also couldn't determine the batch automatically by LIFO and FIFO logic.

Actually i want to ask that for LIFO and FIFO as we have to use the standard characteristic LOBM_LFDAT.and as it is the standard characteristics, so system doesn't allow you to do changes to it,in ct04 (edit mode)so its not possible to maintain the values inside it.

So, you guys want to say that first create the batch automatically in production order if i have maintained such settings, and than do the confirmation and goods receipt for it. Now select that batch again and go to edit mode(MSC2N) and in classification tab page maintain the goods receipt date as value of the characteristics LOBM_LFDAT.Am i right?Plz guide.

If yes than do i have to do this for all batches i created and did the goods receipt for it,than only system will do the batch determination by LIFO and FIFO logic.

[former_member42744]

You do not need to maintain any LOBM characteristics manually. The values should automatically be there if the related value has been calculated/populated by the system.

LOBM_LFDAT is a linked to the delivery date and should only be used in the selection class when your selecting for deliveries to customers. It is not the last goods receipt date.

I'm not sure why you want to use last receipt date anyway. I suggest using batch expiration date (LOBM_VFDAT) as your selection critieria. Typcially the batch expiraton date will be sequential anyway with regard to receipt. The goal is to use the oldest material first so it does not expire or need to be retested. (Some places use next inspection date (LOBM_QNDAT, if the goal is to minimize lab tests.)

If you use last GR date, you have no guarantee your using the oldest material first. You could receive two shipments from the same raw material supplier a few months apart and find that the most recent shipment sent, actually has a batch that expire before the one received earlier.

You should look at SAP note 48765. It explains the use of SAP standard characteristics and how to use them with regard to batch search strategies. Some standard characteristitcs should only by in selection classes and others only in batch classes. Notes 33396 and 65816 may also be of value to you.

Craig

[Former Member]

LOBM_VFDAT is for shelf life expiration date . I hope you are maintaining this in the batch. Anyways for LIFO or FIFO why do you want shelf life expiration days anyway .

I have done batch determination successfully in LIFO & FIFO criteria in the following way . It worked . Try it if you like.

If you want to select the batch in FIFO criteria that is first in first out i.e. the batches that are received first will be selected, then

You have to create a characteristic for last Goods receipt date with table name MCH1 & field LWEDT

Assign this to class

Create sort sequence with ascending order CU70

Then create batch search strategy in MBC1 transaction if you want batch determination in production order

Give the sort rule there

Give the no. of batch splits as much as you want or just keep 999 , give the batch selection criteria if u want or just give the indicator for no selection criteria

Then try doing the batch determination & check if you are getting what you want

Similarly If you want to select the batch in LIFO criteria that is last in first out i.e. the batches that are received last will be selected, then

You have to again create a characteristic for last Goods receipt date with table name MCH1 & field LWEDT

Assign this to class

Create sort sequence with descending order CU70

Then create batch search strategy in MBC1 transaction if you want batch determination in production order

Give the sort rule there

Give the no. of batch splits as much as you want or just keep 999 , give the batch selection criteria if u want or just give the indicator for no selection criteria

Then try doing the batch determination & check if you are getting what you want

revert if any clarification required

[dhaval_choksi3]

Hy Jitendra,

I think no value of LOBM_VFDAT is missing in Both batches.

So check in MSC3N for both batches in Classification screen whether value of this characterstic is maintain or not.

Regards,

Dhaval

[Former Member]

Check the following

In the batch concerned is the cherectristics value i.e.date field is filled or not?

In the batch I hope you have assigned goods recipt date as a charecter?