6. Order Data ERP --> HYDRA

Data transfer process

The data provision from the ERP system is realized in a file that must be made available in a defined directory on the HYDRA server. The transfer of the data from the ERP system to HYDRA can be summarized in a file to create/ change or to delete the data. The segment name of a data record (one line in a file) shows to HYDRA whether the data record concerned is to be inserted/ updated (suffix "_A" to segment name) or whether it must be deleted (suffix "_D" at the segment name).

HYDRA will process the contents of the file in sequences from the top to the bottom. The higher a data record is positioned, the earlier it will be processed in HYDRA. This ensures that the file can be created in the chronological correct order in PPS/ ERP.

The HYDRA 7 variant ("compatibility mode") of transferring the data to be created/changed and the data to be deleted separately by different file extensions is still supported by HYDRA 8 but no longer developed.

Creating/modifying data

At the interface for the transfer of production orders all data, which are relevant for HYDRA will entirely be bundled in an IDOC and transferred by the messaging function (= file extension) "DAT" to HYDRA.

When the order data are transferred from the ERP system to HYDRA this initial data transfer to HYDRA must be made in a specific order. This means that the order data presented in the following chapters must be transferred to HYDRA in the specified order/ hierarchy. Within a transfer level the order can be selected freely, e.g. operation 0200 could be transferred before operation 0100.

Modifications to operations with the status "Running", "Finished" or "Deleted" are not allowed in HYDRA by default.

HYDRA expects always a comprehensive data structure. This means that unused data fields must be occupied by such default values that comply with the applicable convention.

If for a terminated operation a change is transferred from the ERP system to HYDRA, this operation will be reset to "interrupted" to the extent that it is still located in the online data area.

Deletion of data

If complete orders are deleted in the PPS system, an IDOC will be created and transferred together with the message function (= file extension) "DAT" to HYDRA. The deletion data must be transferred in the following order:

· Long texts on the operation

· Documents

· Production resources and tools

· Components

· Operation

When the last operation of an order is deleted via the interface , the order header will also automatically be deleted1.

For deletion, it is sufficient to just indicate the respective key fields in the segment.

Operations assigned to the operation statuses "Running", "Interrupted", "Finished" or "Deleted", cannot be deleted.

Similarly, it is no longer possible to delete operations that are split or that are included in a merged operation.

Data record definition

The order-related data are transferred per production order in a multi-level IDOC with the following structure:

The structures that belong to the individual segments are presented in the following. The individual columns have the following meaning:

Segments when data are created/ modified

This leads for the IDOC to the following specifications:

Message type/ file name:

HY72PPS

Message function/DAT

file extension:

Segments: HY72_AU_HD_001_A (order header)

├ HY72_AU_INFO_AI_001_A (long texts)

├ HY72_AU_USRFLD_001_A (user fields)

└ HY72_AG_HD_001_A (operation data)

HY72_AG_KOMPL_001_A (component list)

HY72_AG_FHM_001_A (PRT/ resources)

├ HY72_AG_DOC_001_A (documents)

├ HY72_AG_INFO_AI_001_A (long texts)

├ HY72_AG_USRFLD_001_A (user fields)

└ HY72_AG_RF_001_A (MPL-RF-specific data)

Segments when data are deleted

This leads for the IDOC to the following specifications:

Message type/ file name:

HY72PPS

Message functions/DAT

file extensions:

Segments: HY72_AU_HD_001_D (order header)

├ HY72_AU_INFO_AI_001_D (long texts)

└ HY72_AG_HD_001_D (operation data)

├ HY72_AG_KOMPL_001_D (component list)

├ HY72_AG_FHM_001_D (PRT / resources)

├ HY72_AG_DOC_001_D (documents)

├ HY72_AG_INFO_AI_001_D (long texts)

Order header

The order header includes the header data for the production order.

In HYDRA the order type controls the global behavior of an order. The order type transferred here must exist in HYDRA and be entirely configured.

Long texts of the order header

The following structure can be used to transfer text fields as additional information on the order (header) to HYDRA that will be shown in MOC. Each data record contains one page of a maximum of 10 lines and 80 characters of text information each.

The long text of the order header is shown in the MOC application "edit orders".

User fields of the order header

User fields offer the possibility to store further customer-specific information to HYDRA besides the fields that are available by default in HYDRA. This segment is used to transfer these data from the PPS system to HYDRA and to store them at the order (header).

The so called user field key determines which user fields are involved and which meaning they have. Every user field key describes a combination of user fields. The customer-specific configuration of the user field key is made while customizing HYDRA

For a data exchange of user fields between the PPS system and HYDRA the customer must ensure that the user

field keys are similarly maintained in both systems to allow for a consistent data exchange between both systems.

Please note

This data structure is only available in connection with the corresponding license.

Order sequences

This segment is only to be used to transfer data if sequences are in use. The definition is made as part of the customer project.