After creation of Project organisation with custom object type as in the link Procedure to create a custom object type in General Structures Mode of OM module..

now, let us create Matrix structure by mapping the Organisational structure with the Project organisation as below: For this, a custom relationship and custom evaluation path must be created...

1) Creation of custom relationship Y11, with two dimensions 'assigned to' and 'incorporates' as in the screen shot in table T778V

Now select the relationships, and click on Allowed Relationships in the Dialog Structure to list the object type for which this relationship is allowed....

Since, each of the dimensions A and B of the Y11 relationships are subtypes of the Relationship infotype 1001, we should create them as subtypes and assign time constraints to them in T778U as follows:

Now Assigning time constraint to AY11 subtype of Infotype 1001 as below:

Like wise for BY11 subtype of Infotype 1001 also:

This completes creation of custom relationship Y11...

2) Custom Evaluation path: Z-11_s-----Go to T778A via OOAW tcode and click on new entries to create the evaluation path as below:

Now select the Z-11_S and double click on the Evaluation path (individual maintenance) in the Dialog structure and list is out as in screen shot:

Now go to matrix structure in the front end via PPME and give the dimensions as follows:

Click on execute to display the following screen for mapping:

Select the position to be part of the Project team 4 as under

Now click on the projection icon to display your matrix structure or Go to  PPSM of General Structures and view using the custom evaluation path Z-11_S

Regards,

Santoshini.

Unlike other modules data processing in SAP , HR module data processing is little bit different. Here the resultant data will be stroed in Clusters , which we can not access directly with normal select satments . One have to use the SAP provided methods only for data accessing. So I thaught the below program will help a little for HR ABAPers who are learning now.

Below is the program to retrieve an employee's last run payroll results. For this program I used PNP LDB .

PROGRAM:-

And the Final output will be like as below.

Regards,

Praveen Chitturi.

Hi,

AGENDA:-

Writing a  sample code for report program to retrieve new Payroll results generated in the selected period. It will include all those with status indicator "A" and their immediate predecessors, those with status indicator "p".

FUNCTION MODULES USED :-

PYXX_GET_EVALUATION_PERIODS

PROGRAM CODE:-

*&---------------------------------------------------------------------*

*& Report ZR_CSD129

*&

*&---------------------------------------------------------------------*

*&

*&

*&---------------------------------------------------------------------*

REPORT ZR_CSD129.

** Data declarations for the function module import and export.

DATA: IT_RESULTPERIODS TYPE TABLE OF PAYIN_RESULT,

W_RESULT TYPE PAYIN_RESULT,

W_RT TYPE PC207.

TABLES PERNR.

START-OF-SELECTION.

GET PERNR.

** After Get pernr Call the FM which will take Pernr as input

** along with IN-period , Period parameters.

** We will get the output of pay results as a table

CALL FUNCTION 'PYXX_GET_EVALUATION_PERIODS'

EXPORTING

CLUSTERID = 'IN'

EMPLOYEENUMBER = PERNR-PERNR

INPER_MODIF = PN-PERMO

INPER = PN-PAPER

TABLES

EVALUATED_PERIODS = IT_RESULTPERIODS

EXCEPTIONS

NO_PAYROLL_RESULTS = 1

NO_ENTRY_FOUND_ON_CU = 2

IMPORT_ERROR = 3

OTHERS = 4.

IF SY-SUBRC <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

** Loop the Payroll result internal table for printing the Data

LOOP AT IT_RESULTPERIODS INTO W_RESULT.

LOOP AT W_RESULT-INTER-RT INTO W_RT WHERE LGART = '/560'.

WRITE:/ PERNR-PERNR, W_RESULT-EVP-SEQNR, W_RT-LGART, W_RT-BETRG, PN-PAPER.

ENDLOOP.

ENDLOOP.

Regards,

Praveen Chitturi

USEFUL FUNCTION MODULE IN HR ABAP :-

I will keep updating this FM document for better result.

Regards,

Praveen Chitturi.

Steps :

Following Steps are involved in creating an HR query:

1. Set Query Area

2. Creating a user group

3. Creating info set

4. Creating Query  and Executing

Set Query Area

There are two query areas, Standard area which is client dependant and Global area which is client independent.

For our exercise and development we would be using “Global area” because of following reasons:

• It requires transport request to create any object in Global area, means no separate process for transport request required.

• If any change is required in any component in future, it can only be done in development client and then moved along the landscape.

• It ensures that all queries under the info set created in global area will also have to be created in global area.

To set query area go to transaction SQ01, Environment and Query Areas: Select Global area and click choose

Now go to tcode SQ03 to create a user group as follows with a meaningful name like ZHRPA for users in HR and using Personnel Administration Module and click on create tab….as shown below

Now that the user group is created, assign user id to this user group. In other words, it is nothing but assigning users to this user group by clicking on Assign users and infosets…

Creating Info set

Next step is to create infoset, an infoset defines the data that needs to be used for building reports such as name of employee, position, salary, education etc.

For HR, Logical databases are used, which makes it fairly simple to have a query with a lot of data without much effort. Infoset is created based on Logical database and all the data related to that logical database can be used in queries.

