HR organization unit levels table

Hi,
Is there any table which havinging organization levels and its node i.e org level1,org level2....

resolved

Similar Messages

How to get the Organizational Unit One level up

Hi
Does any one know any function module to get the org unit one level up by giving the current Organizational unit as input. Please reply very urgent.

Hello Nirmal
I am usually using the following function module to read to OM:
* SAP_SORG
* OrgStructure with assigned orgunits)
 REFRESH: lt_struc.
 CALL FUNCTION 'RHPH_STRUCTURE_READ'
 EXPORTING
 plvar = '01' " active Planvar.
 otype = 'O' " OrgUnit
 objid = l_wa_cb1-objid " Toplevel-Node
 wegid = 'SAP_SORG'
 begda = iw_begda
 endda = iw_endda
 pup_info = 'X'
 with_stext = 'X'
 tdepth = 0 " alle Sub-Levels
 TABLES
 stru_tab = lt_struc
 EXCEPTIONS
 catalogue_problem = 1
 root_not_found = 2
 wegid_not_found = 3.
The parameter WEGID is the crucial on which determines the objects that are read from the OM. In your case you will need WEGID = 'A002' (reports (line) to).
To understand the evaluation path (WEGID) better have a look at transaction PPST.
Regards
Uwe

Assign a Position in CRM to an Organization Unit at a higher level.

Hi,
While configuring the Organizational Management in CRM 5.1, I have copied the sales areas created in ECC to CRM.
The resulting structure is a freely definable Org Unit at the top level called Sales Area (as is was created in ECC) and under that all the Sales Organizations are existing.
I need to create positions for the Sales Organizations and assign employees to these positions created.
As per our client requirement, I need to create the positions at the higher level (probably the Org unit level) and assign the employees to these positions created.
The reason for doing this is that the same employees work across different Sales Orgs.
Is it possible to create the positions at the highest level so that they can be inherited by the Sales Orgs defined below or do i need to create the positions and the employees separately for each Sales Org.
I would appreciate if you could answer at the earliest. I need to complete the configuration at the earliest.
warm regards,
Rohan Bhate

Hello,
Try this SAP CRM: Webclient UI - Framework for this kind of question.
Regards,
Fred

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

PM Organization Units Authorization on User Level

Hello experts,
Is there a way to add authorization for an organization unit (i.e. Planning Plant) on a user (SU01) level and not on a authorization objects (PFCG) level?
For example,
I would like to create the following Role (profile):
ZPM_AUT_EQM_EQUIPMENT_DISPLAY
This role should be able to display equipment from the Plant Maintenance module.
However our problem is, we would like to create authorization levels with organizational units for each user:
For example:
User jsmith has ZPM_AUT_EQM_EQUIPMENT_DISPLAY assigned but can only display equipment from Planning Plant SL01.
We know we can create this authorization creating several roles, like:
ZPM_AUT_EQM_EQUIPMENT_DISPLAY_SL01
ZPM_AUT_EQM_EQUIPMENT_DISPLAY_SJ01
ZPM_AUT_EQM_EQUIPMENT_DISPLAY_AG01
but our idea is not create several roles, but to assign the Planning Plant authorization on a user level and leave just one role so we would only need ZPM_AUT_EQM_EQUIPMENT_DISPLAY.
Is there a way to do this?
Thank you in advanced for your replies.
Best regards,
Fernando Montenegro

Hi ,
Could you share about your solution ? I think I have face the same problem as yours.

Organization Units Authorization on user level

Hello experts,
Is there a way to add authorization for an organization unit (i.e. Company Code) on a user (SU01) level and not on a authorization objects (PFCG) level?
For example,
I would like to create the following Role (profile):
ZFI_AP_REPORT_DISPLAY
This role should be able to display AP report from the Financial module.
However our problem is, we would like to create authorization levels with organizational units for each user:
For example:
User Anson has ZFI_AP_REPORT_DISPLAY assigned but can only display Report from Company Code 3202.
We know we can create this authorization creating several roles, like:
ZFI_AP_REPORT_DISPLAY_3201
ZFI_AP_REPORT_DISPLAY _3202
ZFI_AP_REPORT_DISPLAY_3203
but our idea is not create several roles, but to assign the Company Code authorization on a user level and leave just one role so we would only need ZFI_AP_REPORT_DISPLAY.
Is there a way to do this?
Thank you in advanced for your replies.
Christine Tseng

