Anda di halaman 1dari 8

Manually Restoring Lost Delta Data from ECC.

Applies to:

SAP NetWeaver BW 3.x and 7.0 For more information, visit the Business Intelligence homepage

Summary
We are here simulating the scenario where this delta data queues / entries gets corrupted or deleted and
contemplating the possibility of recovering this lost data manually.

Author: Jitu Krishna


Company: IBM India Pvt Ltd.
Created on: 1 April 2010

Author Bio
Currently working with IBM India as a Sr. SAP BI Consultant. Has more than 5 years of SAP BI Consulting
experience. Started career with Satyam and was fortunate enough to be a part of SAP operations, BW to be
precise. Has a considerable amount of exposure in Development, Enhancement, Performance tuning, and
Application management support in SAP BI space and is an SAP Certified
SAP NetWeaver 2004s Business Intelligence (BI 7.0) Solution Consultant.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 1
Manually Restoring Lost Delta Data from ECC.

Table of Contents
Introduction..................................................................................................................................... 3
Resolution . 3
Wave 1 (Delta data) reloads... 4
Wave 2 (Full Loads) reloads.. 5
Data Validation.. 5
Additional Information. 5
Related Content. 6
Copyright

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 2
Manually Restoring Lost Delta Data from ECC.

Manually Restoring Lost Delta from ECC.

The Success of any BW Implementation is measured primarily by the availability of Right Data at the Right
time for reporting. This data is essentially the base on which informed decisions can be taken by
Leadership. The major quantum of this data is the Current or Daily delta data. This is normally provided by
Delta capable DS to BW. In most cases this comes thru R/3 RSA7 which captures Delta data as well as
Repeat Delta data.

We are here simulating the scenario where this delta data entry gets corrupted or deleted and
contemplating the possibility of recovering this lost data manually.

This delta corruption can happen due to Improper Upgrade / Patch application / Add-on installation
practices, incorrect transports or due to human mistake.

Resolution

This first step is to identify the DS / Application areas / Queues / TCodes which have been affected. This
may be found out from RSA7 / LBWQ / SMQ1 / SLG1 / SM21 / Other logs etc and with the help of System
admin.

Once the issue is identified as deletion of Delta data from Delta Queue (RSA7) and SMQ1 (QRFC
Monitor/Outbound Queue) the priority is given to find the delta data that got deleted.

Further analysis reveals that the Delta queue deletion may only have impacted DS that functions based on
Push Mechanism (LO) and where delta data comes through RSA7 Delta queue. DS based on Pull Mechanism
(Generic, FI, COPA) may not get affected as delta queue for those stores Repeat delta information alone
and not delta. This necessitated immediate action to recover data for DS with Push mechanism.

First step is to identify the affected DS for which the delta needs to be restored. This information was
gathered by collecting data from multiple sources like RSA7, Data flow in Daily Batch Network, Process
chains, Design documents, TO, system logs etc.

The second task was to identify the delta data for these DS. As delta contains any newly created or any
changed records the foremost importance was to find these records.

For this we undertook multiple approaches. The starting point is finding out the application / base tables
from which these DS are being populated and the timestamp / date or similar fields which can be
effectively utilized to determine the deltas.

This can be finalized after consulting SAP documents / Consulting Techno-Functional Consultants. Each DS,
the related application tables / base tables, possible time stamp fields (created on / changed on etc) need
to be categorized.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 3
Manually Restoring Lost Delta Data from ECC.

Wave 1 (Delta data) reloads.

From Application / Base tables

Newly created records can be identified using Date/Timestamp fields available in the application tables.
Application tables for each application tables have created date / Changed date fields. This gave a relatively
complete set of records that were newly created records and any old that records that got changed during
this period.

CDHDR and CDPOS

Another approach was to identify the changed records from R/3 tables CDHDR and CDPOS. We need to
have the object class for each application to fetch the information from CDHDR and CDPOS tables. The
object class for each application can be identified from TCode SCDO / Table TCDOB, TCDRP, TCDRS in ECC
and the records fetched from the above mentioned tables. This is better done with the assistance a
functional expert. It may not be very easy to retrieve this information from ECC base tables without the
help of an ECC Consultant.

A list of all those records created / changed can be compiled through the above mentioned steps. The
record numbers should be tallied with the load history of each of these Datasource to confirm that the data
volume is matching approximately.

Once the entire missing delta data is identified the next priority is identified as extracting the same from
R/3. As these were LO Datasources this will necessitate filling up of setup tables for these applications with
these records and pulling them into BW.

This was done for all the LO Datasources.

Examples of Application area and related base tables.

Application List of base tables


Purchasing EKKO, EKPO
Manufacturing CAUFV, AUFK, AFRU, AUFM, AFKO, AFPO
QM QALS, QMEL, QAVE
Billing VBRK,VBRP
PM AFIH, QMEL

