Employee To Vendor Conversion in SAP

By Arindam Bhuin, Tricon Infotech Introduction There are accrued payments to the Employees apart from payroll as they are related to Organization activities. These kind of accrued payments are not paid by through HCM (Payroll) as they are related to handling expenditure related to organization activities. Examples of these kinds of payments: Petty cash (temporary and permanent). Settlement of vendor invoices. Office operations (buffets and misc.).

We need to have the ability to automatically create employee as a supplier. By this we can link the employee record in HCM with the financial aspect, it is very important that they have the same data and number Example: John has employee number INEMP56, so I can create him as a supplier with the different number INVEN10 and also with the same data. Pre-requisite 1. Employee should be created in the system. 2. The following infotypes should maintained for an employee Actions (Infotype 0000) Organizational Assignment (Infotype 0001) Personal Data (Infotype 0002) Permanent Residence (Infotype 0006 Subtype 1) Bank Details (Infotype 0009 Subtype 0 or 2)

3. Note that for the reference vendor, reference data must exist for all company codes that are applicable according to HR master data. 4. You must be sure that the reference vendor is assigned to an account group that requires internal number assignment. Step 1 Go to Transaction PRAA Fill the following fields with relevant data as shown in screenshot below

Personnel (for which vendor has to be created) Reference Vendor File name Name of job Name of batch input session

Click on Execute (F8) The following output will appear

Step 2 Go to Transaction SE38 Execute the Report RFBIKR00 On the selection, enter the File path name (same as entered in transaction PRAA)as shown below:

Click on Execute (F8) The output will appear as below:

Click he

Create PU12 interface format for Time data'

By Kamesh, Infosys Go to transaction PU12.

Click on Create. Give Country grouping and Description .

Select both Master data and Payroll results/Time data check box as below.

Select infotypes as per the requirement as a part of Master data.

Enter the table name, cluster name and press enter e.g. PCL2, B2.

Press Enter.

'Change validation' in PU12

By Kamesh, Infosys This document explains what is change validation concept in PU12 and what are all the options exist in change validation concept . Change validation in PU12 is useful when the information only needs to appear in the export file if the data has changed from the previous time the export was run. Change validation is applicable on PU12 interface level. To achieve this, select the 'change validation' button at the top of the screen. Tcode :PU12

Interface format is defined with below infotypes.

Click on Change validation .

Place the cursor on Objects of change validation and Click on Create.

Pop up will be asked to choose the infotypes and all the infotypes defined in interface format will be shown up here.

IT0002,IT0006,IT0008 and IT0014 are selected .

Any field of P0002 ,P0006, P0008 and P0014 can be exported to Pu12 file . Few fields can be deleted like INFTY field becuase always INFTY field will have infotype number even if we change the data also. To ensure that only fields that have been changed are exported, the 'single field validation' must be assigned at the table level. To do this, select the table and select the single field validation button. Removed all the fields and remaining fields are to be exported to file .

Single field validation shown in the below screen .

Click here t

Matrix Structure in SAP HCM

By Sravanthi

Requirement: To implement the functional areas into respective departments in the Org unit. Matrix Structure for functional areas: SAP, Oracle and Mainframe with organization for the org units HR department, Finance Department, IT department and Procurement Dept.

Matrix Structure is set up by using the concepts of objects, relationships and Evaluation path. Objects: O (Organizational Unit), S (Position), P (Person), R Resource type, T Task. Relationships such as A: bottom up or B: top down Evaluation Paths such as O-O, ORGEH, O-S-P. 1) Path: Human Resources Organizational Staffing PPOCE Create. 2) Transaction Code as: PPOCE. In this we create the Org units and departments. Management Organizational Plan Organization and

Date can be entered as per requirement.

Create the Organization units as shown below. In the below example I just took HCL Pvt ltd as the organization unit and under that create four departments HR, Finance, IT and Procurement Departments.

Now go to SPRO SAP Reference IMG Personnel Management Organization Assignment Basic Settings Data Model Enhancement Main Object Types.

Click on New Entries and give the desired object name.

