COA Inspection specifications at distribution center

[MIGO101]

Dear forum members,
In certificate profile, I am using 'Insp specifications from QM'. That means system gets the specifications from most recent inspection lot of batch in the delivering plant of the delivery.
It is working good if my delivering plant is factory (where I've insp lots for batch), but if my delivering plant is a DC, then system is not able to find inspection lot.
Is there any modification / exit where I can tell to system to look for the insp lots in factory ?
There is 'EXIT_RQCAAP00_002' that is called in SAP cert program RQCAAP00 -> Include AAP00F03, but this exit is just to evaluate the inspection lots that are selected by standard program, but not to determine the inspection lot.
So please give me some ideas on how to solve my requirement.

Thank you,

[Craig]

I had this problem at a client.

If I remember correctly we addressed this by creating a new FM for the inspection specs origin. It was a copy of the one provided by SAP except it looked at the other plants I believe.

Craig

[MIGO101]

Thanks Craig, I thought about that option.
But I was checking if there is any other easy solution, because inspection lot is selected first by RQCAAP0* program and then passes it to 'QC02_INSPECTION_CHAR_SPECS' (if I use 'Insp spec from QM', in cert profile).
Any way, I too think there is no other solution except writing a copy of above func module and in that I need to specify
IF I_QALS-PRUEFLOS IS INITIAL, then change WERKS = factory plant and perform 'Lot selection' (of include AAP00F03 in cert program) and 'QC02_INSPECTION_CHAR_SPECS' again.

[Craig]

I know we did it without changing the COA program or any of the includes.

You really don't want to change the COA program. Please avoid that!

Now if you already did that then I guess you can. But you really don't want to.

I can't remember but I believe we did find a way to use an exit or enhancement.

Craig

[Donk]

Hi,

If it's batch managed materials, you should be able to use the standard certificate function QC02_CHAR_MVALUE_BEFORE in combination with the profile settings (correct explosion level, materials, etc) to grab the results from the batch where used list...

Regards,
John

[MIGO101]

Craig, thanks for your replies. I am not intending to change the std cert program nor developing a copy of it. I will use the standard RQCVAA* programs
John, thanks for your reply. Your suggestion works, but I am not going to follow your suggestions because I am planning to create a very limited amount of cert.profiles (may be 5 or 6) and going to assign them to several thousands of materials / customer-material combinations. If I follow your suggestion, I would have to ask the user to list all thousands of FERTs in the cert.profile's material list and it is a very tiny screen. I am sure the user doesn't like it.

So what I am going for is, I am going to develop a new insp spec origin without the control 'read insp lots'. Then the main program skips reading the inspection lots in delivering plant and directly jumps to the Z func module (that is assigned in this origin). In this Z func module I will read the inspection lots info of my desired plant (in my case it is factory).

[Craig]

Good luck!

Let us know how it works out for you! I'm looking forward to hearing about it. (yes.. my life is that boring sometimes!!)

Craig

[Donk]

Hi,

I would have to ask the user to list all thousands of FERTs in the cert.profile's material list and it is a very tiny screen. I am sure the user doesn't like it.

Yep, this would not be a good route to go then, but the small screen size would be the least of your worries... it would probably take hours to create a certificate while it cycles through all those materials & batches looking for certificate results!

John

[MIGO101]

To Craig,
As you requested, I am sharing how I solved this.
At my client they test only HALB batches and simply fill various FERTs with a HALB batch. Then distribute these FERTs through different DCs. Given this background, I've done the below set-up
1. During the HALB GR Insp lot UD, with a follow-up func module I am passing the Insp lot no. into it's batch classification
2. During the FERT GR from it's Prod order, I am using batch derivation to pull info from HALB batch to FERT batch
3. Incase if the FERT batch is tested again for extension fof Shelf life, the corresponding insp lot no. of FERT batch will overwrite the existing insp lot no. in batch classification.
4. I created a new Insp spec origin in cert profile that will look at the insp lot no. in batch classification of FERT batch and get the specifications.

[Craig]

Very cool idea! I like it!

I really appreciate you sharing the information!

The only downside I see is creating the sending/receiving records for batch derivation. But I suspect you were already doing that to derive the batch values anyway.

That might be a great suggestion at ASUG for SAP. Maybe suggest they create a standard batch characteristic such as LOBM_INSP_LOT which would contain the inspection lot number that provided the last UD code for the LOBM_UDCODE characteristic. That would at least save you from doing the follow-up action. And it might be nice thing to have for documentation purposes.

Craig

[MIGO101]

Yes I've set-up batch derivation (pull process) to send values from HALB to FERT batches in factory plant at the time of FERT GR from production order. I've created a simple access sequence with material type/plant combination in both sender and recevier condition records.
Unfortunately my client has activated batch level at Material-plant level. So if the FERT is transferred to DC from factory, then I am using the extended classification option of 101 / 305 movement types that triggeres a user exit to copy batch char values form source to receving plant during GR of STO delivery.

I am still struggling with how to send the updated/new batch char values to all DC plants (whereever the batch is present) when a FERT batch is tested at factory for SLED extensions. I thought I could use push derivation during UD, but for some reason it doesn't seem to work as I expected

[Craig]

Yes, if you routinely transfer materials between sites, you should typically be at the batch/material lever.

You'd have to probaly look at user exits for the various GR's that you mober the material around for.

Craig