Error Handling

Message Header

If a process message cannot be processed correctly by PROCESS_MESS_UPLOAD, the return code for this message is set to a value not equal to 0 (field RCODE in table MSHD).

Return codes on message header level:

Return code

Meaning

0

Message processed correctly.

1

Plant does not exist (field WERK in table MSHD.

2

Message category not created in the plant (field MSCLA in table MSHD).

3

Invalid test indicator (field TSTKZ in table MSHD).

4

No authorization to create process messages in the specified plant.

99

Message could not be processed due to an error in the corresponding characteristic. (see section on error handling at characteristic level below)

 

Message Characteristics

If inconsistencies or errors are discovered when the message characteristics are checked, the return code of the corresponding characteristic is set to a value not equal to 0 (field RCODE in table MSEL).

Return codes at message characteristic level:

Return code

Meaning

0

No errors discovered during characteristic check

1

Characteristic is not created (field ATNAM)

2

Invalid characteristic format (field ATFOR)

3

According to the characteristic definition in PP-PI, the characteristic value should be a long text. However, the table TLINES does not contain a corresponding entry.

4

No value assigned to characteristic. This is not allowed according to the characteristic definition within PP-PI.

5

The corresponding characteristic is used in the message more than once.

 

If one of the errors listed above occurs, the corresponding process message cannot be processed. The return code at message header level is set to 99.

Internal Errors

If errors occur during message processing that are not due to faulty or inconsistent interface data, the exception INTERNAL_ERROR is triggered. In this case, none of the process messages transferred are processed.

Processing of Transactional RFC

f the control system does not transfer an RFC destination to PP-PI in a transactional message upload (parameter RFC_DESTINATION_FOR_TRFC), the results of message processing cannot be transferred to the control system. In this case, PP-PI raises exception NO_RFC_DESTINATION. The system does not process the process messages transferred.