Maintain info types for the object type which has been created earlier. Create the object. Create the relationship. The standard object and the relationship need to be created for the object type.

Here we relate the object name to the standard object (info type 1000) and relationship (info type 1001) as shown below.

Click here to continue...

Profile Match Up tool

By Sravanthi Profile match up tool is a tool which can be used to match the profiles of different objects which could be used for further decision making. To execute to this profile match up tool certain components must be in place. A comparison of the position's requirements Vs the person's qualifications.

Qualification Catalog: It denotes the complete list of Qualifications and it is combination of all Qualification Group. Qualification Group: It denotes an independent category of Qualifications. These can be various Qualification Groups created as per requirement. The group of Qualification groups would constitute a Qualification Catalog. A Qualification group might have a sub Qualification Group if needed. Qualification: It denotes the smallest element in the hierarchy it is the element which is assigned to a person or a position. The number of Qualifications to be created would dependent on requirements. The respective Qualification must be created under the corresponding Qualification Group. A Proficiency Scale must be assigned to Qualification Group which would get inherited to all Qualifications created under the respective Qualification Group.

Below are the configuration settings for the Qualification Catalog. SPROSAP Reference IMGPersonnel ManagementPersonnel DevelopmentMaster DataEdit Qualifications Catalog.

Click on Catalog Create.

Give the Scale: 5 point Scale. Click SAVE and press enter. Click on SAP Catalog Create.

Click on Qualification group.

Click h

Configuration of SAP HCM Structural Authorizations

By Kiran Kumar Vuppala, Sita Corp (India) Pvt Ltd About this document This document describes how the Structural Authorization, its importance and the configuration steps. It can be used as a best practice which includes test scenarios.

Explanation was given with the help of screenshots, but please do not expect that all the possible customizing options are shown with screenshots. While going through this document, try to access your own system for perfect understanding. Authorizations Authorizations control system users access to system data and are therefore a fundamental prerequisite for the implementation of business software. General Authorizations o Single Role - Individual authorizations either to screens, infotypes, etc., - Group of Single Roles clubbed together and called as composite

o Composite Role role Structural Authorization

The Structural Authorization determines to which object/objects in the organizational structure the user has an access. It describes the special authorizations that you can define in Personnel Planning and Development in addition to the basic access authorizations The General Authorization determines which object data (infotype, subtype) and which access mode (Read, Write ...) the user has an access. General Data Structural Authorizations will be assigned to Users with Structural Profiles in table T77UA (User Authorizations) or using Transaction Code OOSB. Initially system checks the table T77UA consists of Username with a Structural Profile attached to it or not. If there is no entry in the table T77UA for the user, then the system checks whether the User is assigned with profile SAP*, else authorization is denied. In the standard system, there will be a User Name - SAP* assigned with Profile - ALL, which means, when we first implement mySAP HR, all users have complete authorization concerned to Structural Authorization. Note: If you delete the SAP* row, no user can pull the report for any standard org Structure. (Never ever delete the standard entry)

IMG Configuration Step 1

Node Maintain Structural Profiles Transaction Code OOSP Table Name T77PQ
Select Maintain Structural Profiles

Below window will get displayed. Click on Authorization Profiles New Entries

Input Authorization Profile and Authorization profile Name

Save it in a Customizing Request. Select our profile, and Double Click on Authorization Profile Maintenance

Click her

Additional fields for selection in the Free Search (Object Manager) option in PA20/PA30
By Ganesh Kumar K, Intelligroup Below is the documentation helps in adding the additional fields (like custom info type fields) for selecting the Employee number in free search (Object manager) in PA20.

When you click on the free search option system internally calls an ADHOC query. These entries for each scenario (like Employee, Applicant) will be maintained in T77OMAHQ_FUNCAR. If there is no entry in this it calls the default one /SAPQUERY/HR_ADM.

Go to SQ02 and copy /SAPQUERY/HR_ADM to ZHR_ADM, we can add the custom info type fields in the new one.

Add the info types from Edit -> Info type selection

Select the required Info type from further info types.

