Help for extractors

[Former Member]

Hi

I'm going crazy.

I've to find in which R/3 tables are data for dataSource 2LIS_11_VAHDR (extractor MCEX_BW_LO_API I think).

I'm using transaction rsa3 in debug mode and looking for SELECT statments or using SQL trace (st05), but I cant find data tables.

where i'm wrong?

Someone know where to find documentation for this DataSource or a better way to find my tables?

thanks to all

Michele

[Former Member · Accepted solution]

Hi Michele,

the extract structure is MC11VA0HDR. The table is MC11VA0HDRSETUP. Check the data of the table with SE16. If it's empty run a setup from your logistics customizing cockpit for application 11. By the way, I know the tables for sales orders (vbak, vbpa, vbuk... for headers, vbap, vbpa, vbup for items ...) because I already did a lot of programming on R/3 side related to SD.

You can also figure out which tables the standard uses as a data basis by maintaining your extract structure. The tablename is given there as a structure name like MC<tablename>. So for vbak (sales order header) it is mcvbak.

regards

Siggi

regards

Siggi

[Former Member · Accepted solution]

Hi Siggi, if I call SE84 and open MC11VA0HDR I cant find MC<tablename> as you said, the only MC.. are MC11VA1HDR and MC11VA2HDR, where I'm wrong?

[Former Member · Accepted solution]

Michele,

go to se11 and in 'view' (this is a structure) and put your MC(table)...

if you're facing some particular problem let us know the details...

bye,

Roberto

[Former Member · Accepted solution]

Hi Roberto, I think I have no particular problem (Except I think i have no data in R/3 source tables), I only want to understand how to locate source tables from witch extractor load data.

If I open MC11VA0HDR with se11 as you said I cant find any link to source tables vbak, vbpa, vbuk, vbap, vbpa, vbup.

Thanks for your time

Michele

[Former Member · Accepted solution]

Hi Michele,

we have to come back to clarify this issue...

now you are using a Logistic Cockpit Extractor (LBWE)...for this type of datasource there is no direct access to the application tables (like, in your situation, VBAK and so on), but there is the following mechanism:

- when you perform an init or a full, the function module MCEX_BW_LO_API (I suggest you to take a look to the code of this FM) selects the records from the setup tables (you filled from the different OLI*BW); now, the only link there is with your application tables is in the recompilation run (try to debug it and you will see the select statements against VBAK, VBAP...)

- when you perform a delta, the function module comes to the delta queues (you can see that from RSA7 or LBWQ); here there isn't any link with your application tables, cause, thanks to V3 method (with some difference among the serialized one, direct, queued...), the records are updated automatically in V2 state (with a sinchcronous and an asinchronous update directly from the transactions..that is VA01 or VA02..) and you have to schedule a job that make these records available in your queues (RSA7) with V3 completed...

So, if you have some difficult to find something, please refer to the above scenario and try to find the solution...

If you want some more detailed infos..

Bye,

Roberto

[Former Member · Accepted solution]

Hi Roberto, I think I get it, can you please explain this:

> selects the records from the

> setup tables <b>(you filled from the different OLI*BW);</b>

Thanks

[Former Member · Accepted solution]

When you run an init or a full, the FM MCEX_BW_LO_API take this infos from these elements:

CASE s_estruc.

(...)

• extractstruc internal table setup table

*-->Application '11' (Sales)

sel 'MC11VA0HDR' mc11va0hdr_tab mc11va0hdrsetup.

(...)

CALL METHOD exit->fill_data

EXPORTING

i_estruc = s_estruc

i_t_select = s_t_select[]

flt_val = mcapp

i_maximum_size = s_maximum_size

i_source = i_isource

IMPORTING

e_t_data = e_t_data[]

e_flg_no_more_data = s_flg_no_more_data

CHANGING

c_cursor = g_cursor

EXCEPTIONS

error_passed_to_mess_handler = 1.

thank to this method the records are taken from the setup table (init or full), that you are filled before by running your OLI7BW.

[Former Member · Accepted solution]

Hi can you please explain this:

>that you are filled

> before by running your OLI7BW.

Michele

[Former Member · Accepted solution]

Michele,

the OLI7BW is the transaction that permit to run the recompilation job in order to fill your sales setup table; you can arreive there also following this path SBIW->Business Information Warehouse->Settings for Application-Specific DataSources->Logistics->Managing Extract Structures->Initialization->Filling the Setup Table->Application-Specific Setup of Statistical Data->Perform Setup SD Sales Orders.

Once you have ran this job (and once it's successful finished) you can find your setup table filled. Only at this moment you can perform a full or initial load (and the FM will take the records just from this table).

What isn't clear in this procedure ?

[Former Member · Accepted solution]

Thank you so much.

br

Michele