5. Material Consumptions MES --> ERP

Overview

The withdrawals recorded in the MES including the return transfers are transmitted to the ERP system

In the ERP system the withdrawal postings are deducted from the warehouse and added to the individual production order. If withdrawals for an ERP batch cannot be executed in the production warehouse specified by MES (missing inventory), it will be deducted from that warehouse where the ERP batch is found. Only if this is also not successful, the system will issue an error message. This approach (searching for an ERP batch) should also be used for return transfers in ERP.

This data is read from the MES table EVENT_MLB.

MES provides this data cyclically to the ERP system. The IDoc is of the type ZWAU01. This leads to the following IDoc specification:

Message type ZWAU

File name (for file transfers) Z2WAU000X000

File extension (for file transfers)

Depending on the configuration (by default .dat“)

IDOC type (with tRFC communication):

ZWAU02

Segments: Z2WAU000X000 (goods issues)

The following documentation of the structures uses the following column headings with the meaning described here:

Movement types

In general, the following movement types are supported:

Data structure (Z2WAU000X000)

Information on the fields CHARGENNUMMER / CHARGENNUMMER_LONG

The field CHARGENNUMMER_LONG is only available as of MPL 8.2.

If MPL 8.2 is used the fields CHARGENNUMMER and CHARGENNUMMER_LONG will be completed as follows:

CHARGENNUMMER includes the ERP batch number including the characters 1-10.

CHARGENNUMMER_LONG includes the ERP batch number including the characters 1-20.

It is recommended to use the value of the CHARGE_LONG field for new implementations