I agree with Jurjen. There is no point creating a "new" authorisation concept for a few transactions. If you use standard authorisation objects for the check in your custom tcodes then you will likely have very little work to do if you assign those tcodes to existing roles.
Even using a custom auth object & creating the variants will take up no more time than doing something like repeating the variable functionality in BI or messing about with PIDs in the UMR (which I definitely do not recommend). By sticking with the standard concept you ensure consistency, making it much easier to support and/or handover if you move on from the role.

Tables for organizational unit

Hello!
I created an organizational unit including position and user id's.
In which tables this information is avaliable?
regards
yifat

Hi,
If you want to see the Organizational unit assigned to an employee, check PA0001 for that PERNR(Employee ID) and pick the ORGEH (Organizational Unit) and PLANS(Position).
If you just want to see the existence of org unit and position goto HRP1000 table and pick OTYPE = 'O' for organizational Unit and OTYPE = 'S' for positions.
If you want to see the relationship between them then goto table HRP1001. OTYPE = 'O' for org unit, OTYPE = 'S' for position and Check their relationship with OTYPE = 'P' for Person.
Regards,
Amit
Reward all helpful replies.

How to get Personnel Numbers from Organizational Unit ?

Hello All,
I have a requirement in the HR module to get a list of all the personnel numbers maintained for a Organizational Unit.
Is there any Function Module to find out the Personnel Numbers assigned to a Organizational Unit for HR module ?
Thanks,
Ketan.

Hi Ketan,
    I'm not sure that there is any Function Module available for finding the Personnel Numbers. I have listed some Tables in HR Module try whether this will help you in finding Personnel Numbers for Organizational Unit.
