DirectorySearcher for an Organizational unit

&(objectClass=user)(memberOf=cn=MyGroup,ou=West,dc=MyDomain,dc=com) work great for a group.What syntax do I use for an Organizational unit?
Certified Geek

Hello Arne,
>>What syntax do I use for an Organizational unit?
If you mean you want to do a query against a OU, you could check this link:
https://technet.microsoft.com/en-us/library/cc755655(v=ws.10).aspx#BKMK_4
Search for “dsquery ou”, it shows how to
find organizational units in the directory that match the specified search criteria.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

  • For an Organization unit, unable to assign Business partners in devlopment box

    Dear All,
    For an Organization unit, unable to assign Business partners in development-box , when i click on assign button
    its navigating to organization unit only (choose relation ship)
    But for production system i can assign the BP with out any issue
    Can u please suggest us, do we have any settings to chose the relation ship as position...
    Please find below screen image for your reference
    Thanks ,
    Rahul Yedapally 

    Vijay,
    There should be some relationship attached to those BP. Select any BP for which you are getting error, go to trx BP --> Open that BP --> then go to "RELATIONSHIP" tab and check. If entries there, you can delete those realtionship and try again.
    Regards
    Pankaj

  • PPOME - Can't insert the SAME task for different organization unit

    Hi all,
    I have a doubt; in SAP 46C, it seems that is impossible to insert in PPOME, Detailed window, Tasks tab the same task for different organization unit. The only way to do this is in PP01 - General management, where you can explicitely create a [B-007] relations with the same "T" Object. Now, it is a little bit difficult for a user to switch from PPOME ad PP01 when defining new organizational structure.
    The question: is there any way to insert the <b>SAME</b> task directly in PPOME, overwriting the standard behaviour of the system that by default create a new task for each new insertion?
    Thanks all
    Paolo

    Hi Naveen
    thank you for your prompt reply.
    The issue that I want to solve is that some organization unit (not all) must be flagged for an external export to another system, depending on some characteristic of each org unit. I didn't find a similar attribute on standard field, so I thought to insert a common task to all the org units to export, so that this relation can serve as the missing attribute on org unit definition.
    PP01 let me insert a task (type T, and not TS) on an org unit directly, so I want to know if I'm going to break some standard behaviour of SAP if I insert a task on OU.
    Thank you
    Paolo

  • Deactivate a workflow only for an organizational unit

    Hello,
    I would like to know if it is possible to deactivate a workflow for a particular organizational unit.
    I would like to deactivate the workflow 'completion by purchaser' only for an organizational unit in order to skip the step of purchaser validation.
    Regards,
    Lina

    Hi,
    Just code it using the expression i have given mixed with the one who you want to use. Then use symbols such as "="(equal) to set your company value...
    Remember that you have to code all possibilities !
    Example : if you want to trigger the WF if company code = 0001, then you have to tell the system what to do if company code different to 0001 !
    Kind regards,
    Yann

  • How do I activate the object history for an organizational unit ?

    Dear experts,
    we're using organizational units, positions, persons and users of the
    organizational management (Transactions PPOCE and PPOME) for
    the determination of (possible) agents in our Workflows.
    The objects seem to have an object history, at least you find such an
    option in the "find by" window on the left hand side of the maintenance
    transactions, but in our system there are no entries and I can't figure
    out how to activate history entries to be written.
    Do you ?
    Thanks in advance
    Andreas

    Hi,
    In OM all relation have a validity. I think you mean this with object history.
    If you double click an organizational unit for instance and then open the detail tab (if it wasn't open already)
    there you'll see Valid On with todays date this is the date which is used for determining the organizational structure, also you'll see No Periods with a green square to the left of the text.
    Just above the text Valid On, you'll see a button, when you click on the display periods button you can change the date to see what the relation of the object was at that time.
    You can also search the HR forum for more on organizational management.
    Kind regards, Rob Dielemans

  • Number range for Object (Organizational unit, Job, Position)

    Hi all,
    How to maintain number range for Organizational unit or Job or Position by Company Code or PA, EG, ...?
    Thanks,
    Quang

    Hi,
    For organizational objects maintain number ranges via OONR.
    e.g. In order to maintain number range for C - Job object in plan version 01 add the following line to OONR:
    01C  IN  EX
    Then select this line and hit "Number range maintenance"
    There create the interval you want.
    (EX 60000000 69999999)
    For PA, EG there is no number range maintained.
    Regards,
    Dilek
    Edited by: Dilek Ersoz Adak on Jan 14, 2010 8:08 AM

  • 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

  • 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

  • Generate a BP number for Org. Unit in Org. Model

    Hi experts,
    For each organizational unit created in the organizational model a business partner is generated automatically.
    However, when I go to Org. Model and create a Org. Unit, it is NOT generating a BP number for it.
    Can anybody help me on this ?
    I configured as following steps:
    Step 1: Defining Number Range for Org Business Partners
    Step 2: Defining Groupings for Org Business Partners
    Step 3: Set up integration
       HRALX-HRAC - X
       HRALX-OBPON - ON
       HRALX-ONUMB - 2
       HRALX-OSUBG - Enter your Number Range defined in the   previous steps here.
    save your entries.
    Step 4: Execute Report for Changeover Classification
    I will reward who could help me...
    Regards,
    AHM

    Hi,
    You can follow the below steps to assign the BP to the org units if it is not assigned automatically
    Go to IMG--> CRM --> Master data ->  Business Partner ->  Integration Business Partner-Org Mangement -> Create Business Partner Intially
    Select the Organization unit check box and execute
    Doble click on  without business partners (All objects-> Org units -> without business partners )
    Select the org units and click on start repair
    I the above will solve your issue
    Reward points if it helps
    Regards,
    Madhu

  • Organizational Units with Business Partner

    Hi Experts,
    I'm creating my organizational structure on CRM system: on transaction "PPOMA_CRM" I'm creating all the organizations I need. But I 'm facing with a problem: I'm not able to assign them a business partner. I mean: in the transaction "PPOMA_CRM" under the column "Business Partner" I'm not able to insert any business partner.
    And on the other hand, if I go on transaction "BP" in order to define a new organization, when I select which is  the BP role to use for the creation of the organization, I don't see BUP004.
    Do you have any suggestions.
    Why I can't see it?
    And what I have to do to assign a business partner to an organization?
    Full point sif it helps.
    Thanks a lot.
    Best regards,
    Stefano

    Hi,
    Please find below my answers:-
    In a first moment I configured the HR-CRM integration and when I go on transaction PPOMA_CRM in order to display the Organizational Structure I can see, for each Organizational unit downloaded from HR, a business partner ID under the column "business partner". This is the same number ID which allows to identify the same Organizational Unit on transaction BP.
    Answer- In Transaction BP you can find the same Org unit business prtner created in PPOMA_CRM.
    Suppose you have created BP_Org in PPOMA_CRM which has got generated with certain BP number.But this will not reflect in transaction BP. All the Business Partners created under BP_Org will be getting reflected.
    Now I deactivated the HR-CRM integration and when I create a new Organizational Unit on PPOMA_CRM I'm not able to fill the column "Business Partner".
    Ans- If you have not maintained in HR-CRM Integration there will be no number range.
    If I insert the Organizationa Unit ID (displayed on PPOMA_CRM) in transaction BP I don't get any results.
    Ans- While searching in BP , first you donu2019t have option of searching BP with Org Unit ID but you will find number instead. But as I told you earlier this will search the Business Partner under your Root Organization in our case it is BP_Org. You cant search for BP_Org in Tx-BP
    I need to assign a business partner to my organizational unit for escalation purposes since the escalation is succesfully only for the organizational units with that business partner ID, i.e. all the organizational units downloaded from HR.
    So at the moment the escalation process doesn't work for the organizational units just created only on CRM standalone system.
    I think it is possible to make it work also for these organizations, but I don't know how!
    Ans-  You will have to maintain as below-
    Customer Relationship ManagementMaster DataBusiness PartnerIntegration Business Partner-Organization Management Set Up Integration with Organizational Management
    HRALX- OBPON =ON
    HRALX- ONUMB
    HRALX-OSUBG
    HRALX-HRAC=
    Regds...
    Arup

  • Mapping organizational units

    For an organizational unit in the CRM , for a service scenario I  need to  assign a new R/3 Plant, to make the mapping with this unit, in the field “R/3 Mait.PLNG Plant” the problem is  that I only done this for sales,  mapping S. Organization, DC and DIV,  and in the IMG I’ve not seen any thing to do this. 
    Can any one help me ?
    Kind Regards
    João Lopo

    Solved

  • Organization unit description translation

    I would like to know how to maintain different languages for the organization unit description.
    I have tried to use PP10, however, there seems no options to add another languages.
    Thank you in advance.
    Ken

    For example, I have an organization unit call "Purchasing Department". I need to maintain in more than one languages like:
    EN       "Purchasing Department"
    ES       "XXXXYYYY" (a name in Spanish)
    DE      "GGGGGG" (a name in German)
    That is for one organization unit, I need to maintain three languages.
    Thanks!

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

  • Usage of Department/Staff switch in Organizational Unit

    Hi All,
    Just would like to know the detail usage of the Department/Staff switch for the Organizational Unit. Currently neither the Department nor the Staff switch is selected for all the organizational units created. What would be the effect and impact if I set the Department switch for the organizational unit?
    Thanks a lot,
    Francis

    Hi Francis,
    A staff flag does not have to be marked as such. It does, however, influence the presentation of positions and organizational units in the graphic. Positions or organizational units marked with a staff flag are shown in the graphic next to their respective superior nodes. Without a staff flag they are shown under the superior node.
    As for the department,marking an org unit is optional and relates to integration.
    If integration with Payroll Accounting is active, certain records are written from Personnel Management to Master Data. If you flag organizational units as departments, only the marked units are written to Master Data.
    Marking units as departments makes sense when your organizational structure includes organizational units that are not actual departments (for example, a special project team).
    NOTE: In order for the department marks to be recognized, you must also make adjustments in Customizing.
    Department Switch in T77S0 (PPABT PPABT):
        o   0 = causes the organizational unit directly above a position     to
            be read
        o   1 = causes the organizational unit with a department flag
            (infotype 1003 "Department/Staff") above a position to be read
    Hope this helps.
    Regards,
    Arpita

Maybe you are looking for