Customer 0CUSTOMER

Hi,
I was wondering if you can clarify something for me. When developing customer profitability analysis we replicate 0CUSTOMER to BI. How does one info object read several customer names and numbers. Are individual customers supposed to be assigned seperate info objects, or does 0CUSTOMER does the trick. Please shed some insight on this.
Thanks

Hi Daniel,
Technically speaking 0CUSTOMER is an info object and this object contains tables. A table is a place where we enter N no. of records related to that Info object.
All the customer data will be maintained on R3 side. As a BW consultant we extract the data and load it to respective tables ( i mean Data targets).
Is it clear? A basis consultant can enlight you more.
Thanks
Kiran

Similar Messages

  • Problem with master data lookup in transformations

    Hi,
    We're experiencing a strange problem in the transformations for an Error Reporting scenario.
    We've the SAP standard customer (0CUSTOMER) in DSO 2 which derives it's value from the navigational attribute of YCUSTNR (0CUSTOMER is the navigational attribute of YCUSTNR) in DSO1. But the problem here is that even when there is no entry for YCUSTNR, the 0CUSTOMER in DSO 2 returns a value.
    Referential Integrity check is not employed for this scenario. Is it because of this reason that lack of master data is returning some value held in memory. I'm not sure whether it's an issue with the cache. Is there any work around for solving this problem other than the standard master data look up?
    Any help in this issue would be appreciated and rewarded.
    Thanks & Regards
    Hari

    Note 1031553 - Reading master data returns value that does not exist
    will solve this problem.
    Regards,
    József.

  • Runtime Errors         ASSIGN_TYPE_CONFLICT.

    Hi,
    Can any one help me on the below error.
    Runtime Errors         ASSIGN_TYPE_CONFLICT.
    I am trying to load Master data text for 0CUSTOMER and the DTP fails.I am in BI 7.0 environment.
    Thanks
    Raj

    This is for 0CUSTOMER Text master data load.
    I did a transport from DEV to QAS.It worked fine in DEV but not in QAS.
    The transformation is pretty simple
    KUNNR(customer) -
    > 0CUSTOMER
    TXTMD(Name)       -
    > 0TXTMD(Medium Description)
    The info package works fine but the DTP fails.
    Runtime Errors         ASSIGN_TYPE_CONFLICT
    Date and Time          19.11.2007 13:48:33
    The detailed error message :
    Short text
         Type conflict with ASSIGN in program "GPCFUGFSZVTSH2ZBSQO537K7P2W".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "GPCFUGFSZVTSH2ZBSQO537K7P2W" had to be terminated
          because it has
         come across a statement that unfortunately cannot be executed.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
         You attempted to assign a field to a typed field symbol,
         but the field does not have the required type.
    How to correct the error
         Adapt the type of the field symbol to the type of the field or use an
         untyped field symbol or use the "CASTING" addition.
         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:
         "ASSIGN_TYPE_CONFLICT" " "
         "GPCFUGFSZVTSH2ZBSQO537K7P2W" or "GPCFUGFSZVTSH2ZBSQO537K7P2W"
         "EXECUTE"
         If you cannot solve the problem yourself and want to send an error
         notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    Thanks
    Raj

  • Please Could some one Help me

    Hi experts i have to develop a report based on the following data  Using ODS and Cube.Iam providing all the details as under.
    DSO
    Key Part
    0CUSTOMER
    ZTID
    Territory ID
    Data Part
    0FISCYEAR
    Zpercent Key Figure
    Cube
    Customer
    0Customer
    Territory
    ZTID
    Time
    0FISCYEAR
    Key Figures
    ZREVENUE
    Sample Data in DSO
    Customer Territory 0FISCYEAR Zpercent
    C1 T1 2008 50%
    C1 T2 2008 50%
    C2 T1 2008 25%
    C2 T2 2008 25%
    C2 T3 2008 50%
    Sample Data into Cube
    C1 2008 100000 USD
    C2 2008 200000 USD
    C3 2008 100000 USD
    Sample Report 1
    C1 T1 2008 50000
    C1 T2 2008 50000
    C2 T1 2008 50000
    C2 T2 2008 50000
    C2 T3 2008 10000
    C3     2008  10000
    i have desinged cube and DSO as per the requirement with given characteristics.But iam not able to generate the report as per requirement.Iam using multiprovider with cube and DSO and then developing report.I will allocate points to all hose help me and advance thanks.
    Bye

    Hi
    Try this and let me know in case of any issues
    Create a calculated key figures with the formula (NDIM(ZREVENUE)) * (Zpercent / 100)
    Please let me know the assignment in the Multiprovider for customer and fiscal year
    Regards
    Rohit
    Edited by: Rohit Deshmukh on Jul 2, 2008 9:13 AM

  • 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

  • Start Routine to Populate Account Group Field from Master data of 0Customer

    Hello Friends. Please help me edit this ABAP code to make it work. I am putting this code in start routine in between two DSO. where I am using the
    Start Routine to Populate Account Group Field from Master data of 0Customer. I do not want to use read from master data functionality since that field 0customer is not there in dso but similar field 0debitor is there. so i want to put this code
    during the load from source DSO to Target DSO.
    Error Explicit length specifications are necessary with types C, P, X, N und
    DATA: L_S_DP_LINE TYPE DATA_PACKAGE_sTRUCTURE.
        types: begin of comp,
         CUSTOMER       type  /BI0/OICUSTOMER,
         ACCNT_GRP          type /BI0/OIACCNT_GRP,
       end of comp.
        DATA: l_S_comp type comp.
        DATA: L_th_COMP TYPE HASHED TABLE OF COMP WITH UNIQUE KEY customer INITIAL SIZE 0.
    IF  L_th_COMP[] IS INITIAL.
    SELECT CUSTOMER ACCNT_GRP FROM /BI0/PCUSTOMER APPENDING CORRESPONDING FIELDS OF TABLE L_th_COMP.
    ENDIF.
    LOOP AT SOURCE_PACKAGE INTO L_S_DP_LINE.
    READ TABLE L_TH_COMP INTO L_S_COMP WITH TABLE KEY CUSTOMER = L_s_DP_LINE-CUSTOMER
    IF SY-SUBRC = 0.
    L_S_DP_LINE-/BIC/ACCNT_GRP = L_S_COMP-/BIC/ACCNT_GRP.
    MODIFY SOURCE_PACKAGE FROM L_S_DP_LINE.
    ENDIF.
    ENDLOOP.
    soniya kapoor
    Message was edited by:
            soniya kapoor

    Hello Wond Thanks for Good Answer and good option, But Client does not like this option and does not like Nav Attribute so he does not want to turn on any Nav Attribute, In general also We hav requirement to read a third table while uploading 1 dso table to 2 dso table,
    so  Please help me edit this ABAP code to make it work. I am putting this code in start routine in between two DSO. where I am using the
    Start Routine to Populate Account Group Field from Master data of 0Customer.
    No syntax Error But during the load it is updating the source table and not the target table. how to define now target table.
    ***SOURCE DSO Table
    types: begin of typ_tgl1.
        include type /BIC/AZDAFIAR000.
        types: end of typ_tgl1.
        types: begin of comp,
         CUSTOMER       type  /BI0/OICUSTOMER,
         ACCNT_GRP          type /BI0/OIACCNT_GRP,
       end of comp.
    DATA: L_th_COMP TYPE HASHED TABLE OF COMP WITH UNIQUE KEY customer
    INITIAL SIZE 0.
      data: wa_itab type COMP.
        data: wa_zdtg type typ_tgl1.
    IF  L_th_COMP[] IS INITIAL.
    ***Master Data Table
    SELECT CUSTOMER ACCNT_GRP FROM /BI0/PCUSTOMER APPENDING CORRESPONDING
    FIELDS OF TABLE L_th_COMP.
    sort L_th_COMP by CUSTOMER.
    ENDIF.
    LOOP AT L_th_COMP into wa_itab.
    select * from /BIC/AZDAFIAR000 into wa_zdtg
                        where DEBITOR  eq wa_itab-CUSTOMER.  *** SOURCE DSO Table
    IF SY-SUBRC = 0.
    wa_zdtg-ACCNT_GRP = wa_itab-ACCNT_GRP.
    MODIFY /BIC/AZDAFIAR000 from wa_zdtg. *** modify SOURCE DSO Table
    ENDIF.
      endselect.
        endloop.
    soniya kapoor

  • AR Report Requirement - Customer Credit Management - 0FI_AR_9

    HI There,
    We have a requirement in AR report to add the below fields from Customer Credit Management Datasource 0FI_AR_9
    KNKLI - Credit Control Account- 0CRED_ACCNT     
    KLIMK - Credit Limit - 0CRED_LIMIT
    CTLPC - Risk Category     -  0RISK_CATEG     
    Except KNKLI (Credit control account), remaining two fields are master data.
    Can we use the data from 0FI_AR_9 by writing look up? Please suggest.
    Thanks
    Vandana

    Hi,vandana_ir
    i don't know what's your requirement else,if you wanna add those fields to the report
    those below solution may be can help you
    1.data loading into InfoObject etc.0customer
    2.using virutal key figure tech to read customer value from infoObject.

  • Customer Alpha Conversion

    Hi All,
    I have customer ID's being used from sales data(DataSource ), GL data (Attribute of 0PROJECT), Cost for Controlling (Routine which picks the same table of 0PROJECT).
    I have checked this table /bi0/PProject here I see the customers having values such as 00000R1010, 00000R4000 when these should be R1010, and R4000.
    0CUSTOMER is a CHAR 10 Field with ALPHA.
    Customer numbers with just numeric values are correct while customer numbers starting with charecter i.e. (R) is having the problem.
    All suggestions are appreciated.
    Kind Regards
    James

    hi,
    The Alpha conversion will only work for Numeric values, for Alpha numeric values it does not do anything.
    The data in IO 0PROJECT is being loaded from the R/3 system and the values itself are coming with appended zeros in the beginning. You can write the ABAP code in the transformation to 0PROJECT to delete the leading zeros while loading customer values in 0PROJECT.
    SHIFT CUSTOMER LEFT DELETING LEADING '0' .
    This will delete leading zeros and store values in 0PROJECT as R4000
    regards,
    Arvind.
    Edited by: Arvind Tekra on May 4, 2011 7:46 AM

  • Inactive Customer Report/ Customer who has done transaction

    Hi All.
    I need to created report for customer who has done any transaction in last 2 years, please suggest me way to achieve this
    Thanks
    Prem

    Hi ,
    which is the Idea given by our collegue it is ok,
    But there you can keep all the objects data.
    so you can try in this way
    take the info object ( ocustomer) and take the cube ( where you are getting the transactional daat of that customers)
    keep left side the 0customer object and right side info cube and create teh infoset with left outer  join
    here you can get the all the customer detials based on the masetr data , and which are c ustomers are done business for thenm transactional data will come.
    now in query where the  value <0 condtion , you can keep , it shows onle who are not done businees .
    Thansk & Regarsd,
    sathish

  • Customer Master Text data label display in BEx query

    Hi,
    In my query output i have the customer number and its text displayed. The data comes from customer master infoobject.
    But the label is displayed only for customer number.
    But I need the label for text also needs to be displayed.
    Kindly let me know is there any possibilities to display the label for the text.
    Regards,
    Indhu

    Hi Induja ,
    For 0CUSTOMER , name attribute is there so it will work fine, for others like 0MATERIAL, 0COMP_CODE etc. you can follow the steps which i have posted in above reply.
    Use the same steps for 0Material, creation of Z- infoobject with reference char. of 0Material.....
    Create one custom 'z' InfoObject lets say ZCUSTOMER with Reference Characteristic of 0CUSTOMER and add it to the data target, map it with same field for which 0CUSTOMER is mapped and load data into target (DSO, cube) or if you are reporting on multiprovider then assign it.
    Because ZCUSTOMER is created with reference of 0CUSTOMER and mapped with the same source field , ZCUSTOMER will act as copy of 0CUSTOMER.
    In query designer drag 0CUSTOMER and ZCUSTOMER. change display setting
    0CUSTOMER display as Key only
    ZCUSTOMER display as Text only.

  • 0Customer I need to add a new field KDGRP

    Hi All
    I need to add the field kdrgp in the 0customer it's possible? any can helpme...
    tk's
    ulna

    Hi Raj,
    Sorry in which part I can and need Add the field, I need have the field KDGRP inside the data master in customer.
    please do you tellme step by step
    thank's

  • Reporting on master data customer and bad performances : any workaround ?

    Hello,
    I've been asked to investiguate on bad performances encountered when performing reporting
    on the specific master data zcustomer.
    Basically this master data has a quite similar design that 0customer, there are 96000 entries in the master data table.
    A simple query has been developed : the reporting is done on the master data zcustomer and its attributes : no key figure, no calculation, no restriction ...
    Nevertheless, the query can not be executed .. the query runs around 10 minute in rsrt, then the private memory is exhausted and then a short dump is generated.
    I tried to buid a very simple query on 0customer, this time, without the attributes ... and it took more than 30 sec before I get the results.
    I checked the queries statistics :
    3.x Analyzer Server 10 sec
    OLAP: Read Texts : 20 sec
    How is it that it is so long to performthe reporitng on those master data, while in the same time If i try to display the content in SAP by choosing "maintain master data", I have an immediate answer.
    I there any workaround ?
    Any help would be really appreciated.
    thank you.
    Raoul

    Hi.
    How much data have you got in the cube?
    If you make no restrictions, you are asking the system to return data for all 96.000 customers. That is one thing that might take some time.
    Also, using the attributes of this customer object, fx making selection or displaying several of them, means that the system has to run through the 96.000 records in masterdata to know what goes where in the report.
    When you display the masterdata, you are by default displaying just the 250 or so first hits, and you are not joining against any cube or sorting the result set, so that is fast.
    You should make some kind of restriction on other things than zcustomer (time, org.unit, version, etc, to limit the dataset from the cube, but also a restriction on one of the zcustomer attribs, with an index for that maybe, and performance should improve.
    br
    Jacob

  • Loading customer hierachy from flat file

    Hello Friends,
    I have a requirement to load time dependent customer hierarchy, to be used in BEx reports. I have gone most of the threads in the forums about 0cust_sales and 0customer.
    The table that is updated in ECC is KNVH. As we cannot map the data from KNVH directly to 0customer, I have loaded the data to 0cust_sales using using datasource 0CUST_SALES_LKDH_HIER.
    Now I have downloaded the 0cust_sales hierarchy using the program Z_SAP_HIERARCHY_DOWNLOAD and changed the object there to reflect 0customer.
    Once the file is downloaded, I tried to create a file datasource for 0Customer and load the file.
    Initially I found issues with format, as 0cust_sales would have a combination of sales org, dist channel, division together with customer. I replaced all those numbers with zeros.
    The preview looks good with all the fields properly populated.
    But still not able to load the file. I have checked in SLG1, its all green. but hierarchy does not show any update.
    As a second step, I tried to create a manually 2 nodes in the 0customer hierarchy and tried to download it using the program. Then tried to upload again. Its working after manual change only for some entries
    Any inputs are highly appreciated.
    Thanks
    Ed.

    Thanks Aditya for your reply.We are on BW 7.3.
    These are the steps taken
    1. Loaded the 0cust_sales hierarchy from ECC(knvh) - good
    2. Downloaded the hierarchy as a .txt file using Z_SAP_HIERARCHY_DOWNLOAD program
    3. Created a Datasource for hierarchy for 0customer using file system
    4. Modified the downloaded file ( re arranged the columns and also the width of the columns) and saved it as .csv
    4. Created transformations and uploaded the file to 0customer. It went though fine.
    5. The requirement is to automate it. I am not able to upload the downloaded file from 0cust_sales to 0customer, even if i remove distribution channel, division and sales org
    Following is the snippet of the file
    Or there are any other options.
    0cust_sales download
    000000010HIER_NODE               
    ~ROOT                       
    0000000000000002000000009999123110000101                                                           
    Ep11    p1 p1
    000000020HIER_NODE               
    1220070                     
    0000000100000003000000109999123120131025                                                           
    E000000000001220070  000000000001220070                 
    000000000001220070
    file that I uploaded to 0customer is
    NODEID,INFOOBJECT,NODENAME,LINK,PARENTID,DATETO,DATEFROM,CHILDID,NEXTID,LANG,SHORTD,MEDD,LONGD
    1,0HIER_NODE,ROOT,,0,99991231,10000101,2,0,E,ROOT,ROOT,ROOT
    2,0CUSTOMER,1220070,,1,99991231,20131025,3,10,E,L Holding Company Inc,L Holding Company Inc,L Holding Company Inc

  • How to use customer exit variable in the report

    Dear All,
    i want to use a standard customer exit variable in the report properties.
    In the Bex Query Designer right hand bottom you will find two buttons "Properties" and "Task". Click on task you will get different option. Choose properties from there and then select "variable sequence tab".
    I need to add a standard variable there. How can i achieve it?
    Appreciate your early help.

    You need to add variable to corresponding charctertic then you can get that varaible for sorting the sequence....
    If 0CUST is the varaible then you need to assign it 0CUSTOMER then 0CUST will be available for the sequence.
    Edited by: shanthi bhaskar on Apr 2, 2009 5:41 PM

  • Load custom hierarchy (multiple ownership / parents)

    Hi all
    Lots of questions below, I just need some input on this..:) Thx. in advance..
    I have a question regarding loading a custom Customer hierarchy from SAP CRM to SAP BW. The special thing about this hierarchy is that is a leaf (child) can have multiple parents. E.g.
    - Customer C belongs to both Customer A and Customer B. (Shared ownership.)
    - Furthermore I have the information that Customer A owns 40% of C and Customer B owns 60% of C.
    Is this something that you see I can support in BW, by loading this hierarchy to 0CUSTOMER? Is this at all supported in BW to have leafs with multiple parents?
    Let's say I have an infocube and I do not want the key figures for Customer C to sum up for all parents that owns this customer, but I still want to display the relations (e.g. display Customer C under both Customer A and B, but if you look at the result this should not add up twice). Furthermore do you know how I can connect the percentage to the specific relationship and show this in the report?
    I have heard about this option called "Linked nodes", where the system creates a reference for a particular node to an original node. Thereby the possibility to display the subtree of a node multiple places in a hierarchy. But I do not know if this is supported for leafs as well?

    No one?

Maybe you are looking for