The Enterprise Source System Framework (ESF) is a solution for the financial sector. It provides a framework that makes different data sources such as SQL, Oracle and SAP available to the Microsoft Dynamics Ax financial system.

Annata ESF is a tool that aggregates multiple finance sources into a single access point for Microsoft Dynamics AX.

System description

ESF is a dynamic framework module developed by Annata for managing huge amount of data imports through established pipelines into Dynamics Ax. It is a highly configurable and robust system designed for Enterprise companies that need to handle huge amounts of data into the system and have many company accounts / branch departments.

ESF offers three types of source data imports:

1. Direct database access
2. Delimited file
3. Web Service

• All data, regardless of data type can be inserted into the system.
• ESF has an easy to use interface for setup, monitoring and error handling.
• ESF offers full traceability.
• Notification through e-mail or messaging with multilingual possibility.
• Ledger account distribution between company accounts
• Each source data has its unique process into the system that is easy to define, redefine and validate at a different level for each import.
• Source configurations are defined with set of actions - Configurations are setup of one or many action.
• An example of a source configuration could be configured with three actions; Import Source Data, Validate and Post.
• Configurations can be setup to control where to post the data - Source data can be distributed to many company accounts.
  
  

The process 

ESF is a framework module developed by Annata for managing data imports through established pipelines.  The source data, which can be either a delimited file or a database query, is transferred into a container called Source Origin Data (SOD). Due to the nature of the container, all data regardless of data type can be inserted into the SOD´s own configuration and code class.

When the SOD has been populated, another pipe is utilized which sorts out the SOD container into Source System Synchronized Data (SSD). The SSD is identical throughout all configurations, however, population of individual fields in the SSD may vary depending on the SOD data. 

After the SSD fields are populated another pipeline springs into action, this time to populate a journal in a company set forth by the Configuration of that specific Subsystem and Sub module.  In this pipeline all sorts of validation kick in to ensure that the journal created fulfills the financial requirements and practices upheld by the financial system (Dynamics Ax). Once the journal has been populated it is passed through Interbranch Clearing and then posted.