MIC at sample level instead of inspection lot level

[Former Member]

Experts,

I have a custom program that takes sample size as input. Say user enters 2 and executes the program - Now BDC for QA01 is called & 2 samples are created against inspection lot. Additionally popup screen from QA01 is displayed to choose MICs. Users can choose the MICs required. As per my understanding, these MICs are saved against inspection lot in PLMK & QAMV tables.

Scenario: Users would like to choose MICs at sample level. In below image, we can see 2 samples created against inspec. lot via BDC call to QA01.

I am planning to add dynamic columns next to short text column that will display the MICs. User should then be able to check/uncheck MICs for each sample & press save button.

Question: Being an abaper, I would like to understand if this is correct to choose MICs at sample level instead of inspection lot level. If yes, then is there any standard table where i should update MICs against sample number. I can easily create a custom table & update this data. But I would like to know if there are standard tables that hold MIC data against samplenos. If so, I will write code to update them as well.

BR,

Aspire

[Former Member]

Craig,

It takes a big heart to take your precious time & energy to lay everything down in detail for me. Huge thanks to you. For someone getting started on QM functional area, this is tremendous help.

I will work on this valuable reply and will keep you posted with my progress.

BR,

Aspire

[former_member42743]

I can appreciate the issues you have. Honestly.. I can.. Again, avoid it!

I might suggest the following. Add all your necessary MIC's to the plan. Set all of them to be SKIP characteristics all the time except one of them and make that required. Use free inspection points to create your samples as you need them, (or physical samples).

When a new physical sample is created, the one require MIC is a pass/fail "Tests selected". The person creates the sample, goes in to the sample, via the inspection lot results recording, set the "Tests selected" to pass. They then set for processing each MIC they want tested. That makes them required now. QE51n can be set up with a display variant to only show required characteristics for those people doing the testing. They won't even see the other SKIP ones.

OR.. OR.... there is the standard functionality, that you do what I said with the one MIC, "Tests Selected" and then the person goes in and simply adds the additional tests. There is a menu choice for this actually all built in there already. (to be honest I forgot all about that and just remembered!!!). But please.. honestly.. don't go writing code!!!

The screen shot i attached shows an inspection lot where a second sample was created and in addition to the two standard tests, (you'd have just the one in your case), I added the Adsorption Capacity test as an ad hoc test. Note this is only on the second sample, not the first sample. This is all standard SAP. Zero customization. Only some minor configuration to do.

Craig

[former_member42743]

So just to follow up on the above. You create a plan with just one required MIC in it. "Tests Selected" which is a PASS/FAIL MIC.

The user (or event), creates an inspection lot. The go into QA02, and add the number of containers. The plan is set up for physical sample using a sample drawing procedure that specifies number of samples = no. of containers.

The lot is saved and in QE51n you'll see the correct number of samples created all with the one required test of "Tests Selected". The person goes into results recording for the first sample and selects from the menus "Edit-->Create Additional Characteristic". All available MIC's are available to select from. Once added, add in any additional tests. Now record a PASS for "Tests Selected" and lock.

Repeat this for each created sample.

If they wanted too, They could just by default create the first sample only. Then when in QE51n you use the "further inspection" to create and add as many additional samples as you want. Depends on how they want to work.

I think this pretty much gives you the full functionality you've described.

[Former Member]

Hi Craig,

I shared your suggestions to business team step by step. They seem to be familiar with this solution. They are looking for more flexibility where the user executes the custom tcode to create inspection lot & samples against it in mass using our custom BDC program so that they can comfortably choose all the MICS applicable for a sample upfront from a single screen.

Say they decide sample size is 20. Now custom program will create an inspection lot with 20 samples in it. In the final screen, an ALV report is displayed listing 20 samples & inspection lot number. At this point, they want to quickly pick and choose the MICs applicable for each sample. Say 5 MICs are applicable for sample1, 2 for sample2, 4 for sample3 etc... by checking/unchecking checkboxes. Screen should look as below,

Technically this is doable. But as you rightly mentioned this involves lot of programming. We finally agreed to develop this on an ongoing basis as & when i find time and not as part of current deliverables. This is part of the wishlist for users.

I am really thankful to you for sharing the solution in detail with screenshots.

BR,

Aspire

[former_member42743]

Well. the important thing is that you offer them the available choices. If they still feel they want to pay the price for this that is there choice.

I think they'll pay the piper someday down the road for it.

Craig

[Former Member]

Hi Craig,

Thanks a bunch for your detailed reply. I shared your reply with Business team & was informed that we are not taking advantage of full blown capabilities of QM or using it the way it should be used.

We manufacture products for which our company performs trails before product is manufactured in our plant to test for Nitrogen content levels, PH levels etc... Samples are assigned to inspection lot. MICs are the characteristics in samples for which test is performed. Let us say they create an inspection lot. In this lot, they assign samples & for each sample they want to assign MICs. Say in sample 1 they want to test for Nitrogen levels. In sample 2 they want to test for PH levels. Current process does not allow them to assign MIC at sample level. They have to assign MICs Nitrogen & PH level to inspection lot. Then they have to go to QE51N tcode to manually close MIC PH level which is not applicable for sample and close Nitrogen level which is not applicable to sample 2.

So the ask is to assign MICs at sample level. Users mentioned that they can close the MICs from QE51N against sample. This is where I would like to know the standard table where MICs are stored against sample. I have to update this standard table so that users can access this info from QE51N tcode. If i updated the MICs against sample only in my custom table, users will not be able to access this info from QE51N Tcode.

BR,

Aspire

[Martin_H]

Hey Aspire,

as fire.fighter already mentioned you normally two choices when using SAP:

1. Adapting to the concepts SAP has implemented in their software (e.g. sampling schemes, inspection plans, MICs assignment, ...) and then slightly customizing that to fit your needs
2. Keeping your working mode and programming masses of code to built a way around the SAP concepts

You are trying to go with option 2. Based on my experience I would advise you not to do so.

MH

[Former Member]

Hi Martin,

Thanks a lot for your valuable directions. I am new to QM functional & have ABAP background. Currently I am connecting with business users directly to understand the requirements. Without much window to learn QM and then implement solutions, i see that i am opting for the known route of writing code to achieve everything. Thanks for this great help in making sure i am not heading in the complex direction.

BR,

Aspire

[former_member42743]

Ok.. you've left your user's go too far afield here IMHO.

Picking MIC's to test is usually, in general, a bad quality practice. It's also inefficient and a waste of time.

It's rare that a standard testing regiment can't be figured out. It usually indicates a lack of resource being applied to planning.

For one, most MIC's can be assigned to test plans and set up as optional testing anyway. Then the user can make this required if they want to be recording anything in the description. So why give them a pop-up to pick from? Surely products have a limited subset of mics they can actually test for.

Partial samples and physical samples are standard functionality that can apply specific samples to specific MICS. I.e. in your inspection plan you can indicate which tests share which physical samples. So for instance, all GC results share partial sample 001 that goes to the GC lab. All wet chemistry test are assigned to partial sample 002 which goes to the wet chem lab, (ph, viscosity, water, etc.) , Partial sample 003 might be for an fast IR scan. Sample 004 might assigned to the micro tests and be sent to a microbiology lab.

It actually sounds like you are building a lot of stuff that isn't even needed to start with. All that can be done by standard out-of-the box SAP.

Craig