Add the info type in the Info set and Generate. Assign the Info set to the User group.

Make and entry in T77OMAHQ_FUNCAR

Now go to PA20 and check we can see the newly added fields.

Display Photo of any employee in PA30

By Saikumar Bonakurthi, HCL Technologies To display photo of any employee in PA30/PA20/PA10 , we need to modify header . To modify header go to SM30 table name T588J.

Make a entry in the table 06 2 70 0000 PERNR PIC

To know the header modifyer no we have to check in PA30 and selecting one header filed of tech settings , we can see a program name is /1PAPAXX/HDR_80006A. so here 06 is your header modifier. so for 06 u need to make entries in the table.

T.Code : OAAD To upload photo into R/3 select the button Store and Assign

Enter Business object PREL and Document Type HRICOLOFOTO and create

Click here to

Absence Quota Generation (HCM)

By Naveen Bhukta, TATA Consultancy Services This document explains the various steps involved in configuration of IT0007 and also there by how to generate Absence quota using the standard program RPTQTA00. IT0007 Configuration Steps SPRO Path

Public Holiday Class

SAP Calendar: Main Menu

Create Public Holidays

Public Holiday Calendar

Personnel Subarea Grouping for Work Schedules A personnel subarea grouping for work schedules is a grouping of personnel subareas with the same work schedule rules. The personnel subarea grouping for work schedules, the Holiday ID and the Employee subgroup grouping for work schedules form a key for the work schedule rule. This allows you to define different organizational groups for work schedules within the same public holiday calendar, for example.

Group Personnel Subareas for the Daily Work Schedule In this step, you assign a personnel area grouping for daily work schedules to a personnel area grouping for work schedules.

Example Employees in personnel areas 0001 and 0002 have been assigned to personnel subarea grouping for work schedules 01. Employees in personnel area 0003 have been assigned to grouping 02. All three personnel areas are to use the same daily work schedules. You therefore assign personnel subarea grouping for daily work schedules 01 to personnel subarea groupings for work schedules 01 and 02.

Define Break Schedules

Previous Day Indicator The previous day indicator in Time Management indicates that the record should be assigned to the previous day. It is relevant mainly to daily work schedules which bridge two calendar days (e.g. 22:00 06:00). Use You only use the previous day indicator if you record time data with clock times. The daily work schedule assigned to the employee always applies to the day on which the start time lies in this case. The information provided by the previous day indicator is therefore of central importance. There is no other way for the system to assign a record which has a start time a day later than the start time in the personal work schedule to the correct daily work schedule. Planned Record is set Examples The daily work schedule NIGHT 2 comprises a planned working time of 22:00 through 06:00. An employee works the night from December 14 to December 15, and works a substitution for his/her foreman from 02:00 through 04:00. The previous day indicator was not set when the substitution was recorded. The substitution is therefore assigned to December 15 instead of December 14. This can lead to the following problems, for example: Collisions with substitutions on the following day. The substitution not being taken into account in payroll, as the following day is a Saturday and the employee does not have to work on Saturdays. Define Rules for Variants In this step, you can define rules for daily work schedules. The rules allow you to stipulate that a variant of the daily work schedule should apply on certain days. Taking the following parameters into account, you can set up rules for daily work schedule variants: The public holiday class of the current day The public holiday class of the next day working entered 02:00 time 05:00 22:00 -> previous day 06:00 indicator

weekday Example A number of employees in your enterprise work Monday through Thursday from 8 a.m. to 4.45 p.m., and from 8 a.m. to 2 p.m. on Fridays. The daily work schedule for Fridays is derived using the daily work schedule selection rule 01 with variant A

Click here to continue...

SAP Enterprise Structure for Personnel Administration

By B.D Ballani, Tata Consultancy Services The following elements define the SAP enterprise structure for Personnel Administration: Company Code Personnel Area Personnel Subarea

Remember to assign the same country grouping to all personnel areas within a company code. The configuration of these elements which includes defining and assignment are done as follows: Step 1 : IMG : Enterprise Structure -> Definition -> Financial Accounting -> Define Company

