Batch determination fails.

Hello All,
Can anyone help me out in this..
When executing CORK, and processing the Goods Movements, the batch
determination within the certain materials will have various materials
"fail"
and then they will reside in the COGI report to get resolved. Upon some
troubleshooting, i found that the batch search strategy or batch
determintion
that does not allow certain materials that do not have a certain batch
class
assigned to get consumed. Seems components that have a Batch Class of
"EP_RAWMAT_CLASS" never have an issue, and those materials that are
being
consumed that do not have this Batch Class assigned always fail
Thanks in advance.

Hi
Chk you batch search startegy, bacth class, chars, sort rule .
Regards
YMREDDY

Similar Messages

No manual entry of batch, if batch determination fails to pick batch in DO

Dear Experts,
I have a scenario, where I want system to stop users to pick batch manually in Delivery order creation (VL01N), if batch determination procedure fails to auto-pick batch due to any reason.
By standard configuration, is there any-way to cater this requirement or we need user-exit only?
PLease suggest.
Regards,
Praveen

Hi Praveen
The standard SAP allows you to change manually determined batch. When the batch is selected manually, the automatic determination has failed because the batch characteristics are not proper as per the condition set in VCH1. When you manually select the batch in the delivery, then the system would throw up a message saying Invalid batch (batch number) according to selection criteria in batch determination (Message no. VL215). This is a warning message. Try changing this to an error message in the user exit.
Thanks
Indranil

Batch Determination with SLED Selection Using LOBM_RLZ

Hi All,
I am trying to determine Batches at the time of Goods Issue against Production Order (i.e. Movement Type 261).
These are the steps I have used.
1. Created a Batch Class with Standard Characteristics LOBM_RLZ, LOBM_VFDAT, LOBM_LFDAT.
2. Assigned this class to the Material Master of the Component and marked the material relevant for Batch and SLED.
3. At the time of GR for the component, the Batch is generated with the Expiration Date.
3. Created the Batch Determination Rule using Condition Table ME01 for movement type 261, plant and component.
The Search Criteria is to select a Batch with LOBM_RLZ >=1 day.
4. Now at the time of Batch Determination in CO27 (Picking TCode) the determination is failing. I can check in MB5M there are two batches of the Component available in stock with Remaining Number of shelf life as 2 days and 370 days.
Can anyone suggest what might be missing?

Are you using a separate batch selection class versus the batch class?
There are characteristics that must be in the selection class, but cannot be in the batch class.
See OSS note 33396.
1. If you want to search for batches on the basis of a remaining shelf
         life in batch determination, the system has to calculate a requested
         shelf life expiration date dynamically from the information you
         give.
     2. Add characteristic LOBM_VFDAT to the batch classes.
         For the revaluation of reference characteristics, refer to Note
         78235.
         Characteristics LOBM_RLZ and LOBM_LFDAT must not be included in the
         batch classes!
     3. Add characteristics LOBM_VFDAT, LOBM_LFDAT, and LOBM_RLZ to the
         selection classes.
         Maintain a remaining shelf life in the strategy records for batch
         determination. Relational operators (> , < , <= , >=) are considered
         in the dynamic calculation of the shelf life expiration date in
         batch determination.
From your note you have placed LOBM_RLZ and LOBM_LFDAT in your batch class. You cannot do that.
FF

Error during batch determination in sales order

Hi all,
I have this information error during batch determination: LB059 " Error when mixing configuration and selection criteria" .
Does anyone know what i´m doing wrong?
We are using materials with characteristics, and when i try the batch determination in a sales order, i got this messagge.
Thank you all!!

