Deciphering contents of Setup tables

Is there a tool, transaction which I can read a record from a setup table? Thanks

Hi Niten,
You cannot directly read the contents of a Setup Table. Its not a Database Application table whose contents you can view by SE11 using the table name.
Setup Tables are <b>CLUSTER Tables</b>, which combines many Table.
To have more details on Cluster Tables have a look at the following link...
http://help.sap.com/saphelp_erp2005vp/helpdata/en/cf/21f0b7446011d189700000e8322d00/frameset.htm
Regards,
Vidhya

Similar Messages

TCODE-to view the content of setuo table

Hi Experts,
Can anyone let me know is there any TCODE where we can view the content of setup table
Regards,
Meera

Hi,
Normally the tables r in the form of clustertables if u want to see there is no special tcode for this go to the SE11 or SE16 give the table name as below
if the datasource is 2lis_11_vahdr after filling setup tables for this datasource9for this application component)MC11va0hdrsetupin se11 in table u give that bold one and execute it u can see the setup tables.
Thanks & regrds
sathish
Edited by: sathish kakumudi on Jan 30, 2009 2:22 PM
Edited by: sathish kakumudi on Jan 30, 2009 2:24 PM

Problem with populating setup tables for purchasing

I'm working on NW2004s.
Problem: Setup tables are not getting populated for 2lis_02_hdr, 2lis_02_item..
what all i've done so far:
1. Activated Data Sources in RSA5.
2. In LO Data Extraction, all the extract structure are active. (btw in job control i'm not sure what it does, i did make job parameter start date immediate, didnt set the print parms, schedule job gives an error.. anything here i may be messing it up?)
3. In SBIW initialization Deleted the contents of setup table and executed the 'Purchasing - perform setup'.
4. In NPRT i can see the log, the name of the source table EKKO, duration of run is 0.0 and no of docs 130.
5. In RSA3 for 2lis_02_hdr extraction process 0 records.
6. I look at SE11 for 'MC02M_0HDRSETUP' and table contents gives 0 records.
Any help is appreciated what i'm missing why the setup tables are not populating. I went thru the forum and did what was said but no sucess yet. I'm not an expert in SAP BW just been working for a year so pl dont be cryptic, explain u'r answers. Thanks for your time
Mayil

Hi,
All the active datasources will be available in RSA6, after that go to LBWE ,maintain Ex Stru, Maintain DS and make that active, then we go for statistical setup
have you done these things?
Did you put any filters while filling up the setup tables?
what is the transaction you used for Setup.
cheers
RK

How to initialize the setup table for GTMuFF08Global Trade ManagementuFF09?

hi experts,
I can find the datasource of GTM like 2LIS_46_SCL, 2LIS_46_ITM with rsa6.
But when I use rsa3 to do test it, nothing found. I try to initialize the setup table, but I can not find it under SBIW.
Please help me, many thanks.
Brgds/steve

Hi
These Data Sources are from LOGISTICS Try at Tcode.LBWE --Logistics **** Pit.
Here is LO Cockpit Step By Step
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 u2013 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
Hope it helps

Setup table and delta mechanisim

Hi,
Can anyone explain in detail setup table concept in LO extraction and
Delta mechanisim?
Sridhar

Hi
LO Cockpit Step By Step
Here is LO Cockpit Step By Step
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 u2013 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
1. Data Flow
Relevant T-Codes
a) Initializtion
LBWE: Maintain Extract Structure, DataSource, Active Status, Job Control, Update Mode
SBIW, then follow tree menu path: Settings for App-Specific DS(PI) -> Logistics -> Managing Extract Structures -> Initialization -> App-Specific Setup of Statistical Data -> Choose XX Application -> Delete/Fill Setup(reconstructing) Table content
RSA3: Check content of setup table
b) Delta upload
SM13: Display update table/Extraction Queue content
RSA7: Display Delta Queue content
Edited by: Tapashi Saha on Jul 24, 2008 7:33 AM

Steps for Setup table

