Transaction OMCT (about batch level)

Question

Hello people,
I would like to know if anybody can help me with the transaction OMCT. We are trying to change the batch level (conversion). Right now we have the same batch number for one material in two different plants and we also have the same batch number for two different material. When I throw the program in that transaction (OMCT) many incidents come out so I would like to have same information about how this program works.
Thank you very much

Answer 1

Go thorugh the OSS note 41715 adn 533377
OSS note 41715
OMCT, OMCE
Reason and Prerequisites
This function is not implemented in the standard system.
Solution
On principle, SAP recommends to stay on material level.
Reason:
1. If the batch level is defined on plant level, batch properties of a material batch of the same name are not transferred in case of cross-plant processes (see also Note 156299). In addition, a material batch may have the same name but different properties (e.g. expiry date) in different plants, since two plant-dependant batch masters exist. This should be considered in particular regarding the increasing importance of batches and the obligation of keeping a cross-reference without any gaps. A synchronization of patch properties beyond plant boundaries can only be guaranteed using the material level or the client level.
2. If a material is to be handled differently in different plants regarding the requirement of managing batches, this can only be realized using the plant level. For this case, however, we recommend nevertheless to stay on material level and create a dummy batch in the plant where batch management is not desired. In this dummy batch, all stocks of the material are managed. This has the advantage that the batch management requirement can be later introduced without any problems.
3. WIth SAP products R/3 Enterprise 4.7, APO 4.0, and CRM 4.0, the batch is increasingly used in cross-system processes. For those cross-system processes, plant level is not supported.
If the plant level is to be recreated nevertheless, please consider the following:
Since this type of conversion is very complex, it should be executed in a test system first.
After the conversion, check all batch data randomly for consistency.
It is recommended to inform the SAP Development department (distribution list DESDFUNC) by means of REMOTE consulting or through your personal consultant about the following points prior to a conversion in the production system:
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 or individual batch valuation being used?
5. Number of records for class type 023 in table INOB
6. Number of records for class type 023 in table AUSP
7. Number of records for class type 023 in table KSSK
8. Number of records in table MCH1
9. Number of records in table MCHA ========================================================================
This type of conversion can only be made as of Release 3.1I. Proceed as follows:
1. For all releases earlier 4.5B, apply the correction as well as the modification in RM07CHDX as specified in the correction instructions.
2. Create report ZCHTCUCH which is specified in the attachment.
3. Execute this report in the client in which you want to reset the batch level to plant level.
4. Call Transaction OMCT.
5. Check whether the batch level is set to "Batch unique at plant level".
6. Perform function "Batch level -> Convert".
7. Determine a plant for a possibly missing plant view.
8. Always execute the report in the test mode first. Analyze the error log.
9. If no errors occurred, you can execute the report in the production mode.
10. In case you are using long texts for batches, you should run report ZM07CHDX_TEXT afterwards (in the test mode first).
OSS note  533377
You want to convert the batch level from plant to material. The standard report (transaction OMCT) provided by Customizing of the batch management cannot execute the conversion, because
the plant definition cannot be explicitly defined for individual batches, or
the batch management requirement is not cross-plant unique for individual materials - in this case you must take Note 533276 into account.
Other terms
OMCT, RM07CHDX
Solution
You can solve the problem that repeatedly occurring batch numbers are flagged for deletion and then reorganized or archived with standard means. Batch stocks, which may exist, have to be cleared in advance.
In the case of a larger number of affected batches you can alternatively use a special conversion-report of the batch development, which executes the conversion without further manual interventions. However, the prerequisite here is that you can determine a 'leading plant' which then defines the plant batches whose data is retained during the conversion.
We have developed the main features of this report, but it must be adjusted to individual business processes in a customer project that is subject to charges.