Input-Event rejected

The Input-Event is rejected when either:

  • An error occurs during processing in Step E or S
  • All the Transformation–Phases using the Input-Event concerned are in error in Step T

Circumstances

The processing error that causes the Input-Event to be rejected may arise for one of the following reasons:

Reason Meaning

1

It cannot be identified

2

No processing is required in the parameter settings for this type of Input-Event

3

There is an anomaly in the restructuring exit for this Input-Event

4

There is an anomaly in the pre-transformation checking and enrichment exit for this Input-Event

5

There is an anomaly in the preprocessing applied

6

All the processing applied to this Input-Event in the Transformation-Phases in step T are placed in anomaly

7

The Input-Event-level balance check fails

8

No Output-Events are generated and the option to Check for the production of at least one Output-Event per Input-Event is not enabled

Consequences

Reason Meaning

1

Nothing is generated from the transformation of the Input-Event

2

All the transformation anomalies are printed

3

A copy of the Input-Event is output to the Rejected_IEvent exchange zone, so that it can be recycled

4

If the Group Management option is active, the group to which the Input-Event belongs is also rejected

5

If the aggregation option is active, it is the individual Input-Events that are rejected

6

If the most serious error found in the session is a rejected Input-Event, a return code of 6 is set for the execution

7

If a rejection threshold is reached, either for Events or groups, this causes the system to stop the session with a return code=10.
(See the tables in Reminder about how the Rule Engine works paragraph)

Related Links