DD01L Domains
DD02L SAP tables
DD03L Table Fields
DD03T DD: Texts for fields (language dependent)
DD04L Data elements
DD04T R/3 DD: Data element texts
DD05S Foreign key fields
DD06L Pool/cluster structures
DD20L Matchcode Ids
DD24S Fields of a matchcode ID
T000    Clients
T001    Company Codes
T001E Company code-dependent address data
T001P Personnel Areas/Subareas
T012    House banks
T012K House bank accounts
T012T House bank account names
T500L Personnel Country Grouping
T500P Personnel Areas
T500T Personnel Country Groupings
T501    Employee Group
T501T Employee Group Names
T502T Marital Status Designators
T503    Employee Groups / Subgroups
T503K Employee subgroup
T503T Employee Subgroup Names
T504A Benefits - Default Values (NA)
T504B Benefit Option Texts (North America)
T504C Benefit Type (NA)
T504D Benefit Credit Group Amount
T504E Benefit Amount
T504F Benefit Costs
T508A Work Schedule Rules
T508T Texts for Employee Subgroup Groupings for Work Schedules
T510   Pay Scale Groups
T510A Pay Scale Types
T510F Assign Pay Scale > Time Unit, Currency
T510G Pay Scale Areas
T510H Payroll Constants with Regard to Time Unit
T510I Standard Working Hours
T510J Constant Valuations
T510L Levels
T510M Valuation of pay scale groups acc. to hiring date
T510N Pay Scales for Annual Salaries (NA)
T510S Time Wage Type Selection Rule
T510U Pay Scale Groups
T510Y Special Rules for Wage Type Generation
T511    Wage Types
T512R Cumulation Wage Types in Forms
T512S Texts for Cumulation Wage Types in Forms
T512T Wage Type Texts
T512W Wage Type Valuation
T512Z   Permissibility of Wage Types per Infotype
T513    Jobs
T514S Table Name Texts
T514T Field Name Texts
T51D2 Wage Type Classes
T51D3 Reduction Rules
T51D4 Cumulation Rules
T527X Organizational Units
T528B Positions - Work Centers
T528C Wage Type Catalog
T528T Position Texts
T529A Personnel Event
T529F Fast Data Entry for Events
T529T Personnel Event Texts
T52BT Texts For HR Objects
T52C0 Payroll Schemas
T52C1 Payroll Schemas
T52C2 Texts for Personnel Calculation Schemas
T52C3 Texts for Personnel Calculation Schemas
T52C5 Personnel Calculation Rules
T52CC Schema Directory
T52CD Schema Directory
T52CE Directory of Personnel Calculation Rules
T52CT Text Elements
T52CX Cross References via Generated Schemas
T52D1 Valid Processing Classes
T52D2 Valid Values for Processing Classes
T52D3 Valid Evaluation Classes
T52D4 Permitted Values for Evaluation Classes
T52D5 Wage Type Groups
T52D6 Wage Type Group Texts
T52D7 Assign Wage Types to Wage Type Groups
T52D8 Valid Processing Classes - Texts
T52D9 Valid Values for Processing Classes - Texts
T530 Reasons for Events
T530E Reasons for Changes
T530F Reasons for Changes
T530L Wage Types for Special Payments
T530T Event Reason Texts
T531 Deadline Types
T531S Deadline Type Texts
T533 Leave Types
T533T Leave Type Texts
T539A Default Wage Types for Basic Pay
T539J Base Wage Type Valuation
T539R Events for Standard Wage Maintenance
T539S Wage Types for Standard Wage Maintenance
T548 Date Types
T548S Date Conversion
T548T Date Types
T548Y Date Types
T549A Payroll Areas
T549B Company Features
T549C Decision Trees for Features (Customers)
T549D Feature Directory
T549L Date modifiers
T549M Monthly Assignment: Payroll Period
T549N Period Modifiers
T549O Text for date modifier
T549P Valid Time Units for Payroll Accounting
T549Q Payroll Periods
T549R Period Parameters
T549S Payroll date types
T549T Payroll Areas
T549M Monthly Assignment: Payroll Period
T549N Period Modifiers
T549O Text for date modifier
T549P Valid Time Units for Payroll Accounting
T549Q Payroll Periods
T549R Period Parameters
T549S Payroll date types
T549T Payroll Areas
T554S Absence and Attendance Types
T554T Absence and Attendance Texts
T554V Defaults for Absence Types
T554Y Time Constraints in HR TIME
T555A Time Types
T555B Time Type Designations
T559A Working Weeks
T559B Name of Working Week
T572F Event Texts
T572G Allowed Values for Events
T572H Event Value Texts
T582A Infotypes
T582B Infotypes Which Are Created Automatically
T582S Infotype Texts
T582V Assignment of Infotypes to Views
T582W Assigns Infotype View to Primary Infotype
T582Z Control Table for PA Time Management
T584A Checking Procedures - Infotype Assignment
T588A Transaction Codes
T588B Infotype Menus
T588C Infotype Menus/Info Groups
T588D Infogroups for Events
T588J Screen Header Definition
T588M Infotype Screen Control
T588N Screen Modification for Account Assignment Block
T588O Screen Modification for Assignment Data
T588Q Screen types for fast entry
T588R Selection Reports for Fast Data Entry
T588S Screen Types for Fast Entry
T588T Menu and Infogroup Designations
T588V Business object type
T588W Event types for infotype operations
T588X Cust. composite definition of event types for IT operations
T588Z Dynamic Events
T591A Subtype Characteristics
T591B Time Constraints for Wage Types
T591S Subtype Texts
T596F HR Subroutines
T596G Cumulation wage types
T596H _Cumulation wage type texts
T596I Calculation rule for cumulation wage types
T596U Conversion Table
T599B Report Classes
T599C Report Classes
T599D Report Categories
T599F Report Classes - Select Options
T777A Building Addresses
T777T Infotypes
T777Z Infotype Time Constraints
T778T Infotypes
T778U Subtypes
Error Messages tables
T100 Messages
T100A Message IDs for T100
T100C Control of messages by the user
T100O Assignment of message to object
T100S Configurable system messages
T100T Table T100A text
T100V Assignment of messages to tables/views
T100W Assign Messages to Workflow
T100X Error Messages: Supplements

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

Organizational unit's attributes

Hi! How can i to see the organizational unit's attributes ?
For example in the transaction ppoma_crm , subscreen function, radiobutton service, local service organization.
I need this information in a very technical level, tables, function modules....
Regards, Miguel.

Hi,
everything you need can be found in functiongroup RHOMATTRIBUTES
FM RH_OM_ATTRIBUTES_READ for instance reads all of the attribute data.
Kind regards, Rob Dielemans

SRM 5.0 Exception E:BBP_BUPA:034 -Organizational unit in SUS

