No Records in RSA7

Hi Gurus
I have new ECC system connected to BI 7.0 , I have activated LO datasources and also filled up set up tables but when I go to RSA7 there is no records( I have also tried to run LIS job(V3 Job) but no records/Datasource in RSA7).
would you pl advise what can be wrong?

Hi Kris,
RSA7 is the delta queue which doesn't gets data from the setup tables. The setup tables are meant for full loads. When you run the V3 job, it transfers data from lbwq to RSA7. So, check if you have any data in lbwq because if you don't have anything there, then the V3 job won't transfer anything to RSA7. Also, make sure that a transaction is actually being posted on the R/3 side which is then recorded in lbwq and then when you run V3, it gets transferred to RSA7.
Hope it helps. Assiging points is the way of saying thanks at SDN.
Thanks,
Rishi

Similar Messages

  • No.of transferred records do not match with delta records in RSA7

    Hi,
    The full update was failing since a number of days in 0vendor because of error in the source system. So I did an initialize with data transfer and corrected the PSA data and updated it using scheduler in the infoobject. In this case the number of transferred records was 24300 and added records was 0.Next I executed the delta infopackage and was expecting 0 records,since there were 0 records in rsa7. But I got 16000 records.Can you explain me why this happened?
    Regards,
    Shalaka

    Hi Shalaka,
    In which version of SAP you are working?
    You might want to have a look at the table BDCP2 which is a different table that handles the delta mechanism for the change pointers.
    You can reset the processing status using the program RSA1BDCP ex with following entries.
    Now, coming to your issue - to verify the initial loads I am listing some basic checks(step by step).
    You can give it a try in Dev/QAS if you have any restrictions in Prod.
    1. Check and verify if the RSA7 delta queue is present.
    2. In BW system, delete the INITIALIZATION request from infopackage - This should delete the delta queue from RSA7 in ECC system. (I am not 100% sure about this so try this once)
    3. Re-initialize the datasource from BW system and note the no. of incoming records in BW. This should match with LFA1 entries.
    4. Check the delta queue in RSA7 - There should be a new delta queue created
    5. Start the Delta load - The should not be any records coming in to BW
    6. Check the entries in table BDCP2 and its process indicator.
    7. Create a new vendor from XK01 and check the entry again in BDCP2 table.
    8. Run the delta again in BW and this time delta should have the newly created vendor.
    Also be aware that since its a master data datasource and deals with change pointers you will not see any entries in RSA7.
    A possible reason I could think of you getting 16000 records in delta is because you might have initialize the datasource is past and then started the FULL loads. So the deltas actually started accumulated in BDCP2 with processing status as BLANK and then when you triggered delta again back now all the historical deltas are processed.
    This apply with BDCPV too if you are on older version of SAP.
    Did you tried running delta's multiple times - you should not face any delta records when the processing status of change pointers is set to 'Processed' i.e. 'X'.
    PS: You can find the message type for 0VENDOR_ATTR in ROOSGEN table. This will be useful in looking at table BDCP2.
    Please let me know if there are any questions.
    Thanks
    Amit

  • Data source was activated and replicated but not showing up in RSA7.

    Hello,
    Data source was activated and replicated but not showing up in RSA7.  At what point does the data source appear in the Delta Queue?
    Thanks

    Hi,
    for LO,LIS,generic,FI data sources, delta records come from delta queue.
    if u run the INIT in BW whether it may be success or not delta queue will be maintained in RSA7. and u can check the records in RSA7 or smq2.
    when the init request goes to R/3 then it will maintains delta queue in RSA7.
    assign points if it helps,
    thanks,
    pavan.

  • Deltas are not coming to RSA7 from SM13

    Hi All,
    In BW i am not getting Delta's for 2LIS_02 Datasources,
    I have checked in RSA7 it is showing 0 Records, but in SM13 there are many V2 Processed Jobs.
    Please can anybody help me how to get Delta's to RSA7, this problem is persist since 1 week.
    Regards,
    Kiran

    Hi Praveen,
    I have run that, still i am not getting  records in RSA7.
    I have followed like this, Please correct me if i am wrong
    Gone to LBWE, Selected Job Control towards 02, 
    Maintained Start Data is Immediate in Job Parameter,
    And Scheduled Job from Job Control,
    When i checked in SM37, there is no job, Only one job is in Released state for Tomorrows load.
    Please let me know your views on this.
    Regards,
    Kiran

  • RSA7 to BW data fetch problem

    Hi Guys,
    I am extracting data from RSA7 to BW with delta update.
    in RSA7 tcode I can see column Total is populated with some entries means it has records, when I tried to see these records
    in Queue-> Display data entries->Update mode (Delta update) I don't see any records but when I used (Delta Repitition)
    as a update mode I am able to see the records.
    But when I am doing Delta update to BW it ends with 0 Records and RSA7 total column shows 0 entry.
    What could  be the problem?
    Thanks & Regards
    Deepak Chaavn.

    Hi
    See
    https://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
    Checking the Data using Extractor Checker (RSA3) in ECC Delta Repeat Delta etc...
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/80f4c455-1dc2-2c10-f187-d264838f21b5&overridelayout=true 
    Data Flow from LBWQ/SMQ1 to RSA7 in ECC and Delta Extraction in BI
    http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/d-f/data%20flow%20from%20lbwq_smq1%20to%20rsa7%20in%20ecc%20and%20delta%20extraction%20in%20bi.pdf
    Thanks
    Reddy

  • Urgent(Issue in RSA7 and SMQ1)

    We have two data sources 0CRM_OPPT_H and 0CRM_OPPT_I are in RSA7 and
    we deleted queues manually for these data source in SMQ1. Whenever we
    dochanges to records related to these data sources that changes we can
    able to see in RSA3 and Data base tables but there is no change in
    number of records in RSA7 and no Queue created automatically in SMQ1.
    We reinitialized the data source and scheduled it. We can able to
    see records when we do Init scheduling and zero records for Delta
    scheduling even after we did some changes in CRM side records. Delta is
    not picking up in BI side and we are not able to see that changes in
    RSA7 and also SMQ1 for these data sources in CRM side.
    We are testing this issue in QA and DEV which are SP14 upgrade
    systems. We tested in staging which is SP9 system; here I deleted
    Queues related to these data sources (0CRM_OPPT_H and 0CRM_OPPT_I) in
    SMQ1 and automatically the data sources deleted in RSA7. We
    reinitialized the data source and scheduled it. We did some changes to
    records related to these data sources and we can see the entries in
    RSA7 and SMQ1.

    Whenever you make a change in a Delta Datasource, after you reactivated and replicated in BW, the only way to reflect the changes in the queue is to reinitialize it.
    If you're planning to reinitialize, it doesn't have any impact if you delete the specific queue in RSA7... However, it's always a good practice to have those queues emptied before making any changes so you don't leave behind records with errors. But that has to be done before the changes.
    Hope it helps.
    Regards,
    Luis

  • Missing records in BW

    Hi friends,
    We load sales order daily in our Quality system using a process chain, but lately we are facing a strange issue. The records in BW rae not matching in R/3.
    EX: on 17.10.2007 in VBAK table there are around 6500 Orders created (Created on), the same will be loaded to our BW ODS without any transformation or restrictions, so we should get the same number of records. Instead we got 100 records only.
    This missing records is not happening every day. It happened in the 1st week of OCt and also on 17th of Oct rest other days its OK.
    I wanted to know if anyone of u have faced similar issue? if yes  how did u solve ( Filling up of setup tables for the missing records is not the solution), what i am looking at is is there any programs which deletes records either from the LBWQ or RSA7?.
    Your help is very much needed.
    Thanks in advance.
    BN

    Hi Manoj,
    Thanks a lot for ur quick reply. We are loading data for Header, Item and conditions in BW, we are not doing any transformations anywhere from R/3 BW, its all 1-2-1 mappings.
    We have been loading this for last 2 yrs, it suddenly started misbehaving. I suspect there must be some job which might be deleteing the records from RSA7, but im not sure if there is any prog or job which does this.
    Thanks
    BN

  • Missing records in BW Production

    In BW production system, while running reports, we were able to identify few records loaded on 11/1/2005 that are missing from BW.  The recurring theme is records entered on 11/1/2005 in PA R/3, are not loaded(delta) in the ZCOPAE001 custom cube in BWP.
    We checked the TR & UR there were no issues.
    PSA check was also done. Perfect.
    records in PSA - 717
    records loaded in the data target - 717
    I don't know what checks to be done in the source system.
    or
    Clues to proceed further..
    It would be great, if some one will share the information/steps. Resolution of this issue is urgent. Please help me.

    Hi Manoj,
    Thanks a lot for ur quick reply. We are loading data for Header, Item and conditions in BW, we are not doing any transformations anywhere from R/3 BW, its all 1-2-1 mappings.
    We have been loading this for last 2 yrs, it suddenly started misbehaving. I suspect there must be some job which might be deleteing the records from RSA7, but im not sure if there is any prog or job which does this.
    Thanks
    BN

  • Delta not reflecting in Queue (RSA7)

    For testing purpose we posted some FI documents in R/3(Devlopment) side using tcode F-02
    after that we used tcode RSA3
    DataSource: 0FI_GL_4
    Update mode: D
    Target System: BIWXYZ
    after extraction we could view the posted enteries...
    after 1 day(As FI data gets available in queue after 24hrs) we tried to view the same in delta queue using tcode RSA7 but its not being reflected over there
    any clue???

    Hello Alok,
    RSA3 picks the record from the delta queue which in turn for the FI data source shows the records which are part of delta.
    FI data source do not use the delta queue and store records into that like LO data source
    There are delta is triggered by the API's....that is at the time when the infopackage is scheduled in BW the delta entries are pulled based on timestamp and before that they are not stored anywhere separately.
    So the entry in delta queue for FI data sources tells that init is done for the data source and delta can be scheduled...but there is no such mechnisam or periodic jobs to push the records from the FI tables to extractors as in the case of LO data sources and where we see the records in RSA7...therefor wwe dont see records in delta queue for the FI data sources and this is how FI data sources are designed.
    once the delta is scheduled then the records are kept  for the purpose of repeat delta and this most probably you can see if you use the delta repetition in RSA7 display...but i think its not possible even there..
    Thanks
    Ajeet

  • 0HR_PT_1 , delta records are not extracting.

    HI,
    We are done delta initialization for 0HR_PT_2, and 0HR_PT_1
    After when we try to pull delta it coming 0 Records,
    In RSA7 delta record is showing 0,
    We are maintaining the  T569R table also.
    Can you please suggest me some solution on this
    Many Thanks
    Shashi

    hi,
    chk whether the users were allowed to do posts after the init loads.chk if any new records in the HR tables after ur init loads.
    All R/3 Tables
    http://www.sap-img.com/sap-download/sap-tables.zip
    HR data source and other objects
    http://help.sap.com/bp_biv170/
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/505351fe-ec8c-2910-c5b5-a43bbf53f6fc
    http://help.sap.com/saphelp_nw04/helpdata/en/2a/77eb3cad744026e10000000a11405a/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/63/351e3c6a2fc036e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/f1/28a63afb214549e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/acb3392f65f530e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/3d/36bf39f6335871e10000000a114084/content.htm
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    http://www.sap-img.com/sap-hr.htm
    Ramesh

  • SAP BI INTERVIEW QUESTIONS

    Hi Friends,
    I was  face some Interview.
    Please send answers to the questions?
    How many data Fields  and key fields we can create in DSO?
    You can overwrite key fields or Data Fields?
    Which up date we use in Delta queue extraction( v1 or v2 or v3)
    Which message we get when transported request is failed?
    what is the Structural difference between Infoucbe and DSO
    Data Loading is taking huge time when we extract data from source system to BI system/ how to solve?(Before it took 3-4 Hours now data loading takes 4 days)

    What is the difference between Display Attribute and
    Navigational Attribute? How to make display attribute and navigational
    attribute?
    How to load flat file data?
    How to load Hierarchy file data?
    What is HACR?
    How to maintain HACR?
    If any issue in HACR then how to resolve the issue?
    What is Baby Cube?
    Why we are creating Aggregates?
    What is the use of Aggregates?
    Is there
    any particular field on that we can create Aggregates or we can maintain
    Aggregate on any field?
    What is
    the different DSO available? And what is the difference between those DSO?
    What is
    replacement path?
    What are
    the extractor types?
    • Application Specific
    o BW Content FI, HR, CO, SAP CRM, LO Cockpit
    o Customer-Generated Extractors
    LIS, FI-SL, CO-PA
    • Cross Application (Generic Extractors)
    o DB View, InfoSet, Function Module
    2. What are the steps involved in LO Extraction?
    • The steps are:
    o RSA5 Select the DataSources
    o LBWE Maintain DataSources and Activate Extract Structures
    o LBWG Delete Setup Tables
    o 0LI*BW Setup tables
    o RSA3 Check extraction and the data in Setup tables
    o LBWQ Check the extraction queue
    o LBWF Log for LO Extract Structures
    o RSA7 BW Delta
    Queue Monitor
    3. How to create a connection with LIS InfoStructures?
    • LBW0 Connecting LIS InfoStructures to BW
    4. What is the difference between ODS and InfoCube and MultiProvider?
    • ODS: Provides granular data, allows overwrite and data is in transparent
    tables, ideal for drilldown and RRI.
    • CUBE: Follows the star schema, we can only append data, ideal for primary
    reporting.
    • MultiProvider: Does not have physical data. It allows to access data from
    different InfoProviders (Cube, ODS, InfoObject). It is also preferred for
    reporting.
    5. What are Start routines, Transfer routines and Update routines?
    • Start Routines: The start routine is run for each DataPackage after the data
    has been written to the PSA and before the transfer rules have been executed.
    It allows complex computations for a key figure or a characteristic. It has no
    return value. Its purpose is to execute preliminary calculations and to store
    them in global DataStructures. This structure or table can be accessed in the
    other routines. The entire DataPackage in the transfer structure format is used
    as a parameter for the routine.
    • Transfer / Update Routines: They are defined at the InfoObject level. It is
    like the Start Routine. It is independent of the DataSource. We can use this to
    define Global Data and Global Checks.
    6. What is the difference between start routine and update routine, when, how
    and why are they called?
    • Start routine can be used to access InfoPackage while update routines are
    used while updating the Data Targets.
    7. What is the table that is used in start routines?
    • Always the table structure will be the structure of an ODS or InfoCube. For
    example if it is an ODS then active table structure will be the table.
    8. Explain how you used Start routines in your project?
    • Start routines are used for mass processing of records. In start routine all
    the records of DataPackage is available for processing. So we can process all
    these records together in start routine. In one of scenario, we wanted to apply
    size % to the forecast data. For example if material M1 is forecasted to say
    100 in May. Then after applying size %(Small 20%, Medium 40%, Large 20%, Extra
    Large 20%), we wanted to have 4 records against one single record that is
    coming in the info package. This is achieved in start routine.
    9. What are Return Tables?
    • When we want to return multiple records, instead of single value, we use the
    return table in the Update Routine. Example: If we have total telephone expense
    for a Cost Center, using a return table we can get
    expense per employee.
    10. How do start routine and return table synchronize with each other?
    • Return table is used to return the Value following the execution of start
    routine
    11. What is the difference
    between V1, V2 and V3 updates?
    • V1 Update: It is a Synchronous update. Here the Statistics update is carried
    out at the same time as the document update (in the application
    tables).
    • V2 Update: It is an Asynchronous update. Statistics update and the Document
    update take place as different tasks.
    o V1 & V2 don't need scheduling.
    • Serialized V3 Update: The V3 collective update must be scheduled as a job
    (via LBWE). Here, document data is collected in the order it was created and
    transferred into the BW as a batch job. The transfer sequence may not be the
    same as the order in which the data was created in all scenarios. V3 update
    only processes the update data that is successfully processed with the V2
    update.
    12. What is compression?
    • It is a process used to delete the Request IDs and this saves space.
    13. What is Rollup?
    • This is used to load new DataPackages (requests) into the InfoCube
    aggregates. If we have not performed a rollup then the new InfoCube data will
    not be available while reporting on the aggregate.
    14. What is table partitioning and what are the benefits of partitioning in an
    InfoCube?
    • It is the method of dividing a table which would enable a quick reference.
    SAP uses fact file partitioning to improve performance. We can partition only
    at 0CALMONTH or 0FISCPER. Table partitioning helps to run the report faster as
    data is stored in the relevant partitions. Also table maintenance becomes
    easier. Oracle,
    Informix, IBM DB2/390 supports table partitioning while SAP DB, Microsoft SQL
    Server, IBM DB2/400 do not support table portioning.
    15. How many extra partitions are created and why?
    • Two partitions are created for date before the begin date and after the end
    date.
    16. What are the options available in transfer rule?
    • InfoObject
    • Constant
    • Routine
    • Formula
    17. How would you optimize the dimensions?
    • We should define as many dimensions as possible and we have to take care that
    no single dimension crosses more than 20% of the fact table size.
    18. What are Conversion Routines for units and currencies in the update rule?
    • Using this option we can write ABAP
    code for Units / Currencies conversion. If we enable this flag then unit of Key
    Figure appears in the ABAP code as an additional parameter. For example, we can
    convert units in Pounds to Kilos.
    19. Can an InfoObject be an InfoProvider, how and why?
    • Yes, when we want to report on Characteristics or Master Data. We have to
    right click on the InfoArea and select "Insert characteristic as data
    target". For example, we can make 0CUSTOMER as an InfoProvider and report
    on it.
    20. What is Open Hub Service?
    • The Open Hub Service enables us to distribute data from an SAP BW system into
    external Data Marts, analytical applications, and other applications. We can
    ensure controlled distribution using several systems. The central object for
    exporting data is the InfoSpoke. We can define the source and the target object
    for the data. BW becomes a hub of an enterprise data warehouse.
    The distribution of data becomes clear through central monitoring from the
    distribution status in the BW system.
    21. How do you transform Open
    Hub Data?
    • Using BADI we can transform Open Hub Data according to the destination
    requirement.
    22. What is ODS?
    • Operational DataSource is used for detailed storage of data. We can overwrite
    data in the ODS. The data is stored in transparent tables.
    23. What are BW Statistics and what is its use?
    • They are group of Business Content InfoCubes which are used to measure
    performance for Query and Load Monitoring. It also shows the usage of
    aggregates, OLAP and Warehouse management
    http://www.ittestpapers.com/articles/713/3/SAP-BW-Interview-Questions---Part-A/Page3.html
    Communication Structure and Transfer
    rules
    • Create and InfoPackage
    • Load Data
    25. What are the delta options available when you load from flat file?
    • The 3 options for Delta Management with Flat Files:
    o Full Upload
    o New Status for Changed records (ODS Object only)
    o Additive Delta (ODS Object & InfoCube)
    Q) Under which menu path is the Test Workbench to be found, including in
    earlier Releases?
    The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
    Q) I want to delete a BEx query that is in Production system through request. Is
    anyone aware about it?
    A) Have you tried the RSZDELETE transaction?
    Q) Errors while monitoring process chains.
    A) During data loading. Apart from them, in process chains you add so many
    process types, for example after loading data into Info Cube, you rollup data
    into aggregates, now this rolling up of data into aggregates is a process type
    which you keep after the process type for loading data into Cube. This rolling
    up into aggregates might fail.
    Another one is after you load data into ODS, you activate ODS data (another
    process type) this might also fail.
    Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data
    packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything
    OK ---- Simulate update. (Here we can debug update rules or transfer rules.)
    SM50 à Program/Mode à Program à Debugging & debug this work process.
    Q) PSA Cleansing.
    A) You know how to edit PSA. I don't think you can delete single records. You
    have to delete entire PSA data for a request.
    Q) Can we make a datasource to support delta.
    A) If this is a custom (user-defined) datasource you can make the datasource
    delta enabled. While creating datasource from RSO2, after entering datasource
    name and pressing create, in the next screen there is one button at the top,
    which says generic delta. If you want more details about this there is a
    chapter in Extraction book, it's in last pages u find out.
    Generic delta services: -
    Supports delta extraction for generic extractors according to:
    Time stamp
    Calendar day
    Numeric pointer, such as document number & counter
    Only one of these attributes can be set as a delta attribute.
    Delta extraction is supported for all generic extractors, such as tables/views,
    SAP Query and function modules
    The delta queue (RSA7) allows you to monitor the current status of the delta
    attribute
    Q) Workbooks, as a general rule, should be transported with the
    role.
    Here are a couple of scenarios:
    1. If both the workbook and its role have been previously transported, then the
    role does not need to be part of the transport.
    2. If the role exists in both dev and the target system but the workbook has
    never been transported, and then you have a choice of transporting the role
    (recommended) or just the workbook. If only the workbook is transported, then
    an additional step will have to be taken after import: Locate the WorkbookID
    via Table RSRWBINDEXT (in Dev and verify the same exists in the target system)
    and proceed to manually add it to the role in the target system via Transaction
    Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
    3. If the role does not exist in the target system you should transport both
    the role and workbook. Keep in mind that a workbook is an object unto itself
    and has no dependencies on other objects. Thus, you do not receive an error
    message from the transport of 'just a workbook' -- even though it may not be
    visible, it will exist (verified via Table RSRWBINDEXT).
    Overall, as a general rule, you should transport roles with workbooks.
    Q) How much time does it take to extract 1 million (10 lackhs) of records into
    an infocube?
    A. This depends, if you have complex coding in update rules it will take longer
    time, or else it will take less than 30 minutes.
    Q) What are the five ASAP Methodologies?
    A: Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
    1. Project Preparation: In this phase, decision makers define clear project
    objectives and an efficient decision making process ( i.e. Discussions with the
    client, like what are his needs and requirements etc.). Project managers
    will be involved in this phase (I guess).
    A Project Charter is issued and an implementation strategy is outlined in this
    phase.
    2. Business Blueprint: It is a detailed documentation of your company's
    requirements. (i.e. what are the objects we need to develop are modified
    depending on the client's requirements).
    3. Realization: In this only, the implementation of the project takes place (development
    of objects etc) and we are involved in the project from here only.
    4. Final Preparation: Final preparation before going live i.e. testing,
    conducting pre-go-live, end user training etc.
    End user training is given that is in the client site you train them how to
    work with the new environment, as they are new to the technology.
    5. Go-Live & support: The project has gone live and it is into production.
    The Project team will be supporting the end users.
    Q) What is landscape of R/3 & what is landscape of BW. Landscape of R/3 not
    sure.
    Then Landscape of b/w: u have the development system, testing system, production system
    Development system: All the implementation part is done in this sys. (I.e.,
    Analysis of objects developing, modification etc) and from here the objects are
    transported to the testing system, but before transporting an initial test
    known as Unit testing
    (testing of objects) is done in the development sys.
    Testing/Quality system: quality check is done in this system and integration
    testing is done.
    Production system: All the extraction part takes place in this sys.
    Q) How do you measure the size of infocube?
    A: In no of records.
    Q). Difference between infocube and ODS?
    A: Infocube is structured as star schema (extended) where a fact table is
    surrounded by different dim table that are linked with DIM'ids. And the data
    wise, you will have aggregated data in the cubes. No overwrite functionality
    ODS is a flat structure (flat table) with no star schema concept and which will
    have granular data (detailed level). Overwrite functionality.
    Flat file
    datasources does not support 0recordmode in extraction.
    x before, -after, n new, a add, d delete, r reverse
    Q) Difference between display attributes and navigational attributes?
    A: Display attribute is one, which is used only for display purpose in the
    report. Where as navigational attribute is used for drilling down in the
    report. We don't need to maintain Navigational attribute in the cube as a
    characteristic (that is the advantage) to drill down.
    Q. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
    A: But how is it possible? If you load it manually twice, then you can delete
    it by requestID.
    Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
    Sure you can. ODS is nothing but a table.
    Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
    A) Yes of course. For example, for loading text and hierarchies we use
    different data sources but the same InfoSource.
    Q. BRIEF THE DATAFLOW IN BW.
    A) Data flows from transactional system to analytical system (BW). DataSources
    on the transactional system needs to be replicated on BW side and attached to
    infosource and update rules respectively.
    Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER
    RULES?
    Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
    FULL and DELTA.
    Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN
    WHAT IS THE PROCEDURE IN LO-COCKPIT?
    No LIS in LO cockpit. We will have datasources and can be maintained (append
    fields). Refer white paper
    on LO-Cockpit extractions.
    Q) Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
    A) Initially we don't delete the setup tables but when we do change in extract
    structure we go for it. We r changing the extract structure right, that means
    there are some newly added fields in that which r not before. So to get the
    required data ( i.e.; the data which is required is taken and to avoid
    redundancy) we delete n then fill the setup tables.
    To refresh the statistical data.
    The extraction set up reads the dataset that you want to process such as,
    customers orders with the tables like VBAK, VBAP) & fills the relevant communication
    structure with the data. The data is stored in cluster
    tables from where it is read when the initialization is run. It is important
    that during initialization phase, no one generates or modifies application
    data, at least until the tables can be set up.
    Q) SIGNIFICANCE of ODS?
    It holds granular data (detailed level).
    Q) WHERE THE PSA DATA IS STORED?
    In PSA table.
    Q) WHAT IS DATA SIZE?
    The volume of data one data target holds (in no. of records)
    Q) Different types of INFOCUBES.
    Basic, Virtual (remote, sap remote and multi)
    Virtual Cube is used for example, if you consider railways reservation all the
    information has to be updated online. For designing the Virtual cube you have
    to write the function module that is linking to table, Virtual cube it is like
    a the structure, when ever the table is updated the virtual cube will fetch the
    data from table and display report Online... FYI.. you will get the information
    : https://www.sdn.sap.com/sdn
    /index.sdn and search for Designing Virtual Cube and you will get
    a good material designing the Function Module
    Q) INFOSET QUERY.
    Can be made of ODS's and Characteristic InfoObjects with masterdata.
    Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
    In R/3 or in BW? 2 in R/3 and 2 in BW
    Q) ROUTINES?
    Exist in the InfoObject, transfer routines, update routines and start routine
    Q) BRIEF SOME STRUCTURES USED IN BEX.
    Rows and Columns, you can create structures.
    Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
    Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes &
    Characteristic values.
    Variable Types are
    Manual entry /default value
    Replacement path
    SAP exit
    Customer exit
    Authorization
    Q) HOW MANY LEVELS YOU CAN GO IN REPORTING?
    You can drill down to any level by using Navigational attributes and jump
    targets.
    Q) WHAT ARE INDEXES?
    Indexes are data base indexes, which help in retrieving data fastly.
    Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
    Help! Refer documentation
    Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
    No.
    Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
    KPI's indicate the performance of a company. These are key figures
    Q) AFTER THE DATA EXTRACTION
    WHAT IS THE IMAGE POSITION.
    After image (correct me if I am wrong)
    Q) REPORTING AND RESTRICTIONS.
    Help! Refer documentation.
    Q) TOOLS USED FOR PERFORMANCE TUNING.
    ST22, Number ranges, delete indexes before load. Etc
    Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
    There should be some tool to run the job daily (SM37 jobs)
    Q) AUTHORIZATIONS.
    Profile generator
    Q) WEB REPORTING.
    What are you expecting??
    Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
    Of course
    Q) PROCEDURES OF REPORTING ON MULTICUBES
    Refer help. What are you expecting? MultiCube works on Union condition
    Q) EXPLAIN TRANPSORTATION OF OBJECTS?
    Dev---àQ and Dev-------àP
    Q) What types of partitioning are there for BW?
    There are two Partitioning Performance aspects for BW (Cube & PSA)
    Query Data Retrieval
    Performance Improvement:
    Partitioning by (say) Date Range improves data retrieval by making best use of
    database [data range] execution plans and indexes (of say Oracle database engine).
    B) Transactional Load Partitioning Improvement:
    Partitioning based on expected load volumes and data element sizes. Improves
    data loading into PSA and Cubes by infopackages (Eg. without timeouts).
    Q) How can I compare data in R/3 with data in a BW Cube after the daily delta
    loads? Are there any standard procedures for checking them or matching the
    number of records?
    A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the
    number of records extracted. Then go to BW Monitor to check the number of
    records in the PSA and check to see if it is the same & also in the monitor
    header tab.
    A) RSA3 is a simple extractor checker program that allows you to rule out
    extracts problems in R/3. It is simple to use, but only really tells you if the
    extractor works. Since records that get updated into Cubes/ODS structures are
    controlled by Update Rules, you will not be able to determine what is in the
    Cube compared to what is in the R/3 environment. You will need to compare
    records on a 1:1 basis against records in R/3 transactions for the functional
    area in question. I would recommend enlisting the help of the end user community
    to assist since they presumably know the data.
    To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute
    and you will see the record count, you can also go to display that data. You
    are not modifying anything so what you do in RSA3 has no effect on data quality
    afterwards. However, it will not tell you how many records should be expected
    in BW for a given load. You have that information in the monitor RSMO during
    and after data loads. From RSMO for a given load you can determine how many
    records were passed through the transfer rules from R/3, how many targets were
    updated, and how many records passed through the Update Rules. It also gives
    you error messages from the PSA.
    Q) Types of Transfer Rules?
    A) Field to Field mapping, Constant, Variable & routine.
    Q) Types of Update Rules?
    A) (Check box), Return table
    Q) Transfer Routine?
    A) Routines, which we write in, transfer rules.
    Q) Update Routine?
    A) Routines, which we write in Update rules
    Q) What is the difference between writing a routine in transfer rules and
    writing a routine in update rules?
    A) If you are using the same InfoSource to update data in more than one data
    target its better u write in transfer rules because u can assign one InfoSource
    to more than one data target & and what ever logic u write in update rules
    it is specific to particular one data target.
    Q) Routine with Return Table.
    A) Update rules generally only have one return value. However, you can create a
    routine in the tab strip key figure calculation, by choosing checkbox Return
    table. The corresponding key figure routine then no longer has a return value,
    but a return table. You can then generate as many key figure values, as you
    like from one data record.
    Q) Start routines?
    A) Start routines u can write in both updates rules and transfer rules, suppose
    you want to restrict (delete) some records based on conditions before getting
    loaded into data targets, then you can specify this in update rules-start
    routine.
    Ex: - Delete Data_Package ani ante it will delete a record based on the
    condition
    Q) X & Y Tables?
    X-table = A table to link material SIDs with SIDs for time-independent
    navigation attributes.
    Y-table = A table to link material SIDs with SIDS for time-dependent navigation
    attributes.
    There are four types of sid tables
    X time independent navigational attributes sid tables
    Y time dependent navigational attributes sid tables
    H hierarchy sid tables
    I hierarchy structure sid tables
    Q) Filters & Restricted Key figures (real time example)
    Restricted KF's u can have for an SD cube: billed quantity, billing value, no:
    of billing documents as RKF's.
    Q) Line-Item Dimension (give me an real time example)
    Line-Item Dimension: Invoice no: or Doc no: is a real time example
    Q) What does the number in the 'Total' column in Transaction RSA7 mean?
    A) The 'Total' column displays the number of LUWs that were written in the
    delta queue and that have not yet been confirmed. The number includes the LUWs
    of the last delta request (for repetition of a delta request) and the LUWs for
    the next delta request. A LUW only disappears from the RSA7 display when it has
    been transferred to the BW System and a new delta request has been received
    from the BW System.
    Q) How to know in which table (SAP BW) contains Technical Name / Description
    and creation data of a particular Reports. Reports that are created using BEx
    Analyzer.
    A) There is no such table in BW if you want to know such details while you are
    opening a particular query press properties button you will come to know all
    the details that you wanted.
    You will find your information about technical names and description about
    queries in the following tables. Directory of all reports (Table RSRREPDIR) and
    Directory of the reporting component elements (Table RSZELTDIR) for workbooks
    and the connections to queries check Where- used list for reports in workbooks
    (Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table
    RSRWBINDEXT)
    Q) What is a LUW in the delta queue?
    A) A LUW from the point of view of the delta queue can be an individual
    document, a group of documents from a collective run or a whole data packet of
    an application
    extractor.
    Q) Why does the number in the 'Total' column in the overview screen of
    Transaction RSA7 differ from the number of data records that is displayed when
    you call the detail view?
    A) The number on the overview screen corresponds to the total of LUWs (see also
    first question) that were written to the qRFC queue and that have not yet been
    confirmed. The detail screen displays the records contained in the LUWs. Both,
    the records belonging to the previous delta request and the records that do not
    meet the selection conditions of the preceding delta init requests are filtered
    out. Thus, only the records that are ready for the next delta request are
    displayed on the detail screen. In the detail screen of Transaction RSA7, a
    possibly existing customer exit is not taken into account.
    Q) Why does Transaction RSA7 still display LUWs on the overview screen after
    successful delta loading?
    A) Only when a new delta has been requested does the source system learn that
    the previous delta was successfully loaded to the BW System. Then, the LUWs of
    the previous delta may be confirmed (and also deleted). In the meantime, the
    LUWs must be kept for a possible delta request repetition. In particular, the
    number on the overview screen does not change when the first delta was loaded
    to the BW System.
    Q) Why are selections not taken into account when the delta queue is filled?
    A) Filtering according to selections takes place when the system reads from the
    delta queue. This is necessary for reasons of performance.
    Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has
    also been loaded successfully?
    It is most likely that this is a DataSource that does not send delta data to
    the BW System via the delta queue but directly via the extractor (delta for
    master data using ALE change pointers). Such a DataSource should not be
    displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
    Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the
    loading procedure from the delta queue?
    A) The impact is limited. If performance problems are related to the loading
    process from the delta queue, then refer to the application-specific notes (for
    example in the CO-PA area, in the logistics cockpit area and so on).
    Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as
    effective for the delta queue as for a full update. Please note, however, that
    LUWs are not split during data loading for consistency reasons. This means that
    when very large LUWs are written to the DeltaQueue, the actual package size may
    differ considerably from the MAXSIZE and MAXLINES parameters.
    Q) Why does it take so long to display the data in the delta queue (for example
    approximately 2 hours)?
    A) With Plug In 2001.1 the display was changed: the user has the option of
    defining the amount of data to be displayed, to restrict it, to selectively
    choose the number of a data record, to make a distinction between the 'actual'
    delta data and the data intended for repetition and so on.
    Q) What is the purpose of function 'Delete data and meta data in a queue' in
    RSA7? What exactly is deleted?
    A) You should act with extreme caution when you use the deletion function in
    the delta queue. It is comparable to deleting an InitDelta in the BW System and
    should preferably be executed there. You do not only delete all data of this
    DataSource for the affected BW System, but also lose the entire information
    concerning the delta initialization. Then you can only request new deltas after
    another delta initialization.
    When you delete the data, the LUWs kept in the qRFC queue for the corresponding
    target system are confirmed. Physical deletion only takes place in the qRFC
    outbound queue if there are no more references to the LUWs.
    The deletion function is for example intended for a case where the BW System,
    from which the delta initialization was originally executed, no longer exists
    or can no longer be accessed.
    Q) Why does it take so long to delete from the delta queue (for example half a
    day)?
    A) Import PlugIn 2000.2 patch 3. With this patch the performance during
    deletion is considerably improved.
    Q) Why is the delta queue not updated when you start the V3 update in the
    logistics cockpit area?
    A) It is most likely that a delta initialization had not yet run or that the
    delta initialization was not successful. A successful delta initialization (the
    corresponding request must have QM status 'green' in the BW System) is a
    prerequisite for the application data being written in the delta queue.
    Q) What is the relationship between RSA7 and the qRFC monitor (Transaction
    SMQ1)?
    A) The qRFC monitor basically displays the same data as RSA7. The internal
    queue name must be used for selection on the initial screen of the qRFC
    monitor. This is made up of the prefix 'BW, the client and the short name of
    the DataSource. For DataSources whose name are 19 characters long or shorter,
    the short name corresponds to the name of the DataSource. For DataSources whose
    name is longer than 19 characters (for delta-capable DataSources only possible
    as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
    In the qRFC monitor you cannot distinguish between repeatable and new LUWs.
    Moreover, the data of a LUW is displayed in an unstructured manner there.
    Q) Why are the data in the delta queue although the V3 update was not started?
    A) Data was posted in background. Then, the records are updated directly in the
    delta queue (RSA7). This happens in particular during automatic goods receipt
    posting (MRRS). There is no duplicate transfer of records to the BW system. See
    Note 417189.
    Q) Why does button 'Repeatable' on the RSA7 data details screen not only show
    data loaded into BW during the last delta but also data that were newly added,
    i.e. 'pure' delta records?
    A) Was programmed in a way that the request in repeat mode fetches both
    actually repeatable (old) data and new data from the source system.
    Q) I loaded several delta inits with various selections. For which one is the
    delta loaded?
    A) For delta, all selections made via delta inits are summed up. This means, a
    delta for the 'total' of all delta initializations is loaded.
    Q) How many selections for delta inits are possible in the system?
    A) With simple selections (intervals without complicated join conditions or
    single values), you can make up to about 100 delta inits. It should not be
    more.
    With complicated selection conditions, it should be only up to 10-20 delta
    inits.
    Reason: With many selection conditions that are joined in a complicated way,
    too many 'where' lines are generated in the generated ABAP
    source code that may exceed the memory limit.
    Q) I intend to copy the source system, i.e. make a client copy. What will
    happen with may delta? Should I initialize again after that?
    A) Before you copy a source client or source system, make sure that your deltas
    have been fetched from the DeltaQueue into BW and that no delta is pending.
    After the client copy, an inconsistency might occur between BW delta tables and
    the OLTP delta tables as described in Note 405943. After the client copy, Table
    ROOSPRMSC will probably be empty in the OLTP since this table is
    client-independent. After the system copy, the table will contain the entries
    with the old logical system name that are no longer useful for further delta
    loading from the new logical system. The delta must be initialized in any case
    since delta depends on both the BW system and the source system. Even if no
    dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you
    should expect that the delta have to be initialized after the copy.
    Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of
    processes?
    A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW
    queues only after informing the BW Support or only if this is explicitly
    requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
    Q) Despite of the delta request being started after completion of the
    collective run (V3 update), it does not contain all documents. Only another
    delta request loads the missing documents into BW. What is the cause for this
    "splitting"?
    A) The collective run submits the open V2 documents for processing to the task
    handler, which processes them in one or several parallel update processes in an
    asynchronous way. For this reason, plan a sufficiently large "safety time
    window" between the end of the collective run in the source system and the
    start of the delta request in BW. An alternative solution where this problem
    does not occur is described in Note 505700.
    Q) Despite my deleting the delta init, LUWs are still written into the
    DeltaQueue?
    A) In general, delta initializations and deletions of delta inits should always
    be carried out at a time when no posting takes place. Otherwise, buffer
    problems may occur: If a user started the internal mode at a time when the
    delta initialization was still active, he/she posts data into the queue even
    though the initialization had been deleted in the meantime. This is the case in
    your system.
    Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some
    entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What
    do these statuses mean? Which values in the field 'Status' mean what and which
    values are correct and which are alarming? Are the statuses BW-specific or
    generally valid in qRFC?
    A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read
    once either in a delta request or in a repetition of the delta request.
    However, this does not mean that the record has successfully reached the BW
    yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that
    the record has been written into the DeltaQueue and will be loaded into the BW
    with the next delta request or a repetition of a delta. In any case only the
    statuses READ, READY and RECORDED in both tables are considered to be valid.
    The status EXECUTED in TRFCQOUT can occur temporarily. It is set before
    starting a DeltaExtraction for all records with status READ present at that
    time. The records with status EXECUTED are usually deleted from the queue in
    packages within a delta request directly after setting the status before
    extracting a new delta. If you see such records, it means that either a process
    which is confirming and deleting records which have been loaded into the BW is
    successfully running at the moment, or, if the records remain in the table for
    a longer period of time with status EXECUTED, it is likely that there are
    problems with deleting the records which have already been successfully been
    loaded into the BW. In this state, no more deltas are loaded into the BW. Every
    other status is an indicator for an error or an inconsistency. NOSEND in SMQ1
    means nothing (see note 378903).
    The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
    Q) The extract structure was changed when the DeltaQueue was empty. Afterwards
    new delta records were written to the DeltaQueue. When loading the delta into
    the PSA, it shows that some fields were moved. The same result occurs when the
    contents of the DeltaQueue are listed via the detail display. Why are the data
    displayed differently? What can be done?
    Make sure that the change of the extract structure is also reflected in the
    database and that all servers are synchronized. We recommend to reset the
    buffers using Transaction $SYNC. If the extract structure change is not
    communicated synchronously to the server where delta records are being created,
    the records are written with the old structure until the new structure has been
    generated. This may have disastrous consequences for the delta.
    When the problem occurs, the delta needs to be re-initialized.
    Q) How and where can I control whether a repeat delta is requested?
    A) Via the status of the last delta in the BW Request Monitor. If the request
    is RED, the next load will be of type 'Repeat'. If you need to repeat the last
    load for certain reasons, set the request in the monitor to red manually. For
    the contents of the repeat see Question 14. Delta requests set to red despite
    of data being already updated lead to duplicate records in a subsequent repeat,
    if they have not been deleted from the data targets concerned before.
    Q) As of PI 2003.1, the Logistic Cockpit offers various types of update
    methods. Which update method is recommended in logistics? According to which
    criteria should the decision be made? How can I choose an update method in
    logistics?
    See the recommendation in Note 505700.
    Q) Are there particular recommendations regarding the data volume the
    DeltaQueue may grow to without facing the danger of a read failure due to
    memory problems?
    A) There is no strict limit (except for the restricted number range of the
    24-digit QCOUNT counter in the LUW management table - which is of no practical
    importance, however - or the restrictions regarding the volume and number of
    records in a database table).
    When estimating "smooth" limits, both the number of LUWs is important
    and the average data volume per LUW. As a rule, we recommend to bundle data
    (usually documents) already when writing to the DeltaQueue to keep number of
    LUWs small (partly this can be set in the applications, e.g. in the Logistics
    Cockpit). The data volume of a single LUW should not be considerably larger
    than 10% of the memory available to the work process for data extraction
    (in a 32-bit architecture with a memory volume of about 1GByte per work
    process, 100 Mbytes per LUW should not be exceeded). That limit is of rather
    small practical importance as well since a comparable limit already applies
    when writing to the DeltaQueue. If the limit is observed, correct reading is
    guaranteed in most cases.
    If the number of LUWs cannot be reduced by bundling application transactions,
    you should at least make sure that the data are fetched from all connected BWs
    as quickly as possible. But for other, BW-specific, reasons, the frequency
    should not be higher than one DeltaRequest per hour.
    To avoid memory problems, a program-internal limit ensures that never more than
    1 million LUWs are read and fetched from the database per DeltaRequest. If this
    limit is reached within a request, the DeltaQueue must be emptied by several
    successive DeltaRequests. We recommend, however, to try not to reach that limit
    but trigger the fetching of data from the connected BWs already when the number
    of LUWs reaches a 5-digit value.
    Q) I would like to display the date the data was uploaded on the
    report. Usually, we load the transactional data nightly. Is there any easy way
    to include this information on the report for users? So that they know the
    validity of the report.
    A) If I understand your requirement correctly, you want to display the date on
    which data was loaded into the data target from which the report is being
    executed. If it is so, configure your workbook to display the text elements in
    the report. This displays the relevance of data field, which is the date on which
    the data load has taken place.
    Q) Can we filter the fields at Transfer Structure?
    Q) Can we load data directly into infoobject with out extraction is it
    possible.
    Yes. We can copy from other infoobject if it is same. We load data from PSA if
    it is already in PSA.
    Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY
    AND MONTHLY.
    a) We can set the time.
    Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS.
    THROUGH WHICH NETWORK.
    a) VPN…………….Virtual
    Private Network, VPN is nothing but one sort of network
    where we can connect to the client systems sitting in offshore through RAS
    (Remote access server).
    Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
    Prepare Project Plan and Environment
    Define Project Management
    Standards and
    Procedures
    Define Implementation Standards and Procedures
    Testing & Go-live + supporting.
    Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE
    CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
    Go to TCode sm66 then see which one is locked select that pid from there and
    goto sm12
    TCode then unlock it this is happened when lock errors are occurred when u
    scheduled.
    Q) Can anybody tell me how to add a navigational attribute in the BEx report in
    the rows?
    A) Expand dimension under left side panel (that is infocube panel) select than
    navigational attributes drag and drop under rows panel.
    Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
    In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
    Q) WHAT IS TRANSACTIONAL CUBE?
    A) Transactional InfoCubes differ from standard InfoCubes in that the former
    have an improved write access performance level. Standard InfoCubes are
    technically optimized for read-only access and for a comparatively small number
    of simultaneous accesses. Instead, the transactional InfoCube was developed to
    meet the demands of SAP Strategic Enterprise Management (SEM), meaning that,
    data is written to the InfoCube (possibly by several users at the same time)
    and re-read as soon as possible. Standard Basic cubes are not suitable for
    this.
    Q) Is there any way to delete cube contents within update rules from an ODS
    data source? The reason for this would be to delete (or zero out) a cube record
    in an "Open Order" cube if the open order quantity was 0.
    I've tried using the 0recordmode but that doesn't work. Also, would it
    be easier to write a program that would be run after the load and delete
    the records with a zero open qty?
    A) START routine for update rules u can write ABAP code.
    A) Yap, you can do it. Create a start routine in Update rule.
    It is not "Deleting cube contents with update rules" It is only
    possible to avoid that some content is updated into the InfoCube using the
    start routine. Loop at all the records and delete the record that has the
    condition. "If the open order quantity was 0" You have to think also
    in before and after images in case of a delta upload. In that case you may
    delete the change record and keep the old and after the change the wrong
    information.
    Q) I am not able to access a node in hierarchy directly using variables for
    reports. When I am using Tcode RSZV it is giving a message that it doesn't
    exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other
    options to get the same functionality in BEx?
    A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards,
    it's possible in the Query Designer (BEx) itself. Just right click on the
    InfoObject for which you want to use as variables and precede further selecting
    variable type and proce

  • Useful Interview Questions and Answere

    Hi All
    Some of the Real time question.
    Q) Under which menu path is the Test Workbench to be found, including in earlier Releases?
    The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
    Q) I want to delete a BEx query that is in Production system through request. Is anyone aware about it?
    A) Have you tried the RSZDELETE transaction?
    Q) Errors while monitoring process chains.
    A) During data loading. Apart from them, in process chains you add so many process types, for example after loading data into Info Cube, you rollup data into aggregates, now this rolling up of data into aggregates is a process type which you keep after the process type for loading data into Cube. This rolling up into aggregates might fail.
    Another one is after you load data into ODS, you activate ODS data (another process type) this might also fail.
    Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything OK -
    Simulate update. (Here we can debug update rules or transfer rules.)
    SM50 à Program/Mode à Program à Debugging & debug this work process.
    Q) PSA Cleansing.
    A) You know how to edit PSA. I don't think you can delete single records. You have to delete entire PSA data for a request.
    Q) Can we make a datasource to support delta.
    A) If this is a custom (user-defined) datasource you can make the datasource delta enabled. While creating datasource from RSO2, after entering datasource name and pressing create, in the next screen there is one button at the top, which says generic delta. If you want more details about this there is a chapter in Extraction book, it's in last pages u find out.
    Generic delta services: -
    Supports delta extraction for generic extractors according to:
    Time stamp
    Calendar day
    Numeric pointer, such as document number & counter
    Only one of these attributes can be set as a delta attribute.
    Delta extraction is supported for all generic extractors, such as tables/views, SAP Query and function modules
    The delta queue (RSA7) allows you to monitor the current status of the delta attribute
    Q) Workbooks, as a general rule, should be transported with the role.
    Here are a couple of scenarios:
    1. If both the workbook and its role have been previously transported, then the role does not need to be part of the transport.
    2. If the role exists in both dev and the target system but the workbook has never been transported, and then you have a choice of transporting the role (recommended) or just the workbook. If only the workbook is transported, then an additional step will have to be taken after import: Locate the WorkbookID via Table RSRWBINDEXT (in Dev and verify the same exists in the target system) and proceed to manually add it to the role in the target system via Transaction Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
    3. If the role does not exist in the target system you should transport both the role and workbook. Keep in mind that a workbook is an object unto itself and has no dependencies on other objects. Thus, you do not receive an error message from the transport of 'just a workbook' -- even though it may not be visible, it will exist (verified via Table RSRWBINDEXT).
    Overall, as a general rule, you should transport roles with workbooks.
    Q) How much time does it take to extract 1 million (10 lackhs) of records into an infocube?
    A. This depends, if you have complex coding in update rules it will take longer time, or else it will take less than 30 minutes.
    Q) What are the five ASAP Methodologies?
    A: Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
    1. Project Preparation: In this phase, decision makers define clear project objectives and an efficient decision making process (i.e. Discussions with the client, like what are his needs and requirements etc.). Project managers will be involved in this phase (I guess).
    A Project Charter is issued and an implementation strategy is outlined in this phase.
    2. Business Blueprint: It is a detailed documentation of your company's requirements. (i.e. what are the objects we need to develop are modified depending on the client's requirements).
    3. Realization: In this only, the implementation of the project takes place (development of objects etc) and we are involved in the project from here only.
    4. Final Preparation: Final preparation before going live i.e. testing, conducting pre-go-live, end user training etc.
    End user training is given that is in the client site you train them how to work with the new environment, as they are new to the technology.
    5. Go-Live & support: The project has gone live and it is into production. The Project team will be supporting the end users.
    Q) What is landscape of R/3 & what is landscape of BW. Landscape of R/3 not sure.
    Then Landscape of b/w: u have the development system, testing system, production system
    Development system: All the implementation part is done in this sys. (I.e., Analysis of objects developing, modification etc) and from here the objects are transported to the testing system, but before transporting an initial test known as Unit testing (testing of objects) is done in the development sys.
    Testing/Quality system: quality check is done in this system and integration testing is done.
    Production system: All the extraction part takes place in this sys.
    Q) How do you measure the size of infocube?
    A: In no of records.
    Q). Difference between infocube and ODS?
    A: Infocube is structured as star schema (extended) where a fact table is surrounded by different dim table that are linked with DIM'ids. And the data wise, you will have aggregated data in the cubes. No overwrite functionality
    ODS is a flat structure (flat table) with no star schema concept and which will have granular data (detailed level). Overwrite functionality.
    Flat file datasources does not support 0recordmode in extraction.
    x before, -after, n new, a add, d delete, r reverse
    Q) Difference between display attributes and navigational attributes?
    A: Display attribute is one, which is used only for display purpose in the report. Where as navigational attribute is used for drilling down in the report. We don't need to maintain Navigational attribute in the cube as a characteristic (that is the advantage) to drill down.
    Q. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
    A: But how is it possible? If you load it manually twice, then you can delete it by requestID.
    Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
    Sure you can. ODS is nothing but a table.
    Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
    A) Yes of course. For example, for loading text and hierarchies we use different data sources but the same InfoSource.
    Q. BRIEF THE DATAFLOW IN BW.
    A) Data flows from transactional system to analytical system (BW). DataSources on the transactional system needs to be replicated on BW side and attached to infosource and update rules respectively.
    Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER RULES?
    Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
    FULL and DELTA.
    Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN WHAT IS THE PROCEDURE IN LO-COCKPIT?
    No LIS in LO cockpit. We will have datasources and can be maintained (append fields). Refer white paper on LO-Cockpit extractions.
    Q) Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
    A) Initially we don't delete the setup tables but when we do change in extract structure we go for it. We r changing the extract structure right, that means there are some newly added fields in that which r not before. So to get the required data (i.e.; the data which is required is taken and to avoid redundancy) we delete n then fill the setup tables.
    To refresh the statistical data. The extraction set up reads the dataset that you want to process such as, customers orders with the tables like VBAK, VBAP) & fills the relevant communication structure with the data. The data is stored in cluster tables from where it is read when the initialization is run. It is important that during initialization phase, no one generates or modifies application data, at least until the tables can be set up.
    Q) SIGNIFICANCE of ODS?
    It holds granular data (detailed level).
    Q) WHERE THE PSA DATA IS STORED?
    In PSA table.
    Q) WHAT IS DATA SIZE?
    The volume of data one data target holds (in no. of records)
    Q) Different types of INFOCUBES.
    Basic, Virtual (remote, sap remote and multi)
    Virtual Cube is used for example, if you consider railways reservation all the information has to be updated online. For designing the Virtual cube you have to write the function module that is linking to table, Virtual cube it is like a the structure, when ever the table is updated the virtual cube will fetch the data from table and display report Online... FYI.. you will get the information : https://www.sdn.sap.com/sdn/index.sdn and search for Designing Virtual Cube and you will get a good material designing the Function Module
    Q) INFOSET QUERY.
    Can be made of ODS's and Characteristic InfoObjects with masterdata.
    Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
    In R/3 or in BW? 2 in R/3 and 2 in BW
    Q) ROUTINES?
    Exist in the InfoObject, transfer routines, update routines and start routine
    Q) BRIEF SOME STRUCTURES USED IN BEX.
    Rows and Columns, you can create structures.
    Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
    Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes & Characteristic values.
    Variable Types are
    Manual entry /default value
    Replacement path
    SAP exit
    Customer exit
    Authorization
    Q) HOW MANY LEVELS YOU CAN GO IN REPORTING?
    You can drill down to any level by using Navigational attributes and jump targets.
    Q) WHAT ARE INDEXES?
    Indexes are data base indexes, which help in retrieving data fastly.
    Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
    Help! Refer documentation
    Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
    No.
    Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
    KPI's indicate the performance of a company. These are key figures
    Q) AFTER THE DATA EXTRACTION WHAT IS THE IMAGE POSITION.
    After image (correct me if I am wrong)
    Q) REPORTING AND RESTRICTIONS.
    Help! Refer documentation.
    Q) TOOLS USED FOR PERFORMANCE TUNING.
    ST22, Number ranges, delete indexes before load. Etc
    Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
    There should be some tool to run the job daily (SM37 jobs)
    Q) AUTHORIZATIONS.
    Profile generator
    Q) WEB REPORTING.
    What are you expecting??
    Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
    Of course
    Q) PROCEDURES OF REPORTING ON MULTICUBES
    Refer help. What are you expecting? MultiCube works on Union condition
    Q) EXPLAIN TRANPSORTATION OF OBJECTS?
    Dev-àQ and Dev-----àP
    Q) What types of partitioning are there for BW?
    There are two Partitioning Performance aspects for BW (Cube & PSA)
    Query Data Retrieval Performance Improvement:
    Partitioning by (say) Date Range improves data retrieval by making best use of database execution plans and indexes (of say Oracle database engine).
    B) Transactional Load Partitioning Improvement:
    Partitioning based on expected load volumes and data element sizes. Improves data loading into PSA and Cubes by infopackages (Eg. without timeouts).
    Q) How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?
    A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the number of records extracted. Then go to BW Monitor to check the number of records in the PSA and check to see if it is the same & also in the monitor header tab.
    A) RSA3 is a simple extractor checker program that allows you to rule out extracts problems in R/3. It is simple to use, but only really tells you if the extractor works. Since records that get updated into Cubes/ODS structures are controlled by Update Rules, you will not be able to determine what is in the Cube compared to what is in the R/3 environment. You will need to compare records on a 1:1 basis against records in R/3 transactions for the functional area in question. I would recommend enlisting the help of the end user community to assist since they presumably know the data.
    To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute and you will see the record count, you can also go to display that data. You are not modifying anything so what you do in RSA3 has no effect on data quality afterwards. However, it will not tell you how many records should be expected in BW for a given load. You have that information in the monitor RSMO during and after data loads. From RSMO for a given load you can determine how many records were passed through the transfer rules from R/3, how many targets were updated, and how many records passed through the Update Rules. It also gives you error messages from the PSA.
    Q) Types of Transfer Rules?
    A) Field to Field mapping, Constant, Variable & routine.
    Q) Types of Update Rules?
    A) (Check box), Return table
    Q) Transfer Routine?
    A) Routines, which we write in, transfer rules.
    Q) Update Routine?
    A) Routines, which we write in Update rules
    Q) What is the difference between writing a routine in transfer rules and writing a routine in update rules?
    A) If you are using the same InfoSource to update data in more than one data target its better u write in transfer rules because u can assign one InfoSource to more than one data target & and what ever logic u write in update rules it is specific to particular one data target.
    Q) Routine with Return Table.
    A) Update rules generally only have one return value. However, you can create a routine in the tab strip key figure calculation, by choosing checkbox Return table. The corresponding key figure routine then no longer has a return value, but a return table. You can then generate as many key figure values, as you like from one data record.
    Q) Start routines?
    A) Start routines u can write in both updates rules and transfer rules, suppose you want to restrict (delete) some records based on conditions before getting loaded into data targets, then you can specify this in update rules-start routine.
    Ex: - Delete Data_Package ani ante it will delete a record based on the condition
    Q) X & Y Tables?
    X-table = A table to link material SIDs with SIDs for time-independent navigation attributes.
    Y-table = A table to link material SIDs with SIDS for time-dependent navigation attributes.
    There are four types of sid tables
    X time independent navigational attributes sid tables
    Y time dependent navigational attributes sid tables
    H hierarchy sid tables
    I hierarchy structure sid tables
    Q) Filters & Restricted Key figures (real time example)
    Restricted KF's u can have for an SD cube: billed quantity, billing value, no: of billing documents as RKF's.
    Q) Line-Item Dimension (give me an real time example)
    Line-Item Dimension: Invoice no: or Doc no: is a real time example
    Q) What does the number in the 'Total' column in Transaction RSA7 mean?
    A) The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repetition of a delta request) and the LUWs for the next delta request. A LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
    Q) How to know in which table (SAP BW) contains Technical Name / Description and creation data of a particular Reports. Reports that are created using BEx Analyzer.
    A) There is no such table in BW if you want to know such details while you are opening a particular query press properties button you will come to know all the details that you wanted.
    You will find your information about technical names and description about queries in the following tables. Directory of all reports (Table RSRREPDIR) and Directory of the reporting component elements (Table RSZELTDIR) for workbooks and the connections to queries check Where- used list for reports in workbooks (Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table RSRWBINDEXT)
    Q) What is a LUW in the delta queue?
    A) A LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet of an application extractor.
    Q) Why does the number in the 'Total' column in the overview screen of Transaction RSA7 differ from the number of data records that is displayed when you call the detail view?
    A) The number on the overview screen corresponds to the total of LUWs (see also first question) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both, the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. Thus, only the records that are ready for the next delta request are displayed on the detail screen. In the detail screen of Transaction RSA7, a possibly existing customer exit is not taken into account.
    Q) Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
    A) Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded to the BW System. Then, the LUWs of the previous delta may be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change when the first delta was loaded to the BW System.
    Q) Why are selections not taken into account when the delta queue is filled?
    A) Filtering according to selections takes place when the system reads from the delta queue. This is necessary for reasons of performance.
    Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has also been loaded successfully?
    It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor (delta for master data using ALE change pointers). Such a DataSource should not be displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
    Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
    A) The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area and so on).
    Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as effective for the delta queue as for a full update. Please note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the DeltaQueue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.
    Q) Why does it take so long to display the data in the delta queue (for example approximately 2 hours)?
    A) With Plug In 2001.1 the display was changed: the user has the option of defining the amount of data to be displayed, to restrict it, to selectively choose the number of a data record, to make a distinction between the 'actual' delta data and the data intended for repetition and so on.
    Q) What is the purpose of function 'Delete data and meta data in a queue' in RSA7? What exactly is deleted?
    A) You should act with extreme caution when you use the deletion function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. You do not only delete all data of this DataSource for the affected BW System, but also lose the entire information concerning the delta initialization. Then you can only request new deltas after another delta initialization.
    When you delete the data, the LUWs kept in the qRFC queue for the corresponding target system are confirmed. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs.
    The deletion function is for example intended for a case where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.
    Q) Why does it take so long to delete from the delta queue (for example half a day)?
    A) Import PlugIn 2000.2 patch 3. With this patch the performance during deletion is considerably improved.
    Q) Why is the delta queue not updated when you start the V3 update in the logistics cockpit area?
    A) It is most likely that a delta initialization had not yet run or that the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data being written in the delta queue.
    Q) What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
    A) The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name are 19 characters long or shorter, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
    In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.
    Q) Why are the data in the delta queue although the V3 update was not started?
    A) Data was posted in background. Then, the records are updated directly in the delta queue (RSA7). This happens in particular during automatic goods receipt posting (MRRS). There is no duplicate transfer of records to the BW system. See Note 417189.
    Q) Why does button 'Repeatable' on the RSA7 data details screen not only show data loaded into BW during the last delta but also data that were newly added, i.e. 'pure' delta records?
    A) Was programmed in a way that the request in repeat mode fetches both actually repeatable (old) data and new data from the source system.
    Q) I loaded several delta inits with various selections. For which one is the delta loaded?
    A) For delta, all selections made via delta inits are summed up. This means, a delta for the 'total' of all delta initializations is loaded.
    Q) How many selections for delta inits are possible in the system?
    A) With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more.
    With complicated selection conditions, it should be only up to 10-20 delta inits.
    Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code that may exceed the memory limit.
    Q) I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
    A) Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name that are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta have to be initialized after the copy.
    Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of processes?
    A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW queues only after informing the BW Support or only if this is explicitly requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
    Q) Despite of the delta request being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
    A) The collective run submits the open V2 documents for processing to the task handler, which processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.
    Q) Despite my deleting the delta init, LUWs are still written into the DeltaQueue?
    A) In general, delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. Otherwise, buffer problems may occur: If a user started the internal mode at a time when the delta initialization was still active, he/she posts data into the queue even though the initialization had been deleted in the meantime. This is the case in your system.
    Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
    A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this does not mean that the record has successfully reached the BW yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the DeltaQueue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a DeltaExtraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which is confirming and deleting records which have been loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status is an indicator for an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903).
    The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
    Q) The extract structure was changed when the DeltaQueue was empty. Afterwards new delta records were written to the DeltaQueue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the DeltaQueue are listed via the detail display. Why are the data displayed differently? What can be done?
    Make sure that the change of the extract structure is also reflected in the database and that all servers are synchronized. We recommend to reset the buffers using Transaction $SYNC. If the extract structure change is not communicated synchronously to the server where delta records are being created, the records are written with the old structure until the new structure has been generated. This may have disastrous consequences for the delta.
    When the problem occurs, the delta needs to be re-initialized.
    Q) How and where can I control whether a repeat delta is requested?
    A) Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for certain reasons, set the request in the monitor to red manually. For the contents of the repeat see Question 14. Delta requests set to red despite of data being already updated lead to duplicate records in a subsequent repeat, if they have not been deleted from the data targets concerned before.
    Q) As of PI 2003.1, the Logistic Cockpit offers various types of update methods. Which update method is recommended in logistics? According to which criteria should the decision be made? How can I choose an update method in logistics?
    See the recommendation in Note 505700.
    Q) Are there particular recommendations regarding the data volume the DeltaQueue may grow to without facing the danger of a read failure due to memory problems?
    A) There is no strict limit (except for the restricted number range of the 24-digit QCOUNT counter in the LUW management table - which is of no practical importance, however - or the restrictions regarding the volume and number of records in a database table).
    When estimating "smooth" limits, both the number of LUWs is important and the average data volume per LUW. As a rule, we recommend to bundle data (usually documents) already when writing to the DeltaQueue to keep number of LUWs small (partly this can be set in the applications, e.g. in the Logistics Cockpit). The data volume of a single LUW should not be considerably larger than 10% of the memory available to the work process for data extraction (in a 32-bit architecture with a memory volume of about 1GByte per work process, 100 Mbytes per LUW should not be exceeded). That limit is of rather small practical importance as well since a comparable limit already applies when writing to the DeltaQueue. If the limit is observed, correct reading is guaranteed in most cases.
    If the number of LUWs cannot be reduced by bundling application transactions, you should at least make sure that the data are fetched from all connected BWs as quickly as possible. But for other, BW-specific, reasons, the frequency should not be higher than one DeltaRequest per hour.
    To avoid memory problems, a program-internal limit ensures that never more than 1 million LUWs are read and fetched from the database per DeltaRequest. If this limit is reached within a request, the DeltaQueue must be emptied by several successive DeltaRequests. We recommend, however, to try not to reach that limit but trigger the fetching of data from the connected BWs already when the number of LUWs reaches a 5-digit value.
    Q) I would like to display the date the data was uploaded on the report. Usually, we load the transactional data nightly. Is there any easy way to include this information on the report for users? So that they know the validity of the report.
    A) If I understand your requirement correctly, you want to display the date on which data was loaded into the data target from which the report is being executed. If it is so, configure your workbook to display the text elements in the report. This displays the relevance of data field, which is the date on which the data load has taken place.
    Q) Can we filter the fields at Transfer Structure?
    Q) Can we load data directly into infoobject with out extraction is it possible.
    Yes. We can copy from other infoobject if it is same. We load data from PSA if it is already in PSA.
    Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY AND MONTHLY.
    a) We can set the time.
    Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS. THROUGH WHICH NETWORK.
    a) VPN…………….Virtual Private Network, VPN is nothing but one sort of network where we can connect to the client systems sitting in offshore through RAS (Remote access server).
    Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
    Prepare Project Plan and Environment
    Define Project Management Standards and
    Procedures
    Define Implementation Standards and Procedures
    Testing & Go-live + supporting.
    Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
    Go to TCode sm66 then see which one is locked select that pid from there and goto sm12
    TCode then unlock it this is happened when lock errors are occurred when u scheduled.
    Q) Can anybody tell me how to add a navigational attribute in the BEx report in the rows?
    A) Expand dimension under left side panel (that is infocube panel) select than navigational attributes drag and drop under rows panel.
    Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
    In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
    Q) WHAT IS TRANSACTIONAL CUBE?
    A) Transactional InfoCubes differ from standard InfoCubes in that the former have an improved write access performance level. Standard InfoCubes are technically optimized for read-only access and for a comparatively small number of simultaneous accesses. Instead, the transactional InfoCube was developed to meet the demands of SAP Strategic Enterprise Management (SEM), meaning that, data is written to the InfoCube (possibly by several users at the same time) and re-read as soon as possible. Standard Basic cubes are not suitable for this.
    Q) Is there any way to delete cube contents within update rules from an ODS data source? The reason for this would be to delete (or zero out) a cube record in an "Open Order" cube if the open order quantity was 0.
    I've tried using the 0recordmode but that doesn't work. Also, would it
    be easier to write a program that would be run after the load and delete
    the records with a zero open qty?
    A) START routine for update rules u can write ABAP code.
    A) Yap, you can do it. Create a start routine in Update rule.
    It is not "Deleting cube contents with update rules" It is only possible to avoid that some content is updated into the InfoCube using the start routine. Loop at all the records and delete the record that has the condition. "If the open order quantity was 0" You have to think also in before and after images in case of a delta upload. In that case you may delete the change record and keep the old and after the change the wrong information.
    Q) I am not able to access a node in hierarchy directly using variables for reports. When I am using Tcode RSZV it is giving a message that it doesn't exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other options to get the same functionality in BEx?
    A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards, it's possible in the Query Designer (BEx) itself. Just right click on the InfoObject for which you want to use as variables and precede further selecting variable type and processing types.
    Q) Wondering how can I get the values, for an example, if I run a report for month range 01/2004 - 10/2004 then monthly value is actually divide by the number of months that I selected. Which variable should I use?
    Q) Why is it every time I switch from Info Provider to InfoObject or from one item to another while in modeling I always get this message " Reading Data " or "constructing workbench" in it runs for minutes.... anyway to stop this?
    Q) Can any one give me info on how the BW delta works also would like to know about 'before image and after image' am currently in a BW project and have to write start routines for delta load.
    Q) I am very new to BW. I would like to clarify a doubt regarding Delta extractor. If I am correct, by using delta extractors the data that has already been scheduled will not be uploaded again. Say for a specific scenario, Sales. Now I have uploaded all the sales order created till yesterday into the cube. Now say I make changes to any of the open record, which was already uploaded. Now what happens when I schedule it again? Will the same record be uploaded again with the changes or will the changes get affected to the previous record.
    A)
    Q) In BW we need to write abap routines. I wish to know when and what type of abap routines we got to write. Also, are these routines written in update rules? I will be glad, if this is clarified with real-time scenarios and few examples?
    A) Over here we write our routines in the start routines in the update rules or in the transfer structure (you can choose between writing them in the start routines or directly behind the different characteristics. In the transfer structure you just click on the yellow triangle behind a characteristic and choose "routine". In the update rules you can choose "start routine" or click on the triangle with the green square behind an individual characteristic. Usually we only use start routine when it does not concern one single characteristic (for example when you have to read the same table for 4 characteristics). I hope this helps.
    We used ABAP Routines for example:
    To convert to Uppercase (transfer structure)
    To convert Values out of a third party tool with different keys into the same keys as our SAP System uses (transfer structure)
    To select only a part of the data for from an infosource updating the InfoCube (Start Routine) etc.
    Q) What is ODS?
    A) An ODS object acts as a storage location for consolidated and cleaned-up transaction data (transaction data or master data, for example) on the document (atomic) level.
    This data can be evaluated using a BEx query.
    Standard ODS Object
    Transactional ODS object:
    The data is immediately available here for reporting. For implementation, compare with the Transactional ODS Object.
    A transactional ODS object differs from a standard ODS object in the way it prepares data. In a standard ODS object, data is stored in different versions ((new) delta, active, (change log) modified), where as a transactional ODS object contains the data in a single version. Therefore, data is stored in precisely the same form in which it was written to the transactional ODS object by the application. In BW, you can use a transaction ODS object as a data target for an analysis process.
    The transactional ODS object is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.
    Transactional ODS objects allow data to be available quickly. The data from this kind of ODS object is accessed transactionally, that is, data is written to the ODS object (possibly by several users at the same time) and reread as soon as possible.
    It offers no replacement for the standard ODS object. Instead, an additional function displays those that can be used for special applications.
    The transactional ODS object simply consists of a table for active data. It retrieves its data from external systems via fill- or delete- APIs. The loading process is not supported by the BW system. The advantage to the way it is structured is that data is easy to access. They are made available for reporting immediately after being loaded.
    Q) What does InfoCube contains?
    A) Each InfoCube has one FactTable & a maximum of 16 (13+3 system defined, time, unit & data packet) dimensions.
    Q) What does FACT Table contain?
    A FactTable consists of KeyFigures.
    Each Fact Table can contain a maximum of 233 key figures.
    Dimension can contain up to 248 freely available characteristics.
    Q) How many dimensions are in a CUBE?
    A) 16 dimensions. (13 user defined & 3 system pre-defined )
    Q) What does SID Table contain?
    SID keys linked with dimension table & master data tables (attributes, texts, hierarchies)
    Q) What does ATTRIBUTE Table contain?
    Master attribute data
    Q) What does TEXT Table contain?
    Master text data, short text, long text, medium text & language key if it is language dependent
    Q) What does Hierarchy table contain?

    Hi DST
    This is a great effort and gesture. thank you on behalf of all the newbies.
    PJ

  • Interview Questions

    Hy Gurus
    I am new to BW.
    Can u please let me know the answers for the following Qs.
    1.     What is a Data warehouse? List Few Properties of a Data warehouse.
    2. What are the major challenges of any Data Warehouse design?
    3. Data loading issues, Reporting, Production support issues?
    4.     Data Modeling, Info cube, ODS obj creation?
    5.     SAP Batch process in BW side?
    6.     How to schedule the Background jobs in ABAP, & BW?
    7.     Variables in Query? User exit variables? How do u create user exit variable? And wt u have used?
    8.     Structures in Query Reporting? What are structures?
    9.     Transportation steps?
    10.     How to compress the Info cube? What happens when you compress the info cube?
    11.     Performance issues in Reporting? How can you improve the performance of the query?
    12.     Where the ABAP routines are used in BW side?
    13.     How to create Primary index & secondary indexes on ODS?
    14.     How to prevent the duplicate records at the data target level?
    15.     Issues regarding double records?
    16.     Info sets and multiprovider differences?
    17.     Issues faced in Delta loading? Why it happened?
    Enhancements to the Data sources?
    18.     Issues in loading the data from Flat files? Delta load issues? Which will u suggest for flat file loading is it delta or full load?
    19.     How to prevent the Replication Errors? What happens when you replicate the Data Sources?
    20.     Process chain steps? Which process type is used to delete the last request when loading the data?
    21.     What is virtual cube? Characteristics? Its significance?
    22.     Diff. methods for Generic Data Sources?
    23.     What is Extract structure? Where it is used?
    24.     Data Modeling – design issues, Tech specifications, Modeling , Reporting, Testing, Transportation
    25.     Extraction on R/3 side steps?LO’s
    26.     How do you setup LIS?
    27.     SAP Batch process? /.where does u setup batch process?
    28.     Reconstruction tab in Info cube? Why it is used?
    29.     Suppose Info cube (A) having 10 records.
                         We want to take the some records say 4-7 from Info cube (A) -- Info cube (B).
                How does u handle the situation?
    30.     Suppose ODS contains 5 records and the Info cube shows 12 records. How to solve it?
    31.     Landscape
    32.     Tell me typical BW Team & How u work?
    33.     How to Maintain the Master data at Client –Server architecture?
    34.     Query performance problems? How does u improve the performance?
    35.     How does u improve the Info cube design performance?
    36.     How do you improve the Dimension & fact table performance?
    37.     How to push data from PSA to ODS?
    38.     How to postpone daily load?
    39.     The functions of Administrator Workbench are…
    40.     What is RECORD MODE
    41.     What is partition? How to partition the Info cube & PSA. ?..
    42.     How to filter single records when uploading into an ods object?
    43.     How can u connect a new data target to an existing data flow?
    44.     When it is advantageous to create secondary indexes for ODS field?
    45.     Purpose of setup tables?
    46.     What is Delta mechanism?
    47.     Will u create an infosourse for every data souse? How many infosourse can we connect to a Data Sources?
    48.     What is a Star Schema? What is the Differences between a Classic Star Schema & Extended Star schema.
    49.     What is an Attribute? Difference between Display Attribute & Navigational Attribute?
    50.     What is Transfer Rule? List the methods used in Transfer Rules.
    51.     Why we need ODS? /List a few of the technical settings that can be defined when building/modifying an ODSObject?
    52.     What is ODS? What are the three tables associated with an ODS object? What are the two types of ODS.
    53.     Name the two tables that provide detailed information about data sources.
    54.     What are two data transfer methods? Which is the preferred method and why?
    55.     Where will the development take place?&  Who will do the development testing.
    56.     Who will be responsible for long-term support?
    57.     What is a Slowly Changing Dimension?
    58.     What is namespace for SAP BW?
    59.     What are nine decision points of Data warehouse
    60.     How does u install BW Statistics? How you enable monitoring using BW Statistics.
    61.     How do u rate u r self in Modeling, Reporting & Extraction.
    62.     What are the advantages with LO Extraction.
    63.     What are the steps in General to enhance data?
    64.     What are Phases in ASAP Methodology?
    65.     What is the 90 Day rule?
    66.     What is the demo content use?
    67.     What is the use of RSRAJ Transaction?
    68.     What is the use of RSSU53 Transaction?
    69.     Can u repeat the Master Data Source?
    70.     What is diff. b/w DW and BW?
    71.     Will u use idol methods in BW?
    72.     What does the number in the 'Total' column in Transaction RSA7 mean?
    73.       The extract structure was changed when the Delta Queue was empty. Afterwards new delta records were written to the Delta Queue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the Delta Queue are listed via the detail display. Why are the data displayed differently? What can be done?
    74.     How and where can you control whether a repeat delta is requested?
    75.     Can I use several clients within SAP BW?
    Thanks in Advance
    murali

    Hi
    I have few questions and answer u can check it out which would be more helpful
    Solution
    Questions and answers.
    Question 1:
    What does the number in the 'Total' column in Transaction RSA7 mean?
    Answer:
    The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repeating a delta request) and the LUWs for the next delta request. An LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
    Question 2:
    What is an LUW in the delta queue?
    Answer:
    An LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet from an application extractor.
    Question 3:
    Why does the number in the 'Total' column, in the overview screen of Transaction RSA7, differ from the number of data records that are displayed when you call up the detail view?
    Answer:
    The number on the overview screen corresponds to the total number of LUWs (see also question 1) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. This means that only the records that are ready for the next delta request are displayed on the detail screen. The detail screen of Transaction RSA7 does not take into account a possibly existing customer exit.
    Question 4:
    Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
    Answer:
    Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded into the BW System. The LUWs of the previous delta may then be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change if the first delta is loaded into the BW System.
    Question 5:
    Why are selections not taken into account when the delta queue is filled?
    Answer:
    Filtering according to selections takes place when the system reads from the delta queue. This is necessary for performance reasons.
    Question 6:
    Why is there a DataSource with '0' records in RSA7 if delta exists and has been loaded successfully?
    Answer:
    It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor . You can display the current delta data for these DataSources using TA RSA3 (update mode ='D')
    Question 7:
    Do the entries in Table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
    Answer:
    The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area, and so on).
    Caution: As of PlugIn 2000.2 patch 3, the entries in Table ROIDOCPRMS are as effective for the delta queue as for a full update. Note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the delta queue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.
    Question 8:
    Why does it take so long to display the data in the delta queue (for example approximately 2 hours)?
    Answer:
    With PlugIn 2001.1 the display was changed: you are now able to define the amount of data to be displayed, to restrict it, to selectively choose the number of a data record, to make a distinction between the 'actual' delta data and the data intended for repetition, and so on.
    Question 9:
    What is the purpose of the function 'Delete Data and Meta Data in a Queue' in RSA7? What exactly is deleted?
    Answer:
    You should act with extreme caution when you use the delete function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. Not only do you delete all data of this DataSource for the affected BW System, but you also lose all the information concerning the delta initialization. Then you can only request new deltas after another delta initialization.
    When you delete the data, this confirms the LUWs kept in the qRFC queue for the corresponding target system. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs.
    The delete function is intended for example, for cases where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.
    Question 10:
    Why does it take so long to delete from the delta queue (for example half a day)?
    Answer:
    Import PlugIn 2000.2 patch 3. With this patch the performance during deletion improves considerably.
    Question 11:
    Why is the delta queue not updated when you start the V3 update in the logistics cockpit area?
    Answer:
    It is most likely that a delta initialization had not yet run or that the the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data to be written to the delta queue.
    Question 12:
    What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
    Answer:
    The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name is shorter than 20 characters, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in Table ROOSSHORTN.
    In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.
    Question 13:
    Why is there data in the delta queue although the V3 update has not yet been started?
    Answer:
    You posted data in the background. This means that the records are updated directly in the delta queue (RSA7). This happens in particular during automatic goods receipt posting (MRRS). There is no duplicate transfer of records to the BW system. See Note 417189.
    Question 14:
    Why does the 'Repeatable' button on the RSA7 data details screen not only show data loaded into BW during the last delta but also newly-added data, in other words, 'pure' delta records?
    Answer:
    It was programmed so that the request in repeat mode fetches both actually repeatable (old) data and new data from the source system.
    Question 15:
    I loaded several delta inits with various selections. For which one
    is the delta loaded?
    Answer:
    For delta, all selections made via delta inits are summed up. This
    means a delta for the 'total' of all delta initializations is loaded.
    Question 16:
    How many selections for delta inits are possible in the system?
    Answer:
    With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more.
    With complicated selection conditions, it should be only up to 10-20 delta inits.
    Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code which may exceed the memory limit.
    Question 17:
    I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
    Answer:
    Before you copy a source client or source system, make sure that your deltas have been fetched from the delta queue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name which are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta has to be initialized after the copy.
    Question 18.
    Am I permitted to use the functions in Transaction SMQ1 to manually control processes?
    Answer:
    Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW queues only after informing BW Support or only if this is explicitly requested in a note for Component 'BC-BW' or 'BW-WHM-SAPI'.
    Question 19.
    Despite the delta request only being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
    Answer:
    The collective run submits the open V2 documents to the task handler for processing. The task handler processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.
    Question 20.
    Despite deleting the delta init, LUWs are still written into the DeltaQueue
    Answer:
    In general, delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. Otherwise, buffer problems may occur: If you started the internal mode at a time when the delta initialization was still active, you post data into the queue even though the initialization had been deleted in the meantime. This is the case in your system.
    Question 21.
    In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the Table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
    Answer:
    Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this still does not mean that the record has successfully reached the BW. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the delta queue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a delta extraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which confirms and deletes records loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status indicates an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903). However the value 'U' in field 'NOSEND' of table TRFCQOUT is of concern.
    Question 22.
    The extract structure was changed when the delta queue was empty. Afterwards new delta records were written to the delta queue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the delta queue are listed via the detail display. Why is the data displayed differently? What can be done?
    Answer:
    Make sure that the change of the extract structure is also reflected in the database and that all servers are synchronized. We recommend resetting the buffers using Transaction $SYNC. If the extract structure change is not communicated synchronously to the server where delta records are being created, the records are written with the old structure until the new structure has been generated. This may have disastrous consequences for the delta. When the problem occurs, the delta needs to be re-initialized.
    Question 23. How and where can I control whether a repeat delta is requested?
    Answer:
    Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for any reason, manually set the request in the monitor to red. For the contents of the repeat, see Question 14. Delta requests set to red when data is already updated lead to duplicate records in a subsequent repeat, if they have not already been deleted from the data targets concerned.
    Question 24.
    As of PI 2003.1, the Logistic Cockpit offers various types of update methods. Which update method is recommended in logistics? According to which criteria should the decision be made? How can I choose an update method in logistics?
    Answer:
    See the recommendation in Note 505700.
    Question 25.
    Are there particular recommendations regarding the maximum data volume of the delta queue to avoid danger of a read failure due to memory problems?
    Answer:
    There is no strict limit (except for the restricted number area of the 24-digit QCOUNT counter in the LUW management table - which is of no practical importance, however - or the restrictions regarding the volume and number of records in a database table).
    When estimating "soft" limits, both the number of LUWs and the average data volume per LUW are important. As a rule, we recommend bundling data (usually documents) as soon as you write to the delta queue to keep number of LUWs low (this can partly be set in the applications, for example in the Logistics Cockpit). The data volume of a single LUW should not be much larger than 10% of the memory available to the work process for data extraction (in a 32-bit architecture with a memory volume of about 1 GByte per work process, 100 MByte per LUW should not be exceeded). This limit is of rather small practical importance as well since a comparable limit already applies when writing to the delta queue. If the limit is observed, correct reading is guaranteed in most cases.
    If the number of LUWs cannot be reduced by bundling application transactions, you should at least make sure that the data is fetched from all connected BWs as quickly as possible. But for other, BW-specific, reasons, the frequency should not exceed one delta request per hour.
    To avoid memory problems, a program-internal limit ensures that no more than 1 million LUWs are ever read and fetched from the database per delta request. If this limit is reached within a request, the delta queue must be emptied by several successive delta requests. We recommend, however, to try not to reach that limit but trigger the fetching of data from the connected BWs as soon as the number of LUWs reaches a 5-digit value.
      THANKS =POINTS in SDN
    SANJEEV

  • Step by step Data loading to BI 7.0 from SAP R/3 not from flat files

    Dear Guru's
    As i am new to BI 7.0, i need to extract the data from R/3 to BI. so could anyone help me in this regrds
    Thanks
    C.S.Ramesh

    if ur still not clear
    go thr this
    Hi,
    Check the following links.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    check the following
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    business content
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
    https://websmp203.sap-ag.de/co
    http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
    (navigate with expand left nodes)
    also co-pa
    http://help.sap.com/saphelp_nw04/helpdata/en/53/c1143c26b8bc00e10000000a114084/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1910ab90-0201-0010-eea3-c4ac84080806
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ff61152b-0301-0010-849f-839fec3771f3
    LO Extraction
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Check these links:
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    Re: LO-Cockpit  V1 and V2 update
    Also Refer this link:
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    FI-CO 'Data Extraction -Line Item Level-FI-CO
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
    FI-GL
    http://help.sap.com/saphelp_nw04/helpdata/en/c9/fe943b2bcbd11ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_470/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm
    http://www.sapgenie.com/sapfunc/fi.htm
    FI-SL
    http://help.sap.com/saphelp_nw2004s/helpdata/en/28/5ccfbb45b01140a3b59298c267604f/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/41/65be27836d300ae10000000a114b54/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
    How to do basic LO extraction for SAP-R3-BW
    1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
    2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
    3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
    4. Go to transaction RSA3 and check the data.
    5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
    6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
    7.Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
    8.Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
    9.Now you can go to your data target and see the delta record.
    find your scenario and find what data sources do you need on R3 side and ensure they are active as well:
    http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
    find your scenario -> data sources -> go to R3 -> sbiw and activate required data source
    replicate data sources in BW:
    RSA1 -> source systems -> right click on your source system -> replicate
    then activate your BC:
    service.sap.com/bi -> BI Business Content -> General Information -> SAP BW Business Content - Activation
    and execute infopackage (it should be delivered with BC)
    Useful links:
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    Pls chk this cookbook for step by step;
    http://www.erpgenie.com/sapgenie/docs/MySAP%20BW%20Cookbook%20Vol%201.pdf
    http://www.erpgenie.com/sapgenie/docs/MySAP%20BW%20Cookbook%20Vol%202.pdf
    Step by step Generic extraction:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
    How To doc link
    https://www.sdn.sap.com/irj/sdn/howtoguides
    Hope this helps

  • Extraction steps

    Hi,
    can somebody help me with the prerequisite steps for Extraction like - assigning logical system and RFC destination for BW and R/3.
    also the step-by-step for all types of Generic and Business content...
    extraction steps.
    thanks.

    Hi Sunil,
    Pls do check the link for step by step for generic xtraction
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    check the following
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    business content
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
    https://websmp203.sap-ag.de/co
    http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
    (navigate with expand left nodes)
    also co-pa
    http://help.sap.com/saphelp_nw04/helpdata/en/53/c1143c26b8bc00e10000000a114084/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1910ab90-0201-0010-eea3-c4ac84080806
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ff61152b-0301-0010-849f-839fec3771f3
    LO Extraction
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Check these links:
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    Re: LO-Cockpit  V1 and V2 update
    Also Refer this link:
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    FI-CO 'Data Extraction -Line Item Level-FI-CO
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
    FI-GL
    http://help.sap.com/saphelp_nw04/helpdata/en/c9/fe943b2bcbd11ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_470/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm
    http://www.sapgenie.com/sapfunc/fi.htm
    FI-SL
    http://help.sap.com/saphelp_nw2004s/helpdata/en/28/5ccfbb45b01140a3b59298c267604f/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/41/65be27836d300ae10000000a114b54/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
    How to do basic LO extraction for SAP-R3-BW
    1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
    2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
    3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
    4. Go to transaction RSA3 and check the data.
    5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
    6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
    7.Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
    8.Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
    9.Now you can go to your data target and see the delta record.
    find your scenario and find what data sources do you need on R3 side and ensure they are active as well:
    http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
    find your scenario -> data sources -> go to R3 -> sbiw and activate required data source
    replicate data sources in BW:
    RSA1 -> source systems -> right click on your source system -> replicate
    then activate your BC:
    service.sap.com/bi -> BI Business Content -> General Information -> SAP BW Business Content - Activation
    and execute infopackage (it should be delivered with BC)
    Useful links:
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    service.sap.com/bi -> BI InfoIndex
    sdn.sap.com -> Business Information Warehouse -> How-To guides (under Quick Links)
    Hope This Helps.
    ****Assign Points If Helpful****
    Regards,
    Ravikanth

Maybe you are looking for