Organizational Unit Hierarchy in Universe

Hi expert,
I created a Universe from a query, in a query I have this Organizational Unit Hierarchy in the row column. In the Universe, I can see the Hierarchy name here but there is not L00 shown in the hierarchy and the level is starting from L01 to L07. After the Universe is created here, I created the report using Web Intelligence, when I add this L01 hierarchy in the report, I cannot see any data.
Does anyone here know why? I am new to this Universe and Web Intelligience.
Thanks!

Hi King,
When you generate a universe from a BEX query, you have to specify whether or not you want to generate a level 0 or not.
If you do not have the L00, you didn't op to do so. You can do this in a refresh structure or with a fresh generate (in the latter case, check your defaults).
Now L00 will be the "all" level. So that may not be your problem.
Did you select at least a key figure in your webI query?
Test what results you get for certain selections when you run the BEX query directly.
Then using the same conditions, you should get the same results in WebI.
Good luck,
Marianne

Similar Messages

  • Database table dip organizational unit hierarchy

    Hi, All!
    Is it possible to add organizational unit hierarchy to DIP based on database table while importing from DB table?
    Thanks!

    Hi!
    Yes, I know that map file should be used. But how?
    I have plain table with users with for example following fields: id, login, pwd, mail, OU and so on...
    DomainRules
    NONLDAP:ou=myusers,dc=my,dc=comp:uid=%,ou=myusers,dc=my,dc=comp
    AttributeRules
    ou: : :ou: ou: : organizationalUnit
    dc: : :domain:dc: :domain
    id: : : :employeenumber: :inetOrgperson
    login: : : :cn: :person
    But I can't create OU and users in required OU (as mentioned in DB record), all users created in "ou=myusers,dc=my,dc=comp".

  • Organizational Unit Hierarchy

    Hello Team,
    I am working for a Banking project.I would like to know the hierarchy datasource for the 0ORGUNIT (Org Structur) maintained in the Transactional banking system.
    I am using the copy of the infocube 0TB_C01 where 0ORGUNIT is also there.This infoobject is hierarchy enabled and i am planning to load the hierarchy from the transactioanl banking system.
    For eg: The Org structure in the banking system would come like Branch->District>Region-->Top Company level.
    Kindly advise on the above.
    Thanks,
    Rajesh janardanan

    Hi Ravi,
    I have seen the standard hierarchy in other systems for 0ORGUNIT.
    But in the Transactioanl Banking System i am unable to find it, even though there are 2 hierarchies.
    These two hierarchies are mapping to different infoobjects if we see the property of these datasources through the transaction RSA2.
    Thanks,
    Rajesh janardanan

  • 500 Internal Server Error because Organizational Unit Hierarchy

    Hi experts!
    I already loaded all hierarchies into the 0ORGUNIT master data.
    But, when I run any query that uses 0ORGUNIT the system abort, message:
    The initial exception that caused the request to fail, was:
    Termination message sent
    ABEND BRAIN (415): Incorrect FRANGE row in FORM/DIM/FAC for InfoObject 0ORGUNIT
      MSGV1: 0ORGUNIT
      MSGV3: DIM
      MSGV4: 0
    What can I do now?    (we have SAP NetWeaver BI 7.0)
    Thanks!
    Ada.

    Thanks Manoj!
    I'll apply the OSS Notes and I'll try again.
    Regards,
    Ada.

  • Partner number of organizational unit

    Hello CRM gurus.
    Is possible to create partner number of organizational unit retrospectively? We have crated organizational unit hierarchy manualy, but the units do not have partner number. Thank you for you help!
    Regard,
    Petr Syka

    Hello Petr,
    Normally the customers copy the organisation structure from R/3 to CRM. And finally to integrate BP's with org units, they would execute the report CRM_COM_ORGMAN_BUPA_INTEGRATE. Sometimes BP's are not created and integration does not work. But however they are able to resolve this issue by making some changes in number ranges and by doing customization as mention in Note 550055.
    I have to admit, I have not much knowledge in the below scenario described by you, nevertheless, I suggest that you refer the note 550055 and the corresponding related notes which might be helpful in meeting your business requirements.
    Best Regards, Adil

  • Dimensional Hierarchy - Organizational unit

    Hi all,
    I have the following queries related to Dimensional hierarchy.
    1. Why we associate logical columns in the dimensional hierarchy?
    2. For a particular organization unit there is no dimensional hierarchy, i mean data is at detailed level..
    How to display data? ....i mean is it required to build dimensional hierarchy.
    Please clarify.
    regards
    chandra kanth

    1. Why we associate logical columns in the dimensional hierarchy?
    Dimension hierarchies establish levels for data groupings and calculations in your report, they also provide paths for drill down.
    2. For a particular organization unit there is no dimensional hierarchy, i mean data is at detailed level..
    How to display data? ....i mean is it required to build dimensional hierarchy.
    Data will always be at granular level for any dimension in a typical data warehouse. In order to report the fact at higher level for business users we create this dimensional hierarchy in the BMM. So, if you want to create your report that shows measure at specific level of organization then create it, else no need.

  • Hierarchical + Analytical query for organizational unit parameters

    Hello gurus,
    I try for a couples of hour ago to make a query work as I would like.
    Our application need to store some parameters for our organization units. These organization units are typically organized in in an hierarchy manner: one top unit with many level of child units. The parameters are stored into another table with 1:1 relationship.
    For sake of visualisation, here is the data for the organization unit and parameter table in a more visual format:
    SQL> select * from organization_unit;
    UNIT_CODE  UNIT_NAME            PARENT_UNIT_CODE
    00000      Top level
    10         L2 unit #10          00000
    10-01      L3 unit #10-01       10
    10-02      L3 unit #10-02       10
    20         L2 unit #20          00000
    20-01      L3 unit #20-01       20
    20-02      L3 unit #20-02       20
    SQL>  select * from org_unit_parameters;
    UNIT_CODE  PARAM1               PARAM2               PARAM3               PARAM4
    00000      Default value        Default value        Default value        {null}
    10         {null}               Value from 10        Value from 10        {null}
    10-01      {null}               {null}               Value from 10-01     {null}
    10-02      {null}               {null}               {null}               Value from 10-02
    20         Value from 20        Value from 20        Value from 20        {null}
    20-01      {null}               Value from 20-01     {null}               {null}
    20-02      {null}               Value from 20-02     {null}               {null}The application will query the parameter table to get a parameter value for a given unit.
    The parameter resolution algorithm is rather simple: when querying a unit, the applicable parameter is the one defined at the requested level. If the parameter is not defined (null) at the requested level, the parameter value that must be returned is the next defined one in the parent hierarchy. In some rare cases, it can be null if a parameter is not defined anywhere from the requested level to top.
    I've made a query that seems to work when querying for one unit at a time. It use hierarchical operators (start with + connect by) with a bit of analytical functions. Here is a test & raw output example:
    SQL> WITH hierarchy
      2  AS
      3  (
      4    SELECT ou.unit_code,
      5         LEVEL            AS lvl
      6    FROM   organization_unit ou
      7    START WITH
      8      ou.unit_code = '20-01'
      9    CONNECT BY
    10      ou.unit_code = PRIOR ou.parent_unit_code
    11  )
    12  SELECT h.*,
    13       p.param1                                                        AS param1_raw,
    14       LAST_VALUE (p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param1_with_last,
    15       FIRST_VALUE(p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param1_with_first,
    16       p.param2                                                        AS param2_raw,
    17       LAST_VALUE (p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param2_with_last,
    18       FIRST_VALUE(p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param2_with_first,
    19       p.param3                                                        AS param3_raw,
    20       LAST_VALUE (p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param3_with_last,
    21       FIRST_VALUE(p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param3_with_first,
    22       p.param4                                                        AS param4_raw,
    23       LAST_VALUE (p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param4_with_last,
    24       FIRST_VALUE(p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param4_with_first
    25  FROM   hierarchy                                h
    26         LEFT JOIN org_unit_parameters         p
    27         ON h.unit_code = p.unit_code
    28  ORDER BY h.lvl DESC;
    UNIT_CODE   LVL PARAM1_RAW           PARAM1_WITH_LAST     PARAM1_WITH_FIRST    PARAM2_RAW           PARAM2_WITH_LAST     PARAM2_WITH_FIRST    PARAM3_RAW           PARAM3_WITH_LAST     PARAM3_WITH_FIRST    PARAM4_RAW           PARAM4_WITH_LAST     PARAM4_WITH_FIRST
    00000         3 Default value        Default value        Value from 20        Default value        Default value        Value from 20-01     Default value        Default value        Value from 20        {null}               {null}               {null}
    20            2 Value from 20        Value from 20        Value from 20        Value from 20        Value from 20        Value from 20-01     Value from 20        Value from 20        Value from 20        {null}               {null}               {null}
    20-01         1 {null}               Value from 20        {null}               Value from 20-01     Value from 20-01     Value from 20-01     {null}               Value from 20        {null}               {null}               {null}               {null}Seems pretty good, the upper parameters are well «propagated» down with LAST_VALUE function. But, I don't understand why the use of FIRST_VALUE and oppposite ordering doesn't give the same result. A little more playing with the last query for getting the final result for a given unit code:
    SQL> SELECT *
      2  FROM
      3  (
      4     WITH hierarchy
      5     AS
      6     (
      7        SELECT ou.unit_code,
      8               LEVEL            AS lvl
      9        FROM   organization_unit ou
    10        START WITH
    11           ou.unit_code = '20-01'
    12        CONNECT BY
    13           ou.unit_code = PRIOR ou.parent_unit_code
    14     )
    15     SELECT h.*,
    16            LAST_VALUE (p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param1,
    17            LAST_VALUE (p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param2,
    18            LAST_VALUE (p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param3,
    19            LAST_VALUE (p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param4
    20     FROM   hierarchy                                h
    21               LEFT JOIN org_unit_parameters         p
    22               ON h.unit_code = p.unit_code
    23     ORDER BY h.lvl
    24  )
    25  WHERE ROWNUM = 1;
    UNIT_CODE   LVL PARAM1               PARAM2               PARAM3               PARAM4
    20-01         1 Value from 20        Value from 20-01     Value from 20        {null}Works well!
    But, my ultimate goal is to create a view that resolve correctly all these parameters for each level of the organization with proper propagation rather then querying for each unit at a time. I played a bit, but without success. :( My current raw query is this one:
    SQL> WITH hierarchy
      2  AS
      3  (
      4     SELECT ou.unit_code,
      5            LPAD(' ',2*(LEVEL-1)) || ou.unit_code    AS tree,
      6            LEVEL                                    AS lvl
      7     FROM   organization_unit ou
      8     START WITH
      9        parent_unit_code IS NULL
    10     CONNECT BY
    11        PRIOR unit_code =  parent_unit_code
    12  )
    13  SELECT h.*,
    14         p.param1                                                        AS param1_raw,
    15         LAST_VALUE (p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param1_with_last,
    16         FIRST_VALUE(p.param1 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param1_with_first,
    17         p.param2                                                        AS param2_raw,
    18         LAST_VALUE (p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param2_with_last,
    19         FIRST_VALUE(p.param2 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param2_with_first,
    20         p.param3                                                        AS param3_raw,
    21         LAST_VALUE (p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param3_with_last,
    22         FIRST_VALUE(p.param3 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param3_with_first,
    23         p.param4                                                        AS param4_raw,
    24         LAST_VALUE (p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl DESC)   AS param4_with_last,
    25         FIRST_VALUE(p.param4 IGNORE NULLS) OVER (ORDER BY h.lvl ASC)    AS param4_with_first
    26  FROM   hierarchy                          h
    27            LEFT JOIN org_unit_parameters   p
    28            ON h.unit_code = p.unit_code
    29  ORDER BY h.unit_code;
    UNIT_CODE  TREE        LVL PARAM1_RAW                PARAM1_WITH_LAST          PARAM1_WITH_FIRST      PARAM2_RAW                   PARAM2_WITH_LAST          PARAM2_WITH_FIRST         PARAM3_RAW                PARAM3_WITH_LAST          PARAM3_WITH_FIRST         PARAM4_RAW                PARAM4_WITH_LAST       PARAM4_WITH_FIRST
    00000      00000         1 Default value             Default value             Default value          Default value                Default value             Default value             Default value             Default value             Default value             {null}                    Value from 10-02       {null}
    10           10          2 {null}                    Value from 20             Default value          Value from 10                Value from 10             Default value             Value from 10             Value from 10             Default value             {null}                    Value from 10-02       {null}
    10-01          10-01     3 {null}                    {null}                    Default value          {null}                       Value from 20-02          Default value             Value from 10-01          Value from 10-01          Default value             {null}                    Value from 10-02       Value from 10-02
    10-02          10-02     3 {null}                    {null}                    Default value          {null}                       Value from 20-02          Default value             {null}                    Value from 10-01          Default value             Value from 10-02          Value from 10-02       Value from 10-02
    20           20          2 Value from 20             Value from 20             Default value          Value from 20                Value from 10             Default value             Value from 20             Value from 10             Default value             {null}                    Value from 10-02       {null}
    20-01          20-01     3 {null}                    {null}                    Default value          Value from 20-01             Value from 20-02          Default value             {null}                    Value from 10-01          Default value             {null}                    Value from 10-02       Value from 10-02
    20-02          20-02     3 {null}                    {null}                    Default value          Value from 20-02             Value from 20-02          Default value             {null}                    Value from 10-01          Default value             {null}                    Value from 10-02       Value from 10-02As you can see, it's not as I expected. I know there's something to do with a PARTITION BY clause, but don't know how.
    Is anyone knows how to solve my problem?
    Thanks
    Bruno
    For reproductibility purposes, here is the code to create sturcture and data:
    Here is the format of my tables and some samble data:
    CREATE TABLE organization_unit (
       unit_code         VARCHAR2(5 CHAR)   NOT NULL PRIMARY KEY,
       unit_name         VARCHAR2(100 CHAR) NOT NULL,
       parent_unit_code  VARCHAR2(5 CHAR)  
    CREATE TABLE org_unit_parameters (
       unit_code         VARCHAR2(5 CHAR)   NOT NULL PRIMARY KEY,
       param1            VARCHAR2(100 CHAR),
       param2            VARCHAR2(100 CHAR),
       param3            VARCHAR2(100 CHAR),
       param4            VARCHAR2(100 CHAR)
    -- Inserting data
    INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
    VALUES ('00000', 'Top level', NULL);
    INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
    VALUES ('10', 'L2 unit #10', '00000');
    INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
    VALUES ('10-01', 'L3 unit #10-01', '10');
    INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
    VALUES ('10-02', 'L3 unit #10-02', '10');
    INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
    VALUES ('20', 'L2 unit #20', '00000');
    INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
    VALUES ('20-01', 'L3 unit #20-01', '20');
    INSERT INTO organization_unit (unit_code, unit_name, parent_unit_code)
    VALUES ('20-02', 'L3 unit #20-02', '20');
    INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param1, param2, param3)
    VALUES ('00000', 'Default value', 'Default value', 'Default value');
    INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param2, param3)
    VALUES ('10', 'Value from 10', 'Value from 10');
    INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param3)
    VALUES ('10-01', 'Value from 10-01');
    INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param4)
    VALUES ('10-02', 'Value from 10-02');
    INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param1, param2, param3)
    VALUES ('20', 'Value from 20', 'Value from 20', 'Value from 20');
    INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param2)
    VALUES ('20-01', 'Value from 20-01');
    INSERT INTO ORG_UNIT_PARAMETERS (unit_code, param2)
    VALUES ('20-02', 'Value from 20-02');
    COMMIT;

    Now, I hoppe I got your reqs:
    WITH hierarchy AS (
                       SELECT  ou.unit_code,
                               LPAD(' ',2*(LEVEL-1)) || ou.unit_code    AS tree,
                               LEVEL                                    AS lvl,
                               param1                                   AS param1_raw,
                               param2                                   AS param2_raw,
                               param3                                   AS param3_raw,
                               param4                                   AS param4_raw,
                               SYS_CONNECT_BY_PATH(p.param1,'#') || '#' AS param1_path,
                               SYS_CONNECT_BY_PATH(p.param2,'#') || '#' AS param2_path,
                               SYS_CONNECT_BY_PATH(p.param3,'#') || '#' AS param3_path,
                               SYS_CONNECT_BY_PATH(p.param4,'#') || '#' AS param4_path
                         FROM  organization_unit ou LEFT JOIN org_unit_parameters p
                                 ON ou.unit_code = p.unit_code
                         START WITH parent_unit_code IS NULL
                         CONNECT BY PRIOR ou.unit_code =  parent_unit_code
    SELECT  unit_code,
            tree,
            lvl,
            param1_raw,
            REGEXP_SUBSTR(param1_path,'[^#]+',1,GREATEST(1,REGEXP_COUNT(param1_path,'[^#]+'))) AS param1_with_last,
            REGEXP_SUBSTR(param1_path,'[^#]+')                                                 AS param1_with_first,
            param2_raw,
            REGEXP_SUBSTR(param2_path,'[^#]+',1,GREATEST(1,REGEXP_COUNT(param2_path,'[^#]+'))) AS param2_with_last,
            REGEXP_SUBSTR(param2_path,'[^#]+')                                                 AS param2_with_first,
            param3_raw,
            REGEXP_SUBSTR(param3_path,'[^#]+',1,GREATEST(1,REGEXP_COUNT(param3_path,'[^#]+'))) AS param3_with_last,
            REGEXP_SUBSTR(param3_path,'[^#]+')                                                 AS param3_with_first,
            param4_raw,
            REGEXP_SUBSTR(param4_path,'[^#]+',1,GREATEST(1,REGEXP_COUNT(param4_path,'[^#]+'))) AS param4_with_last,
            REGEXP_SUBSTR(param4_path,'[^#]+')                                                 AS param4_with_first
      FROM  hierarchy
      ORDER BY unit_code
    UNIT_ TREE              LVL PARAM1_RAW       PARAM1_WITH_LAST PARAM1_WITH_FIRS PARAM2_RAW       PARAM2_WITH_LAST PARAM2_WITH_FIRS PARAM3_RAW       PARAM3_WITH_LAST PARAM3_WITH_FIRS PARAM4_RAW       PARAM4_WITH_LAST PARAM4_WITH_FIRS
    00000 00000               1 Default value    Default value    Default value    Default value    Default value    Default value    Default value    Default value    Default value
    10      10                2                  Default value    Default value    Value from 10    Value from 10    Default value    Value from 10    Value from 10    Default value
    10-01     10-01           3                  Default value    Default value                     Value from 10    Default value    Value from 10-01 Value from 10-01 Default value
    10-02     10-02           3                  Default value    Default value                     Value from 10    Default value                     Value from 10    Default value    Value from 10-02 Value from 10-02 Value from 10-02
    20      20                2 Value from 20    Value from 20    Default value    Value from 20    Value from 20    Default value    Value from 20    Value from 20    Default value
    20-01     20-01           3                  Value from 20    Default value    Value from 20-01 Value from 20-01 Default value                     Value from 20    Default value
    20-02     20-02           3                  Value from 20    Default value    Value from 20-02 Value from 20-02 Default value                     Value from 20    Default value
    7 rows selected.
    SQL>  SY.
    Edited by: Solomon Yakobson on Nov 12, 2010 10:09 AM

  • Change Org.unit Hierarchy

    Hi,
    I want to change hierarchy of organization unit X111 immediately after X1.
    Ex:
    Existing
    Root X
            |_X1
                |_X11
                |     |_X111
                |_X12
    Required
    Root X
            |_X1
                |_X11
                |_X111
                |_X12
    Under Org.Unit X111 some employees exist. Live Payroll run at least for 1 year completed.
    Is it preferable to change org. unit report to link from X11 to X1.
    What will be implications ?
    regard,
    Chintan

    Hi Chintan,
    Go to T Code: PPOME
    According to your EX: Select X111, click on it and drag and drop it in X1. So that automatically the link flow over there. Hope there will not be any prob in payroll.
    If found useful awrad points
    Regards,
    Madhu Sudhanan

  • View of organizational unit in Service request

    Hi everyone,
    In our service request, we are trying to visualise all the organizational unit (of the organization model) of a BP.
    We achieve to see the direct service group where the BP is assigned but we are trying to see more of the link to the organizational model.
    For example : our organizational model looks like this:
    For user AJAUSSAUD1, I can see the direct link to PSE Equiment in my service request (this is determined in the partner schema determination)
    However, we would like to be able to see MC1 (here 3 level above) in the service request.
    We are using service organization as function and all the organizational unit are determined as service organization as we are using it to authorizations access.
    Does anyone know if there is a way to see the link with all the organizational unit of a user in a service request?
    Would it be with the attribute available in the ppoma-crm, but how to add the field and make them available in the service request view?
    Thank you,
    Regards,
    Anaïs

    Hello Anais,
    As far as I know, there is no standard way to view an organizational hierarchy in a service request. You will need to do some developments. There are two options -
    1. If you want the 3 org levels to be stored in data base table for future reference and reporting
    You can add 3 fields in ORGMAN sub object using AET. This will add the fields to table CRMD_ORGMAN. After org determination has happened in your service request, you can use BAdi - CRM_ORGMAN_BADI, methd - CRM_ORGMAN_MERGE to fill values of these 3 org levels. You have to recursively use functions or query table HRP1001 to get the parent of determined service org and then its parent and so on.
    Remember once these 3 fields are added at database level, they are available for all transaction types of one order. These fields can be made available to BW queues also at time of adding them.
    2. If you do not want the 3 org levels to be stored in data base table
    This would mean you only want these fields for display to end user.
    Add 3 model nodes in the web ui component. In the getter method of 1st field, add select query or call function to get parent of determined service org. Similarly for other 2 fields.
    Hope this will help. Maybe you also get some different suggestion from other guys.
    Regards,
    Niraj

  • HR Organisation UNIT hierarchy

    Hi guys,
    I have an Organisation Number , and I need a function which gives me all the organisations it belongs to in the Organisation structure, i.e the upward hierarchy ( Organisation Number ) as well as the downward hierarchy ( Organisation Number ).
    Kindly provide me with an FM or a sample code on how do i go about this.
    Thanks and regards,
    Frank

    Hi Frank,
    Please try this Function Module GET_ORG_UNITS.
    U can also find some more Function modules in SE37 Transaction code.
    Goto SE37 and give GETORGUNIT in input field and click on F4 function key, u will get the function modules related to the Organizational Unit
    Hope this helps...
    Best regards,
    raam

  • MSS ECM new column in Organization unit Tree structure

    Hi All
    Requirement is to add aditional column in in Selection Screen of ECM, when user selects dropdown value "Employee Selection by Organization Unit".
    Currently i get only Tree Structure of org unit.  Need to add Custom (or columns if provided by SAP ) in Org unit level.
    Thanks in advance.
    Regards,
    Chinmaya

    Employee search this is possible but not in Team  calendar
    In MSS 1.0 under employee information we have three pages:General
    Information, Compensation Information and Personnel Development .
    All these pages have different employee search iview.
    Basically employee search iview(properties) is responsible for display
    of Organization Hierarchy as table or tree.
    In employee search iview we have iview property "Organizational struct-
    ure with list display in navigation area" Sap.xss.tmv.navlistorgviews.
    This property enables you to define the navigation objects for an
    organizational structure view are to be displayed in a
    table as opposed to a tree hierarchy. In the standard system, navigation
    objects are displayed in a tree structure.
    You can enter the following organizational structure views:
    - Organizational structure views with a navigation area that belong to
    the organizational structure view group you defined with the property
    sap.xss.tmv.orgviewgroup. (Group of Organizational structure views)
    - Organizational structure view you define with the property sap.xss.tmv
    .orgview(Individual organizational structure view) provided it has
    navigation area.
    For e.g.,
    Let say, you would like to display maintain position requirements,
    navigation objects as table.
    Let say in backend you had defined following Organization structure
    views:
    MSS_TMV_EE_ORG1#Employees from Organizational Units
    MSS_TMV_EE_ORG2#Employees from Organizational Structure
    From Content administration ->Portal content ->#. Choose
    Employee Search iview (for compensation information).
    Now in the iview property "Organizational structure views with list
    display in navigation area"  maintain MSS_TMV_EE_ORG1,MSS_TMV_EE_ORG2
    Now for all cases you will get navigation objects as table display.

  • Organizational Model Hierarchy

    Hi Guy,
      I have created the Organizational Unit, but i am not able to assign the hierarchy for the organizational unit.
      Could any one please let me know how can assign the superior for the organzational unit?
    Thanks and Regards,
    Gopi.

    Hi Gopi,
    Create one more Org Unit under that  create one position for superior and then assign the holder as superior name.
    Please go through the following link for your understanding:
    http://help.sap.com/saphelp_crm50/helpdata/en/4b/6a43cccafe11d2b49d006094b9c9b4/content.htm
    Best Regards,
    Johnny

  • Learning Maps-Capture the Organizational Unit of the end user feedback

    Can anyone help me on this:
    Problem: The requirement is to track the enduser feedback from Learning Maps to get information of an organizational unit.
    As per documentation LearningMap feedback is anonymous.
    I would like to know whether there is any BADI or user exits available to solve the problem?
    Message was edited by:
            Ramesh Ramanathan

    Hi,
    Have you maintained your Organizational data? Did you assign any job to any user in the organizational hierarchy. You need to maintain you PPOMA_CRM first in order to assign any roles there.
    Hope this helps
    Rajeev

  • Create admin folders based on OU organizational unit active directory

    We have thousands of users to import from our active directory. In my proof of concepts, the active directory integration service 6.3 running on ALUI 6.1 MP1 imports all the users to the same folder - the folder where my remote authentication source object is.<br>
    Can the active directory integration service create folders based on the many OU's (organizational units) we have? We'd like our portal admin folder structure to mirror our active directory organizational unit structure, but we don't want to have to recreate it manually for the obvious deployment and ongoing maintenance reasons. Is that possible?

    You asked: Can the active directory integration service create folders based on the many OU's (organizational units) we have?
    As far as I understand there is not a way to dynamically generate Admin Hierarchy folders based upon this job.
    Obviously where there is a will there is a way, and if you have a crew of strong developers you could probably write something custom that would do this for you (maybe), but here are 2 other approaches to consider:
    1) use 1 AD Auth source and split the users into multiple folders based upon group association in the "Default Profiles" section under main settings. The problem with this is that if users change groups in AD they will not be resorted in your admin hierarchy.
    2) use multiple AD Auth sources, each with an appropriate query filter. I could be wrong, but the downfall to this approach is that the users that change OU's would be entirely deleted and recreated.
    Edited by geoffgarcia at 04/24/2008 8:11 AM

  • Match code organizational units with tree.

    Hi,
    I've created an input field with a orgeh type context element.
    There a instant solution for attribute a match code like the R3 transaction PP01 for organizational units?
    Thank for answers.

    Hi,
    There is one ready to use Freely Programmable Value help for Org hierarchy shown as a tree in Wiki. Refer to the below link-
    http://wiki.sdn.sap.com/wiki/display/WDABAP/OrganizationHierarchyinTREEstructureasF4+help
    To know more details on how to use a freely programmable value help refer to the below link -
    [Implement freely programmable value help in Webdynpro ABAP|http://www.divulgesap.com/blog.php?p=NjQ=]
    Cheers,
    Ravikiran

Maybe you are looking for