OSS note regarding 0EC_PCA_3 extraction optimization

hello Frnds,
We are facing severe Data load issues with a load from 0EC_PCA_3 in production,
Could any one suggest OSS note regarding 0EC_PCA_3 extraction optimization
Thanks in Advance
raky

Rakesh
Also check this for General BW related Performance issues
Business Intelligence Performance Tuning [original link is broken]
Thnaks
Sat

Similar Messages

  • LIS Extract structure MC17I00ACT changed while implementing oss note 865254

    Hi,
    While i am trying to implement the oss notes 865254 , the sap defined data source 2LIS_17_I0ACTY , having the extracture MC17I00ACT , extract structure is modified and many  fields and includes are deleted .can any one please give soluation how to restore the original extract structure.its very urgent. please help me.
    thanks,
    sri.c

    Hi,
    it might be possible to get it back from the version management. I didn't do that, but you can try. Goto se11->Tools->Versions
    regards
    Siggi
    PS: Be careful and check the versions before.
    Message was edited by: Siegfried Szameitat

  • OSS Note - 409979 regarding dates

    Hi all,
    Did anyone had to apply the OSS Note 409979 and also I saw the process of downloading the note, it asks for setting up the Download manager, is there an easy way to download this or do I have to follow the entire procedure of setting up the Java runtime environment.  Please let me know.
    Thanks,
    Sabrina.

    Hi Sabrina,
    Though, the instructions can be taken by Download manager, the easiest way is the following.
    Suppose you found the note and are in the screen with its description (Text tabstrip).
    Click on a 'Correction Instructions' tabstrip (the 4th from the left).
    Click on Ref Number at the left of the string (# 0000229616).
    Click on a Object Name 'Conversion_Exit_Peri6_Input'.
    The new window will show the code of correction instructions, including the piece of code after which you should delete another piece and insert the correcting one.
    You can copy-paste instructions. But in your case you need just delete some code from 'Conversion_Exit_Peri6_Input' FM.
    Try to force basis guys to get a dev key to implement correction.
    Best regards,
    Eugene
    Message was edited by: Eugene Khusainov
    Message was edited by: Eugene Khusainov

  • 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

  • OSS Notes Please

    Dear Gurus,
    Can anyone send me the following OSS notes if u have.  567747, 130253 and 417307.  Your kind help will be definitely awarded.
    My mail ID is [email protected]
    Best Regards
    Mohan Kumar
    Message was edited by: mohan kumar

    hi Mohan,
    i think you will need to have access to oss yourself,
    note 567747 is composite one that contains several notes.
    sent to you mail ...
    130253
    Symptom
    Uploading transaction data to BW takes too long
    Other terms
    Business Warehouse, data upload, batch upload, transaction data upload,
    performance, runtime, data load, SPLIT_PARTITION_FAILED ORA00054
    Reason and Prerequisites
    Loading data from a mySAP system (for example, R/3) or from a file takes a very long time.
    Solution
    The following tips are a general check list to make the mass data upload to the Business Warehouse (BW) System as efficient as possible.
    Tip 1:
    Check the parameter settings of the database as described in composite Note 567745.
    Check the basis parameter settings of the system.
    Note 192658 Setting basis parameters for BW Systems
    See the following composite notes:
    Note 567747 Composite note BW 3.x performance: Extraction & loading
    Note 567746 Composite note BW 3.x performance: Query & Web applications
    Tip 2:
    Import the latest BW Support Package and the latest kernel patch into your system.
    Tip 3:
    Before you upload the transaction data you should make sure that ALL relating master data has been loaded to your system. If no master has been loaded yet, the upload may take up to 100 percent longer because in this case, the system must retrieve master data IDs for the characteristic attributes and it must add new records to the master data tables.
    Tip 4:
    If possible, always use TRFC (PSA) as the transfer method instead of
    IDocs. If you (have to) use IDocs, keep the number of data IDocs as low
    as possible. We recommend an IDoc size of between 10000 (Informix) and 50000 (Oracle, MS SQL Server).
    To upload from a file, set this value in Transaction RSCUSTV6.
    To upload from an R/3 system, set this value in R/3 Customizing (SBIW -> General settings -> Control parameters for data transfer).
    Tip 5:
    If possible, load the data from a file on the application server and not from the client workstation as this reduces the network load. This also allows you to load in batch.
    Tip 6:
    If possible, use a fixed record length when you load data from a file (ASCII file). For a CSV file, the system only carries out the converison to a fixed record length during the loading process.
    Tip 7:
    When you load large data quantities from a file, we recommend that you split the file into several parts. We recommend using as many files of the same size as there are CPUs. You can then load these files simultaneously to the BW system in several requests. To do this, you require a fast RAID.
    Tip 8:
    When you load large quantities of data in InfoCubes, you should delete
    the secodary indexes before the loading process and then recreate them afterwards if the following applies: The number of the records that are loaded is big in comparison to the number of records that already exist in the (uncompressed) F fact table. For non-transactional InfoCubes, you must delete the indexes to be able to carry out parallel loading.
    Tip 9:
    When you load large quantities of data in an InfoCube, the number range buffer should be increased for the dimensions that are likely to have a high number of data sets.
    To do this, proceed as follows. Use function module RSD_CUBE_GET to find the object name of the dimension that is likely to have a high number of data sets.
    Function module settings:
    I_INFOCUBE = 'Infocube name'
    I_OBJVERS = 'A'
    I_BYPASS_BUFFER = 'X'
    The numbers for the dimensions are then contained in table 'E_T_DIME', column 'NUMBRANR'. If you enter 'BID' before this number, you get the relevant number range (for example BID0000053).
    You can use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Other tools --> Number ranges) to display all number ranges for the dimensions used in BW if you enter BID*. You can use the object name that was determined beforehand to find the required number range.
    By double-clicking this line, you get to the number range maintenance. Choose Edit -> Set-up buffering -> Main memory, to define the 'No. of numbers in buffer'.
    Set this value to 500, for example. The size depends on the expected data quantity in the initial and in future (delta) uploads.
    !! Never buffer the number range for the package dimension !!
    Tip 10:
    When you load large quantities of data, you should increase the number
    range buffer for the info objects that are likely to have a high number of data sets. To do this, proceed as follows:
    Use function module RSD_IOBJ_GET to find the number range name of the info object that is likely to have a high number of data sets.
    Function module settings:
    I_IOBJNM = 'Info object name'
    I_OBJVERS = 'A'
    I_BYPASS_BUFFER = 'X'
    The number for the info object is in table 'E_S_VIOBJ', column 'NUMBRANR'. Enter 'BIM' in front of this number to get the required number range (for example BIM0000053).
    Use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Other tools --> Number ranges) to display all number ranges used for the info objects in BW by entering BIM*. By entering the object name determined beforehand you can find the desired number range.
    By double-clicking this line you get to the number range object maintenance. Choose Edit -> Set-up buffering -> Main memory, to define the 'No. of numbers in buffer'.
    Set this value to 500, for example. The size depends on the expected data quantity in the initial and in future (delta) uploads.
    !! Never buffer the number range object for the characteristic 0REQUEST!!
    417307
    Symptom
    Performance load is too high/not justifiable during data load.
    Customizing settings via extractors IMG path (Transaction SBIW in the OLTP system; can be called directly in the OLTP or using Customizing, from the BW system) do not yield any considerable improvement or are not clear.
    The settings in Table ROIDOCPRMS or in the Scheduler in the BW system are not taken into account by some extractors. How is the data package size defined for the data transfer to the BW? Are there application-specific features to determine the package size? If so, what are they?
    Other terms
    SBIW, general settings extractors, MAXSIZE, data volume, OLTP, service API, data package size, package size, performance
    Reason and Prerequisites
    The general formula is:
          Package size = MAXSIZE * 1000 / size of the transfer structure,
                        but not more than MAXLINES.
    You can look up the transfer structure (extract structure) in Table ROOSOURCE in the active version of the DataSource and determine its size via SE11 (DDIC) -> Utilities -> Runtime object -> Table length.
    The system default values of 10,000 or 100,000 are valid for the MAXSIZE and MAXLINES parameters (see the F1 help for the corresponding fields in ROIDOCPRMS). You can use the IMG Transaction SBIW (in the OLTP system) "Maintain General settings for extractors" to overwrite these parameters in Table ROIDOCPRMS on a system-specific basis. You also have the option of overriding these values in the scheduler (in the target BW system). However, in the Scheduler (InfoPackage) you can only reduce the MAXSIZE. The advantage of using the Scheduler to carry out maintenance is that the values are InfoSource-specific.
    However, some extractors have their own flow logic which MAXSIZE does not load 1:1 from the ROIDOCPRMS.
    This Note does not cover all SAP applications.
    Solution
    Application/DataSource               Standard settings or note
    Generic extractor                     Standard (Example: Note 409641)
    Delta Extraction via DeltaQueue       Standard as of PlugIn 2000.2
                                               Patch 3
    LO-LIS                                 Standard
    Logistic Cockpit SD                       Notes 419465 and 423118
    Logistic Cockpit MM-IM:
    Extraction 2LIS_03_UM                     Notes 537235 and 585750
    Extraction 2LIS_03_BF                     Note 454267
               In general, the following applies to Logistic Cockpit Extraction: The package size set only serves as guideline value.
                Depending on the application, contents and structure of the documents, and the selection in the reconstruction program, the actual size of the transfer packages may differ considerably. That is not an error.
                For 'Queued Delta' update mode the package size of 9999 LUWs (=Logical Unit of Work, in this particular case documents or posting units per transaction are concerned) is set for LO Cockpit. However, if a transaction updated more than 10000 documents at once, the number 9999 would be invalid. This is because an update process cannot be split.
                In the case of a 'Direct Delta' update mode there is no package size for LUW bundling. In the DeltaQueue (RSA1) every LUW is updated individually.
               Also note the following:
                         If you want to transfer large data sets into the BW System, it is a good idea to carry out the statistical data setup and the subsequent data transfer in several sub-steps. In doing so, the selections for the statistical data setup and in the BW InfoPackage must correspond to each other. For performance reasons, we recommend using as few selection criteria as possible. You should avoid complex selections. After loading init delta with selection 1, the setup table has to be deleted and rebuilt with selection 2.
                         Bear the following in mind: The delta is loaded for the sum of all selections from the init deltas. Remember that the selections are made so that they do not impede the delta load, for example, if you have initialized the delta for the periods January 1st, 1999 to December 1st, 2000 and December 2nd, 2000 to August 1st, 2001 then you get a time interval from January 1st, 1999 to August 1st, 2001 in the BW. Documents from August 2nd, 2001 are no longer loaded.
    CO-OM                                     Note 413992
    PS                                        Standard or according
                                               to Note 413992
    CO-PC                                     Standard
    FI (0FI-AR/AP-3)                          First tables with open items(BSID for customers, BSIK for vendors) are read. The package size from the MAXISE field in Table ROIDOCPRMS is used in the extraction from these tables. If the packages are grouped together according to ROIDOCPRMS and a few data records still remain, these remaining records are transferred in one additional package.
    After the open items are extracted, the system extracts from the table of cleared items (BSAD for customers, BSAK for vendors). In this extraction,the package size from the MAXSIZE field is adhered to.
    FI (0FI-/AR/AP/-4 , new as of BW 30A) Like FI-AR/AP-3, but with one difference: if there are remaining records after the system reads the open items using the setting in the MAXSIZE field, they are not transferred in one extra package, but added to the first package of items read from the table of cleared items. For example, if 10 data packages with 15000 data records are extracted from Table BSID in accordance with ROIDOCPRMS, and 400 data records remain, the package size of the first data package from Table BSAD is 15400.
    Both new and changed records are formatted in the following sequence in the delta transfer: 1) new BSIK/BSID records; 2) new BSAK/BSAD records; 3) changed BSIK/BSID records; 4) changed BSAK/BSAD records.
    Package size 0FI_GL_4:
    Prior to Note 534608 and the related notes, package size could vary considerably since the MAXLINES were applied to the document headers only. Then all documents lines for the document headers were read and transferred. As a result, the packages were 2 to 999 times as large as MAXLINES depending on the number of line items per document.
    Note 534608 and the related notes changed the logic so that the MAXLINES is now also applied to the document lines. For each package, MAXLINES can be exceeded by up to 998 lines since a document is always transferred completely in one package. Smaller 'remaining packages' may also occur; for example if MAXLINES = 10000, and 10000 document headers with 21000 lines are selected, 2x10000 and the remainder of 1000 were were transferred in a separate package. Selection logic in 0FI_GL_4: Selection of the new FI documents via CPUDT -> the changed documents are then selected via Table BWFI_AEDAT. When changing the selection from new to changed documents, a package may occur which consists of the 'remainder' of the CPUDT selection and the first package of the BWFI_AEDAT selection. This package can then have a maximum size of 2 x MAXLINES.
    FI-FM                                  Note 416669
    EC-PCA                                 For the most part, the systemadheres to the standard settings but for technical reasons, packages packages smaller than the MAXSIZE or 7200 larger than the MAXSIZE may be omitted in Table ROIDOCPRMS
    FI-SL                                  as in EC-PCA
    PT                                     Standard (refer to Note
                                           397209)
    PY                                     Standard
    PA                                     Standard
    RE                                     Standard
    ISR-CAM (Category Management,
             new as of PlugIn 2001.1)     Standard
    CO-PA                                  During the initialization and fullupdate in the profitability analysis, a join is always read from two tables (For details see Note 392635). To avoid terminations caused by Select statements that run for too long, access occurs with intervals for the object numbers (fixed size 10,000). New intervals are read until the package size requested by BW is reached. Therefore the size of the data package is always equal to or larger than the specification, but it can vary considerably.
    Master data:
    Business partner                       Standard
    Product                                Standard
    Customer                               Standard
    Vendor                                 Standard
    Plant                                  Standard
    Material                               Standard
    567747
    Symptom
    You want to improve the performance of the extraction and loading of your data into SAP BW 3.x.
    Solution
    This is a composite note that deals with performance-relevant topics in the area of extraction and loading.
    If you encounter performance problems, ensure that the current Support Package has been imported.
    This note is continually updated. You should therefore download a new version on a regular basis.
    You will find further documents in the SAP Service Marketplace, alias bw under the folder "Performance".
    Contents:
    I.    Extraction from the OLTP
    II.   Loading generally
    III.  Master data
    IV.   Roll-Up/aggregate structure
    V.    Compression
    VI.   Hierarchies/attribute realignment run
    VII.  DataMart interface
    VIII. ODS objects
    IX.   Miscellaneous
    I.    Extraction from the OLTP
    Note 417307: extractor packet size: Collective note for applications
    Note 505700: LBWE: New update methods from PI 2002.1
    Note 398041: INFO: CO-OM/IM IM content (BW)
    Note 190038: Composite note performance for InfoSource 0CO_PC_01 and
    Note 436393: Performance improvement for filling the setup tables
    Note 387964: CO delta extractors: poor performance for Deltainit
    II.   Loading generally
    Note 130253: Notes on uploading transaction data into BW
    Note 555030: Deactivating BW-initiated DB statistics
    Note 620361: Performance data loading/Admin. data target, many requests
    III.  Master data
    Note 536223: Activating master data with navigation attributes
    Note 421419: Parallel loading of master data (several requests)
    IV.   Roll-Up/aggregate structure
    Note 484536: Filling aggregates of large InfoCubes
    Note 582529: Rollup of aggregates & indexes (again as of BW 3.0B Support Package 9)
    V.    Compression
    Note 375132: Performance optimization for InfoCube condensation
    Note 583202: Change run and condensing
    VI.   Hierarchies/attribute realignment run
    Note 388069: Monitor for the change run
    Note 176606: Apply Hierarchy/Attribute change ... long runtime
    Note 534630: Parallel processing of the change run
    Note 583202: Change run and condensing
    VII.  DataMart interface
    Note 514907: Processing complex queries (DataMart, and so on)
    Note 561961: Switching the use of the fact table view on/off
    VIII. ODS objects
    Note 565725: Optimizing the performance of ODS objects in BW 3.0B
    IX.   Miscellaneous
    Note 493980: Reorganizing master data attributes and master data texts
    Note 729402: Performance when compiling and searching in the AWB

  • OSS Note for dump in program LOLEAU02

    Hallo Everybody,
    I need help in finding an OSS notes for the runtime error MESSAGE_TYPE_X in the program LOLEAU02.The last modified date of this program is 6.11.2003.
    There are many OSS notes and I couldn't able to sort the OSS note for this particular runtime error.I have given some details about the dump.
    <b>
    User and Transaction
        Language key........ "F"
        Transaction......... "IW32 "
        Program............. "SAPLOLEA"
        Screen.............. "SAPLSCAC 0100"
        Screen line......... 0
    Information on where terminated
        The termination occurred in the ABAP program "SAPLOLEA" in "AC_SYSTEM_FLUSH".
        The main program was "SAPLCOIH ".
        The termination occurred in line 29 of the source code of the (Include)
         program "LOLEAU02"
        of the source code of program "LOLEAU02" (when calling the editor 290).
    Source Code extract
    24     WHEN 1.
    25 *     system_error
    26       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.
    27     WHEN 2.
    28 *     method_call_error
    >>       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
    30     WHEN 3.</b>
    Thanks in advance.Any inputs on this will be helpful.
    Regards,
    Raj

    Hi,
    Thanks Chandrasekar.
    The thread has the same dump except the main program which is <b>YQ9_UPLO</b>.In my case the main program is<b> SAPLSMTR_NAVIGATION</b>.
    Still the dumps occurs and I am unable to find the root cause. Any inputs will be som helpful.Thanks in advance.
    Regards,
    Raj

  • Help in finding an OSS notes for a SAP Program

    Hi,
    A runtime error TIME_OUT has occured in the program LSCD2F01.
    I need to find an OSS notes which deals with the correction of this dump.I have checked with the latest date of modification of this program and it is 18.02.2006
    So the OSS notes which has been generated earlier to this date has been implemented in the program.
    I have attached the Dump details below: Any inputs on this will be helpful.
    <b>Information on where terminated</b> 
      The termination occurred in the ABAP program "SAPLSCD1" in "READ_CD_FROM_DB".
        The main program was "SAPMSSY1 ".
        The termination occurred in line 1031 of the source code of the (Include)
         program "LSCD2F01"
        of the source code of program "LSCD2F01" (when calling the editor 10310).
    <b>Source Code Extract</b>
    1020 FORM read_cd_from_db CHANGING pt_cdhdr     TYPE cdhdr_tab
    1021                               pt_cdpos     TYPE cdpos_tab
    1022                               pt_cdpos_uid TYPE cdpos_uid_tab.
    1023
    1024   DATA: lt_cdhdr_for_uid TYPE cdhdr_tab
    1025        ,lv_guid_true     TYPE i.
    1026   FIELD-SYMBOLS: <fs_cdhdr> TYPE cdhdr.
    1027
    1028   CLEAR: lt_cdhdr_for_uid[], lv_guid_true.
    1029
    1030 * select header from cdhdr
    <b>>>>>   SELECT * FROM cdhdr INTO TABLE pt_cdhdr</b>
    1032            WHERE objectclas IN lt_sl_objectclas
    1033            AND   objectid   IN lt_sl_objectid
    1034            AND   changenr   IN lt_sl_changenr
    1035            AND   username   IN lt_sl_username
    1036            AND (
    1037                 (
    1038                   udate =  date_of_change
    1039                   AND
    1040                   utime >= time_of_change
    1041                  )
    1042                  OR
    1043                   udate >  date_of_change
    1044                 )
    Regards,
    Raj

    Check notes:
    459838 Performance improvement with very large datasets
    and
    671283 Performance problem with change documents material master
    Rob

  • ABAP dump in ECC 6.0 - Need OSS notes

    ABAP dump is coming when retriving data between select-endselect.
    Runtime Errors         DBIF_RSQL_INVALID_CURSOR
    Except.                CX_SY_OPEN_SQL_DB
    The problem cannot be resolved without correcting the application
    program.
    The statements MESSAGE, COMMIT WORK, ROLLBACK WORK, CALL SCREEN,
    BREAK-POINT, WAIT, CALL FUNCTION ... DESTINATION, CALL FUNCTION ...
    STARTING NEW TASK, RECEIVE RESULTS, CALL SELECTION-SCREEN, CALL
    DIALOG, CALL TRANSACTION cannot be used within a database
    loop.
    You can collect the data needed for these statements together in an
    internal table and process them
    in a loop.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_RSQL_INVALID_CURSOR" "CX_SY_OPEN_SQL_DB"
    Can you please give the OSS notes no. if anything is available.

    Hi Sreedevi..
    In the dump report, the piece of code where the dump occured will be shown
    something with >>>>>> sign in the line...
    Please copy and paste this peice of code..
    Thanks and Best Regards,
    Vikas Bittera.
    **Reward if useful**

  • OSS note is not working in production but works correctly in test system .

    hello friends ,
    weh have implemented one OSS notes , which is working corectly in Test system , but not working in production .
    Could you please let me know , what could be the reason ?
    OSS note no 1064273-
    Regards,
    Manoj

    Pls. check with Basis if the OSS note has been implemented properly and successfully.

  • In what type of HA context should OSS Note 1052984 be applied to?

    Hello,
    I was wondering if somebody could clarify the Term u201CHigh Availabilityu201D (HA) in an SAP Context.
    I installed a PI 7.11 (SID=ABC) system as part of an HA Cluster Failover.
    The u201CABCu201D system is running on Server Host u201C123u201D. 
    I have another Server Host, u201C456u201D, that is part of the HA Cluster Failover.  This server has two other SAP Instances u201CDEFu201D and u201CGHIu201D installed on it.
    When u201CABCu201D needs to failover, due to Hardware failure, etc, the two Instances u201CDEFu201D & u201CGHIu201D are shut down by the HA Cluster Software on host u201C456u201D, and then u201CABCu201D fails over to server u201C456u201D, and runs on it until the original host, u201C123u201D is available again for u201CABCu201D to run on.
    I was reading OSS Note 1052984, u201CProcess Integration 7.1- High Availabilityu201D, and in this noteu2019s context it seems like HA is referring to an Instance where the
    ASCS u2013 (ABAP System Central Services)
    SCS u2013 (JAVA System Central Services)
    DVEBMGS u2013 (Primary Application)
    DB u2013 (Database Instance)
    Are all installed on separate servers, and not necessarily on an u201CHAu201D cluster, where one SAP instance resides on one server and can failover to another node B server, when the need arises.
    Any insight in to what context Note1052984 is referring to would be very helpful.
    Thank you.
    Regards.

    Hi Hiko,
    You might find the answer to your questions on the following links:
    http://www.sdn.sap.com/irj/sdn/ha#section12
    http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/b09d53ac-8b0f-2b10-6798-ecfd55894839 [original link is broken]
    Hope this helps!
    Kind regards,
    Mark

  • Details of OSS Note in SAP tables

    Hi Experts,
    Do we have any standard report or a simple way by which I can get all the contents of a specific OSS note without going into SNOTE transaction. The reason why I am asking is for analysing a large volume of OSS notes. If I need to go through SNOTE and then find the objects it will be tedious. I know the table where in these details are there but I want to know if there is any report handy to use.
    Kindly help
    Regards,
    Vijay V

    Hello,
    I'm afraid, but there is no such report in SAP using which you'll get the content os any SAP note.
    Another option than SNOTE transaction is to use SAP marketpplace to findout the same.
    Regards,
    Nitin

  • Clarification about OSS note 677377 - E-mail to credit representative

    Hello,
    in the OSS note mentioned in the subject I find the following statement: "The document can be released directly from the e-mail".
    I have this question: the option to release the document from the e-mail is available only if the workflow is active?
    I made all the settings mentioned in the OSS note but I receive in SAPoffice only the notification with no option to release the SO.
    Thanks and best regards,
    Andrea

    Hi,
    try the following:
    open your workplace in SAP office and go to inbox folder. Click on unread or read documents and documents will be displayed on the right side of the screen. Select one of the documents and click on right button of the mouse and click on execute. You´ll execute the tcode you set in execute parameters on your message.
    Regards,
    JM

  • OSS Note for MIGO "Update terminate (SAPSQL_ARRAY_INSERT_DUPREC)"

    Dear all
    I am facing problem during MIGO GR reference Others, MVT 561.
    Upon clicing Button: Save, I face 2 types of errors intermittently
    1. Material document is saved and generated but when comes to displayed, it will say "Document 4900496xxx does not exist in calendar year 2009" And I check in Table: MKPF and it does not exist at all
    2. I am not able to save it and face this termination error:
    The ABAP/4 Open SQL array insert results in duplicate database record
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLGLIU" had to be terminated because one
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and adminis
    termination messages, especially those beyond their normal deletion"
    I have done my investigation and the number range uder FBN1 for this MVT 561 under this Company Code and Year has been maintained.
    Can anyone advise me the OSS note to solve it? I cannot find a direct OSS note on it to solve this.
    Thanks.
    Edited by: Daimos on Oct 26, 2009 7:58 AM

    Sorry Jurgen
    I have posted so many material documents using MIGO to test it out and try to update my OMBT there so many times until I lost track what is the current number range when I wrote my question here.
    I have read that thread you posted regarding the ST22 analysis [Solution from Jurgen|Document does not exist after creation of PO; . I exported them to HTML and did a detail checking, and I find out it is FI GL there did not update the number range properly which in turns cause my GR to have problems.
    Below is my analysis and learning to share with others:
    1. Ask the ABAPER to find out which record value the system trying to insert. Copy down this number.
    2. Check the OMBT value of Current Number.
    3. Then use the MFPK Table to search the latest Number Range.
    4. Try to check if the record value trying to insert already exists in Current Number. Normally, it will exist and that is why 
        system  prompt "insert duplication".
    5. Then check if the record value trying to insert already exists in MFPK Number. Normally, it will exists it will exist and that is
        why system prompt "insert duplication". (There can be situation that the Current Number is lower than the MFPK Number,  
        but it  rarely happen).
    6. Replace the Current Number to be the Next Number of MKPF largest Number. Save and it should work.
    7. If it is not work, please create a material which is non valuated and perform GR, if GR can be done and we can display
        material doc, it means the error is caused by the FI GL number range error.
    8. There can be other issues such as activation of user exits and other.
    Jurgen, I got one more question to ask you. I have tried to replace the current number with the largest number of MKPF without + 1. It can solve my problem.
    But I wonder why SAP Notes and you suggest us to replace Current Number with largest MKPF value PLUS 1?
    Please advise.
    Thanks.
    Edited by: Daimos on Nov 2, 2009 8:41 AM

  • Close the Programs that are opened by OSS Note

    Hi,
      We had opened some of the standard programs (With access key) and made the modifications as per the OSS note some time back, the programs that were modified are still open for editing even now and the client is concerned about the sanctity of the standard programs as they are open for everyone any one can make changes to the programs, how one can make sure that the object once opened should be closed immediately afer applying modifications, does SAP has any kind of mechanism using which we can track this,
    Any help would be highly appreciated,
    Rgds,

    Hi Sailatha,
    Once you have modified an SAP Object using an access key it becomes a custom Object. It can be modified at any time by any developer in the development system. If you have used the Modification Assistant or SNOTE while making the changes the first time, you will be prompted to retain your changes or reset to original in SPAU during upgrades / support packs.
    Regards
    Suresh Datti

  • OSS Notes...

    Hi Gurus,
    I am going through the "How to Handle...Inventory Management Scenarios in BW" and came across the mention of the following OSS Notes. I will really appreciate if any of you can email them to me at [email protected]
    315880
    353042
    486784
    505700
    580799
    586163
    588015
    631345
    637927
    643687
    655798
    728360
    773823
    Regards
    NewBW

    Hi Eric,
    I don't have authorization to service.sap.com. I am self learning right now. So I will require help in this.
    Regards
    NewBW

Maybe you are looking for