MH086 - The matrix for defining variants could not be called up

[Former Member]

Dear community,

we have the following problem in our SAP ECC 6.0 system: We have a generic article and if the user klicks on the "Variant" button the message MH086 - "The matrix for defining variants could not be called up" appears. The material characteristic classification in table AUSP looks damaged - the variant-creating characteristic CIBD_RV01_GARNE_MARKEN seems to be missing for the variant articles. It looks similar to note 360484, but this note is not installable for our release.

We also often have the problem of double entries in AUSP for single-value characteristics (note 392300) for articles with the CIBD_RV01_OVERSTOCK characteristic. Maybe there is any relationship, as you see in the second screenshot this characteristic has counter number 1 in the generic article, but 2 in the variants.

Do you have any solution to this issue? We are looking forward to your replies. Thank you in advance.

[Former Member]

We were able to fix the issue with note 1692447, after we received pilot access.

[Former Member]

Just for your information, we just added the missing AUSP values manually via SE16N in our QA system and the variant matrix now appears correctly. Can we transport the changes without any further problems? Is it bad if the status C is missing in MARA-VPSTA and MARA-PSTAT, but existing in MSTA for the corresponding articles?

[Ritz]

its seems there is inconsitance in data and it will be difficulty to find root cause of this inconsistant data,.

But my suggestion would be to analyze it throughly instead of making or changing table entries.

you can try below reports to check and correct data.

Report to correct error V1854:

RCU_CHECK_CONFIGURATION

SAP note: 900047 Message V1 854: Lost configuration

Reports for the analysis and correction of the data storage for configurations and object structures:

RIBCHECKIBIN

RIBCHECKIBST

Report to clean up unwanted objects for which there are no observers:

RCU_CLEANUP_IBINOBS

Report to correct error UIB1699 or CX699:

RCUIB_CORRECT_OWNER

Thanks

Ritesh

[Former Member]

Thank you, Ritesh,

most of the reports you mentioned were not really helpful for us and did not deliver any results. We don't use variant configuration, however. We are a mail order company and sell clothes and yarns in different sizes and colors, respectively, but the customer immediately orders the variant and not a configurable material.

The report RCU_CLEANUP_IBINOBS found most of our purchase requisitions, but I don't understand what to do with its output ... The tables IBIB, IBST and IBIN are empty, but IBINOBS contains 3092 instances with 1625358 different Objkeys. The other report, RCU_CHECK_CONFIGURATION, is still running.

Are there any further consistency checks?

[Ritz]

Marius Spix,

Sorry I didnt realize you are not using VC, just the material classification using class 001.

Still my suggestion is not to make direct table entries insted try to investigate why values are missing and correct the process.

Thanks

Ritesh

[Former Member]

Ritesh Dube,

I already undid the table changes to the state before.

The job RCU_CHECK_CONFIGURATION aborted after 4:15 h with an DBIF_RSQL_SQL_ERROR while reading VBAP via "SELECT * FROM VBAP INTO TABLE L_T_VBAP WHERE CUOBJ NE 0." in FORM CHECK_VBAP_CUOBJ_EXITS.

We now tried the Report Z_CHECK_VARIANTS from Note 360484 and have the following output:

Error: variant 000000000100110432 with characteristic

CIBD_RV01_GARNE_MARKEN

Error: variant 000000000100110433 with characteristic

CIBD_RV01_GARNE_MARKEN

Error: variant 000000000100110434 with characteristic

CIBD_RV01_GARNE_MARKEN

Error: variant 000000000100110435 with characteristic

CIBD_RV01_GARNE_MARKEN

Error: variant 000000000100110436 with characteristic

CIBD_RV01_GARNE_MARKEN

Error: variant 000000000200201242 with characteristic

CIBD_RV01_WEIN

Is there any possibility to repair the erroneous variants?