41715 - resetting batch level

3

Click here to load reader

Upload: ranaahead

Post on 02-Jun-2018

219 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 41715 - Resetting Batch level

8/11/2019 41715 - Resetting Batch level

http://slidepdf.com/reader/full/41715-resetting-batch-level 1/3

SAP Note 

Header Data

Symptom 

Error message CZ308 "This type of conversion is not yet implemented" is issued when you try to resetthe batch level from material level or client level to plant level.

Other Terms 

OMCT, OMCE

Reason and Prerequisites 

This function is not implemented in the standard system.

Solution 

We recommend that you remain at material level.Reason:

1. If the batch level is defined at plant level, batch properties of a material batch of thesame name are not transferred in case of cross-plant processes (see also Note 156299). Inaddition, it is possible for a batch of a material with the same name to have differentcharacteristics (for example, shelf life expiration date) in different plants because there aretwo plant-specific batch master records. Take this into account in particular if batches areincreasingly important and a continuous where-used list is required. Batch properties can onlybe synchronized using plant boarders at material level or client level.

2. If you want a material to be treated differently regarding batch management requirement indifferent plants, you can only do this at plant level. However, in this case, we recommend thatyou stay at material level and create a dummy batch in the plant in which you do not want batchmanagement. In this dummy batch you then manage all stocks of the material. The advantage ofthis is that the introduction of a batch requirement at a later time can be done withoutproblems.

3. With the SAP products R/3 Enterprise 4.7, APO 4.0 and CRM 4.0, the batch is increasingly usedin cross-system processes. Plant level is not supported in these cross-system processes.

However, if you want to restore plant level, take the following into account:

Since this type of conversion is very complex, first carry it out in a test system.After the conversion, check all batch data randomly for consistency.Prior to a conversion in a productive system, we recommend that you inform SAP development(distribution list DESDFUNC) using REMOTE consulting or through your consultant of the followingpoints:

1. Is classification for batches being used?

2. Is batch status management being used?

3. Are long texts for batches being used?

4. Is split valuation or individual batch valuation being used?

5. Number of records for class type 023 in the table INOB

6. Number of records for class type 023 in the table AUSP7. Number of records for class type 023 in the table KSSK

8. Number of records in the table MCH1

9. Number of records in the table MCHA

========================================================================This type of conversion can only be made as of Release 3.1I. Proceed as follows:

41715 - Resetting batch level from material to plant level  

Version  24 Validity: 23.08.2013 - active Language  English

Released On  26.08.2013 08:32:23

Release Status Released for Customer

Component  LO-BM Batch Management

Priority  Recommendations / Additional InfoCategory  Consulting

Page 2: 41715 - Resetting Batch level

8/11/2019 41715 - Resetting Batch level

http://slidepdf.com/reader/full/41715-resetting-batch-level 2/3

1. For all releases lower than Release 4.5B, implement the corrections and the modification inthe report RM07CHDX as described in the correction instructions.

2. Implement the report ZCHTCUCH from the correction instructions.

3. Run this report in the clients for which you want to reset batch level to plant level.

4. Call transaction OMCT.

5. Check whether the batch level for "Batch unique at plant level" is set.

6. Implement Notes 821891, 944278, 950540 and 1091613 if you have not already done so (or youhave not imported the corresponding Support Package).

7. Execute the function "Batch Level -> Conversion".

8. Define a plant for a plant view that may be missing.

9. Always execute the report in the test mode first. Analyze the error log.

10. If no errors occur, you can execute the report in production mode. 

11. If you are working with batch long texts, first execute the report ZM07CHDX_TEXT in testmode.

Other Attributes

Validity

Correction Instructions

References

This document refers to:

SAP Notes 

MCH1

 OMCE

 OMCT

Software Component From Rel. To Rel. And Subsequent

SAP_APPL  30C  31I  

40A  40B  

45A  45B  

46A  46B  

46C  46C  

470  470  

500  500  

600  600  

602  602  

603  603  

604  604  

605  605  

606  606  

616  616  

617  617  

Correction Instructions

Software Component Valid from Valid to Number

SAP_APPL  30C  617  80672

 SAP_APPL  30D  40B  80671

1474776 Data is not converted during conversion to plant level 

1387713 OMCT: CZ314 or batch status management cannot be activated 

950540 Batch level conversion: Message CZ 304 

891902 FAQ: Batch level 

Transaction codes

Page 3: 41715 - Resetting Batch level

8/11/2019 41715 - Resetting Batch level

http://slidepdf.com/reader/full/41715-resetting-batch-level 3/3

 

This document is referenced by:

SAP Notes (5) 

821891 Short dump ABAPTSV_TNEW_PAGE_ALLOC_FAILED in prog RM07CHDX 

821891 Short dump ABAPTSV_TNEW_PAGE_ALLOC_FAILED in prog RM07CHDX 

950540 Batch level conversion: Message CZ 304 

1474776 Data is not converted during conversion to plant level 

1387713 OMCT: CZ314 or batch status management cannot be activated 

891902 FAQ: Batch level