About nitin_jinagal

nitin_jinagal · 02-03-2020

Hi, I have configured new condition tables and replaced the older ones from an exisiting sequence. This access sequence is later used in output condition types to generate COA in an outbound delivery. Output condition records are also maintained. ...

nitin_jinagal · 10-10-2019

Hi All, In the inspection plan, there are several MICs which are linked to batch characteristics and different specification is maintained for each MIC in different plan. E.g MIC1 can have spec limit of 3-5 in Plan1, could be 7-9 in Plan2 and 15-1...

nitin_jinagal · 06-13-2017

Hi folks, Im stuck with a scenario and not finding a way to map this. I hope I get an advice here. This scenario is related to inspection of incoming goods (Type 01). My client follows AQL to carry out sampling and inspection of raw materials. They h...

nitin_jinagal · 03-14-2015

Inspection point is a wonderful tool which can be used to carry out inspection on the basis of several factors i.e Time frame, Quantity based, Sample Management, Calibration, or any other factor called as a POINT. In simple words, Inspection points c...

nitin_jinagal · 01-30-2015

Hi Everyone,I'm thinking of having a discussion after witnessing few activities today on SCN. Some deleted contents, Locked threads, Continuous cross posting, New blog on user behavior etc.So How about having a space or something where all the locked...

nitin_jinagal · 02-05-2020

Yes I did it today. Did not have the access before. Also got to know that in the configuration, it can be run by clicking on 'Utilities' for an access sequence and this will remove the inconsistency. Thank you very much for the support.

nitin_jinagal · 02-04-2020

Yes, thats correct. So what is the confusion here ?

nitin_jinagal · 02-04-2020

Please look into batch derivation. Your ingot should be the sender material and Angle would be reciever. You define the parameters for which results must be copied along with defing the rule. Thanks,Nitin

nitin_jinagal · 02-04-2020

Yes old record is not the issue here because there are several documents created which could have been impacted and thats why old records were left untouched. Problem is with display only which occurs in VV23 as explained.

nitin_jinagal · 02-04-2020

Hi Craig, Thank you for taking up my question. So its not about the deliveries. Problem is with the condition records display. I'll explain it. E.g. Old sequence had two combinations, 1. Storage location/Material2. Storage locationNew sequence has, 1...

User Statistics

User Activity

New Access sequence is missing in 'Condition info' in VV23

Different specification for same MIC linked to Class characterisitic

Calculation of 'Units to be inspected' and sample size of inspection lot

Inspection Points: Key settings and Usage

Locked thread space :-|

Re: New Access sequence is missing in 'Condition info' in VV23

Re: Inspection Points: Key settings and Usage

Re: Copying of Inspection result from RM to FG (Batch to Batch) automatically

Re: New Access sequence is missing in 'Condition info' in VV23

Re: New Access sequence is missing in 'Condition info' in VV23