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

Similar Messages

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

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

"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

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,

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

While uplading Flat Files data to BW without movement type...........

Hi
We have to populated historical data to BW. In r/3 we are maintaining MM data with respect to Movement Type.
However, the historical data which is provided to me is not with respect to movement type.
will that affect accuracy in reporting if i populate the historical data without Movement type to 0IC_C03.
Can anybody suggests, how to proceed with this.......
Thanks in advance...
Rahul

Rahul
You can ask your client to provide you the data according to movement type. Also you can get movement type mappings from the transaction OMJJ.
If you upload the data without movement type, then you will have problem, while you generate reports which involves historical and operational data.
Hope it helps
Sayed Rafi Basheer

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

Data loading problem with Movement types

Hi Friends,
I extarcted data using the data source General Ledger : Line itemdata (0fi_gl_4) to BW side.
Problem is Movement Types for some documents missing.
But i checked in rsa3 that time showing correctly.
i restricted the data in bw side infopackage level only particular document that time data loading perfecly.
this data source having 53,460 records.among all the records 400 records doc type 'we' movement types are missing.
please give me solution for this how to loading the data with movement types.
i checked particular document of 50000313 in RSA3 it is showing movement types. then i loaded data in bw side that time that movement types are not comming to be side. then i gave the particular doc 50000313 in infopackage level loading the data that time movement types are loading correctly. this extaractor having 55000 records.
this is very urgent problem.Please give me reply urgenty. i am waiting for your's replys.
Thanks & Regards,
Guna.
Edited by: gunasekhar raya on May 8, 2008 9:40 AM

Hi,
we enhanced Mvement type field(MSEG-BWART) General ledger (0FI_GL_4) extractor.
this field populated with data all the ACC. Doc . number.
Only 50000295 to 50000615 in this range we are not getting the movement types values.
we didn't write any routines in transfer and update rules level.
just we mapped to BWART field 0MOVETYPE info object.
we restrict the particular doc no 50000313 infopackage level that time loading the the data into cube with movement types.
but we remove the restriction infopackage level then loading the data that time we missing the movement types data of particular doc no 50000295 to 50000615.
Please give mesolution for this. i need to solve this very urgently.
i am witing for your reply.
Thanks,
Guna.

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

Posting with MM Movement Type 309 material to material: Error in WM

Hello,
i post an MM-Movement type (Bewegungsart) 309 (material to material).
The MM-goods movement works, but then in warehouse mangagement there is a problem:
The creation of the transfer order (Transportauftrag) stops in many cases.
The aim is to post Material A to the same storage bin in Warehouse Management where Material B was before.
I programmed this in user-exit (ZXLToU03) that by movement type 309, always taking same storage bin. But then I often get the error: transfer order could not be created. Then I have to do the creation of tranfer order in foreground and then I get an error like this:
capacity of the bin location is not enough.
The Problem is that I do a posting for example:
001 010101 to 922 Umbuchungzone --> Transfer order Pos 1
922 Umbuchungszone to 001 010101 --> Transfer order Pos 2.
And so the first transfer order position is not confirmed when I do the transfer order Pos 2.
How can I confirm Pos 1 by batch-input? The Programm to do 309 should posting 1000 materials in one step. But in Warehouse management I get those problems?
Is it possible to increase the capacitiy of the storage bin and then decrease it after creation of transfer order(where can I do this and when)???
I hope anybody can help me.
Thanks.

Hello Kevin,
I donu2019t think it is necessary to use a user exit to keep the Material B (that is transferred from Material A) in the same bin.
This can be controlled in the customizing: indicator Post to same bin, that can be set in the WM Movement type (V_T333-KZUAP) and in the Storage type (V_T3010-KZUAP).
Now I donu2019t know your business process but I am surprised that Material B requires more space than Material A since it is u2018bornu2019 by means of a transfer posting and not a production or packing step that makes it bigger in terms of capacity required.
A workaround for this could be to transfer (LT10) Material A first to a separate Storage type (with the Post to same bin-flag set) that has no Capacity check and after the 309 posting transfer it back into the warehouse with LT10.
Success and thanks beforehand for any credits!
Kind regards,
Bart

Restriction to use mov type 309

Hi,
I need to restrict some of users not to use mov type 309 only, other mov type they need to use, in that case how to do ??
I knew the object (object name -authorization object is M_MSEG_BWA) pls tell me the steps?

Dear Jayakumar,
While creating the roles using T Code PFCG,after adding the T code MB1B under any role,ask your Basis consultant to look for
this authorization object M_MSEG_BWA,and dont include the check box for 309 movement and include it for the other
movement's like 311,312 etc.
So whatever role that's allowing MB1B should be checked so that it 's not having the authorization for 309 movement.
Check and revert back.
Regards
Mangalraj.S

Error in Standard SAP movement type 309?

Path: SPRO > Logistic execution > Warehouse Management > Interfaces > Inventory Management > Define
Movement type > Assign WM Movement Type References to IM Movement Types
IM Movement type 309 has as Reference Movement types WM 301, 302 and 309.
IM Movement type 311 has as Reference Movement types WM 311, 312 and 309.
Path: SPRO > Logistic execution > Warehouse Management > Interfaces > Inventory Management > Define
Movement type > LE-WM Interface to Inventory Management
Reference Movement type 301 has WM Movement type 301.
Reference Movement type 302 has WM Movement type 302.
Reference Movement type 309 has WM Movement type 309.
Reference Movement type 311 has WM Movement type 311.
Reference Movement type 312 have WM Movement type 312.
Path: SPRO > Logistic execution > Warehouse Management > Activities > Transfers > Define Movement
types
WM Movement type 301 has Destination Storage type 920.
WM Movement type 302 has Source Storage type 920.
WM Movement type 309 has Source and Destination Storage type 922.
WM Movement type 311 has Destination Storage type 9210.
WM Movement type 312 has Source Storage type 921.
In my opinion this means that if I make an IM movement with movement 309 the material will be picked from a Storage
bin and moved to Storage type 920. After the change the material will be brought back from Storage type 920 to the same Storage bin.
The change will be done with WM Movement type 309 in Storage type 922.
This creates negative stock in both Storage type 920 and 922.
In my opinion this means that if I make an IM movement with movement 311 the material will be picked from a Storage
bin and moved to Storage type 921. After the change the material will be brought back from Storage type 921 to the same Storage bin.
The change will be done with WM Movement type 309 in Storage type 922.
This creates negative stock in both Storage type 920 and 922.
Is this an error in SAP standard? Should I Change the Source and Destination Storage types of Movement types 301,302,311 and 312 to 922?

Hi,
Please check wheather the material type of the material belongs to NLAG/UNBW or any other type which will not have qty/value updations for that plant at Attributes of the material type at SPROlOGISTICS GeneralMaterial mastermaterila types
Or take the question mark which is there on the error screen so that the information will become self explanatory.
Please reply back with your info.

GL account for movement type 309

How to find GL account for movement type 309. Tcode etc
Stop Cross-Posting

Hi,
Try using transaction code OMWB (press cancel on pop-up) >
Press "Simulation" button and enter plant + mat + movement type >
Press "Account assignments" button
Dr/Cr G/L accounts displayed for posting lines.
Kind regards,
Robert

Next Inspection Date in case of Mov. Type: 309

Similar Messages

Maybe you are looking for