Transformation anomalies

Title:  INPUT-EVENT ANOMALIES AND REJECTIONS REPORT

This report is produced automatically; you do not need to set any special parameters in the script.ges file.

This report lists the properties of each anomaly that was found during the session. It uses the ap.Detail_Anomaly_Reject_IEvent intermediate data file. This report may be empty if no anomalies were found during transformation.

The information is presented in the following blocks:

  • General information
  • The Input-Event identifiers
  • The anomaly identifiers
  • A description of the rule
  • System identifiers
  • The content of the segment

Certain blocks of information may be empty, depending on the type of anomaly found.

General information

This information identifies the anomaly within the anomalies file:

Label Displayed Meaning

Anomaly Number

Sequence number of the anomaly. Identifies the anomaly as the nth found in the session

Input-Event in Error

Sequence number of the Input-Event in error. Identifies the Input-Event as the nth found to be in anomaly in the session

Segment Sequence Number

Sequence number of the segment within the Input-Event. Identifies it as the nth segment in the processed Input-Event

Input-Event identifiers

This information identifies the Input-Event in anomaly:

Label Displayed Meaning

Group Code

Code of the group to which the Input-Event belongs
(optional information)

Input-Event Code

Name of the type of Input-Event processed

Input-Event Version

The version number of the Input-Event processed

Input-Event Instance Code

Instance code of the Input-Event in anomaly (optional information)

Anomaly identifiers

This information allows a diagnosis of the problem with the Input-Event.

Display label Meaning

Anomaly Type

The anomaly type may be one of the following:

  • Rule: The execution of a rule was terminated by an anomaly
  • Input-Event rejected: The Input-Event being processed was rejected

Generation Level

The point at which the anomaly was detected:

  • Principal:The anomaly found causes the Input-Event to be placed in anomaly (or rejected)
  • Secondary: The anomaly described is caused by a principal anomaly or relates to an anomaly found earlier

Origin of rejection

Reason the Input-Event was rejected (if the anomaly type is Input-Event rejected):

  • Identification of Input-Events:
    The Input-Event type that was to be processed could not be identified
  • Identification of the segment:
    One of the Input-Event segments could not be identified
  • Input-Event check:
    A check that was applied to the Input-Event (through an exit) failed
  • All phases in anomaly:
    The execution of each of the phases associated with the Input-Event type was terminated by an anomaly
  • Balance at Input-Event level:
    The balance check at Input-Event level failed
  • Output-Event check:
    An Output-Event check (through an exit) failed
  • Segment audit:
    The application of an audit rule to a segment caused an anomaly
  • Phase recycling:
    The Input-Event was recycled and the application of the phase is in anomaly
  • Input-Event with no Output-Event:
    The transformation of the Input-Event produced no Output-Events and the IEvent_No_Output keyword is set to No
  • Balance at group level:
    The balance check at group level failed

Error code

The code of the error detected

Error and additional description

Description of the anomaly

Phase code

Name of the phase in which the error occurred. Optional information

Domain code

Name of the domain that was active when the anomaly occurred

Segment code

Type of segment found to be in anomaly during processing

Description of the anomaly

This information identifies precisely the processing that was underway when the anomaly occurred. The information supplied varies with the type of processing:

Processing in anomaly Information displayed

Enrichment-Rule

Rule code (the name of the Enrichment-Rule that was applied)

Rule version (the start and end dates that define the period of validity of the version of the rule)

Output-Event generation rule (Transformation-Rule)

 

 

If Detection Level = Financial-Case

 


If Detection Level = Mapping Rule

Rule code, that is, the name of the Transformation-Rule that was applied

Rule version, that is, the start and end dates that define the period of validity of the version of the rule

Detection level: execution Financial-Case or Mapping Rule

Priority code (identifies the execution priority level of the Financial-Case)

Financial-Case code (the number of the Financial-Case)

Financial-Case code (the number of the Financial-Case)

Output-Event mapping order (the order in which it is created)

Minimum Field Position (minimum position of the field in the structure)

Output-Event segment structure code (name of the structure  used by the Output-Event)

Segment audit

Rule code (name of the audit rule applied to the Output-Event)

Rule version, (the start and end dates that define the period of validity of the version of the rule)

Segment aggregation

Rule code (name of the aggregation rule applied to the segment)

Rule version, (the start and end dates that define the period of validity of the version of the rule)

Output-Event audit

Rule code (name of the audit rule applied to the Output-Event)

Rule version, that is, the start and end dates that define the period of validity of the version of the rule

Information on the Transformation-Rule that generated the Output-Event: name, rule version, Financial-Case number, Mapping Rule order, Output-Event structure

Output-Event Aggregation

Rule code (name of the aggregation rule applied to the Output-Event)

Rule version, that is, the start and end dates that define the period of validity of the version of the rule

Information on the Transformation-Rule that generated the Output-Event: name, rule version, Financial-Case number, Mapping Rule order, Output-Event structure

Balancing check on Output-Events (at rule level)

Rule code (name of the balancing rule applied to the Output-Events)

Rule version (start and end dates that define the period of validity of the version of the rule)

Information on the Transformation-Rule that generated the Output-Events: name, rule version, Financial-Case number, Mapping Rule order, Output-Event structure

Enrichment of the Output-Event by an exit

Information on the Transformation-Rule that generated the Output-Event: name, rule version, Financial-Case number, Mapping Rule order, Output-Event structure

Accounting check on an Output-Event

Rule code (name of the Transformation-Rule that was applied)

Rule without an Output-Event

Rule version (start and end dates that define the period of validity of the version of the rule)

System identifiers

This is the diagnostic information that the Axway support staff will require, if you need support.

Contents of the segment

This information is not displayed if the Input-Event or segment cannot be identified. Instead, the following message is displayed: The segment format is unknown.

The report displays the values of each of the fields that make up the processed segment. The table below lists these fields:

Column Name Meaning

Field code

Name of the field in the structure

Field label

Description of the field in the structure

Field position

Position of the field in the structure

Field length

Length of the field in the structure

Field data type

Internal data type of the field in the structure

Field Value

Value of the field in the current segment
This may be empty if the value has not been supplied

Caution   This report does not display the results of the Pre-calculations in the Transformation-Rules.

The fields are displayed in alphabetical order. On MVS you can display the information in the order in which the fields are defined in the structure, by replacing the EDDETANO printing step with the following lines:

//RGCLCR   DD DSN=SOP$TEST.SHRRDJ.XRDJ11.DATFVS.RGCLCR.CLST,DISP=SHR//DESCEE   DD DSN=SOP$TEST.SHRRDJ.XRDJ11.DATFVS.DESCEE.CLST,DISP=SHR

By:

//RGCLCR   DD DSN=SOP$TEST.SHRRDJ.XRDJ11.DATFAX.RGCLCR.AIX.PATH,DISP=SHR//DESCEE   DD DSN=SOP$TEST.SHRRDJ.XRDJ11.DATFAX.DESCEE.AIX.PATH,DISP=SHR

Note   The prefix « SOP$TEST.SHRRDJ.XRDJ11 » is specific to the Axway environment.

Related Links