Lo extraction part 8 %3a support issues

LO Extraction – Part 8
Post Implementation and Support
Issues

Applies to:
SAP BI, NW2004s Business Intelligence, ABAP, BI, For more information, visit the ABAP homepage.

Summary
This article explains about very few post implementation and support issues involved LO extraction. I have
included some standard support issues which can be solved by the possible SAP notes. It is highly
impossible to elaborate on each topic of the support issues, so many support issues are not discussed here,
and if possible I can include those in the later versions of this article.

Author : P. Renjith Kumar
Company : SAP Labs India
Created on : 26 Nov 2010

Author Bio
P Renjith Kumar is presently working in SAP Labs India Pvt Ltd and specializes in
Extraction and Modeling areas of BI. Basically as an ABAP consultant, he has extensive
cross functional experience and has been with end to end SAP ERP and BI
implementation projects across manufacturing domain.

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

LO Extraction – Part 8 Post Implementation and Support Issues

Table of Contents
Prerequisite ......................................................................................................................................................... 3
1. Data not transferred from LBWQ to RSA7 ..................................................................................................... 3
2.Useful reports in LO extraction ........................................................................................................................ 3
3.LO Extraction ( Delta) Information on upgrade ................................................................................................ 3
4.No data in RSA7 .............................................................................................................................................. 4
5.Performance tuning ......................................................................................................................................... 4
6.Master Data Delta ............................................................................................................................................ 4
7.Delta queue general questions ........................................................................................................................ 4
8.Data missing in extraction................................................................................................................................ 4
9.Analyze the update of document data ............................................................................................................. 4
10.ROIDOCPRMS and package size ................................................................................................................. 5
11.Reports for delta queue ................................................................................................................................. 5
12. TRFC Transaction Recorded in Transaction SM58. .................................................................................... 6
13.Extraction Important Tables ........................................................................................................................... 6
14. 2LIS_02_SRV datasource not in LBWE ....................................................................................................... 7
15.Performance in LIS-BW-VB_APPLICATION* Job Collective run performance ............................................ 7
Related Content .................................................................................................................................................. 9
Copyright........................................................................................................................................................... 10

© 2010 SAP AG 2


Prerequisite
Once you are done with the all seven parts of the article mentioned at the end of this article this will help you.

1. Data not transferred from LBWQ to RSA7
Run the report RMBWV3* ,
Here * denotes application component. Eg: RMBWV311 for application component 11.

2.Useful reports in LO extraction
RSTRFCK0 Consistency Check of tRFC/qRFC LUWs (Outbound Queues)
RSTRFCK1 Consistency Check of tRFC LUW
RSTRFCK2 Consistency Check of All tRFC LUWs
RSTRFCK3 Consistency Check of qRFC LUW (Outbound Queue)
RSTRFCK4 Consistency Check of All qRFC LUWs (Outbound Queue)
RSTRFCK5 Consistency Check of qRFC LUW (Inbound Queue)
RSTRFCK6 Consistency Check of All qRFC LUWs (Inbound Queue)
RSTRFCDP Display Data of qRFC LUW (Outbound Queue)
RSTRFCDQ Display Data of qRFC LUW (Inbound Queue)
RSTRFCEF Consistency Check: ARFCSSTATE< QREFTID< >ARFCSDATA >ARFCS
RSTRFCEG Consistency Check for Outbound Queues
RSTRFCEH Consistency Check for Inbound Queues
RSTRFCEJ Deletion of TRFCQSTATE, TRFCQDATA, TRFCQIN (Internal Use)
RSTRFCEK Consistency Check: TRFQIN< > TRFCQSTATE< >TRFCQDATA
RSTRFCEL Consistency Check: TRFCQOUT< > ARFCSSTATE >QREFTID
RSTRFCG0 qRFC Tools: MENU Display