Hi,
I am using 2lis_02_itm and when trying to pull data.. it is not taking single record.
What we have to do? DO we have to fill setup table?
How to do this.>Can anyone explains me in steps
Thanks
Ananya

step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 Sales & Distribution) and Execute
- Now, Fill the Setup tables

Trying to fill setup table for 2LIS_04_P_ARBPL

Hi
I am trying to delete and fill setup tables for 2LIS_04_P_ARBPL. I go to SBIW, delete setup tables for application component 04 and then go back to fill setup tables. But I get the message "DataSource 2LIS_04_P_ARBPL contains data still to be transferred".
Am I missing a step?
Thanks
Pooja

I went to transaction SBIW ->Settings for Application specific datasources ->Logistics->Initialization->Delete contents of setup tables-> Application 04
Then under Initialization I went to Filling in the Setup table->Application specific setup of statistical table ->Production.
I entered the date & time (and entered my own Run name. Should I say new run or rerun or give my own Run name?) and executed the transaction.
Then I got the message - datasource still contains data to be transferred.
Thanks!

What does it mean by deleting the Content of the setup table when LO cockpi

Hi all:
what does it mean by deleting the Content of the setup table when LO cockpit ? why should we do it? why set up tables ?
Thank you very much!!!
Edited by: jingying Sony on Jun 7, 2009 4:46 AM

Hi Jingying Soni,
Data sources in LO cockpit have a seperate exctraction source during full update mode and delta update mode.
During delta update mode(when an transaction is posted in any particular application - like SD - sales orderm delivery) data is posted in application tables and updated alongside to the update table/extraction queue.
From the extraction queue this data is further transfered to the delta queue using periodic background jobs.The data is then upladed in BW. The delta lad always reads data from this delta queue.
However, when a full load is requested from the BW, the data is sourced by the set up table of the corresponding application.
The setup table is loaded/initalized first. In this initialization process , it reads data frm the corresponding application tables and stores it within this table. Later BW reads from this set up table whenever full/initial load is requested.
The process of filling set up able before full load request frrom BW is called set up run.
Before you run a set up to fill the set up tables you need to check that the set up table is empty.
If it is still containing data that was previously loaded in some other set up run. This data will als get loaded in BW unitinetionally/accidentally.
So, you need to ensure that you only get the intended data in BW. This can be done by proper selections to transfer data from application tale to set up table and from setup table to BW.
Along with this you hae to ensure that the set up table is either empty or you are using a disparate selection in the set up run and BW load which does not overlap with the previous set up runs data.
Hope it helps,
Best regards,
Sunmit.

Eroro while tryin gto see the setup table content

HI gurus,
i would like to see the setup table content for 2lis_11_vahdr.
when iam trying to got to T-cOde -OLI11BW it is saying that " No extract structure is activated or bw not connected" , i checked that extract structure is in active state . plase let me know the possible causes for this error.
Praveen

hello praveen
u can see the setup table contents in SE11
give table name as MC11VA0HDRSETUP for header level
                            MC11VA0ITMSETUP for itm level
                            MC11VA0SCLSETUP for scl level.
and one more OLI7BW IS FOR STATISTICAL SETUP OF SALES ORDER DS.
                 OLI8BW IS FOR STATISTICAL SETUP OF SD DELIVERY DS.
                 OLI9BW IS FOR STATISTICAL SETUP OF SD BILLING DS.
PLS AGGIGN POINTS IF IT WORKS FOR U,
THANKS,
PAVAN.
Edited by: pavan kumar on Feb 15, 2008 8:47 AM

Data not seen in RSA3 after setup table was filled

HI
We have an issue where we do not see data for Sales Orders and Deliveries in RSA3 (and hence is missing in BW).
For sales orders we are missing 6 months' data and for Deliveries we are missing data from june to october 2007.
We checked the sales order and delivery documents in R/3 and they exist for the above date ranges. We deleted and filled up the setup tables. But still don't see the data in RSA3.
There were no extractor changes done.
Any tips?
Thanks
Pooja

Go to SE11 and search for setup and look for the specific data source and see the content, if the content is actually zero, then there is nothing in the setup table.
thanks.
Wond

