Bin at Batch LEVEL

Hello Experts,
We have bins that are set up at batch level ...we dont want this setting cos when we are running analysis it is giving a wrong value in one of the key figure....
can any one tell me is it cycle counting at batch level can we change it to storage location level please explain ...
EXample: we use an exception ...when ever the bin is empty it should trigger the exception but suppose there are 3 batches in the bin whenever you issue a batch it is trigerring the exception ...suppose if there are three issue it should trigger once but it triggers three times PLEASE HELP
Will award full points
Thanks
J

In general, the fixed bin strategy allows you to specify the bin to which a material will be placed during a putaway transaction (provided the concerned storage type has putaway strategy configured as F).
I understand your requirement is to place different batches into different bins ie the bin is determined depending on the batch.
While not possible in standard, you can try making use of an exit for this purpose. The exit MWMTO003 may be used in CMOD to develop your own putaway strategy. You will have to activate the exit (a checkbox) in the putaway control parameters in the storage type configuration.
Check the documentation in the following IMG path:
Logistics Execution > Warehouse Management > Strategies > Putaway Strategies > Develop Extensions for Putaway Strategies
Hope this helps.
Regards,
Aroop

Similar Messages

Stock transfer valuation error at batch level

Dear All,
I have an issue with Stock valuation at batch level, when a site to site stock transfer is done in the ERP.
As a consequence, Stock values in reporting are completely wrong.
As a standard behavior for stock transfers, we have the following article movements in the ERP :
MatNo      MovTyp Date      Plant      Stor.loc.    Batch      Qty.    Value
MAT1      101    01.01.06 USD1      0001         HJ01       1         180000
MAT1      641    15.01.07 USD1    0001          HJ01       -1      -180000
MAT1      641    15.01.07 3041                                     1      180000
MAT1      101    16.01.07 3041      0001           HJ01       1       0
We are using 0IC_C03 cube, with 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
In 0IC_C03 cube, if we do a query at site level for this article, everything is correct :
MatNo     Plant     Qty.    Value
MAT1      USD1     0     0
MAT1     3041     1     180000
Then if we go at batch level, the value for the batched article is wrong (0).
The real value is held by the "empty batch" article.
MatNo     Plant     Batch     Qty.    Value
MAT1      USD1     HJ01     0     0
MAT1     3041               0        180000
MAT1     3041     HJ01      1     0
We already implemented the workaround on storage location level (How to "Realize summarized display of stock values on
storage location level").
But the same principle wouldn't work here, as the purpose of the batch is to have different valuations by article.
If we have then several batched article in the same site, we would apply an average value to them, which would also be wrong.
I tried to apply OSS note 589024, but for the same reason as described above, this is not working.
Would you have any clue or similar experience ?
Thanks for your help,
Stephane.

Hi.
I would also appreciate an answer to this problem, if you have one. . .
Thanks in advance,
Ian.

How to use BAPI_MATERIAL_AVAILABILITY Function Module at batch level?

How to use BAPI_MATERIAL_AVAILABILITY FM to check material available at batch level?
And another question is what's the meaning of 'CHECK_RULE' in this FM. Thanks!

Field name : PRREG
fcheck more details on f1 help...
check_group defines the checking procedure to be used for availability check in individual applications.
along with the checkg group, checking rule specifies the final procedure for chkg..
eg:
ST for stock transport order
AQ for SD order project srock
also chk this help doc.
http://help.sap.com/saphelp_470/helpdata/en/cf/70124adf2d11d1b55e0000e82de178/content.htm
search the forum for sample code..
How to use BAPI_MATERIAL_AVAILABILITY Function Module....

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.

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.

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.

Goods issue error at batch level stock

Hi Experts,
In MMBE for Material 12121426 Plant 6348 storage location 0001,batch 4065634891 in storage
location level have stock is 12.000 EA and batch 4065634891 level stock is
4,164.000 EA
User is performing Goods issue through MB1A 261 movement type For 4,164.000 EA EA but showing error
is Deficit of SL Unrestricted-use 4,152 EA : 12121426 6348 0001 4065634891
Please suggest any one why batch level stock not updated to storage location level and why system not allowing batch level stock in MB1A How to rectify this error
Regards
Mohan

You probably have to contact SAP. There is hot news about inconsistencies between batch stock and storage location stock: 1930161 - Stock inconsistencies in table MCHB for batches
See as well KBA 1963022 - More details on the stock inconsistencies situation mentioned in Hot News 1930161

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,
MdZ

Hi,
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

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 Level Stock

Hi All,
I am using Batch management in ECC6.0. All stocks are maintained at batch level. I wnated to know in which table this batch level stock data is stored. I know that in Table MARD storage location level stock data is stored in LABST.
Pls. help.
Thanks
Sanjay

hi Sanjay,
Batch Stocks are maintained in table MCHB.
- Rahul

What's the purpose of "Conversion of Batch Level"?

Hi, MM Gurus!
T-Code OMCT is to activate the Conversion of Batch Level.
Is this step mandatory? Why?
If batch management is requried only at material level, still needs to run OMCT?
Thanks in anticipation.
Regards,
Jason

Hi,
SAP allows a configuration setting for 3 different batch levels. This wills effective your possibilities. Option Number 2 is the default configuration for SAP out of the box:
1.) Plant - can allow for the Batch Management Flag on a material sold out of 2 different plants to be set independently. Batch numbers can be used for multiple materials, and batch specifications and analytical results can be different for each batch (multiple batch Master records).
2.) Material - Batch Management flag is set the same for the material across all plants that use it. Batch numbers can be used for multiple materials, however, batch specification and analytical results are the same for the batch (one Batch Master Record).
3.) Client - Batch Management flag is set the same for material across all plants that use it. Batch number can only be used for one material across the client. (One Batch Master Record).
If the Batch level flag is set at the Client level, it allows for a batch number to be used with only one material throughout the entire SAP client. This is troublesome with products which are produced in bulk and then packaged into smaller size containers for sale. Due to the limitation of having only one batch number per material, when the product is packaged, new batch numbers have to be assigned to the finished packages, even though the same bulk material is being used inside the package. Because of this work-a rounds have been created and business processes adjusted to accommodate this restriction.
May be some one explain some more details.
regards

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

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,

Bin at Batch LEVEL

Similar Messages

Maybe you are looking for