3.LO Extraction ( Delta) Information on upgrade
Before the upgrade (import of a queue), all extraction queues and open update orders in all clients must be
processed. The content of the setup tables must be deleted. To avoid this problem during the upgrade or to
correct it, carry out the following steps:
1. Call transaction SMQ1 and check whether all queues in all clients (client = '*', queue name 'MCEX*') have
been processed. To process the queues, start the collective run report for each application in the displayed
clients. If you no longer need the data in the BW system, deactivate the relevant extraction queues and
DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in transaction SMQ1.
2. If you use the V3 update that is not serialized (usually only for application 03): Start collective run report
RMBWV303. Then check the update orders in transaction SM13. If there are incorrect update orders in
transaction SM13, correct the orders and then start the collective run report again. If you no longer require
the update orders, you can delete them. There may be inconsistencies between tables VBMOD and VBHDR.
For further information about this, see Notes 652310 and 67014.
3. Before the upgrade, delete the contents of the setup tables. Execute report RMCEX_SETUP_ENTRIES to
find out which setup tables still contain entries. You can use transaction LBWG to delete the contents of the
setup tables for all clients.
Unfortunately the check that the system carries out during the upgrade or when you import a Support
Package does not display all affected applications. Therefore, Note 1083709 provides a check report that
you can use to determine all affected applications and tables or queues.

© 2010 SAP AG 3


For More detailed information please check these following notes:
1083709-Error when you import Support Packages
1081287-Data extraction orders block the upgrade process

4.No data in RSA7
You need to initialise delta for desired datasources .
Check the attached notes below:
728687 Delta queued: No data in RSA7
505700 LBWE: New update methods as of PI 2002.1
Do check the given note below that will tell how to reconstruct the data for BW:
602260 Procedure for reconstructing data for BW

5.Performance tuning
Check these notes
417307 Extractor package size: Collective note for applications
409641 Examples of packet size dependency on ROIDOCPRMS
892513 Consulting: Performance: Loading data, no of pkg, req size
561880 Requests hang because IDocs are not processed

6.Master Data Delta
Master DataSource uses ALE change-pointeres
table: ROMDDELTA
TBD62 - shows which fields are relevant for change documents
BDCPV - shows message type and table for which change pointers are used
TBDA2 - shows the message type, and whether it is active
ROOSGEN - shows message type for the dataSource
Check this note for more info.
141436 BW master data delta: additional information

7.Delta queue general questions
Check this note
380078 - FAQ: BW delta queue (RSA7): Questions and answers
Check this blog
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/8173

8.Data missing in extraction
Check note 602260 Procedure for reconstructing data for BW

9.Analyze the update of document data
You can use the report RMCEX000 after you save a document to check which data has been updated to the
extraction queues.
o Set the parameter MCL to "X" for your user (Menu: System -> User Profile -> Own Data).

© 2010 SAP AG 4


o Create a new document or change an existing one.
o Call the report RMCEX000 for your user after you save the document.
o You get a list with the extractors that have been updated for the document. When you click in the "Field
name" column, you can see which data has been updated.
The report RMCEX000 allows you to see only the data for the last posting. If you want to log the update
permanently, use the log file as described in Note 874986.

