Change batch level from plant to material
Hi,
is there any possibility to change the batch level from Plant to Material level. system has now changed the table in material master from MARA to MARC.
Regards,
Ali
Hi,
please check the below link.
http://help.sap.com/saphelp_45b/helpdata/en/25/2838714f7811d18a150000e816ae6e/content.htm
Similar Messages
-
Changing Batch Level from Material Level to Plant Level.
I want to create the batch class with the class code 22 instead of 23. As the batch class is maintained at the Material Level, not at the Plant Level. So is it possible to change the batch class from Material to Plant Level and create batch class with code 22.
Kindly suggest.Hi, Thanks for ur reply.
I have applied SAP notes and changed the batch status from material level to plant level...But still i am getting the class type as 23.
What are the next steps to be done. Currently in OMCT, Batch Level Conversion tab is active and rest all the tabs are in inactive state. so please guide. -
Process for batch level at plant level
Folks,
In case we have set batch level at plant level, how does the system reacts in case of an STO? I.e. I ship batch 1 for material 1 from plant A to plant B. In plant B, this batch might already exists as the level of batches is on plant level. HOw will the GR react? Will it create a new batch number in plant B?
Regards,
MdZHi,
Thanks for the reply. Just to be sure; in case of a scenarion in which we have an STO, an outbound delivery with message type SPED which creates the inbound delivery and copies over the batch numbers in the inbound delivery and we do a GR on the inbound delivery, the system will try to do GR for these specific batches. Will the system then also either receive the batches on the inbound delivery in case these do not exist and create new ones in case they do exist?
Regards,
MdZ -
D/ friends,
In OMCT, in Batch level option, Batch level is defined at material level by default. I want to change it to plant level. When Iu2019m selecting the option u201CBatch unique at plant levelu201D, sys is giving err: u201CThis typ of conversion is not yet implemented. Message no. CZ 308u201D. Pls help how to solve this err.
Iu2019ve searched the forum but to no avail.
Thanks.Check SAP note 911975 with your BASIS person.It maybe due to some program error.
Regards,
Indranil -
Change batch determination from TO level to Delivery level
Hi,
Need input on this.
We want to change the batch determination from TO level to delivery level. How do we do this? What are the implications of this change?
Regards
RJSHi,
1) You can switch of WM batch determination by deleting the WM batch search strategy in LS52
2) You have to maintain the necessary setting in customizing for batch determination in delivery
SPRO > Logistcs - General > Batch Management > Batch Determination and Batch Check...here you have to all the setings
3) You have to maintain suitable batch search strategy in VCH1/VCH2/VCH3
If batch is determined in the delivery it means that you cannot change it when creating the TO.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/25/283aac4f7811d18a150000e816ae6e/frameset.htm
http://www.sap-img.com/sap-sd/some-light-on-batch-determination.htm
http://www.renet-web.net/2008/09/05/sap-batch-determination-made-easy/
Regards,
Csaba -
I want to change my Batch level in my prototype company. However in transaction OMCT the option for "Batch Level" is greyed out. That makes me think I need to run the conversion for Batch Level. However, that option is greyed out as well.
Is there a pre-requisite step to running the conversion? The 3 boxes for Batch Status Management are all available.I figured it out. I had to run the conversion for Batch Status Management first. After that completed successfully the Batch Level option was no longer greyed out,
-
Change PP order from PLANT STOCK to PROJECT STOCK ?
We are creating a production order via BAPI_PRODORD_CREATE_FROM_REF. We are using an existing production order as our reference. The existing production order has account assignment to WBS, and the existing production order is listed under PROJECT STOCK in MD04. The newly created order does not have the assignment to WBS, and also is showing up as a fulfillment of PLANT STOCK in MD04.
We attempt to update (via CO02) the newly created order by populating the WBS and settlement rule, but it remains in PLANT STOCK. How can we get the production order removed from PLANT STOCK and show up in PROJECT STOCK for the correct WBS?Hi,
I doubt the BAPI - BAPI_PRODORD_CREATE_FROM_REF will help for your need, as WBS element is not one of the inputs for this BAPI.
A suggestion which might help:
- Create a planned order using BAPI - BAPI_PLANNEDORDER_CREATE by specifying the planned order type as PR. Here you can give the details of WBS & other things as needed.
- Next use BAPI - BAPI_PRODORD_CREATE_FROM_PLORD where-in you can convert the planned order create in the earlier step into a production order.
This will ensure that the order will be in project segment.
Regards,
Vivek
Added
Just to inform you, SAP confirms that the BAPI - BAPI_PRODORD_CREATE_FROM_REF simulates CO01 & not CO10. Hence you will be unable to use this BAPI to meet your need.
You can use the option suggested earlier or go for a BDC recording. -
Want to Change Passthrough level from 1 to 2 ......
[timesten@dellstudio bin]$ ttisql tt_passuser1
Copyright (c) 1996-2008, Oracle. All rights reserved.
Type ? or "help" for help, type "exit" to quit ttIsql.
All commands must end with a semicolon character.
connect "DSN=tt_passuser1";
Connection successful: DSN=TT_passuser1;UID=passuser1;DataStore=/d01/app/oracle/tt70/DataStore/TT_passuser1;DatabaseCharacterSet=WE8ISO8859P1;ConnectionCharacterSet=US7ASCII;DRIVER=/d01/app/oracle/tt70/TimesTen/tt70/lib/libtten.so;OracleId=db10g;Authenticate=0;PermSize=100;PassThrough=1;TypeMode=0;
(Default setting AutoCommit=1)
Command> show passthrough;
PassThrough = 1
Command> show autocommit;
autocommit = 1 (ON)
my current value for passthrough is 1 i want to chane it to 2;
when i change it it remain 1....do i have to edit manually in sys.odbc.ini file in my DSN.
Command> set passthrough 2;
Command> commit;
Command> show passthrough; "not changed"
PassThrough = 1
regards
Muh.UsmanWhen you set passthrough using the 'passthrough' command in ttisql the new value only remains in effect until you commit and then it gets reset back to the setting in the DSN. This is why you can only use the passthrough command when autocommit is disabled.
Note that the setting fof passthrough takes effect at command 'prepare' time not execute time annd is saved as part of the prepared command 9same is true when using it in applications). Consider the following sequence in ttIsql:
autocommit 0;
passthrough 3;
prepare 1 update sometabe set somecol = 4 where somepk = 100;
commit;
passthrough 1;
prepare 2 insert into anothertab values ('1', 'Some Row');
commit;
passthrough 2;
exec 1; -- the update still executes with passthrough 3
exec 2; -- the insert still executes with passthrough 1
commit;
Chris -
Transaction OMCT (about batch level)
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 muchGo 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. -
Batch level settings conversion from plant-to-plant to material-level
If someone has worked on conversion of Batch level settings within SAP from plant-to-plant to material-level batch management, please let me know what are the challenges involved in doing this. Thanks.
Check help !!!
To change the batch level, you have to start a conversion program. This program first checks whether conversion is possible and outputs an error log containing all batch numbers that occur more than once at the new level. Now you need to manually transfer these batch records to batch numbers within Inventory Management using a transfer posting 'material to material'.
If you change the level from plant level to a higher level, it is possible that batches with the same batch numbers in different plants are actually identical. In this case, all you have to do is remove stocks (including previous period stocks) so that all batches with the same batch numbers, except one, can be reorganized.
When you convert from plant level to material level, the material is then to be handled in batches in all plants in which it is defined.
Standard settings
In the standard delivery batches are uniquely defined at material level.
Activities
To change the batch level, proceed as follows:
1. Choose the level at which you want your batches to be unique.
2. Save the new settings and choose Back.
3. Choose Batch level -> Conversion.
4. If necessary, carry out the conversion in test mode first.
Further notes
Note that you cannot reset conversion from plant level to a higher level in the standard.
If you create a client by copying an existing client, initially, there are no settings in the target client at batch level. The system makes the settings in the target client only when you have carried out an activity (maintaining master data or posting a goods movement, for example). The client level is not transported. If you copy a client with client level, you have to manually set the client level in the target system. -
About the effect for batch level conversion from material to plant level
Dears,
Now we use batch management at material level in our system, now we want to change to batch level from material level to plant level, what effects or risks it will bring during the process of conversion?
Thanks a lot
ZhongkaiHi
check the following SAP help link it is very helpful:
http://help.sap.com/saphelp_40b/helpdata/es/d2/1d4b6e5733d1118b3f0060b03ca329/content.htm
at the link you can find the following
Specify batch level and activate status management
In this IMG activity, you specify the following:
the level at which batch numbers are unique
whether batch status management is active in the client
the plants in which batch status management is active
the initial status of new batches
Batch level
Batch numbers can be unique at the following levels:
at plant level
at material level
at client level for a material
If you choose plant level, the batch number is unique in conjunction with the respective material and the plant. If you choose material level, the batch number is unique together with the material. At client level, the batch number is unique in the whole client.
To change the batch level, you have to start a conversion program. This program first checks whether conversion is possible and outputs an error log containing all batch numbers that occur more than once at the new level. Now you need to manually transfer these batch records to numbers within Inventory Management using a transfer posting 'material to material'.
If you change the level from plant level to a higher level, it is possible that batches with the same batch numbers in different plants are actually identical. In this case, all you have to do is remove stocks (including previous period stocks) so that all batches with the same batch numbers, except one, can be reorganized.
When you convert from plant level to material level, the material is then to be handled in batches in all plants in which it is defined.
Standard settings
In the standard R/3 System, batches are unique at plant level.
Activities
To change the batch level, proceed as follows:
1. Choose the level at which you want your batches to be unique.
2. Save the new settings and choose Back.
3. Select function Batch level -> Conversion.
4. If necessary, carry out the conversion in test mode first.
Further notes
Note that you cannot reset conversion from plant level to a higher level in the standard.
If you create a client by copying an existing client, initially, there are no settings in the target client at batch level. The system makes the settings in the target client only when you have carried out an activity (maintaining master data or posting a goods movement, for example).
SETTINGS BEFORE/AFTER CLIENT COPY:
Source client Target client
Client level Material level
Material level Material level
Plant level Plant level
Batch status management
Batch status management is an additional function provided by the standard R/3 System.
Standard settings
Batch status management is not active in the standard R/3 system.
Activities
To activate batch status management, proceed as follows:
1. Choose Batch status management active.
2. Save the new setting and choose Back.
3. Choose Batch status management -> conversion.
4. If necessary, carry out the conversion in test mode first.
Further notes
Batch status management is linked to the batch level. At material and at plant level, the status management settings are valid within the client, that is for all plants. However, if you have defined batches to be unique at plant level, you have to select the plants in which status management is to be active using function Plants with status management.
If you activate status management, all existing batches are assigned status 'unrestricted'. If you deactivate status management, the systems transfers all restricted batches to unrestricted stock within conversion. Restricted stock only exists if status management is active.
If you create a client by copying an existing client, status management is automatically activated if batches exist in the target client, independent of the settings in the source client. If no batches exist in the target client, it is not activated. In this case, you have to activate or deactivate status management manually, if required.
Plants with batch status management
Activities
To select the plants in which status management is to be active, proceed as follows:
1. Set characteristic Batch status management for those plants in which batch status management is to be active.
2. Save your settings and choose function Back.
3. Choose function Batch status management -> conversion
4. If necessary, carry out the conversion in test mode first.
Initial status of a new batch
Using this function, you can specify for each material type which initial status new batches are to be assigned. However, if you use a quality management system, this specifies the status of the batches.
Hope it will help
Best Regards -
Batch Management-Change of batch level
Hi Friends,
I would like to convert the Batch level using T-Code "OMCE" from "batch unique at the material level" to "batch unique at the plant level." When I attempt to change the configuration, I receive a message that "This type of conversion is not yet implemented"
Could any one tell me to change batch level from material level to plant level.
Your help is very much appreciated.Hi,
First check is there any stock available for any material with batch managed if it is there then stock out means make stock zero for current & previous period then try to run the conversion program as per procedure given by SAP.
If you choose plant level, the batch number is unique in conjunction with the respective material and the plant. If you choose material level, the batch number is unique together with the material. At client level, the batch number is unique in the whole client.
To change the batch level, you have to start a conversion program. This program first checks whether conversion is possible and outputs an error log containing all batch numbers that occur more than once at the new level. Now you need to manually transfer these batch records to batch numbers within Inventory Management using a transfer posting 'material to material'.
If you change the level from plant level to a higher level, it is possible that batches with the same batch numbers in different plants are actually identical. In this case, all you have to do is remove stocks (including previous period stocks) so that all batches with the same batch numbers, except one, can be reorganized.
When you convert from plant level to material level, the material is then to be handled in batches in all plants in which it is defined.
To change the batch level, proceed as follows:
1. Choose the level at which you want your batches to be unique.
2. Save the new settings and choose Back.
3. Choose Batch level -> Conversion.
4. If necessary, carry out the conversion in test mode first.
Regards
Ravi shankar. -
Hi,
Pls explain abt batch levels and its usage and
which batch level sap recommends and
which level most of the companies are using??
as well, how to check which batch level is using for a client??Hi,
You can detail document about batch level in given path help documentation.
SPRO-IMG-Logistics general-Batch management-Specify Batch Level and Activate Status Management.
In this IMG activity, you specify the following:
The level at which batch numbers are unique
Whether batch status management is active in the client
The plants in which batch status management is active
The initial status of new batches
Batch level
Batch numbers can be unique at the following levels:
At plant level
At material level
At client level for a material
If you choose plant level, the batch number is unique in conjunction with the respective material and the plant. If you choose material level, the batch number is unique together with the material. At client level, the batch number is unique in the whole client.
To change the batch level, you have to start a conversion program. This program first checks whether conversion is possible and outputs an error log containing all batch numbers that occur more than once at the new level. Now you need to manually transfer these batch records to batch numbers within Inventory Management using a transfer posting 'material to material'.
If you change the level from plant level to a higher level, it is possible that batches with the same batch numbers in different plants are actually identical. In this case, all you have to do is remove stocks (including previous period stocks) so that all batches with the same batch numbers, except one, can be reorganized.
When you convert from plant level to material level, the material is then to be handled in batches in all plants in which it is defined.
Standard settings
In the standard delivery batches are uniquely defined at material level.
Activities
To change the batch level, proceed as follows:
1. Choose the level at which you want your batches to be unique.
2. Save the new settings and choose Back.
3. Choose Batch level -> Conversion.
4. If necessary, carry out the conversion in test mode first.
Regards
Ravi shankar. -
Changing Batch Management Level from Material to Plant
Hi all,
We are investigating changing our batch management level from material to plant to meet business requirements.
SAP has pointed us to a note with a program to reset the batch level, as well as highlighting some things to look out for.
I've conducted the change in a playpen system and so far it looks relatively straightforward, with complexities arising only when characteristics exist, or when a batch exists in multiple plants.
Seems that batch master data is moved from MCH1 to MCHA, including the object link number to classification. Unfortunately it seems a limitation of the conversion is that the batch master data is copied to ONE plant only in MCHA, no doubt due to the fact the object number link to classification must be unique.
My question is this: has anyone performed this change before, and if so can you offer me any advice on what to look out for, or potential problems that arose after the change?
Any help or comments are appreciated.
Mark.hi..
first of all try this simple one...
You will have to delete all the materials, remove stock and then switch the batch management flag.
Or
To convert the batch from plant level to material there is Conversion Program defind by the SAP...
1. For all releases lower than Release 4.5B, implement the corrections and the modification in the report RM07CHDX as described in the correction 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 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 you have 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 test mode.
try this out..hope is works,,
Thanks.. -
Dear All,
Actually i have changed the batch level form client level to material level because i have to assign same batch to another material , but while GR again production order through MB31 again same batch system gives the message batch is already assign to another material .
can anybody help me regarding this issue.
System Message :-
Batch 3000000058 is already assigned to another material
Message no. M3773
Diagnosis
You have attempted to create a batch for the specified material. However, the batch number has already been assigned to another material.
Please do the needful
Procedure
Please correct your entry.You can change from client level to material level.
"You cannot change back from a higher level to plant level in the standard system. However,
you can change the batch level from client level back to material level."
This is from SAP batch management documentation at the top of page 12:
http://help.sap.com/printdocu/core/print46c/en/data/pdf/LOBM/LOBM.pdf
I think that the conversion program might not have been run. I.e. the steps to make the change were not fully done. I would like to believe that you tried this in a sandbox and a development box and a quality control box before trying this in production.
FF
Maybe you are looking for
-
Firefox Sync custom server fails - invalid HTTPS certificate
Windows XP SP3, Firefox 3.6.8. Using a custom Sync server, the Weave minimal server written by Toby Elliot. Firefox Sync 1.4.4 extension is crapping out at the setup stage. I've got a self-signed SSL certificate behind my web server, since it's for m
-
I bought an I phone 4 from ebay and it still has the last persons icloud e-mail. How do you do a hard reset
-
Mail takes FOREVER to send. Suggestions?
I had this problem since I got my Mac and 10.5.6. I've been using Thunderbird but would like to be able to use Mail for the integration with the rest of OS X, iLife. Thunderbird works as expected, sending and receiving. Receiving is fine, but sending
-
How do I copy 1-page of a 62-page document?
How do I copy a single page of a 62 page document?
-
Rebuilding library and now iphoto won't open
We recently upgraded to Lion and now iphoto won't work. I'm trying to rebuild my library but I can't even get iphoto to open now. Has anyone else had issues using iphoto after upgrading to Lion?