Step 2 : IMG : Enterprise Structure -> Definition -> Financial Accounting -> Edit, Copy, Delete, Check Company Code

Step 3: IMG : Enterprise Structure -> Assignment -> Financial Accounting -> Assign company code to company

Click h

Step-by-Step procedure to maintain Dynamic actions (HCM)

By Piyush Mathur, Tata Consultancy Services Dynamic Action feature is provided in SAP HR to call another Infotype while processing one Infotype. Here, you control the initiation of actions when maintaining an Infotype record. For each action, you can determine whether it is always carried out when you change an Infotype or a subtype or whether it is only carried out if you change certain fields. You can state whether the action is to be carried out for "Change", "Create" and/or "Delete" record. You can store the conditions for executing the action, for example, the comparison of the old and new value of a field. Finally, you can also specify default values for a record that is to be created. View V_T588Z is the maintenance table to maintain Dynamic Actions. Let understand the views field for V_T588Z. Execute the T code SM31 and open V_T588Z for maintain.

A new popup will come for Infotype. Pass the Infotype for which you want to maintain the Dynamic Action. I am taking example for a custom Infotype 9800.

Press Enter. Now maintenance screen will open for view V_T588Z. Click on New Entries.

Field contains below 6 columns.

Sty: This column is to maintain Dynamic Action for Specific Subtype. If user need to execute the Dynamic Actions based on specific Subtype then this column need to be filled else it can be blank. Field Name: Column to specify field name, if require to process Dynamic Actions. Function Character of step: This column is important part of Dynamic Actions. Its specified on which action (Create/Change/Delete), dynamic action need to be called. This column required to fill with two digit of below numbers as per the requirements. 00 - An action is carried out irrespective of whether specified Infotype was 02 For Change 04 For Create 06 For Change and Create 08 For Delete 10 For Change and Delete 12 For Create and Delete Sequence Number: To determine the sequence of each step Indicator of Step: Below are the available indicators. P - Check conditions I - Maintain infotype record W - Set default values when creating a new record V - Reference to another step F - Call routine M - Send mail Variable Function part: Another important column which contains the steps and definition on the based of previous column Indicator of Step. If maintained Indicator of Step Column as P Plausibility checks Here you can enter values for infotype field to check the condition before proceeding the next step. Infotype field values are available in PSAVE structure. For example to check the Employee Status maintained as below: Infotype Field ..... Ind. Variable function part created/Changed/deleted.

0007

STAT3

P0007-STAT3='0'

If maintained Indicator of Step Column as I Maintain Infotype record To create/Change/Delete another infotype ,Enter the step, infotype, subtype, object ID, start and end dates of the record and an indicator which defines whether the step is to be run in the background. Separate the indicator for suppressing dialog from other entries by a slash D (/D). 9800.... I INS,6,,,(P9800-BEGDA),(P9800-ENDDA)

Step: Create a Infotype record (0006) without subtype and object ID. The start and end dates are the same as those in the current Infotype (9800); specify these two fields only if they are filled because the dynamic action was triggered by this Infotype. If maintained Indicator of Step Column as W Default values for new record This step used to default the variable values for new Infotype. Set the defaults for the Infotype, subtype, object ID, start and end dates using an I step and not a W step. Do not set defaults for Q fields of an Infotype because the values for these fields are derived from the corresponding P fields. Examples Infotype 0021 0021 Subtype ..... 2 2 FC 04 04 W Ind. I Variable function part INS,0015,M430 P0015-BETRG='10000'

When a Family/Related Person record (0021) record with subtype 2 (child) is created, an Additional Payments record (0015) with a default amount of 100.00 is created. If maintained Indicator of Step Column as V Cross-reference to another step Here, you can combine fields to groups. The variable function part contains the value in the field which follows the "field" column. Steps which are specified only for the following field are also triggered for each of the other fields. Examples Infotype 0016 0016 Field PRBZH PRBZT FC 06 06 Ind. V I Variable function part PRBZT DEL,0019,01/D

Infotype 0019, subtype 01 is deleted in the background when the field PRBZT or PRBZH in infotype 0016 is changed or created (function code 06). If maintained Indicator of Step Column as F Call a routine.

