Basics of Extractors

Hello All,
I want some basic information about Extractors. These are the questions i want ur help for.
Q1. What is the function of an Extractor?
Q2. What are the different types of Extractors in BI?
Q3. Which Extractor will be used in what kind of scenario?
Q4. Advantages and Disadvantages of each type of Extractor.
Any other information apart from the above will be all the more helpful.
PS: Precis information from the exising posts did not clear my understanding.
Regards,
Kunal Gandhi

Extractors are one of the data retrieval mechanisms in the SAP source system.
An extractor can fill the extract structure of a DataSource with the data from SAP source system datasets.
2 Types
1.Application Specific Extractors:-These are the extractors specifically designed for the business content datasources.
a)BW Content extractors (Eg: FI, CO, HR, SAP CRM, LO-Cockpit)
b)Customer-Defined extractors (Eg: LIS, FI-SL, COPA)
2.Generic extractors: with Generic extractors you can extract transaction data,master data attributes or texts from the SAP source system and transfer it into BW.
You can run generic data extraction in the R/3 source system application areas such as LIS, CO-PA, FI-SL and HR.Regardless of application, you can generically extract master data attributes or -texts, or transaction data from all transparent tables, database views or SAP query functional areas or using the function module.
Cross-Application
Generic extractors (Eg: Based on DB Table, View or InfoSet or Function Module)
Check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/28/4c553c42360a40e10000000a114084/frameset.htm

