Output-Event: Start here

What is an Output-Event

Where is an Output-Event

How you define an Output-Event

How you use an Output-Event

What is an Output-Event?

An Output-Event is an output segment produced by AccountingIntegrator Enabler as a result of transforming the Input-Event segments entered into a Transformation-Rule. AccountingIntegrator Enabler performs this transformation operation via the set of mappings which define the way each field in the incoming structure is transformed before the system assigns it to a field in the outgoing structure.

The definition of an Output-Event is based on the following:

  • A Business-Document: provides the structure of the Output-Event.
  • (optional) A Mapping-Template or Output-Event template: The Mapping-Template is an object that describes a set of mappings which correspond to a given Business-Document and specifies the condition to fulfill before the system can generate the mappings.
  • (optional) A Financial-Tag which you can use to perform balancing operations in a Balancing-Rule.

Parent and child Output-Events

The relationship between parent and child Output-Events is hierarchical. A child is an Output-Event which references another Output-Event or a Mapping-Template, both of which are parent objects. A parent object and child Output-Event must have the same structure, that is, use the same Business-Document.  By default, the child Output-Event inherits all mappings from the parent object or Template. Composer automatically modifies the child Output-Events whenever you change mapping parameters in either the parent object or the Mapping Template.

You can overwrite the inherited mappings in the child Output-Event only if you previously defined the inherited mappings as modifiable. However, when you overwrite inherited mapping values, you break the link between the child and parent for each overwritten field. This means there is no automatic update of changes to these customized fields.

Output-Event templates

When you define the mappings in an Output-Event, including an Output-Event that inherits from a Mapping-Template, you can then declare the Output-Event as an Output-Event template and reuse it as a template for other Output-Events within the same Transformation-Rule.

You use an Output-Event template to make available all the common mappings within a given Transformation-Rule so as to optimize processing when AccountingIntegrator Enabler executes the Transformation-Rule.

The benefits of each type of template available for an Output-Event are summarized as follows:

Template type Benefit


Saves time during the design stage because you avoid having to redefine identical mappings in several Output-Events.

Output-Event template

Saves time during the execution stage when AccountingIntegrator Enabler runs the Transformation-Rule. AccountingIntegrator Enabler optimizes the processing of the Output-Event that reference the Output-Event template in either of the following methods:

  • stores the Output-Event template
  • stores the Output-Event template and generates it as an entirely separate entry

Selecting Output-Event templates in Financial-Cases

Whichever method you choose for processing the Output-Event template, the system applies it globally to the Transformation-Rule and thus to the Financial-Cases it executes. Consequently, to have an exact reflection of what AccountingIntegrator Enabler executes when you generate an Output-Event template, you must stick to the following principles:

  • Select the Output-Event template in the target Financial-Case.
  • Select the Output-Event template in Financial-Cases where you have selected at least one child Output-Event that references the Output-Event template.

This method enables you to view the exact status of the Output-Events that AccountingIntegrator Enabler generates when it executes a Rule.

When you Check the Rule, the system verifies that the Output-Event templates are correctly selected in the Financial-Cases.

Executing mappings in Output-Event templates

As with the mappings in Pre-calculations, AccountingIntegrator Enabler only executes the Output-Event template mappings once, when it begins processing the Transformation-Rule. It is therefore recommended that you do not use data calculated dynamically during the transformation of the Output-Events.

For example, if you increment the value of a Variable to use it as a counter in the Output-Event mappings, and you store this mapping in an Output-Event template instead of in the Output-Events that use the template, the system always produces the same value. That is, the system generates the value it calculated once for the Output-Event template instead of a recalculated value for each output segment.

Where is an Output-Event?

Axway module

AccountingIntegrator Enabler


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 Output-Events.


How you define an Output-Event

Before you define an Output-Event

Before you create an Output-Event, you must create a Financial-Case within a Transformation-Rule

Defining an Output-Event

Create the Output-Event in the Dictionary or Business view tabs:

  • Either within the Financial-Case sub-element of a Transformation-Rule object.
  • Or directly as a sub-element of the Transformation-Rule object in the tree hierarchy by selecting the Create Output-Event action in the contextual menu.
    The Output-Event that you create is then nested in the Transformation-Rule under the Financial-Case that it is associated with.

To define a new Output-Event object, complete the following tabs:

In addition, the Output-Event properties window contains the following tabs:

  • Signature tab
  • Description tab

After you define an Output-Event

After you define an Output-Event object, you can:

  • Change it into an Output-Event template to use its mappings in other Output-Events in the same Transformation-Rule
  • associate the Output-Event with a Financial-Case

How you use an Output-Event

You can perform all basic operations on Output-Event objects, depending on your user rights. [FOR DETAILS: Working with objects: Start here]

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

Back to top

Related Links