Sometimes user wants to do some complex validations before processing the Dynamic action which can not be easily maintained in V_T588Z. IN that case, developer can developed a ABAP programs in a routine and called the routine in Dynamic Actions. Below is the syntax to call the routine, Infotyp ..... 0001 Ind. F Var. function part GET_DATE(ZPUDYN01)

GET_Date is the routine name in ABAP program ZPUDYN01. M - Send a mail Enter the name of the feature which defines the characteristics of the mail. Example Infotype 0001 Field ..... SACHP Ind. Var. M function part M0001

A mail is sent when the field SACHP is changed. The characteristics of the mail are defined in feature M0001 For more information on same please refer SAP F1 help. Now let maintained the records in V_T588Z. Lets take a scenario, Whenever user Create or Change Infotype 9800, Infotype 6 need to be created. So Maintain entries in V_T588Z as below.

Now create a new record for IT9800.

Now as you press save, dynamic action will be triggered and a new window will open to maintained Infotype 0006.

You cab restrict the Infotype creation on the basis of Subtype and you also suppress the dialog i.e. you can create the new Infotype in background by specifying /D. For example INS,6,,,(P9800-BEGDA),(P9800-ENDDA)/D

Creating custom payroll function

By Piyush Mathur, Tata Consultancy Services This document contains step by step procedure to create custom payroll functions. Before starting development procedure, we will cover basic details of payroll Schema and payroll functions. Payroll Function and Schema: Payroll function and Schema plays very important roles in SAP HCM payroll run. Functions are used to calculate different amounts on the basis of Infotype values, wage type values etc. SAP provides many standard functions to calculate the amount for payroll run.

Now lets have a small description of Schema. Schema is just a collection of payroll functions executed in specific order. You can create Schema using transaction code PE01. SAP Payroll driver reads the schema and execute the embedded payroll functions. Let create payroll function. Execute transaction code PE04. Pass Custom function name and press Create.

Now click on Green Tick in pop up box.

Now pass the function description. There is option available to create function to corresponding to any countries. Select Other Countries.

Next click on Input parameters.

Click here to continue....

Configuration of Wage Types in IT0014 and IT0015

By Govindu Naveen Bhukta, Tata Consultancy Services SPROPersonnel ManagementPersonnel AdministrationPayroll Employee Subgroup Grouping for PCR and Coll.Agrmt. Prov. DataBasic PayDefine

The below setting will make sure that you are configuring the wage types for a particular country which you select here.

SPROPersonnel ManagementPersonnel AdministrationPayroll DataRecurring Payments and DeductionsWage Types

Define Reason for Change

Copy Wage types.

Wage Type Group

Check Wage Type Texts

Click here to continue...

Concepts of Central Person and Steps to follow in Case if all the Personnel Assignments for a Personnel Number are not shown in PA30
By Vijay Sundaresan, Tata Consultancy Services Before going into a specific issue, lets see what a Central Person is. CP (Central Person) is an object type which is linked via a relationship to object type P (Person). CP object is created in background while hiring a person (necessary configuration should be in place). CP is mainly required when there are multiple countries implemented in a system and an Employee needs to be re-assigned to a country other than Home country. In that case a new PERNR is generated for this employee for the new Country and this PERNR is again linked to the same CP object. Thus all the various PERNRs of Employee are liked to the same CP which uniquely identifies the Employee. CP->PERNR1 (Object type P)

CP->PERNR2 (Object type P) CP->PERNR3 (Object type P) CP->PERNR4 (Object type P) This helps in tracking the Employee with different PERNRs in different countries with the a unique Central Person ID (CP). SCENARIO: In PA30, Below is the screen where the Pers Assgn at the top has only one assignment in Yellow.

The related Personnel number 3364 is shown below with Pers Assgn as Blank.

Ideally the above two personnel numbers refers to one and the same Person due to the different Personnel Assignments. (like expatriate). But the Personnel Assignments in the system shows just one instead of two. This is because that the Central Person ID 00000227 is linked only to Personnel Number 00003369 and not to the related Personnel number 00003364 as it is below.