How to check the content of cluster table smw3_bdoc1(00)

Hi!
I want to check the business partner changes sending via bdoc from crm to sap.
For this i want to look into the bdocs.
I think it's the cluster-table smw3_bdoc1.
'Cause i don't know which is the name of the structure in the clustd-field i use:
data: dirtab type table of cdir,
      wa_dirtab like line of dirtab.
import directory into dirtab from database
                                  smw3_bdoc1(00)
                                  id '49600667F6980046E1008002AC18C6E5'.
if sy-subrc = 0.
write / 'Directory:'.
loop at dirtab into wa_dirtab.
    write: / wa_dirtab-name, wa_dirtab-otype, wa_dirtab-ftype,
             wa_dirtab-tfill, wa_dirtab-fleng.
endloop.
else.
write 'Not found'.
endif.
So i've found the directory object "BDOC_BODY".
Now i want to read the content with:
data:   iclust type string.
loop at itbdocid.
     IMPORT BDOC_BODY = iclust FROM DATABASE smw3_bdoc1(00)
                                    ID itbdocid-bdoc_id.
endloop.
An error message raises with...
"error importing the object BDOC_BODY"
The dump tells me that object types of BDOC_BODY and iclust doesn't match.
I've changed the field iclust to type xstring... but it's the same error.
If somebody here can help... Thanks a lot!
Cheers, Ingo

Hi,
Thanks, I can see the data now.I am expecting that data should display in the 2LIS_VDKON extractor.There are two records for particular condition type.Item 10 and Item 20, but in RSA3, it is showing only one record for Item 20 and not showing for Item 10.
I have cleaned and filled the setup tables, but still no luck.
Can you please guide me, where else to look?
Thanks
Priya

SETUP tables steps required

<Moderator Message: Please search before posting. You can find a lot of information related to this issue searching the forums, the blogs and of course the online help.>
Hi friends,
I want do purchase extraction using LO cockpit extraction before doing this i want to know about R/3 steps & setting if any in R/3 system.
I know about LO extraction steps apart from that if we have any steps in R/3 setting kindly forward to me.
thanks
Siri
Edited by: Siegfried Szameitat on Jan 26, 2009 12:31 PM

