Next Inspection date in batch master

[Former Member]

Dear all,

I want that if UD is OK i.e. in qa32 in UD accepted then this date should be taken or picked up in batch master.Is this possible in recurring inspection.

Thanks All in advance.

Manisha

[Former Member · Accepted solution]

HI

If the interval for the recurring inspection has been defined in the material master record, the date of the next recurring inspection is entered automatically when creating a batch.

then if you when you run the dead line monitoring for the batch, sytem will check the recuring inspection date, if the date is as on the same day, then system transfers the batch stock to the quality with inspection type 09.

-ashok

[Former Member · Accepted solution]

Hi Ashok,

You are 100% correct. If the "Inspection interval" is defined in the QM view of Material Master, The system will calculate the next inspection date, and feed it automatically in the relevant field in the Batch. But this calculation will be done from the Date of GR.

E.g. Gr Date 31.07.2008 and the inspection interval maintained as 10Days it will give the Next Inspection Date value in the Batch as 10.08.2008.

But What ms. Manisha is asking for is the date should be calculated from the UD. It means GR Date 31.07.2008, UD done on 05.08.2008 now the Next Inspection date will be 15.08.2008

.

Dear Manisha,,, Kindly Correct me if I am wrong

So to incorporate this scenario, what to be done is....

Create A function module as per the requirement,

assign the FM to the Follow-up action,

Now create a UD Code, where we need to attach this follow-up action.

It will required even though we activate or do not activate the inspection type 09.

Regards,

Shyamal

[Former Member · Accepted solution]

HI

yes , if that is teh case , then the issue has to be work out with Function module,

-ashok

[Former Member · Accepted solution]

Hi All,

Dear Shyamal the way u have explained is exactly my requirement ,already recurring inspection settings are made but the date has to be catched with the UD date.U have almost resolved my problem,thanks a lot.Also can u pls tell me how this QA05 is used alongwith this recurring inspection because im working on offshore support for this client.

Thanks a lot.

Manisha

[Former Member · Accepted solution]

Hi Manisha,

=> Run Trx QA05, Click on Create vriant.

=> Name the Variant, Click on the CREATE

=> Select Full Screen,

=> Now system will lead you to the same screen as QA07. Here Assign the values as per your requirement.

E.g. If you are planning a job for a specific plant then enter the plant.

=> In your case you need to enter the plant( If applicable), INITIAL RUN IN DAYS (e.g. 10 as meeting your requirement), and select the "To Inspection Stock at Lot Creation"

By selecting this radio button.... If you choose this option, batches whose next inspection date lies within the opening period, are posted from the unrestricted-use stock to the inspection stock. At this transfer posting, a new inspection lot is created for each storage location. If a corresponding inspection lot already exists and if the next inspection date is reached, the transfer posting is also carried out and the existing inspection lot is changed accordingly.

=> In the lower portion, the details for "Batch Status Changed When Expiration Date Is Reached" is there, It will refer the Shelf life expiration date in the Batch itself and Post the batch to block stock if the check box here "Block Batch" is ticked.

=> For the Both the functions it will take a Initial run in days in count to pick the batches. E.g. if you enter 10 as run in days, so where ever the program "RQAAAS10" will run, it will post those batches in Quality for which the the next inspection date falls in the orbit of next 10 days. Similarly block the batches for which the Shelf Life Expiration date falls under orbit of next 10days.

=> Now go back and select option yes to the message populate having text as "Leave value maintenance: Save values?"

=> Then name your variant logically, set the appropriate values for variant, if required.

=> Save.

Hope that clears your the QA05 variant creation if not revert with the step where you stuck up, and if yes then revert with cheers.

Else what you can do is post a separate thread. That will encourage others also to reply.

Regards,

Shyamal

[former_member42744 · Accepted solution]

Next inspection date is always calculated from the UD date when doing recurring inspections. It's the way SAP designed it.

The first time the inspection date is set it uses the current date of the goods receipt + inspection interval.

From reading your positngs, I think that is exactly what you want the system to do. Ther should be no need for any function modules.

Now if you want the first inspection date to be calculated from the UD of the "04" inspection lot and not the GR date, (or to be more accurate, the first GR of the batch), then you need to do something different and you'll probably want to use a follow-up action for that.

Craig

