Audit rejects and anomalies

By default, rejects and anomalies of Input-Events are not tracked.

To track rejects and anomalies, configure process_context_in in the AI Enabler and select Audit of rejects and anomalies.

Example

In the case below, two Input-Event segments are aggregated in one record. The record is rejected during transformation rule and it produces two new records. Each record has a stampid prefixed with the letter J for rejects.

In the case below, two Input Event segments are aggregated in one record. The record is rejected as an anomaly only in the phase 2 of the transformation rule. It produces two new records. Each record has a stampid prefixed with letter O for anomalies.

Relationships

To manage the relationship between InterPlay and Rule Engine for rejects and anomalies, you must configure the multi-session audit.

To configure the multi-session audit, specify the position and length of the original stampId in the process_context_in file in the AI Enabler.

The RuleEngine, will set automatically the value of the Original Stampid in the ap.Cra file used by Interplay

Related Links