Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

Create new Variants via Bapi in Retail

Former Member
0 Kudos

Hello together,

I has a problem in the Retail 4.6.c.

I would like to create new variants for an existing article and


since I must use original IDOC , because of the existing information.

New installation of the article with variants that runs well,

but if I liked to add only variants break off the Bapi with

"E MH 051" "classification could am not accomplished".

First thought I, the error came because of the Function = '005',

i changed it then on ' 004 ' .

The same result Who can help me there please?




Active Contributor
0 Kudos

Hi Thorsten!

In general this is possible (as it is already explicit mentioned in the help). But I don't see, how you can use the original IDOC data for extension of an article. Do you have external number assignment?

Anyway, start with a small test. Enter the header data and in variantskeys only the new variant. The critical part (according to your error) is in CHARACTERISTICVALUE. Was customizing changed in between? Is your new value not allowed in the current class?

Be aware, the field material in the tables has to be sometimes the generic article number (as in header and I think characteristics), and sometimes the new variant (as in e.g. materialdescriptions and other variant specific tables).

Maybe you should go even one step further back: try this online (MM42), maybe really classification is not correct.



0 Kudos

Hallo Christian,

ich hoffe es ist ok für dich, das ich zu Deutsch wechsle, so kann ich besser erklären.

Ich nutze die die AFS-Retail schnittstelle, die mit Artmas-Idocs arbeitet.

D.h. die Variantennummern werden schon im AFS generiert und an Retail via IDOC gesendet.

Das geht immernoch.

Nun kommt aber die Anforderung 2.Wahl-Artikel anzulegen.

Das bietet die Schnittstelle aber nicht, da nur EAN-tragende Artikel gesendet werden.

Die 2. Wahl-Artikel sollen genau dem Artikel der ersten Wahl gleichen, nur haben sie eine intern vergebene EAN und einen anderen Suffix in der Variantennummer.

Beispiel: 50100255


001 erste Wahl


001 2. Wahl

Ich habe also den IDOC noch mal gelesen und habe die relevanten DAten in Tabellen für den BAPi verändert.

Mit der MM42 klappt das ordentlich.