Go to transaction SQ02 for creating infoset, even now you are still in the global area, which will not change unless you change it from step 1, however do ensure that it shows query area as Global.

Give a meaningful name in infoset area in our exercise we will be using ZHRPA_INFOSET, click on create in SQ02 as follows:

Now give a meaningful name to the infoset, and assign logical database as PNPCE, it’s the logical data base for personnel administration and uses all info types mentioned in personnel administration. Now click OK

It will take you to the infotype selection area, select the ones required, in our case we will select Organizational Assignment and Personal Data. Click Ok Icon

The screen will have two areas, one that shows complete set of fields and one on the right that shows fields that can be used in queries. Fields can be moved from Left to right side if not already available

Save the infoset at this stage and provide with the same transport request used previously. Generate the infoset

Go back to first screen of transaction SQ02 and this time enter the info set already created and click on Role/User Group Assignment. Select the user group that was create previously ZHRPA from the list click it and click save

Now go to ADHOC Query by Menu Path as follows: SAP Easy Access Menu—HR---Info systems—Reporting tools—Adhoc query

and give the info set and select the user group as follows:

Now Select the company code field to list the employees under SAM8 as follows

To the right hand side of the screen, give SAM8 (or any company code) as follows

Now select the first name and last name as follows as the output fields:

And click on Output as below:

To see the report as follows :

Regards,

Santoshini

Reporting using SAP Query  tool is as follows:

Creating Query : Go to transaction SQ01, if it doesn’t mention the user group that you just created then click on

Now give a name for the query, in our case ZHR_EMPDET and click Create

Select the infoset that was created from the list and click Ok icon

Give a meaningful title for your report. Click on

The fields that you require to be in the output of the report click on check box in List Column next to that field as shown below….select cost centre, employee name , position from Data fields on the left of the screen….and save

Now go back to first screen of transaction SQ01, it will show the query that was just created, click on execute to test the query by inputing any selection criteria…in this scenario, Personnel Area (SAML) taken….

Click on execute to see the report as follows

The following are the subsequent activities after payroll is run viz.,

1) Bank transfer:

2) Posting Payroll Results:

1. Bank transfer:  After payroll is run, SAP DME process will transfer payment amount to employees’ bank accounts as follows

• Run Preliminary DME Program: The Tcode to run Prelimiary DME Program is PC00_MXX_CDTA where XX = MOLGA.  This program will prepare the payroll results for the DME process (i.e., Data Medium Exchange Process).  It uses information from HR Masterdata (0001, 0002, 0006, 0009) and information from payroll results. (Payroll program tables WPBP and BT). This program creates a file which contains data which complies with bank regulations. If the values are inaccurate, you will need to correct the errors and re-run the preliminary DME program. If the values are accurate, you will use the file as input for creating bank transfer text files (DME file).

        Procedure:

        1.  Enter payroll area and Personnel number. Rest of the selection criteria can be kept default and click execute

        2.  Note down the program run date and identification feature.

• Create DME file: The Tcode is PC00_MXX_FFOT, where XX=MOLGA.  This program uses the successful file created by the preliminary DME program.  It produces a payment summary, a DME Accompanying sheet and a DME file (per Company code) for each paying bank of company.  The DME file may need to be uploaded into designated software that enables a transfer between  company and paying bank (house bank or company bank).

        Procedure:

        1.  Enter Program run date and Identification feature, Paying company code, payment method, House bank, Account ID, Currency, and click on execute.

             (In other words, the company provides DME file to the house bank. Based on this DME file, the house bank will make bank transfers.)

2.  Posting payroll results:  Posting payroll results to accounting is done after payroll run.  It is done once each payroll period, as well as after each off-cylcle payroll run. General Ledger (G/L)Posting involves the following:

• Grouping together posting-relevant information from the payroll results.
• Creating summarized documents.
• Performing the relevant postings to appropriate G/L accounts and cost centres.

How posting is evaluated:  Each employee’s payroll result contains different wage types that are relevant to accounting.

• Wage types such as standard salary, bonus and overtime represent various expenses for the company, which are posted to a corresponding expense account.
• Wage types such as bank transfer, employment tax, employees’ contribution to social insurance are the employer’s payables to employee, tax office, and are posted as credits to a corresponding payables or financial account.
• In addition, there are wagetypes such as the employer’s health insurance contribution which represents an expense for the enterprise, and at the same time, a payable to social insurance agency.  For this reason, such wage types are posted to two accounts---once debited as an expense and once credited as a payable.

Procedure:

1. Create a posting run using Tcode PC00_M99_CIPE.  This step creates a posting run based on payroll results, with a distinctive number, a ‘run type PP’, and the accompanying posting documents.  The posting run ensures that payroll results for an employee are only posted once.  Processed payroll results for an employee are flagged.  If the posting run is successful, it gets the status, ‘Documents created’.  If the posting run is unsuccessful, it gets the status, ‘Incorrect Documents’. Relevant error message will appear in output log.

A posting run can be executed in three modes.