10.ROIDOCPRMS and package size
In every SAP source system, part of the ROIDOCPRMS table controls the data transfer from the source
system to the BW system. The table contains the following information:
- MAXSIZE - Maximum size of a data package in KB
- STATFRQU - Number of packets that are transferred before statistical
information is sent
- MAXLINES - Maximum number of records sent in one data package
- MAXPROCS - Maximum number of dialog work processes for each upload
request used to send the data to the BW system
Recommendation:
To ensure the performance and stability of the upload process, IT IS VERY IMPORTANT that table
ROIDOCPRMS be set up correctly on both the Source system side as well as on the BI side (for DataMart-
related loads). This table contains the control parameters for data transfer.
Alternatively in your R/3 system, go to transaction SBIW -> General settings -> Maintain control parameters
for data transfer.
Although there is no specific recommendation on this setting, standard values are as follows:
statfrqu 10
maxprocs 3
maxsize value between 20,000 to 50,000 (default is 10,000)
maxlines value between 50,000 to 100,000 (default is 100,000)
Extract from SAP note 417307
The general formula for package size is:
Package size = MAXSIZE * 1000 / size of the transfer structure,
but not more than MAXLINES.
You can look up the transfer structure (extract structure) in the table ROOSOURCE in the active version of
the DataSource and determine its size using SE11 (ABAP Dictionary) -> Utilities -> Runtime Object -> Table
Length. The system default values of 10,000 or 100,000 are valid for the MAXSIZE and MAXLINES
parameters (see the F1 help for the corresponding fields in ROIDOCPRMS). You can use the IMG
transaction SBIW (in the OLTP system) "Maintain general settings for extractors" to overwrite these
parameters in the table ROIDOCPRMS on a system-specific basis. You also have the option of overriding
these values in the scheduler (in the target BW system). However, in the scheduler (InfoPackage), you can
only reduce the MAXSIZE. The main advantage of using the scheduler to carry out maintenance is that the
values are InfoSource-specific.

11.Reports for delta queue
Execue the report RSC1_DAIGNOSIS, in order to check the inconsistencies at the delta queue in the source
system.

© 2010 SAP AG 5


Take a detailed look at the note 583086.
Furthermore execute the report RSTRFCEG to find and correct the inconsistencies in the delta queue.For
further information please check the note 779664.

12. TRFC Transaction Recorded in Transaction SM58.
Usually the status "transaction executing/ recorded" will occur in SM58 if there is a resource issue. The note
below provides a solution to process these stuck LUWs.
784414 - Transaction recorded in SM58 in a BW application In this case it is not necessary to delete them.
The alternative is to switch to batch processing of tRFCs. The "Process Immediately" "Transfer
immediately" option should not be used for high volume, noncritical transactions because you will encounter
resource problems such as this. Instead you need to ensure you are using background processing for our
ALE communications.
Configure program RBDAPP01 (inbound) RSEOUT00 (outbound) to run very specifically for the high
volume message types on your system.
Schedule regular runs of report RBDAPP01 RESOUT00 - can be run for IDoc Type andor Partner etc..
You can configure these reports to run every 10 minutes or as often as required. Then change the
processing mode for the IDocs in question if this has not be done.
For inbound:
-> go to transaction WE20 -> Select Partner
Select Inbound Message Type and change the processing method from "Trigger Immediately" to "Trigger by
background program".
For Outbound:
-> go to transaction WE20 -> Select Partner
Select Outbound Message Type and change the processing method from "Transfer IDoc Immedi." to "Collect
IDocs"
What will happen then is that these IDocs will be processed via background runs of report RBDAPP01
RSEOUT00 (using background work processes) in batch mode leaving dialog work processes free for users
and mission-critical processes.
Take note of the following - if you have very large loads this issue can occur. Please read carefully note
892513 Consulting: Performance: Loading data, no of pkg, and notes
142419 and 527481 for current requirements. Make sure these are met.

13.Extraction Important Tables
TRFCQOUT - tRFC Queue Description (Outbound Queue)
TMCEXCFS - LO Data Extraction: Field Status of Communication Structure
It shows which fields are active, which fields are possible to be added into the datasource
and which fields are forbidden.
TMCEXCFZ - LO Data Extraction: Field Status Comm. Strctre (Customer)
Contains the fields added by the customer (not standard) in the datasource.
TMCEXACT - LO Data Extraction: Activate Data Sources/Update
It shows which datasources are active (used on the cockpit – LBWE)
TMCEXEVE - Events/Extract Structures
It contains the related events covered by a datasource. It’s also possible to check the
information on the BW cockpit – LBWE.

© 2010 SAP AG 6


