Input-Event: Processing tab

About Processing

Completing the Pre-Processing Rules category

Completing the Processing category

Completing the Processing Rules tab

Using the Linked Rule versions tab

About Processing

An Input-Event comprises one or more segments, each of which defines a separate part of the Input-Event. For example, in the case of an invoice, you can have one header segment, several line segments and one footer segment. [FOR DETAILSWhat is an Input-Event?]

The Processing tab describes the Rules that AccountingIntegrator Enabler  Rule Engine applies to these Input-Event segments when it runs the session. It is illustrated schematically as follows.

Processing category to define the Rules to apply to each Segment Type during:

  • Pre-processing of the Input-Event
  • Processing of the Transformation-Phases

Dynamically loaded tab with the details of Rules to define in the Processing category you selected in the left pane.

Displays the:

Linked Rule versions tab

Dynamically loaded browser.

For each of the Rules you selected in the Processing category, this browser displays the existing Rule versions which are valid within the validity period(s) of the Input-Event.

Processing category

On the Input-Event Processing tab, you specify the Rules that AccountingIntegrator Enabler  Rule Engine applies when it runs the transformation session:

Processing option Rules to apply

Pre-Processing

  • Pre-Audit-Rule: to apply to detailed Input-Event segments before aggregation
  • Aggregation-Rule
  • Post-Audit-Rule: to apply to a set of aggregated Input-Event segments

Processing

  • Pre-Transformation-Rule(s): to apply before the Enrichment-Rule
  • Enrichment-Rule
  • Post-Audit-Rule: to apply after the Enrichment-Rule
  • Post-Transformation-Rule(s): to apply after the Enrichment-Rule

 

Completing the Pre-Processing Rules category

Use the Pre-Processing categoryto define which Rule versions to apply to each Segment Type during the Pre-Processing Phase. The Pre-Processing category comprises three sections:

The Pre-Processing node in the left pane contains the Segment Types that you previously defined on the Structuretab.

Use the Pre-Processing-Rules tab to define the Aggregation-Rule and Audit-Rules to apply each Segment Type during pre-processing:

  1. Click the Segment Type in the left pane.
  2. Complete the fields for that Segment Type on the Pre-Processing Rules tab, as described in the following table:
Field Contents

Pre-Audit-Rule

If you use the audit process, it is recommended that you associate two Audit-Rules with each Segment Type. The first Audit-Rule is applied to the individual Input-Event segment aggregation. The second Audit-Rule is applied to them after aggregation.

Use either of the following methods to select the Audit-Rule to apply before aggregation:

  • From the drop-down list: To filter the list of Rules displayed in the drop-down list, click and enter the filter criteria.
  • Drag-and-drop a Rule from the Dictionary tab or Entity Browser in the navigator pane.

[FOR DETAILSAudit-Rule: Start here]

Aggregation-Rule

Select an Aggregation-Rule to apply to the selected Segment Type.

[FOR DETAILS: Selecting a Rule]  

Each Segment Type can only have a single Aggregation-Rule.

Keep in mind that the Business-Document for the selected Aggregation-Rule must be identical to the Business-Document you selected for the Segment Type (Structure tab). If it does not, then AccountingIntegrator Enabler displays a warning message and rejects the Aggregation-Rule.

Aggregation-Rules can exist in different versions. [FOR DETAILS: Validity periods for Rules and Input-Events]

Post-Audit-Rule

Select an Audit-Rule to apply after aggregation.

[FOR DETAILS: Selecting a Rule]  

Completing the Processing category

Use the Processing categoryto define which Rule versions to apply to each Segment Type during the Processing Phase. The Processing category comprises three sections:

Using Transformation-Phases

Use Transformation Phasesto group processing to meet your requirements.

For example, you may need to route certain incoming segments generated by a financial application into your Accounting department, other segments into your Statistics department, and occasionally both sets of segments into both departments.

In this case you:

  1. Define two Phases:
  • ACCOUNTS: groups the processing required for the Accounting department
  • STATS: groups the processing required for the Statistics department
  1. Define two Transformation-Domains:
  2. ACCOUNTS: associated with the ACCOUNTS Phase
  3. STATS: associated with the STATS Phase
  1. On execution, you link the transformation environment to one of the Transformation-Domains or to both, depending on your requirements at the time.

Processing order in a Phase

AccountingIntegrator Enabler  Rule Engine, the execution engine, processes Rules related to Segment Types in a Phase in the following order:

  • 0 to 1Pre-Audit-Rules
  • 0 to n Transformation-Rules (1)
  • 0 to 1 Enrichment-Rules
  • 0 to 1 Post-Audit-Rules
  • 0 to n Transformation-Rules (2)

