Data Reload for Standard

Banking framework BW Datasource

Applies to:

SAP BI 2004s or SAP BI 7.x. For more information, visit the Business Intelligence homepage.

Summary

This document explains the procedure to perform repair load from SAP core banking to SAP BW for Banking framework Datasource

Author: Manasij Biswas Company: Accenture Created on: 15th October2015

Author Bio:

Manasij Biswas, working in Accenture, has an experience of more than 3.5 years in SAP BI ABAP. He has been a part of Production Support, Development and Implementation Projects. Have knowledge in Banking Source systems.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

Table of Contents

Data source..................................................................................................................................................... 3

Difference in banking datasource....................................................................................................................3

Backend tables for Data extraction of datasource............................................................................................3

Procedure to Reload Missing Data …............................................................................................................. 4

Related Content……………..…....................................................................................................................... 7

Disclaimer and Liability Notice ..........................................................................................................................7

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

Datasource?

A DataSource is a set of fields that provide the data for a business unit for data transfer into the BW. From a technical perspective, the DataSource is a set of logically-related fields that are provided to transfer data into the BW in a flat structure (the extraction structure) or in multiple flat structures (for hierarchies).

There are four types of DataSource:

 DataSource for transaction data

 DataSource for master data

 DataSource for attributes

 DataSource for texts

 DataSource for hierarchies.

Difference in Banking datasource and Traditional BW datasource

Most of the standard extractor does not use any of the usual procedures for delta update, but uses an application-specific delta mechanism. Backend tables of Data extraction for BW datasource In this Document 0TB_PAYMITEM_E_TRAN datasource has been discussed. The extractor extracts details from table BCA_PAYMITEM: Using the append technique you can add fields of this table that are not contained in the extract structure. Only those payment items that were released between the time of the last extraction and the current extraction are selected. (The extraction times are recorded in table BCA_BCT_UPD_MGMT and are used for determining the volumes of data to be extracted). In addition, data records (payment items) from periods before the extraction that have been reversed or returned in the meantime are also selected. TIMESTAMP_RELEAS of BCA_PAYMITEM field is being used by extractor to determine what are the records to be fetched in next run. We need to consider TIMESTAMP_CHANGE field of BCA_PAYITEM also as , data records (payment items) from periods before the extraction that have been reversed or returned in the selected timeline in the datasource are also selected as part of data load. Extraction time, Request number of all banking datasource for history data load and current data load has been stored in BCA_BCT_UPD_MGMT.

.

BCA_BCT_UPD_PARA table TSTAMPHI will store from which timestamp next data load will fetch data as part of daily load.

To load missing data records we need to manually maintain BCA_BCT_UPD_PARA table TSTAMPHI value. Below point we will discuss about repair load from banking to BW.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

Procedure to Reload Missing Data

Issue:-

Data records have been missed due to unknown reason. Need to reload data from banking to BW.

Solution

To repeat the extraction, proceed as follows:

1. Determine the time interval in which the data is missing.

Example:

Below ITEM_ID have been missing from BW.

 005056AB0ADE1ED4ABAA08D*********

 005056AB0ADE1ED4ABAA2677*********51

 005056AB0ADE1ED4ABAA08D*********4E

 005056AB0ADE1ED*********1E894DB9D29

 005056AB3B*********BAA30C21FCD9B6E

 005056AB3BE71EE4ABAA30C21F*********

Need to search these IDs in the base table BCA_PAYMITEM as we are discussing about 0TB_PAYMITEM_E_TRAN data source.

Determine the TIMESTAMP_RELEAS range from BCA_PAYMENT table to reload the data, need to consider TIMESTAMP_CHANGE also.

Take TIMESTAMP_RELEASE range from table.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

Example:-

Here TIMESTAMP_RELEASE range is 20,150,205,145,211.50 to 20,150,205,161,334.00 .

2. In the BCA_BCT_UPD_MGMT table, select the entries for the relevant DataSource. Check NOF_INTERVALS already available in this table for the relevant DataSource.

Example: NOF_INTERVALS = {50,20,10} already exist for the 0TB_PAYMITEM_E_TRAN DataSource.

3. Select a NOF_INTERVALS that does not yet exist.

Example: NOF_INTERVALS = 1 --> Need to create 1 record. If we select NOF_INTERVAL  2 we need to create 2 entries.

4. Note the following when creating new data records:

OLTPSOURCE = DataSource name

NOF_INTERVALS = Number of intervals

INTERVALNR = From 1 to NOF_INTERVALS

CHANGE_TSTAMP = Any

TSTAMP_LOW = Any TSTAMP_HIGH = The lower limit of the time interval that you selected

UPDMODE = C

LAST_TS = 'X'

One entry created in the example:

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

5. Higher Limit has to be maintained in the BCA_BCT_UPD_PARA in TSTAMPHI for respective Datasource.

From TSTAMP_HIGH of BCA_BCT_UPD_MGMT to TSTAMPHI of BCA_BCT_UPD_PARA data will be extracted from the base table.

6. In BW, create several "NOF_INTERVALS-" InfoPackages for the corresponding InfoSource.

Here we have "NOF_INTERVALS-" = 1 , so only one infopackage has to be created. Please find below selection of info package.

7. Perform the extraction.

8. Set the TSTAMPHI parameter of the BCA_BCT_UPD_PARA table to its original value.

