How to remove Batch Management Check in the Material

[Former Member]

I have one requirement to remove batch management check in the materials which should not be deleted.

I created a testing material with batch management check on and put in material through 561, then did good issue for

scrapping to remove the stock out. So existing stock is zero in Material Master.

Then deleted the batch in MSC2N by putting all the delete checks on. There was just one batch created for the material.

Then ran transaction MM74 to archive, the spool request is as below:

MCHB: 000000000010000498 2002 1002 D000000200 entry archived 1 000000000010000498

Archiving Session Number 000004

Number of Written Data Objects 1

Size of Archiving Session in MB 0,011

Proportion of Header Data in % 96,7

Then in MMPV changed the closing period to may as all the postings were performed in april.

Now still when I go and remove the batch management check in MM02 Purchasing view, still gives we DISPLAY ERROR message:

The batch management requirement cannot

be changed for the follow

Batches already exist.

ANY IDEAS why its not allowing me to remove the check as I guess I have performed all the steps required.

[JL23 · Accepted solution]

you archived just MCHB record, this is only the stock segment of the batch.

you have to archive as well MCHA and MCH1 record.

check the setting you made for archiving

[JL23 · Accepted solution]

in variant of MM74

enter material number

set a checkmark in box in front of batches

set a checkmark in box in front of inlcude batch records without deletion indicator

set radio button to Production mode

all other fields and boxes shall be kept empty.

[Former Member · Accepted solution]

MCHB: 000000000010000500 2002 1002 D000000101 entry archived 3 000000000010000500

MCHA: 000000000010000500 2002 D000000101 change documents will be archived 2 000000000010000500

MCH1: 000000000010000500 D000000101 class assignments will be archived 1 000000000010000500

MCHA: 000000000010000500 2002 D000000101 further dependent data archived 2 000000000010000500

This is the record I am getting now, but still in MM02, I cant remove the check, still batch exists error.

[Former Member · Accepted solution]

Dear Afshad,

Once material is activated as Batch Managed then it is Almost highly impossible to De-activate .

For this you need to directly contact SAP

More over they charge for the solution also.

so best way is to go with delete the existing material & Creating new one

Good Luck !!!

Regards

Madhu

[Former Member · Accepted solution]

Check whether the batch master is still exists in MSC3N .if it ia archived it should not be avialble in MSC3N

Refer note:30656

Reason and Prerequisites
The message that stocks still exist refers not only to stocks in the current period, but also to stocks in the previous period.
The reason for checking previous period stocks is that postings can also be made to the previous period when entering goods movements. This would result in inconsistencies if the base unit of measure had meanwhile been changed.
Solution
Check whether stocks still exist for the previous period by displaying; for example, the plant stock view or storage location stock view of the material. You do this by selecting "Extras -> Previous period -> Prev. pd SLoc. stock or Prev. pd plant stock".
If previous period stocks exist, you can make a withdrawal posting as follows:
1. Post the same amount to current period stock (for example, using movement type 561) so that previous period stock and current period stock are identical.
2. Make a withdrawal posting in the previous period for the stock together with posting date (for example, using movement type 562).
You can now try to change the base unit of measure or the batch management requirement indicator again.
Since the posting of the previous period values to zero is identical with posting to the stocks of the current period, you should reverse the above stock postings (that is, the stock from the previous period should be booked in again) to make sure that the stock values from the previous and the current periods correspond to the state before the change. However, note that the postings are then carried out using the changed master data from the current period (for example, account determination and so on)

[Former Member · Accepted solution]

Hello Raja,

I checked in MSC3N and the batch still exists. Seems like it is not archived. Any idea on what went wrong and I know its tough to get the batch management check removed and SAP gives paid solution for removing this check without going through all the hassle, but this is a good learning experience. Hopefully we will solve it and then we can give client both options either go with paid service of SAP or either go through this tough experience as currently I am just clearing one 561 and 562 posting and having so much problem, what will happen while searching all the other documents e.g. Pos, Grs, etc, need to clean them all in working material.

[JL23 · Accepted solution]

if the batches still in those tables despite of successful archiving, then you just did not run the deletion step of the archiving object.

if you did that, then you have to check whether your variant was wrongly setup and you deleted in test mode instead of production mode.

[Former Member · Accepted solution]

Jurgen,

Do you see anything wrong in this log:

MCHB: 000000000010000502 2002 1002 D000000102 entry archived 3 000000000010000502

MCHA: 000000000010000502 2002 D000000102 change documents will be archived 2 000000000010000502

MCH1: 000000000010000502 D000000102 class assignments will be archived 1 000000000010000502

MCHA: 000000000010000502 2002 D000000102 further dependent data archived 2 000000000010000502

Again, I created a new material with 561 and 562 movements, then put delete check in msc2n, all 3 checks activated, then running mm74 file with above variants of yours and getting with this result, still I can view the batch in msc3n and cant delete the check in mm02. Any ideas?

[Former Member · Accepted solution]

you have to give start date as immediately and spool parameter as local printer . In the variant you have to select processing option as Production mode .Now run and check the job overview . if you are try with MM70 and object MM_SPSTOCK ,you have to do 2 things first write and then delete.

[Former Member · Accepted solution]

>

> you have to give start date as immediately and spool parameter as local printer . In the variant you have to select processing option as Production mode .Now run and check the job overview . if you are try with MM70 and object MM_SPSTOCK ,you have to do 2 things first write and then delete.

I am running it through MM74 and yes I am following above settings.

[JL23 · Accepted solution]

the log is okay, but it is just the log for the write task of archiving.

MM74 is a stone age transaction, you should not use these old archiving transactions. Always use SARA transaction for archiving.

In SARA enter MM_SPSTOCK as object and hit enter.

Now you will get some buttons. they represent the usual steps for archiving.

Based on your customizing, you either have to process the deletion step seperatly or it is done in one call (but still 2 individual jobs) with the write step.

I am pretty certain that your customizing - which can be accessed directly from SARA - does not automatically start the deletion job.

Because of this you have to start it manually.

Click deletion button, then button for archive selection.

select the archive you just created with your write job and continue to schedule the deletion job.

The deletion job reads the archive and checks whether the archive can be accessed and read succesfully. And if this is okay then it reads the archive sequentially and deletes the corresponding entry from the MCHA, MCH1 and MCHB tables.

[Former Member · Accepted solution]

Thank you SIR Jurgen, you resolved the issue. I will never think of competing with you again for No.1.

Thanks again for everyones help. It was a great learning experience and hope lots will learn from this issue as well.

CHEERS

[Former Member]

Hi,

Check OSS Note 533383

[former_member187989]

If there is any batch stocks(valuated) exists in previous period/periods,It won't allow to detick batch management.

[Former Member]

Dear,

It may be possible because stock still available in previous month history. hence if you try in next month then i think it should work.

Regards,

Rajesh

Edited by: Rajesh Koladiya on May 3, 2010 4:48 AM

[Former Member]

I anticipated this problem as well, by reversing the said document in previous month, still cant remove the batch tick.

I went through SAP notes as well. Even created a new material, and just did 561 in current period and then 562 against it, and then went on deleting the batch through MSC2N and MM74, still I cant remove the batch management tick, someone has better ideas for me?.