• Test run without documents (T)
• A Simulation run with simulation documents (S)
• A Productive run (P)

Test Run (T):  In a test run, the system checks only whether the balance of expenses and payables is zero as it should be.

Simulation Run (S):  In both simulation and productive runs, the system checks all HR and RT tables and the posting information in master data to determine whether they exist and if they are consistent.

Productive Run (P):  When you choose execute run for a productive run, the system performs the following steps:

• Selects the employees and their payroll results for the evaluation.
• Creates a posting run.
• Creates posting documents.

1. Editing a posting run via Tcode PCP0.  This step provides an overview of all documents created during the posting run. Alternatively, we can also access the document overview from the create Posting Run log by choosing the Document Overview button or by double clicking on the Document creation line.  We can drill-down through these documents to identify the reasons for which errors have occurred for unsuccessful posting run (i.e., with an incorrect status)

Posting run status:

Initially, the posting run status should be Documents created.  If the status is No documents created and you were expecting documents, go back to the previous ‘create a posting run’ step and retry. If there are incorrect documents, review the error message and resolve.  Once error is resolved and status is ‘Document created’, select ‘Release Document’ Button and status will change to ‘All Documents Released’.  Next click on ‘Post documents button’, status will change to ‘Documents Posted’.

I. Relationship

     In International Payroll, as you may know, technical wage types are very important, such as: /801, /802, etc. These wage types contains factoring and will be multiplied with current values in wage types (inputted in PA30 Personnel Administration) and final results are employee's salary. In order to easier understand, let's see an example below: employee A has basic salary (wage type 1000) in IT0008 with value 1000$. And his salary is calculated by multiplying wage type 1000 with technical wage type /801. If he works full month, rate in /801 is 1, so he gets full basic salary 1000$. If he absences (unpaid or leave without pay), of course Rate in /801 is decreased (it's lower than 1), his salary is reduced as well.

     How are they processed in SAP HCM? Yes with 3 steps below:

1. Creating infotype involving salary (IT0008, IT0014, IT0015).

2. Time Evaluation

     2.1. Run daily and calculate how many working days or absence days (store in Time Type)

     2.2. When cut-off date comes, transferring value in Time Type into Time Wage Type.

3. Payroll:

     3.1. in sub-scheme XAL9 (Monthly factoring and storage (cumul.of gross amount) INTERNATIONAL), these technical wage type /801, /802, etc will be processed.

     3.2. multiply current value wage type in IF (0008, 0014, etc) with corresponding technical wage type (configured in processing class 10) /801, 802. etc.

     Finally, relationship is still TIME WAGE TYPE and process:

Time Evaluation run -> generate Time Type -> transferring to TIME WAGE TYPE -> Payroll run -> use TIME WAGE TYPE to calculate  Technical Wage Types.

     However, today I will not explain standard schema, I will share you solution to control your scheme by yourself to fit customer's complicated requirement. If you need understand standard schema, you can go inside schema and pressing F1 key .

II. Requirement

     In customer system there is an Absence Type - Sick Leave. Annually Sick Leave total will impact employee's salary as below:

     With this request, only option is modifying both Time Schema and Payroll Schema.

III. Solution

    As mentioned in first part, some steps need to be done:

     1. Create 1 time type to accumulate Sick Leave Yearly.

     2. Creating 4 time types to store how many Sick Leave in 16 -> 25; 26 -> 35; 36 -> 45 and above 45. We have to store into 4 different Time Types, because the percentage salary doesn't equal for all.

     3. On the cut-off date: moving values from 4 time types into 4 Time Wage Types.

    Cut-off date in current topic is EOM End Of Month, in Understanding Relationship PT and PY it's 25th monthly, so there is a little bit different between configuration and logic. I don't need to carry forward value from last period to current period, and clear accumulate value in Time Type as well.

     4. In payroll schema: the values in time types will modify Technical Wage Type /801, /802, etc.

     In scope of this document, only demonstrate customizing /801.

1.Time Type Accumulated Sick Leave Yearly

     Go to V_T555A with T-code SM30 / SM31 and configure as below:

     Active Cumulate in period balance and Transfer prev. period to store all Sick Leave in 1 year. Don't need to Transfer prev. year.

     Creating 1 PCR to accumulate Sick Leave:

     Absence Code of Sick Leave is 1020. Whenever data in TIP retrieved from Absence (Origin status is A) and Subtype is 1020 in internal table TIP, plus 1 into time type 9WSL. Thanks to configure in V_T555A, value in Time Type 9WSL will be accumulated in Function CUMBT. PCR ZW05 is inserted into Time Schema ZW04 as below (ZW04's copied from standard schema TM04): after successfully call function P2001.

2. Comparing Annual Sick Leave

     We have to check whether Accumulated Sick Leave with 15, 25, 35 and 45, as it effects employee's salary. Creating 4 constants in V_T511K

     4 Time Types to hold values whenever 9WSL > ZSLL1 (15):

     4 Time Types share the same configuration as below:

     Setup PCR ZW06 to check 9WSL and insert into schema after PCR ZW05

HRS=M9WSL  => Accumulated Sick Leave until the day before current day.

HRS+D9WSL  => plus value in current day (as accumulating only execute in Function CUMBT).

If (M9WSL + D9WSL) > ZSLL4 (45):

     value in current day 9WSL will be updated into Time Type 9W00.

If (M9WSL + D9WSL) > ZSLL3 (35) and (M9WSL + D9WSL) <= 45

     value in current day 9WSL will be updated into Time Type 9W25.

If (M9WSL + D9WSL) > ZSLL2 (25) and (M9WSL + D9WSL) <= 35

     value in current day 9WSL will be updated into Time Type 9W50.

If (M9WSL + D9WSL) > ZSLL1 (15) and (M9WSL + D9WSL) <= 25

     value in current day 9WSL will be updated into Time Type 9W75.

3. Transferring Time Type into TIME WAGE TYPE on cut-off date

     On the EOM (End Of Month), PCR ZW07 will be called to bring value in Time Types to TIME WAGE TYPE

     Time Type 9W75 => Time Wage Type 9050

     Time Type 9W50 => Time Wage Type 9055

     Time Type 9W25 => Time Wage Type 9060

     Time Type 9W00 => Time Wage Type 9065.

     And merge ZW07 into Schema ZW04  as below:

     These are all steps in Time Schema. As you can see, after running Time Evaluation, 4 wage types 9050, 9055, 9060 and 9065 contain sick leave days in current period, how many sick leave days in 16 -> 25, 26-> 35, 36 -> 45 and above 45.

4. Modify Technical Wage Type /801 in Payroll

     Copy standard sub-schema XAL9 into ZALW with 2 new PCRs ZK08 and ZW14:

     First we have to change Number in Time Wage Type  9050 Sick Leave 75%, 9055 Sick Leave 50%, 9060 Sick Leave 25% because they are not deduction full. Only Time Wage Type 9065 is kept current value. It's executed in ZK08:

     Current value in 9050, 9055 and 9060 will be multiplied with corresponding Rates:

Finally, calculation technical wage type /801 in PCR ZW14

III. Testing

     Hiring employee with basic salary is 1000$ per month.

     Configure Wage Type 1000 with processing class 10 in V_512W_D:

     In Apr-2012, employee took 22 Sick Leave Absence days:

   And his salary was correct as picture below:

In Jul-2012, he requested 23 Sick Leave Absence

And Salary in Jul-2012 was exactly:

In the document, I have shared you how to control Time and Payroll as well. There are a lot of difficult requests in fact, so understanding deeply Time  and Payroll schema is very important. If you investigate the topic carefully, you will be control schema by yourself soon and not scare touching schema anymore

Hope it helps!

Regards!

Woody

Why you should attend this seminar:

In early 2012 SAP acquired the SaaS HCM software vendor SuccessFactors to complement the existing on-premise HCM Suite. AS a result, SAP now offers a full HCM suite both on-premise and in the Cloud. Join this interactive seminar with Luke Marson, SAP Mentor and co-author of the SAP Press title "SuccessFactors with SAP HCM", in order to better understand what SuccessFactors is, how it fits into SAP's long-term HCM strategy, and what the impact is for customers of SAP.

Agenda Day 1

·         What is & who are SuccessFactors?

·         The acquisition by SAP

·         SAP’s Cloud & HCM strategies

·         Implementation Practices

·         Integration

·         Technical overview

Agenda Day 2

·         Employee Central

·         Cloud Payroll

·         Business Execution (BizX) Suite

·         Workforce Analytics

·         SAP’s Product Roadmap for SuccessFactors

Please book directly here:

https://training.sap.com/ch/de/courses-and-curricula/prof
or
http://www.sap.com/swiss/services/education/professional-seminars/index.epx

     One day, your customer called you come to his seat and said to you - a functional consultant - that: employee worked only 1.99 extra hours, why the guy received allowance for Over Time, or currently they has only 3 rules for extra working hours, new policies would like to add 2 more rule and new Rate when paying allowance:

     What should you do? SAP HCM module is very huge, you don't have enough time to touch every thing inside. So you couldn't know anything. You need the way or tip or experience to help you correctly approach customer's expectation at soonest, both business side and in SAP HCM side.

     Today I would like to share you a tip to resolve these issues or requests involving wage type in Payroll.

First of all, these steps below must be done as soon as possible

1. You need to know: which Payroll Schema and Time Scheme using in your customer's system. It's very easy, isn't it. Through documents written by who set-upped system. (some case you can ask key users who are very clear enterprise's businesses and processes).

2. Extracting very detail both Payroll and Time Schema. Using standard program RPDASC00 to expand clearly schemas.

As you can see here, all schema, sub-schema and PCRs have been extracted into only 1 excel file.

3. Preparing for yourself with knowledge in schema. You can using F1 key or go-to T-code PDSY to investigate logic Functions and Operations in Time and Payroll Schema, or looking for through internet. Deeply understand overview processes and logic (Functions, operations and PCR) is very important for a SAP HCM functional consultant.

Secondly, these steps should be followed.

1. Mapping issue / request with exactly wage types. You can contact with key user to know the Wage Type Codes. They will support you and confirm how wage type's descriptions.

2. You already had extract Payroll Schema in excel file. Simply using Ctrl + F to looking for these wage type (9031, 9032, 9033) in all sheets. Thanks to a common tool, you can find corresponding Constants (maintaining in V_T511K or V_T511P):

of-course you can know which PCRs to generate these wage type in Payroll Schema. Now you just simply edit these constant, the request for changing current rules will be done

3. For any changing in Time, you just look for in Time Schema (The Time Schema file that you created by using program RPDASC00). You know, the relationship between Time Evaluation and Payroll is Time Wage Type. You can re-use wage types above ( 9031, 9032, 9033) to find these corresponding Time Type ).