9. Validate with Banking Base table and BW data. TIMESTAMP_CHANGE field of BCA_PAYITEM also need to be considered as data records (payment items) from periods before the extraction that have been reversed or returned in the selected timeline in the datasource are also selected as part of data load.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

Related Content

For more information, check SAP Note 678506 - TRBK 2.0; Loading missing data into BW

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

A complete vision on SAP Financial Services Network (SAP FSN)

For those of you willing to understand more on the SAP FSN story, value drivers, solution scope and vision, kindly take a look at this presentation: SAP Financial Services Overview

SAP Financial Services Network Overview

This document provides an overview of SAP Financial Services Network values, foundational services and Value Added Services.

Understanding the basic SAP FSN Payment Flow - an End-to-End Demo

The basic foundational services of SAP FSN are based on SAP ERP Financials integration:
•Accounts Payable:◦Outgoing Payments
◦Payment Status Messages (Optional)

•Accounts Receivable◦Collection Data

•Electronic Bank Statement (Treasury, AP and AR)

Videos for SAP for Banking

This document features selected promotional videos and learning videos about specific tasks across the banking areas. The intention is to give users a quick overview about the new features and a quick start on selected user interaction topics in banking processing. For more information, see also Benefit from New Videos on Selected SAP for Banking Topics.

Banks around the world are flocking to digital tools and new technologies both to meet higher customer expectations and to respond more quickly to their changing environments. One of the most beneficial technology adoptions has been the move to cloud-based technology platforms and financial applications.

More than half of banks worldwide (60 percent) will process the majority of their transactions in the cloud as early as this year, according to Gartner.This includes daily bank transactions, account updates and deposits, as well as loan- and credit-processing capabilities.

So financial institutions should act fast if they don’t want to be left behind.

Reduce Operational Costs While Boosting Innovation

More than 93 percent of financial service executives believe cloud solutions will transform their organization, according to a recent SAP benchmark survey. By moving core banking systems to the cloud, financial institutions are able to re-focus their resources to better understand and serve customers, rather than maintaining 30-year-old technology or managing difficult integrations to legacy systems.

A single, integrated, cloud-based system allows financial institutions to build a window into their operational, process and customer information – getting a real-time, 360-degree view of customer activity, and eliminating the complexity of the multistep process for customers to gain a comprehensive view of their accounts. This is a singular system that consolidates critical data, enabling straight-through processing from account opening to transactions and balances for customers.

Another benefit of moving core banking systems to the cloud is the ability to reduce system maintenance costs, which lowers legacy technology worries. This allows banks to re-focus budgets on innovation, customer satisfaction and growing the business.

For example, the Bank of New York Mellon has been using a private cloud for the past three years. It has improved the bank’s ability to innovate; nearly doubled the density on servers compared to virtualization alone; reduced data center power consumption; and largely eliminated manual patching, according to Dr. Swamy Kocherlakota, managing director, global head infrastructure architecture and engineering.

Connect ERP, CRM and More – All in Real Time

Breaking away from legacy systems and into the cloud liberates banks from the constraints of outdated technology, a move that can open up a world of data. By consolidating, analyzing and leveraging this data, banks can then provide the relevant information and instant access that customers demand. 

For example, when making a banking transaction, customers want to see the result of their actions immediately to ensure accuracy and security.

Moving applications and platforms to the cloud also enables banks to provide a consistent, digital experience across all customer-facing channels – mobile apps, Web site, social media and phone – helping improve experiences for consumer bank customers. Instead of attempting to upgrade and integrate legacy systems to support new functions like mobile banking, a solution such as SAP Cloud for Customer offers a fully complete, robust solution with prepackaged integrations to ERP, CRM, mobile platforms and social connectors that can help banks stay on top of the latest customer demands.

Connecting ERP systems to the cloud also allows banks to provide a full range of commercial services – including payments and related services without the need for custom interfaces for each corporate client. Additionally a best-of-breed cloud suite can cover all lines of the financial business with end-to-end integration, innovations in human capital management, procurement, sales and social collaboration. By covering all lines of business, companies are better able to provide a customer-centric experience across digital channels, manage regulatory reporting and risk, drive efficiency and be more flexible to adapt as market needs evolve.

For example, international insurance group Ageas recently adopted the industry’s first end-to-end enterprise insurance software in the cloud, deployed on SAP HANA Enterprise Cloud. The company now has a centralized platform for policy administration, quotation, underwriting, claims, commissions, collections and disbursements, as well as finance, procurement, HR and enterprise analytics. This integrated set of solutions gives Ageas full visibility into operations and supports the agility it needs to help establish and penetrate new markets.

Be Flexible and Fast!

The flexibility doesn’t stop there. Applications outside of core banking, leveraged by financial institutions, can also benefit from cloud-based solutions. Companies moving human resource functions to the cloud can manage the entire workforce much more easily due to the consolidation of data and systems. This includes everything from initial recruiting and onboarding to ongoing development, performance management, retention and retirement.

The world of banking isn’t slowing down. For financial institutions to stay ahead of the pack, they must be ready to take on new challenges. This means moving the majority of core banking – daily bank transactions, account updates, deposits, and loan- and credit-processing capabilities – to the cloud. Financial institutions don’t just need to embrace cloud solutions: They need to do it now.

This page provides promotional videos and videos demonstrating how to use selected functions of SAP for Banking.