Hello Juan
The characteristics you used to configure the product in the sales order are passed dynamically during run time as selection criteria to determine a matching class and that's where the problem is happening.
Sit with an ABAPer to debug and find out what's the issue. Your focus for this activity should be on the following includes to Program SAPLV01F:
LV01FFC1
and
LV01FM01
More specifically, test the following Function Modules with your live data to figure out which one is failing:
CLO0_DDB_OBJ_VALUATION_OPEN
CTMS_DDB_HAS_CHARACTERISTICS
CTMS_DDB_HAS_VALUES
CTMS_DDB_DEL_VALUE
CTMS_DDB_SET_VALUE_INTERNAL
CLO0_DDB_OBJ_VALUATION_CLOSE
Hope this helps. Sorry it is hard to give a functional type of response to this very technical issue.

Batch Determination in SD - Fixed Storage Type

Hi,
We have enable automatic batch determination at the delivery stage (VL01N). for example:
Plant: 1000
Storage Location: 3000
Warehouse number: 300
Storage type in warehouse number 300: 910,911,912, NF1, NF2, NF3
In SD batch determination process in some cases batch are select from storage type 910 or 912 or NF1 (depend on unrestricted use), how to configure in SD batch determination configuration for always select batch´s from fixed storage type (in this case NF1 or NF2 or NF3).
Regards,
Enrique Figueroa
Edited by: Benito Enrique Figueroa Flores on Sep 30, 2008 11:46 PM

Nice idea, but what is your plan if no other batch is there, and all stock is in the interim storage type?
From my point of view it does not really matter where the process flow stucks, if you wait for batch assignment in delivery until the batch is in its real bin or if you do the assignment right away and the creation of WM-TO stucks until the quant is moved from the interim storage type to its final bin.
You just have to understand that batch determination and source bin determination serves usually different needs.
I usually search for a by certain quality figures to meet my customers requirement. Or by age, to always issue the oldes stuff first.
A interim storage type is a warehouse internal thing, as I already said, nothing phyiscal. And in WM you use the storage bin search to determine the bin from where you can pick the desired material and batch.
My batch determination is setup to execute automatically when delivery is created. My deliveries are either created manually at the shipping office or automatically with a batch job.
Instead of using LT03 we have to use LB10 to create a WM-TO. Of course this will fail if the quant is locked because of an open TO or if the storage type where it physically resides is not includes in the search.

Batch determination cannot pick batch

Dear SAP gurus,
We are in SAP ECC 6 EHP 7. We are using batch determination in Delivery and also availability check which include delivery item in the checking.
We have a scenario to transfer 1 pc of tock X from plant A to plant B then to plant C. We are creating STO 1 from plant A to plant B, and then STO 2 from plant B to plant C. STO 1 auto-create delivery 1 and STO 2 auto-create delivery 2. When STO/Delivery created, the stock situation for X is 10 pcs in plant A, 0 in plant B, and 0 in plant C.
When delivery 1 created, batch determination kick in, batch is determined. When delivery 2 created, because there is 0 stock in plant B, batch determination cannot determine any batch. At this time when we see stock requirement list of material X in plant B, there is -1 qty assigned to delivery 2.
After we issue stock X using delivery 1, the stock in plant A become 9, and stock in plant B become 1. Then we edit the delivery, re-trigger the batch determination in the hope now system can get the batch (because the stock already 1 now). But the problem is, it is NOT. It seems that before batch determination kick in, SAP is using availability check to determine whether there is any quantity can be commited to delivery 2. The problem is, because it thinks that planned available quantity is -1, it fails to commit the quantity, thus batch determination cannot kick in.
The weird thing is the planned availability check is -1 in the first place because the delivery 2 itself (!!) Health logic suggest that because I already order something in plant B, when the goods finally arrived in B, I should be able to pick this goods, but apparently it is NOT. I'm almost sure that the problem is in the availability check, as if I dont include delivery in the availability check, SAP able to commit 1 qty and then batch determination kicks in. But I cannot de-activate this, as we dont want Sales Order and DO commit to quantity that already book.
Is there something that I miss in here?
Best regards,
John

Hi,
Anyone have suggestion on this?

Batch Determination While Goods Issue

