on 09-30-2005 7:00 AM
Hi All,
!!!!!!!!!!!Make my concept clear Guys!!!!!!!!!!
Lets take a datasource 2LIS_04_P_ARBPL when any transaction is done in production planning the data is gathered in extract structure and when collective update is run (queue delta) then data comes to Bw Delta queue(RSA7). Datasource has function module which actually fetches the data when the request comes from BIW.
Query: Is the functional module which is an actual engine to datasource, and send data to BW, fetches the data from where??? Is it from delta queue or from actual tables.
Thanks
Sachin K
Hi roberto,
What i understood is when my infopack is scheduled on BW side the datasource on the r/3 side will read the data from delta que. through extract structure.
Right???
sachin k
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Roberto,
I went through your document but i could not find any thing related to keyword datasource. but good one to understand other concepts..
What i understood here is there is fn called
1. MCEX_UPDATE_CALL_XX which gets executed when the document is posted and data comes in extract structure
2. Using MCEX_UPDATE_XX_QRFC data comes to BW delta queue.
Can you explain more ..
Sachin K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sachin,
everything inside the weblog is related to your keyword datasource !!!
What do you understand about datasource concept ?
Datasource (as physical object) is nothing is you don't link it (and consider during your reasoning) together with its extract structure and extraction pgm/mechanism: it would be only an empty box !
So, after the two points that you highlighted in your previous post, add the following:
3. Start the infopackage in BW
4. The datasource, through extraction structure, will take data and everthing (as IDoc) is transferred to your BW.
If you have any doubt, let us know !
Bye,
Roberto
...and please don't forget to reward the answers...it's THE way to say thanks here...
and look also to many of your previous threads: close your questions and assign points to the contributors !
Hi Sachin!
Look here...
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
As you can understand, how function modules work depends from delta method you are using (direct, queued or unserialized...).
All the pictures I think can be useful to clarify the concept (anyway, during the first update - V1 - data comes from the transaction, not from the tables, directly involved only during setup job)!
Hope it helps!
Bye,
Roberto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All
Still the discussion does not lead mean to any conclusion at all..
Sachin K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anil,
If it is so then if you see the functional module for that datasource you will find the logic access directly the table also why is it so????
Sachin K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Function module is used to get data from different tables and putting in structure that is extract structure...this will have records when the program/function module/datasource is running/executing...
it is not possible to get data from directly tables to the extract struc/datasource for bw....
lakhes of records will get created for some tables like bseg/bsek...is it possible to get these data to bw directly....no no..it is not possible....bcos of these function module are coming here....
let me know if you have issues/correct me if i wrong....
thanks,/mahantesh
Hi Mahantesh,
with referenct ot your statement:
<i>tables like bseg/bsek...is it possible to get these data to bw directly....no no..it is not possible....bcos of these function module are coming here....</i>
When BW wants the delta data for Account documents, it will not fetch from BSEG or RSA7. It will take the help of one intermediate table BWFI_AEDAT.
With rgds,
Anil Kumar Sharma .P
Hi Anil!
<i>If so, I guess, The function module is taking the reference from RSA7 to select the records from base table.</i>
The delta queue actually contains all the transaction data (not just references).
A (generic) function module pulls the data from the delta queue and it is then posted to BW.
How and when the data is written into the delta queue depends on the update mode you select in transaction LBWE. If you use 'queued delta' the transaction data is collected in a queue (which you can access via TA LBWQ) and then written into the delta queue (RSA7) by a job (which can be scheduled in TA LBWE). If you use direct delta, the transactional data is written into the delta queue 'on-line', i.e. when an R/3 user creates, changes, or deletes a document in R/3.
The mechanism that actually posts the data into LBWQ (for queued delta) or RSA7 (for direct delta) is part of the LIS in R/3 and is not just used for BW extraction purposes.
Hope this helps...
Kind regards,
Christian
Hi,
From RSA7 , the data will be pulled to BW, when you execute the info package.Tahts why you will see zero recrds if you execute info package before pushing the data from Extraction queue to Delta queue.
With rgds,
Anil Kumar Sharma .P
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.