Get started with AccountingIntegrator

The following procedures illustrate an end-to-end scenario that uses the samples provided with the product.

Sample configuration in design environment:

Sample usage in runtime environment:

Prerequisites

Before you start, make sure that:

  • Components have been installed and started.
  • The AI Enabler has been setup with a user and a folder.

About AccountingIntegrator samples

To help you get started or to help you define a configuration based on an existing one, AccountingIntegrator provides samples that can be used by different services.

Located in the [Install_Path]/AccountingIntegrator/getStarted directory, the samples contain configuration and data that can be used to configure and test the user environment.

  • Configuration - Configuration file for the AI Enabler and the Rule Engine execution
  • Data - Input data file for the Rule Engine execution.

Samples description

RuleEngine Session1

The RuleEngine Session1 handles RELEASE Input-Events to provide:

  • NOM_ME Output-Events that are transformed into TAMORT Input-Events to be handled by the RuleEngine Session2. Each RELEASE Input-Event that is processed generates one NOM_ME Output-Event.
  • ACC_ME that are General Ledger entries supposed to be sent to a General Ledger application. At least four ACC_ME Output-Events are generated for each RELEASE Input-Event that is processed.
  • Audit files that contain traces to be stored. Five audit lines are generated for each RELEASE Input-Event that is processed.
  • Rejected events that are stored and and manually updated in Interplay before recycling to RuleEngine Session1. Two Input-Events are rejected in Session1.

RuleEngine Session2

The RuleEngine Session2 handles TAMORT Input-Events to provide:

  • TAM_ME Output-Events that contain the lines of the calculated amortization schedule for the loan. One line per month of amortization is provided for each TAMORT Input-Event processed.
  • Audit files that contain traces to be stored. One audit line is generated for each TAMORT line and TAM_ME line that is processed.

Input-Events in AI Enabler

The configured Input-Events in AI Enabler are:

  • RELEASE: Loan release, multi-segment Input-Event based on Business-Documents NOMINAL and FEES.
  • TAMORT: Amortization of loan.

The fictive Input-Events in AI Enabler are:

  • ACC_ME is a General Ledger entry event generated after RELEASE Input-Event and TAMORT Input-Event have been processed.
  • NOM_ME is generated when RELEASE Input-Event has been processed to be handled in a second Rule Engine session. It provides the loan amortization table transferred to the TAMORT Input-Event.
  • TAM_ME is generated when TAMORT is processed. It contains the lines of the calculated amortization schedule for the loan.

Session1 rules

Session1 Rules Name Description
Transformation-Rules RT001 Takes the Nominal amount of the Loan release (transformation of NOMINAL into ACC) into account to provide General Ledger entries.
  RT002 Takes the Fees amount types (transformation of FEES into ACC) into account to provide General Ledger entries.
  RT003

Multi sessions: Transforms NOMINAL into NOM and provides the Input-Events for the next session.

Enrichment-Rules RM001 NOMINAL Segment enrichment : Calculates the variables for RT001 and updates the REL_DATE value in the Input-Events.
  RM002 FEES Segment enrichment : Calculates the variables for RT002 and updates the REL_DATE and FEES_DATE values in the Input-Events.
Aggregation-Rules AGR_FEES Aggregates the FEES Input-Events.
  AGR_ACC Aggregates the ACC generated Output-Events.
Audit-Rules NOMINAL Displays audit trace information for NOMINAL segment in the RELEASE Input-Event.
  FEES Displays audit trace information for FEES segment in the RELEASE Input-Event.
  NOM_ME Displays audit trace information for NOM_ME generated Output-Event.
  ACC_ME Displays audit trace information for ACC_ME generated Output-Event.

Session2 rules

Session2 Rules Name Description
Transformation-Rules RT004

Calculates the amortization schedule (takes TAMORT Input -Event into account) to provide TAM_ME Output-Events.

Audit-Rules TAMORT Displays audit trace information for TAMORT Input-Event.
  TAM_ME

Displays audit trace information for TAM_ME generated Output-Event.

Creat the AI Enabler configuration

Create the configuration for the sample

To create the initial folder and the configuration for the sample in the AI Enabler:

  1. Open the Integration Services workbench.
  2. Import the composer.xml from the getStarted/configuration directory with the update the folder hierarchy option.
  3. Make a recursive check on all Input-Events.
    You can use the Entity Browser’ (F7) to validate the objects. All objects in the folder must be in ‘Checked’ status.

Configure the Rule Engine

Get the delivered configuration from the sample – Copy the mvt.mvt, ctx.mvt, script.fic files from the getStarted/configuration directory to your %RuleEngine_runtime_path%/dat directory

Configure the Rule Engine:

  • Clean the configuration : launch %RuleEngine_runtime_path%/script/rdjraz
  • Deploy the sample configuration : %RuleEngine_runtime_path%/script/rdjdep

Execute the Rule Engine session

Get the delivered data from the sample:

  • Copy the IEvent.seq file from the getStarted/data directory to your Rule Engine %RuleEngine_runtime_path%/dat directory
  • Copy the predefined session launcher ais_finance1.bat from the getStarted/script directory to your Rule Engine %RuleEngine_runtime_path%/script directory

Execute the accounting transformation:

  • Launch the %RuleEngine_runtime_path%/script/ais_finance1.bat
  • You can find the reports in the %RuleEngine_runtime_path%/edi directory
  • You can find the results in the %RuleEngine_runtime_path%/bres directory :
    • OSegt****.seq are the generated Output Events
    • ap.****_Trace are the generated audit traces
    • ap.cra are the Input Events to be recycled
  • Related Links