cancel
Showing results for 
Search instead for 
Did you mean: 

Source inspection: get variant configuration values as specifications

Former Member
0 Kudos

Experts,

We are using variant configuration and source inspection for our purchasing flow. In fact we create 2 different inspection lots in the purchase flow:

inspection lot created at goods receipt --> the values of the variant configuration are copied in the inspection lot as specification

inspection lot created after PO creation (source inspection, transaction QI07) --> issue: the VC values are not copied

Both inspection types are setup in the same way ("inspection by configuration" flagged and inspection origin is "01" --> goods receipt).

Is this a restriction of SAP that the copy from VC to inspection lot only happens in the goods receipt program? Or did we do something wrong in the setup?

Thanks for the input,

Jan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I think this is defualt SAP

same can be observed with stock posting screen

Sujit

Former Member
0 Kudos

We checked the program of QI07 and indeed, this is not possible in standard SAP.

It will only copy the VC values to the inspection lot at the moment of goods receipt (for inspectiion lots created at that moment).

Former Member
0 Kudos

HI,

to copy VC into specification not in std. SAP apply enhancement QMCF0001 (include ZXMCU01) pl create a Z table for VC MIIN and MAX values and store into it and same will gte overright in your specfication during RR. pl provide further status.

Cheers,

Former Member
0 Kudos

Rahul,

Thanks for your input.

What you say is to implement SAP note 119708. We did this before, indeed to get a min and max characteristic as a range in 1 MIC in the inspection lot. This because ranges can not be used when you use dependencies in VC.

But this is not solving the problem I described above. It is not possible in standard SAP to get the VC values in the inspection lot when you create it independent from a GR. In the code of the program of transaction QI07 this is not foreseen. The field CUOBJ is not filled.

Answers (0)