XBRLmapper

XBRLmapper WIKI

Product page

[XBRL Mapper product page]

Main window

XBRL Mapper tool main window

Tool icon

XBRL Mapper tool icon

Descripcion

XBRLmapper is a sofisticated tool that transfers data from information systems to XBRL reports and from XBRL reports to other systems. It supports then two different purposes:

1. Automatic generation of XBRL reports from different data sources
2. Automatic extraction of data from XBRL reports and data loading into different repositories

Both products share a similar architecture. Both are based on a common definition of data events connected with the XBRL side and specific drivers that attend the data events. Both sides (definition of events, and driver) can be configured using XML files. This architecture has multiple advantages:

1. Isolates the complexity of the XBRL Technology in one part (the data events). If the taxonomy changes the user may need to change just the connection between the events and the taxonomy or instance templates
2. Isolates the complexity of the internal data repositories each one of the repositories may be accessed by an intantiation of a specific driver
3. Each driver has his own configuration file that is specific for the data repository it is specialized
4. The generation of an XBRL report may involve several drivers looking at data in different repositores simultaneously
5. The same event could be potentially attended by more than one driver
6. Multiple drivers of the same repository type can be used concurrently

The XBRL mapper is a software component that can be launched from a GUI or can be integrated in a workflow. The integration requires development of code (in Java or .NET)

Generating XBRL (Mapper)

Generating XBRL reports is one of the operations for which the mapper was conceived. In this documentation Mapping is the process of obtaining data from data repositories in order to create an XBRL report.

The XBRL Mapper product designed by Reporting Standard S.L. is adapted to work in the most complex scenarios. The XBRL Mapper is robuts, powerful and flexible.

• Robust because it is based on a native XBRL API that supports 100% Conformance level with XBRL Validation
• Powerful because it is based on an architecture that allows the users to plug-in drivers prepared to read different data sources and prepare combinations of data sources attending "mapping events".
• Flexible because it allows users to easily migrate to new taxonomies by just changing the instance document template but maintaining the same "mapping event" names and driver configurations. Or to adapt the system to obtain data from different data sources while using the same target taxonomy.

The configuration of the mapping engine requires then two steps:

1. Preparing an instance document template and the definition of "mapping events"
2. Preparing the configuration file for the driver(s) attending "mapping events"

The instance document template

The instance document template is the configuration file where the "mapping events" are defined. As the name suggest, the instance document template resembles an XBRL report but it is parameterized in order to turn each one of the facts in a report into a "mapping event". It is important to notice that while the instance document template may have just one fact for a concept definition in the taxonomy, the response from drivers about requesting data for one mapping event may be multiple facts and, if this is the case, the final output file will have multiple facts as a result of multiple data items for the same mapping event.

The creation of an initial instance document template is a straingt forward process that can be initiated from two different sources, the file can be adapted to cover more complex mapping scenarios later.

From a DTS (A set of Taxonomies and Linkbases)

In this case, the instance document template will be generated according to all concept definitions that exists in the DTS (all taxonomy schemas providing item and tuple definitions for the DTS). If the purpose of the instance document template is just the concepts in a specific presentation hierarchy it would be more interesting prepating a sample instance document and convert the sample report into an instance document template (See the next section).

So, the creation of an instance document template from a complete DTS may generate a template with lots of events. The user should use this option if he is absolutelly sure this is the way to go.

Steps to produce the initial template file:

1. Open Loader Editor tool
2. In the "Mapper" menu, select the "New Template from DTS" option
3. In the Compose DTS dialog, select the required files
4. In the Parameters for the mapper configuration file dialog make sure you specify a template file name and also one initial data source (more data sources will be added later).

Navigate

Main Page