How To Active batch Determination at the time of issue the goods
I have done following SPRO setting .
Strategy type --> YB01
Inventory managment Search Procedure --> YB001
Allocation IM Search Procedure -->> 261assigned to YB001 along with Active "Check batch"
In MBC1....for Search Startegy YB01 , for combination of Movement Type/Plant/Material ,materil assignement made as
material 40100
No. batch -999
Changed Allowed : Check
Uom : B
Mproposal : Active
Material Master of raw Material 40100
Material Master batch Management tick active
Classifcation view : Class As Shelf life
Characheirstics :Remaining Shelf Life
Now i have cretaed prodcution order of 10 qty ..
I have Four Batches With Differnt Life is available in Stock...
Now i want to see this Four batch at The time of Issue so that i can select one of the batch for issue..
Right now i m not getting Batch determination ..
What else i have to do ...
Please Guide..

Dear,
Have you created the sort rule in ACU70 with LOBM_VFDAT?
Have you assigned the sort rule in MBC1?
Also check Implementation Guide for R/3 Customizing (IMG)-- Logistics u2013 General-- Batch Management--Batch Determination and Batch Check -->Batch Search Procedure Allocation and Check ActivationAllocate IM Search Procedure/Activate Check
Assign for 261 mov type - YB0001.
Same need to assign in OPL8 also please try and come back.
Regards,
R.Brahmankar

Batch Determination at Storage location Level

Dear All,
I have one question on batches when I am entering stock against batches in Outbound Delivery Note (as batch split ) the batch determining the storage location is different not the one which it belongs to, I need the batch stock should be determine in same storage location not the different one.
For example: I have 5 storage locations, each storage location contain 5 to 6 batches;
Storage Location: WO1, WO2, WO3, W04 AND WO5
Batches: A1,B1,C1,D1,E1 etc.
Stor. Loc    Batches
1. W01:             B1, B2, B3, B4, B5, B6
2. W02:             A1, A2, A3, A4, A5
3. W03:             C1, C2, C3, C4, C5
4. W04:             D1, D2 D3, D4, D5
5. W05:             E1, E2, E3, E4, E5
I. If I enter B1 and stock 10kg then it automatically determining storage location as W02. Actually it belongs to storage location W01 it should be the same W01only
II. If I enter C1 and stock some 15kg then also it automatically determining storage location as W02. Actually it belongs to storage location W03 it should be the same W03.
Kindly give me the solution.
Thanks in advance
Regards,
MH

Clsing due to no reply

Issues during Component Batch Determination for Process Orders

Hi,
I am encountering a strange issue during component batch determination of process order.
1. During creation of process order, when I execute batch determination, systems does determination based on strategies we have set and when I click on Copy it gives an error
"Log cannot be saved: Object/subobject not specified"
Message no. BL201
*Diagnosis
Log save cancelled because at least one log contains no object or subobject.
Object and subobject are needed to classify application logs because there are several log types. Only a few logs are managed in main memory at runtime, so this classification is not needed.
If the logs are to be saved in the database, object/subobject must be specified for later retrieval.
Procedure for System Administration
Object/sub object can be passed when a log is created (function module BAL_LOG_CREATE) and changed with BAL_LOG_CHANGE.
The possible values for object and sub object must be configured in transaction SLG0.*
If I save the order with CRTD status and come back again in change mode and do determination, It works fine.
Again when the order is in REL status and do the determination, It gives the same error.
This happens only for a specific plant, In other plants batch determination works in all scenarios.
I checked for all plant related Config for batch determination and coudn't find any discrepancies.
Please advise how to resolve this issue. Thanks in advance for your help
Regards,
Aheesh

There Is no direct solution for your requirement just try this work around.
While defining the batch determination search strategy for process order in COB1, there is one column Quantity proposal where you can attach the Routines (This is written in ABAB code ) make use of this, define New Routines with ABAB help to fulfill your requirement. Try this if found useful award full points.
Regards,
Ajay Nikte

Batch Determination based on date of consig recieve

