Output-Event: General tab

Complete the fields on the General tab as follows.

Field Contents

Number

(Mandatory)

You can create a maximum of 90 Output-Events for a Financial-Case. To identify each of them, enter a number between 01 and 90. Each Output-Event must have a unique number.

You can open and edit several Output-Events at the same time.

Label

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

Status

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

Business-Document

(Mandatory)

Use this field to select an output-Business-Document to define the structure of the Output-Event segments.

Composer then displays the selected output-Business-Document in the Mapping Rule tab where you can map fields from the input Business-Document you selected as the input structure of the Transformation-Rule.

If you change the Business-Document, AccountingIntegrator Enabler displays the warning message: "Selected Business-Document object has been changed. Do you want to keep compatible mapping rules?" If you answer:

Answer

Then AccountingIntegrator Enabler ...

Yes

Only deletes those Mapping Rules in the Output-Event that are not compatible with the new format.

Compatible fields must have the same name, but can have different data types or definitions. If the data type changes, AccountingIntegrator Enabler truncates the fields to fit where necessary.

No

  • Deletes all existing Mapping Rules in the Output-Event
  • Reinitializes the mapping expressions in those fields which have the default value associated with their data class

Data class of field

AccountingIntegrator Enabler reinitializes field to...

Integer

0

Date

No specified value.

AccountingIntegrator Enabler leaves the mapping expression empty.

String

During this operation, if mappings already exist in the Output-Event, either its own mappings or those inherited from a parent object you previously selected, then Composer gives you the following options, depending on whether the fields are compatible with the new Business-Document:

Field type

AccountingIntegrator Enabler ...

Compatible,that is, the fields have the same name as in the Business-Document.

Retains the mappings in the Output-Event in the form of default mappings.

Not compatible

Removes the mappings.

In addition, when you change the Business-Document, AccountingIntegrator Enabler automatically removes any associated Output-Event Template/ Mapping-Template you selected previously.

In an Output-Event Template, you can only change the Business-Document if the template is not being used by another Output-Event.

Output-Event Template

Select this check box to set the Output-Event as an Output-Event template. AccountingIntegrator Enabler automatically sets the Output-Event Template/ Mapping-Template drop-down list to only display Mapping-Templates compatible with the Business-Document you select for this Output-Event. That is, Composer only displays the Mapping-Templates which use the same Business-Document.

If you do not select this option, AccountingIntegrator Enabler lists both the Output-Event Templates and Mapping-Templates which use the same Business-Document as the one you define for this Output-Event.

AccountingIntegrator Enabler conventions regarding Output-Event Templates

  • You can define a maximum of 10 Output-Event Templates in each Transformation-Rule.
  • The Output-Events are listed in the General tab of the Financial-Case object. An Output-Event designated as a template is shown as .
  • All non-template Output-Events are shown as:
    • Not classified
    • Credit
    • Debit
  • You can only unselect this option when no Output-Events use the Output-Event template.
  • If a child Output-Event references an Output-Event template, it must overwrite at least one mapping. This constraint is imposed by AccountingIntegrator Rule Engine.

Output-Event template/ Mapping-Template

You can apply the following templates to the Output-Event:

  • Output-Event template: enables you to apply mappings from another Output-Event on condition that it belongs to the same Transformation-Rule.
  • Mapping-Template: enables you to apply mappings across several Transformation-Rules.

When you apply the template, the Output-Event becomes the child object of the parent template. From the drop-down list, select the parent template whose mappings you want this Output-Event to inherit.

To differentiate the inherited mappings from those defined in the child object itself, Composer uses the following color coding to display the mappings in the Mapping-Rule tab:

Mapping color

To indicate that the mapping belongs to the ...

black

current Output-Event

blue

Output-Event template parent object that the Output-Event child object, uses.

You can overwrite this type of mapping in the Output-Event child object.

green

Mapping-Template or Output-Event template parent object that the child object uses.

An Output-Event template can in effect be both a parent and child object.

You can modify and overwrite this type of mapping in the Output-Event child object.

red

Mapping-Template or Output-Event template parent object that the child object uses.

You cannot modify and overwrite this type of mapping in the Output-Event child object.

If you remove overwrites you made to an inherited mapping, Composer automatically reinitializes the field with either of the following:

  • the inherited mapping, if you select a parent object
  • the default value for the data class associated with this field

If you select a new parent object in an Output-Event that either has its own mappings or inherits them from a parent object you previously selected, Composer displays the message: "Selected Output-Event/Mapping-Template object has been changed. Do you want to keep old mapping rules template and set as the default mapping?"

Answer

Then AccountingIntegrator Enabler ...

Yes

Retains the mappings in the Output-Event in the form of overwrites to the modifiable mappings that will be inherited from the new parent object you selected.

However, if, for a given field, there are duplicates between the inherited mapping and the original one, that is, the expressions are absolutely identical, AccountingIntegrator Enabler removes the overwrite and only takes into account the inherited mapping.

No

Deletes the mappings.

If you remove the parent/child link,that is, you unselect the parent object,Composer displays the message: "Selected Output-Event/Mapping-Template object has been changed. Do you want to keep old mapping rules template and set as the default mapping?"

Answer

Then AccountingIntegrator Enabler ...

Yes

Retains the mappings in the Output-Event in the form of default mappings

No

Deletes the mappings.

Financial-Tag

From the drop-down list, select the Financial-Tag which describes the functional role of this Output-Event. [FOR DETAILS Financial Tags]

Generation

If you created Generation conditions in the Mapping Rule tab, use these radio buttons to define how many times AccountingIntegrator Rule Engine tests the condition criteria and thus generate the Output-Events. The maximum number of Output-Events you can generate is 90.

Composer distinguishes the Output-Events that have generation conditions with the icon in the Financial-Case General tab.

Note

From the Financial-Case General tab, when you position the cursor over an Output-Event, the ToolTip displays the Generation condition and whether or not it is Exclusive. In addition the ToolTip shows the Priority and Number properties of the Output-Event.

Generate Output-Event once if condition verified

Output-Event is generated once if the condition is true.

Repeat Output-Event generation provided condition verified

Output-Event is generated as many times as the condition is valid. If you select this option, you must use a Variable in the condition, to avoid provoking an error when AccountingIntegrator Rule Engine generates more than 90 Output-Events for a given Financial Case when it processes the Transformation-Rule.

Back to top

Related Links