Goto to RSA2 in source system.
Give the datasource.
Check the extractor details. Click on the extractor. It will open the code.
Showing posts with label Extraction. Show all posts
Showing posts with label Extraction. Show all posts
3 Mar 2009
Idocs between R3 and BW while extraction
1)When BW executes an infopackage for data extraction the BW system sends a Request IDoc ( RSRQST ) to the ALE inbox of the source system.Information bundled in Request IDoc (RSRQST) is :
Request Id ( REQUEST )
Request Date ( REQDATE )
Request Time (REQTIME)
Info-source (ISOURCE)
Update mode (UPDMODE )
2)The source system acknowledges the receipt of this IDoc by sending an Info IDoc (RSINFO) back to BW system.The status is 0 if it is ok or 5 for a failure.
3)Once the source system receives the request IDoc successfully, it processes it according to the information in the request. This request starts the extraction process in the source system (typically a batch job with a naming convention that begins with BI_REQ).
The request IDoc status now becomes 53 (application document posted). This status means the system cannot process the IDoc further
4)The source system confirms the start of the extraction job by the source system to BW by sending another info IDoc (RSINFO) with status = 1
5)Transactional Remote Function Calls (tRFCs) extract and transfer the data to BW in data packages. Another info IDoc (RSINFO) with status = 2 sends information to BW about the data package number and number of records transferred
6)At the conclusion of the data extraction process (i.e., when all the data records are extracted and transferred to BW), an info IDoc (RSINFO) with status = 9 is sent to BW, which confirms the extraction process.
Request Id ( REQUEST )
Request Date ( REQDATE )
Request Time (REQTIME)
Info-source (ISOURCE)
Update mode (UPDMODE )
2)The source system acknowledges the receipt of this IDoc by sending an Info IDoc (RSINFO) back to BW system.The status is 0 if it is ok or 5 for a failure.
3)Once the source system receives the request IDoc successfully, it processes it according to the information in the request. This request starts the extraction process in the source system (typically a batch job with a naming convention that begins with BI_REQ).
The request IDoc status now becomes 53 (application document posted). This status means the system cannot process the IDoc further
4)The source system confirms the start of the extraction job by the source system to BW by sending another info IDoc (RSINFO) with status = 1
5)Transactional Remote Function Calls (tRFCs) extract and transfer the data to BW in data packages. Another info IDoc (RSINFO) with status = 2 sends information to BW about the data package number and number of records transferred
6)At the conclusion of the data extraction process (i.e., when all the data records are extracted and transferred to BW), an info IDoc (RSINFO) with status = 9 is sent to BW, which confirms the extraction process.
30 Sept 2008
Difference between LIS and LO Extraction
Both (LIS & LO) extractors are used to extract logica data from source system. Now a days most of the clients using LO extractor insted of LIS extractor.
LIS is old technique through which we can load the data. Here we use typical delta and full up-loading techniques to get data from an logistics application, it uses V1 and V2 update, it means that it was a synchronous or asynchronous update from the application documents to LIS structures at the time when the application document was posted.
LO Cockpit is new technique i think from bw 3.0 (not sure) which uses V3 which is an update that you can schedule, so it does not update at the time when you process the application documents, but it will be posted at a later stage.
You have separate datasources for header level, item level and schedule line level available in LO, you can choose at which level you want to extract your data and switch off others, which results in reduced data.we do not have this flexibility with LIS structures
All most all LIS extractor is outdated becuse of it's disadvantages.
Differences :
1. LIS works on transparent table concept and LO’s works on Cluster table concept.
2. Each data source i.e 2lis_11_s264 is splitted in to multiple data sources like 2 lis_11_vahdr, 2lis_11_vaitm,2lis_11_vascl, with this we can give more detailed level of information to the end users.
3. LIS works under Push mechanism where as Lo works on PULL Mechanism.
4. when we r doing delta then two transparent tables will come into picture i.e SBIW1 and SBIW2 in LIS. Where as in Los structures called LBWQ (Extractor queue), SM13 (Updatequeue)and RSA3 (delta queue).
5.LO cock pit is BW CONTENT EXTRACTOR
where as LIS is CUSTOMER GENERATED EXTRACTOR..
6.LO cockpit is uses Readymade datasorce...
but LIS we need to cretae everything...
and not to forget,
LO cockpit supports V3 update(BACK GROUND SCHEDULING Jobs)
LIS does't supports V3 update mode... it supports only V1 (SYNCHRONUS)& V2ASYNCHRONUS UPDATE)
LIS is old technique through which we can load the data. Here we use typical delta and full up-loading techniques to get data from an logistics application, it uses V1 and V2 update, it means that it was a synchronous or asynchronous update from the application documents to LIS structures at the time when the application document was posted.
LO Cockpit is new technique i think from bw 3.0 (not sure) which uses V3 which is an update that you can schedule, so it does not update at the time when you process the application documents, but it will be posted at a later stage.
You have separate datasources for header level, item level and schedule line level available in LO, you can choose at which level you want to extract your data and switch off others, which results in reduced data.we do not have this flexibility with LIS structures
All most all LIS extractor is outdated becuse of it's disadvantages.
Differences :
1. LIS works on transparent table concept and LO’s works on Cluster table concept.
2. Each data source i.e 2lis_11_s264 is splitted in to multiple data sources like 2 lis_11_vahdr, 2lis_11_vaitm,2lis_11_vascl, with this we can give more detailed level of information to the end users.
3. LIS works under Push mechanism where as Lo works on PULL Mechanism.
4. when we r doing delta then two transparent tables will come into picture i.e SBIW1 and SBIW2 in LIS. Where as in Los structures called LBWQ (Extractor queue), SM13 (Updatequeue)and RSA3 (delta queue).
5.LO cock pit is BW CONTENT EXTRACTOR
where as LIS is CUSTOMER GENERATED EXTRACTOR..
6.LO cockpit is uses Readymade datasorce...
but LIS we need to cretae everything...
and not to forget,
LO cockpit supports V3 update(BACK GROUND SCHEDULING Jobs)
LIS does't supports V3 update mode... it supports only V1 (SYNCHRONUS)& V2ASYNCHRONUS UPDATE)
Subscribe to:
Posts (Atom)