Now the above two Personnel Number 3364 and 3369 has to be linked to the same Central Person ID so that there can be two different Personnel Assignments. When you try to create a link between the Central Person and the Personnel Number directly in PP01, you will get the below error. Relationship CP B 209 P cannot be maintained using basic transaction

This can not be maintained through the basic transaction PP01. To maintain this through Basic Transaction, following settings has to be done. Go to SM30 and the table is T777E

Select the relationship 209 and GOTO Allowed Relationship in left

In the below screen, if both the Top Down and Bottom Up relationships are checked (enabled) for NOT MAINTAINED field, then it will not allow to maintain in the basic transaction PP01.

Click here t

Creating an Organizational Structure

By Madhusudhan M Before we go ahead and create an Organizational Structure, lets have a quick look at the terminology used in the organization structure. Structures in SAP HCM 1. Organizational structure. 2. Enterprise structure. 3. Personnel structure 1. Pay scale structure Applicant structure Wage type structure

Organizational structure: It contains organizational objects /elements. These are called building elements.

Organizational objects / elements are: Organizational objects Organizational unit Job Position Person Cost center Task Task group Org. key O C S P K T Ts

If we create any organizational object, System will assign a eight digit numeric number, which is called unique Number. 1. Organizational Unit: Represents a functional unit in your enterprise, Human Resources department, for example. According to how tasks are divided up within an enterprise, this could be a department,

group or project team, plant, for example. Organizational units differ from other units in an enterprise such as personnel areas, company codes, business areas etc. These are used to depict structures (administration or accounting, for example) in the corresponding components. Kinds of organizational units A). Main Organizational unit / Root organizational unit: Whatever the organization we create for the first time is called Main organizational unit. B). Sub organizational unit: Under Main org. unit whatever we create is called sub org.units. 2. Job: Jobs, in contrast, are classifications of functions in an enterprise (administrator, for example), which are defined by the assignment of characteristics. Jobs serve as job descriptions that apply to several positions with similar tasks or characteristics. Jobs are used as templates to create Positions that means to say without a job we cant create a position. Example:

Manager
Engineer Consultant Designer Administrator

3. Position: Represents a post that can be occupied by a person (employee) in the staff assignments of an organizational unit, purchasing administrator, for example. Positions differ from jobs. A job is not concrete but rather the basis for the creation of various positions with similar tasks and characteristics. . Positions are created based on jobs; it means to say without a job we cant create a Position. Job Manager Position HR manager Marketing manager Finance manager Plant manager Production engineer Site engineer Software engineer SAP HR consultant FI/CO consultant SD consultant Software designer Web designer

Engineer

Consultant

Designer

1.

Person: An individual, who is listed as an employee in Personnel Administration. A position can be occupied partially, hundred percentage. Task: It is a collection of duties and responsibilities. Tasks are assigned to jobs and positions. Activity which is performed within an organizational unit

2.

1. Task group: It is a group of tasks which can be assigned either a job or a position. * HOW TO CUSTOMIZE ORGANIZATIONAL STRUCTURE* Organizational structure can be created in three procedures. 1. Simple Maintenance 2. Expert Mode / Detailed Maintenance 3. Organization and Staffing Comment: If we create organizational Structure in any procedure, the same structure reflects in other two procedures. If we create organizational structure in Simple maintenance and Organization and Staffing the relationship between the objects are assigned by the system. Where as in detailed Maintenance the user has to assign the relationship code. The relationship between two objects is expressed in three digit numeric characters. Each and every relation can be expressed in two ways. 1. Top down which is indicated with B 2. Bottom up which is indicated with A For example: TATA group of business---Btop down. TATA mobiles business-- -Abottom up In the above Organizational units i.e. BTATA group of business shows its relationship towards A i.e. TATA mobiles, in the same way A i.e. TATA mobiles shows its relationship towards B i.e. TATA group of business. That means to say TATA mobiles reports to TATA group of business / TATA group of business is the line supervisor of TATA mobiles. So we come to know that the lower level organizational object is A So we come to know that the higher-level organizational object is B The relationship codes can be seen through transaction code OOVK table name is T778V The relationship codes: Relationship code Relationship bottom up Indicates with A * 001 Is a subdivision of 002 Reports (line) to 003 Belongs to

