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

Similar Messages

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.

Batch determination based on fifo during goods issue

Hi All,
My client requirement is that system should propose automatic batch during goods issue based on goods receipt.
I have activated batch wise split valuation.
I have maintained characterstics with MCH1 table and HSDAT.
Assigned to class and class is assigned to stratergy type.
Created sort sequence and sort rule ascennding.
Assigned this to stratergy type.
Maintained condition record also.
During goods issue to production system is not proposing the batch based on gr date.
System is not stopping me while making goods issue with other batch.
Please guide to fix the above issue.
Regards,
Venkatesh

Split valuation has nothing to do with this problem.
I hope you do not just require the sequence for physical goods issue to be FIFO because your year end valuation will be FIFO method, as this is not necessary for FIFO valuation.
IMG > Ligistics general > batch managment > batch determination > Allocation of batch determination schema and activation >...
here you set the box for batch check active, which means if a batch is entered manually then this batch is checked against the batch determination and an error is issued if the wrong batch is entered.

Automatic Batch determination based of sales order type

I want to do automatic batch determination on basis of sales document type.
1) I have made a condition table and added sales document type field in it.
2) defined Access Sequence and added that field in that sequence.
3) defined the strategy type, assigned the class "FEFO - First Expiry first out".
4) Added by condition type in the standard search procedure "SD0001".
5) added the order type in VCH1
If, i define the search strategy on material base in vch1 "SD01" then it works fine in sales order & delivery order...
but if i define it on order type then automatic batch determination doesnt works fine.
any guidance please?

solved...there was issue of expiry date field.

Automatic Batch Determination in Production order

