Organizational Key VDSK1 POSTED BY Sappy Guy on 6:11 PM under Features, Organizational Management

VDSK1 is the feature to represent the Organizational Key which is important to run diverse authorization checks by organizational assignment in SAP HR. The Organizational Key enables you to define the organizational assignment more exactly. It Consists of elements from Enterprise Structure and Personnel Structure. Its content is derived from either the Organizational Assignment IT-0001 or from the manually written entries. 3 COMMENTS

Configure OM Infotypes - add/hide tabs POSTED BY Sappy Guy on 1:15 AM under config, infotypes, Organizational Management

For Example: Hiding or adding the Address infotype tab which gets displayed at the bottom of the PPOME screen. The tabs for infotypes can be configured by using the table T77OMTABUS Steps to configure: 1. Select the scenario OME0 (Organization and Staffing) from Scenario Definition (Hierarchy Framework). 2. With the selected scenario, select Tab Page in Scenario for each Object Typetab on the left side under the tab Scenario Definition (Hierarchy Framework). 3. Double click on the Tab Page in Scenario for each Object Type with the selected scenario.

4. It will display columns like scenarios, Object type, tab page, sequence, report name etc. The last column would be Do not Display column. It should be checked if that particular infotype for Object Type needs to be displayed else it should be unchecked.

Note: The columns are the combinations of Object type, tab page etc. So while performing the Do not Display column activity, these combinations should be checked thoroughly based on the requirement. 1 COMMENTS

Developing OM Infotypes - PPCI

POSTED BY Ananth TM on 1:39 AM under infotypes, Organizational Management

Although the need for creating OM ifotypes is rare, some projects do require this knowledge. In some ways OM infotypes are similar to their PA counterparts. For example:

Infotypes have a validity period - start date and end date Each Organizational object has a record of infotype 1000 (object infotype)

OM Objects and infotypes are used when defining the organizational plan. From the user's standpoint, the organizational plan is a display of the organizational structure that shows relationships between objects such as organizational units, positions and persons.

The most frequently used organizational objects are organizational units, position, job and person. The relationships between objects are represented in Infotype 1001. These infotypes form the organizational structure or hierarchy. The relation is defined in both the related objects.

PPCI (Personal Planning Infotype Copier) is used to develop OM infotypes. Suppose the client demands maximum loan limit to be defined for each and every position, then this is defined by creating a new OM infotype.

Use SE11 (ABAP Dictionary) to create a table. Create a few sample records in the table. It is a good idea to create the elementary search help ZLOAN in transaction SE11 with the selection method ZLOAN and the export parameter ZTTYP.

1 COMMENTS

SPOCK - Objects in OM POSTED BY Ananth TM on 10:14 PM under Organizational Management S.P.O.C.K - These are the most important objects in OM

S - Position P - Person

O - Organizational Unit C - Job K - Cost Center

Organizational units can any type of organizational entity. Eg. programs, regions, districts, divisions, departments, teams, etc. Seperate Organizational units are needed when: 1. Reporting for each is required seperately 2. Units can have Managers/Leaders 3. Units that have distinct tasks/activities Jobs are general classification of tasks that are preformed together. Eg. Human Resources Director, Administrative Specialist, Equipment Operator, etc.

Positions are organization specific. A number of positions can be based on the same job. As a general rule, each position represents only one employee.

Persons hold positions - more information on persons are stored in PA (Personnel Administration)

Relationships: Position belongs to org unit <-> org unit incorporates position Job describes a position <-> position is described by a job A postion reports to another position <-> A position is the line supervisor of another position A person is the holder of a position <-> Position is assigned to a person as a holder

OM Attributes - Each object can have a number of attributes. These attributes are stored in infotypes. These attributes are inherited based on the relationships. Eg. If a job has a salary range, the position related to it inherits it and thus the person that holds that position. Org Units and postions will inherit cost center of the parent org units. Positions can inherit tasks of the jobs that describe them (and can also have tasks directly assigned to them). The important attributes of the OM objects are listed below.