[Former Member · Accepted solution]

Yes Sir,

Correctly said, for the first next inspection date for the batch = Gr Date + Inspection Interval.

But as you know in some parenteral pharmaceutics where the GR processing time (Inspection lot creation to release time i.e. the actual duration for what the lot will be under inspection because of some microbiological tests like Sterility, BET etc.) hikes up to 20-26 days. In this kind of cases we need to count the Next Inspection date Based on the UD date, initially also.

And you have also suggested correctly to use the Follow-up action.

The same I have also suggested, but I was also in the same kind of issue to a my first implementation project, and we couldn't find any ready made follow-up action, that counts Next inspection date from UD date, so we developed own FM and assign it to follow-up action and resolve it.

I just shared one of the way but the ready made FM will be the great help and obviously a better option.

Reagrds,

Shyamal

[former_member42744 · Accepted solution]

I guess it would depend on the auditor. I would say the first GR date is the better date to calculate the initial inspection date from. The material starts to degrade as soon as its made.

If you wait till bug testing is done, you could be adding an extra month to the inspection interval which I would have a hard time supporting.

Ideally, in pharma, you would use sample drawing procedures and calculate the inspection date from the date the samples are drawn.

Craig

[Former Member · Accepted solution]

Hello,

Thanks to all of you first.

This is raw material,when the material comes in the GR is done by the client,but this same GR is released only after the UD id accepted hence they require the NID to be calculated from UD date.

Hence how can this be done.

Because When GR is done the calculation of NID is perfect in batch,but when the UD id done for the same batch the system should automatically now calculate the NID from this date,Is this possible.

I have done the same settings as in client server in a demo srvr and it is working fine that is the system calculates the date from the UD date and changes the earlier NID calculated from GR date.

But when I try to do the same in the development server of the client.After UD is accepted the system does immediately ask for the NID in batch(it shows 00.00.0000 and gives message invalid date).But client does not want to put this date manually.They are also running the program QA05.Is it because of this that the system is not calculating the date.

Iam not much aware of Tcode and never used it earlier.

Pls help if you can

Thanks a lot once again

Manisha

[former_member42744 · Accepted solution]

My guess is that in the development box the next inspection date was not initially populated for an exisitng batch your working with.

I am always suspect of data in development boxes since shortcuts are often taken to create data or we try to reuse data not explicitly set up for what we are testing.

All i can suggest is that you check everything from start to finish. First check the material and make sure the settings are correct. Then issue a PO, then do the GR. Then check the batch to see if a next inspection date was calculated. Then this batch can be used for testing.

To get the inspection date to reflect the UD you will have to create a function module and use it in a follow-up action to all applicable UD codes. The FM should recalculate the inspection interval using the current date plus the inspection interval value from the material master. The FM updates the batch record.

Craig

[Former Member]

hi

When you complete the inspection with the usage decision for an inspection lot, the system updates the next inspection date in the batch master record. The system determines the new inspection date by adding the value of the inspection interval specified in the material master record to the current date.

-ashok

[Former Member]

Why are you not using recurring inspection with insp 09.

With 09, you can do what is required for you.

[Former Member]

Hi Manisha,

What I could understand from your post is,,,

You need to calculate the Next inspection date from the UD date automatically, M I correct?

If yes then you just need to define a new Follow-up action for the UD Code, assign it with the UD Code in QS51.

Regards,

Shyamal

[Former Member]

Hi

You are correct but i need to calculate the date the date only if the UD code is accepted i.e. the material batch is accepted and not otherwise is this possible with this and if yes how to do the same.

Thanks a lot

manisha

[Former Member]

Yes Mam,

It's possible,

In QS51, you will see the follow-up action get assigned to each UD Code.

E.g.

UD Code A=Accepted , assign the follow-up action here.

UD Code R=Rejected , Dont assign the follow-up action to here.

Regards,

Shyamal

[Former Member]

hi,

Thanks a lot again,i got it ,but i do not know how to select/create that functional module "for transferring the date from UD date to the next inspection date in batch master.

Thnks and regards,

manisha

[Former Member]

HI Manisha,

Normally the ABAPers creates the Functional Modules for the same. SO I will suggest to sit with your Developer & get it resolved.

update us to help you more, reward points to help you better!

Regards,

Shyamal