Dear All,
We are using automatic batch determination is based on FIFO (first Mfg first out) for components..After releasing the order.
I have maintained Batch Class in all the materials which are used as a all material special Characteristic LOBM_HSDAT as a one of the class characteristic. as we want batch determination on GR date for few material and for few material LOBM_VFDAT for self life material and its class.
Then create Sort Rule CU70 mainatained the same LOBM_HSDAT in it. and one with LOBM_VFDAT.
Then create Batch serch Strategy (USE T.Code COB1- search strategy CO01the respective sort rule and selection critoria.for All ROH HALB and Finish material.
In Material Master of all component in MRP 2 view select value 3 (Automatic Batch Determination) for BATCH ENTRY. All ROH HALB and Finish material
After mainting above all prerequisite I should able to do the Automatic Batch Determination as per my selection Rule.
But Automatic Batch Determination in Production order after release is not working.
Please need your help.
Regards,
Manish
Edited by: manish gurnule on Dec 30, 2008 5:26 AM

Dear,
Define the batch determination search strategy for process order in COB1 with sort rule in CU70.
On the initial screen of your application choose Logistics>centrel function>batch management>Batch determination>For process order -->Batch search strategy --> Create.
On the initial screen of your application choose Batch search strategy -->Create.
Choose the strategy type, say choose co02
Choose the key combination-
Enter the required dat-->say plant ,production order type, product,valid from and component for which you want to have this
Choose Selection criteria push button. Choose a sort sequence.
If no values have been entered, enter the selection class and the characteristic values.
Go back to the screen on which you create a batch search strategy.
Choose Sort if required(it should be defined earlier(in CU70- here you are giving the charateristic name on which you want to sort)
For component you need to use MBC1 with search stratgey as ME01 for your plant movement type and material and assign the sort rule and search procedure here.
Check also in COR4, for the combination of plant and order type...you have selected search procedure-CO0001
Batch management> Batch serach procedure allocation and check activation
T.Code to be looked specifically OMCG , CORC
Hope it will help you.
Regards,
Madhu

Batch Determination with WM manual staging

Hello,
I found documentation that suggest to use Pick parts when using batch determination with WM in transfer orders. However will/can determination be used with Manually staged components inducator 4?
Thank you

Hi!
I am trying to get batched with shelf life larger than 370.
We are in ECC6.0 and the note applies to releases up to 4.5. I read the note and also tried it but the characteristic does not take a range; only a numberic value. For => 370 I get an error. The date for SLED calculated for batch determination (from the batch determination analysis for a test) as shown below:
Characteristic   Name                           Characteristic value
LOBM_ZUSTD       Status of Batch                Released
LOBM_LVORM       Deletion Ind. for Batches      Not Set
LOBM_RLZ         Remaining Shelf Life for Batc 370 d
LOBM_MBDAT       Material Availability Date     07/17/2008
LOBM_LFDAT       Batch Determin. Delivery Date 07/30/2008
LOBM_VFDAT       Expiration date, shelf life    08/04/2009
I wonder if the problem is that the operator does not seem to appear in this criteria for the calculated LOBM_VFDAT?
Thank you

Batch Determination In Sales Order (VA01)

Hi!,
I have activated automatic batch determination in sales order.
Batch dertimination condition customer(Sold-To-Party)-material record is maintained in VCH1. It is working fine.
Now I have required to perform batch determination based on Ship-To-Party.
Can any body guide in this matter?
Thanks
BD

Hi!
Thanks for the reply. I have already maintained the condition (VCH1) for sold-to-party. As per your advice I have also created another condition for ship-to-party. Still during batch determination sold-to-party is taking.
Now I want to remove the sold-to-party condition record. Can you tell the transaction code to delete this condition record maintained by VCH1.
Thanks
BD

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

Next inspection date in the Batch Determination Screen

Hi Gurus,
I am having problems with some user requirements because I am an abaper and I think this needs some SD expertice. Users want to see the "Next inspection date" of the batch (field QNDAT) when they do the batch determination of a delivery (Batch Split --> Batch determination). They want to see a new column in the screen, right next to the "Characteristic sort" field. I think that to put a new column in that standard screen is not possible. So I suggest to change the contents of the existing characteristic sort. And there is where I do not know how to do that. It is possible at all to have the next inspection date as a characteristic of the batch and then use it to sort?
Any help would be really appreciated.
Regards.

Hi,
Yes you can use next inspection date as a characteristics and sort the batches based on that.
Inform the user to add this characteristics (LOBM_QNDAT) in the material batch class and batch selection class using transaction code CL02.
Then in SPRO, using transaction code CU71, in the sort rule add this field as characteristics (LOBM_QNDAT).By this way the system will sort the batches based on next inspection date as parameter.
Note that the user needs to fill-in the next inspection date in all the batches in order for the sort rule to work properly.
Regards,

Issue regarding Batch determination in Production order as per Expiry date.

Dear all,
first of all happy Navratri.
I have issue regarding batch determination in production order.
I have to compare P.O header materialu2019s expiry date and issuing components expiry date at the time of batch determination.
lets take example, Material having self life is u201CXu201D years and batch determination against PO is based on FEFO with the help of self life we can determine Expiry date of manufacturing material suppose it is u201CYu201D I have to introduce restriction at the time of good issue if expiry date of issuing components u201CZu201D is less than expiry date u201CYu201D.
Please give your valuable suggestions either standard or through SAP enhancements.
thanks & Regards
SIVA

Dear
Thanks for your reply, i am layman about batch derivation can u elaborate it.
Thanks & Regard

Add the " expired date" in the batch determination

Dear Guru
we are to do the batch determination in the sales order,
I want to know is it possible to add the " expired date" in the "batch determination" ?
Thanks.

If you want to add the Expiry Date then you can maintain the same in Batch Characteristics as Expired Date while creation of Batch.
Also maintain in the Material Master Record > Plant Date / Storage 1 > Shelf Life Data - Min. Rem. Shelf Life & Total Shelf Life.
Best Regards,
Ankur

Batch determination with condition next inspection date is =10

Hi,
I want to configure the batch determination in such a way that if next inspection date is <=10 then the batch should not consider in the batch determination at the time of creation of process order, only those batchs should conside whose next inspection date is more 10 days.
can anyone suggest ,any solution on this .
Thanks
HS

Hi Shaymal & VRMP
I have checked the system, the only problem I am facing is that the system does not show next inspection date dialog box at the time of UD where I can see the next inspection date being set by the system
Say, I use QA07 (Triggered Manually) on 19.jan.08. The Next inspection date was 26.jan.08 and Initial Run in Days was 10 (days), the system created inspection lot on 19.jan.08 successfully. At the time of UD it automatically set 29.jan.08 as the next inspection date (i.e. 19.jan.08 + 10 days) istead of 06. Feb.08 (i.e. 26.jan.08 + 10 days) without showing dialog box / suggesting next inspectino date.
regards
Mobashir
Edited by: Muhammad Mobashir on Jan 19, 2009 7:11 AM

Batch Determination Expiration Date / Customer

Hello Experts,
Could you please give me a hand with his requirement?
At this moment, there is a batch strategy determination in delivery according to expiration date, First Expiration Date, First Out, FEFO, and it is working fine.
In addition to this configuration it is necesary that just for some customers the expiration date should not be under a year, otherwise they would not receive this products.
Could you let me know if there is a standard way of achieving this?
Thanks a lot for your help.

Hello Lina
Not fully clear about your requirement.
Here are my suggestions:
1) Bring in Customer into the access fields.
Path: SPRO/IMG/Logistics - General/Logistics - General/Batch Management/Batch Determination and Batch Check/Access Sequences/Define Sales and Distribution Access Sequences
If this does not work
2) Control Expiration date processing with custom code (User exit or BADI):
Path: SPRO/IMG?Logistics - General/Logistics - General/Batch Management/Shelf Life Expiration Date (SLED)/Set Up Customer Exit to Calculate/Check the SLED or BAdI: Control of Shelf Life Expiration Date Processing
Hope this helps.

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,

Batch Determination in SD - Need for Material Master Classification View

Hi!
Is it mandatory to have the classification view of the material maintained to enable expiry date based batch determination at delivery creation?
I have configured BD for the delivery. When testing with a material for which the classification view is maintained, the batch is determined. When testing with a material for which the classification view is <b>not</b> maintained, the batch is not determined.
Appreciate that this may seem like a strange question given what the testing shows but I am working with a colleague who is adamant that the classification view on the material master is not required.
Any casting votes would be much appreciated and rewarded accordingly. Thanks, Duncan

Classification of batches is mandatory if you want to use the batch determination feature.
source: http://help.sap.com/saphelp_erp2005/helpdata/en/4d/2b8bd043ad11d189410000e829fbbd/frameset.htm

Batch Determination based on date of consig recieve

Similar Messages

Maybe you are looking for