Batch Level Changed

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

Similar Messages

  • Batch level change

    Hi Experts,
    I am phasing the problem in batch management, i maintained batch unique at material level.
    But as per my client requirement batch unique in plant level.
    i am trying to change batch unique at manterial level to plant level system is not allowing me to change
    it says ''this type of converstion is not implemented''.pls help how to slove this issue....pls.
    thanks
    RBR

    Hello Bashkar,
    According to SAP help you cannot realize your wish...
    http://help.sap.com/saphelp_46c/helpdata/en/25/2838714f7811d18a150000e816ae6e/frameset.htm
    I have one idea: what if you set the stock level to 0 and archive all existing batch records? Maybe you can change the batch level. You'd better try it in your test system first... (???)
    BR
    Csaba

  • 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.

  • MM42 change material, split valuation at batch level, M301, locking table

    Dear All,
    I'm working on ECC 6.0 retail and I have activated split valuation at batch level.  Now in MBEW for this specific material I have almost 14.400 entries.
    If I try to change some material data (MM42) I receive an error message M3021 A system error has occurred while locking and then Lock table overflow.
    I used SM12 to see the table (while MM42 is still running) and it seems that MBEW is the problem.
    What should I do?  For any material modification the system has to modify every entry in MBEW? Is there any possibility to skip this?
    Thank you.

    Hi,
    Symptom
    Key word: Enqueue
    FM: A system error has occurred in the block handler
    Message in the syslog: lock table overflowed
    Other terms
    M3021 MM02 F5 288 F5288 FBRA
    Reason and Prerequisites
    The lock table has overflowed.
    Cause 1: Dimensions of the lock table are too small
    Cause 2: The update lags far behind or has shut down completely, so that the lock entries of the update requests that are not yet updated cause the lock table to overflow.
    Cause 3: Poor design of the application programs. A lock is issued for each object in an application program, for example a collective run with many objects.
    Solution
    Determine the cause:
    SM12 -> Goto -> Diagnosis (old)
    SM12 -> Extras -> Diagnosis (new)
    checks the effectiveness of the lock management
    SM12 -> Goto -> Diagnosis in update (old)
    SM12 -> Extras -> Diagnosis in update (new)
    checks the effectiveness of the lock management in conjunction with updates
    SM12 -> OkCode TEST -> Error handling -> Statistics (old, only in the enqueue server)
    SM12 -> Extras -> Statistics (new)
    shows the statistics of the lock management, including the previous maximum fill levels (peak usage) of the partial tables in the lock table
    If the owner table overflows, cause 2 generally applies.
    In the alert monitor (RZ20), an overrunning of the (customizable) high-water marks is detected and displayed as an alert reason.
    The size of the lock table can be set with the profile parameter u201Cenque/table_size =u201C. specifies the size of the lock table in kilobytes. The setting must be made in the profile of the enqueue server ( u2026_DVEBM.. ). The change only takes effect after the restart of the enqueue server.
    The default size is 500 KB in the Rel 3.1x implementation of the enqueue table. The resulting sizes for the individual tables are:
    Owner table: approx 560.
    Name table: approx 560.
    Entry table: approx 2240.
    As of Rel 4.xx the new implementation of the lock table takes effect.
    It can also be activated as described in note 75144 for the 3.1I kernel. The default size is 2000 KB. The resulting sizes for the individual tables are:
    Owner table: approx 5400
    Name table: approx 5400
    Entry table: approx 5400
    Example: with the
    u201Cenque/table_size =32000u2033 profile parameter, the size of the enqueue table is set to 32000 KB. The tables can then have approx 40,000 entries.
    Note that the above sizes and numbers depend on various factors such as the kernel release, patch number, platform, address length (32/64-bit), and character width (Ascii/Unicode). Use the statistics display in SM12 to check the actual capacity of the lock table.
    If cause 2 applies, an enlargement of the lock table only delays the overflow of the lock table, but it cannot generally be avoided.
    In this case you need to eliminate the update shutdown or accelerate the throughput of the update program using more update processes. Using CCMS (operation modes, see training BC120) the category of work processes can be switched at runtime, for example an interactive work process can be converted temporarily into an update process, to temporarily increase the throughput of the update.
    For cause 3, you should consider a tuning of the task function. Instead of issuing a large number of individual locks, it may be better to use generic locks (wildcard) to block a complete subarea. This will also allow you to considerably improve the performance.

  • Changing Batch Level

    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,

  • 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.

  • 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

  • Batch Management - Changing Material level to Plant level

    Hi friends,
    We are configuring batch management for ECC 6.0 with CRM 5 .
    I can see the batch level in my system as Material level. But we would like to convert  batch level in to Plant level. when i try to convert the batch level i am getting error "This type of conversion is not implemented".
    There is no batch record exists in the stock.
    Please clarify why can't able to change to plant level from material level.
    Thanks

    YOu need to use  the OSS note 41715
    This will explain what exactly you need to do.
    Please go through the above OSS note.

  • Err in change Batch level

    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

  • Batch management level change to plant level

    Hi,
    Currently,i am using batch managment at material level.I have created material and has its stocks.
    I need to convert it to plant level..How can i convert it to plant level?
    Thanks
    Srini

    Hi,
    Please check the OSS Note 41715 - Resetting batch level from material to plant level.
    Hope it helps you.
    Kuber

  • Batch Management- batch level

    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.

  • 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
    Zhongkai

    Hi
    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

  • Make invoice with item level only not by batch level

    Hii
    i made a delivery doc say material 'A' having batch1,batch2,batch3 with different qty .
    exp:(VL03N)
    material a batch1 10ton
    material a batch2 20ton
    material a batch3 30ton
    Now i wanted to club all this qty and do invoice with single item for 'Material A' ,it shouldn't come with batch level wise material .
    so in vf01 it should look like this .
    material a 50 ton .
    Plss suggest what should i do for this cases ?? if poosible for changes in routine vbrk/vbrp in copy control then kindly suggest /
    sourav .

    Hi,
    Is your requirement for printing the invoice or while creating the invoice [VF01] Please confirm.
    regards,
    Chetan

  • Batch Master Changes reflecting all plant with same Batch

    HI,
    When we are doing any change in Batch Master ( MSC2n ) for one plant  like Shelf Life expiry date or Classification data for one plant.
    its automatically reflect on all plants for same batch.
    Example:
    Material : 123456
    Batch :  10925
    Shelf Life Expiry is : 31.12.2014
    Plant : 1000
    This Batch is available on 10 plants for same material.
    Now when i change Expiry date from 31.12.2014 to 31.12.2015 on Plant 1000 for Batch 10925
    its also change on all other 10 plants.
    How can we restrict this behaviour we only want to change on 1000 plant . should not change other plats.
    Regards

    Thanks all for your replies. yes i have check the system and Batch Level is defined on Material Level.
    Jurgen actually this question is not related to expiry exactly. just for
    good understanding of question i put question like this.
    in classification tab we have one parameter  "Release Status" which have value
    X or Y. X means release and Y means Not release.
    We are using this parameter for Auto batch determination purpose. if value is Y then this
    batch will not come in auto batch determination.
    same thing happend to this parameter. when we change value of this parameter in classification in one plant it is refelecting on all plants. which i dont want.
    i hope you get my point.

Maybe you are looking for