Financial-Case: General tab

About the General tab

Setting Financial-Case properties on the General tab

Associating Output-Events

Managing Output-Events

About the General tab

The General tab contains the descriptive elements of the Financial-Case object.

The following diagram schematically illustrates the General tab.

Properties information

  • Business-Document tab displaying the tree structure of available segments in a Business-Document or any Pre-calculations you have defined. You can drag-and-drop segments into the Condition field to create a condition expression that must be fulfilled for the Financial-Case to be executed.
  • Output-Event tab displaying available Output-Events not yet assigned to the Financial-Case. Drag-and-drop Output-Events into the lower zone to associate the Output-Event with the Financial-Case either as a credit, debit or non-accounting entry.

T- account representation that shows the Output-Events attributed to the Financial-Case, either as credits, debits, or non-accounting 'entries'.



Unclassified (non-accounting) Output-Event

You must define a minimum of one and a maximum of ten Financial-Cases for a given Transformation-Rule. You can open and edit several Financial-Cases at the same time.

Setting Financial-Case properties

Complete the fields on the General tab as follows.

Field Description



You can create a maximum of ten Financial-Cases for a Transformation-Rule. To identify each of them, enter a number between 1 and 10. Make sure it does not correspond to a Number already defined.

When you assign a Number to a Financial-Case you can then use it as sort criteria, by toggling the Number column heading on the Transformation-Rule Financial-Cases tab.



Financial-Cases are executed in order of priority. Set the priority value to between 0 and 9, where 0 represents the highest priority.

You can then sort the Financial-Cases by Priority, by toggling the Priority column heading on the Transformation-Rule Financial-Cases tab.

If several Financial-Cases have the same Priority, AccountingIntegrator Enabler executes them in ascending Number order.

Exclusive Financial-Case

AccountingIntegrator Enabler respects the order of execution determined by the Number/Priority combination. AccountingIntegrator Enabler executes sequentially all the non-exclusive  Financial-Cases whose generation conditions are met until it encounters the first Exclusive Financial-Case with a valid generation condition.

When an exclusive Financial-Case is executed,  AccountingIntegrator Enabler skips all subsequent Financial-Cases and stops executing the Rule.


Financial-Case n°1/ Priority 1= exclusive

Financial-Case N°2 / Priority 0= non-exclusive

Financial-Case n°3 / Priority 0 = non-exclusive

Financial-Case n°4 / Priority 1= non-exclusive

The following table summarizes the order of execution based on various criteria.

Execution basis

Order of execution

N°/Priority combinations only


All the generation conditions are met


Financial-Case N°4 will not be executed because it is scheduled after an exclusive Financial-Case.

Generation condition of Financial-Case N°1 not met




Enter an optional free-text description for the Financial-Case of 255 characters maximum. This text appears in the Label field on the Transformation-Rule Financial-Cases tab ., theEntity Browser (Label field), Output-Event Browser and as a tooltip when you position the cursor over the Financial-Case object.


Use this field to define an execution condition.

  1. Select the criteria to evaluate from one of the following:
  2. an input Business-Document segment. Drag-and-drop to the Condition field the segment that contains the field to evaluate.
  3. a Pre-Calculation
  4. the result of a lookup in a Table
  5. a Variable
  6. the result of an exit call
  7. any combination of the above criteria using DML
  1. Enter the condition expression to trigger the generation of the Output-Events associated with the Financial-Case.
    You can enter this value manually or via the DML Object Browser.

If you do not specify a condition, the Output-Events are generated automatically.

Associating Output-Events

You must associate at least one Output-Event with a Financial-Case. A Financial-Case can generate a maximum of 90 Output-Events.

  1. From the list of Output-Events on the Output-Event tab, in the right pane, select the Output-Events you want to generate when you apply the Financial-Case.

If the list is empty,you can use either of the following methods to create an Output-Event:

  • Right-click the Output-Event tab and select Create an Output-Event.
  • Click on the Output-Event tool bar.
  1. Drag the selected Output-Event(s) to the appropriate zone:
  • Credit
  • Debit
  • Non-classified Output-Event

Use the drag-and-drop feature to move Output-Events between the above zones.

AccountingIntegrator Enabler creates the Output-Events in the order in which you selected them.

Managing Output-Events

Use the Output-Event contextual menu as explained in the following table to work with Output-Events.

Click To...

Create new Output-Event.

This opens up the Output-Event property window.