Thanks for getting these Time Types, you can find the PCRs as well. From here, you can know how to calculate: Working hours in Holidays & Weekly Offs, Week Days & Holidays Extra Shift and Week Days, and then modifying up to you

Finally, you can know how current businesses are and you can start to correct or implement The tip here is very simple: looking for from the bottom to up: with key points are Wage Types and documents prepared by RPDASC00.

Hope it helps!

LIST OF INFOTYPES USED IN SAP HCM (OM)

Prepared By : RG NAWIN KRISHNA,

SAP CERTIFIED ASSOCIATE

Table: T778T

IType      Infotype text

1000           Object

1001           Relationships

1002           Description

1003           Department/Staff

1004           Character

1005           Planned Compensation

1006           Restrictions

1007           Vacancy

1008           Acct. Assignment Features

1009           Health Examinations

1010           Authorities/Resources

1011           Work Schedule

1013           Employee Group/Subgroup

1014           Obsolete

1015           Cost Planning

1016           Standard Profiles

1017           PD Profiles

1018           Cost Distribution

1019           Quota planning

1021           Prices

1023           Availability Indicators

1024           Capacity

1025           Deprec. Meter/Validity

1026           Course Info

1027           Site-Dependent Info

1028           Address

1029           Course Type Info

1030           Procedure

