8. Time Tickets HYDRA --> ERP

Summary

The operation-based confirmations/uploads collected in HYDRA are made available to the ERP system in an individual IDOC with different interface record types (field SATZART in the interface record). To this end, two interface record types are differentiated:

· Operation-based confirmations/uploads (RECORD TYPE = “A“) This interface record type "A" is used to upload all operation-based data records. HYDRA is used to manage those data records with their own collection record type (as shown for example in the

HYDRA maintenance of postings). Based on these indicators, the records identified by the interface record type "A" can be differentiated in greater detail. The following input record types are uploaded:

· Interruption of an operation (posting of the input record type "U" (field KENN in the interface record); processed also at a shift's end if the shift automatic is activated)

· Termination of an operation (postings of the input record type "E" (field KENN in the interface record).

For operations with batch management requirement a data record per order-related posting (interruption, termination) will be transferred, which is not completed with quantities, processing time and RPA. These data records are only used to transfer the labor utilization to this order. When this is terminated, the data record will be used to indicate the end of an order.

The confirmation of the quantities and durations is made in individual records that are generated in HYDRA at the time of the output batch change.Personal confirmation (RECORD TYPE= "P")

If there is a corresponding customizing in HYDRA, the records managed as B-records in HYDRA of the individual persons can also be confirmed. This is then done via the interface record type "P".

The data will then be provided cyclically (by default every 60 minutes) in the HYDRA sub-directory ./inf_int/interf (default version). This directory can be found in the HYDRA directory and/or in case of multi-system environments in the client directory.

On the PPS-side, the OP-relevant data such as quantities or durations will be posted. Incorrect postings will separately be administered and processed in the PPS system.

For the IDOC this leads to the following specifications:

Message type: HY72ADRCK_TT

IDOC type: HY72ADRCK_TT

File name: HY72ADRCK_TIMETICKET

File extension: According to the configuration in the MLE communication (Logical systems > Outbound Configuration Fileport) Normally: .dat

The upload of quantities via partial confirmations/uploads (depending on corresponding customizing through MPDV) with parallel entry of the total quantity counter to MDE machines may effect that the termination of an operation leads to negative quantity postings in yield. To the extent that the PPS-system does not provide for the posting of negative quantities, the parameter /NEG_MENGE must be removed in the script myerprck.scr.

Corrections of postings can be recognized by an "S" (cancellation) in the ERFART field. This value can be identified in the maintenance of postings in the field "Input type" . To the extent that corrections are uploaded, canceled values will be confirmed as absolute values (without sign) and be stored with an "S" to the ERFART field.

Page updated

Report abuse