You can add a new Output-Event after selecting an Output-Event in the hierarchical list. Composer adds the new Output-Event to the bottom of the list of existing Output-Events and assigns a default number incremented by one relative to the maximum already used.

Numbering rules

If the number 90 is already in use, Composer searches from 1 to 90 and uses the first non-assigned number.

Duplicate the selected Output-Event.

A copy of this Output-Event is inserted after all the other Output-Events in the current list, with a number incremented by one relative to the maximum already used. [FOR DETAILS:Output-Event numbering rules]

If the selected Output-Event references an Output-Event Template, the duplicate also references the same Output-Event Template.

Renumber the selected Output-Event.

AccountingIntegrator Enabler assigns the value you enter to the selected Output-Event. If an Output-Event in the Transformation-Rule already exists with the given number, AccountingIntegrator Enabler automatically increments the number by one. This process continues until the renumbering of an Output-Event no longer creates a conflict within the Transformation-Rule.

Output-Event Template considerations

AccountingIntegrator Enabler must respect the constraint of always having a lower number assigned to the Output-Event Template than the Output-Event that uses it. If the selected Output-Event:

  • references an Output-Event Template:  if the number you enter is less than or equal to that of the Output-Event Template, AccountingIntegrator Enabler cancels the action.
  • is itself an Output-Event Template: if the number you enter is more than or equal to that of one of the Output-Events that use it, AccountingIntegrator Enabler cancels the action.


A Transformation-rule has a list of Output-Events: 1,2,3,5 where Output-Event N°2 is an Output-Event Template used by Output-Event N°5.

The following table summarizes the implications of renumbering. Note: These examples are separate are not performed in sequence.

If you change Output-Event number


then, AccountingIntegrator Enabler ...



automatically renumbers N°2 as N°3 and N°3 as N°4



performs the action


N°1 or N°2

cancels the action



performs the action


N°5 or N°6

cancels the action


Show properties of the selected Output-Event.

Analyze dependencies for the selected Output-Event using the Transformation-Rule Browser.

Delete the selected Output-Event.

If the Output-Event is already associated with another Financial-Case, you must confirm your deletion request in the system message which appears.

You cannot delete the Output-Event if an Output-Event Template used by another ME.

Copy the selected Output-Event.

This operation copies the selected Output-Events together with the Output-Event Templates they use onto the clipboard. From the clipboard, you can paste them into either the same Rule or another one which uses the same input Business-Document.

Create a Mapping-Template based on the selected Output-Event

AccountingIntegrator Enabler creates a new Mapping-Template object based on the following elements in the Output-Event:

  • Business-Document
  • inherited mappings
  • overwritten mappings

Paste the selected Output-Event.

AccountingIntegrator Enabler transfers the Output-Events from the clipboard into the selected Financial-Case.

AccountingIntegrator Enabler adds the new Output-Event created to the bottom of the list of existing Output-Events in the list. The renumbering constraints are the same as for creating and duplicating Output-Events. [FOR DETAILS:Output-Event numbering rules]

Output-Event Template considerations

If an Output-Event Template is copied dynamically, that is, you did not select it explicitly when you performed the Copy operation, but selected an Output-Event which uses the Output-Event Template:

  • AccountingIntegrator Enabler first checks whether an identical Output-Event Template already exists in the current Transformation-Rule.
  • If one exists, AccountingIntegrator Enabler does not paste the Output-Event Template, but instead switches all the copied Output-Events that use it to reference the existing template.


A Transformation-rule, RL1, has a list of Output-Events: 1,2,3,5 where Output-Event N°2 is an Output-Event Template used by Output-Event N°5. The following sequence illustrates the implications of copying and pasting:

  1. Copy N°1 and N°2, AccountingIntegrator Enabler places them on the clipboard.
  2. Create a new Transformation-Rule, RL2, with the same input Business-Document and also create a new Financial-Case.
  3. Paste the copied Output-Events into the Financial-Case. AccountingIntegrator Enabler creates Output-Events N°1 and N°2.
  4. In RL1, copy Output-Event N°5, AccountingIntegrator Enabler places N°5 and N°2 on the clipboard.
  5. In RL2, paste the newly copied Output-Events into the Financial-Case. AccountingIntegrator Enabler only pastes N°5 and sets it to reference the existing Output-Event Template N°2.

Renumbering Output-Events

In addition you can renumber an Output-Event using the drag-and-drop function to move Output-Events up and down in the ordered list.

Back to top

Related Links