LIS Extraktion to BW - selfdefined LIS structures

Hi, I found several documents about activation of content LIS structures and the process of extracting these structures into BW.
In our case we defined a new LIS structure, loaded it with datas and now we want to extract this data to BW. Now my question: what do I have to do or customize in R/3 to create a data source for loading BW?
Hope to get usefull information.
Regrads
Mirjam

Hi
See this thread
LIS EXTRACTION STEP BY STEP
Follow step by step
Regards
N Ganesh

Similar Messages

  • LIS Info Structure with table MKPF/MSEG

    Hi Gurus,
    I have a view made up of table MKPF/MSEG (74 fields in totals). Based on my requirement (loading archived and non archived marerial movements data) I am looking to create an Info structure with the same 74 fields - to connect the LIS infostructures to BW.
    I need to create a char. as KF fields catalog.
    my issue is while doing that I am not able to have the 74 fields I am looking for (I am just getting around 50).
    I know how to create an Infostructure/ Catalogue (Transaction MC21/MC18)
    Any Idea how to Create an Info Structure that would have all the fields from table MKPF and MSEG?
    Regards
    Edited by: Blaiso on Jun 2, 2011 6:10 PM

    Hi,
    Steps in LIS EXTRACTION:
    T.code u2013 :MC18 u2013 create field catalog
    1. Characteristic Catalog
    Application-01-Sales and Distribution, 02-Purchasing, 03-Inventory Controlling, etc..
    Catalog category 1. Characteristic catalog, 2. Key figures catalog 3. Date catalog Select characteristic catalog and enter, click on characteristic select the source table and it will be display the relevant source field and select the source field, copy + close, copy.
    Save, similarly create key figures catalog
    T.code : MC21 u2013 create infostructure
    Example u2013
    Inforstructure : S789
    Application u2013 01
    Choose characteristic select the catalog, select the fields, copy + close Choose key figures catalog select the key figures ,copy + close, save and generate
    T.code u2013 MC24 u2013 create updating
    Infostructure : S789
    Update group : 01- Sales document, delivery, billing document ,enter Select the key figures click on rules for key figures give suggest rules, copy save and generate Click on updating (activate updating) Select the infostructure set periodic split 1. Daily, 2. Week, 3. Month, 4. Posting period Updating u20131)No updating,2)Synchronous updating (V1), 3)As synchronous updating (V2), 4)As synchronous updating (V3),
    T.code u2013 LBW0 u2013 Connection of LIS Information structures to SAPBW Information structure : S786 Select the radio button-Setup LIS environment and Execute.
    Select the radio button-Generate data source and Execute.
    For Delta update:
    Select the radio button-Generate updating and Execute Select the radio button -Activate / deactivate and Execute.
    T.code u2013 SBIW u2013 Display IMG (implementation guide) Setting for applications specific data source u2013 logistics u2013 Managing transfer information structure u2013 setup of statistical data u2013 applications specific setup of statistical data u2013perform statistical setup u2013 sales.
    Choose activity
    Setup u2013 Orders, deliveries, billing
    Choose the activities enter the infostructure (S789), give name of the run, date of termination, time of termination, No. of tolerated faulty documents. Then execute
    T.code u2013 RSA3 u2013 Extractor checker
    Give the data source name eg. 2LIS 01S789 and execute, result will get some records Go to BW side replicate data source u2013 Assign infosource u2013 Create infocube u2013 Create update rules u2013 create infopackage and schedule the package with initialize delta process.
    For delta update :
    In R/3 side
    T.code u2013 MC25, set update (V1) or (V2) or (V3)
    T.code u2013 LBW0, choose generate updating and execute then choose activate / deactivate and execute
    BW side u2013 create infopackage and schedule the package with delta update.
    First time if your scheduling the infopackage -in R/3 side T.code :MC25 -Udating set to No update,insted of selecting the update V1,V2,V3.
    If your doing the Delta update:in R/3 side T.code :MC25-Updating set to either V1 or V2 or V3. and the to T.code :LBW0 -Select the radio button Active/deactivate and Execute.
    and schedule the infopackage with delta update.
    Modules for LIS : SD,MM, PP,QM.
    Deltas for LIS:
    After setting up the LIS environment, 2 transparent tables and 1 extract structure is generated for this particular info structure. Within transaction SE11 you can view the tables u2018SnnnBIW1u2019, u2018SnnnBIW2u2019 and the structure u2018SnnnBIWSu2019 and the InfoStructure itself u201ASnnnu2018
    The tables S5nnnBIW1 & SnnnnBIW2 are used to assist the delta update process within BW.
    Extract structure u2018SnnnnBIWCu2019 is used as an interface structure between OLTP InfoStructure and BW
    The OLTP system has automatically created an entry in the control table u2018TMCBIWu2019. Within transaction u2018SE16u2019 youu2019ll see, that for your particular InfoStructure the field u2018BIW activeu2019 has the value u2018Xu2019 and the field u2018BIW statusu2019 is filled with value u20181u2019 (refers to table SnnnBIW1).
    The orgininal LIS update program u201ARMCX#### will be enhanced within the form routines u201Aform Snnnbiw1_update_u2026.u2018 and u201Aform Snnnbiw2_update
    With the transaction u2018SE38u2019 youu2019ll see at the end of the program starting at line 870 / 1006, that the program is enhanced within a u2018BIW delta updateu2019 coding
    Within the flag u201AActivate/Deactivateu2018 the update process into the delta tables (SnnnBIW1/Sn5nnBIW2) is swichted on/off. In the table u201ATMCBIWu2018 is defined, which table is active for delta update.
    Regards,
    Prakash

  • Data in LIS Structures (MCVBAK & MCVBAP)

    Hi
    In Standard SAP, Sales Orders data is copied to tables: VBAK & VBAP.  Parallally data copied to structures MCVBAK & MCVBAP for LIS(Logistics Information System).
    Report from VBAK is mismatching with LIS report.
    Please tell me, how to see the data in structures: MCVBAK & MCVBAP or where this LIS data saves.
    Regards
    Uma

    this will be difficult to accomplish, since data in LIS are -like you already recognized- without any document numbers ... the data there are compressed (like they would be in BI). so what you actually can do is, set up a sandbox system, drop the content of your custom-made table using SE14 and do a test by adding a sales order that would match the criteria to put that order into your LIS table. compare values between LIS and the document. add a couple of more orders to see whether there's a bug in summing up values or a formula or something of that inkling.
    if your test shows that the data are the same in both, document and LIS there might have been an earlier error (maybe some V2-posting that did go awry?), so the only thing you would have to do is, rebuild the data of that table completely. again: search service.sap.com/notes on the how-to.
    if your test shows that the LIS data differ from the ones in the document, you will have to do further R&D - analyzing the structure, the rules etc ...
    please note another thing: most LIS-structures are time-dependent, meaning: that order you are talking about, could have been 'open' in the period you selected on the first screen after calling transaction MCSI. in that case, LIS will show that order as 'open' while VA05N would show you the actual state of the order this very moment - and that might be different.

  • (Old) LIS in (new) R/3 4.7 (Enterprice) & BW 3.5, a pain in the b...

    Hi,
    Yep it's LIS again. Unfortunately I could not find the answer the our specific issue on the forum (nor at SAP-Help).
    We are using the (old) LIS structures S001, S011, S013 & S015 in a R/3 v. 4.7 (latest plugins) & BW 3.5 Environment (as there are no LO-Cockpit structures for these LIS infostructures).
    Al the info found on the forum are Setup (Configuration) manuals and info for Older R/3 versions (4.6 and lower).
    In 4.7 the LIS (and LO-Cockpit) Infostructures & Datasources are part of the Business content (as we think...). Most of the usual Config-steps (like the BW connection) for LIS do not work for S001, S013 & S015 (at least it does not work here...). Strangly they still work for S011.
    Actually some tables in older R/3 environments (as mentioned in the manuals) like the S5nnBIW1/2 does not exist anymore in 4.7.
    Anyone any idea or information what SAP has done with these LIS structures (S001, S013 & S015) in 4.7?
    And what is still needed to setup and use these Structures (and how)?
    Best regards,
    Jos
    (Netherlands)

    Hi all,
    What I have found is that you (at least) have to do in 4.7 is to check note: 115192 (we need to implement it).
    115192:
    Symptom
    The data contents of the key fields within the 'delta tables' SnnnBIW1 or SnnnBIW2 are 'corrupt'. Therefore a delta update from structures of the logistics information system is not possible although the environment necessary for this is set up. During the update, SQL error 804 or error M2022 can occur.
    In Transaction LBW0 (linking LIS information structures to SAP-BW), error M+040
    "The LIS environment is set up incorrectly."
    with long text (documentation) - Error occurred when checking the LIS environment.
    The order of the information structure key fields differs from the one in delta table SnnnBIW1.
    Occurs when displaying the settings for a SAP (LIS & LO-Cockpit, etc.) information structure.
    Cause and prerequisites
    This is caused by an incorrect sequence of key fields in the delta tables SnnnBIW1 and SnnnBIW2.
    Solution
    Change the sequence of key fields in the Data Dictionary (Transaction SE11) in the delta tables so that it corresponds to the sequence of the Snnn table in question (for example: the sequence of the tables S260BIW1 and S260BIW2 must be identical with the sequence of table S260) (The message M2 369 'Generated object! Use maintenance of info structure (MC22).' can be ignored). Then activate the delta tables.
    This note is a prerequisite for the use of the delta function of the
    ·     SD transfer structures S260 to S264
            (S264 as of PI-99),
    ·     SD standard InfoStructures S001 to S006,
    ·     standard infostructure in Purchasing S013
            in all R/3 Releases.
    (Some corrections included in support package, see OSS...)
    Jos

  • Lis and lo extraction doubt

    hai to every body,
    i have an doubt on lis and lo extraction
    In lis extraction we have an information structure(IS).before extraction we all delete the contents of IS.Then by scheduling the v1 or v2 job we update data from database tables to IS by running statistical setup.
    but in los we have an setup tables.before extractiopn we all delete data from setup tables.then by running statistical setup we fill the setup tables with dtatbse data.
    which job(v1 or v2) scheduling between databse tables and setup tables

    Hi uday,
    To tell you, we wont delete the content of Information Structure in LIS, Because, in LIS, whenever,a user do a transaction, that record will automatically updated in the Information structure.
    Where as, if you consider LO, whenever, a user generates a transaction, that records wont be updated in the setup tables, they are directly moved to delta tables(like RSA7 etc).  Only when you do statistical setup, this setup tables are updated, later on these tables are not updated, unlike LIS.
    Only for this, we wont delete the information structure everytime,where as LO we delete the setup tables whenever we do init.
    Thanks
    Vijay

  • LIS -Reports

    Hi Gurus,
                  I have got following questions about reports.
    1. Can i use LIS as reports?
    2. I have just started working with reports, i wanted to follow the following procedure, I appreciate if some one can validate this procedure.
    a. Get the business requirements, Get the fields which business wants to see on reports.
    b. See all the required reports are available in SARP T.code or not.
    c. See is it possible to generate thru LIS
    d. Find out list of custom reports need to be generated
    e. Prepare specs for them.
    3. I appreciate if some one can give me how to generate report thru LIS
    Thank you
    ANil

    Hi,
    The LIS is a central integrated information system where one can create specific tables that are updated at specific stages and that can be used to report on values contained in specific fields. SAP has standard information structures for reporting purposes. The std info structures can be accessed via: LOSDSISStandard analysis. The reports use the following characteristics: customer, material, sales org, shipping point, sales employee, and sales office.
    IMG menu path for SIS: IMG>Logistics General>Logistics Information System (LIS)
    The Logistics data warehouse is divided into two main sections: data basis and updating. Data basis is responsible for the actual design of the info structure, that is, what key fields are reported on or displayed. Updating is responsible for the updating rules used by the system, determining how the info structure is to be updated, and when this updating is to take place.
    Task 1: Create Self-Defined Information Structure
    Use transaction code MC21 (menu path Logistics Data Warehouse>Data Basis>Information Structures>Maintain self-defined information structures> Create) to create a Self-Defined Information Structure. Give a customer-range number 990 (any available number between 501 and 999). To make it easier, use ‘copy from’ to copy structure from S001.
    Task 2: Maintain Update Groups
    SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>General Definition Using Update Groups>Maintain Update Groups
    You can use the existing system-delivered update groups. Use Update Group (UpdGrp) 1 for the standard order process of: SIS: Sales Document, Delivery, Billing Document and use UpdGrp 2 for the SIS: Returns, Returns Delivery, Credit Memo.
    Task 3: Maintain Update Rules
    SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Create Create (transaction code MC24). To make it easier, use ‘copy from’ to copy update rules from S001.
    Please make sure the Source information is properly updated for all the characteristics. Since you copied the rules, the sales order and item rules are defaulted too. Make sure appropriate changes are made for events VC (delivery) and VD (Invoice).
    Task 4: Maintain Statistics Groups
    Maintain Statistics Groups
    Maintain Statistics Groups for Customers, Materials, and SD Document Types etc. Most of the pre-defined settings are enough. Make sure that settings are updated for customized objects too, e.g., SD document types for your organizations.
    Also, make sure that the customer (sales view) and material Master records are updated with appropriate Statistics Groups.
    Maintain Statistics Groups for Customers, Material and Sales documents. Assign Statistics Groups for relevant Sales Document Type, item type, delivery type, item type, Determine Billing Document Types Relevant to Statistics.
    Update Customer Master for Statistics Relevancy
    Transaction Code XD02 (Sales view, field “Cust stats.Grp”)
    Update Material for Statistics Relevancy
    Transaction Code MM02 (Sales 2 view, field “Matl statistics grp”)
    Task 5: Assign Update Groups to Header and Item Levels
    Assign Update Groups on Header and Item levels
    For combinations of Sales Area (Sales Org, Distribution Channel, Division), assign Update groups (transaction codes OVRO and OVRP).
    SIS IMG>Logistics Data Warehouse>Updating>Updating Control>Settings: Sales>Update Group
    Update Groups at Item Level
    Update Groups at Header Level
    Task 6: Activate SIS Update
    Lastly, Activate SIS Update for the Structure (transaction code OMO1)
    SIS IMG path: Logistics Data Warehouse>Updating>Updating Control>Activate Update>Choose Activity as Sales and Distribution.
    Last update our SIS structure S677 with period as ‘Month’ and update option of ‘Asynchronous Updating (2)’.
    Go through the following links
    http://help.sap.com/saphelp_46c/helpdata/en/c1/37544e449a11d188fe0000e8322f96/frameset.htm
    LIS Configuration: http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOLIS/LOLIS.pdf
    Thanks,
    Sree.Manam
    Edited by: manam narayana on Jun 3, 2008 11:21 AM

  • Need LIS Extraction Step by Step

    Hi ,
    Any one can give me a LIS Extraction Step by Step.
    Already i've got some LIS Extraction steps, but i haven't clear with that.
    MC18 – create field catalog
    How to create this field catalog?
    THanks,
    Arun.M.D

    Hi,
    LIS
    lis
    Steps in LIS EXTRACTION:
    T.code - :MC18 – create field catalog
    1. Characteristic Catalog
    Application-01-Sales and Distribution, 02-Purchasing, 03-Inventory Controlling, etc..
    Catalog category 1. Characteristic catalog, 2. Key figures catalog 3. Date catalog Select characteristic catalog and enter, click on characteristic select the source table and it will be display the relevant source field and select the source field, copy + close, copy.
    Save, similarly create key figures catalog
    T.code : MC21 – create infostructure
    Example –
    Inforstructure : S789
    Application – 01
    Choose characteristic select the catalog, select the fields, copy + close Choose key figures catalog select the key figures ,copy + close, save and generate
    T.code – MC24 – create updating
    Infostructure : S789
    Update group : 01- Sales document, delivery, billing document ,enter Select the key figures click on rules for key figures give suggest rules, copy save and generate Click on updating (activate updating) Select the infostructure set periodic split 1. Daily, 2. Week, 3. Month, 4. Posting period Updating –1)No updating,2)Synchronous updating (V1), 3)As synchronous updating (V2), 4)As synchronous updating (V3),
    T.code – LBW0 - Connection of LIS Information structures to SAPBW Information structure : S786 Select the radio button-Setup LIS environment and Execute.
    Select the radio button-Generate data source and Execute.
    For Delta update:
    Select the radio button-Generate updating and Execute Select the radio button -Activate / deactivate and Execute.
    T.code – SBIW – Display IMG (implementation guide) Setting for applications specific data source – logistics – Managing transfer information structure – setup of statistical data – applications specific setup of statistical data –perform statistical setup – sales.
    Choose activity
    Setup – Orders, deliveries, billing
    Choose the activities enter the infostructure (S789), give name of the run, date of termination, time of termination, No. of tolerated faulty documents. Then execute
    T.code – RSA3 – Extractor checker
    Give the data source name eg. 2LIS 01S789 and execute, result will get some records Go to BW side replicate data source – Assign infosource – Create infocube – Create update rules – create infopackage and schedule the package with initialize delta process.
    For delta update :
    In R/3 side
    T.code – MC25, set update (V1) or (V2) or (V3)
    T.code – LBW0, choose generate updating and execute then choose activate / deactivate and execute
    BW side - create infopackage and schedule the package with delta update.
    First time if your scheduling the infopackage -in R/3 side T.code :MC25 -Udating set to No update,insted of selecting the update V1,V2,V3.
    If your doing the Delta update:in R/3 side T.code :MC25-Updating set to either V1 or V2 or V3. and the to T.code :LBW0 -Select the radio button Active/deactivate and Execute.
    and schedule the infopackage with delta update.
    Modules for LIS : SD,MM, PP,QM.
    Deltas for LIS:
    After setting up the LIS environment, 2 transparent tables and 1 extract structure is generated for this particular info structure. Within transaction SE11 you can view the tables ‘SnnnBIW1’, ‘SnnnBIW2’ and the structure ‘SnnnBIWS’ and the InfoStructure itself ‚Snnn‘
    The tables S5nnnBIW1 & SnnnnBIW2 are used to assist the delta update process within BW.
    Extract structure ‘SnnnnBIWC’ is used as an interface structure between OLTP InfoStructure and BW
    The OLTP system has automatically created an entry in the control table ‘TMCBIW’. Within transaction ‘SE16’ you’ll see, that for your particular InfoStructure the field ‘BIW active’ has the value ‘X’ and the field ‘BIW status’ is filled with value ‘1’ (refers to table SnnnBIW1).
    The orgininal LIS update program ‚RMCX#### will be enhanced within the form routines ‚form Snnnbiw1_update_....‘ and ‚form Snnnbiw2_update
    With the transaction ‘SE38’ you’ll see at the end of the program starting at line 870 / 1006, that the program is enhanced within a ‘BIW delta update’ coding
    Within the flag ‚Activate/Deactivate‘ the update process into the delta tables (SnnnBIW1/Sn5nnBIW2) is swichted on/off. In the table ‚TMCBIW‘ is defined, which table is active for delta update.
    Note: The delta updating is client dependent !
    Thanks,
    JituK

  • LIS EXTRACTIONS

    Hi firends,
    1) want to now why we go for the LIS EXTRACTIONS?
    2) what r the steps for the LIS ?
    3) What r the Modules used for the LIS ?
    4)where we can put the DELTAS for the LIS?
    thanks and regards
    shafeeq ahmed

    hi
    steps for LIS:
    Step by Step for LIS Extraction
    LIS EXTRACTION
    T.code - :MC18 – create field catalog
    1.     Characteristic Catalog
    Application-01-Sales and Distribution, 02-Purchasing, 03-Inventory Controlling, etc.
    Catalog category 1. Characteristic catalog, 2. Key figures catalog 3. Date catalog
    Select characteristic catalog and enter, click on characteristic select the source table and it will be display the relevant source field and select the source field, copy + close, copy.
    Save, similarly create key figures catalog
    T.code : MC21 – create infostructure
    Infostructure : S789
    Application – 01
    Choose characteristic select the catalog, select the fields, copy + close
    Choose key figures catalog select the key figures ,copy + close, save and generate
    T.code – MC24 – create updating
    Infostructure : S789
    Update group : 01- Sales document, delivery, billing document ,enter
    Select the key figures click on rules for key figures give suggest rules, copy save and generate
    Click on updating (activate updating)
    Select the infostructure set periodic split 1. Daily, 2. Week, 3. Month, 4. Posting period
    Updating –1)No updating,2)Synchronous updating (V1), 3)As synchronous updating (V2), 4)As synchronous updating (V3),
    T.code – LBW0 - Connection of LIS Information structures to SAPBW
    Information structure : S786
    Select the radio button-Setup LIS environment and Execute.
    Select the radio button-Generate data source and Execute.
    For Delta update:
    Select the radio button-Generate updating and Execute
    Select the radio button -Activate / deactivate and Execute.
    T.code – SBIW – Display IMG (implementation guide)
    Setting for applications specific data source – logistics – Managing transfer information structure – setup of statistical data – applications specific setup of statistical data –perform statistical setup – sales.
    Choose activity
    Setup – Orders, deliveries, billing
    Choose the activities enter the infostructure (S789), give name of the run, date of termination, time of termination, No. of tolerated faulty documents. Then execute
    T.code – RSA3 – Extractor checker
    Give the data source name eg. 2LIS 01S789 and execute, result will get some records
    Go to BW side replicate data source – Assign infosource – Create infocube – Create update rules – create infopackage and schedule the package with initialize delta process.
    For delta update :
    In R/3 side
    T.code – MC25, set update (V1) or (V2) or (V3)
    T.code – LBW0, choose generate updating and execute then choose activate / deactivate and execute
    BW side - create infopackage and schedule the package with delta update.
    First time if your scheduling the infopackage -in R/3 side T.code :MC25 -Udating set to No update,insted of selecting the update V1,V2,V3.
    If your doing the Delta update:in R/3 side T.code :MC25-Updating set to either V1 or V2 or V3. and the to T.code :LBW0 -Select the radio button Active/deactivate and Execute.
    and schedule the infopackage with delta update.
    3.Modules:
    SD,MM, PP,QM..
    4. Deltas for LIS:
    After setting up the LIS environment, 2 transparent tables and 1 extract structure is generated for this particular info structure. Within transaction SE11 you can view the tables ‘SnnnBIW1’, ‘SnnnBIW2’ and the structure ‘SnnnBIWS’ and the InfoStructure itself ‚Snnn‘
    The tables  S5nnnBIW1 & SnnnnBIW2 are used to assist the delta update process within BW.
    Extract structure ‘SnnnnBIWC’ is used as an interface structure between OLTP InfoStructure and BW
    The OLTP system has automatically created an entry in the control table ‘TMCBIW’. Within transaction ‘SE16’ you’ll see, that for your particular InfoStructure the field ‘BIW active’ has the value ‘X’ and the field ‘BIW status’ is filled with value ‘1’ (refers to table SnnnBIW1).
    The orgininal LIS update program ‚RMCX#### will be enhanced within the form routines ‚form Snnnbiw1_update_....‘  and ‚form Snnnbiw2_update
    With the transaction ‘SE38’ you’ll see at the end of the program [starting at line 870 / 1006], that the program is enhanced within a ‘BIW delta update’ coding
    Within the flag  ‚Activate/Deactivate‘ the update process into the delta tables (SnnnBIW1/Sn5nnBIW2) is swichted on/off. In the table ‚TMCBIW‘ is defined, which table is active for delta update.
    Note: The delta updating is client dependent !
    Regards,
    M Kalpana

  • LIS vs. BW

    All,
    I am looking for some feedback regarding LIS. I know that LIS once used to be used quite a lot but with BW I would have assumed that LIS goes more away from being used for new SAP implementation. On my current project they woulike the full extend of LIS but do have BW too. Any advice on this? If it makes sense or not?

    Hi Alex,
    I would use BW instead of LIS. Getting your SAP data into a DW that allows flexible reporting is much better than what LIS has to offer to today. As you might know, there are a lot of the BW extracts that are based on LIS, so you will get the same data in BW that is found in LIS.
    My guess is BW will be SAP long term reporting solution. I am not sure how much longer LIS will be around in R/3 for reporting purposes.
    I am sure other people on the forum can come up with some reason why you should use BW instead of LIS.
    Cheers! Bill

  • HI experts can u tell me the difference between LIS AND LOCOCKCPIT ext ?

    hi experts iam in learning stage ,so plz can some one tell me the differece between LIS and LO COCKPIT  extractions and various steps invovlved in them , sorry for being pain in the back i did search in the previous posting didnt find the right answer . cheers thanks

    Hi,
    LO **** pit 
    -->BW CONTENT EXTRACTOR......
    ---> it uses Readymadely available datasorce
    --->LO cockpit supports V3 update(BACK GROUND SCHEDULING Jobs)
    LIS
    ---> CUSTOMER GENERATED EXTRACTOR.
    > need to cretae everything...
    --->LIS does't supports V3 update mode... it supports only V1 (SYNCHRONUS)& V2(ASYNCHRONUS UPDATE)
    check these links:
    Difference B/n LOCOCKPIT &LIS
    differences between LO and LIS
    Differences between LIS,LO,CO/PA and FI-SL extractors
    Difference between LIS  and LO Cockpi interma of table?
    difference between LIS and LO Setup run
    LIS and LO Cockpit
    hope it helps...............
    Regards
    chandra sekhar
    Edited by: chandra  sekhar on Dec 16, 2008 2:01 PM

  • Diff between LIS,LO,COPA and Genric extarctions.

    HI,
    Can anyone brief me the diff between LIS,LO,COPA and Genric extarctions.

    Hi,
    LIS:
    The Logistics Information System (LIS) is a data warehouse used for reporting in all of the application areas in Logistics (LO).
    Typically, the data stored in the LIS is an aggregated subset of the data stored for your transactions. For example, you would not usually find the full information stored with all sales order documents. Instead, you would find key field values such as order quantities, total order costs, and item costs. These values could also be stored according to business entities such as sales organization, distribution channel, division, and sold-to party. Similarly, the document detail for all material movements is typically not stored, but the aggregated stock quantities and values are stored based on plant and material.
    COPA:
    Profitability Analysis (PA) is an integrated component in the SAP R/3 system.
    All of the data related to profitability from the other SAP R/3 applications is mapped in CO-PA in accordance with the corresponding business transactions.
    This allows you to transfer into CO-PA billing document data from SD, cost object costs from CO-PC, and overall costs from overall cost controlling.
    CO-PA collects all of the OLTP data for calculating contribution margins (sales, cost of sales, overhead costs)
    CO-PA also has powerful reporting tools and planning functions
    Generic Extractors:
    When should you use generic extractors?
    Business Content does not contain a DataSource for your application.
    The application does not feature its own generic delta extraction method
    You are using your own programs in SAP R/3 to populate the tables
    The tools for generic data extraction can be used to generate an extractor for all applications.

  • How to create a new report from an information structure?

    Dear gurus,
    My customer wants to have a sales report by product hierachy. I want to create an information structure for product hierachy and create a report from this info structure like a standard report. I dun know which steps to do. Pls tell me how to do. Your help are highly appreciated.
    Thank you!
    Rgds,
    Nghi Do

    Hi,
    Steps in LIS EXTRACTION:
    T.code - :MC18 u2013 create field catalog
    1. Characteristic Catalog
    Application-01-Sales and Distribution, 02-Purchasing, 03-Inventory Controlling, etc..
    Catalog category 1. Characteristic catalog, 2. Key figures catalog 3. Date catalog Select characteristic catalog and enter, click on characteristic select the source table and it will be display the relevant source field and select the source field, copy + close, copy.
    Save, similarly create key figures catalog
    T.code : MC21 u2013 create infostructure
    Example u2013
    Inforstructure : S789
    Application u2013 01
    Choose characteristic select the catalog, select the fields, copy + close Choose key figures catalog select the key figures ,copy + close, save and generate
    T.code u2013 MC24 u2013 create updating
    Infostructure : S789
    Update group : 01- Sales document, delivery, billing document ,enter Select the key figures click on rules for key figures give suggest rules, copy save and generate Click on updating (activate updating) Select the infostructure set periodic split 1. Daily, 2. Week, 3. Month, 4. Posting period Updating u20131)No updating,2)Synchronous updating (V1), 3)As synchronous updating (V2), 4)As synchronous updating (V3),
    T.code u2013 LBW0 - Connection of LIS Information structures to SAPBW Information structure : S786 Select the radio button-Setup LIS environment and Execute.
    Select the radio button-Generate data source and Execute.
    For Delta update:
    Select the radio button-Generate updating and Execute Select the radio button -Activate / deactivate and Execute.
    T.code u2013 SBIW u2013 Display IMG (implementation guide) Setting for applications specific data source u2013 logistics u2013 Managing transfer information structure u2013 setup of statistical data u2013 applications specific setup of statistical data u2013perform statistical setup u2013 sales.
    Choose activity
    Setup u2013 Orders, deliveries, billing
    Choose the activities enter the infostructure (S789), give name of the run, date of termination, time of termination, No. of tolerated faulty documents. Then execute
    T.code u2013 RSA3 u2013 Extractor checker
    Give the data source name eg. 2LIS 01S789 and execute, result will get some records Go to BW side replicate data source u2013 Assign infosource u2013 Create infocube u2013 Create update rules u2013 create infopackage and schedule the package with initialize delta process.
    For delta update :
    In R/3 side
    T.code u2013 MC25, set update (V1) or (V2) or (V3)
    T.code u2013 LBW0, choose generate updating and execute then choose activate / deactivate and execute
    BW side - create infopackage and schedule the package with delta update.
    First time if your scheduling the infopackage -in R/3 side T.code :MC25 -Udating set to No update,insted of selecting the update V1,V2,V3.
    If your doing the Delta update:in R/3 side T.code :MC25-Updating set to either V1 or V2 or V3. and the to T.code :LBW0 -Select the radio button Active/deactivate and Execute.
    and schedule the infopackage with delta update.
    Modules for LIS : SD,MM, PP,QM.
    Deltas for LIS:
    After setting up the LIS environment, 2 transparent tables and 1 extract structure is generated for this particular info structure. Within transaction SE11 you can view the tables u2018SnnnBIW1u2019, u2018SnnnBIW2u2019 and the structure u2018SnnnBIWSu2019 and the InfoStructure itself u201ASnnnu2018
    The tables S5nnnBIW1 & SnnnnBIW2 are used to assist the delta update process within BW.
    Extract structure u2018SnnnnBIWCu2019 is used as an interface structure between OLTP InfoStructure and BW
    The OLTP system has automatically created an entry in the control table u2018TMCBIWu2019. Within transaction u2018SE16u2019 youu2019ll see, that for your particular InfoStructure the field u2018BIW activeu2019 has the value u2018Xu2019 and the field u2018BIW statusu2019 is filled with value u20181u2019 (refers to table SnnnBIW1).
    The orgininal LIS update program u201ARMCX#### will be enhanced within the form routines u201Aform Snnnbiw1_update_....u2018 and u201Aform Snnnbiw2_update
    With the transaction u2018SE38u2019 youu2019ll see at the end of the program starting at line 870 / 1006, that the program is enhanced within a u2018BIW delta updateu2019 coding
    Within the flag u201AActivate/Deactivateu2018 the update process into the delta tables (SnnnBIW1/Sn5nnBIW2) is swichted on/off. In the table u201ATMCBIWu2018 is defined, which table is active for delta update.
    Note: The delta updating is client dependent !
    Regards,
    Ram Pedarla
    Edited by: RamPedarla on Apr 1, 2010 10:35 AM
    Edited by: RamPedarla on Apr 1, 2010 10:35 AM

  • Data extraction from Structure.

    Hi All,
    Could you please tell the steps for extracting data from Structure.
    Thanks in Advance!!

    Preeti,
    you can extract data from SAP by MC23. also please check these options
    Steps in LIS EXTRACTION:
    T.code u2013 :MC18 u2013 create field catalog
    1. Characteristic Catalog
    Application-01-Sales and Distribution, 02-Purchasing, 03-Inventory Controlling, etc..
    Catalog category 1. Characteristic catalog, 2. Key figures catalog 3. Date catalog Select characteristic catalog and enter, click on characteristic select the source table and it will be display the relevant source field and select the source field, copy + close, copy.
    Save, similarly create key figures catalog
    T.code : MC21 u2013 create infostructure
    Example u2013
    Inforstructure : S789
    Application u2013 01
    Choose characteristic select the catalog, select the fields, copy + close Choose key figures catalog select the key figures ,copy + close, save and generate
    T.code u2013 MC24 u2013 create updating
    Infostructure : S789
    Update group : 01- Sales document, delivery, billing document ,enter Select the key figures click on rules for key figures give suggest rules, copy save and generate Click on updating (activate updating) Select the infostructure set periodic split 1. Daily, 2. Week, 3. Month, 4. Posting period Updating u20131)No updating,2)Synchronous updating (V1), 3)As synchronous updating (V2), 4)As synchronous updating (V3),
    T.code u2013 LBW0 u2013 Connection of LIS Information structures to SAPBW Information structure : S786 Select the radio button-Setup LIS environment and Execute.
    Select the radio button-Generate data source and Execute.
    For Delta update:
    Select the radio button-Generate updating and Execute Select the radio button -Activate / deactivate and Execute.
    T.code u2013 SBIW u2013 Display IMG (implementation guide) Setting for applications specific data source u2013 logistics u2013 Managing transfer information structure u2013 setup of statistical data u2013 applications specific setup of statistical data u2013perform statistical setup u2013 sales.
    Choose activity
    Setup u2013 Orders, deliveries, billing
    Choose the activities enter the infostructure (S789), give name of the run, date of termination, time of termination, No. of tolerated faulty documents. Then execute
    T.code u2013 RSA3 u2013 Extractor checker
    Give the data source name eg. 2LIS 01S789 and execute, result will get some records Go to BW side replicate data source u2013 Assign infosource u2013 Create infocube u2013 Create update rules u2013 create infopackage and schedule the package with initialize delta process.
    For delta update :
    In R/3 side
    T.code u2013 MC25, set update (V1) or (V2) or (V3)
    T.code u2013 LBW0, choose generate updating and execute then choose activate / deactivate and execute
    BW side u2013 create infopackage and schedule the package with delta update.
    First time if your scheduling the infopackage -in R/3 side T.code :MC25 -Udating set to No update,insted of selecting the update V1,V2,V3.
    If your doing the Delta update:in R/3 side T.code :MC25-Updating set to either V1 or V2 or V3. and the to T.code :LBW0 -Select the radio button Active/deactivate and Execute.
    and schedule the infopackage with delta update.
    Modules for LIS : SD,MM, PP,QM.
    Deltas for LIS:
    After setting up the LIS environment, 2 transparent tables and 1 extract structure is generated for this particular info structure. Within transaction SE11 you can view the tables u2018SnnnBIW1u2019, u2018SnnnBIW2u2019 and the structure u2018SnnnBIWSu2019 and the InfoStructure itself u201ASnnnu2018
    The tables S5nnnBIW1 & SnnnnBIW2 are used to assist the delta update process within BW.
    Extract structure u2018SnnnnBIWCu2019 is used as an interface structure between OLTP InfoStructure and BW
    The OLTP system has automatically created an entry in the control table u2018TMCBIWu2019. Within transaction u2018SE16u2019 youu2019ll see, that for your particular InfoStructure the field u2018BIW activeu2019 has the value u2018Xu2019 and the field u2018BIW statusu2019 is filled with value u20181u2019 (refers to table SnnnBIW1).
    The orgininal LIS update program u201ARMCX#### will be enhanced within the form routines u201Aform Snnnbiw1_update_u2026.u2018 and u201Aform Snnnbiw2_update
    With the transaction u2018SE38u2019 youu2019ll see at the end of the program starting at line 870 / 1006, that the program is enhanced within a u2018BIW delta updateu2019 coding
    Within the flag u201AActivate/Deactivateu2018 the update process into the delta tables (SnnnBIW1/Sn5nnBIW2) is swichted on/off. In the table u201ATMCBIWu2018 is defined, which table is active for delta update.
    Note: The delta updating is client dependent !

  • 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

  • Lync 2013 Android can't sign in with 5.4 but can sign in with 5.3

    AS Title said. I has deployed Lync 2013 Mobility. Now I got very strange things. First, I can sign in with Lync 2013 App Android 5.3.1100 and its fully functional(IM,Audio,Video). But when I update to Lync 2013 App Android 5.4.1106. I can't sign in.
    No any Error message on screen. Even checked Android log. Still can't understand what happend.
    My Lync environment is not using Public Cert. But if working fine with Private Cert on Lync 2013 App Android 5.3 version should be fine on Lync 2013 App Android 5.4 version.
    I also test my connectivity on https://testconnectivity.microsoft.com/ . All Pass. No Errors.
    Have anyone can tell me why I can't sign in with Android 5.4 version?
    My Device is Asus padfone. 
    Android Version: 4.1.1
    Here is my Lync 2013 App Android 5.4 log on my device.
    --------- beginning of /dev/log/main
    06-09 22:06:53.112  7271  7271 D SigningInActivity: onPause()
    06-09 22:06:53.142  7271  7271 D SigningInActivity: onStop()
    06-09 22:06:53.142  7271  7271 V ActivityMonitor: Activity Stop: com.microsoft.office.lync.ui.login.SigningInActivity
    06-09 22:06:53.142  7271  7271 V ActivityMonitor: AComo is in backround now.
    06-09 22:06:53.142  7271  7271 V ActivityMonitor: AComo is in background now.
    06-09 22:06:53.172  7271  7271 I LYNC    : INFO APPLICATION .\capplication.cpp/934:CApplication::serialize() called
    06-09 22:06:53.172  7271  7271 V LYNC    : VERBOSE APPLICATION .\ccredentialstore.cpp/137:storing credentials for service:1
    06-09 22:06:53.512  7271  7271 I LYNC    : INFO APPLICATION .\cbasepersistableentity.cpp/179:Storing 1 out-of-sync Object Models took 360ms
    06-09 22:06:53.512  7271  7271 I LYNC    : INFO UTILITIES .\cbasepersistablecomponent.cpp/230:Storing 6 out-of-sync components took 4ms
    06-09 22:06:53.522  7271  7271 I PreferencesManager: commit is called on PreferencesManager.
    06-09 22:06:53.562  7271  7271 W IInputConnectionWrapper: beginBatchEdit on inactive InputConnection
    06-09 22:06:53.562  7271  7271 W IInputConnectionWrapper: endBatchEdit on inactive InputConnection
    06-09 22:06:53.562  7271  7271 W IInputConnectionWrapper: beginBatchEdit on inactive InputConnection
    06-09 22:06:53.562  7271  7271 W IInputConnectionWrapper: endBatchEdit on inactive InputConnection
    06-09 22:07:41.901  7271  7271 I Choreographer: Skipped 36 frames!  The application may be doing too much work on its main thread.
    06-09 22:07:43.892  7271  7271 D SigningInActivity: onStart()
    06-09 22:07:43.892  7271  7271 V ActivityMonitor: Activity Start: com.microsoft.office.lync.ui.login.SigningInActivity
    06-09 22:07:43.892  7271  7271 V ActivityMonitor: AComo is in foreground now.
    06-09 22:07:43.912  7271  7271 I LYNC    : INFO APPLICATION .\cucwadatasynchronizer.cpp/1031:Mode 1 scheduled to timeout in 120sec
    06-09 22:07:43.922  7271  7271 D SigningInActivity: onResume()
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\calertreporter.cpp/131:Clearing all(0) alerts
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\cucwaappsession.cpp/497:Called signOut() in state 1
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\calertreporter.cpp/117:Alert cleared of Category 2, Type 300, cleared 0 alerts
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\calertreporter.cpp/117:Alert cleared of Category 2, Type 301, cleared 0 alerts
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\calertreporter.cpp/117:Alert cleared of Category 2, Type 302, cleared 0 alerts
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\ctransportrequestretrialqueue.cpp/399:Cancelling all requests
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\ctransportrequestretrialqueue.cpp/409:Cancelling request: 0x5cc2b380
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO TRANSPORT
    E:\LcsSource\icomo\main\src\dev\lyncmobile/ucmp/transport/session/private/CSessionBase.hxx/158:Cancelling request: 0x5cc2b380
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO UTILITIES .\cbasepersistablecomponent.cpp/230:Storing 1 out-of-sync components took 1ms
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\cucwaautodiscoveryserviceretrialwrapper.cpp/566:Timer cancelled. OnResume = 0
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\calertreporter.cpp/117:Alert cleared of Category 1, Type 201, cleared 0 alerts
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\cucwaappsession.cpp/975:CUcwaAppSession canceling all requests
    06-09 22:07:44.783  7271  7271 I LYNC    : INFO APPLICATION .\cucwaappsession.cpp/998:CUcwaAppSession::setNewActualState() state=0
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component UcwaSession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component UcwaAutoDiscoverySession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component JoinLauncherSession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component EwsSession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component EwsAutoDiscoverSession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component HttpFileDownloadSession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component BrbSession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component CpsSession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component PsomSession on sign-out.
    06-09 22:07:44.803  7271  7271 I AndroidOperationQueue: CancelSync Started
    06-09 22:07:44.803  7271  7271 I AndroidOperationQueue: No operations pending
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component WebTicketSession on sign-out.
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO TRANSPORT .\chttprequestprocessor.cpp/134:Clearing request processor for component MetaDataManager on sign-out.
    06-09 22:07:44.803  7271  7271 I AndroidOperationQueue: CancelSync Started
    06-09 22:07:44.803  7271  7271 I AndroidOperationQueue: No operations pending
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO APPLICATION .\ccertificateprovisioningservice.cpp/541:Clearing certificate from transport: b72d9723-566b-4bb8-9e03-f58e40e8e34a
    06-09 22:07:44.803  7271  7271 I AndroidOperationQueue: CancelSync Started
    06-09 22:07:44.803  7271  7271 I AndroidOperationQueue: No operations pending
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO APPLICATION .\ccertificateprovisioningservice.cpp/541:Clearing certificate from transport: b72d9723-566b-4bb8-9e03-f58e40e8e34a
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO APPLICATION .\cucwaautodiscoveryserviceretrialwrapper.cpp/566:Timer cancelled. OnResume = 0
    06-09 22:07:44.803  7271  7271 I AndroidOperationQueue: CancelSync Started
    06-09 22:07:44.803  7271  7271 I AndroidOperationQueue: No operations pending
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO APPLICATION .\ccertificateprovisioningservice.cpp/541:Clearing certificate from transport: b72d9723-566b-4bb8-9e03-f58e40e8e34a
    06-09 22:07:44.803  7271  7271 I LYNC    : INFO APPLICATION .\capplication.cpp/934:CApplication::serialize() called
    06-09 22:07:44.803  7271  7271 V LYNC    : VERBOSE APPLICATION .\ccredentialstore.cpp/137:storing credentials for service:1
    06-09 22:07:44.954  7271  7271 I LYNC    : INFO APPLICATION .\cbasepersistableentity.cpp/179:Storing 2 out-of-sync Object Models took 149ms
    06-09 22:07:44.954  7271  7271 I LYNC    : INFO APPLICATION .\cpresencesubscription.cpp/792:Removed 0 success records, current size is 0
    06-09 22:07:44.964  7271  7271 I UcClientStateManager: New UI State: ActualState = IsSignedOut DesiredState = BeSignedOut  DataAvailable = false New state=class com.microsoft.office.lync.ui.login.SigninActivity
    06-09 22:07:44.974  7271  7271 V LyncActivity: finish being called for com.microsoft.office.lync.ui.login.SigningInActivity
    06-09 22:07:44.974  7271  7271 I LyncPerformance: PerfEnd|4-10|1402322864979
    06-09 22:07:44.984  7271  7271 I LyncPerformance: PerfEnd|4-10|1402322864988
    06-09 22:07:44.984  7271  7271 D SigningInActivity: onPause()
    06-09 22:07:45.014  7271  7271 D SigninActivity: onCreate()
    06-09 22:07:45.014  7271  7271 V ActivityMonitor: Activity Create: com.microsoft.office.lync.ui.login.SigninActivity
    06-09 22:07:45.024  7271  7271 W AccessibilityViewFactory: Failed to find class for view ImageView
    06-09 22:07:45.024  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.024  7271  7271 D TextView: Constructor - Got Res id for appearance for textColorPrimaryInverse
    06-09 22:07:45.024  7271  7271 W ResourceType: Skipping entry 0x1060069 in package table 0 because it is not complex!
    06-09 22:07:45.024  7271  7271 D TextView: Constructor - Got appearance for textColorPrimaryInverse
    06-09 22:07:45.024  7271  7271 D TextView: Constructor -- Got mEditTextBackgroundColor
    06-09 22:07:45.024  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.024  7271  7271 D TextView: Constructor - Got Res id for appearance for textColorPrimaryInverse
    06-09 22:07:45.024  7271  7271 W ResourceType: Skipping entry 0x1060069 in package table 0 because it is not complex!
    06-09 22:07:45.024  7271  7271 D TextView: Constructor - Got appearance for textColorPrimaryInverse
    06-09 22:07:45.024  7271  7271 D TextView: Constructor -- Got mEditTextBackgroundColor
    06-09 22:07:45.034  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.044  7271  7271 W AccessibilityViewFactory: Failed to find class for view ImageView
    06-09 22:07:45.044  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.044  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.044  7271  7271 W AccessibilityViewFactory: Failed to find class for view ImageView
    06-09 22:07:45.044  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.044  7271  7271 D TextView: Constructor - Got Res id for appearance for textColorPrimaryInverse
    06-09 22:07:45.044  7271  7271 W ResourceType: Skipping entry 0x1060069 in package table 0 because it is not complex!
    06-09 22:07:45.044  7271  7271 D TextView: Constructor - Got appearance for textColorPrimaryInverse
    06-09 22:07:45.044  7271  7271 D TextView: Constructor -- Got mEditTextBackgroundColor
    06-09 22:07:45.044  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.054  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.054  7271  7271 D TextView: Constructor - Got Res id for appearance for textColorPrimaryInverse
    06-09 22:07:45.054  7271  7271 W ResourceType: Skipping entry 0x1060069 in package table 0 because it is not complex!
    06-09 22:07:45.054  7271  7271 D TextView: Constructor - Got appearance for textColorPrimaryInverse
    06-09 22:07:45.054  7271  7271 D TextView: Constructor -- Got mEditTextBackgroundColor
    06-09 22:07:45.054  7271  7271 W AccessibilityViewFactory: Failed to find class for view TextView
    06-09 22:07:45.054  7271  7271 D TextView: Constructor - Got Res id for appearance for textColorPrimaryInverse
    06-09 22:07:45.054  7271  7271 W ResourceType: Skipping entry 0x1060069 in package table 0 because it is not complex!
    06-09 22:07:45.054  7271  7271 D TextView: Constructor - Got appearance for textColorPrimaryInverse
    06-09 22:07:45.054  7271  7271 D TextView: Constructor -- Got mEditTextBackgroundColor
    06-09 22:07:45.084  7271  7271 D e       : bool
    06-09 22:07:45.094  7271  7271 D e       : bool
    06-09 22:07:45.104  7271  7271 I LyncPerformance: PerfEnd|1:Signin Page Loaded|1402322865109
    06-09 22:07:45.104  7271  7271 D SigninActivity: onStart()
    06-09 22:07:45.104  7271  7271 V ActivityMonitor: Activity Start: com.microsoft.office.lync.ui.login.SigninActivity
    06-09 22:07:45.104  7271  7271 D SigninActivity: onResume()
    06-09 22:07:45.574  7271  7271 D SigningInActivity: onStop()
    06-09 22:07:45.574  7271  7271 V ActivityMonitor: Activity Stop: com.microsoft.office.lync.ui.login.SigningInActivity
    06-09 22:07:45.574  7271  7271 D SigningInActivity: onDestroy()
    06-09 22:07:45.574  7271  7271 V ActivityMonitor: Activity Destroy: com.microsoft.office.lync.ui.login.SigningInActivity
    06-09 22:07:46.645  7271  7271 W IInputConnectionWrapper: beginBatchEdit on inactive InputConnection
    06-09 22:07:46.645  7271  7271 W IInputConnectionWrapper: endBatchEdit on inactive InputConnection
    06-09 22:07:48.377  7271  7450 V LogAttachmentTask: Creating attachment in background task
    Device Information
    BUILD VERSION : 4.1.1
    HARDWARE : qcom
    CPU MAX FREQ : 1512MHz
    BACK FACING CAMERA SPEC
    Supported Preview Size : 1920X1080, 1280X960, 1280X720, 800X480, 768X432, 720X480, 640X480, 576X432, 480X320, 384X288, 352X288, 320X240, 240X160, 176X144
    Supported Picture Size : 3264X2448, 3264X1836, 2592X1944, 2592X1458, 2048X1536, 2048X1152, 1920X1080, 1600X1200, 1600X900, 1280X768, 1280X720, 1024X768, 800X600, 800X480, 640X480, 352X288, 320X240, 176X144
    Supported Video Size :No supported Video size
    FRONT FACING CAMERA SPEC
    Supported Preview Size : 640X480, 576X432, 480X320, 384X288, 352X288, 320X240, 240X160, 176X144
    Supported Picture Size : 640X480, 352X288, 320X240, 176X144
    Supported Video Size :No supported Video size
    DISPLAY DENSITY : 240 dpi

    Please try to sign in with manual settings, you can manually enter the following URLs:
    https://<ExtPoolFQDN>/Autodiscover/autodiscoverservice.svc/Root for external access
    https://<IntPoolFQDN>/AutoDiscover/AutoDiscover.svc/Root for internal access
    Lisa Zheng
    TechNet Community Support
    Lisa Zheng:
         Ok. I tried. Look its 406 on IIS Logs. Finding information. Have any suggestion on this?
         Update:  I find some information. But still not solve my problem.
    My Deployment Structure:
         Server:
         Lync 2013 FE x 1  (Update to CU1,UCMA,database update,ITAdmin-Configuration)
         Lync 2013 Edge x 1
         Reverse Proxy (IIS8+ARR 3.0) x 1
         Privacy Root Cert x 1, FE Cert x 1, Edge Cert x 1, Reverse Proxy Cert x 1.
        Client:
            Lync 2013 Basic(PC is installed  Privacy Root Cert)
            Lync 2013 Mobile ver 5.4 (Android, installed  Privacy Root Cert)  ---  Can't log in.
            Lync 2013 Mobile ver 5.3 (Android, installed  Privacy Root Cert)  ---  All working fine.

Maybe you are looking for