1. Org Unit - Org title, description, address, head of Org Unit, cost center, account assignment features 2. Position - Position title, description, Vacancy, Address, Work Schedule, Cost Distribution, Worker's Comp codes, Account assignement features, Cost Center override 3. Job - Class title, Description, Salary band/Scale, FLSA Status, EEO/AAP codes

1 COMMENTS

Organizational Management - purpose POSTED BY Ananth TM on 7:43 AM under Organizational Management OM is mainly used to perform numerous business and human resources processes. As the first step an organizational plan is created. The organizational plan is a functional structure representing the enterprise. In OM, the current organizational plan can be created and additional organizational plans are created as archives (this provides a clear picture of the organization at any point in time:past, present or future). Organizational Management is the basis for additional Human Resources components and functions as well as for SAP Business Workflow.

OM is installed before Personnel Development(PD), Recruitment, Compensation Management (CM/ECM), Workflow, Time Management, Security, ESS/MSS etc. OM structure provides the foundation for these modules and streamlines business processes. For example MSS setup can be such that the manager will be able to view only the details of those working under him/her - the details of persons working under the manager are picked up from OM. Similarly data from OM is used when WF has to route the work of approving the leave of an employee to his/her manager.

OM is based on the objects and their relationships. Jobs, tasks, positions, etc are the objects. These objects are created in OM. The relationship between various objects is also stored in OM. 6 COMMENTS

Main HR Authorization Object for Security POSTED BY Ananth TM on 6:52 AM under Authorization, Organizational Management

Some of the main HR authorisation objects are:

Object: PLOG Personnel Planning Fields: PLVAR Plan Version OTYPE Object Type INFOTYP Infotype SUBTYP Subtype ISTAT Planning Status PPFCODE Function Code Definition: The present object is used by the authorization check for PD data.

Field Details: PLVAR - Plan version This field defines which plan version(s) the user may access. OTYPE - Object type This field defines which object types the user may access. INFOTYP - Infotype This field defines, which infotypes, that is, attributes, of an object the users (generally) may access. SUBTYP - Subtype This field determines which subtypes the user may access for given infotypes.

Relationships are special subtypes for infotype 1001. Consequently, the relationships for which a user should have access authorization can also be limited in this field. ISTAT_D - Planning status This field determines in which planning status the user may access information. OKCODE - Function code This field defines for which type of information processing (Display, Change ) the user is authorized. The possible values are defined in table T77FC. This protection against unauthorized access is extended by the structural authorization check. Two types of function codes are distinguished in HR management. By marking the processing method Maintenance in table T77FC the function codes are indicated, with which objects may be maintained within the structure; Otherwise, only Display is allowed. The function code has effects in connection with the structural authorization. In table T77PR, authorization profiles can be indicated which are to have maintenance authorization for the structure. Without this authorization, you can only display structures. Consequently, the overall authorization results from the intersection between basis authorization and structural authorization.

Object: P_ABAP HR: Reporting

Fields: REPID ABAP Program Name COARS Degree of simplification for authorization check

Definition:

The authorization object HR reporting (P_ABAP) is used in many ways: HR Reporting with HR Reporting are reports with the RE.SAPDBPNP logical database PNP . Report: RPUAUD00 Logged changes in infotype data Processing person-related data using payment medium programs from Accounting. To 1. You can use the relevant authorization for these objects to control how the objects UO.P_ORGIN HR: Master data (P_ORGIN), UO.P_ORGXX HR: Master data - extended check (P_ORGXX) and CHAP.OHIX0010 structural authorization check are used in specified reports to check the authorization for INFTY HR infotypes . In this way, you can carry out a fine-tuned control on reports for infotype authorization. This can be useful for functional reasons or to improve performance at runtime of the corresponding reports. For this object, specify the report name(s) and the degree of simplification to be used for the authorization check.

