Hierarchy Statistics

Hi,
Is there ant way to find out which are the hierachies which are being used more often and which hierachies are not being used.
For example:
0ACCOUNT has 5 different hierarchies: A1, A2, A3, A4 and A5... How many users are using A1 as hierarchy while running their reports?
We have BI content (statistics for 7.0) activated and running. Is there any BI content object that will store this statistics about hierarchy?
Thanks in advance and points will be awarded.

RSDDSTAT - Obsolete as of Release BI 7.0 -> RSDDSTAT_OLAP/DM
RSDDSTATWHM - gives the details from DataWarehouse / Back-end / Data Loading perspective.
I need from a reoprting perspective.  Which specific hierarchy has been accessed by which user?

Similar Messages

  • Aggregates in Production System and Change Run Hierarchy

    Hi All,
    Can anybody tell me, Why should we create Aggregates in Production System nd How?
    What is Change Run Hierarchy nd How to perform this?
    Reply back me to [email protected]
    Regards,
    Kiran

    Hi Kiran,
    Aggregates are nothing but a subset of your Infocube... when a query is executed, it firstl looks for the presence of the data in your aggregates and if found then it fetches the reocrds from there itself.. Else not, it'll search teh entire infocube and then fetch the records which is at a high risk of time consumption and the performance of the Query execution slows down or becomes worse significantly.. for this purpose, you build aggregates.. how do you decide whether you should go for aggregates or not is based on the following criteria...
    if the %Data Base time is > 30% and if the KPI ratio (selected to transferred records) is > 10, then you go for the aggregates... you can get these details in the ST03N transaction by choosing Expert mode and selecting BI Workload... you can find all the statistics related to the Query execution starting from the front end time to db time/...
    thats all about your aggregates...
    Attribute or Hierarchy change run is done so that any changes to your Master data Attributes will have to get effected in terms of your reporting...
    say for eg.. ur name is XYZ and loc is in India.. this is how it'll be reflected in your reporting also.. but at a later point in time, if you have changed your location from India to Europe, then for that to be reflected in your reporting, you'll have to perform an Attribute change run for that Characteristic...
    Hope it solves your issue..
    Regards
    Manick

  • Nakisa Org Chart Version 3.0 - Org Unit Position Statistics

    Hi All,
    Just a quick question,  I am currently at a client site where org unit position statistics is always coming back with 0 for occupied and vacation positions.
    There are clearly employees assigned to position in the org structure, but I am thinking it may be related to the work percentage on teh A008 relationship between the position and the person.
    Can anyone confirm this or give some insight on why we could be getting zeros.
    We are currently researching the authorizations to rule that out.
    thanks.
    JB

    Hi Jamie,
    I hope you are well. I assume you mean the OrgUnit Hierarchy > FTE View? For the OrgUnit FTE view, the data is calculated by counting all the Positions:
    Occupied Positions: where Position has active Person assigned (defined by S A 008 P relationship and PA0000-STAT2 = 3 for related Person)
    Vacant Positions: where Position has no active Person assigned (defined by S A 008 P relationship and PA0000-STAT2 = 3 for related Person)
    However, this data element (Position_View_Element_Live.xml) uses the BAPI_SAP_NakisaRfcProcessor_PositionVacancyCount_Live class instead of a NakisaRFC Chart class but it does reference the SAPOrgUnitChart_Position NakisaRFC function. It might be that this class alter the output of the NakisaRFC Chart function.
    Does that help?
    Best regards,
    Luke

  • Customer Hierarchy in Pricing

    Hello,
    Please tell me how Customer Hierarchy is used in Pricing? Concept?
    What are the config. we have to do?
    How do we track it in the pricing?
    Thank you.

    dear emre
    Customer Hierarchies
    Use
    With customer hierarchies you can now create flexible hierarchies to reflect the structure of customer organizations. For example, if your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, you can create hierarchies to reflect the structure of these groups. You use customer hierarchies in order and billing document processing for partner and pricing determination (including rebate determination) and for creating statistics.
    You can use customer hierarchies to assign price conditions and rebate agreements to one of the customer’s subordinate levels, to ensure that all subordinate levels are valid for the customer. For each node that you indicate as relevant for pricing, you can create condition records for pricing. If one or more nodes in a hierarchy path for a sales order contain pricing data, this is automatically taken into account in pricing.
    Integration
    You can also use customer hierarchies for evaluations in profitability analysis (CO-PA) and in the Sales Information System (SIS):
    To evaluate customer hierarchies with the sales information system and in the profitability analysis, you can maintain the field Hierarchy assignment on the Marketing tab page in the customer master record for a hierarchy customer. Here you can maintain 10 features for hierarchy customers (HIEZU01 to HIEZU10). You can use these to evaluate hierarchies statistically with up to 10 levels. (Field catalogue VHIE)
    Note that the hierarchy assignment is statistical. If you change the customer hierarchy, you may need to change the hierarchy level manually in the customer master record in the Hierarchy assignment field.
    Features
    A customer hierarchy is a flexible structure consisting of customers. Each customer - with the exception of the uppermost customer - refers to another customer at a higher level in the hierarchy (known as a higher-level customer). Customers that are assigned to higher-level customers are known as dependent customers.
    To be able to display organizational elements, that are not independent partners, you can assign pure hierarchy nodes (account group 0012) in the hierarchy. Specific data can be assigned to a hierarchy node (for example, address, price conditions, rebate agreements) and this then applies to all subordinate customers.
    As all nodes in a hierarchy are time-dependent, you can adapt the customer hierarchy to changes in the structure of a customer at any time.
    Customers can be reassigned in a hierarchy When reassigning a customer, all subordinate customers are moved with it
    You can add new customers to a hierarchy When you assign a new customer to an existing hierarchy, all pricing data, that applies to the higher-level hierarchy node, is automatically copied from the customer
    You can also remove customers from the hierarchy
    you can refer http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f4d9545a11d1a7020000e829fd11/frameset.htm
    rewards if it helps
    siva

  • OBIEE BI Answers: Wrong Aggregation Measures on top level of hierarchy

    Hi to all,
    I have following problem. I hope to be clear in my English because it's a bit complicated to explain.
    I have following fact table:
    Drug Id Ordered Quantity
    1 9
    2 4
    1 3
    2 2
    and following Drug Table:
    Drug Brand Id Brand Description Drug Active Ingredient Id Drug Active Ingredient Description
    1 Aulin 1 Nimesulide
    2 Asprina 2 Acetilsalicilico
    In AWM i've defined a Drug Dimension based on following hierarchy: Drug Active Ingredient (parent) - Drug Brand Description (leaf) mapped as:
    Drug Active Ingredient = Drug Active Ingredient Id of my Drug Table (LONG DESCRIPTION Attribute=Drug Active Ingredient Description)
    Drug Brand Description = Drug Brand Id of my Drug Table (LONG DESCRIPTION Attribute = Drug Brand Description)
    Indeed in my cube I've mapped leaf level Drug Brand Description = Drug Id of my fact table. In AWM Drug Dimension is mapped as Sum Aggregation Operator
    If I select on Answers Drug Active Ingredient (parent of my hierarchy) and Ordered Quantity I see following result
    Drug Active Ingredient Description Ordered Quantity
    Acetilsalicilico 24
    Nimesulide 12
    indeed of correct values
    Drug Active Ingredient Description Ordered Quantity
    Acetilsalicilico 12
    Nimesulide 6
    EXACTLY the double!!!!!!! But if I drill down Drug Active Ingredient Description Acetilsalicilico I see correctly:
    Drug Active Ingredient Description Drug Brand Description Ordered Quantity
    Acetilsalicilico
    - Aspirina 12
    Total 12
    Wrong Aggregation is only on top level of hierarchy. Aggregation on lower level of hierarchy is correct. Maybe Answers sum also Total Row????? Why?????
    I'm frustrated. I beg your help, please!!!!!!!!
    Giancarlo

    Hi,
    in NQSConfig.ini I can't find Cache Section. I post all file. Tell me what I must change. I know your patient is quite at limit!!!!!!! But I'm a new user of OBIEE.
    # NQSConfig.INI
    # Copyright (c) 1997-2006 Oracle Corporation, All rights reserved
    # INI file parser rules are:
    # If values are in literals, digits or _, they can be
    # given as such. If values contain characters other than
    # literals, digits or _, values must be given in quotes.
    # Repository Section
    # Repositories are defined as logical repository name - file name
    # pairs. ODBC drivers use logical repository name defined in this
    # section.
    # All repositories must reside in OracleBI\server\Repository
    # directory, where OracleBI is the directory in which the Oracle BI
    # Server software is installed.
    [ REPOSITORY ]
    #Star     =     samplesales.rpd, DEFAULT;
    Star = Step3.rpd, DEFAULT;
    # Query Result Cache Section
    [ CACHE ]
    ENABLE     =     YES;
    // A comma separated list of <directory maxSize> pair(s)
    // e.g. DATA_STORAGE_PATHS = "d:\OracleBIData\nQSCache" 500 MB;
    DATA_STORAGE_PATHS     =     "C:\OracleBIData\cache" 500 MB;
    MAX_ROWS_PER_CACHE_ENTRY = 100000; // 0 is unlimited size
    MAX_CACHE_ENTRY_SIZE = 1 MB;
    MAX_CACHE_ENTRIES = 1000;
    POPULATE_AGGREGATE_ROLLUP_HITS = NO;
    USE_ADVANCED_HIT_DETECTION = NO;
    MAX_SUBEXPR_SEARCH_DEPTH = 7;
    // Cluster-aware cache
    // GLOBAL_CACHE_STORAGE_PATH = "<directory name>" SIZE;
    // MAX_GLOBAL_CACHE_ENTRIES = 1000;
    // CACHE_POLL_SECONDS = 300;
    // CLUSTER_AWARE_CACHE_LOGGING = NO;
    # General Section
    # Contains general server default parameters, including localization
    # and internationalization, temporary space and memory allocation,
    # and other default parameters used to determine how data is returned
    # from the server to a client.
    [ GENERAL ]
    // Localization/Internationalization parameters.
    LOCALE     =     "Italian";
    SORT_ORDER_LOCALE     =     "Italian";
    SORT_TYPE = "binary";
    // Case sensitivity should be set to match the remote
    // target database.
    CASE_SENSITIVE_CHARACTER_COMPARISON = OFF ;
    // SQLServer65 sorts nulls first, whereas Oracle sorts
    // nulls last. This ini file property should conform to
    // that of the remote target database, if there is a
    // single remote database. Otherwise, choose the order
    // that matches the predominant database (i.e. on the
    // basis of data volume, frequency of access, sort
    // performance, network bandwidth).
    NULL_VALUES_SORT_FIRST = OFF;
    DATE_TIME_DISPLAY_FORMAT = "yyyy/mm/dd hh:mi:ss" ;
    DATE_DISPLAY_FORMAT = "yyyy/mm/dd" ;
    TIME_DISPLAY_FORMAT = "hh:mi:ss" ;
    // Temporary space, memory, and resource allocation
    // parameters.
    // You may use KB, MB for memory size.
    WORK_DIRECTORY_PATHS     =     "C:\OracleBIData\tmp";
    SORT_MEMORY_SIZE = 4 MB ;
    SORT_BUFFER_INCREMENT_SIZE = 256 KB ;
    VIRTUAL_TABLE_PAGE_SIZE = 128 KB ;
    // Analytics Server will return all month and day names as three
    // letter abbreviations (e.g., "Jan", "Feb", "Sat", "Sun").
    // To use complete names, set the following values to YES.
    USE_LONG_MONTH_NAMES = NO;
    USE_LONG_DAY_NAMES = NO;
    UPPERCASE_USERNAME_FOR_INITBLOCK = NO ; // default is no
    // Aggregate Persistence defaults
    // The prefix must be between 1 and 8 characters long
    // and should not have any special characters ('_' is allowed).
    AGGREGATE_PREFIX = "SA_" ;
    # Security Section
    # Legal value for DEFAULT_PRIVILEGES are:
    # NONE READ
    [ SECURITY ]
    DEFAULT_PRIVILEGES = READ;
    PROJECT_INACCESSIBLE_COLUMN_AS_NULL     =     NO;
    MINIMUM_PASSWORD_LENGTH     =     0;
    #IGNORE_LDAP_PWD_EXPIRY_WARNING = NO; // default is no.
    #SSL=NO;
    #SSL_CERTIFICATE_FILE="servercert.pem";
    #SSL_PRIVATE_KEY_FILE="serverkey.pem";
    #SSL_PK_PASSPHRASE_FILE="serverpwd.txt";
    #SSL_PK_PASSPHRASE_PROGRAM="sitepwd.exe";
    #SSL_VERIFY_PEER=NO;
    #SSL_CA_CERTIFICATE_DIR="CACertDIR";
    #SSL_CA_CERTIFICATE_FILE="CACertFile";
    #SSL_TRUSTED_PEER_DNS="";
    #SSL_CERT_VERIFICATION_DEPTH=9;
    #SSL_CIPHER_LIST="";
    # There are 3 types of authentication. The default is NQS
    # You can select only one of them
    #----- 1 -----
    #AUTHENTICATION_TYPE = NQS; // optional and default
    #----- 2 -----
    #AUTHENTICATION_TYPE = DATABASE;
    # [ DATABASE ]
    # DATABASE = "some_data_base";
    #----- 3 -----
    #AUTHENTICATION_TYPE = BYPASS_NQS;
    # Server Section
    [ SERVER ]
    SERVER_NAME = Oracle_BI_Server ;
    READ_ONLY_MODE = NO;     // default is "NO". That is, repositories can be edited online.
    MAX_SESSION_LIMIT = 2000 ;
    MAX_REQUEST_PER_SESSION_LIMIT = 500 ;
    SERVER_THREAD_RANGE = 40-100;
    SERVER_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
    DB_GATEWAY_THREAD_RANGE = 40-200;
    DB_GATEWAY_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
    MAX_EXPANDED_SUBQUERY_PREDICATES = 8192; // default is 8192
    MAX_QUERY_PLAN_CACHE_ENTRIES = 1024; // default is 1024
    MAX_DRILLDOWN_INFO_CACHE_ENTRIES = 1024; // default is 1024
    MAX_DRILLDOWN_QUERY_CACHE_ENTRIES = 1024; // default is 1024
    INIT_BLOCK_CACHE_ENTRIES = 20; // default is 20
    CLIENT_MGMT_THREADS_MAX = 5; // default is 5
    # The port number specified with RPC_SERVICE_OR_PORT will NOT be considered if
    # a port number is specified in SERVER_HOSTNAME_OR_IP_ADDRESSES.
    RPC_SERVICE_OR_PORT = 9703; // default is 9703
    # If port is not specified with a host name or IP in the following option, the port
    # number specified at RPC_SERVICE_OR_PORT will be considered.
    # When port number is specified, it will override the one specified with
    # RPC_SERVICE_OR_PORT.
    SERVER_HOSTNAME_OR_IP_ADDRESSES = "ALLNICS"; # Example: "hostname" or "hostname":port
    # or "IP1","IP2":port or
    # "hostname":port,"IP":port2.
    # Note: When this option is active,
    # CLUSTER_PARTICIPANT should be set to NO.
    ENABLE_DB_HINTS = YES; // default is yes
    PREVENT_DIVIDE_BY_ZERO = YES;
    CLUSTER_PARTICIPANT = NO; # If this is set to "YES", comment out
    # SERVER_HOSTNAME_OR_IP_ADDRESSES. No specific NIC support
    # for the cluster participant yet.
    // Following required if CLUSTER_PARTICIPANT = YES
    #REPOSITORY_PUBLISHING_DIRECTORY = "<dirname>";
    #REQUIRE_PUBLISHING_DIRECTORY = YES; // Don't join cluster if directory not accessible
    DISCONNECTED = NO;
    AUTOMATIC_RESTART = YES;
    # Dynamic Library Section
    # The dynamic libraries specified in this section
    # are categorized by the CLI they support.
    [ DB_DYNAMIC_LIBRARY ]
    ODBC200 = nqsdbgatewayodbc;
    ODBC350 = nqsdbgatewayodbc35;
    OCI7 = nqsdbgatewayoci7;
    OCI8 = nqsdbgatewayoci8;
    OCI8i = nqsdbgatewayoci8i;
    OCI10g = nqsdbgatewayoci10g;
    DB2CLI = nqsdbgatewaydb2cli;
    DB2CLI35 = nqsdbgatewaydb2cli35;
    NQSXML = nqsdbgatewayxml;
    XMLA = nqsdbgatewayxmla;
    ESSBASE = nqsdbgatewayessbasecapi;
    # User Log Section
    # The user log NQQuery.log is kept in the server\log directory. It logs
    # activity about queries when enabled for a user. Entries can be
    # viewed using a text editor or the nQLogViewer executable.
    [ USER_LOG ]
    USER_LOG_FILE_SIZE = 10 MB; // default size
    CODE_PAGE = "UTF8"; // ANSI, UTF8, 1252, etc.
    # Usage Tracking Section
    # Collect usage statistics on each logical query submitted to the
    # server.
    [ USAGE_TRACKING ]
    ENABLE = NO;
    //==============================================================================
    // Parameters used for writing data to a flat file (i.e. DIRECT_INSERT = NO).
    STORAGE_DIRECTORY = "<full directory path>";
    CHECKPOINT_INTERVAL_MINUTES = 5;
    FILE_ROLLOVER_INTERVAL_MINUTES = 30;
    CODE_PAGE = "ANSI"; // ANSI, UTF8, 1252, etc.
    //==============================================================================
    DIRECT_INSERT = YES;
    //==============================================================================
    // Parameters used for inserting data into a table (i.e. DIRECT_INSERT = YES).
    PHYSICAL_TABLE_NAME = "<Database>"."<Catalog>"."<Schema>"."<Table>" ; // Or "<Database>"."<Schema>"."<Table>" ;
    CONNECTION_POOL = "<Database>"."<Connection Pool>" ;
    BUFFER_SIZE = 10 MB ;
    BUFFER_TIME_LIMIT_SECONDS = 5 ;
    NUM_INSERT_THREADS = 5 ;
    MAX_INSERTS_PER_TRANSACTION = 1 ;
    //==============================================================================
    # Query Optimization Flags
    [ OPTIMIZATION_FLAGS ]
    STRONG_DATETIME_TYPE_CHECKING = ON ;
    # CubeViews Section
    [ CUBE_VIEWS ]
    DISTINCT_COUNT_SUPPORTED = NO ;
    STATISTICAL_FUNCTIONS_SUPPORTED = NO ;
    USE_SCHEMA_NAME = YES ;
    USE_SCHEMA_NAME_FROM_RPD = YES ;
    DEFAULT_SCHEMA_NAME = "ORACLE";
    CUBE_VIEWS_SCHEMA_NAME = "ORACLE";
    LOG_FAILURES = YES ;
    LOG_SUCCESS = NO ;
    LOG_FILE_NAME     =     "C:\OracleBI\server\Log\CubeViews.Log";
    # MDX Member Name Cache Section
    # Cache subsystem for mapping between unique name and caption of
    # members for all SAP/BW cubes in the repository.
    [ MDX_MEMBER_CACHE ]
    // The entry to indicate if the feature is enabled or not, by default it is NO since this only applies to SAP/BW cubes
    ENABLE = NO ;
    // The path to the location where cache will be persisted, only applied to a single location,
    // the number at the end indicates the capacity of the storage. When the feature is enabled,
    // administrator needs to replace the "<full directory path>" with a valid path,
    // e.g. DATA_STORAGE_PATH = "C:\OracleBI\server\Data\Temp\Cache" 500 MB ;
    DATA_STORAGE_PATH     =     "C:\OracleBIData\cache" 500 MB;
    // Maximum disk space allowed for each user;
    MAX_SIZE_PER_USER = 100 MB ;
    // Maximum number of members in a level will be able to be persisted to disk
    MAX_MEMBER_PER_LEVEL = 1000 ;
    // Maximum size for each individual cache entry size
    MAX_CACHE_SIZE = 100 MB ;
    # Oracle Dimension Export Section
    [ ORA_DIM_EXPORT ]
    USE_SCHEMA_NAME_FROM_RPD = YES ; # NO
    DEFAULT_SCHEMA_NAME = "ORACLE";
    ORA_DIM_SCHEMA_NAME = "ORACLE";
    LOGGING = ON ; # OFF, DEBUG
    LOG_FILE_NAME     =     "C:\OracleBI\server\Log\OraDimExp.Log";

  • Advise on median MDX query and/or dimension hierarchy setup

    Hey guys,
    I have a fairly weird situation with SSAS/Dimension Hierarchies and an MDX based median-calculation that is actually not working as I would like it to work.
    Hierarchy
     - State
     - County
     - Town
     - Neighborhood
     - Filing Date
     - Usage Category
     - TransactionID (PRIMARY KEY)
    I have a hierarchy set up which shall be used in order drill down the cube. The median, which shall be calculated based off the Sales Price measure and all the affected records, shall be available at every single level of the hierarchy. That is also why
    I decided to use a hierarchy: I am at least not aware of a do-able alternative that would allow to use any available dimension without a hierarchy and calculate the median dynamically based off on that.
    This is the MDX expression I use in order to calculate the median.
    Median
          NONEMPTY(EXISTING Descendants( [Statistics Hierachy1].[Hierarchy].CurrentMember,
                       [Statistics Hierachy1].[Hierarchy].[Transaction Id])),
            [Measures].[Sale Price]
    It works, and the numbers are correct, but it is way too slow in order to use it properly.
    The hierarchy of dimension states that there is no relationship between the attributes of the hierarchy. That is right, because every single attribute is an attribute to the primary key (TransactionId).
    So for me there are three ways to solve this:
     1) Set up relationships. That, for some reason, brings up only a very limited subset of my data. Not sure why?
     2) Get the hierarchy to work properly so it calculates the underlying median FASTER!
     3) Set up a different measure (maybe my MDX is totally wrong?) to calculate the median the right way? In the end the median needs to be calculated based off on all underlying transactions that make up to the current level of the hierarchy.
    In the end we are not talking about a ultra-large cube. Right now it only has like 3.1 Million rows in its one single partition.
    Can anybody of you help me to address either the issue I am facing with the hierarchy (one I set up the relations I only see a subset of data) and/or let me know how to set up the median measure the right way ?
    Thanks in advance! I really appreciate any help!
    Thanks,
    Lars

    Hi L,
    I would encourage you to set up the attribute hierarchies.  That will make your calculation much faster, the further down the user is in the hierarchy.  This is because the nonempty set you are getting the median from will be much smaller.
    As you point out, to have an attribute hierarhcy, you need to have keys that cascade down, which you haven't got, at least yet.  One simple way around this is to use composite keys all the way down the hierarchy.  ie. State just has State as key,
    County has State and County as key, Town has State, County and Town in key etc.  I can assure you that this will make you calc much faster down the hierarchy.
    One side effect you will have is that attributes will now be unique based on their parents.  Two towns with the same name in different states or counties will appear as separate towns.  You may or may not want this.  If you don't want it,
    simply have two Town attributes, call one TownKey (with composite key) which will be invisible as an attribute but used in the hierarchy.  The other Town attribute simply has Town as the key, so it can be used as an attribute on its own.  Town attribute
    can be an attribute of TownKey. 
    Hope that makes sense,
    Richard

  • DB statistics failed in Process Chains

    Hi BI Experts,
    We are maintaining 6 process chains in our system.
    Today every job was running successfully.
    But in every process chains, the DB STATISTICS are failed.When I check in the performance tab , it shows green.
    So i could not solve this problem.
    The log message is:
        The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
         anywhere along
        the call hierarchy.
        Since exceptions represent error situations and this error was not
        adequately responded to, the running ABAP program
         'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
        terminated.
    Please can anyone tell me the process.
    Thanks in advance.
    Regards
    Anjali

    Hi Anjali,
    Check the OSS Note 998904 - Statistics check shows red or yellow traffic lights.
    I am pasting the contents of the Note here:
    Symptom
    After an update statistics run, the check (in transaction RSRV or transaction RSA1--> Manage) continues to show yellow or red traffic lights.
    Other terms
    RSDU_ANALYZE, analyze, statistics, yellow traffic light, red traffic light, performance, RSRV, incorrect statistics, manage
    Reason and Prerequisites
    This problem is caused by a program error.
    Solution
    The check for current statistics on InfoCubes contains a static time query and as a result of this, statistics are incorrectly displayed as 'not current'. This is just a display problem.  After an update statistics run, the statistics are actually up to date.
    SAP NetWeaver 2004s BI
               Import Support Package 10 for SAP NetWeaver 2004s BI (BI Patch 10 or SAPKW70010) into your BI system. The Support Package is available once Note 914304 "SAPBINews BI 7.0 Support Package 10", which describes this Support Package in more detail, has been released for customers.
    In urgent cases, you can implement the correction instructions.
    You must first implement Notes 932065, 935140, 948389, 964580 and 969846, which provide information about transaction SNOTE. Otherwise, problems and syntax errors may occur when you deimplement some notes.
    To provide information in advance, the notes mentioned above may already be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".
    Before you implement an advance correction (if one exists and you want to implement it), see Note 875986. It contains notes regarding the SAP Note Assistant. These notes prevent problems during the implementation.
    Bye
    Dinesh

  • Short dump while loading statistics data - 'CX_RSR_X_MESSAGE'

    Hi all,
    When I am loading statistics data with Init selection,  system gives short dump error. Below is the message-
    The exception 'CX_RSR_X_MESSAGE' was raised, but it was not caught anywhere
    along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program 'SAPLRRMS' has to be
    terminated.
    If anyone know the answer please share with me.
    Regards,

    Hi Preet,
    Please find the details of short dump from ST22-
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
         and therefore caused a runtime error.
    The reason for the exception is:
    No text available for this exception
    to correct the error
    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:
    "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
    "SAPLRRMS" or "LRRMSU13"
    "RRMS_X_MESSAGE"
    Regards,

  • Customer Hierarchy and product Hierarchy

    Hi friends what is customer Hierarchy and what is product hierarchy?
    please explain step by step with examples.
    mail id: [email protected]
    Thanx.

    Hi Sirivas,
    CUSTOMER HIERARCHY:
    Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.
    &#61550; A customer hierarchy consists of nodes.
    &#61550; To create a customer hierarchy:
    1. Create master records for each node.
    2. Assign the nodes to each other.
    3. Assign the customer master records to the relevant nodes.
    &#61550; Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.
    With customer&#61550; hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customer’s at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.
    'How to check'
    All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
    All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
    1) Define hierarchy type: just put and ID and a name to the new hierarchy.
    2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.
    3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.
    4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
    5) Assigning hierarchy type for pricing: you indicate which classes of documents uses hierarchy in pricing determination.
    It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
    Customer hierarchy setup, firstly decide the hierarchy type to be used.
    The standard is type A.
    You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
    Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
    You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
    You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
    All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
    You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
    Product Hierarchy:
    The product hierarchy on the Basic Data screen is used to depict the competitive materials of competitor 1 in relation to those of competitor 2. Here, your own company and its materials are also regarded as a competitor and as competitive materials respectively. You can use this representation as a basis for market analyses.
    Normally we enter competitive materials using material type WETT. When entering your own materials as competitive materials, you can, however, display the product hierarchy on the Basic Data screen for other material types too.
    Requirement type determination is based on the "Origin of requirement type in requirement type determination"
    In this field you can select an alternative search strategy (source):
    Source 0 = Material master strategy, then item category and MRP type
    Source 1 = Item type and MRP type strategy
    Source 2 = Item type and MRP type strategy (as for source 1) with additional check of the allowed requirements type
    e.g. If you set value "0" system will first strategy group in material master based on that it will determine requirement type and no value found then it will determine requirement type based on item category and MRP type.
    Above settings can be found at SD --> Basic Functions --> Availability Check and transfer of requirement --> Transfer of Requirement --> Determination of Requirement type using Transaction
    For make to order std strategy group 20 is used to which req type KE is assigned.
    Check
    Check in Tcode OVZH, what requirement class is assigned to your requirement type
    Check in Tcode OVZG, what value is assigned to field "Consumption" in requirement class because that determines consumption posting.
    The product hierarchy is used to group materials by combining different features. It is used for analyses and pricing. A product hierarchy can consist of up to Eighteen characters. Its features can be combined in various ways.
    Example: A dishwasher can be described by product hierarchy 000010000200000002. This series of characters states that dishwashers belong to the category electrical appliances (series of characters 00001, position 1-5), and also to wet appliances (series of characters 00002, position 6-10) and, finally, to dishwashers (series of characters 00000002, position 11-18).
    One can maintain the product hierarchy via transaction "OVSV" and "V/76.
    Path = IMG-Logistics General-Material master-Setting for Key fields-Data relevant to SD-Define Product hierarchy.
    The product hierarchy is maintained in the Basic Data view of the material master record, and is used for evaluation as well as price determination in materials management.
    The standard SAP allows only 3 levels, but you can go up to 6 levels, for additional 3 levels u will have to take abapper help and add 3 more fields and corresponding data element into structure. So that in material master drop down you will see 6 levels.
    The transaction which will be useful to change product hierarchies for material master will be V/76.
    Yes, You can print the levels of the product hierarchy through a report.
    Use the view SE16 - V_T179 (Table Name) to display Product hierarchy with level numbers.
    Field Name is PRODH
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • What's use for Customer Hierarchy

    Dear Guru
    What's use for Customer Hierarchy? give me a step to config?
    regards
    Mohammed Renu.I

    Hi Mohammed Renu,
    CUSTOMER HIERARCHY:
    Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.
    &#61550; A customer hierarchy consists of nodes.
    &#61550; To create a customer hierarchy:
    1. Create master records for each node.
    2. Assign the nodes to each other.
    3. Assign the customer master records to the relevant nodes.
    &#61550; Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.
    With customer&#61550; hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customer’s at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.
    'How to check'
    All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
    All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
    1) Define hierarchy type: just put and ID and a name to the new hierarchy.
    2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.
    3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.
    4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
    5) Assigning hierarchy type for pricing: you indicate which classes of documents uses hierarchy in pricing determination.
    It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
    Customer hierarchy setup, firstly decide the hierarchy type to be used.
    The standard is type A.
    You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
    Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
    You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
    You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
    All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
    You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Where can I find a tutorial about Show Folders Hierarchy?

    I have Permiere Elements 11 which also has the Elements Organizer as part of the program. And I have Photoshop Elements 10 also. The Elements Organizer with the video editing program is what I'm interested in though. I think my folder hierarchy is not right. I'd like to straighten it out but I don't know how. Can someone direct me to a tutorial on how to work with the Folders Hierarchy.
    This might be a different question, but it might be related to my confusion about the Folder Hierarchy in the Organizer. On June 10 I was copying some photos from my hard drive to the Organizer - probably a dumb thing to do. While I was doing this, the Pictures folder (View and organizes digital pictures) no longer took me to all my photos on the hard drive. The Pictures folder is under Personal Folder, Documents, Music, Control Panel on the Windows 7 desktop to the right of the Start Menus stuff.
    When I click on Pictures now I get two folders: Adobe and Pictures. The Adobe folder has these values - Size: 0 bytes; Contains: 0 Files, 1 Folder; Created: Monday, June 10, 2013; Attributes: Read-only (only applies to files in the folder. I deleted the Abobe folder several times but it keeps coming back.
    What I would really like to do is to restore my Pictures folder to its original state so that I will have access to all my hard drive photos immediately instead of clicking around in those folders. I vaguely think that something I did to the folder hierarchy in the Optimizer has messed up other things on my computer.

    You wrote, "So if you moved the files, what you need to do is move them back..."
    I don't know how to do this. Could you tell  me how. I moved about 50 photos into the Organizer. Now I know I should not have done this. I'd like to correct the mistake.
    When I click on the Show Folder List icon this is what I see:
    My Pictures
         Pictures
              Faces
                   Clowns
         My Videos
         Computer
                   C:
                   Program Data
                   Users
                        Tommy
                              Faces
                                   Dancing
                                   Faces
                                   Lovers
                                   Racing
                                   Tommy
                         Pictures
                  D
                  E
                  F
                  G
    This makes no sense to me. But I could live with it - except perhaps something I did has made my PrE11 impossible to work with. When I put new clips via the memory card into the program, they do not go into the Timeline. All I get is an error message.
    I like the Adobe programs and don't want to give up on them, especially since my problems probably have been self-imposed.

  • Hiding a hierarchy column in graph view

    Hi All,
    In an compound layout I would like to have pivot view and bar chart view.
    There are two hierarchy columns in criteria. These column should display in pivot view.
    My requirement is to hide the hierarchy columns in Bar chart view and can we apply separate selection steps for each view.
    Kindly help me..
    Thanks,
    Haree

    Hi,
    Edit the pivot table and graph and at the below you can see the selection steps for the individual components. So that you can give separately for each of the components.
    Hope this helped/ answered.
    Regards
    MuRam

  • Error in loading a Hierarchy

    When we are loading a hierarchy in the BW system, we get the following error :
    Error in the hierarchy structure: see error log.
    We tried activation of the hierarchy data source then rerun the load. Still it fails with the same error.
    Please let us knwo if any one has inputs regarding the same.

    Please go through the following SAP Notes.
    [Note 1266877 - BW hierarchy error when loading|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1266877]
    [Note 384945 - BW: Incorrect hierarchy extraction for 0REOBJ|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=384945]
    You will also find plent of threads with the same issue. Just search with the key words from the Error Log.
    Regards,
    Gaurav

  • Error while assigning a foreign hierarchy characteristic

    Hi Guys,
    When trying to insert a characteristic node to a hierarchy, it gives me an error saying 'info object OHIER_NODE not entered for /SI/SS_O356(where the hierarchy is being maintained) as a foreign hierarchy characteristic' .Is there anything else that i need to maintain ?
    Can someone please help me get out of this  message
    award will be provide for correct answer
    Thanks

    Hi,
    Have you got the solution for your problem?  .If so, may i know how did you solved it.
    If not, please do not make thread as answered ,it misguide us that you got solution.
    With rgds,
    Anil Kumar Sharma .P

  • Statistics Currency Error while posting Sales Order (No: V1453)

    Hi Sappers,
    I am in process of making a company in SAP ERP SD - IDES, and while posting Sales Order, after I input Sold to Party, PO no, Del Plant and Incoterms and I press ENTER: The error comes up as:
    Statistics: The currency from in INR for date 25.11.2011 could not be determined.
    Kindly suggest a possible solution.
    Thanks
    Rahul Tikku

    Hi,
    Just go to "OBD2", select the Accounts group of your customer and "Double Click" on it, then "Double  cliick" on "Sales Data" > Further goto,  "Sales" and check if "Currency" field is suppressed. if so then change it to required or optional Entry. save and update you customer master in XD02. Then try your process.
    Reagrds
    DSR

Maybe you are looking for