Hello,
We are in process of upgrade srm 4.0 to srm 5.0 , as configured Plan driven procuremnet with supplier enablement scenario . Connected R/3 (46 c) to SUS using PI 7.0 . But stuck in problem as no new vendor replicated in sus from R/3. XML message processing shows error at SUS system ie ..
"An error occured within an XI interface: Exception occurredE:BBP_BUPA:034 -Organizational unit 50000001 does not exist; check entries Programm:"
while successfully updated existing( working with srm 4.0 since last two years) vendors from same system ,
pls advise.
Regards,
Santosh
I am came across the organization plan change for srm 5.0. Want to be clarify that is it also applicable for SUS organization for vendors.
report BBP_XPRA_ORGEH_TO_VENDOR_GROUP
can any one light on it.
Message was edited by:
 Santosh Patil

Hi
Please read this carefully ->
See the following SAP OSS Notes as well ->
Note 957851 SRMSUS: Modification in usermanagement for CUA replication
Note 792364 SRM50/SUS/BP: Conversion of SUS business partner
Note 628547 SRM-SUS: Corrections for SUS 2.0 SP01: business partner,user
Report BBP_XPRA_ORGEH_TO_VENDOR_GROUP
[Convert Org. Units to Vendor Groups ]
Mode details
Mode Short text
0 Do not carry out structure checks
1 Business partner exists for root org.
2 Partner for root org. (only) has org. unit role
3 All level 2 nodes are org. units
4 All level 2 nodes have business partners
5 All level 2 nodes have (only) org. unit role
6 All level 3 nodes are org. units
7 All level 3 nodes have business partners
8 All partners (level 3) has (at least) org.unit + bidder role
9 All level 4 nodes are positions
Purpose of this report
This report converts the HR organizational model for external business partners (bidders, vendors, and their employees).
You have to run this report after an upgrade from BBP 2.0C, EBP 3.0, EBP 3.5, EBP 4.0 and SRM Server 5.0 for every root organizational unit of these external business partners (if you have several such root unit, you have to run the report several times).
This report does not run across clients, so you have to start it separately in every client that you have.
The conversion is required because, in the new HR organizational model, external objects can no longer be stored as object 'O' (=organizational unit); consequently, it is no longer possible to create positions for external objects.
This has the following effects for external business partners who are stored in the organizational model:
The old root object, the 'Central Organizational Unit for Vendors' will in future not be an organizational unit, but rather an organizational object of the type 'VG' (=vendor group)
The interim nodes that were created for reasons of system performance (each containing 100 vendors/bidders) will in future not be an organizational unit, but rather an organizational object of the type 'VG' (=vendor group)
The external business partners of the type Organization (bidders, vendors) are no longer represented by a separate organizational object (in other words, there is no longer an organizational object that has the identity relationship to the partner)
Since the org. object that previously represented the partners is missing, the business partners are now linked directly with the interim nodes (previously, the organizational unit for the partner, and not the partner itself, was linked)
If a business partner has a set of attributes that is different to the attribute values specified for the interim node, the partner in question is not linked directly to the interim node, but rather to another 'VG' object (which has the attributes of the partner), which in turn is linked to the interim node.
Previously, if an external business partner had an employee and this employee has a user in the system, the employee staffed the position in the organizational unit that represented the partner. However, since this organizational unit no longer exists, the position and the staffing relationship no longer exist either. This means, among other things, that there is no reporting option in HR that enables you to navigate from a user to the business partner of the user's company.
Since there is currently no way of directly assigning a user to a business partner (of the type Person), the organizational object 'CP' (=Central Person) is still used to establish this link.
Once the conversion report has run successfully, you will no longer be able to see the organizational structure of the external business partners by calling transaction PPOSA_BBP (or PPOMA_BBP).
However, a new transaction called PPOMV_BBP is available instead. You can use this transaction to display the converted (and newly generated) structure for bidders/vendors.
Prerequisites
Before you actually convert your organizational structure, you should let the report check the structure, and correct any errors that the report detects.
Features
The report has the following features:
A 'Check Only' mode is available, which you can use to check the consistency of the organizational structure of the external business partners at different levels
The report can be restarted. This means if the conversion is canceled due to errors or system problems, and you restart the report, it will recognize any new objects that have already been generated, thus ensuring that structure elements that have already been processed are not converted a second time (this is achieved by evaluating at runtime the log tables BBP_O_TO_VG_OBJ (for generated objects) and BBP_O_TO_VG_REL (for generated relationships)).
If you use table BBP_MARKETP_INFO to store the root organizational units, the report changes the old entries accordingly.
The report writes an application log (log object BBP_XPRA_O_TO_VG) in which messages are logged at two different levels; alternatively, you can request that the message be output directly ('WRITE', for background spool lists).
Although we do not recommend that you do this (because it can result in very long response times), you can run the report in parallel and thus convert several root organizational units at the same time.
Activities
Start the report for every 'Central Organizational Unit for Vendors' (root organizational units for external business partners) in every client that you use.
Annotations
We recommend that you do not use the 'Direct Message Output' option (that is, the option where an application log is not written) in conjunction with the 'Detailed Message Output' option for larger organizational structures, because every object and relationship that is generated will be output, and you will not feasibly be able to process this list.
Even if you use it in conjunction with the writing of an application log, the 'Detailed Message Output' option rarely makes sense if you have tens or hundreds of thousands of vendors/bidders.
Estimated work/expenditure necessary
The runtime for this report depends on the hardware, system load, and structure involved (for example, the number of vendors/bidders who have employees and users and, therefore, also positions, the number of vendors who have attributes different than those of the interim node, and so on).
As a rule of thumb, though, structures with vendors where 10% of users have their own individual attributes are processed at the rate of approximately 25,000 per hour.
Remember, however, that the time required depends to a large degree on the number of nodes where local attributes have been defined, and on the number of business partners who have users.
This can lead to situations where an organizational structure with 100,000 nodes but no local attributes or users can be converted more quickly that a structure with only 5,000 nodes but with local attributes and assigned users.
Hope this will help.
Regards
- Atul

