Skip to Content
avatar image
Former Member

Can create material using MM01, but not using IDOC message type MATMAS with same fields.

Jul 18, 2017 at 12:31 PM | 201 Views | Last edit Jul 18, 2017 at 12:41 PM 3 rev.

Hello Experts,

I Created a material - Test_01 using transaction code MM01 with below details.

Material number : Test_01

Industry Sector : Mechanical Engineering (M)

Material Type: Semi finished Products (HALB)

View - Basic Data 1

Description : Test material

Base unit of Measure : PC

Trying to create a material - Test_02 using the IDOC message - MATMAS

IDOC type - MATMAS05

Process code - MATM

Inbound FM - IDOC_INPUT_MATMAS01

Segment: E1MARAM

MSGFN : 009

MATNR : Test_02

MTART : HALB

MBRSH : M

MATKL : D14110101

MEINS : ST

GEWEI : KGM

Segment : E1MAKTM

Function : 009

CHAR1 : E

Description : Test_02 Test Material

IDOC Created with status message - 51 (Error status)

Below are the error I got in MM90

  • Specify a unit of measure
  • The material Test_02 does not exist or is not activated
  • Field WERKS has been transferred inconsistently or is blank
  • WERKS for MARC is ""; previously ""
  • Field WERKS has been transferred inconsistently or is blank
  • WERKS for MARC is ""; previously ""
  • Field LGNUM has been transferred inconsistently or is blank
  • LGNUM for MLGN is ""; previously ""
  • Field LGNUM has been transferred inconsistently or is blank
  • LGNUM for MLGN is ""; previously ""
  • Field VKORG has been transferred inconsistently or is blank
  • VKORG for MVKE is ""; previously ""
  • Field VKORG has been transferred inconsistently or is blank
  • VKORG for MVKE is ""; previously ""

Even If I provide all these values to resolve the error, still I am getting couple of errors -

  • Configurable material for client-specific configuration missing
  • Operation not possible (e.g. incorrect material type or plant)

Why MATMAS IDOC is demanding more information for creating a material of same kind as I could create using MM01?

Please help me to create a material using MATMAS and with required information only.

Thanks,

Hemant Gandhe

NW ABAP Integration Technology (ALE)
ABAP Testing and Analysis | NW ABAP Communication Services | ABAP Development
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Jürgen Lins
    Jul 18, 2017 at 10:51 PM

    somehow I can't believe that you are really doing the same getting this huge pail of errors .

    There are various reasons why an online transaction with direct communication paths to a user works different to a batch process via IDocs.

    The easiest to find out what is needed and how an Idoc looks like is to send the material with BD10 and then check the Idoc in BD87

    I can already tell you that the Idoc for your Test_01 material would have the segments E1MARAM, E1MAKTM and E1MARMM

    and hence your provided fields that you used for your TEST_02 with its values are not sufficient yet.

    Looking at these endless list of errors makes me think that you created an Idoc with a lot more segments than you mentioned and that you missed to maintain any values in those segments. How else should SAP come along with messages about MARC, MLGN and MVKE?

    And because of that your TEST_02 with the IDoc is much different than just creating the basic data view from your TEST_01

    Add comment
    10|10000 characters needed characters exceeded