cancel
Showing results for 
Search instead for 
Did you mean: 

Batch Date in APO = 01.01.1970

liam_ryan2
Explorer
0 Kudos

Hi All,

I have a problem with the batch date in APO.

It shows as 01.01.1970.

This effects dynamic pegging as nothing gets pegged to it as it is

too far in the past.

There is a date of manufacture etc in R3 on the batch.

The Delta report shows no inconsistencies.

How can I correct this ?

Thanks,

Tony

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Tony,

Please confirm whether shelf life is defined for these products. In case, if shelf life is expired, then APO will not recognise those stocks. Meanwhile, let me find any report/note to fix this issue.

Regards

R. Senthil Mareeswaran.

liam_ryan2
Explorer
0 Kudos

Hi,

Shelf life is in use and in date.

Thanks,

Liam

Answers (4)

Answers (4)

Former Member
0 Kudos

YES; without using shelf life charactheristics; all stock in SAP APO will have an availability date of 1/1/1970 as APO wouldn't know when it is really available.

Ken Snyder

Former Member
0 Kudos

Hi Tony,

You need to make sure all the characteristics values like (availability date, production date and expiry date) for batches are transfered to APO. For any batch you can check the same in versions tab of transaction /n/SAPAPO/RRP3.

For old batches if the characteristic is added later on then it will not pick the new characteristic value. For such batch goto MSC2N in R3 and in classification tab peform consistency check. Here it will acquire values of new charactristics. (For mass updation you might need to right BDC)

Then re-CIF batches again by again generating and activating IM.

Now the date 01.01.1970 should not appear.

Best regards,

Vaibhav

Former Member
0 Kudos

Hi Tony,

Please check sap note 546957 whether applicable to you.

liam_ryan2
Explorer
0 Kudos

Hi R. Senthil Mareeswaran,

Thanks for your response although I am sure

that I could get the dates correct if creating a new batch etc.

The problem is now that there are many batches in a production system

with this issue.

Do you know a report / job etc that could fix this ?

Can you suggest any root cause ?

Thanks,

Tony

Former Member
0 Kudos

Hi tony,

Please try whether this works.

1) Create a production/process order for that material and inside the components,

2) Enter the same component again with the qty available and batch number.

3) Save and release the order

4) Carry out confirmation and post the same qty with new running current batch and qty

5) The new batch number and qty will get transferred to APO via CIF.

6) Then you can check the pegging whether happening or not like.

Kindly confirm

Regards

R. Senthil Mareeswaran.