Hi,
I am getting problem when i am trying to do manual batch determination in the outbound delivery.
I have created a record in VCH1 based on customer/Material/Plant. In this i have maintained a sort rule also. what characteristaics i must use to make my batch determination based on customer consignment recieving date?
If i go in MSC3n with Material, Plant and batch data then in the screen ( table MCHA, MCH1) onlt data available is for ERSDA, LAEDA and LWEDT.
In delivery when i click on batch determination button. my Sort rule is not automatically determined. So i have to maunally entered my soirt rule but at the same time my qty proposal in the same screen is 1 which is nothing but
FORM CHMVS_001.
DATA: lv_line TYPE kondh-chasp VALUE '1'.
LOOP AT disqty.
    CHECK lv_line <= no_of_split.
    IF QUAN_TO_DIS > 0.
      IF DISQTY-AVAL_QUAN > QUAN_TO_DIS.
        DISQTY-QUANTITY = QUAN_TO_DIS.
      ELSEIF disqty-aval_quan > 0.
        DISQTY-QUANTITY = DISQTY-AVAL_QUAN.
      ENDIF.
      IF disqty-quantity > 0.
        quan_to_dis = quan_to_dis - disqty-quantity.
        MODIFY disqty TRANSPORTING quantity.
        ADD 1 TO lv_line.
      ENDIF.
    ENDIF.
ENDLOOP.
ENDFORM
When i am taking characteristics LOBM_VFDAT for sort rule in Cu70 then i am not getting batch determination as i required even if i maintained Shelf expiry date in MSC3n.
Please suggest where i must look into so that my batch determination would be based on date of consignment recieved.. currently if it s taking based on max qty available in MMBE.
Regards
Nitin

I have already assigned sort rule in VCH1 but dont know which Characteristics i must assign for customer consignment stock on FIFO basis. Could you please tell me the characteristics for it which i must consider?
LOMB_VFDAT i have already tried but its not working for me.
Edited by: Nitin Agarwal on Oct 30, 2008 8:14 AM

Batch determination -sort rule -reg

hi,
requirement is :
Through COR2 , for the process order's component when batch determination is done , Batch determination should first select for the unrestricted stock in the storage location and once all the unrestricted stock is consumed then only batch determination should happen from the stock of the batches of the consignment stock in the storage location.
With in the stock of the storage location ... first it should check for unrestricted stock -with in unrestricted it should sort based on GR date of the batch and consume the oldest batch.Once all unrestricted is consumed then only it should look for consignment stock consumption , again based on the Gr date and consume the oldest batch with in the consignment .
We have created a sort sequence with unrestricted stock as the first characteristic (table MCHB-field CLABS in the additional data tab of the CT04) and then Gr date in ascending (table MCH1-Field LWEDT)
and also tried with the combination of consignment stock also (from MARD table ) but it is not working as expected
System is always picking the oldest GR date batch irrespective whether it is unrestricted or consignment as sorting is done for the characteristic Gr date which is updated in the classification tab of the batch when it is created .
Can the multiple sorting ( first sort on stock type :unrestricted / consignment & then on gr date) is possible in standard SAP
please guide us
regards,
Madhu Kiran

Hi Madhu,
I have the same issue. What was your solution please ?
Thanks in advance,

Stock determination in Batch determination.

Hi Freinds,
Scenario is as follows:
Batch determination is already active with FIFO logic. There are 2 types of stock ( Own unrestricted and consignment)with batches in same storage location.
If I maintain stock determination rule as 'consignment' in Component material master then only consignment batches are pulled in production order component overview while Order release.
If i dont maintain stock determination rule then batch determination is done with FIFO logic and accordingly batches are pulled in correctly but then if the batch is from consignment stock, there is no Special stock indicator 'K' in the component overview against the consignment batch.
Is there any way I could pull in the special stock indicator keeping the FIFO logic same in batch determination.
Please note that batches are already pulled on FIFO logic and requirement is to bring in the special stock indicator K if batch is from consignment stock. I dont want any particular stock type to be given priority since batches are pulled on FIFO base irrespective of stock types.
Can we fulfill this requirement ?
Any inputs would be highy appreciated.
Thanks in Advance
Shailesh Nadkarni.