Note: Note that this object differs from the object UO.S_PROGRAM ABAP: Program run checks . The latter is used for general program authorization checks. In HR reports, these checks are carried out in addition to the HR infotype authorization check. HR: Reporting , however, overrides the HR infotype authorization check for selected reports, with the result that the authorization checks are weakened or completely switched off. Examples: In your company, the authorization for infotypes is, for example, independent of the authorization for specific organizational units (one administrator may be authorized to access address, personal and education data only for personnel area 0101 - but not for address data in personnel area 0101 and personal data in personnel area 0102). If you enter 1 in the Degree of simplification field, the above facts are taken into account in the specified report and the check is carried out more quickly for a user with this authorization. If certain HR reports are not critical (telephone lists etc.) and authorization protection is not required, enter the report name and = * in the Degree of simplification field. The system then checks

whether the person starting the report is authorized to do so (object - ABAP/4: Program run checks), but performs no other checks (object - HR: Master data).

In your company, one user may have access to all HR infotype data. For this user, enter * in the Report name and Degree of simplification fields. The system then only checks whether this user is authorized to start the report in question but not whether he/she is authorized to display the requested HR infotype data.

A time adminstrator should carry out time evaluations (report HR: Time - time evaluation (RPTIME00) for employees with the organizational key 0001TIMEXXX . For certain additional information that is needed internally (the program user either cannot see this, or can only partially see it), the Basic pay infotype (0008)must be imported, for example, to timeevaluation. To carry out time evaluation, the administrator must therefore have display authorization for the Basic pay infotype (0008).

If the administrator is not to have display authorization for this infotype, the read authorization for the Basic pay infotype can be restricted for individuals with the organizational key 0001TIMEXXX for the report HR: Time - Time evaluation (RPTIME00). For this, use the following authorization

Object HR: Master data (P_ORGIN) (two authorizations) Infotype 0008 ' ' Subtype * ' ' Authorization level R ' ' Organizational key ' ' 0001TIMEXXX

Object HR: Reporting (P_ABAP) Report name RPTIME00 Degree of simplification 1

In this way, a simple check is carried out for the authorization check infotype in conjunction with the report HR: Time - Time evaluation (RPTIME00): The infotype, subtype, level are checked, and then, independently, the organizational assignment (in the example, the Organizational key field) (according to degree of simplification 1 ). In report HR: Time - Time evaluation (RPTIME00), infotype Basic pay (0008) can also be read. However, if the check is not in conjunction with the report HR: Time Time evaluation (RPTIME00), all fields of the object HR:

Master data (P_ORGIN) are checked together, but in this way there is no read access to the Basic pay infotype (0008). TO 2. Evaluations of the logged changes in infotype data are subject to infotype authorization checks. However, usually, someone, who starts such an evaluation, has extensive authorizations. In this case, it is useful, in order to ensure improved performance, to do without the check of individual data and instead, grant the user global authorization for logging evaluations using the report Logged changes in the infotype data (RPUAUD00). For this, use an authorization for the object, by specifying the value RPUAUD00 in the Report name field, and the value 2 in the Degree of Simplification field. To 3 The payment medium program of accounting processes, in particular, confidential personal data.

In addition the check to see whether the user is authorized to start the program, a check to see whether the corresponding authorization exists for the object is also carried out, as an additionl security measure : The name of the payment medium program must be entered in the Program name field, the value 2 (or * must be entered in the Degree of simplification field.

Field Details: Report name COARS Degree of simplification

Object: P_APPL HR: Applicants Fields: INFTY Infotype SUBTY Subtype AUTHC Authorization level PERSA Personnel Area APGRP Applicant group APTYP Applicant range VDSK1 Organizational Key RESRF Personnel officer responsible for application

Definition:

This object is used for the applicant data authorization check. This check is carried out when INFTY applicant infotypes are edited or read. When a transaction for editing applicant data is accessed, the system first checks whether the user has the minimum authorization. Depending on the transaction this may be write authorization or read authorization ( AUTHC_D authorization level = '*' or R). If the

user has the minimum authorization, a further and more detailed authorization check is carried out within the transaction itself.

Field Details: INFTY Infotype SUBTY Subtype AUTHC_D Authorization level PERSA Personnel area APGRP Applicant group APTYP Applicant range VDSK1 Organizational key RESRF Personnel officer responsible for applicant

Object: P_ORGIN HR: Master Data Fields: INFTY Infotype SUBTY Subtype AUTHC Authorization level PERSA Personnel Area PERSG Employee Group PERSK Employee Subgroup VDSK1 Organizational Key

Definition: The object HR: Master data (P_ORGIN) is used for authorization checks of personal data. Checks are performed only when INFTY HR infotypes are edited or read. When you call up a transaction for editing of personal data, the system checks that you at least have one read authorization ( AUTHC_D authorization level R). If you do, a more specific authorization check is carried out within the transaction. In HR reports that use the Program run checks and UO.P_ABAP HR: Reporting must also be taken into account. Note that values specified for the individual fields do not generally contain other values. The value ' ' must therefore be specified explicitly. The value ' ' must always be used for the subtype field (reason: the field is initial if the infotype does not support any subtypes, or if the subtype has not been specified).

Field Details:

INFTY Infotype SUBTY Subtype AUTHC_D Authorization level PERSA Personnel area PERSG Employee group PERSK Employee subgroup VDSK1 Organizational key

Object: P_ORGXX HR: Master Data - Extended Check Fields: INFTY Infotype SUBTY Subtype AUTHC Authorization level SACHA Payroll Administrator SACHP Administrator for HR Master Data SACHZ Administrator for Time Recording SBMOD Administrator Group

Definition: The object HR: Master data - Extended check (P_ORGXX) can be used to check authorization for personal data INFTY (HR infotypes) This check is not active in the standard system. The program switch HR: Master data - Extended check (ORGXX) can be used to add this check in the standard system or set it as an alternative to UO.P_ORGIN HR: master data . The main switch settings can be processed using transaction HR: Authorization switch (OOAC)

Field Details: Administrator for the person being processed (stored in the organizational assignment infotype) SACHA Payroll administrator SACHZ Time data administrator SACHP HR master data administrator SBMOD Administrator group

View of data: INFTY Infotype SUBTY Subtype AUTHC_D Authorization level (write, read, write with lock indicator, unlock).

Object: P_PCLX HR: Clusters Fields: RELID Area identifier for cluster in tables PCLx AUTHC Authorization level

Definition: This object is used in the authorization check when accessing PCLx (x = 1, 2, 3,4) HR files using the PCLx buffer (interface supported by HR).

Field Details: Cluster ID: enter the cluster name in this field. Authorization level: in this field you must specify the operation to be carried out on the cluster along with the cluster ID specified above. The values which can be entered here are R (read), U (update database) and S (export data to PCLx buffer without database update). 2 COMMENTS

Report RHINTECHECK POSTED BY Ananth TM on 10:12 PM under Organizational Management, reports

Many are familiar with Integration Reports between PA - OM/PD such as below

RHINTE00 - Transfer PA Records To PD Positions. In another world, it creates the HRP1001 between P to S in the OM side of the world. When you view a record via IT0001, you see this person holds the position, however via HRP1001, that relationship isnt so. RHINTE10 - Generates the required relevant tables. (T513 - Jobs, T513S - Jobs, T528B Positions, T528T - Work Center, T527X - Org Unit RHINTE20 - checks for all objects for integration between PA and OM. This is a big one and will take awhile to run. What it does is look at table T513/T513T - Jobs, T528/T528T Position, and T528X - Org Unit. It will then compare it against the HRPxxxx table to find missing objects. If there are any missing objects, it will create the record. RHINTE30 - Transfer OM to PA. This will create infotype 0001. If the conversion strategy is to have SAP auto inherit factor to kick in for IT0001, often time jobs and org unit are missing via IT0001 during the inital conversion load. RHINTE30 will find the relationship and push it through IT0001.

For more information on these reports for OM-PA integration, Click here

But not everyone are familiar with Report RHINTECHECK, Which is a very useful report,highly neglected.Most consider that Running Integration Reports mentioned above completes the Integration Process,but not until one runs report RHINTECHECK,which if comes out error free does actually one complete Integration Process successfully.RHINTECHECK reports checks for any inconsistancies that occur during the PA-OM integration, so it is advised to run this report after you are done running your other Integration reports.

Most likely the errors that are brought about are often solved by running either RHINTE00 or RHINTE30 report. Also the other useful report is RHCHECKV - Which Checks all inverse relationships.

For a full list of reports in SAP HR, Click here

0 COMMENTS

How To Transport Organizational Structure POSTED BY Ananth TM on 9:43 PM under Organizational Management, transport

After spending hours creating an Organizational Structure, it is rather silly to recreate that for each environment you have for testing purposes. One simple solution to that vs doing an entire system company is to use a standard delivered tool from SAP. This tool could be used in several different way, we'll get that into that in a bit. SAP deliver a really neat tool called "Manual Transport Link". You can access it via transaction SE38 and progam name RHMOVE30.

What this program does is allowing you to capture PD/OM objects and place it in a transport you can easily release and apply to other clients / systems. To start, let say for example you want to transport organizational structure and all positions below it. WIth that, you will start with creating 1 transport containing all O objects. Specify the O objects, all for reporting period, and add it to the transport. To specifically capture the position, specify the evaluation path in the selection paramters for it to find the position and add that to the transport. Do some trial and error testing of this in a sandbox environment with different selection variations

to see how it operate. You might find the best combination that fit your needs. I was at a SAP implementation with the production orgranizational structure was maintained in a DEV environment during the lifecycle of the project. Using this allows you to transports exactly how production structure will look like to all your environment. Thus easily replicating conversion cycles multiple times and cutting the time out from converting OM objects. 4 COMMENTS

OM - Transaction codes POSTED BY Ananth TM on 1:46 PM under Organizational Management, Transaction codes

PPOM - Change org Unit PO03 - Maintain Jobs P013 - Maintain Position PO10 - Maintain Organizational Unit PP01 - Maintain Plan Data (menu-guided) PP02 - Maintain Plan Data (Open) PP03 - Maintain Plan Data (Event-guided) PP05 - Number Ranges PP06 - Number Ranges Maintenance HR Data PP07 - Tasks/Descriptions PP69 - Choose Text for Organizational Unit PP90 - Setup Organization PP01 - Change Cost Center Assignment PP02 - Display Cost Center Assignment PP03 - Change Reporting Structure PP04 - Display Reporting Structure PP05 - Change Object indicators (O/S) PP06 - Change Object indicators OS PPOA - Display Menu Interface (with dyn.) PPOC - Create Organizational Unit PPOM - Maintain Organizational Plan PPOS - Display Organizational Plan PQ01 - Events for Work Center PQ02 - Events for Training Program PQ03 - Events for Job PQ04 - Events for Business Event Type PQ06 - Local Events PQ07 - Resource Events PQ08 - Events for External Person PQ09 - Events for Business Event Group PQ10 - Events for Organizational Unit

PQ11 - Events for Qualification PQ12 - Resource Type Events PQ13 - Events for Position PQ14 - Events for Task PQ15 - Events for Company PSO5 - PD : Administration Tool PSOA - Work Center Reporting PSOC - Job Reporting PSOG - Org Mgmt General Reporting PSO1 - Tools Integration PA-PD PSOO - Organizational Unit Reporting PSOS - Position Reporting PSOT - Task Reporting 2 COMMENTS

OM Infotypes POSTED BY Ananth TM on 5:29 AM under infotypes, Organizational Management

Looking for other details about infotypes? Click here Want to know the basics of an infotype? Click here Want to enhance infotypes, Click here || Excel of all infotypes

In some respects, OM infotypes are similar to PA infotypes: 1. Each infotypes has validity period (begin date and end date) 2. Infotypes are described by time constraints (the difference is that OM infotypes vary for different objects Infotype 1000 is the basis for OM information. Each organizational object has a record of infotype 1000.

Examples where custom infotypes were created:

Positions are linked to holiday premuim pay, night shift allowance Jobs need specific experience needs, competencies

T777I contains the OM infotypes. We need to add an entry in this table for new infotypes.

The master data stored in OM infotypes will be stored in HRI* tables. for example, relationship (infotype 1001) will be stored in HRI1001 table.

For a real-time scenario which needs new OM infotypes click here

For more details on how to prepare OM infotypes click here 0 COMMENTS

Organizational Structure POSTED BY Ananth TM on 12:20 PM under basics, Organizational Management GENERAL INFORMATION In the SAP System, the companys structure is defined by the Enterprise Structure and the Personnel Structure. When used together, these structures defined the legal entities of the company, work locations for the company, and the Companys various employee groups. Because the enterprise and personnel structures help the company differentiates between the various type of employee and work locations, the structures values are used extensively in payroll, time and benefit processing rules. The enterprise and personnel structures are also used extensively by the financial components of SAP. For instance, the structure values are used in rules to appropriately posts payroll expenses to the correct GL accounts. Additionally, the tracking of recurring base budgets by staff group relies heavily on Enterprise and Personnel structure values. Enterprise and Personnel structures are stored on positions. When positions are created by the HR compensation Analyst, the appropriate structure values will be selected and stored for the position. As employees are assigned to positions, the employee will inherit the structure values stored on the position. If the values are not appropriate for the assignment, the values may be changed on the employee assignment screen (Infotype 0001, Organizational Assignment). Especially with concurrent employment, the enterprise and personnel structure values will require carefull over sight. OVERVIEW OF the ENTERPRISE STRUCTURE The enterprise structure for Personnel Administration is made up of the following elements. Client : an independent legal and organizational unit of the system Company Code : An independent company with its own accounting unit;a company that draws its

own balance sheet Personnel Area : A specific entity for Personnel Administration; a sub division of the company code Personnel SubArea : A sub division of the personnel Area Following is a more detailed of each enterprise structure value. Company Code The company code is the highest level of the enterprise structure within the client. It represents an independent company. The company code is established in the Finance module of SAP. The IMG Path: IMG-> Enterprise Structure -> Definition -> Financial Accounting -> Define Company IMG-> Enterprise Structure -> Definition -> Financial Accounting -> Edit, Copy, Delete and Check Company Code And Related above definition altogether: IMG-> Enterprise Structure -> Assignment -> Assign Company Code to Company Note: Country groupings are assigned to the company code. The country groupings control master data entry and the setting up and processing of wage types and pay scale groups in Payroll on a countryspecific basis. The country grouping must be unique within a company code. Personnel Area The personnel Area represent a subdivision of the company code. The personnel Area can be used to perform system evaluations of data or to perform authorization checks. It is also can be used in report selection parameter in delimiting the report output. The IMG Path: IMG-> Enterprise Structure -> Human Resources -> Definition -> Pesonnel Areas Then to link personnel Area to related Company Code IMG-> Enterprise Structure -> Human Resources -> Assignment Personnel Area to Company Code By relate the personnel Area and Company Code, in case FI module has Go-Live, the the configuration will be directly linked to the Controlling Area that is used by Finance Side. Thus the payroll live posting into FI has been set In case, the FI module has not GO-Live yet, then this Company, Company Code also have to be set anyway.. Personnel SubAreas The personnel subarea represents a subdivision of the personnel area. For instance, within each personnel area, the company has a variety of employees. Some are eligible for pay while others are not. Some are eligible for benefits while others are not.

For Instance, company A has 2 separate location of plant. One is for their head office and the other is for manufacturing plant. But both of their financing transaction m would be reconciled into the same Accounting balance sheet, that is to company A. Each of plant will issue their Tax reporting to separate Tax office addresses. 0 COMMENTS

Organizational Plan POSTED BY Ananth TM on 4:56 AM under Organizational Management To Copy org plan Use report RHCOPL00 /RE_RHCOPL00 But an entry should be there in OOPV transaction with the target Plan Version before copying an existing one Leaving evaluation path empty copies the complete org structure. Evaluation path is used to focus on certain relations which are changing To compare Use report RE_RHCOPLPT OOAP - to set Active plan version 3 COMMENTS

OM - Easy access paths POSTED BY Ananth TM on 4:47 AM under Organizational Management SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOCE SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOME SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change > Go to > Reporting structure SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment > maintain cost center SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Position SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOCE

SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOME SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change > Go to > Reporting structure SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment > maintain cost center SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Position SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Cost Distribution 0 COMMENTS

OM - PA Integration POSTED BY Ananth TM on 4:41 AM under Organizational Management, PA To make integration between PA and OM (also read as integration between PA and PD) IMG--> PA--> OM--> Basic settings --> integration-->set up integration with PA set the integration switch PLOGI ORGA to X Table T77S0 is the major table for OM - PA integration

Reports in relation to PA - OM

Report RHINTE00 is used to transfer data from PA to OM RHINTE10 is to transfer OM data to PA tables RHINTE30 is to update IT0001 (org assignment) for the person you have selected RHINTE20 is to determine whether the data relevant for integration is available in PA and OM Overview It is important to realize that in PA, there are tables that contain objects from OM, i.e. for those items displayed on infotype 0001 Organizational Assignment. Sometimes the tables can get out of step with those in PD table HRP1000. The tables are: T513, T513S Object type C (Job)

T528B, T528T Object types S (Position) and A (Work center) T527X Object type O (Organizational unit)

RHINTE00 This loops through all employees in PA by looking at positions on infotype 0001. It checks thecorresponding person to position relationship exists in PD (A008), if not it is created. RHINTE10 Generally, the program RHINTE20 will be used instead of this one. This program loops through the PD table HRP1000. For each job, position, work centre and organization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also. The main difference with this program as opposed to RHINTE20 is that this one has the option to delete items from the PA tables, which no longer exist in PD. RHINTE20 This program loops through the PD table HRP1000. For each job, position, work centre andorganization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also. 0 COMMENTS

OM - Configuration Steps POSTED BY Ananth TM on 4:38 AM under config, Organizational Management

Configurations Steps: -------------------------

IMGPersonnel management Organizational management Basic settings Maintain number ranges set up number assignment for all plan versions Maintain object type: IMGPersonnel management Organizational management Basic settings Data model enhancement maintain object type Maintain infotypes IMGPersonnel management Organizational management Basic settings Data model

enhancementinfotype maintenance maintain infotypes Relationaship maintenance: IMGPersonnel management Organisational management Basic settings Data model enhancement Relationship maintenance maintain relationships Maintain evaluation paths: IMGPersonnel management Organisational management Basic settings Maintain evaluation paths Maintain personnel actions: IMGPersonnel management Organisational management Basic settings Maintain personnel actions Activate inheritance of account assignment features IMGPersonnel management Organisational management Basic settings Activate inheritance of account assignment features Setup integration with Personnel Administration IMGPersonnel management Organisational management Basic settings Integration Setup integration with PA Transfer data from Pa IMGPersonnel management Organisational management Basic settings integration transfer data from PA Perepare integration with Pa MGPersonnel management Organisational management Basic settings integration Prepare integration with PA Transfer data to PA IMGPersonnel management Organisational management Basic settings integration Transfer data to PA Check integration consistency IMGPersonnel management Organisational management Basic settings integration Check integration consistency