Check setup tables R/3

When using report rmcex_setup_entries in R/3 one can easily show the contents of all the setup tables in R/3.

Also you have the ability to jump to LBWG transaction to delete contents of setup tables of a particular application.

0FI_*_4 datasource

For the 0FI_*_4 datasource the following tables are being used in R/3 / ECC.

General Ledger

0FI_GL_4 > BSEG/BKPF

Accounts Receivable

0FI_AR_4 > BSIK / BSAK

Accounts Payable

0FI_AP_4 > BSID / BSAD

Taxes

0FI_TX_4 > BSET

If 0FI_GL_4 datasource is used, its timestamp is also leading for the other 0FI_*_4 datasources. Timestamps of the datasources can be found in table BWOM2_TIMEST.

Standardly a delta request on leading datasource 0FI_GL_4 picks up all changes up to the day before if load is started after 02:00 AM of systemtime. There is a safety margin of two hours build in to sustain a certain consistency between R/3 and BW.

More info on extraction logic of these datasources

http://help.sap.com/saphelp_nw70/helpdata/en/af/16533bbb15b762e10000000a114084/content.htm

Cleaning up statistic tables in BI

In order to keep your BI system healthy, it's necessary to clean-up some statistical tables once in a while. Especially in BI 7.0 I experienced some tables growing rapidly (e.g. DTP statistics).

In RSA1 goto Tools à Settings for BI Statistics.

Choose and select the tables you want to clean up:

Which option cleans which tables? Here you go:

Option	Tables
Query Statistics Tables	RSDDSTATHEADER, RSDDSTATDM, RSDDSTATEVDATA, RSDDSTATAGGRDEF, RSDDSTATINFO.
Statistic Loggin Tables	RSDDSTATLOGGING
Aggregates/BIA Index Process	RSDDSTATAGGR, RSDDSTATTREXSERV, RSDDSTATTREX,
InfoCube Statistics (Delete, Compress)	RSDDSTATDELE, RSDDSTATCOND

Didn't see this option in 3x System. There you can execute the same program manually: RSDDSTAT_DATA_DELETE.

Is your 'huge' table not here, maybe this will help:

Datasources	Tables
0TCT_DS01, 0TCT_DS02, 0TCT_DS03	RSDDSTATHEADER, RSDDSTATINFO RSDDSTATEVDATA RSDDSTATDM

By loading Technical content, data in these tables is automatically saved for 14 days. To change the # of days: change parameter TCT_KEEP_OLAP_DM_DATA_N_DAYS in table RSADMIN.

Last but not least: Table BALDAT (Application Log) can be cleaned with tcode SLG2.

Good luck!

Extraction Logistics Datasources: Tcode and program

An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). With this handy table you can find the status of your current job or previous initialization jobs through SM37.

Datasource	Tcode	Program
2LIS_02*	OLI3BW	RMCENEUA
2LIS_03_BX	MCNB	RMCBINIT_BW
2LIS_03_BF	OLI1BW	RMCBNEUA
2LIS_03_UM	OLIZBW	RMCBNERP
2LIS_04* orders	OLI4BW	RMCFNEUA
2LIS_04* manufacturing	OLIFBW	RMCFNEUD
2LIS_05*	OLIQBW	RMCQNEBW
2LIS_08*	VTBW	VTRBWVTBWNEW
2LIS_08* (COSTS)	VIFBW	VTRBWVIFBW
2LIS_11_V_ITM	OLI7BW	RMCVNEUA
2LIS_11_VAITM	OLI7BW	RMCVNEUA
2LIS_11_VAHDR	OLI7BW	RMCVNEUA
2LIS_12_VCHDR	OLI8BW	RMCVNEUL
2LIS_12_VCITM	OLI8BW	RMCVNEUL
2LIS_12_VCSCL	OLI8BW	RMCVNEUL
2LIS_13_VDHDR	OLI9BW	RMCVNEUF
2LIS_13_VDITM	OLI9BW	RMCVNEUF
2LIS_17*	OLIIBW	RMCINEBW
2LIS_18*	OLISBW	RMCSNEBW
2LIS_45*	OLIABW	RMCENEUB

Analyzing Throughput Times Process Chains

To analyze your process chains in SAP BI (but also other BI elements, SAP provides the program /SSA/BWT.

How to use:

Select the first bullet after running the program in SA38:

Enter the technical name of the process chain to be analyzed:

In the following screen you can see all details of the different process chain runs, but also compare different process chain runs with each other.

This program is very useful when you want to analyse why a certain process chain is taking longer.

Try it out!

Solving delta queue issues after system copy

Always make sure you empty ALL delta queues on ECC before doing a system copy. Stop the V3 jobs and run the infopackages. After system copy the queues between ECC-BW are not aligned anymore.

After a system copy or refresh of the R/3 source system, you may encounted dumps in your BI system when you want to initialize (logistic) data flows.

Mostly it occurs that in R/3 there are no activated delta queues, but in BI the Infopackages still contain the Init entry. The system dumps when you want to open the Infopackage, making it impossible to delete the Init entry there!

To solve this you have to run program RSSM_OLTP_INIT_DELTA_UPDATE in your BI system.

Fill in the fields. If you are sure, mark ALWAYS with X and execute the program.

After this action you can open your InfoPackage again and initialize the delta queue!

Welcome to this Blog

Hi all,

Welcome to this Blog about SAP BI.

We both have around 2,5 years of experience with all the different aspects in SAP BI.

We try to share our tips and tricks we have used or encountered during our work. Hopefully we can help others by sharing our 5 years of knowledge with you.

If you have any comments or suggestions, feel free to contact us!

Best regards,

Reemon & Frake