Página 1 de 6
One stage stop to know all about BW Extractors-Part1
Subscribe Print Permalink Share
swapna gollakota Business Card Company: satyam computer services ltd Posted on Jan. 14, 2008 12:19 AM in Beginner, Enterprise Data Warehousing/Business Warehouse
What do you feel after having a glance atthe above snapshot............. Wait a minute I know what you guys are thinking.. Few of us will say immediately with out any second thought that it is a graphical representation of various extractors involved in data acquisition. Great! We got the answer But if the image still dwells on your mind and if it motivates you to know more on how the various extractors behave (or) how the extractionhappens? This blog is created to answer this. Note:Please refer "one stage stop to know all about BW Extractors -Part2", to know how customer generated extractors behave. Extractor in a simple terminolgy is used for extracting the data from various sources to BW. For this purpose we have SAP pre-defined extractors (LO extraction etc...) and customized extractors (Generic extractors)
Applicationspecific BW content extractors:
Lo Extraction: Logistics refers to the process of getting a product or service to its desired location upon request which involves transportation, purchasing, warehousing etc. Main areas in logistics are: Sales and Distribution (SD) Materials Management (MM) Logistics Execution (LE) Quality Management Plant Maintenance (PM) Customer Service (CS) Project System (PS)SAP Retail : application 11, 13, 08 (in LBWE T-code) : application 03, 02 : application 12 : application 05 : application 04, 17 : application 18 : application 20 : application 40,43,44,45
How the data extraction happens? Extraction can be done using either Full update/delta update. Full load: Incase of logistic application, Full/Initialization will extract the data from setup tables (containsonly historical data). So if you have decided to go for full load, wait a minute there is a road block For full update the data will be taken from setup tables, so in order to capture the changes you need to fill setup tables every time ,which will be a laborious task. So, it is always suggestible to go for delta loads which makes loading life easier. Read the below note to get details on deltaload-: Initialization: Data will be fetched from application table to setup tables (In Lo extraction, the extractor won't allow the direct communication with the application tables) from here, data finally reaches the target (info cube/ODS).Remember this process is for onetime. Pre-requisites: Prior to initialization make sure the following steps are completed: 1. Maintain Extract Structure 2.Maintain data sources 3. Activate Extract Structure 4. Delete Setup tables 5. Fill setup tables
SAP Network Blog: One stage stop to know all about BW Extractors-Part1
Página 2 de 6
Delta load: Once after successful initialization, we can use delta update to capture the changed /new records Once a new transaction happens/an existing recordis modified, upon saving it goes to the respective application table. From here depending on the update mode Direct/queued/Unserialized V3 update the data will be populated in delta queue (RSA7) and finally reaches to BW.
Pre-requisites: Prior to delta loads make sure the following steps are completed: 1.Define periodic V3 update jobs 2. Setting up the update mode (direct/queued/Un serializedv3 update) LO- Delta Mode: Info object 0Recordmode helps in identifying the delta Check the field "delta "in ROOSOURCE /RODELTAM table Incase of Lo extraction it is "ABR" ABR: An after image shows the status after the change, a before image the status before the change with a negative sign and the reverse image also shows the negative sign next to the record while indicating it for deletion....