I have only worked on a scenario where there needs to be priority assigned based on stock type first followed by batch, but not this one so the below is not from exp. but just a suggestion.
Add a characteristic to your batch determination procedure being used for production orders for stock type. With that in place, check if you can get the stock type passed to the order as per your need.
Give it a try n let me know if it works, meanwhile if there is anything else which comes to my mind will post in here.

Batch determination based on WM storage type stock positions

Hello experts,
I am hoping the get some advise on the best method to achieve this:
We have batch determination turned on for select customers and the system is proposing stock that is mainly in our each or lose pick storage types (110), the issue with that is the fact that we do not pick in less then case qty for those customers so if the stock doesn't exist in our general storage the user must re-determinthe batch codes before delivery release.
This process is becoming very time consuming so I would like to improve it.
My first thought is to create a custom check in the batch search strategy that will only propose batch codes that exist in our general storage (search strategy based on WM stock positions)
Are there any other options to achieve a batch search strategy based in WM stock positions other then the one above and does that solution sound practical?

I'm not referring to the type of picking either (i'm not referring to picking strategies at all). I'm referring to storage type search criteria defined in OMLY.
"We need batch determination based on WM storage type stock positions" -> you are running BD at delivery level and therefore, there is nothing from a standard perspective that we can do to run BD based on WM storage type again. Since the BD has already occurred, we need to find other venues to direct the pick to the appropriate storage types.
This is what I'm understanding but I reckon there's something that I'm missing and so let's take the below example and then you can get back with corrections:
R001 plant
ZM01 storage location
Z01 WH
110, 120, 130, 140 storage types (110, 120, 130 are case/lose pick, and 140 is general)
Since you had mentioned earlier that the BD is running at plant level, I'd assume the storage location ZM01 is automatically determined (since the batch resides in ZM01). Since the batch is already determined, based on your 'storage search strategy' (110, 120, 130) the system tries to pick this batch in these storage types. Now, when there is no full case, you have to manually change the storage type to 140 to pick and this is where the problem is. So, I was recommending that since there is no standard way to automatically pick the full case from 140, use the enhancement.

Table for batch determination date

hi,
im printing the Dispensing slip...they want the output based on the batch determination date..
can any one tel me in which table i willl get batch determination date?
Regards
Smitha

Are you using a separate batch selection class versus the batch class?
There are characteristics that must be in the selection class, but cannot be in the batch class.
See OSS note 33396.
1. If you want to search for batches on the basis of a remaining shelf
         life in batch determination, the system has to calculate a requested
         shelf life expiration date dynamically from the information you
         give.
     2. Add characteristic LOBM_VFDAT to the batch classes.
         For the revaluation of reference characteristics, refer to Note
         78235.
         Characteristics LOBM_RLZ and LOBM_LFDAT must not be included in the
         batch classes!
     3. Add characteristics LOBM_VFDAT, LOBM_LFDAT, and LOBM_RLZ to the
         selection classes.
         Maintain a remaining shelf life in the strategy records for batch
         determination. Relational operators (> , < , <= , >=) are considered
         in the dynamic calculation of the shelf life expiration date in
         batch determination.
From your note you have placed LOBM_RLZ and LOBM_LFDAT in your batch class. You cannot do that.
FF

How to trun off batch determination for certain shipping points ?

During Delivery Notes creation we would like to turn off the batch determination on basis of certail shipping points. can some please guide what is the best way to do it. We do not want it turned off for all the shipping points but for a special ones.
The idea is when we create Delivey for certain shipping point we do not need to fill in the batch code and yets save, pick confim, goods issue during delivery creation process....
we have sepcial shipping points for consignment process and for them we need to skip the batch determination......
Thanks in advance
Rajey

I don;t think you can control based on shipping point because batch creation is controlled at movement type level

Batch determination fails.

Similar Messages

Maybe you are looking for