TMCEXPRA - Control Table for LO Extraction-XPRA RMCSBWXP_COM
TMCEXLOG - Logfile Control of Applications
On this table is possible to activate the log information for non direct delta update methods
applications. It’s possible to maintain it using SE16.
TMCEXUPD - Update Control of Applications
It contains the update method (direct, queue delta, v3) defined on the BW cockpit – LBWE.

14. 2LIS_02_SRV datasource not in LBWE
2LIS_02_SRV > New datasource in EHP3, It will not be seen in LBWE.
Issue: No data extracted.
The 2LIS_02_SRV datastructure is new for the EHP3 and there are some steps to activating it. First of all
there is the entry in TMCEXACT.You should add this entry, using something like se11 with create
permission. The entry should be something like:
ESTRUC ISOURCE ISGEN UPDACT ADDHEADER MCAPPUPDA
MC02M_0SRV 2LIS_02_SRV X X 02
TMCEXACT : LO Data Extraction: Activate Data Sources/Update
Also you will need to activate EHP3 switch:
1) Enter the transaction SFW5 , search for business function in ENTERPRISE_BUSINESS_FUNCTIONS-
>LOG_MM_CI_2 ,Check whether dependencies are off.
2) Switches MM_SFWS_SC2 and MM_SFWS_UI_1P2P Check if these are Off.
You need to turn ON both Switches as well as the Business Function.
This will activate the code that fills the structure.

15.Performance in LIS-BW-VB_APPLICATION* Job Collective run performance
Check the notes
407125 Poor performance of Q and TRFC on ORACLE
332677 Rebuilding fragmented indexes
Check the table
TMCEXUPD : LO Data Extraction: Update Control of Applications
You need to maintain the field UPD_HEAD_COUNT effectively
What does that field mean

Maximum Number of Documents for Collective Update

This parameter is used to define how many documents are to be transferred into the BW delta queues in
compressed form in a LUW when the V3 update method has been selected or the use of extraction queues has
been selected.

If this number is not defined for an application, the system normally compresses up to 10,000 documents into a
LUW.

If a Multi Queue Procedure is used in an application, the document data is transferred into various extraction
queues during delta extraction. When starting the collective update, these are processed with parallel processes
and transferred into the BW delta queues. In this case, we recommend that you specify the number of documents
to be compressed into a LUW to be between 1,000 and 5,000. This prevents lock and working memory problems

© 2010 SAP AG 7


How can I maintain that field?
Transaction LBWR Or Report RMBWV3RE
This is normally a reconstruction report, But you can use this
See the below part

Execute , Now it will change the table TMCEXUPD-UPD_HEAD_COUNT Field

© 2010 SAP AG 8


Related Content
LO Extraction Part 1 – SD Overview
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1034bcbe-b459-2d10-2a89-
ecdeb4e53ff1?QuickLink=index&overridelayout=true
LO Extraction Part 2 – Database Update Logic
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/804165a5-c081-2d10-39b4-
af09a680f591?QuickLink=index&overridelayout=true
LO Extraction Part 3 – Extractor Logic
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1094e790-1d93-2d10-17ba-
8b559bf0f75b?QuickLink=index&overridelayout=true
LO Extraction Part 4 – Update Methods
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5039632a-c398-2d10-0aaf-
97167a3de753?QuickLink=index&overridelayout=true
LO Extraction Part 5 – Datasource Overview
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d07aa007-84ab-2d10-46ba-
a5a2679f0d7b?QuickLink=index&overridelayout=true
LO Extraction Part 6 – Implementation Methodology
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0508c20-84c1-2d10-2693-
b27ca55cdc9f?QuickLink=index&overridelayout=true

LO Extraction - Part 7 : Enhancements

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09d5356-d8c4-2d10-8b84-
d24723fc1f0a?QuickLink=index&overridelayout=true

© 2010 SAP AG 9


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.

© 2010 SAP AG 10

Lo extraction part 8 %3a support issues

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (17)

Recently uploaded

Recently uploaded (20)

Lo extraction part 8 %3a support issues