Transformation-Rule: General tab

Complete the fields on the General tab as follows.

Field Contents

Name

(Mandatory)

Enter a mandatory name for the Transformation-Rule. This is the logical name that is used to reference the Transformation-Rule object throughout AccountingIntegrator Enabler.

You can enter up to five alphanumeric characters which must respect the naming conventions.

Note: A single Folder cannot contain a Transformation-Rule and an Enrichment-Rule that have the same name.

Version

The Version is a numeric reference that you enter manually to designate which version of a given Transformation-Rule this represents. [FOR DETAILS: Versions and validity periods]

Label

Enter an optional free-text description for the Transformation-Rule. This text appears in the Entity Browser (Label field) and as a Tooltip when you position the cursor over the Transformation-Rule object.

Status

This field displays the current status of the Transformation-Rule, set to ToBeChecked by default. You cannot directly change the status in this field. [FOR DETAILS: life cycle and statuses]

Business-Document

(Mandatory)

This field references the Business-Document which defines the structure of the Input-Event segments to be transformed by this Rule.

Select an input Business-Document from the drop-down list of available Business-Documents.

Validity period

[FOR DETAILS Versions and validity periods]

Any given version of a Transformation-Rule is only valid and applicable during a specific time period, referred to as the validity period.

To define this period, you specify its start date and end date, as follows.

Start date

Use to set the start and end dates of the validity period.

End date

 

Balancing Check

Defines whether the Output-Events generated by this Rule can be entered in a balancing check, provided you activated a Balancing-Rule in the Processing-Context-Out. The following table provides an example of an Input-Event with several different Rules applied to its segments.

 

Input-Event

Composed of segments

 

Each segment can have a set of Rules associated with it

Each of these Rules generates a set of Output-Events (OE)

Segment 1 (S1)

Rule 1 (R1)

Rule 2 (R2)

Rule 3 (R3)

OE of S1/R1

OE of S1/R2

OE of S1/R3

Segment 2 (S2)

Rule A (RA)

Rule B (RB)

OE of S2/RA

OE of S2/RB

Segment 3 (S3)

Rule X (RX)

OE of S3/RX

Select one of the following options:

  • At Event level: the Output-Events generated by this Rule are processed in the Input-Event level balancing check.

    All the Output-Events generated from a given Input-Event via the associated Rules must be balanced. In the example above, this means Output-Events S1/R1 to S3/RX.

  • At Rule level: the Output-Events generated by this Rule are processed in the balancing check applied via a Balancing-Rule.

    Only the Output-Events generated by a specific Transformation-Rule associated with a given Input-Event must be balanced. In the example above, for Transformation-Rule B, only OE S2/RB is generated.

  • None: the Output-Events generated by this Rule are not subject to a balancing check.

Back to top

Related Links