Difference betten lo.extraction &lo cockpit

can anyone explain the difference LO-EXTRACTION &LO-COCKPIT.
where do we use it?

Hi
Logistics Customizing Cockpit (LO Cockpit) allows you to extract data from your logistics applications to your SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system. This tool, which you access with transaction LBWE, is also available for SAP Business Information Warehouse (SAP BW). Let me introduce you to this tool, explain its benefits, answer some common questions about it, and address some of the most commonly encountered errors
LO Cockpit Step By Step
Here is LO Cockpit Step By Step
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 – Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders – Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
Redards
tapashi

Similar Messages

  • Difference between Logistic extraction( Lo Cockpit) and Finance extraction

    Hi All,
                   Can anyone explain me, Why Finance data sources are not included in the LO-COCKPIT. Why logistics data sources are given this much care. Why there is no Filling /Deleting Set up tables in the FI extractors. Can any one explain how the FI extractors pull the data from the base tables.
    With Regards,
    Naveen

    Hi,
    Difference starts with Setup table and delta Processes  etc.....
    Please refer below link
    http://scn.sap.com/thread/1169207
    Best regards,
    Varun gandhi

  • What is the difference between unstack, extract, and split

    I want to make a copy of a picture. I used the duplicate option, which does whatever it does and causes them to be linked somehow. I'm trying unstack, extract, and split to try to make the duplicate act as an independent picture.
    I'm wanting a second copy to put in another project. Yet when I move any of these duplicates, they all move.
    What is the difference between unstack, extract, and split?
    How can I move a copy of a pic from one project to another without the original moving?
    Thanks

    Yes - you are correct and yes extracting one will make it behave independently but you almost never actually want to do that. What you really want are album picks.
    Stacks are extremely useful - here is a little info
    [Aperture stacks|http://photo.rwboyer.com/2008/09/16/aperture-2-organization-tip-more-on- stacks-and-albums>
    You may also want to check out the Organization eBook.
    RB

  • Difference between Generic extraction and Generic Delta

    Hi Experts,
    Pleasee give of some information below  query:
    1) Difference between Generic extraction and Generic Delta.
    2) How to achieve Generic delta.
    3) When we go for Generic delta instead of generic extraction.
    Advance ThankU. Points vl be assigned.
    Thanks,
    Ragu.R

    Hi,
    Generic delta is the delta load done using Generic DS.
    Generic extraction
    Usage:
    1. When the standard extractors are not supporting the extraction what you need. If SAP does not have a standard extractor for your need to get data from R3, you would have to go for generic extractor.
    2. If you create a custom object say by combining certain base tables in R3 say custom tables ZTAB1 and ZTAB2. These two tables are not SAP provided tables and there will not be any standard extractors. So cases like this you will have to go for generic extractors.
    How:
    You have to use RSO2 transaction and you can also set delta based on, one of the three characteristics such as timestamp, calday or pointer (a sequence no).
    once you create it and activate it. The extractor will be available in ROOSOURCE - (table in R3 where all the data sources are available).
    Refer:
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Generic Extraction via Function Module
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    thanks,
    JituK

  • Any difference in ECC - LO Extraction

    Hi Experts,
    Is there any difference in LO Extraction steps compare to R/3.
    I have tried to fill the setuptables,but it saying that termination time is in past.
    Pls guide me the steps.If there is any changes
    Regards
    Lucky

    hi,
    choose the option new run check box, and give the run name.
    if there is any delta entry in the RSA7 for the application, then u can do init setup table in background.
    choose the printer as LP01 and save and schedule immediate.
    chk the data in RSA3.
    Ramesh

  • Reasons for Posting Free Period in LO Cockpit Data Extraction

    Dear Experts,
       I am quite new to the concept of LO Cockpit, but I have learnt that we need to stop posting transaction in R/3 during the process of filling up the set up table. I really want the reasons for this, so I can convince my customers.
    1) May anyone give me the exact reasons by providing some example cases please?
    Some sourcess mentioned that if we don't stop posting documents, there may be duplicated records (in Set Up table and in Delta Queue table). Is this true?
    2) May anyone provide me the step of extracting LO Cockpit data please? When the R/3 system should be freezed? When it should be unfreezed? Why do we have to use initialization without data transfer? Please give me the steps in details.
    Thank you so much

    Hi,
    If the users don't stop posting, and at the same time if you are filling up the setup tables, you'll lose the data. Ex if you are filling up setup table for Sales order and if at the same time the user is changing it, its going to take the earlier version or not pick the sales order at all, and thus the changes are lost.
    You usually freeze the R3 system when you are ready to fill up the setup tables. Users are locked out of the system so no transaction posting takes place and all batch jobs that update the tables are suspended.
    You usually do an init without data transfer so as not to hold up the system as the setup tables might have a lot of records. This reduces the R3 system downtime.
    Here's a thread that gives you detailed LO information :
    LO step by step procedure
    Cheers,
    Kedar

  • Difference between extraction collective run and a V3 collective run

    Hello Roberto.
    As per your weblog can you elaborate on the difference between a Extraction collective run and a V3 collective run for Queued delta and V3 Update respecively,
    Regards,
    pravin

    Hello Roberto,
    Fine Roberto I have 3 more questions with regards to Queued delta-
    1.     In case of Queued deltas how does the data come to the LBWQ ex. MCEX02 queue from the application technically when a transaction is posted in R/3.
    2.     What role does the Function Module MCEX_UPDATE_02_QRFC play in getting the data in LBWQ.
    3.     Does the extraction Queue read the update tables VBHDR,VBMOD eventually like the V3 collective run.
    Regards,
    Pravin

  • Difference between Extraction Structure and Datasource

    Hi Gurus,
    I have a very basic question here.Can anybody explain to me in detail the difference between an extraction structure and Datasource.
    Thanks in advance

    Hi:
    I am pasting a summarized def. from sap notes.
    http://help.sap.com/saphelp_bw30b/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm
    Data Source:
    Data that logically belongs together is stored in the source system in the form of DataSources. A DataSource contains a number of fields in a flat structure used to transfer data into BW (Extract Structure).
    Extract Structure:
    In the extract structure, data from a DataSource is staged in the source system. The extract structure contains the amount of fields that are offered by an extractor in the source system for the data loading process.
    You can edit and enhance DataSource extract structures in the source system. To do this, in the BW Administrator Workbench choose Goto à Modeling à Source Systems à Your Source System à Context Menu (right mouse click) à Customizing Extractors à Subsequent Processing of DataSources.
    While, you are on the topic, you have one more structure.
    Transfer Structure:
    The transfer structure is the structure in which the data is transported from the source system into the SAP Business Information Warehouse.
    It provides a selection of the extract structure fields for the source system.
    It may be a good idea to look into a sample Business Content extractor to get a better understanding of how they are related.
    Chamarthy

  • 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

  • Bussiness  Scenario for GENERIC   EXTRACTION

    Hi friends,
       can any one  explain me... in what situation we go for Generic Extractions..
    The normal reason is  When  the Bussiness Content  Datasource is not matching with our requirement.. we go for Generic extraction.. 
         I told like this only... but they are not satisfied with my answer.. and they asked .. tell me the  bussiness scenario( in what situation u  done  generic extraction)
      so, friends... could any one plz explain  me any scenario... which you done for generic extraction...
             i will appriciate  by giving   points  to the appropriate  answers..
    Thanks
    babu

    Hi,
    These 2 below links may be helpful,
    <u>GENERIC DATA EXTRACTION USING FUNCTION MODULE</u>
    <u>Difference between Generic Extraction and Enhancement of existing Extractor</u>
    1)Go to RSA6 and find the data source you need to enhance.--> Display
    2)Double click on the Extract structure.
    3)Now click on the append structure button to add the required field on to the existing structure.
    4) add your required fields with ZZ appended to your field.
    5) Save & Activate the append structure. Then go back and make sure you activate the extract structure also.
    6) Now again go back to RSA6 and select your Data Source. But this time go to change Data Source to remove the hide option to the enhanced fields. By default they’ll be in hide mode. If you don’t remove the hide field then this field will not be seen in BW side.
    7) Now go to SE38 to write the logic to populate the data into the enhanced field. Program name to write the logic is ZXRSAU01.
    8) Check + Save + Activate.
    9) Check in RSA3 if data is populated as per your requirement.
    10) Replicate your Data Source.
    11) Now go to Data Source/ Trans. Structure screen. Now you can see the enhanced field on the right hand side.Enhancements:
    <b>Enhancements:BW Side:
    Go to CMOD.</b>
    1. To Save&#61664; give Description &#61664; create&#61664;create new project—give the project name
    2. Select the radio button Enhancement Assignment and give the Enhancement name you want and press Enter.
    3. If the Enhancement is already assigned to some other project it will display the same message saying it is already assigned it some other project. Click on&#61664;
    4. If the Enhancement is not assigned to any project save.
    5. Give RSR00001 (For Variable Exits)
    6. Activate the Project.
    7. and click on the components button.&#61664;Now go to Display
    8. Now Double click on EXIT_SAPLRRS0_001. In that you can see an include ZXRSRU01.
    9. Double click on that include, it will say program name ZX…… are reserved for includes of exit Functions groups.
    10. Just Press Enter.
    11. It’ll Pop-Up a window Create Object.&#61664;saying Include ZX…. Does not exits
    12. That is where you have to write the code for the variable exits. BW: Virtual&#61664;
    13. RSR00002 Chars and Key Figures. BW: Moving Characteristics.&#61664;
    14. RSR00003
    Thanks,
    Aby Jacob

  • Generic Extraction creation

    HI All,
    I want to extract data from two tables from CRM(Z tables).
    When I goto RSO2 to create a generic data source it is giving me the options of Extract from View,Extract from Info Set and Extract BY FM.
    But when I select Extraction from View it is giving me an option to select from one table only.
    HOw can I extract data from two tables?
    Please help me
    Sridath

    Hi,
    Check the below links, you will get more info on Generic Extraction.
    Generic Extraction:
    http://help.sap.com/saphelp_nw70/helpdata/en/28/4c553c42360a40e10000000a114084/frameset.htm
    Check the link.
    http://www.erpgenie.com/sapgenie/docs/MySAP%20BW%20Cookbook%20Vol%202.pdf
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Refer:
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    Generic Extraction with Table, View, FM & Infoset
    Creating a datasource for generic extraction
    Generic Extraction
    Customer and Generic extraction difference ?
    generic extraction
    Re: Generic extractors
    generic extraction
    Reg
    Pra

  • 2LIS_05_Q0ITEM Enhancement / Extract structure

    Hi experts,
    I am trying to enhance a data source and am having an issue adding a field to the extract structure.
    The 2LIS_05_Q0ITEM includes a field called MATNR for the Material Number of the claimed notification (Table MCQMEL) which I don't need (as it is in the Notification Data source).
    What I need is the material number of the replacement part (MATNR / Table MCQMFE). I can't add it in the Extraction Customizing cockpit. (2 fields with the same is not possible and it isn't possible either to remove the MCQMEL/MATNR field).
    I tried to find a workaround using a user exit to enhance the extract structure but couldn't find anything allowing me to retrieve the MATNR from MCQMEL.
    Any clues on how to add this field to the datasources other than doing a select fron the Table in the extract structure?
    Thanks,

    Hi,
    The LO steps are described in:
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:How_to_do_LO_Extraction
    Go through these weblogs for detailed understanding of LO extraction mechanism. If you have any further queries, post them.
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins
    Bye
    Dinesh

  • Regarding diff between LO EXTRACTION , FI and CO EXTRACTION

    Hello gurus
    i got 2 points infact
    1. please anyone tell me in detail about difference between LO extraction and FI and CO extraction.
    2. In Infopackage, what it explains in a tab saying, with masterdata and without masterdata check box for loading data.
    thanks in advance
    points rewareded.
    bikid

    hi,
    mainly extractor has two types
    1. application specific extractor
    2. cross application specific extractor
    in the application extractor also divided in two parts
    1. customer generated extractor
    2. business content extractor.
    FI AND CO-PA extractor will fall under customer generated extractor and the LO extractor comes under BI Content extractor.
    BI Content extractor has the advantage of editing and modifying the extract structure of data source, but in customer generated extractor this is not possible.
    for your second question
    you can have two option with update data with respect to master data or without master.
    mostly it's depends upon the loading. transactional data loading with respect to master data.
    hope this help you
    regards
    harikrishna N

  • Can anyone tell me where to see OSS notes

    Hi
    Can anyone tell me where to see composite OSS note 586163 (any OSS notes). In which site and in which category i should search.

    www.service.sap.com
    SAP Support Portal
    Quick Lnks :
    Search for OSS notes.
    You need to have a login..its not free.
    After login - Help & Support - Search for SAP notes
    <b>
    Anyws here is the note</b>
    Summary
    Symptom
    You are transferring data from SAP R/3 Inventory Management to the BW system. You get unexpected data or data that differs from the data in the analyses in the R/3 system.
    This note should help you to analyze this problem.
    Other terms
    2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 2LIS_03_S195,
    2LIS_03_S196, 2LIS_03_S197, 2LIS_03_S198, 0IC_C01, 0IC_02, 0IC_C03,
    0IC_MC01, 0IC_MC02, 0IC_MC03, stock analyses, inventory management,
    Non-cumulative InfoCubes, stock key figures, stock, stocks,
    RMCBINIT_BW, RMCBNERP, RMCBNEUA, consistency,
    data consistency, healthcare, health service
    Reason and Prerequisites
    This note provides an overview of the release strategy, sources of information, tips and tricks, and known errors for this subject area.
    Solution
    Contents
    1. Release strategy
    a) General information
    b) Recommended objects for BW Releases 3.0B, 3.1 Content and 3.2 Content
    c) Recommended objects for BW Releases 2.0B and 2.1C
    d) Obsolete objects
    e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
    2. Sources of information
    a) BW technology
    SAP BW online documentation
    "How to" documents
    b) Business Content
    Online documentation for BI Content
    Extraction Documentation:
    "How to" documents
    Plug-In information
    3. Extracting non-cumulative data from R/3
    a) Explanations for the extraction
    b) Known errors
    Stocks (2LIS_40_S278/2LIS_03_BX)
    Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
    Industry-specific notes
    4. Technical information regarding non-cumulative info cubes in BW
    a) Warehouse Management
    b) Queries
    c) Update rules
    d) Known errors
    5. Stock Analyses in BW
    a) Explanations on data flow
    b) Known errors
    c) Tips and tricks
    6. Performance
    1. Release strategy
    Use the following objects depending on your BW and R/3 or plug-in releases:
    a) General information
    The following basic principle applies: The 0IC_C03 InfoCube (material movements) replaces the 0IC_C01 (material movement plant) and 0IC_C02 (material movements storage location) InfoCubes. The 2LIS_03_BX (material stocks) InfoSource or DataSource replaces the 2LIS_40_S278 (transfer BW: stock) 2LIS_03_S197 (material stocks storage location) and 2LIS_03_S198 (material stocks plant) InfoSource or DataSource. The 2LIS_03_BF (material movements) InfoSource or DataSource replaces the 2LIS_03_S195 (material movements storage location) and 2LIS_03_S196 (material movements plant) InfoSource or DataSource.
    We therefore STRONGLY recommend that you use the OIC_C03, 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM objects. We will continue to deliver and support any other objects mentioned in this note, but only for reasons of downward compatibility. These objects will not be enhanced because they are based on obsolete technology.
    For information about the general support for DataSources based on information structures, see also Note 543002.
    As of PI 2002.2, the 2LIS_03_BX DataSource is available for Release 4.0B and higher.
    As of PI 2001.2, the 2LIS_03_BF and 2LIS_03_UM DataSources are available for Release 4.0B and higher.
    The 0IC_C03 InfoCube is available as of Release 3.0B.
    b) Recommended objects for BW Release 3.0B and higher
    InfoCube: 0IC_C03 (Material movements)
    InfoSources and update rules:
    2LIS_03_BX (stocks) - available for Release 3.0B as of Support Package 10
    2LIS_03_BF (movements)
    2LIS_03_UM (revaluations)
    If your Support Package version for Release 3.0B is Support Package 9 or lower, you have the alternative option of using the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons stated above, we recommend that you change to 2LIS_03_BX as of Support Package 10. For more information, see Note 588015.
    c) Recommended objects for BW Releases 2.0B and 2.1C
    InfoSources: 2LIS_03_BX (stocks) - available for Release 2.0B as of Support Package 30
                                    - available for Release 2.1C as ofSupport Package 22
                2LIS_03_BF (movements)
                2LIS_03_UM (revaluations)
    If you are using Release 2.0B Support Package 29 or lower or Release 2.1C Support Package 21 or lower, you can alternatively use the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons given above, we recommend that you change to 2LIS_03_BX as of Support Package 30/Support Package 22. For more information, see Note 588015. Unfortunately, we cannot provide the 0IC_C03 InfoCube and related update rules. If you need to use this InfoCube, we can provide a similar solution to the one provided for Releases 3.0B or higher as part of a consulting project. Note that Note 589024 does not apply in this case.
    d) Obsolete objects
    If you are using R/3 Release 3.1I and do not intend to upgrade to a higher release (regardless of the BW release) in the foreseeable future, use only the 0IC_C01 and 0IC_C02 InfoCubes and the related InfoSources or DataSources 2LIS_03_S195 - 2LIS_03_S198. If you are using the Healthcare industry solution and are interested in using the 0IC_C01_Q0020 and 0IC_C01_Q0021 queries, you can also use the 0IC_C01 InfoCube and related objects. Unfortunately, there is no automatic data migration for the transition from 0IC_C01/2 to 0IC_C03. See also Note 804781 for a complete overview of all key figures in 0IC_C03 that are also possible in 0IC_C01/2.
    e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
    For more information, see Note 591063.
    2. Sources of information
    The main sources of information are located in the BW online documentation in the BW section of the SAP Service Marketplace and in the IMG documentation for the Plug-In. Other useful information is contained in various notes. These notes are listed under headings 3 - 6 below.
    a) BW technology
    This area contains documentation on the technical mapping of stock analyses in SAP BW.
    Online documentation SAP BW (http://help.sap.com)
    -> Documentation -> SAP NetWeaver -> '04
    -> Information Integration -> SAP BW
    i Stocks
        -> BI Platform -> OLAP
        -> Performance Optimization -> Stocks
    ii Validity Table
        -> Data Warehousing
        -> Administrator Workbench -> Modeling -> InfoCube
        -> Additional functions for InfoCube maintenance
        -> Stock Parameter Maintenance
    iii Compression
        -> Data Warehousing
        -> Administrator Workbench -> Data Warehouse Management
        -> Process Management
        -> Managing Data Targets
        -> Managing InfoCubes -> InfoCube Compression
    iv Aggregation
        -> Data Warehousing
        -> Administrator Workbench -> Modeling
        -> InfoObject -> Create InfoObject: Key Figure
        -> Aggregation v Exception Aggregation
        -> BI Platform -> OLAP
        -> Special OLAP Functions and Services
        -> Aggregation
        -> Scenarios for the Use of an Exception Aggregation
    "How to" documents
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW InfoIndex
    -> In the information index: N ("Non-cumulatives") ->
    "Non-Cumulative Values 3.x (ppt)"
    b) Business Content
    This area contains the business content representation of stock analyses in SAP BW, based on the SAP R/3 process and object model.
    Online documentation for BI Content (http://help.sap.com)
    -> Documentation -> SAP NetWeaver -> '04
    -> Information Integration: BI Content
    -> BI Content -> Supply Chain Management
    -> Supply Chain Performance Management -> Inventory Management
    Documentation for extraction (OLTP system)
    -> Transaction SBIW
    -> Business Information Warehouse
    -> Settings for application-specific DataSources
    -> Logistics
    Here you will find the relevant documentation for each of the relevant nodes.
    "How to" documents
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW InfoIndex
    -> in the information index: N ("Non-cumulatives") ->
    "How to... Handle inventory management scenarios in SAP BW 3.x" (pdf)
    Plug-In information
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW Extractors - Plug-in
    3. Extracting non-cumulative data from R/3
    This section explains the extraction process in the R/3 system and it gives an overview of known errors and their solutions.
    a) Explanations for the extraction
    Determining transaction keys
    Note 492828
    Determining the component
    When stocks are initialized, the 'MM' core application is transferred, regardless of which component you specify in Customizing under 'Specify Industry' (TAC MCB_). You must implement Note 323018 for this purpose.
    In most cases, the 'MM' Core application is also used when you initialize documents and for the delta load. However, 'IS-R' is transferred as the component if Retail is set as the component and you are working with stock transfers or movements for material group articles (MATNR <> MATBF).
    To create the component, the BW enrichment is required during extraction. For more information, see Notes 315880 and 353042.
    The "GETSYSDEF" report provides the system setting.
    Creating non-cumulative relevance
    In general, the non-cumulative relevance is set to '1', meaning 'relevant'. The exceptions are consumption postings (BSTTYP = V and BSTAUS = V) and postings for material group articles (MATNR <> MATBF). Value '2' is assigned in these cases.
    Logistics data extraction: Customizing Cockpit (transaction LBWE)
    You can configure the 2LIS_03_BF und 2LIS_03_UM DataSources in application 03. You cannot configure the 2LIS_03_BX DataSource in the Customizing Cockpit. To activate the 2LIS_03_BX DataSource, see Note 631345.
    Generic extraction of stocks
    This function is available as of PI 2003.1. For lower release levels, a consulting solution can be implemented on request (contact SAP in this case).
    User exit (SAP enhancement RSAP0001)
    Note 413807
    Update methods/extract structures/XPRAs
    i  Update methods (V3 update, DeltaQueue, and so on).
    Notes 380078, 396647, 486784 and 505700.
    For information about the automatic conversion of update methods in the logistics extraction, refer to the release notes for plug-in 2003.1
    DataSources for application 03 are delivered by default with the "Unserialized V3 Update" method.
    A change to "Queued Delta" may occur.
    For performance reasons, you should not select "Direct Delta".
    ii Changes to extract structures/XPRAs
    Notes 328181, 489259, 511657 and 566917.
    If you try to add another field from the pool to the "2LIS_03_BF" DataSource , the system issues error message "D0 322".
    Possible reason:
    XPRA "RMCSBWXP_IM_01" did not run after you imported the plug-in. This XPRA is responsible for comparing customer fields in the extract structure (enhancement) with new default fields in the extract structure (SAP). This error message appears as a result.
    b) Known errors
    Stocks, movements and revaluations are transferred to BW using various extractors. All known errors and proposed solutions of these three extractors are listed below.
    Stocks (2LIS_03_BX/2LIS_40_S278) -> see Note 691228.
    i Rounding error/valuation at company code level
        Notes 663681 and 762219
    ii Project stocks
        Note 535657
    iii Valuated sales order stocks or project stocks
        Notes 487043, 616119, 674351 and 756151
    iv Vendor consignment stocks
        Notes 585619 and 726485
    v Special stocks for customers/vendors
        Note 533682
    vi Valuation class
        Note 684789
    vii Stock in transit
        Notes 767786 and 898231
    Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
    i Delta ability/procedure
        Notes 385703 and 581778
    ii Update methods (V3 update, delta queue, qRFC and so on)
        Notes 339691, 444261, 498484 and 631562
    iii Missing BW derivation (component,
        transaction key, and so on)
        Notes 315880 and 353042
        Caution: You MUST read these notes
        BEFORE you transfer data to the BW system.
    iv Movements (2LIS_03_BF)
        - Returnable packaging with customer
          Notes 512597 and 530730
        - Vendor consignment
          Notes 585139 and 607710
        - Project stocks
          Note 522770
        - Stock transfers
          Notes 399929, 557378 and 628090 (stock in transit/
          valuation type)
        - Purchase orders with account assignment (consumptions)
          Notes 587320 and 629726 (non-valuated materials,
          see also Notes 752607 and 790506)
        - Batches
          Notes 445632 and 685450
        - Incorrect stock type
          Notes 438649 and 451355
        - Customer consignment
          Note 563342
        - Incorrect / missing valuation class
          Notes 735425, 747581 and 770858
        - Returns (movement types 122/123)
          Notes 741396 and 763424
        - Profit center
          Note 769660
        - Subsequent adjustments
    Note 822396
    v Revaluations (2LIS_03_UM)
        - Incorrect update because the
          BSTAUS and BSTTYP fields are missing
          Notes 494288 and 675610
        - Missing BW derivation of characteristics with settlement ofrequests
          Notes 523298 and 747361
        - External display of the WBS element does not exist
          Note 512611
        - Incorrect transaction key during setup
          Note 587241
        - Incorrect sign
          Note 587283
        - Duplicate document for MR22
          Note 587304
        - Incorrect/missing document number
          Notes 489290, 500825, 507958, 521046, 619482,
                  667534, 739050, 839711, 845307, 856669 and
                  864630
        - The BUZEI field is not filled
          Note 599731
        - Currency field not filled
          Note 612131
        - Returns (movement types 122/123)
          Note 715176
        - Reconstruction report RMCBNERP
          Note 735209
        - Missing valuation class
          Note 837052
    vi Master data (0STOCKTYPE/0STOCKCAT)
          Note 766954
        - 0STOCKCAT_TEXT is not filled since the value 'U' has not been added to the BSTTYP domain.
          Note 907195
    Industry-specific notes
    i IS Retail
    - Revaluation at retail (2LIS_40_REVAL)
    Notes 533577 and 600460
    - Miscellaneous
    Note 841878
    ii IS Oil/IS Mine
    - G/L quantity for two-step stock transfer procedure
    Notes 608744, 608975 and 629320
    4. Technical information regarding non-cumulative info cubes in BW
    In addition to the relevant sections in the online documentation, there are a number of explanatory notes that will help you to analyze problems. Section 4 e) deals with known errors and proposed solutions.
    a) Warehouse Management
    Validity table: Notes 360249 and 534865
    Selective deletion: Note 510680
    Aggregates: Note 456359
    ODS capability: Notes 322303, 323811, 385099, 417703, 581778,
    747037, 752492/782314 and 773823
    DataMart/Open Hub capability: Notes 375098, 566145 and 566762
    Compression (updating the stock marker)
    ->>> ESSENTIAL INFORMATION <<<-
    You can see in the log whether or not the stock marker was updated during the compression (as of 3.0B Support Package 13)
    For example:
    "START cond CUBE IC11 at 165446 on 20030514 maxreqid 23282 maxcnsid 0 refpoint update + null elim" ->
    "refpoint update" or "no refpoint update" provides the relevant information.
    See Notes 613701 and 639253 if you are using Oracle 9.
    Also see Notes 643687 and 655798.
    For a BW system with several application servers, see also Note 834829.
    ->>> ESSENTIAL INFORMATION <<<-
    b) Queries
    -> For information about the recommended procedure for analyzing query problems see the following note: Note 370004
    Slow-moving item/slow seller reports: Note 541559
    A How to document is also available:
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW InfoIndex
    -> in the information index: M ("MultiProviders") -> "MultiProviders (incl. Slow Moving Item Scenario) ..."
    c) Update rules
    The following special features are provided for updating in non-cumulative cubes:
    The non-cumulative key figure has to be included with the relevant cumulative value(s) in the InfoCube definition.
    Only receipt key figures are provided for updating from the InfoSource with the stocks.
    The issue and receipt key figures are provided for updating from the InfoSource with movements.
    Therefore, from a technical point of view, stocks are written to the receipt key figure. The process of differentiating between the stocks and the remaining receipts then takes place in the InfoCube using record type = 1 (InfoObject: 0RECORDTP) in the technical dimension table (this also sets up the connection to the validity table).
    The OLAP processor dynamically calculates non-cumulative key figures in the query (taking into account the issues/receipts and the validity table).
    d) Known errors
    Warehouse Management
    i Loading data
         Notes 534865 and 529610
    ii MultiCube/MultiProvider
        Note 435227
    iii Compression (updating the stock markers)
        Notes 613064, 613701 and 615349
    iv Updating
         Note 574341
    Queries
    i Fiscal year variant characteristic (0FISCVARNT, 0FISCPER
    and 0FISCYEAR)
        Note 490067
    ii Exception aggregations
        Notes 145630 and 607608
    iii No/multiple time restrictions
         Note 388983
    5. Stock Analyses in BW
    This section explains the data flow in BW and provides an overview of known errors and their solutions. This section also explains certain limitations and workarounds for same.
    a) Explanations on data flow
    See the How to paper from Section 2 b)
    "How to... Handle inventory management scenarios in SAP BW 3.x" (PDF).
    Note that the 2LIS_03_UM can also be loaded before the 2LIS_03_BF.
    You will find further information on the SAP Service Marketplace:
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW Business Content
    -> SAP Supply Chain Management
    -> Supply Chain Performance Management
    -> In the navigation area on the left: Related Topics
    -> Business Content
    -> Inventory Management.
    b) Known errors
    0IC_C03
    Notes 637927, 655798, 668085 and 710404
    0IC_MC01
    Note 664520
    Queries
    Notes 534429, 630034 and 676960
    c) Tips and tricks
    Analyses in BW with the storage location (0STOR_LOC) and stock characteristic (0STOCKTYPE) characteristics in the drilldown.
    Solution: Note 589024 (see also Notes 201327, 322335, 456106, 506077 and 543188) and the How to document
    -> http://service.sap.com/bw
    -> In the navigation area on the left: Services & Implementation
    -> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
    "How to... Realize summarized display of stock values on storage"
    Stock transfers in the two-step stock transfer procedure/differences between analyses in BW and the R/3 transaction MB5B
    If you notice different results for the issue and receipt quantities of the total stock during the analysis of stock transfers in the two-step procedure, for example, storage location to storage location within a plant (movement types 351 and 101), add the "0STOCKTYPE" characteristic to the drilldown. Where necessary, filter according to the values "A" (unrestricted) and "H" (transit). You will then find the same values under stock type "A" and in transaction MB5B (if you select the storage location stock or the valuated stock).
    Individual analysis of revaluations
    After stock is initialized using the 2LIS_03_BX InfoSource, load revaluations into the 0IC_C03 InfoCube with the 2LIS_03_UM InfoSource. By doing this, you avoid uploading movements with the 2LIS_03_BF InfoSource. If you do so, the non-cumulative values (quantities and values) can no longer be calculated. Reason: When you initialize stocks, DIM IDs are created for 0BASE_UOM and 0LOC_CURRCY. As a result, all stock markers for 0BASE_UOM have an entry other than ' '. With revaluations, only values are updated-all quantities and their units are updated with ' '. This means that you can no longer assign revaluations to the stock markers because the units of measure are inconsistent. Solution: Update the revaluations with quantities also, as you did for the values (the result for the quantities is always RESULT = 0).
    Incorrect results if quantity key figures and value key figures are analyzed together.
    For example, you only displayed quantity key figures in the current drilldown. If you now add value key figures, the quantity key figures are no longer calculated correctly (the reverse also applies). As in the case of individual analyses of revaluations, movements may not be assigned to the stock markers due to missing DIM IDs. As a result, stock cannot be recalculated correctly either. This should not usually occur when the 0IC_C03 InfoCube is filled with the 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM InfoSources (this is also the case with the other relevant Business Content InfoCubes, for example 0CP_IC_C1 or 0RT_C36/37). However, it may occur because of certain loading processes, for example. Solution: Update the quantities (or values) in the same way as the values (or quantities) (RESULT = 0 is always the result for the quantities or values). See Note 643291 for the 0CP_IC_C1 InfoCube.
    Enhancing the 0IC_C03 InfoCube with additional characteristics
    These additional characteristics must be updated from the 2LIS_03_BX InfoSource, as well as from the 2LIS_03_BF and 2LIS_03_UM InfoSources, only then can movements be assigned to stock markers (see the two preceding points).
    The following enhancements are possible:
    1. Valuation type (0VAL_TYPE)
    Source field from 2LIS_03_BX/BF: BWTAR
    2. Company code (0COMP_CODE)
    Source field from 2LIS_03_BF/UM: BUKRS
    3. Valuation area (0ID_VALAREA)
    Source field from 2LIS_03_BX/BF/UM: BWKEY
    4. Vendor (0VENDOR/0GN_VENDOR) - for vendor consignment stocks
    Source field from 2LIS_03_BX/BF/UM: LIFNR
    This is delivered with BI Content 3.3 Add-On (see SRM Business Content Online documentation).
    5. Customer (0CUSTOMER) - for consignment stocks at customer
    Source field from 2LIS_03_BX/BF/UM: KUNNR
    6. Sales order (0DOC_NUMBER/0S_ORD_ITEM) - for sales order stocks
    Source field from 2LIS_03_BX/BF: KDAUF/KDPOS
    7. Project number (0WBS_ELEMT) - for project stocks
    Source field from 2LIS_03_BX/BF: PS_PSP_PNR
    8. Evaluation class (0VAL_CLASS)
    Source field from 2LIS_03_BX/BF/UM: BKLAS (Note 684789)
    Enhancement possibilities for 2LIS_03_BX:
    Note that the 2LIS_03_BX DataSource cannot be extended in the same way as the 2LIS_03_BF DataSource, for example.
    Only SAP can enhance this DataSource (Note 684789).
    Other enhancements are no longer useful since fields, such as the movement type, G/L account or profit center do not in appear in the stock tables (for example, MARC and MARD) but only in the movement tables (for instance, MSEG).
    Evaluation restrictions that occur as a result (similar to the two preceding points) can only be resolved by a data enhancement (for example, reading from a DataStore object with all material movements) subsequent to the extraction or by not using 2LIS_03_BX. In both cases, all material movements must exist in the source system. If this is not the case, you must read from the corresponding archive files for the extraction.
    Changing the exception-aggregation of the stock key figures
    There is a predefined exception aggregation for stock key figures (for example, "last value") in the key figure definition. If you want to override these in the query definition, proceed as follows:
    -> Create a new calculated key figure.
    -> Drag the relevant basic key figure to the formula area.
    -> Choose "OK".
    -> In the next window, choose "Extend >>".
    -> Then, maintain the required exception aggregation and the reference characteristic.
    Mapping FIFO logic
    The data structures in the 0IC_C03 InfoCube allow FIFO logic to be mapped using the relevant query definitions. In this case, contact your SAP consultant.
    Unexpected or negative stock values due to FI document summarization
    If FI document summarization is activated for the MATNR field, revaluations (2LIS_03_UM) are transferred to BW without a material number. As a result, complete analyses are no longer possible at material number level. For more information, see Notes 36353 and 497992.
    Options for the R/3 and BW data verification/consistency check
    TAC MB5B <-> Queries 0IC_C03_Q???
    (Stocks/movements R/3 <-> BW)
    TACs MC.? <-> Queries 0IC_C03_Q???
    (Inventory controlling LIS <-> BW)
    Reports MBQUANT and RM07MMFI
    (verification of the R/3 data)
    Notes 739863 and 745788 provide additional information in this regard, as well as the options that exist to clean up data in BW.
    With Note 766622 you can also create a LOG file for the extraction.
    Archiving
    See the corresponding "How to" document about archiving that is available on SAP Service Marketplace:
    -> http://service.sap.com/bw
    -> In the navigation area on the left: SAP BW InfoIndex
    -> in the information index: A ("Archiving")
    MultiProvider and non-cumulative key figures
    Note 690475
    Displaying the contents of the InfoCube with TAC "LISTCUBE"
    Note 629451
    Snapshot scenario
    The "How to" document mentioned in section 2 b) "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)" contains important information about the advantages and disadvantages of mapping stocks using a snapshot procedure.
    Validity period of stocks
    You can use transaction RSDV to determine the time period in which stocks can be calculated. This time period is determined automatically by the oldest and the most recent material movement. If you have a reporting requirement to display further stocks in the past, you can use the RSDG_CUBE_VALT_MODIFY report to manually change the time period.
    Evaluations of cross-company code stock transfers.
    Corresponding reports are currently not possible using the 2LIS_03_BX/BF/UM DataSources. For further information, see the following "How t"o document:
    -> http://service.sap.com/bw
    -> In the navigation area on the left: Services & Implementation
    -> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
    "How to... Report on cross company stock in transit", which allows you to carry out evaluations in BW similar to the ones in R/3 transaction "MB5T".
    0IC_C03 data modeling
    Due to the different characteristic value calculation for stock quantities and values, a MultiCube scenario ("sparse tables") is useful in this case, one InfoCube for quantities and one for values.
    You can then execute common stock quantities, values and evaluations using queries on a MultiCube.
    The 0IC_C03 InfoCube currently uses a key figure model (various specific key figures, such as inspection stock, stock in transit and so on). In this case, an account model is suitable:
    - Three key figures: Stock quantity, stock value and valuated stock quantity (including the movement key figures)
    - Based on stock instance/type, you can then limit the query to the special stock
    - Advantage: Uses less database space
    - Disadvantage: The load for the OLAP processor is higher and there is more work during the query definition, the other approach may also be more transparent for the end user.
    Inventory management and ODS
    ODS objects cannot admit any stock key figures (see Notes 752492 and 782314) and, among other things, they do not have a validity table, which would be necessary. Therefore, ODS objects cannot be used as non-cumulative InfoCubes, that is, they cannot calculate stocks in terms of BW technology.
    In this connection, you should use the ODS technology only for:
    - Document-related reporting or the Enterprise DataWarehouse layer based on the 2LIS_03_BX/BF/UM InfoSources (see Notes 581778 and 747037).
    - The implementation of a snapshot scenario; see the How to document mentioned in section 2 b) for more information:
    "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
    Implement Note 773823 to be able to update the 2LIS_03_BX InfoSource to an ODS.
    If you want to activate another ODS object for the 2LIS_03_BF and 2LIS_03_UM DataSources before the 0IC_C03 InfoCube, we recommend a parallel update.
    However, if you want the InfoCube to be filled by a subsequent update from the ODS, take the following into account:
    Documents that are entered after the stock initialization (CPUDT field > stock initialization key date) and are posted back to a period before the stock initialization (BUDAT field < stock initialization key date),
    must be updated with a delta request in the InfoCube, because only these requests can be compressed with a stock marker update.
    Therefore, mechanisms for which the movements are different before and after the stock initialization (as a result of restrictions on the posting date) are incorrect in this case. However, if you want to work with the requests in question, you must restrict the movements using the date of entry (CPUDT). Otherwise the stock evaluations will be incorrect due to the compression logic used.
    The same problem occurs if documents are posted to the future (CPUDT field > stock initialization key date and BUDAT field > stock initialization key date).
    Posting to a prior period and postings to the future
    If you can post this type of material documents in the system, take note of the documents that caused the initialization run (transaction MCNB, or report RMCBINIT_BW)during the reconstruction in R/3 (transaction OLI1BW, or report RMCBNEUA):
    1. BUDAT < stock initialization key date and CPUDT > stock initialization key date
    You execute the report with a date restriction (for example, upper limit = key date of stock initialization) to avoid a posting block.
    -> Postings to a prior period are selected by mistake.
    -> Solution: You MUST set a posting lock (if this is not possible, it may help to select according to the document number).
    2. BUDAT > stock initialization key date and CPUDT < stock initialization key date
    Here the same applies as described under point 1, however, the documents are then missing in the setup table. You can still make restrictions according to the posting date but you must set a relatively high upper limit.
    Consumption key figures in 0IC_C03 (the same as LIS reports)
    See Note 804781.
    Avoiding data inconsistencies, HASH solution.
    See Note 838050 for more information.
    Connection between transaction keys and reversals. See Note 352344 (and an example in Note 745788).
    Suppressing the display of the previous period in the BEx Web Analyzer.
    See Note 623944.
    6. Performance
    a) General BW/logistics extraction (TSV_TNEW_PAGE_ALLOC_FAILED/ SYSTEM_IMODE_TOO_LARGE)
    Notes 409641, 417307, 419465, 548845 and 589997
    b) Extraction 2LIS_03_BX
    The recommended setting in the RMCBINIT_BW report for 'Number of data records per LUW' is 5000. Higher values may cause the following errors:
    TSV_TNEW_PAGE_ALLOC_FAILED
    TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
    TSV_LIN_ALLOC_FAILED
    You can reduce an extremely long runtime by setting up the stock individually for each plant. For more information, see Note 728360.
    When you run the report, the "Transfer Zero Stocks" option must NOT be active, because this will significantly increase the runtime.
    This is no longer required as of Note 823951 (for more information, see Note 655798).
    c) Extraction 2LIS_03_UM
    Notes 537235 and 585750
    d) Extraction 2LIS_03_BF
    Note 454267
    e) Warehouse
    Due to the stock marker generation technology, it is normal for the E table to be larger than the F table in the non-cumulative InfoCubes.
    As a result of the different updating of stock quantities and values (see Note 589024) required by the R/3 data model, movement data usually generates two entries in the F table.
    To reduce the data volume of the 0IC_C03 InfoCube, you can distribute quantity and value key figures to two InfoCubes. As a result, the key figures have the same characteristic value update again. You can then use MultiCubes to execute common evaluations of quantities and values.
    f) Queries
    Notes 419490 and 784682
    Message was edited by:
            Jr Roberto

  • How to embed information in an image

    im trying to add text to an image without it displaying on the image. basically i need to know how to embed text in a jpeg. currently im trying to send information by adding data to the least significant bit but to no avail.
    any help will be much appreciated. thanks.

    heres how it went kevin
    i loaded an image. the image data is a cluster. by using unbundle by name i can separate it to components. the rgb info on the data is located in "image" in the unbundle. send this to a decimate...extracting 3 values. these three values are the rg and b components of the image. the rest is as i mentioned above. take either r,g or b value (doesnt matter which color you encode the data to) do a string to byte array. send through an empty for loop with the string length wired to the count...making the loop run as many times as the number of characters ur embedding. the result is sent to replace array subset (with index 0) and then interleaved with the remaining 2 channels to form back the composite rgb...send back to a bundle by name with the characteristics coming from the original image data. draw flattened pixmap and output (this displayed pic with encoded data...no difference!!). extraction is a reverse process but inside the forloop place index array with index zero. loop count once again wired to original string length. output from the for loop goes to a byte to string and string indicator! let me know if it works for you
    dee.

Maybe you are looking for

  • Is it ok not to have phone in the dock?

    Is it ok to plug my phone into just the cord and not the dock, this way i can keep my case on. Is there any difference besides just having it sit up in the docking station. Message was edited by: soccerdogs89

  • How do I refer to the stage from a class?

    I have a class that places objects on stage with addChild(obj) it allowes me to position objects using pixels( say obj.x = 10; obj.y= 50; ) just fine but if I try this:  obj.x = stage.stageWidth / 2;  I get a message that I Cannot access a property o

  • Error during Exe preparation

    Dear Sir, We are using Labview 8.2 and developed the software code using it. In this code one button is used as Exit to exit from the code and shutdown the labview. In the code when i click on EXit button it got exited properly but when i prepared th

  • Date format problem in pl/sql

    Hi all, I want to convert a date in a text format like below: 7/2/2010 5:15:28 PM Could someonce advise on how to do to have a the above format please. Thanks Luc

  • Rsh between solaris

    Hi: Please your help. I have 2 solaris 8, called app01 and wss01. Also, I have 1 script in app01, it script only contains ls -lrt command. I try to run remotely my script from wss01, so I ran following sentence in wss01 wss01:/$> rsh app01 -l user01