Relationship top down Indicates with B Is subdivided into Is line supervisor of Incorporates

004 005 006 007 008 009 010 011 012 013 014 015 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051

Is subordinate to (disc.) Is subordinate to Substitutes for Describes Holder Successor Substitute Cost center assignment Manages... Staffing requirement Cost distribution Is identical to Is carried out by Previous org. assignment Planned org. change Is a specialization of Is equipped with Requires Reserves Takes place in Is attended by Is held by Has a prebooking for Imparts Presupposes Is a specialization of Requires Fulfils Is planned for Was attended by Is previous job of Is organized by Designated as successor Has potential for Supplies Was cancelled by Is an equivalent job Interests and preferences Dislikes Consists Of Created receives Contains Application by Is developed by Assesses Is a session of

Is disc.supervisor of Is supervisor of Is substituted by Is described by Holder Successor Substitute Cost center assignment Is managed by... Staffing requirement Cost distribution Is identical to Carries out Previous org. assignment Planned org. change Is a generalization of Is contained in Is required by Is reserved by Is location of Takes part in Is the instructor for Is prebooked for Is imparted by Is presupposed by Is a generalization of Is required by Is fulfilled by Can attend Attended events of type Is subsequent job of Organizes Designated as successor Is a potential of Is supplied by Has cancelled Is an equivalent job Interests and preferences Is dislike of Is part of Was created by Was created for Is an element of Application for Develops Is assessed by Is main event of

052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 077 080 081 083 088 089 090 101 108 200 201 202 204 207 208 209 210 220 221 222 223 224 225 226 227 228 230

Attends session Still requires Uses (for attendee) Uses (for bus. event) Person has cost center Has attendee apprsl model Has event apprsl model Employee pool Capacity assignment Equals Requirement description Requires Requirements definition Planned assignment Reserve pool assignment Exclusive temp.assignment No shift planning Is temporarily done by Responsible for cost plan Parallel temp.assignment Shift planning by Passes through Assigned to exposure grp Higher duty holder Is Key Position of Dotted Line Reports to Dotted Line Reports to Is responsibility of Country reassgmt to Is assigned to Replaces Assigned role Notification agent Possible roles Is identical to Is identical to Is filled by Substitutes with profile Belongs to Is object reference of Belongs organizationally Is assigned (valid.per) Is object type of Is event of Is method of Triggers Terminates Is part of

Is attended by Is still required by Is used by (attendee) Is used by (bus. event) Persons on cost center Is at'ee apprsl model for Is event apprsl model for Employee pool Person assignment Equals Requirement description Defines demand for Requirements definition Planned assignment Reserve pool assignment Exclusive temp.assignment No shift planning Works temporarily as Responsible for cost plan Parallel temp.assignment Shift planner for Is passed through by Exposure group contains Higher duty holder Incorporates Key Position Dotted Line Supervises Dotted Line Includes Is responsible for Country reassgmt from Is assigned to Is replaced by Role incorporates Notification agent Possible roles Is identical to Is identical to Has employment contract Substitutes with profile has Contains objects Incorporates SAP objects Incorporates(for valid.) Is container instance of Has event Has method Is triggered by Is terminated by Contains

231 232 240 250 262 263 264 280 281 282 283 290 291 292 293 299 300 301 310 311 312 313 314 315 400 401 601 605 606 607 620 700 701 710 711 712 750 751 752 753 754 755 756 900 903 962 963

Assignment exists Has element Existence depends on Is responsible for Reports to Belongs (not uniquely) to Belongs (uniquely) to Belongs to system Belongs to function Is an element of Sends message Has administrator Partner agreement Maintains brokers Has user for commissions Is supported by... Is financed by... Increases Is responsible for Substitutes for Belongs to (reclassif.) Reclassified from Is to be financed by Responsible for Financing Is child of Is assigned Represents Is an Element Of Is attribute ref. for Is described by Is assigned Is responsible for Is assigned Fulfils Requires Imparts Vacant position in Is responsibility of Fills Publishes Publishes in Application by Has applicant Manager to manager Belongs to (alternative) Reports to (alternative) Belongs to (preferred)

Assignment exists Is an element of Defines Is responsibility of Is superior of Incorporates (not unique) Incorporates (uniquely) Uses function Has combination Has object Receives message Is adminstrator for Partner agreement Brokers are maintained Is user for commissions Supported Finances... Is increased by Is responsibility of Is substituted by Incorporates (re-valuatn) Reclassified into Is earmarked for Responsible for Financing Is parent of Is assigned Is Represented By Includes Element Refers to attributes of Descriptive element of Is assigned Is responsibility of Is assigned Is fulfilled by Is required by Is imparted by Incorporates vacant pos. Is responsible for Will be filled by Published by Publishes Application for Applied for position in Manager under manager Incorporates(alternative) Is superior (alternative) Incorporates (preferred)

Simple maintenance: How to create organizational structure in Simple maintenance? PathSAP easy accesshuman resourcesOrganizational managementExpert modeSimple Maintenance Text Create Transaction code PPOC_OLD

Change

PPOM_OLD

Display

PPOS_OLD

Enter PPOC_OLD in the command field Or Go through the path

Click he

HCM - "Personnel Actions" Tutorial

By Madhusudhan 1. DEFINE INFO GROUPS

Click on define info groups You will a popup screen

Double click on user group dependency on Menus and info groups Go to new entries

Press enter and save.

Come back to popup screen and double click On Info group You will get another popup screen in which enter the defined menu code i.e. NE

Press enter Go to new entries

Press enter and save.

Click on Info group modifier

Click on Change icon

Maintain infogroup modifier Ctrl F2 and Ctrl F3 Set up personnel actions Same path

Click on set up personnel actions You will get a pop up screen

Double click on personnel action type Go to new entries

Press enter and save.

HCM - Create Positions

By Achirangshu De, Thomson Reuters

Transaction Code
PP01

Object
Select Object Create

Save Enter a customizing request

New Position (Object) has been created.

Table HRP1000 (Infotype 1000) stores all the information.

Table T528B also gets populated with the new record. This table stores only the active positions.

Relationships (Infotype 1001)

Now we need to create the Relationships (Infotype 1002) and other infotypes

Relationship : Belongs to (Organizational Unit)

Relationship: Cost Center Assignment

Description (Infotype 1002)

Some other information can also be stored in Description

Click h

Add infotypes to PA30

By Madhuri This tutorial would detail the procedure for adding more infotypes in PA30. Go to transaction PA30. By default, following are the tabs (for various infotypes) are available for maintenance:

We can add new infotypes to the above screen by using the infotype V_T588B. For this, we need to know the user group for which the user belongs. For this click on System -> User Profile -> Own data. Click on Parameters tab: Check the value assigned for UGR.

Let us check the same: Go to transaction SM30 and enter the view V_588B.

Enter the value 01 (Basic Personal data)

Click on Continue.

Here you can observe the infotypes related to Basic personal data being assigned to different user groups. Scroll down the list for more information:

Thus any infotypes that you would look to appear in PA30 needs to be maintained here as per the infotype category.

Deleting Personnel information

By Madhuri The personnel information is maintained in the transaction PA30. Let us first check what happens when we try deleting the personnel information from PA30. Go to transaction PA30. Enter the required personnel Number and press Enter.

Select the corresponding Infotype for which we need to delete the information and click on Delete button available on the toolbar. The screen with details regarding the Infotype appears:

Now click on Delete button again. Following message appears:

Alternative way to delete the personnel information: Go to transaction PU00. Enter the personnel number to be deleted:

Press Enter.

Click on Execute button. Following screen appears:

Select the Infotype record to be deleted and click on Delete:

Following confirmation pop-up screen appears:

Click on Yes. Following confirmation message appears: