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

Similar Messages

Deactivate creation of new next inspection date on re-GR

Our user created GR (MIGO) against a PO and subsequently a new batch with a next inspection date was created based on inspection interval set to 730 days.
The user agin after a few days did GR against the same PO and the next inspection date was again calculated based on this GR date and the interval. We do not want this re-assignment of the next inspection date once it has been set. Please help.
Mrunal

The problem is a user error.
When you receipt a material that has a shelf life requirement, you must enter in the production date, (manufacture date), in the GR. If you don't, it will default in the current date and usse that to calculate the expiration date.
On the second receipt, the same thing will happen. If the same batch is specified, if I remember correctly, the system should give a message that "batch has already been receieved" or some kind of warning. For the production date, I believe it will still default in the current date. I think there is another warning that the expiration date will be recalculated and a "do you want to continue" question. If they blow through all these warnings, the system takes the new manufacture date and recalculates the new expiration date. To the best of my knowledge you can't change this. The users must be trained to ALWAYS enter in the correct prodcution date.
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,

Next inspection date is not updated in batch / prposed at the time of UD

Hi
I have configurted the system for retest of batches, the system successfully creates the inspection lot but when does not propose next inspection date at the time of UD nor it updates in Batch Master.
I entered inspection interval days in QM View, the system entered the first inspection date correctly. Also Batch Restriction is working properly.
Kindly help.
regards
Mobashir

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

Report to get next inspection date from msc2n

Dear All ,
I am trying to create a report for materials batches and the next inspection dates in msc2n . Is there a report of this type available in standard SAP ?
Secondly
From msc2n it gives the field as QNDAT in table MCHA . However I notice that when the dates in msc2n are manually changed or many other times the fields QNDAT in MCHA are completely blank . I have how ever noticed that the field QNDAT in MCH1 gives all the next inspection dates . How ever it is not mentioned in msc2n > How could this be explained .
Ram~

Hello Ram,
No there is no such STD trx available that can give you your desire list for 'Next Inspection data'.
Regards,
Shyamal
Edited by: Shyamal Joshi on Dec 23, 2008 11:48 AM
Yes As correctly suggested by Ashok the table is MCH1, from where you can find all the details you need. along with the changed (Updated record) through MSC2N.
Edited by: Shyamal Joshi on Dec 23, 2008 2:24 PM
Dear Ram,
BMBC will not help you to see the 'Next Inspection Date' in list form for all the batches in one screen. You will need to go to the Batch detail Change-Display for each batch to meet the requirement. While the table MCH1 is 100% satisfactory one for your requirement.

Next inspection date

"Inspection interval" is defined in the QM view of Material Master, and the system is calculating the Next inspection date from mfg. date automatically, and feeding it automatically in the relevant field in the Batch.
Hence, we need to change u201CNext inspection dateu201D manually for each previous batch if it is revised on the basis of stability, which is practically vary difficult.
Requirement: Retest period shall be revised if changed updated in material master for inspection interval.
AYK

Dear AYK
From your post it appears that you have Batch Management activated lready and QM functionality you are trying to activate subsequently.
I think you need to make use of Recurring inspection for Batches with Shelf Life Expiry Date (SLED) then only this functionality will work in totality. For this purpose in QM view add Inspection interval period alongwith SLED data
You can use Trigger manually ( T.code QA07) or Job planning ( T.code QA05) for this purpose.
Incase you just want to update next Inspection, you need to do one by one OR make LSMW for same.
Hope this will give you clue
Regards
GIRISH

Variable Next inspection date

Hello Forum,
I am working on a requirement of Variable Next inspection date. First time the next inspection time line is after 6 months and 2nd time it should be triggered after 4 months and subsequent one at each month . There is only single field as Inspection interval in the material master. After looking superficially it looks to me that we can realise this through the exit QEVA0003.
But before designing in detail using this exit I would like to understand whether we can achieve this with any other standard SAP functionality -. Bespoke development and exits are the last thing I like to suggest to clients if we have standards SAP way to do the same thing .
Regards
Kaushik

You are correct.
The customer exit 'QEVA0003' inputs the next inspection date of batch master.
User can change the next inspection date at transaction MSC2N or MSC5N in SAP standard.
But if you have variable interval for recurring inspection and want to assign next inspection date automatically, you should implement the exit 'QEVA0003'.
Regards
Luke

Next Inspection Date in case of Mov. Type: 309

Hi,
During Transfer posting using Mov. Type: 309, (Inspection Type: 08) the Next Inspection Date is coming as per our logic of UD Date + 365 (Inspection Interval maintained in Material Mst.).
But our requirement if that, the Next Inspection Date in case of transferred material must be same as from which transfer has been done.
e.g. suppose material ABC is received with GR (Mov. Type:101) and its Its Next Inspection date is coming as 01/01/2012 (as its UD was done on 01/01/2011 + 365 (Inspection Interval maintained in Mtrl Mst).
When we transfer this material to XYZ (with Mov. Type:309), its Next Inspection Date is required that of ABC (01/01/2012). But, as per present logic it is coming UD Date + 365 Days = 23/01/2012 (i.e. if UD is performed on 23/01/2011).
How can I do that ?
Thanx
Vivek

My guess is your batch level is at the plant level. If the batch level is changed to material level or client level, this problem would go away. This can have major impacts in other areas so it must be carefully considered. But if this your requirement, it sounds like you might be at the wrong batch level right now.
FF

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

Automatic inspection lot creation upon reaching the next inspection date

Hi qm experts,
I have this scenario; my client wants to make an automatic inspection lot creation as well as posting to quality inspection stock of certain materials upon reaching its next inspection date defined in the msc2n transaction; how shall i make the inspection set-up of this materials??Thanks
Regards,
Matildo, Edsel F.
QM Consultant

Ok, you have me confused. You want to do this as a one time thing? I thought you want it to look every day, or every week, for batches that have reached their next inspection date?
If its a one time thing, then yes, just run QA07 one time. It only looks at unrestricted inventory. Do not set up any parameters in the bottom half of the screen for expiration date. If you do, any of those that have reached expiration date will be moved to blocked stock and no inspection lots created.
If you want this to run regularly, you, or someone, needs to use QA05 to set up the batch job to run on a regular basis witht the approriate "days" value for how often your running it and how far in advance of the inspection date you want lots created. And of course tick on "to inspection stock".
There is no "automatic creation" as I think your thinking. You either run QA07 once a day, or once a week or as often as you want to. OR you set it up in a batch job (QA05) to be run once a day, once a week or as often as you want to.
When the batch job is running, it 'appears' that the lots get created automatically. But it is the QA07 program being run in batch that is creating them.
Craig

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

Batch Determination With out characteristics ..?

Dear Experts
I have finished the batch determination for the SLED but i had to create characteristics for it refrence to VFDAT field in MCHA table
but I need to knowhow to refer direct to the field with out refering to the characteristics
for example I need to create a batch determination for the creation date of the batch so I want to refer direct to the field ERSDA in table MCHA .. I don't want the user to enter while doing a GR to enter the creation date of the batch in the classification of the batch
If its not possible to do such a thing .. so how can I make the characteristics which will hold the creation date of the batch to get the date in field ERSDA automatic
Best Regards
Edited by: Sap Sap on Jul 19, 2009 10:42 AM

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

Problem in batch determination with Transfer Order

Hello,
I want to use SLED batch determination to supply my shop floor from my central warehouse.
I activate the SLED batch determination procedure for WM and I create the search strategy for movement code 319.
When I convert my transfer requirement in transfer order the batch proposed is the first batch number while it's not the first expired.
In my TO if I choose to display the Batch determination, the list is well sort by expired date, and so the first batch of the list is the first expired. So why it is not this batch that is proposed in the batch field of my order ?
Thanks for your help.
Laurent.

Hello,
thanks for your answers.
I confirm that the removal strategy is H for the storage type 200 (the warehouse where the component come from).
The search strategy seems to be well maintened because when I display the Batch determination in my TO (Environement/Display Batch det.) , I obtained the list of batch sort by expired date. But in the field batch it still the first batch number that is proposed.
What do you mean by "(i.e. storage type, section are choosen according to Whse & Material master indicator and bins do exist)" ?
Laurent.

Automatic batch determination with fixed batch number for production order

Hello all,
I want to create a production order where the batc number can be assigned for one component as Batch fixed value once the order is released.
1.- I have created the characteristic (CT04) assigned to the table MCHA and field CHARG (Batch number) and one value: LINER.
2.- I have created the class (CL02) and assign to this the characteristic.
3.- I have created the sort ZSORT and the batch (MSC1N).
4.- I have checked the classification in the material and it has assigned correctly the class and characteristic and the MRP2 view has the backflush = 1, batch entry = 3 and the prod. stor. location = COIL.
5.- I have created the strategy (COB1, strategy type CO02) and assigned the selection criteria and sort.
6.- I have created the order (CO01).
7.- I was releasing the order and the batch number was assigned but, with numbers!! and I need assign this with fixed value = LINER.
Could you help me please? How can I do it?
Kind regards,
SP
Edited by: SANDRA PALOMO on Mar 15, 2011 11:28 AM

Hi Vishwas.K
Thank you for your respone, but, doing more researching, let me explain you with more detail:
1.- I am going to the transaction CO02 in order to release the order, but, before it, I am checking the component by Go to > Overviews > Components.
2.- Then, I am selecting my component and making a click in "Batch determ. " button.
3.- The system is showing me many batch numbers and I select the "Selection criteria" button and the system said: "Selection class "LINERBATCH" does not contain any selection criteria". But, it has a characteristic that I have created before.
4.- Then, I select in the new screen "Selection criteria: Origin..." the"create" button.
5.- The system selection my class from the material classification and when I go back to the last screen, finally the system is showing me my batch: LINER.
Do you know why my selection criteria with my selection class is not working in automatic?
Thank you for your time and support.
Kind regards,
Sandra Palomo

Calculated measure with condition on 2 date dimensions

Hi,
I built a cube which has 2 different time dimensions, let's say Time1 and Time2 (which both have 2 levels : Year and month), and a measure we'll call measure1.
I would like to define a new measure as a calculated member, that would sum the values of measure1 only where Time1 <= Time2.
Should I write it in SQL, the query would be :
SELECT Sum(measure1)
FROM table
WHERE Time1 <= Time2
Seems to me that it would be an easy thing to do, but as a beginner with MDX I can't find anything that seems to work consistently.
Any help would be appreciated.
Thanks in advance

When you expect to filter time like Time1 <= Time2, you can do it in MDX if it is from the same dimension and same attribute using the range operator ":".
But when it is different dimension you can achieve the same by filtering members from the dimensions. Select all members from dimension1 and dimension2 that you want to analyse, no need of creating new measure.
Theoretically speaking member x1 from dimenion1 is not same as member y1 from dimension2 and you cannot filter x1 on the basis of the y1.
Since I don't know exactly what is your scenario is, alternate approach is as below. It is a sample query, where I am expecting goods to be delivered the same day it is shipped.
with member [measures].[ship date] as Int([Ship Date].[Date].currentmember.Member_Key)
member [measures].[delivery date] as Int([Delivery Date].[Date].currentmember.Member_Key)
member [measures].[late shipping] as iif([measures].[delivery date]>[measures].[ship date],[Measures].[Sales Amount],0)
select {[Measures].[Sales Amount],[measures].[late shipping],[measures].[ship date],[measures].[delivery date]} on 0,
non empty{[Delivery Date].[Date].[Date]*[Ship Date].[Date].[Date]} on 1
from (
select ([Delivery Date].[Date].&[20030713],[Ship Date].[Date].&[20030708]) on 0
from [Step-by-Step])
http://www.bifeeds.com

Batch determination with condition next inspection date is =10

Similar Messages

Maybe you are looking for