1031           Room Reservations Info

1032           Mail Address

1033           Scale

1034           Name Format

1035           Schedule

1036           Costs

1037           Billing/Allocation Info

1038           External Key

1039           Shift Group

1040           NICHT MEHR VERWENDEN

1041           Course Blocks

1042           Schedule Model

1043           Appraisal Model Info

1044           Result Definition

1045           Rating

1046           Requirements Attributes

1047           Processing Modules

1048           Proficiency Description

1049           Requirements Attributes

1050           Job Evaluation Results

1051           Survey Results

1055           Qualification Management

1060           Course Demand

1061           Web Link

1062           Knowledge Link

1063           Course Group Info

1070           Application area

1071

1072

1201           WF Object Method

1205           WF Workflow Definition

1206           WF Work Item Text

1207           Customer Task,replaces TS

1208           SAP Organizational Object

1209           Cost Data

1210           WF Container Definition

1211           WF Container Texts

1212           WF Event Binding

1213           WF Role Binding

1214           WF Other Binding

1216           Function Area Assigned

1217           Classification/Lock Ind.

1218           WF Def. Responsibility

1220           Activity Profiles

1221           Excluded Activities

1222           General Attribute Maint.

1240           Existence Dependency

1250           Prof.Gen.: Authorizations

1251           Prof.Gen.: Specifications

1252           Profile Gen.: Org. Levels

1253           Profile Gen.: Variants

1254           User Variables/Activ.Grps

1260           CIC Profile

1261           IC Web Client Profil

1270           CO Group assignment

1271           Composite Survey Result

1291           EIC: Support Level

1403           Exposure: LTA

1404           Exposure: Task

1500           BS element management

1501           Pay Scale Valuation

1502           Allowance Valuation

1503           Service Type/Category

1504           Budget Updates

1505           Budget.Rule(Obsolete1509)

1506           Reclassification rule

1507           Teaching Hours

1509           Budgeting Rule (PBC)

1511           Alternative Valuations

1512           Job Index Attributes

1513           Job Index

1514           Valuation Additional Data

1515           Monitoring of Tasks

1516           Funding Status

1517           Excel Communication

1518           Assignment FM Designation

1519           Integration FM

1520           Original Budget

1600           Organizer ID (F)

1601           Statutory Specifications

1610           US Job Attributes

1612           WC State and Code

1613           WC State, Code, Attribute

1620           Job Attributes (D)

1630           NQF Unit standard

1631           NQF Qualifications

1632           NQF Outcomes

1633           Equity Attributes (ZA)

1640           Special Labour Conditions

1641           WC Attributes for JOB

1650           Grade (FR)

1651           Grades (BE)

1652           Occupational Categories

1653           Retirement Age

1654

1660

1661

1670

1671

1675           Nature of Object

1680           Status

1681           Regulatory Compliance

1682           Administrative Data

1683           Budget

1684           Invoice

1685           General Attributes

1686           Absence/Attendance

1687           No-Inheritance Data

1690

1800           Industry

1801           Account Assignment

1802           Relevance