Restrictions

  • You cannot reuse the same Transformation-Rules in cases (1) and (2). In any given Phase, you can only use a given Transformation-Rule once.
  • If you do not use an Enrichment-Rule, you can only use the Pre-Audit-Rules and Transformation-Rules (1). Do not specify any Post-Audit or Transformation-Rule (2), because they are not applicable in this case.

Creating a Transformation-Phase

  1. Select the Processing node in the left pane of the Processing tab, then click .
    A new Transformation-Phase is added to the node. The new Phase is added to the bottom of the list of defined Phases. Each Phase nests the Segment Types defined on the Structure tab.
    The right pane changes to display information for that Phase.
  2. Complete the fields on the Phase tab as follows:
Field Contents

Name

(Mandatory)

Enter a mandatory name for the Transformation-Phase. This is the logical name that is used to reference the Phase throughout the software.

If a processing error occurs in the current Processing Phase, AccountingIntegrator Enabler writes the Phase name in the Phase code field of the Input-Event segment concerned.

As a default value, the system supplies the name P, followed by a number that increments for each additional Phase that you define. The name of the Phase determines the order in which the processing is executed. Phases are executed in ascending alphabetical order for a given Transformation-Domain. That is, P1 is executed before P2.

You can enter up to 25 alphanumeric characters, including the underscore (" _ ") character.

Caution: The "_" character has an alphabetical order that varies depending on the target system. If you use it, you risk processing your Phases in an order different to the one you intended.

[FOR DETAILS: AccountingIntegrator Enabler standard character set]

Label

Enter an optional free-text description for the Input-Event. This text only appears on this tab.

Domain

(Mandatory)

From the drop-down list, select a Transformation-Domain for this Phase.

[FOR DETAILS: Transformation-Domains]

Completing the Processing Rules tab

Use the Processing Rules tab to select the Rules to apply to each Segment Type during the Processing Phase. When you select a Rule, the software checks that the basic structure of that Rule is identical to the structure of the Segment Type. If the structures are not identical, a warning message is displayed in the message pane when you click the Rule in the drop-down list.

For each type of Rule, a drop-down list displays all the available Rules. If no Rule is available, you must define one.

After you define the properties of a given Phase, expand the Phase node in the left pane of the window to display the list of Segment Types defined for this Input-Event.

For each Segment Type, complete the fields on the Processing Rules tab, as described in the following table:

Field Contents

Pre-Audit-Rule

From the drop-down list, select an Audit-Rule to apply before applying the Enrichment-Rule.

To filter the list of Rules displayed in the drop-down list, click and enter the filter criteria.

The guidelines for creating Audit-Rules are as follows:

  • If you use pre-processing, it is recommended that you specify the Audit-Rules in the pre-processing section (before and after the Aggregation-Rule). You can then specify the same Audit-Rule here in the Processing Phase, or select a completely separate one.
  • If you specify an Enrichment-Rule, you can define up to two Audit-Rules: one pre-Audit-Rule before the Enrichment-Rule and one post-Audit-Rule which executes after the Enrichment-Rule.
    However,if the last processing in the pre-processing stage is an Audit-Rule, it is not necessary to define an Audit-rule at the beginning of the processing stage.
  • If you do not have an Enrichment-Rule, you can only specify one Audit-Rule which you define either as a pre- or post-Audit depending on your auditing requirements.

Pre- Transformation-Rules

(Mandatory)

You must select at least one Transformation-Rule for each Segment Type. Each Transformation-Rule that you select will be processed in sequence in the order you specified.

To select a Transformation-Rule to apply before the Enrichment-Rule, click , then select an existing Transformation-Rule from the drop-down list.

To delete a selected Rule, click .

You cannot select the same Transformation-Rule twice for the same Segment Type.

Enrichment-Rule

Optionally, from the drop-down list, select an Enrichment-Rule to apply to this Segment Type.

[FOR DETAILS: Filtering Rules in drop-down list]

An Enrichment-Rule is used to modify, enrich and validate the data in an Input-Event segment. When this data is modified, the result can be used by the Transformation-Rules that process the modified segment.

Post- Audit-Rule

From the drop-down list, select the Audit-Rule that will be applied after processingthe Enrichment-Rule selected in the previous field.

[FOR DETAILS: Filtering Rules in drop-down list]

Post-Transformation-Rules

To select a Transformation-Rule to apply after the Enrichment-Rule, click and select an existing Transformation-Rule from the drop-down list.

To delete a selected Rule, click .

Using the Linked Rule versions tab

Composer provides the Linked Rule versions tab for you to view and verify, for each of the Rules you selected in the Pre-processing or Processing sub-tabs, the existing Rule versions which are valid within the validity period(s) of the Input-Event.

To view the properties of a Rule, right-click the selected Rule and select Properties from the contextual menu. Composer displays the Properties window of the Rule in read-only mode.

Back to top

Related Links