Input-Event in anomaly during transformation

The Input-Event is placed in anomaly when a processing error occurs in one of the component segments during a Transformation-Phase in step T.

The Input-Event in anomaly is associated with the Transformation-Phase during which the anomaly occurred.

Circumstances

The processing error arose during the Transformation-Phase for one of the following reasons:

Reason Meaning

1

An anomaly was found during the execution of the enrichment and check exit called before the execution of one of the phase rules phase

2

An anomaly is found in the application of a phase rules to a segment of the current Input-Event

3

An anomaly is found in the application of a rule to one of the Output-Events generated from the current Input-Event

4

An anomaly is found during the check carried out on one of the Output-Events generated from the current Input-Event
This check can be carried out either by the core code or by an exit

5

The rule does not generate any Output-Events and the option to Check for production of at least one Output-Event per Transformation-Rule is not enabled

Note   Note:If all the Transformation-Phases applied to the Input-Event type result in anomalies, the Input-Event is rejected. (See Input-Event rejected).

Consequences

Reason Meaning

1

All the products of the Transformation-Phase are canceled for all the component segments in the Input-Event

2

The products from the other Transformation-Phases are kept and generated as output, provided that these phases complete properly

3

An anomaly is listed in the report, with a description of its salient features

4

The Input-Event is copied out to the Anomaly_IEvent exchange zone, so that it can be recycled

5

The name of the phase in which the anomaly occurred  is written in the Input-Event according to the position and length defined in the Processing-Context-Out if you have declared the technical field Code_Phase_Anomaly

6

The Input-Event is not redirected

7

The Input-Event in anomaly is written to the Anomaly_IEvent file in the results directory

If the most serious error found in the session is an anomaly in an Input-Event, a return code of 4 is set for the execution.

If a rejection threshold is reached, either for Events or groups, this causes the system to stop the session with a return code=10. For more information, refer to Session stopped.

Related Links