1803           Roles

1804           Details

1805           Control Objective Categ.

1806           Details

1810           Control Type

1811           Settings: Process

1812           Settings: Process Group

1813           Settings: Org Unit

1814           Tester

1815           Settings: Local Mgmt Ctrl

1816           FS Assertion

1817           Account Grp: Significance

1818           Threshold Value

1819           Transaction Type

1820           Project Scope

1821           Qualitative Risk Impact

1822           Chart of Accounts

1823           Change Documentation

1824           AIS Reports

1840

1841

1842

1850           Risk catalog group

1851           Activity catalog group

1852           Activity Master

1853           Common activity group

1854

1880           Equipment

1881           Type of Instruction

1882           Description

1883           Test

1884           Check

1885           Didactic Schedule

1886           Grading Rule

1887           Days Without Instruction

1888           Test Defaults

1889           Accessible

1950           Force Properties

1951           Force Readiness

1952           Deployment

1953           Range of Services

1954           Service Provider

1955           Subordination Relatnshps

1956           Operation/Exercise

1957           Obsolete: Do Not Use

1958           Spec. Position Chars

1959           Command & Control Support

1960           Joint Venture Partner

1961           Additional attributes

1980           Relocation

1981           Material Relocation Assi

1982           Personnel Relocation Assi

1983           Spec. Job Chars

1984           Logical System

1985           Operation/Exercise Relatn

1986           Structure Information

1990           NATO Information

3000           PPC Basic Data

3001           PPC Hierarchy Allocation

3003           PPC Default Values

3005           PPC Scheduling Data

3006           PPC Capacity Assignment

3007           PPC Technology Data

5003           Course Content Static

5004           Curriculum Type Info

5006           Course Type Content

5007           Delivery Method

5008           Completion Specifications

5009           Course Content

5010           Planning of Pers. Costs

5020           Category Assignment

5021           Layout Definition

5022           Column/Cell Definition

5023           Column Access

5024           Role Assignment

5025           Processing

5026           Status Switch

5030           Expert Basic Data

5031           Profile Type, Search Scen

5032           Qualification Export EF

5041           Workflow Settings

5042           Ext. Catalog Connection

5043           Ext. Training Provider

5044           Learning Portal Control

5045           Collaboration Room

5046           Collab. Room Template

5047           Follow-Up Control Options

5048           Corr. Control Options

5049           Versioning Options

5050           Compensation Job Attrib.

5070           Job Family

5102           Candidate Information

5103           Work Experience

5104           Education

5105           Qualifications

5106           Desired Employment

5107           Desired Work Location

5108           Availability

5110           Contact Rule

5111           Licenses/Certificates

5112           Consulting Activities

5115           Talent Group Information

5121           Posting Information

5122           Posting Instance

5125           Requisition Information

5126           Job Description

5127           Further Requirements

5128           Education Requirements

5129           Qualifications Fulfilled

5130           Licenses/Certs Awarded

5131           Persons Responsible

5132           Application Information

5133           Candidacy Information

5134           Attachments

5135           Manual Activities

5136           Correspondence

5137           Qualifying Event

5138           Invitation

5139           Status Change

5140           Data Transfer

5141           Questionnaire

5142           Appraisal

5143           Confirmation

5144           Background Check

5145           Parsing

5151           Support Group Information

5152           Group Members

5580           HR Master Record (0000)

5581           Org. Assignment (0001)

5582           Personal Data (0002)

5583           Address (0006)

5584           Bank Details (0009)

5585           Communication (0105)

5586           Relationships (5586)

5587           CATS: Sender Information

6070           WFM Extended Data

6200           Planned Operations

I. Purpose

     More deeply understand Time Schema, this document will guide you how to check early/ late coming and generate Overtime by configuration in T555Z.

