w

1/10(W)

> NWBI

140

How to run bw setup table ?

2011-07-25 | 5260 19 |

Alpha.zhou:

What are the Setup Tables?

What are the Setup Tables?

SAP 10R/3...

The Setup Tables are the objects from which the Business Warehouse system is going to extract data for Full loads and Initialization on LO Cockpit DataSources. Not just "LO DataSources" because there are some that don't use this feature. When a Full extraction or a Delta Initialization is going to be performed, the Setup Tables need to be filled with all the historical data to be loaded to the Business Warehouse system.
0

33.00

Their content can be deleted any time, without affecting the R/3 transaction data. In fact, after the full/Init load has been performed, it is highly likely that the information contained in the Setup Tables is already not up-to-date anymore. Therefore, it would be no harm at all to delete their content. You may think of it as a "PSA" on the R/3 side. If the load performed was an Initialization, the next records to be extracted will be sent to the Delta Queues.

... Google BPF(Business Process Fl... SAP BADI-BADI BPC BW abap DataSource Enhancement ...

It isn't 100% true to say that the reason for the Setup Tables is to ensure the extractors won't need to access the always busy application tables (like EKKO or VBAK). The application tables are still read during the setup running.

53[] In-memory database SAP BASIS

Setup Tables Nomenclature

... >>

The base nomenclature for these tables is MC*SETUP. It may not be easy to find the actual name you may be looking for, but if you display some in se11/se16 you may figure it out by the description. I created the following Wiki page with the Setup Tables names:

BW Setup Tables List

Application DataSource Setup Table

02

Purchasing Purchasing Purchasing Purchasing

2LIS_02_ACC 2LIS_02_CGR 2LIS_02_HDR 2LIS_02_ITM

MC02M_0ACCSETUP MC02M_0CGRSETUP

Folder: BW Setup for MC02M_0ACC BW-Rebuild for MC02M_0CGR Storage

: 86... ...

Storage BW Setup for MC02M_0HDRSETUP MC02M_OHDR Storage BW Setup for MC02M_0ITMSETUP MC02M_OITM

18

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

2/10(W)

Purchasing Purchasing Purchasing Inventory Controlling Inventory Controlling Inventory Controlling Production / 04 Shop Floor Control Production / Shop Floor Control Production / Shop Floor Control Production / Shop Floor Control Production / Shop Floor Control Production / Shop Floor Control 05 Quality Management

2LIS_02_SCL 2LIS_02_SCN 2LIS_02_SGR

MC02M_0SCLSETUP MC02M_0SCNSETUP MC02M_0SGRSETUP

Storage BW Setup for MC02M_OSCL BW-Rebuild for MC02M_0SCN Storage BW-Rebuild for MC02M_0SGR Storage

... >>

Save BW 2LIS_03_BF MC03BF0SETUP Reorganization for MC03BF0 BW Stock Initialization Storage for MC03BF Save BW 2LIS_03_UM MC03UM0SETUP Reorganization for MC03UM0 BW Reorganization Store for MC04P_0ARB

2 3 4 5 6 7 8 9 10

03

2LIS_03_BX

MC03BX0SETUP

2LIS_04_P_ARBPL MC04P_0ARBSETUP

BW Reorganization 2LIS_04_P_COMP MC04P_0COMSETUP Store for MC04P_0COM 2LIS_04_P_MATNR MC04P_0MATSETUP BW Reorganization Store for MC04P_0MAT

BW Reorganization 2LIS_04_PEARBPL MC04PE0ARBSETUP Store for MC04PE0ARB BW Reorganization 2LIS_04_PECOMP MC04PE0COMSETUP Store for MC04PE0COM BW Reorganization 2LIS_04_PEMATNR MC04PE0MATSETUP Store for MC04PE0MAT BW Reorganization 2LIS_05_Q0ACTY MC05Q00ACTSETUP Store for MC05Q00TSK (Notif. Activity)

Quality Management

BW Reorganization Store for 2LIS_05_Q0CAUSE MC05Q00CSESETUP MC05Q00CSE (Notification Cause) 2LIS_05_Q0ITEM BW Reorganization MC05Q00ITMSETUP Store for MC05Q00ITM (Notification Item)

Quality Management Quality Management Quality Management

BW Reorganization 2LIS_05_Q0NOTIF MC05Q00NTFSETUP Store for MC05Q00NTF (Notification) 2LIS_05_Q0TASK BW Reorganization MC05Q00TSKSETUP Store for MC05Q00TSK (Notification Task) BW Reorganization Store for MC05Q1_INSPSETUP MC05Q1_0INSP (Check Results) BW Reorganization for MC05Q2_INSPSETUP MC05Q2_0INSP (Inspection Results) Store BW Reconstruction for MC05QV0UDNSETUP MC05QV0UDN (Usage Decision)

Quality Management

2LIS_05_QE1

Quality Management

2LIS_05_QE2

Quality Management

2LIS_05_QVUDN

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

3/10(W)

06

Invoice Verification

2LIS_06_INV

MC06M_0ITMSETUP

Folder: BW Setup for MC06M_0ITM

08

Transport/ Shipment/ 2LIS_08TRFKP Shipment Costs Transport/ Shipment/ 2LIS_08TRFKZ Shipment Costs Transport/ Shipment/ Shipment Costs Transport/ Shipment/ Shipment Costs Transport/ Shipment/ 2LIS_08TRTS Shipment Costs 2LIS_08TRTLP 2LIS_08TRTK

Storage BW MC08TR0FKPSETUP Reorganization for MC08TR0FKP MC08TR0FKZSETUP BW Reorganization Store for MC08TR0FKZ BW Reorganization Store for MC08TR0TK BW Reorganization Store for MC08TR0TLP BW Reorganization Store for MC08TR0TS BW Reorganization Store for MC11V_0ITM BW Reorganization Store for MC11V_0SCL

MC08TR0TKSETUP

MC08TR0TLPSETUP

MC08TR0TSSETUP

11

SD Sales Orders SD Sales Orders SD Sales Orders SD Sales Orders SD Sales Orders SD Sales Orders SD Sales Orders SD Sales Orders SD Sales Orders

2LIS_11_V_ITM 2LIS_11_V_SCL 2LIS_11_V_SSL

MC11V_0ITMSETUP MC11V_0SCLSETUP

BW Reorganization MC11V_0SSLSETUP Store for MC11V_0SCL BW Reorganization MC11VA0HDRSETUP Store for MC11VA0HDR BW Reorganization Store for MC11VA0ITM

2LIS_11_VAHDR

2LIS_11_VAITM

MC11VA0ITMSETUP

2LIS_11_VAKON

Storage BW MC11VA0KONSETUP Reconstruction for MC11VA0KON BW Reorganization MC11VA0SCLSETUP Store for MC11VA0SCL MC11VA0STHSETUP MC11VA0STISETUP BW New Structure Store for MC11VA0STH BW New Structure Store for MC11VA0ST

2LIS_11_VASCL 2LIS_11_VASTH 2LIS_11_VASTI

12

LE Deliveries / 2LIS_12_VCHDR Shipping LE Deliveries / 2LIS_12_VCITM Shipping LE Deliveries / 2LIS_12_VCSCL Shipping

BW Reorganization MC12VC0HDRSETUP Store for MC12VC0HDR MC12VC0ITMSETUP MC12VC0SCLSETUP BW Reorganization Store for MC12VC0ITM BW Reorganization Store for MC12VC0SCL

13

SD Billing Documents SD Billing Documents SD Billing Documents Plant Maintenance Plant Maintenance

2LIS_13_VDHDR

BW Reorganization MC13VD0HDRSETUP Store for MC13VD0HDR MC13VD0ITMSETUP BW Reorganization Store for MC13VD0ITM

2LIS_13_VDITM

2LIS_13_VDKON

Storage BW MC13VD0KONSETUP Reconstruction for MC13VD0KON MC17I00ACTSETUP BW Reorganization Store for MC17I00ACT (Notif. Activity) BW Reorganization Store for MC17I00CSE (Notification Cause)

17

2LIS_17_I0ACTY

2LIS_17_I0CAUSE MC17I00CSESETUP

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

4/10(W)

Plant Maintenance Plant Maintenance Plant Maintenance Plant Maintenance

2LIS_17_I0ITEM

MC17I00ITMSETUP

BW Reorganization Store for MC17I00ITM (Notification Item) BW Reorganization Store for MC17I00NTF (Notification) BW Reorganization Store for MC17I00TSK (Notification Task)

2LIS_17_I0NOTIF

MC17I00NTFSETUP

2LIS_17_I0TASK

MC17I00TSKSETUP

2LIS_17_I3HDR

Store BW MC17I30HDRSETUP reconstruction for MC17I30HDR (Order) Store BW Reconstruction for MC17I30OPR (Process) BW Reorganization Store for MC18I00TSK (Notif. Activity) BW Reorganization Store for MC18I00CSE (Notification Cause) BW Reorganization Store for MC18I00ITM (Notification Item) BW Reorganization Store for MC18I00NTF (Notification) BW Reorganization Store for MC18I00TSK (Notification Task)

Plant Maintenance

2LIS_17_I3OPER

MC17I30OPRSETUP

18

Customer Service Customer Service Customer Service Customer Service Customer Service Customer Service

2LIS_18_I0ACTY

MC18I00ACTSETUP

2LIS_18_I0CAUSE MC18I00CSESETUP

2LIS_18_I0ITEM

MC18I00ITMSETUP

2LIS_18_I0NOTIF

MC18I00NTFSETUP

2LIS_18_I0TASK

MC18I00TSKSETUP

2LIS_18_I3HDR

Store BW MC18I30HDRSETUP Reconstruction for MC18I30HDR (Order) Store BW Reconstruction for MC18I30OPR (Process)

Customer Service

2LIS_18_I3OPER

MC18I30OPRSETUP

40

Retail / Retailing Agency Business Agency Business Agency Business Agency Business Agency Business Agency Business

2LIS_40_REVAL

BW Reorganization MC40RP0REVSETUP Store for MC04PE0ARB MC45CD0LSTSETUP Folder: BW Setup for MC45CDLST

45

2LIS_45_CDLST

2LIS_45_PDLST

Folder: BW Setup for MC45PD0LSTSETUP MC45PD0LST (Posting List) Folder: BW Setup for MC45VD0LSTSETUP MC45VD0LST (Settlement Vendor) MC45W_0HDRSETUP MC45W_0ITMSETUP MC45W_0LSTSETUP Folder: BW setup for MC45W_0HDR Folder: BW Setup for MC45W_0ITM Folder: BW Setup for MC45W_0LST

2LIS_45_VDLST

2LIS_45_HDR 2LIS_45_ITM 2LIS_45_LST

I tried to list all the tables I could find. I didn't list them all here in this post, because there is a large number of Setup Tables. It is better to put that in a Wiki, just so you guys can add more names you find, or correct mistakes. Let's work together on that.

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

5/10(W)

If you need to quickly find the name of a name, just Control+F this Wiki!

Procedures involving the Setup

Well, it does sound pretty simple if you consider only the purpose of the Setup Tables. The part which would turn this subject eligible for a blog post is how to properly handle these tables in various possible activities. I have composed a list of step-by-step explanations for some procedures that, in a way or another, end up involving Setup Tables somehow. I'll also mention what are the common consequences of not performing these activities correctly.

Deleting Setup Tables Content

1- To delete the Setup Tables, you may go directly to LBWG or choose the following IMG option (transaction SBIW). IMG path: - Data Transfer to the SAP Business Information Warehouse - Settings for Application-Specific DataSources (PI) - Logistics - Managing Extract Structures - Initialization >>Delete the Contents of the Setup Tables

2- Select the application for which you want the Setup Tables to be deleted. 3- Click on "Execute" or press F8.

How can you check if the content was properly deleted? You may check the correspondent Setup Table or perform an extraction check for the relevant extractors in RSA3.

Filling Setup Tables

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

6/10(W)

1- Before filling the Setup Tables, you need to ensure at least 1 extractor for the application is active in LBWE. 2- To enter the transactions to perform the setup, you may either go directly to one of the following transactions, or choose one of te options from the SBIW menu displayed below.

Application

Transaction

Component

02 03

Purchasing Inventory Controlling Production / Shop Floor Control Quality Management Invoice Verification Transport /Shipment Shipment Costs SD Sales Orders LE Deliveries / Shipping SD Billing Documents Plant Maintenance Customer Service Retail / Retailing Agency Business

OLI3BW MCNB OLI1BW OLIZBW

BW-BCT-MM-PUR BW-BCT-MM-IM

04 05 06 08 08 11 12 13 17 18 40 45

OLI4BW OLIQBW OLI6BW VTBW VIFBW OLI7BW OLI8BW OLI9BW OLIIBW OLISBW ORISBW OLIABW

BW-BCT-PP-LIS BW-BCT-QM BW-BCT-MM-IV BW-BCT-LE-TRA BW-BCT-LE-TRA BW-BCT-SD-SLS BW-BCT-LE-SHP BW-BCT-SD BW-BCT-PM BW-BCT-CS BW-BCT-LO BW-BCT-ISR-AB

IMG path: - Data Transfer to the SAP Business Information Warehouse - Settings for Application-Specific DataSources (PI) - Logistics - Managing Extract Structures - Initialization - Filling the Setup Tables >> Application-Specific Setup of Statistical data

3- Specify a Run Name and Date (inform a future date). 4- Execute. Hint: You can check the logs for the Setup in Transaction NPRT.

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

7/10(W)

How can you check the data that was filled? You may check the correspondent Setup Table or perform an extraction check for the relevant extractors in RSA3.

Initialization or Full Loads

1. Delete the Setup Tables contents from the relevant application number. 2. Lock all users and terminate all scheduled jobs that could affect the application. In particular, you must deactivate the start of the RMBWV3xx update report. 3. Then load the delta data from R/3 into BW, so that the delta queue (transaction RSA7) no longer contains any data. 4. Fill the Setup Tables. 5. If the datasource supports early delta initialization (ROOSOURCE-ZDDABLE field), you may unlock the users and return regular activities. 6. Run the InfoPackage. 7. If the datasource doesn't support early delta initialization (ROOSOURCE-ZDDABLE field), you'll be able unlock the users and return regular activities only after the Init request has finished in the BW system.

More details on SAP's recommedations can be found on the following SAP Note: 602260 - Procedure for reconstructing data for BW. The performance on the construction of the Setup Tables can be improved, with the following SAP Note: 436393 - Performance improvement for filling the setup tables.

What happens if you don't fill the Setup Tables before performing a full or delta initialization? If you have deleted the content or has never filled them before: No data is extracted. If you have already filled it and haven't deleted the content: the data extracted won't be up to date. What happens if you don't delete the Setup Tables before performing a full or delta initialization? If you don't refill them: the data extracted won't be up to date. If you refill them: there is a risk you will have duplicate records.

Extractors Maintenance

1. 2. 3. 4. 5. 6. 7. 8.

Lock users out of R/3. Deletion of the contents of Setup Tables for specific applications in transaction LBWG. Run the collective run, so all the data is sent into the delta queues. Empty BW delta queues on R/3 by extraction to BW. Apply the changes / Transport. Unlock users out of R/3. Run the collective run so all the data are sent into the delta queue. Recommence extraction into BW from the modified R/3.

The following SAP Note contains more information about this: 328181 - Changes to extraction structures in Customizing Cockpit. What happens if you maintain the extractors with data in the Setup Tables or in the Delta Queues? When you apply the changes (via transport, for example), there is a chance inconsistencies will be generated in the structure of the extractor. The job that collects data for deltas, for

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

8/10(W)

example, may start to fail. It may also appear that delta records were lost. This records are actually written into the extraction queue or in SM13, however it's not possible to read them, because of the differences in the structure. Note that even if you are adding a new extractor that didn't exist before, this may also affect the existing extractors. If inconsistencies are found or records are missed, the solution is to perform a Full Repair load or to reinitialize the DataSource. For some applications, you may use the Hash Solution to recover them. The following SAP Note describes this procedure: 835466 - Using the repair mode of the hash solution. (I'll make sure I do post new post just about the Hash Solution) In case of missing records, you may also run a Full Infopackage in Repair Mode. You should be able to identify, though, which documents need to me contained in this repair.

R/3 Upgrades

In upgrades, a check was introduced to make sure this procedure is followed. SAP Support's recommendation is to follow the steps listed below, when performing an upgrade. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Lock users out of R/3. Deletion of the Setup Tables contents for specific applications in transaction LBWG. Run the collective run so all the data are sent into the delta queue. Empty the BW delta queues on R/3 by extraction to BW: Start prepare phase on R/3 including generation of shadow instance. Return R/3 productive instance to users. Recommence normal extraction from R/3 to BW, while upgrading shadow instance. Lock users out of R/3. Run the collective run so all the data is sent into the delta queue. Empty BW delta queues on R/3 by extraction to BW. Final upgrade of productive instance. Return upgraded system to users. Re-commence extraction into BW from upgraded R/3.

SAP Note 1081287 contains a Step-by-Step explanation about cleaning up the Setup Tables and the Delta queues during an upgrade. 1081287 - Data extraction orders block the upgrade process. As you may be wondering, the act of locking the users in step 1 and 8 isn't the automatic lock the upgrades performs. You will need to lock the users yourself, with transaction SU10, for example. The main purpose is to prevent that data is sent to the extraction queues or Setup Tables. What happens if you don't properly clean up the Setup Tables in an upgrade? The consequences are basically the same as changing an extractor: inconsistencies and missing delta records. In this situation, the Hash-Solution isn't really a good option, because the upgrade may have delievered changes on way too many structures. The risk of generating more inconsistencies with the Hash-Solution is great.

Plug-in upgrade or plug-in patch upgrade, support package upgrade or Unicode conversion

SAP Support's recommended Step-by-Step for these activities is very similar to maintaining an extractor. 1. 2. 3. 4. Lock users out of R/3. Deletion of the contents of Setup Tables for specific applications in transaction LBWG. Run the collective run so all the data are sent into the delta queue. Empty BW delta queues on R/3 by extraction to BW.

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

9/10(W)

5. Apply one of these processes: plug-in upgrade or plug-in patch upgrade; support package upgrade; transports; manual changes; Unicode conversion. 6. Unlock users out of R/3. 7. Run the collective run so all the data are sent into the delta queue. 8. Recommence extraction into BW from modified R/3.

Creating ABAP Programs for Maintaining ... FAQ: SAP BI Some configuers and solutions

(0)

( )

Garbage Collection--Part 2: Auto... BASE: An Acid Alternative - ACM ... Resource Management Design Patte... rabbitmqctl(1) manual page CSDN Spring Web Flow .... pc(Op... GIS in Design and Asset Manageme...

27 ...

[]GV

L44 80.00

Sony/ ST27i 1700.00

(NB38+S64) 300.00

2011-9-8 15:29:34

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18

10/10(W)

QQ

http://www.360doc.com/content/11/0725/11/7281976_135709068.shtml

2013-08-18