!--a11y-->
Tools (FS-BA-TO) 
You can use this component to call functions that are used in various places in Customizing for Bank Analyzer.
In addition, the following tools are available:
The derivation tool enables you to control how the system derives characteristics and key figures from other characteristics and key figures, and how it derives the fixed fields of a field catalog. In Bank Analyzer the system calls derivations from the coding or by using a secondary data source. You can create this secondary data source with the module editor in Customizing for Bank Analyzer.
You can state the derivation environment for deriving the validity of a hedging relationship, for example, in Customizing for Bank Analyzer by choosing Processes and Methods ® Hedge Processes ® Portfolio Fair Value Hedge ® Configuration ® Derivation of Validity. You use this derivation process in the secondary data source in order to use the characteristics of a transaction to derive whether the transaction is one of the qualified positions or unqualified positions in hedge accounting.
The module editor generates modules that contain a sequence of processing steps. The modules are used to enrich user-defined information and provide the system with secondary data sources.
An application makes entries into the fields of an input structure and calls the module. The system applies each processing step of the module in the sequence defined in Customizing. The system can call function modules, derivations, or primary data sources within the module. The system then makes entries into fields of the output structure.
Modules can
have various functions. The selection module of the
Strategy Analyzer,
for example, selects data using the Primary Data Source processing step. The
calculation module of
Profit Analyzer
carries out complex calculations for the processing steps formula, derivation, and function module.
You can find the settings for the module editor, for example, in Customizing for Bank Analyzer by choosing Bank Analyzer ® Analytics ® Profit Analyzer ® Profit Engine ® Calculation ® Edit Modular Costing.
The
Result Database
(RDB) is a database in which the system saves results data permanently.
Results are then available for further processing, by reporting, for example,
or for additional calculation runs.

The RDB and the
Results Data Layer
(RDL) are two different results databases in which the system can store
results data. Each database is based on different principles. The RDB is found
in a variety of forms in Bank Analyzer. These forms depend on the various
areas (Financial Accounting, Basel II). The RDL is a standardized results data
store for accounting and risk-based analyses of financial transactions or
financial instruments.
For the long-term we recommend that you use the central RDL to store results data in a standardized way. In Customizing for Bank Analyzer you can choose whether the system is to store Basel II-specific results data in the RDB or the RDL.
The
Processing
Framework supplies the processing rules with data from various data source
categories. The calculation and allocation processing rules are available in
Profit Analyzer, for example. The system uses suitable selection conditions to
create a worklist. The system can also add further information using a
secondary data source. The result records generated by the processing rules
are forwarded to the temporary buffer, The system provides verification lists
which you can use to check whether the result records are plausible from a
business perspective. The result records are then updated in data
drains.
You can also start the processing steps manually. In a typical scenario, you include the processing steps in the Schedule Manager which then carries out an automatic month-end processing on the basis of this.
Run administration
provides you with various processing functions for the runs in the individual
Bank Analyzer applications. Run administration therefore enables standard,
general run administration.
The aggregation tool is used to aggregate data from primary and secondary data sources, BAPIs, and the Data Processing Framework. The aggregation type is determined using granularities such as the branch or the business partner. Possible aggregation functions are determining minima, maxima, totals, or the number of occurrences of a certain value.
You can find the settings for aggregation, for example, in Customizing for Bank Analyzer by choosing Analytics ® Historical Database ® General Settings for the Historical Database ® General Settings for Data Selection ® Settings for Aggregation Processes. You can use the Aggregation Business Add-In (BAdI) to override the results from the aggregation process you defined in the IMG activity Edit Aggregation. This enables you to change individual results.
The Data
Processing Framework provides selection processes for processing data to the
Historical
Database, the
Limit Manager and
Bank Analyzer-wide to
generic BI data
extraction and
generic ad hoc
reporting For example, you determine the selection settings in Customizing
for the -Historical Database in the Edit
Basic Settings for Data Sources section. Every selection is assigned to a
fixed context (application of the Data Processing Framework) which is, in
turn, assigned to a certain application of the module editor. Data processing
that is either triggered by a report or by generic data extraction, for
example, can contain both selection BAdIs as well as aggregations and general
selection criteria.
The
configurator reads characteristics and key figures and generates
customer-specific database tables and field structures for further processing.
The system calls these processes "generation". The system currently uses only
both Bank Analyzer accounting
scenarios for generation. For more information, see the documentation about
Generation.
