4. Material Supply ERP --> MES

Overview

Certain material movements are transferred from the ERP system to the MES. IDocs are created cyclically (e.g. every 5 minutes) and transferred to HYDRA. IDocs are called ZMBEW03.

The MES material type must also be stored in the ERP system and transferred together with the provided data.

If batch movements are transferred including user-specific information, this information must also be transferred to HYDRA.

This leads to the following IDoc specification:

Message type/ file ZMBEW

name:

File extension (for file transfer) DAT

IDoc type (for tRFC communication): ZMBEW03

Segments: Z2MBEW001X000 (goods movements) 1 - n

Z2MBEW002X000 (goods movements continued)1 0 - 1

Z2CNRATT_C000X000 (alphanumeric batch attributes part 1) 0 - 1

Z2CNRATT_C001X000 (alphanumeric batch attributes part 2) 0 - 1

Z2CNRATT_N000X000 (numeric attributes) – (OBSOLETE)2 0 – 1

Z2CNRATT_N001X000 (numeric attributes)3 0 - 1

Z2CNR_USRFLD000X000 (user fields)4 0 - 1

Segments in SAP have to be created according to the pattern Z1<segment name> in order to

generate the above-mentioned segment names in SAP. The version control function of SAP

outbound processing generates segment names in the form Z2<segment name><version>.

Example: segment name Z1MBEW001X is converted to Z2MBEW001X000

This documentation uses the below-mentioned column headings with the meaning described here:

1. The segment is available from MLE option ZMBEW_012 on.

2. We recommend to no longer use this segment for new implementations. Segment Z2CNRATT_N001X000 should be used instead. Segment Z2CNRATT_N000X000 is still available (backwards compatible) but will no longer be maintained. Both segments have different field lengths for their decimal fields.

3 The segment is available from MLE option ZMBEW_014 on.

4 The segment is available from MLE option ZMBEW_010 on.

Goods movements (Z2MBEW001X000)

Material supplies: Goods receipt, reposting to a different material buffer. If a batch is already known in HYDRA, the batch inventory will be updated.

The batch inventory can only be updated if the batch is currently not in use

(not running), i.e. batch status <> "L"

Please note that depending on the material type, individual OP-based user fields (transferred together with the operation from the PPS system) can be transferred to batch-related user fields (so called batch attributes) during the generation of batches in HYDRA. These are then

transferred to the PPS system as ERP batch together with the batch at the goods receipt and will be returned when such an ERP batch is provided the next time.

Information on the fields CHARGE and CHARGE_LONG

The following logic/condition applies for providing the SAP batch:

Checking if the CHARGE (CHAR10) field is assigned a value:

• Yes:

This value is adopted.

• No:

Checking if the CHARGE_LONG (CHAR20) field is completed:

o Yes:

This value is adopted as PPS batch number.

o No:

This value ("nothing") is adopted as PPS batch number.

Goods movements continued (Z2MBEW002X000)5

The batch inventory can only be updated if the batch is currently not in use (not running), i.e.

batch status <> "L"

Alphanumeric batch attributes part 1 (Z2CNRATT_C000X000)

The following segment supports the (first 20) alphanumeric batch attributes for the transfer.

Alphanumeric batch attributes part 2 (Z2CNRATT_C001X000)

The following segment supports the (last 20) alphanumeric batch attributes for the transfer.

Numeric batch attributes (Z2CNRATT_N000X000) – (OBSOLETE)

We recommend to no longer use this segment for new implementations. Segment

Z2CNRATT_N001X000 should be used instead. Segment Z2CNRATT_N000X000 is still available

(backwards compatible) but will no longer be maintained. Both segments have different field

lengths for their decimal fields