More information on this can be found from SAP documentation.

Examples of Applications and related object class from SCDO.

Application Object class


Sales Order VERKBELEG
Billing Document FAKTBELEG
Delivery LIEFERUNG
Purchasing EINKBELEG

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 4
Manually Restoring Lost Delta Data from ECC.

Wave 2 (Full Loads) reloads.

The third step was to perform full / Repair Full loads for a minimum credible period.

The first set of reloads (Wave 1 for delta data alone) is to be followed by Wave 2 full / Repair Full Reloads.
This can be done over an extended period of time as this is more time consuming given the considerable
increase in data volume for each application. From a practical perspective this full reloads may be only be
necessary for critical applications and applications where data volume is considerable lesser.

During Wave 2 Reloads we need to perform full data reload for affected applications from R/3. This should
ensure that all the data in R/3 has been loaded into BW and there are fewer chances of data integrity issue
in the future and to load any delta that could have been missed out during Wave 1 delta load.

Data Validation

Data Validation was done by primarily done checking the data in the reports and also by Interacting with
Business. Secondary data validation can be done by comparing ECC and BI data randomly.

Additional Information

ECC Tables

Object class - Application

TCDOB / TCDRP / TCDRS

Change documents

CDHDR Change document header

CDHDRDISP Change document header display structure

CDHDRH Change Document Header Per Point in Time

CDHDR_ALV Change Document Header Shipment

CDHDR_OLD Change document header

CDPOS Change document items

CDPOS_OLD Change document items

CDRED Change documents, display structure

CDREDDISP Change document display structure

CDTXT Change documents: Text changes

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 5
Manually Restoring Lost Delta Data from ECC.

TCodes / Programs

SCDO CHDO AENDBELEG => Gen. by RSSCD000

AENDBELEG_WRITE_DOCUMENT CHDO AENDBELEG => Gen. by RSSCD000

Other resources
Documents: How to track changes through ABAP?

https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/6054

http://help.sap.com/saphelp_nw04/helpdata/en/2a/fa015b493111d182b70000e829fbfe/frameset.htm

http://wiki.sdn.sap.com/wiki/display/ABAP/Change+Document

http://wiki.sdn.sap.com/wiki/display/Snippets/Steps+to+enable+logging+of+changes+in+change+documen
ts

A Safety Belt for Logistics Extraction Queues

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5316

How to Data Recovery In SAP BW Systems (NW2004)

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/001ef297-9bbf-2910-bbaa-
babedc1b01ca

Note 1008250 - Backup table for the queues of logistics extraction into BI
Note 422173 - Information: BW/CO-PA upload data inconsistency correction
Note 731682 - Backup in BW and OLTP: Experiences, risks & recommendations
Note 860500 - BW-BCT-FI: Repeating delta extractions
Note 739863 - Repairing data in BW
General notes on data reconciliation:
Repair Request Functionality (How to Use the Repair Request): 739863
How to Reload Delta Data Without New Init (Workaround): 691721
Down Time Reducing in LO-LIS: 753654
Multiple BI Systems Are Getting Data from One OLTP- Problems with Delta: 775568
Backup in BI and OLTP: Risks & Tips: 731682
Extraction from Archives: DataSources / Applications / Workaround if the Functionality Is Not Available:
643541
Wrong Results with STAR_TRANSFORMATION_ENABLED=TRUE : 717496
Wrong Results with ODS or Non-Star Transformation Queries: 727310
Notes for the data reconciliation in specific content area:
FI: Reconciliation Items : 616331, 616918
FI: Reload Wrong or Missing Documents: 616331
FI: How to Involve Documents Which Did Not Have Been Updated in the System into Delta Load: 651227
FI: Recommendations to the Delta Modeling in FI Content Area: 656687
FS-TB : Comparison Report Payment Item Content 0TB*: 757008
MM-PUR: Number of Deliveries for Goods Receipt: 381267

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 6
Manually Restoring Lost Delta Data from ECC.

CO-OM: Elimination of Internal Business Volume: 590812


CO: Customer Uses ODS Object with Totals Record: 448693
CO: Safety Time Interval for CO DataSource is Too Small: 553561 and 416265.
LO Cockpit: Changes to Extract Structures in Customizing Cockpit: 328181

Note

The same method can be also employed during ECC BI Reconciliation or to identify missing deltas and
perform Full repair loads to BI.

OSS Note 1008250 mentions about an automated approach. It would be useful if we explore the
possibility mentioned in this note before trying the manual approach or along with this.

This methodology deals with an unexpected and unwelcome scenario. So my advice would be to try this
only when you have a genuine requirement. It may not be a good idea to try this out in a live system just
for educational or learning purposes.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 7
Manually Restoring Lost Delta Data from ECC.

Copyright
Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

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

Anda mungkin juga menyukai