II. Solution

     1. Checking early/ late coming

          First, you have to get Start Working Time in Planned Working Time (IF0007) of employee. Creating PCR ZSWT

              HRS=SNTB     Start of normal working hours => Time type 9000 will hold this value - Start Working Time of employee.

          After having start working time, comparing it with first check in (clock in) as in PCR ZE&L

              HRS=PBEG it's the first check in.

              HRS-D9000 minus first check in with start working time holded in Time Type 9000

              HRS?0 comparing with 0.

                    Who comes early, Time Type 9002 (Early coming) will be updated.

                    Otherwise, Time Type 9003 (Late coming) will be updated.

     Now merging 2 new PCRs into Time Schema ZM00 (it's copied from standard Time Schema TM00).

2. Generation Overtime

     In the Time Type Determination view (V_T555Z), you define which time types and processing types the

          TIP entries are assigned, based on the time identifier and the pair type:

          Pair type 0: Unrecorded times

          Pair type 1: Attendances from time postings and planned pairs

          Pair type 2: Absences (infotype 2001)

          Pair type 3: Attendances (infotype 2002) and off-site work postings

        Calculation Overtime bases on Clock in / out, so you have to configure with Pair type 1

     In order to understand, look at processing in Time Schema with Function TIMTP (Assign time type to time pair)

          Inputting:

               Planned Working Time: 09:00 - 17:00 (Break from 13:00 - 14:00)

               Time Events: clock in on 08:00 and clock out on 19:00

          After processing with TIMTP (basing configuration on T555Z), results are:

     How it processes? because the meaning of all ID in T555Z (from 01 to 09)

   01 = Overtime, unapproved (outside of planned working time)

   02 = Fill time (during planned working time, without core times)

   03 = Core time

   04 = Core time break

   05 = Fill time break

   06 = Paid break

   07 = Unpaid overtime break (infotype 2005)

   08 = Paid overtime break (infotype 2005)

   09 = Overtime break

          => from 08:00 to 09:00 (before start working time, ID's 01), 1 hour Overtime will be assigned into Time Type 0310

          => from 09:00 to 13:00 (working time, ID's 02), from 14:00 to 17:30 (working time, ID's 02), insert into Time Type 0110

          => from 13:00 to 14:00 (break time, ID's 05), Time Type 0510 will be updated.

          => from 17:30 to 19:00 (after end working time, ID's 01), 1.5 hours Overtime for Time Type 0310.

III. Testing

     One employee has working time from 01st-Jan-13 to 06th-Jan-13 as below (note 01-Jan-13 is Holiday)

     Actual working time:

     These are reports after running Time Schema.

     Report for early/ late coming (01 Jan is Holiday and 06 Jan is Sun, not calculate on these days)

          Employee came Early on 02-Jan and 05-Jan and Late on 03-Jan and 04-Jan. It's exactly.

     Report for Overtime:

          Overtime on 01 Jan and 06-Jan are full days as 2 days are Holiday and Sunday - no working time. Overtime on 02-Jan and 05-Jan are correctly as well.

Hope you have more knowledge and tobe clear time schema and configuration in T555Z

Unlike other modules data processing in SAP , HR module data processing is little bit different. Here the resultant data will be stroed in Clusters , which we can not access directly with normal select satments . One have to use the SAP provided methods only for data accessing. So I thaught the below program will help a little for HR ABAPers who are learning now.

Below is the program to retrieve an employee's last run payroll results. For this program I used PNP LDB .

PROGRAM:-

And the Final output will be like as below.

Regards,

Praveen Chitturi.

Step 1:

• Personnel Development is integrated with Personnel Administration

SM30>>TABLE >>T77S0 >> PLOGI APPRA “ 1 A032 Q”

Step 2:

               Spro>>PM>>PD>>Appraisal System>> Edit Form of Appraisal

Step 3:

Create  Appraisal Model T-Code:00AM

Here You give the name to your Appraisal Model either This is for Employee Appraisal or Applicant Appraisal you will chose the form of Appraisal which you defined in step 2: here

If it is employee Appraisal you will also chose either Individual Appraisal or 360 degree Appraisal etc.

Step:4   

Now prepare the Appraisal Model According to the Requirement .

1. Criteria Group :
2. Criterion:

Click on Appraisal Model And Press New Button. The Below Widow will Appear Give the name of your Criteria Group e.g Section A and Also Select the result tab to insert the method of calculation you want to create .press F1 if required any Assistance.

Step 5: chose scale for Criteria group.

Step :6   Set Scale for Criterion Group  by pressing Result Tab.

Step:7 T-Code  :Appcreate 

Here you can choose the appraisal model according to the requirement .

Step 8:Appraisal Form is Like this which you designed in Step 3 to Step 6:

Fill the supervisor who is the Appraiser

And employee who is going to be Appraised

Press f8 and fill out the form with ratings  this date than save the data 

Step 9:

Integration switch is on you can see the appraisal form of all employees who appraised by the specific supervisor by going pa30 supervior personnel id no:xxxxxxxxx and chose infotype 0025.

All completed in preparation and in process Appraisal will be shown here you can edit it if the status is not completed.

I just spent couple of hours banging my head against the wall with this one. The requirement was clear. If the A002 relation for an existing position is changed, I should trigger a workflow and send out a notification. Easy, right? I ended up searching SCN and I was surprised to see that there are many discussions on the topic and no solutions.

What you will need to do is go to SWEHR1 and enter the configuration for S-1001-A002.

Next you will have to go to SWEHR3 and enter the configuration for S-1001-A002. Notice however that the action type is not UPD, it is DEL + INS. This is the tricky part! You can configure until pigs fly but UPD won't get you anywhere.

Copy the template function module HR_EVENT_OT_NNNN_UUUU_TEMPLATE to create your own function module.

I calculate payroll and the system creates WPBP split up No. 3. When I check RT table WT/101 total gross is different basic salary 0.01 which it's not correct.  Please kindly suggestion me to solve this problem.

Example

Basic salary     WT1000      26,170

Table WPBP

No     From - To

01     01.11.2012 - 10.11.2012 

02     11.11.2012 - 11.11.2012

03     12.11.2012 - 30.11.2012

Table RT

WT1000     01          7,223.33

WT1000     02          722.33

WT1000     03          13,724.33

Total WT/101 Total Gross 21.669.99

I checked display log simulate payroll, when at rule XVAL it's generate not correct.

Thanks you so much for advice me for solve this problem.

Best Regard,

Chotirod S.

USEFUL FUNCTION MODULE IN HR ABAP :-

I will keep updating this FM document for better result.

Regards,

Praveen Chitturi.

He has used LSMW in multiple implementation/rollout projects,but never has he came across this debug option in LSMW.Infact he learnt it recently and he takes joy in sharing this with others.

no worries

kg

Valuation of wage types is done in two ways either using constant remuneration (wage type dependent constant or pay scale dependent constant) or using person related remuneration. In other words, valuation of time wage types in payroll i.e., processing of overtime for different working hours in payroll. 

The wage types initially contain the number of hours of overtime that the employee has worked. This figure is specified in the number field (NUM) to be multiplied by a payable amount.

Valuation of wage types using wage type dependent constant and standard modifier:  This involves three steps viz.,

1.  Creation of time wage type that carries the no. of hours in the number field (NUM) maintained via Info type Employee Remuneration Information (2010).  For example creation of wage type 2221 Bad Weather Bonus using country grouping 99 (International) by copying wage type 2000

i.  Go to Tcode OH11 or SPRO--IMG--PM--PA--Payroll data---Employee Remuneration Information---Wage types--- Click on Create Wage type catalog as follows

Uncheck test run and click on Copy.

ii.  Go to next node Check wage type group Employee Remuneration Information to check if the wage type 2221 is present i.e., in table V_T52D7.

iii.  Check wage type Catalog:

     a. Check wage type text (V_512W_T)

     b. Check entry permissibility per infotype (V_T512Z)

     c. Determine wage type permissibility for each PS and ESG (V_511_B).  Then accordingly group either Employee Sub groups or Personnel Sub area groupings.

     d. wage type characteristics (V_T511):  Check the wage type characteristics as follows:

This done, now the next step is to create valuation bases.

2. Using the standard modifier 01 in table V_T510J (Constant Valuations) to give amount (Say 10 Euros) with which the No. of hours contained in wage type 2000 will be multiplied.

SPRO---IMG---Payroll---International---Time wage type valuation---Valuation bases---Constant Valuation Bases---Click on Wage type Dependent Constants..

and choose Determine Constant Valuation per wage type from the Activity box...and click on new entries and maintain as follows

3. Assigning valuation bases in table V_512W_B (Valuation bases) as K for the same wage type 2000 where K is an indicator for valuation with a constant amount from Constant Valuation table V_T510J.

Now maintain the infotype  2010 ( Employee Remuneration Info) for wage type 2221 with 10 hrs as follows

Now run Payroll for the relevant period and open the payroll log to  see the valuation as follows:

Valuation of wage type using wage type dependent constant can also be done using Modifiers for table access based on organizational assignment as shown below.  That is here we would see a how a time wage type is valuated based on wage type dependent constant if an employee belongs to a particular Personnel Area ( Say CABB here ).

1. As usual creation of time wage type (2221) that carries number of hours maintained through Infotype 2010 ( Employee Remuneration Information)

i. Go to SPRO---IMG---Personnel Management---Personnel Administration---Payroll Data---Employee Remuneration Informatin---wage types---Click on Create wage type catalog and copy wage type 2000 for Country grouping 99 to wage type 2221 as follows:

ii. Now, click on next node, check wage type group 'Employee Remuneration Information' (Table V_T52D7) and check if the wage type is present.

iii. Then click on Check Wage type Catalog---

• Check wage text( Table V_512W_T)--Here we change the text of the wage type if need be as per our custom requirement.

• Check check entry permissibility per infotype ( Table V_T512Z ) as follows:

• Check wage type permissibility for each PS and ESG (Table V_511_B)

• Check wage type characteristics (Table V_T511)

2. Copying the Standard Personnel Calculation Rule XMOD and modifying it (ZM12 here) to include the Personnel Area CABB and then copying the Standard modifier 01 and renaming it as custom modifier and entering the relevant amount to be used to valuate the wage type 2221 as in the screen-shot below. Besided, include the custom PCR in the Schema.

SPRO---IMG--Payroll---Payroll International---Time wage type valuation---valuation bases---constant valuation bases---click on define wage type dependent constant

Select set modifier for constant valuation in the activity box and copy and modify the standard PCR as follows

And insert custom PCR ZM12 into custom  Sub-schema( ZMKT here) copied from Standard Sub schema XT00 as below...

Finally insert the custom sub schema into the custom schema (M000) copied from Standard Schema X000 as under:

Now select Determine Constant Valuation per Wage type (Table V_T510J) and give the amount with which the wage type 2221 is to be valuated as below:

3. Assignment of valuation bases in table V_512W_B.

4. Maintain Infotype 2010 (Employee Remuneration Information) via PA 30 for an employee of Personnel Area CABB as follows:

5. Now run Payroll for the relevant period for the employee using the custom schema and see the result in the payroll log:

Open time data processing sub-schema and go to PIT X015 GEN (Valuation of time wage types) and see IT in the OUTPUT node as follows

Double click on IT table to see the below result: