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.

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 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

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

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

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

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.

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

Getting organizational unit with API in OBPM 11g

Hi all,
I'm not able to find the way to get the organizational unit of a participant using the OBPM 11g API. Can anyone tell me how can I do that?

Organizational Unit API was included in 11.1.1.5 FP4 - see : http://www.oracle.com/technetwork/middleware/soasuite/documentation/11gr1ps4featurepackdoc-462677.html and download BPM Java API Reference. Within the download you will find oracle.bpm.services.organization.IBPMOrganizationService interface that contains method getOrganizationalUnitForUser which should do the job.
For the process there is an XPath method bpm:getUserOrganizationUnit() that according to documentation:
"Returns the fully qualified organization unit name with the parent hierarchy The signature of this function is bpm:getUserOrganizationUnit(userName, realmName, parentPath). The arguments to the function: 1) userName - a user name 2) realmName - The realm name. This is optional and if not specified default realm is assumed 2) parentPath - This is optional and if sepcified, would be used for resolving conflicts if the user belongs to more than one organizational unit. For example if user belongs to OUs americas/north/us/NY/sales and americas/taskforce/globalsales then americas/north or americas/north/us or americas/north/us/NY can be used as parent path. Note that longer the path, more efficient it is to search."

Retrieve Organizational Unit ID from ECC Purchase organization ID

hello Experts!
I am facing an issue. In SRM - given the ID of the Purchase Organization downloaded from ECC, I need to retreieve the related SRM Organizational Unit ID.
I have found a FM (BBP_CTR_UI_BE_PORG_DETERMINE) that is doing exactly the other way around, but coudln't find a function module / alternative way to satisfy my requirement.
Doesn anybody have an idea?
Thanks!

Hi
You can retrieve it using table HRV5500A to get the Org. unit ID for the corresponding backend pur org. If you want description of the Org unit then you can use table HRP1000.
Regards,
Sanjeev

Organizational unit transfers ,how to deal with the person in it ?

Hi,All,I need your help!
if an organizational unit has been transfered to another upper organizational unit ,and there are already persons assigned to different positions of it,so how to deal with this problem?are those person's IT 0000,0001should be changed too?and how to maintain this kind of change?is a personnel action necessary?or there is some other more efficient way for it?

Hi
In IT0001 You have a Position which is linked to a Org unit. If you want to change the org units reporting relationship then you have to change it in OM by creating a new relationship with the upper org unit.
All the person are assigned to position so nothing needs to be done in PA.
Reward points if useful.
Regards

Function module for automating creation of organizational unit

Experts,
I am using SRM 4.0. In my system R/3 is acting as backend.
For creation of new organisational unit in SRM, which is not present in SRM but present in R/3 side i have to do the manual activity every time.
Is there any function module? Which can automate this process. If there is any function module which i can use please let me know. and how can i use that also please let me know.
By this automation every time through the program the new organization unit should created in SRM side.
Please let me know..
Thanks in advance. I will appriciate through rewards points.

Hi,
Thanks for your input. But i am planning to send one file for HR records and then from that file through program i will upload the file. IF for some user the orgaisation unit will not be found then there itself it would create the OU through Function module(If Any)... I am doing like this as the HR system is some legacy system not the R/3 system.
So Please help me to find out function module.
i will appeciate for you help.
Thanks

Business partner of organizational unit is not consistent

Hi,
Client is on SRM 4.0. When we are trying to search a user in the org structure, and when clicking on "Check" for this user, it was showing fine. But when we are searching any BP in the org strucutre, then immediately the BP name is vanishing against the BP of the user and when doing the "Check" it is showing the below two messages:
Business Partner of organizational unit XXXXXXX is not consistent
User cannot be repaired becasue the organizational unit contains errors
When checking in BBP_CHECK_USRES, the user is not showing as defective. It is green.
Similarly, the the organizational unit check is also showing as green.
System is advising to run BBP_BP_OM_INTEGRATE. When we run this for the org units, these are coming as green.
Users are able to create the shopping carts and also are able to create confirmations. But the problem is happening for some of the users where the system is not allowing to create shopping basket / confirmation.
Strange thing is that, when we are searching the user by user id in the org structure, then the check is showing no messages. But if we search the same user using the BP number, then in the check, the messages are coming. And once the messages appear, it is appearing for all the users in the org strucutre even at the root node level.
Any help is highly appreciated.
Thanks & Regards,
Aswini

Hi Aswini,
There are some possibilities to raise these kind of errors messages:
1) User with inconsistent data.
Please, check the instructions described in the following notes:
597475 - Repair users with inconsistent address data
-> use the report B_REPAIR_EBP_USER_2 to make the user consistent.
419423 - Repairing incorrect EBP users
350129 - Creating business partner for organizational unit
When you create the Org Units have you fully completed the address
data, e.g post coe, telephone/fax number etc..
If not, please enter a full address, save the data and see if this
generates the Business Partner.
Remember, that you can delete this user and create a new user.
2) Error in the positions after HR replication
Please, implement the following notes and retest the scenario:
1056873 - Incorrect SRM users after HR distribution
1016450 - Replication of persons deletes positions in SRM
After implementing these notes you should send the employee
corresponsing to the user in error with his position (using
transaction PFAL or report RHALEINI in UPDATE mode for all periods.
3) the user was deleted and a new was created and during these two
actions the user opened documents. So, in this case, the new user
becomes inconsistent
If the user is deleted from SU01 still the BP and S which is related to
that user will be retained (we can see this in PPOMA_BBP) transaction.
In this case we can create the user again using SU01 and can be attached
with the old 'S' and 'BP'.
2. If the user is completed deleted ie., all relations BP and S.
The new user has created.
In this case if the new user is corrupted we can delete this
user (since the new user doesn't create any documents so far). But the
old documents should refer to the new BP related to the new user.
========================
Also, another option would be to follow the below instructions
After applying the notes 1056873 & 1016450, send the employees
corresponding to the users in errors with their positions (using
transaction PFAL or report RHALEINI in UPDATE mode for all periods,
using evaluation path A008) ? If not, please do this and it must repair
the SRM users. Please test and give me the feedback.
Hope this helps,
Kind Regards,
Matthew

Dimensional Hierarchy - Organizational unit

Similar Messages

Maybe you are looking for