Hi Siri........
U want to extract Logistic data........
The following section describes the steps that are necessary to configure a data
flow for logistics data extraction.
1. Transfer the logistics DataSource for transaction data from Business Content
With the transfer of the DataSource, the associated extraction structure is
also delivered, but the extraction structure is based on LIS communication
structures. Furthermore, based on the extraction structure for the DataSource,
a restructuring table that is used for the initialization and full update to BI
is generated.
Naming convention:
DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
optional
Examples:
2LIS_11_VAITM: 11 = SD Sales VA = sales order, delivery schedule ITM
(u2192 ITEM) = document position
2LIS_02_HDR: 02 = MM purchasing HDR (u2192 HEADER ) = Document
header
Extraction structure MC<Application><Event/group of
events>0<Suffix>; where MC is derived from the associated communication
structures and <Suffix> is optional
Examples:
MC11VA0ITM: Extraction structure for the DataSource 2LIS_11_VAITM
MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
where M_ indicates the group for the events MA (order), MD (delivery
schedule), ME (contact) and MF (request).
Restructuring table (= setup table) <Extraction structure>SETUP
Example:
Extraction structure: MC11VA0IT u21D2 Restructuring table:
MC11VA0ITSETUP
2. Maintain extraction structure (transaction LBWE)
This means that fields can be added to the extraction structure that is
delivered with the DataSource without modifying anything. On the one
hand, fields from the LIS communication structures that are assigned to the
extraction structure can be used, that means standard fields that SAP has
not selected, and on the other hand, customer fields that were attached to
the LIS communication structures with the append technique can be used.
After the extraction structure is created, it is generated automatically and the
associated restructuring table is adapted.
3. Maintain/generate DataSource
In the DataSource maintenance, you can assign the properties Selection,
Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
the fields of the extraction structure. After enhancing the extraction structure,
the DataSource always has to be generated again!
4. Replicate and activate DataSource in SAP BI (=metadata upload)
5. Maintain Data Target (Data Store Object, InfoCube)
6. Maintain Transformations between DataSource and Data Target
7. Create a Data Transfer Process
the Data Transfer Process will be used later to update the data from the PSA
table into the Data Target.
8. Set extraction structure for updating to active (transaction LBWE)
In this way, data can be written to the restructuring table or the delta queue
from then on using the extraction structure (see following steps).
9. Filling the restructuring table/restructure (OLI*BW)
During this process, no documents should be created or changed in the
system! In some applications, it is possible to fill the restructuring table
beforehand in simulation mode. These results are listed in a log (transaction
LBWF). Before filling the restructuring table, you must ensure that the
content of the tables is deleted (transaction LBWG), preventing the table
from being filled multiple times. Once the restructuring tables are filled,
document editing can resume as long as Unserialized V3 Update or Queued
Delta is selected in the next step. Be absolutely sure that no V3 collection
run is started until the next successful posting of an InfoPackage for delta
initialization (see step 11).
10. Select update method
Unserialized V3 update
Queued delta
Direct delta
11. Create an InfoPackage for the DataSource and schedule the Delta
Initialization in the Scheduler
This updates the BI-relevant data from the restructuring table to the
PSA table. Since the restructuring table is no longer needed after delta
initialization, the content can be deleted (transaction LBWG).
Use the Data Transfer Process created in step 7 to update the data from
the PSA table into the Data Targets. After successful delta initialization,
document editing can resume, as long as the direct delta update method
was selected in step 13. This means that BI-relevant delta data is written
directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the delta data can
be written to the delta queue during delta initialization. This feature is
controlled with an indicator in the Scheduler.
12. Start V3 collection run (transaction LBWE)
This step is only necessary when the update method unserialized V3 Update
or Queued Delta was selected in step 10. By starting a corresponding job for
an application, the BI-relevant delta data is read from the update tables or
extraction queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BI and schedule the Delta
Update in the Scheduler
The BI-relevant delta data from the delta queue for the DataSource is updated
to the PSA table. Use the Data Transfer Process created in step 7 to update
the data from the PSA table into the Data Targets.
Hope this helps.......
Regards,
Debjani......

About setup tables

hi experts
happt new year to u all in advance.
i want o know that weither their wil set up tables in fi/sl & copa extraction .
and for what this set up tables meant for.
plz send answers to my mail id
kalyan11069@gmail
with regerds,
lakshmi raj.

there will be no setup tables for FI/SL and COPA extractions..
Go through the link:
http://help.sap.com/saphelp_nw04/helpdata/en/f3/3a69377f2b8032e10000009b38f8cf/content.htm
Regards
Manga
Assign points if it helps

Setup table Administration with Direct Delta mode

Hi guys,
I have a direct delta as update mode for my 2LIS_11_VAITM extractor in R/3.
I'd like to know if I have to manage the relative setup table (MC11VA0ITMSETUP) with this update mode also.
For instance, If I delete an ODS content and restart a new INIT on BW system, do I need to delete and then to fill the setup table?
In general, Do I need always to menage the setup table with each kind of update mode (direct delta, queued delta and V3 update)?
if you know the answers, please reply me direcly without insert link.
Many Thanks.

yes, you do....the initial loads for lo datasources are completely independent of the delta loads and hence of the delta method...
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
M.

Inventory Management Setup Table MC03BF0SETUP

Is there a limit to the number of records this setup table (MC03BF0SETUP) can hold? I am in the process of rebuilding InfoCube 0IC_C03.
Thanks,
Brendan.

Is there a limit to the number of records this setup table (MC03BF0SETUP) can hold? I am in the process of rebuilding InfoCube 0IC_C03.
I got your question . Please follow the steps
First check the data base table how many records its holding .
Delete the contents the of setup table and fill it again and check weather you are getting the same
number of records or not .
If same number of records issue solved .
Assign marks is the best way to appreciate help whoever it is

Deciphering contents of Setup tables

Similar Messages

Maybe you are looking for