Audit-Rule: start here

What is an Audit-Rule

Where is an Audit-Rule

How you define an Audit-Rule

How you use an Audit-Rule

What is an Audit-Rule?

The Audit-Rule object lets you define the information that will be kept about how individual items of information are processed. The Audit-Rule provides a means of taking a snapshot of the value of data that AccountingIntegrator Rule Engine processes at any given stage in the transformation cycle. The information is stored as an audit trail, which constitutes a complete trace on how a specific Output-Event was created (as a field in an Input-Event) and processed (via all the Rules applied to it). The audit mechanism is thus an important feature given the volume and sequence of processing that the information undergoes in the course of a transformation session.

To summarize the AccountingIntegrator Enabler philosophy, the objective is to produce Output-Events from Input-Events fed by Financial-Events based on upstream applications external to AccountingIntegrator Enabler and then send these Output-Events to Processing-Context-Out objects.

The Audit Rules must therefore apply:

  • During the transformation of the Input-Event segments
  • During the Pre-processing phase: That is, as pre-Audit Rules before you run an Aggregation-Rule on the Input-Event and then as post-Audit-Rules after the Aggregation-Rule.
  • During the Processing phase: That is, as a pre-Audit-Rule before the Transformation-Rule and as a post-Audit Rule after the Enrichment-Rule.
  • During the data flow to the Processing-Context-Out

This two-level audit is required because it is logical to audit the beginning (Input-Event) and the end (Processing-Context-Out) of the processing sequence. The Audit-Rules applied on the Input-Event and Processing-Context-Out are not generally the same, as they are defined from Business-Documents with distinct structures given that the Input-Event and Output-Event structures are generally different.

Where is an Audit-Rule?

Axway module

AccountingIntegrator Enabler

Workbench

Integration-Services: Finance tab

Object dependencies

When you define or import an object, it is stored in the metadata repository and is available for reuse by other objects. Typically, the objects that you define exist in a specific object hierarchy. That is, objects:

  • use objects below them in the hierarchy
  • are used by objects above them in the hierarchy

To help you manage the interlinked network of objects, the software provides the Object Dependencies Browser that displays the object dependencies for a selected object.

The following table lists the objects that use and are used by Audit-Rules.

Audit-Rules

Use

Are used by

Business-Documents

Input-Events

How you define an Audit-Rule

Before you define an Audit-Rule

Before you create an Audit-Rule, you must create a Business-Document. The Business-Document describes the format of the segments on which you run Output-Events where you apply this Rule.

Defining an Audit-Rule

Create the Audit-Rule object from the Dictionary tab.

To define a new Audit-Rule object, complete the following tabs:

In addition, the Audit-Rule properties window contains the following tabs:

  • Signature tab
  • Description tab

After you define an Audit-Rule

After you define an Audit-Rule object, you can apply the Audit-Rule in the Processing tab of an Input-Event.

How you use an Audit-Rule

You can perform all basic operations on Audit-Rule objects, depending on your user rights. [FOR DETAILS: "Working with objects" in the Composer User Guide.]

The Audit-Rule object does not follow the standard object life cycle. You cannot explicitly send this object to Production.

Back to top

Related Links