Similar Messages

  • BW extractor -XI-File

    Hi all,
    Basically, the extractors collect data to be sent to BW (an R/3 background job runs every few minutes to fill them). BW then initiates an RFC to R/3 to pull the data out of the extractor and into BW.
    Now can I use the same extractors to pull data into XI? If so how? Is there any flat file that can be sent to XI?
    Thanks,
    Srinivas
    Edited by: Srinivas Davuluri on Jul 15, 2008 4:13 PM

    Hi srinu,
    verify this link,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/18dfe590-0201-0010-6b8b-d21dfa9929c9
    Regards,
    Suryanarayana

  • Best practice data source from ECC 6.0 for legal consolidation in BPC NW7.5

    Hi there,
    after scanning every message in this forum for "data source" I wonder if there isn't any standard approach from SAP to extract consolidation data from ECC 6.0. I have to say that my customer is not using New g/l so far and therefore the great guide "how to get balances from ECC 6.0 ..." does not fully work for us.
    Coming from the old world of EC-CS there is the first option to go via the GLT3 table. This option requires clever customization and the need to keep both GLT0 and GLT3 in line. Who has experiences regarding maintenance of these tables in a production environment?
    We therefore plan to use data source 0FI_GL_4 which contains all line items to the financial documents posted. Does this approach make sense or will it fail because of performance issues?
    Any help is appreciated!
    Kind regards,
    Dierk

    Hi Dierk,
    Do you have a need for the level of detail provided by the 0FI_GL_4 extractor? Normally I would recommend going for the basic 0FI_GL_6 extractor, which provides a much more manageable data volume since it only gives the periodic activity and balances as well as a much smaller selection of characteristics. Link: [http://help.sap.com/saphelp_nw70/helpdata/en/0a/558cabb2e19a4db3097b81bba4fd0e/frameset.htm]
    Despite this initial recommendation, every client I've had has eventually had a need for the level of detail provided by the 0FI_GL_4 extractor (or the New G/L equivalent - 0FI_GL_14). Most BW systems can handle the output of the line-item extractors without much issue, but you should test using production data and make sure your system sizing takes into account the load.
    The major problem you can run into with the line-item extractors is that if your delta somehow gets compromised it can take a very long time (days, sometimes weeks) to reinitialize and this can cause a large load in your ECC and BW system. Also, for the first transport to production, it is important to plan time to initialize the delta.
    Ethan

  • Creation of custom table in R/3

    Hi Experts,
                 We have content extractor  which takes excessively longer time to load the data. We are planning to  create a custom table and use generic extraction of data. Appreciate any expertise on this issue.
    Thanks,
    Varun.

    Hi Varun,
    Basically Content Extractors are supposed to be very efficient. But if you are still planning to go ahead by creating your own custom table and carrying out generic extraction of data you can use the below document to do the same...
    Create Generic Delta Documentation -->
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Explanation  on Upper Limit and lower limit -->
    http://help.sap.com/saphelp_nw04/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/frameset.htm
    Hope this helps.
    Thanks & Regards,
    SH

  • Update mode and rsa3

    Dear Experts,
    Sometimes though basically certain extractor like generic extractor based on a view is working, in RSA3, when I select the update mode as Delta, there is an error produced when executing the extractor checker. This generic extractor is delta-enabled and the delta is working in BI.
    So, why is it that it works only when select F update mode which is for full load?
    regards
    Bass

    Hi,
    You can only chcek delta in RSA3 if its property is maintained in RSA2 t-code which won't be there for your generic data-source.
    Hi,
    Goto the tcode RSA2 and check the extraction tab for your data-source if the checkbox for "Delta Test Proccess" is ticked then you should be able to do the same in RSA3 otherwise you cant.
    Regards,
    Arminder Singh

  • Basic customizing for COPA extractors

    Hi,
    we are working on account-bassed CO-PA extractors of SAP ECC 6.0 in order to be able to analize finance data in BW7.0.
    We are having problems with the extractor so, I need help for the basic customizing of COPA because we are having the following errors:
    Error KM 443: No profile has been assigned (TKA01-CVPROF) to controlling area HHSC.
    Error GP 526: Version 0 is not set up for controlling area CO = FR01.
    Any help will be welcome.
    Best regards.

    Hi Monica
    There is a whole bunch of BCsets which have been arranged in a heirarchical order as per the way they should be implemented in the standard system. They have all the settings to set up WH 0001 with structure, product, HU etc. The main BC set which has this is '/SCWM/BASICS'. This is a heirarchial BC set which has all the required config step by step.
    Further more there are specific BC sets for setting up the standard config for inbound and outbound deliveries - '/SCWM/DLV_INBOUND' & '/SCWM/DLV_OUTBOUND'.
    You can use these to get the basic config in place.
    Hope this helps.
    Thanks and regards
    Deepak Joshi

  • 0FC_OP_01 extractor issues- DFFKKOPBW data not matching with

    Hi All
    We have an issue with the extractor 0FC_OP_01. Our business is comparing the values in
    R/3 report u2013 G/L Account Balance Display (t-code S_ALR_87012277)   with the
    Open Items by GL Account report in BW .(actually these values in the BW report are coming from DFKKOPBW table in R/3) .
    But since august, the R/3 G/L account balance report is not matching with the DFKKOPBW table balances. So bottom line the extractor 0FC_OP_01 is doing something wrong when populating the DFKKOPBW table  which is causing these two reports to be out of balance
    Did anybody face this kind of issue before? Please Advise.
    FYI : We are following the same procedure to populate the DFKKOPBW table as in the below article.
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a9996115-0b01-0010-b2b2-d9de0170a425;jsessionid=%28J2EE3417800%29ID0001499250DB01896329908162586522End
    Thanks
    KPK

    In my case the Cube/PSA data itself is not matching with the R/3 report data. 
    Basically we run a job in R/3 in t-code FPBW with a Date id and Indentification. This job will pull the entries from base table DFKKOP into DFKKOPBW table .Then FRom this DFKKOPBW table data is loaded into PSA/Cube.
    Here in my case the data in table DFKKOPBW itself is not matching with the R/3 report -  G/L Account Balance Display (t-code S_ALR_87012277)) .
    I am following the same procedure to run the JOb in T-code FPBW to populate the DFKKOPBW table as listed in the document at the above link.  Moreover this difference in balances is occuring only starting from August ..Till July the balances in DFKKOPBW tally with the R/3report.
    Please advise ..
    Thanks
    KPK

  • Enhance CRM extractor for BW

    Hi all,
      To enhance CRM extractors we enhance the BDoc and then used the BADI CRM_BWA_MFLOW or CRM_BWA_SFLOW whichever is applicable to extract the data for the enhanced fields and fill the data source.
    Also we go to transaction RSA6 enhance the datasource structure.
    Now my basic question is why User exists are also enhanced. The procedure is
    In transaction RSA6 select the datasource structure and choose the menu "Function enhancment". This goest to CMOD transaction and there the user exit "EXIT_SAPLRSAP_001" is enhanced
    Could someone explain me why some coding is done in the user exit when the data which needs to be send from the BDoc is already filled in the badi implementation. When does this user exit actually used. In what scenarios do we use this user exit along with the badi implementation.
    Any idea. Thanks for the continued support and I wish "Happy new year" to all of you.
    Thanks in advance
    Jothi

    Hi all,
      To enhance CRM extractors we enhance the BDoc and then used the BADI CRM_BWA_MFLOW or CRM_BWA_SFLOW whichever is applicable to extract the data for the enhanced fields and fill the data source.
    Also we go to transaction RSA6 enhance the datasource structure.
    Now my basic question is why User exists are also enhanced. The procedure is
    In transaction RSA6 select the datasource structure and choose the menu "Function enhancment". This goest to CMOD transaction and there the user exit "EXIT_SAPLRSAP_001" is enhanced
    Could someone explain me why some coding is done in the user exit when the data which needs to be send from the BDoc is already filled in the badi implementation. When does this user exit actually used. In what scenarios do we use this user exit along with the badi implementation.
    Any idea. Thanks for the continued support and I wish "Happy new year" to all of you.
    Thanks in advance
    Jothi

  • Filling the 2LIS_02_SCL extractor.

    Hi experts,
    I am an abap programmer but i am now starting working on a BW project to become a junior BW consultant.
    I am now trying to fill the extractor 2LIS_02_SCL. Qhen i go to the RSA3 transaction on the R3 sistem, i see that it is now empty. How can i fill it on the r3 system? it is the first time i'm doing this, excuse me if the quation is too basic.I'll later charge this data to the BW system.
    Thank you very much!

    Hi
    Please have a look at the below url..it gives an idea how to go with LO extraction
    LO step by step procedure
    Hope it helps
    Thanks,
    Teja

  • R/3 Table from Extractors

    Hi guys,
    can anyone tell me how can I find R/3 Table names from Extractors.I have already gone through some previous threads about it... looking at RSA2 or Debuging Extraction from RSA3 does not help that much, does it?? At least I wasnt able to find the coresponding R/3 Table name, maximum information there is for domain field, no Table name is specified....is there any decent way to find it??( I have already looked at the Functional Modules and Structures for the DS) .......any help will be highly appritiated.....Thanks in advance

    Hi,
    just some hints to use the trace properly:
    - call rsa3 with your datasource; enter 1 call and 1 record per call, press enter
    - only then start your trace in another session
    - execute the extraction in your rsa3 session
    - stop the trace and dislay it
    - from the menu Goto, summary
    - position cursor on first row and pressF6; position the cursor on the last row and hit the button select end (F6 again doesn't work...) in order to select everything
    - then hit summarize and acknowledge the message.
    You should now see something like the following (I ran it for 0MATERIAL_ATTR):
    Tcode/prog    Table                  SQL op  Accesses      Recs.       Time Percent                                                                               
    BALDAT                    INS         1          3     15,680     3.1
                   BALHDR                    INS         1          1     37,086     7.3
                   ROMDDELTA                 SEL         1          1        634     0.1
                   ROOSOURCET                SEL         1          6      1,374     0.3
    RSA3          BALSUB                    SEL         1          1      1,504     0.3
    RSA3          DD01L                     SEL        52        226     56,237    11.0
    RSA3          DD02L                     SEL         4          6      3,556     0.7
    RSA3          DD02T                     SEL         4          6      3,105     0.6
    RSA3          DD03L                     SEL         2        262      7,456     1.5
    RSA3          DD04L                     SEL        52        254     72,628    14.3
    RSA3          DD04T                     SEL        52        254     58,820    11.6
    RSA3          DOKIL                     SEL         4          1     24,326     4.8
    RSA3          MARA                      SEL         1         57     48,066     9.4
    RSA3          RODCHABAS                 SEL         1          1     17,044     3.3
    RSA3          ROMDDELTA                 SEL         3          3      2,083     0.4
    RSA3          ROOSFIELD                 SEL         1        126      1,844     0.4
    RSA3          ROOSOURCET                SEL         3         18      3,362     0.7
    RSA3          RSFHGENTD                 SEL         1          1    108,445    21.3
    RSA3          RSSGTPDIR                 SEL         1          1     13,853     2.7
    RSA3          TRDIR                     SEL         1          1     10,906     2.1
    RSA3          UST12                     SEL         4          2     15,539     3.1
    RSA3          VARID                     SEL         4          0      2,867     0.6
    ST05          TFDIR                     SEL         2          2      2,671     0.5                                                                               
    Total                                             197      1,233    509,086   100.0
    Now of course somebody who has quite knowledge about R/3 tables will immediately analyze the following:
    BALx are logs tables
    ROx and RSx are usually BW 1plug-in system tables related to datasources, extraction and delta info...
    DDx are ABAP dictionary tables
    xDIR are usually related to ABAP code function modules/report
    USx user master
    VARID variants
    If one doesn't know, simply select the table list with ctrl-y, open SE16 with DD02T table, select language EN and paste the list of tables in the TABNAME selection screen; you'll get the following:
    TABNAME                          DDTEXT                                                                               
    BALDAT                           Application Log: Log data                                 
    BALHDR                           Application log: log header                               
    BALSUB                           Application log: sub-objects                              
    DD01L                            Domains                                                   
    DD02L                            SAP tables                                                
    DD02T                            R/3 DD: SAP table texts                                   
    DD03L                            Table Fields                                              
    DD04L                            Data elements                                             
    DD04T                            R/3 DD: Data element texts                                
    DOKIL                            Index for Documentation Table DOKH                        
    MARA                             General Article Data                                      
    RODCHABAS                        InfoObjects / basic characteristics in the source system  
    ROMDDELTA                        BW: Assignment DataSource - Changer Pointer               
    ROOSFIELD                        DataSource Fields                                         
    ROOSOURCET                       Texts for an OLTP source                                  
    RSFHGENTD                        Generated Routines for Data Extraction of Transaction Data
    RSSGTPDIR                        BW generation tool: Directory of the generated programs   
    TFDIR                            Function Module                                           
    TRDIR                            Generated Table for View TRDIR                            
    UST12                            User master: Authorizations                               
    VARID                            Variant directory                                         
    Moreover you can goto DD02L and perform the same; the important field here is CONTFLAG:
    "pasted from the perf assistant
    Delivery class
    The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems.
    The delivery class is also used in the extended table maintenance.
    There are the following delivery classes:
    A: Application table (master and transaction data).
    C: Customer table, data is maintained by the customer only.
    L: Table for storing temporary data.
    G: Customer table, SAP may insert new data records, but may not overwrite or delete existing data records.
    E: System table with its own namespaces for customer entries. The customer namespace must be defined in table TRESC.
    S: System table, data changes have the same status as program changes.
    W: System table (e.g. table of the development environment) whose data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL, etc.).
    The selection on DD02L give the following
    TABNAME                        TABCLASS CLIDEP CONTFLAG
    BALDAT                         TRANSP   X      L      
    BALHDR                         TRANSP   X      L      
    BALSUB                         TRANSP          E      
    DD01L                          TRANSP          W      
    DD02L                          TRANSP          W      
    DD02T                          TRANSP          W      
    DD03L                          TRANSP          W      
    DD04L                          TRANSP          W      
    DD04T                          TRANSP          W      
    DOKIL                          TRANSP          E      
    MARA                           TRANSP   X      A      
    RODCHABAS                      TRANSP          E      
    ROMDDELTA                      TRANSP          E      
    ROOSFIELD                      TRANSP          E      
    ROOSOURCET                     TRANSP          E      
    RSFHGENTD                      TRANSP          L      
    RSSGTPDIR                      TRANSP          L      
    TFDIR                          TRANSP          W      
    TRDIR                          VIEW                   
    UST12                          TRANSP   X      E      
    VARID                          TRANSP   X      E      
    from the above screen, the only table populated with application data is MARA.
    The above might not work for all datasources but for most of them.
    hope this helps....
    Olivier.

  • Delta Extractor Is not picking changed values

    Hi All,
    When the values or texts in a PO are changed the delta extractor is picking up the changed values as deltas  (provided the changes where done in PO <b>Header</b> or <b>Item Overview</b>) but when a PO values or text that are changed in the <b>Item Details</b> the delta mechanism is not picking up the changed values (the fields whose values are changed were initially not in the LO Cockpit Extractor they where added and the values to these fields are populated using an ABAP Program)
    Is there a reason that Delta mechanism doesn't work for fields that are not delivered by the SAP Extractor or do we need to modify the code in order to collect these changed values by Delta Mechanism (Direct Delta as the Update Mode).
    Please let me know if anybody came across the same problem .
    Thank you all in advance.
    Regards,
    Dhanam

    Hi,
    this is another story.....
    You'll have to
    - enhance the PO items table (EKPO) with your fields
    - activate the right customer exit for purchase orders (search in SMOD; or in this forum..) and populate your fields during this exit. if the field needs to be maintainable by the R3 user, you'll have find a SAP exit (again SMOD) in order customize one of the screen and populate your fields in R3.
    - use another exit to populate the new fields to LO delta queue
    - enhance your BW extract structure (done)
    - and so on...
    As you can imagine, the above get quite more complicated (an expert in MM shall support you) and it needs to be approved by the PM since you'll modify R3.
    But that's basically it!
    hope this helps...
    Olivier.

  • Extractor for Material Characteristics - Variants

    Hello Gurus,
    There are few characteristics that we have configured in ECC system for Materila. If you go to MM01 or MM03-> BASIC DATA 2 -> Client Specific configuration -> There is an option of creating a Cross-Plant CM. You can create additional characteristics once you click the Configure Variant button. There are values that are assigned to the Characteristic Value Assignment.
    I would like to know is there a Standard Extractor, that gets these characteristics.
    Thanks in advance
    Full points to right answers

    Thanks for your reply again.
    The following are the parameters:-
    Basis Datasource : 0MATERIAL_ATTR
    Client: 100
    Class Type: 001 (Material Class) It does not allow me to select any other class
    Obj Table: MARA
    Datasource Type: ATTR
    Datasource : 1CL_OMAT001
    And then I double click on characteristic, to add my characteristics.
    The system generates a TEXT DATASOURCE for individual text characteristics, which when using RSA3 gets the relevant data.
    But when I execute the datasource 1CL_OMAT001, it does not retrieve any data.
    Just to clarify: The SBIW node says "Maintain Data Sources for Classification Data".
    Does it mean, it will extract data from the CLASSIFICATION tab of the MM03.
    B'cas I am interested in the "BASIC DATA 2" tab -> Client Specific Config-> Configure Variant (button).
    Thanks

  • Extractor for Planned order

    Hi Experts,
    I am looking for the stabdard extractor for the Planned order, Basically I need the fields from the table PLAF.
    Please let me know any standard extractor available or any extractor need to enhance.
    Thanks
    sai

    Hi Sai,
    Take a look at 2LIS_04_P_MATNR and see if it is usefull:
    http://help.sap.com/saphelp_nw70/helpdata/en/88/7fc73c0c52085be10000000a114084/frameset.htm
    Else it seems that you should create a generic extractor directly on the table according to this thread:
    Re: Extractors for Planned orders and Proces Orders
    Hope this helps.
    BR
    Stefan

  • Use of BI Extractors in CRM ?

    Hello All,
    I am a CRM consultant with no knowledge of BI.
    I am currently trying to look for options for reporting for CRM Interaction center and would like to know if we have standard BW extracters available to report the time stamps for change of statuses and categories in CRM Transaction.
    l would like to report how much time the transaction spent on each status and for how long was one specific partner attahed to the transaction, etc... Basically trying to extract time data for each stage through the life cycle of a transaction...
    Is this possible... if yes.. can you pls direct me to some material that I can refer to ...
    Thanks and Regards,
    Farhad.

    There is a standard extractor for Interaction Center statistics. The InfoSource is  0CRM_CIC_CTI_1 that is based on DataSource 0CRM_CIC_CTI.
    The flows for CRM Interaction Center analysis standard content available can be view on the SAP Help Portal at [http://help.sap.com/saphelp_nw70/helpdata/en/ee/be7e4050336e1de10000000a1550b0/frameset.htm]

  • How to use Microsoft SSIS to communicate with SAP Extractors? Is XI a way?

    Hello Extraction Experts!
    here is a challange for you:
    Our customer wants to pull GL Data from ECC6 as well as other various R3 Special Ledgers into a database (Not SAP BW at this point in time!), which can then provide the data to a 3rd party tax calculation tool.
    Until we are able to move to SAP BW we would like to use the delta enabled General Ledger extractors to pull the data into SQL Server by using MS SSIS (Event Handler). The reason for this is that the standard extractors are
    a) delta enabled and
    b) provide data enhancements which otherwise we would have to rebuild. (like currency transformations or calculation of the cumulated balance)
    So the big question is now how can Microsoft SQL Server with SSIS  be configured in such a way that it can communicate with the standard extractors? All settings which are in the Infopackage need to be configurable (Data selection, update mode settings for full vs. delta request, schedule and so on).
    The extractors use Services API, iDocs, RFC.
    What exaclty needs to be rebuild and how? Is XI an option here? If we dont extract the data in the wway SAP does it it will be very difficult to move to SAP lateron.
    Thanks for all your comments and help.
    kind regards,
    Marko

    Interesting
    Of course the easiest way to do it is to install a GL DSO on BW extract the data into there and then extract the data out of BW
    However to do this you will need hardware and an additional license to extract from the BW system (it does cost quite a bit for the license - but it should be discountable)
    The idea of using the delta extractors is fine - but to be quite honest the logic in the FI extractors can easily be built into a ABAP to dump the data out to a flat file
    That will be cheapest option without any doubt - not the most fancy but definately cheaper
    So I would approach it as - take the GL4 extractor code, hack it and write the output to a flat file.
    The GL4 extractor does basically this..
    read bwom_timestamp t get the last timestamp selected up to
    read bwom_settings to get the safety mechanisms (ie how the timestamps should be manipulated)
    loop around a datapackage size
       select * from bkpf where cpudat between two datetimestamps (from above)
         select from bseg for those records
         read into an itab and manipulate the data
         send package to BW
    endloop
    loop around a datapackage size
       select from bwfi_aedat where change time between datetimestamps
         select from bkpf/bseg for those records
         read into an itab and manipulate the data
         send package to BW
    endloop
    update the timestamp table with the timestamps used
    Now you will need to have some sort of table in your source application which will resolve the duplicates - as GL transactions can be modified and FI does not provide a before and after image - ie you only get the after image

Maybe you are looking for