Q: SRM/EBP Organizational units without business partner

Hi,
Good day!
I have a problem on generating business partner when creating an organizational unit via PPOMA_BBP.
Please see below setting of HRLAX of table T77S0.
HRALX     HRAC     X     Activate HR Integration
HRALX     MERID     X     Enter Integration Error in IDOC
HRALX     MSGRE     0     Recipient of Error Message When Creating BP
HRALX     OADBP          Business Partner of Standard Address
HRALX     OADRE          Address Necessary for Business Partner?
HRALX     OBPON     ON     Integration O-BP Activated
HRALX     OBWIG     X     Ignore Business Partner Warnings
HRALX     ONUMB     2     Business Partner Number Assignment (Org. Unit)
HRALX     OPROL     BUP004     Role of organizational unit in business partner
HRALX     OSUBG     01     Business Partner Subgroup (Organizational Unit)
HRALX     PALEO          Log: Organizational Units in ALE
HRALX     PALEP          Log: Employees in ALE
HRALX     PBPHR     CREATE     Employees Are Replicated from HR System
HRALX     PBPON     ON     Integration Employee/BP Activated
HRALX     PCATS          Integration P-BP for CATS Activated
HRALX     PLEVE     3     Log: Detail Level of Error Messages (1 - 5)
HRALX     PNUMB     1     Business Partner Number Assignment (Employee)
HRALX     PPROL     BUP003     Role of employee for business partner
HRALX     PQUAL          Import Qualifications
HRALX     PRTON          Log Active
HRALX     PSYNO          Log: Organizational Units in Dialog
HRALX     PSYNP          Log: Employees in Dialog
HRALX     USRAC     X     Create relationship to user
This happens when i changed the HRLAX ONUMB to 2.
Thanks in advance for your help.
Regards,
Glenn

Hi Glen
What is the reason you are using ONUMB = 2. Why are you not using ONUMBE = 1
Note on ONUMB and PNUMB u2013
1. For switch value 1, the internal interval is used.
2. For switch values 2 and 3, the interval is defined by switches HRALX/OSUBG and HRALX/PSUNG.
3. Additionally for switch values 2 and 3, a grouping must be created (transaction BUC2) for these intervals. So that the system can connect the grouping and number range interval, the name of the grouping must be identical to the name of the corresponding number range interval (the name of the grouping is in the first column of the table).
4. If type 3 is chosen (switch HRALX/ PNUMB=3) for the number assignment of business partners of the employee role, switch HRALX/PSUBG need to be created manually in table T77S0.
Refer to other OSS notes mentioned in the document
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50350f29-1db1-2d10-0194-d6a3bf01a5aa?quicklink=index&overridelayout=true
Regards
Virender Singh

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.

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

HR organization unit levels table

Similar Messages

Maybe you are looking for