on 2019 Nov 14 12:46 PM
Hello,
Today I ran into the interesting fact: into table QPMZ data of one Master Inspection Characteristic can be stored in 2 rows. Duplicating unique keys.
The first row contain data on Inspection Method. The second – on Assigned Code Group or Selected Set.
Such way of MIC data storing is relevant when it’s manually created (tr. QS21).
When the migration instruments* are used, there is the only possibility to load either Inspection Methods OR Catalogs. Otherwise the mistake “Enter a selected set” will appear.
*Migration instruments: Migration Cockpit and LSMW BAPI.
What’s more after first MIC loading (with fields for Catalogs) and second MIC loading (with fields for Inspection Methods) its data will not be distributed across 2 rows, as it happens with manually MIC creation.
Data will be overwritten with the last migration, in case of LSMW BAPI. And simply not transferred to SAP system when Migration Cockpit using.
I would like to know whether it was possible to migrate both Inspection Methods and Catalogs at a time?
Request clarification before answering.
Yes, it is possible with LSMW BAPI Method to upload Insp Method and Catalog for Inspection method together.
By filling
PLANT_QPMK MST_INSP_CHA VMSTR_CHAR VALID_FROM PMETHOD METHOD VMETHOD INSP_METHOD_POSNR CAT_TYPE1 SEL_SET1 PSEL_SET1 IND_SELSET_OR_CODEGRP1You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nice catch. I imagine this is caused by the design of the structure S_QPMZ and the migration tools. Nothing to do with QM really.
It's kind of a bad design to start with. SAP probably should have just created two separate tables, one to link methods and one to link catalogs.
As you pointed out, the construct of having both a method and a catalog assigned is supported if it is done manually.
And to point out, one MIC could have many records in QPMZ since a MIC in one plant can be used by any other plant. In fact, I usually recommend the use of a master QM data plant that is just used to create all the MICS so there are not multiple MIC's across plants. In that case, you would have one MIC in plant 1000 for example, but in QPMZ you would have a method assigned in plant 2000, 2001, 2002.. etc.. same for catalog assignment.
Craig
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Craig S.
So, If I understood correctly, due to the S_QPMZ structure design there isn't possibility to migrate both Inspection Methods and Catalogs at a time?
That's what I believe.
But you'd have to check with SAP to be sure. I'd definitely put in an OSS note for this if I were you and get SAP's opinion. They probably won't consider it a bug (i.e. programmed as designed), but functionally it fails to do what you need it to.
Craig
User | Count |
---|---|
86 | |
8 | |
6 | |
5 | |
5 | |
5 | |
4 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.