SAP Bank Analyzer – implementation

SAP Bank Analyzer Implementation Strategy -High Level Implementation / Overview

 SAP Bank Analyzer –

This article will explain best approach and Implementation approach for the SAP Bank Analyzer solutions, upgrade or integration. Recently I've had opportunity to work on two demo solutions for a banking system SAP Bank analyzer implementation within risk and profit analyses team and a short term test strategy development for rapid SAP bank analyzer implementation within an investment bank.

This article will explain best approach to implement SAP Bank Analyzer solution 8.0 or  upgrade from or integration. Recently we worked on two demo solutions for a banking risk system SAP Bank analyzer implementation within risk and profit analyses team and a short term test strategy development for rapid SAP bank analyzer implementation within an investment bank.

In next couple of blogs we will detail an effective way to test SAP Bank analyzer and its individual components.

 - SAP BA - Objectives in upgrade and in new Implementation

                 Business Architecture      

                Test Approach

There could be two scenarios either – Accounting IFRS implementation or risk architecture – see below diagram for both .. 

A)  Accounting IFRS implementation (accounting consequence, SGL scenarios)

B) Risk architecture

Lets review each of the element in the diagram
See SAP SDN for SDS -

 First later is SD component to load original data from other operational systems or source systems into the Source Data Layer (SDL) by means of an extraction, transformation, and loading process (ETL process).  The SDL saves, consolidates, and manages the original data. At the same time it provides interfaces to additional operational systems.

The primary objects of the Source Data Layer (SDL) and their scenario versions are a flexible way of saving master data, flow data, and market data. They also group this data into units that belong together logically from a business perspective. This ensures that the Bank Analyzer components that are linked to the SDL have a standard, consistent data source.

In addition to storing primary object data, the SDL provides the following primary objects functions for applications linked to it:

●     Access to source data

●     General functions for source data layer

●     Methods for source data

●     General access to corrections

●     Tools

Integration

The SDL provides both the central original data basis and a part of the underlying infrastructure for linked applications. It is therefore a key element in ensuring the consistency of data and results.

<To be updated soon) - if you need detail document, please email your request

Category 1 - business transactions

• Post external business transactions
• Update secondary business Transactions

Category 2 - date valuation
 

• Key date valuation for all financial positions
• Financial Positions for Period (PICC) event processing etc
• Update costing for period before GL and during transferring GL documents
• Calculation for all PICC

Category 3 – SAP GL Postings

• GL Connector and document generation – Journal and document review and finance reconciliation of the GL, Profit centre and any material code posting review
• Balance processing step 1 - (SV)
• Balance processing step 2 - (ATP)

Testing of the accounting for FI with Aggregation (AFI) for Accounts Results before RDL and GL

Category 1 – position management

• Generate Finance Instruments position
• Aggregate Financial Transactions
• Prepare Business Transactions for Aggregation
• Process Reassignments for Business Transactions
• Aggregate Business Transactions
• Aggregate Current Accrual Results
• Process Reassignments for Accrual results
• Aggregate Retroactive
• Accrual Results
• Derive Application Events for source data aggregation

Imported Sub-Ledger Documents (ISD) for Results

 ISD sub-ledger import