Transcript
02.11.2011Page 1 of 3 SAP Note 41715 -Resetting batch level from material to plant level Note Language: EnglishVersion: 22 Validity: Valid Since 10.11.2009 The displayed SAP Note is not up to date in the selected language / Summary Symptom Error message CZ308 This type of conversion is not yet implemented isissued when you try to reset the batch level from material level or clientlevel 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 amaterial batch of the same name are not transferred in case ofcross-plant processes (see also Note 156299). In addition, it ispossible for a batch of a material with the same name to havedifferent characteristics (for example, shelf life expiration date) indifferent plants because there are two plant-specific batch masterrecords. Take this into account in particular if batches areincreasingly important and a continuous where-used list is required.Batch properties can only be synchronized using plant boarders atmaterial level or client level.2.If you want a material to be treated differently regarding batchmanagement requirement in different plants, you can only do this atplant level. However, in this case, we recommend that you stay atmaterial level and create a dummy batch in the plant in which you donot want batch management. All stock of the material is managed inthis dummy batch. This has the advantage that the batch managementrequirement can be later introduced without any problems.3.With the SAP products R/3 Enterprise 4.7, APO 4.0 and CRM 4.0, thebatch is increasingly used in cross-system processes. Plant level isnot supported in these cross-system processes.However, if you want to restore plant level, take the following intoaccount:Since this type of conversion is very complex, first carry it out in a testsystem.After the conversion, check all batch data randomly for consistency.Prior to a conversion in a productive system, we recommend that you informSAP development (distribution list DESDFUNC) using REMOTE consulting orthrough your consultant of the following points:1.Is classification for batches being used? 02.11.2011Page 2 of 3 SAP Note 41715 -Resetting batch level from material to plant level 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 INOB6.Number of records for class type 023 in the table AUSP7.Number of records for class type 023 in the table KSSK8.Number of records in the table MCH19.Number of records in the table MCHA========================================================================This type of conversion can only be made as of Release 3.1I. Proceed asfollows:1.For all releases lower than Release 4.5B, implement the correctionsand the modification in the report RM07CHDX as described in thecorrection instructions.2.Create the report ZCHTCUCH, which is specified in the attachment.3.Run this report in the clients for which you want to reset batch levelto plant level.4.Call transaction OMCT.5.Check whether the batch level for Batch unique at plant level isset.6.Implement Notes 821891, 944278, 950540 and 1091613 if you have notalready done so (or you have not imported the corresponding SupportPackage).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 errorlog.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 reportZM07CHDX_TEXT in test mode. Header Data Release Status:Released for CustomerReleased on:26.10.2011 07:25:33Master Language:GermanPriority:Recommendations/additional info 02.11.2011Page 3 of 3 SAP Note 41715 -Resetting batch level from material to plant level Category:ConsultingPrimary Component:LO-BM Batch Management Valid Releases Software ComponentReleaseFrom ReleaseToReleaseandSubsequent SAP_APPLMERCURYMERCURYMERCURYSAP_APPL3030031ISAP_APPL4040A40BSAP_APPL4545A45BSAP_APPL4646A46BSAP_APPL46C46C46CSAP_APPL470470470SAP_APPL500500500SAP_APPL600600600SAP_APPL602602602SAP_APPL603603603SAP_APPL604604604SAP_APPL605605605 Related Notes NumberShort Text 1474776Data is not converted during conversion to plant level950540Batch level conversion: Message CZ 304891902FAQ: Batch level821891Short dump ABAPTSV_TNEW_PAGE_ALLOC_FAILED in prog RM07CHDX Attributes AttributeValue Transaction codesMCH1Transaction codesOMCETransaction codesOMCT Correction Instructions CorrectionInstructions Validfrom ValidtoSoftwareComponentType*)ReferenceCorrectionLastChanged 8067130D40BSAP_APPLCP30K051489 20.03.199918:21:4680672300605SAP_APPLC 02.11.201012:23:14*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work
