SAP HR Defining Base Enterprise Structure

GENERAL INFORMATION

In the SAP System, the company’s 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 Company’s 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.

1. Client : an independent legal and organizational unit of the system
2. Company Code : An independent company with its own accounting unit;a company that draws its own balance sheet
3. Personnel Area : A specific entity for Personnel Administration; a sub division of the company code
4. Personnel SubArea : A sub division of the personnel Area

Following is a more detailed of each enterprise structure value.

Tarif Baru Pajak Penghasilan

Wahyu Daniel – detikFinance Selasa, 2 Sept 2008

Undang-undang pajak penghasilan yang baru kini sudah disahkan oleh DPR. Beberapa tarif pajak dipotong sehingga diperkirakan potensial lost pajaknya mencapai Rp 40 triliun. Wajib pajak yang tak ber-NPWP akan dikenakan pajak yang lebih tinggi.

Berikut pokok-pokok pikiran dalam UU Pajak Penghasilan (PPh) yang baru disahkan oleh DPR, di gedung DPR, Senayan, Jakarta, Selasa (2/9/2008).

SAP PY-ID How to Determine Projection Factor /402 in Payroll Result

As we all may know that WT /402 (Projection Factor) are positioning a very critical in the SAP Indonesia Payroll processing. Especially in calculation of the Income tax (Article 21 – Income Tax). Incorrect understanding about the wage type will lead to the incorrect of overall Income Tax calculation

Definitions

This wage type is actually used for projecting/annualized the total income in yearly basis. The formulas could be found at PCR IDN3 (Setup Projection Factor for Tax Calculation) in sub Pay Schema IDN0. Generally, the PCR can be read as below:

SAP Time Constraint in HR Infotypes

Time Constraint Value

1 = Record must have no gaps, no overlappings
2 = Record may include gaps, no overlappings
3 = Record may include gaps, can exist more than once
A = Infotype exists just once from Jan.1 1800 to Dec.12 9999
B = IT exists for maximum of once from Jan.1 1800 to Dec.12 9999
T = Time constraint is based on subtype or subtype table
Z = Time constraint for time management infotypes -> T554Y

Time Constraint Definition
A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:

1 = An infotype record must be available at all times. This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.
2 = Only one record may be available at one time, but time gaps are permitted.
3 = Any number of records may be valid at one time, and time gaps are permitted.

Other possible time constraint indicators are as follows:

A = Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
View V_T582B Infotypes Which are Created Automically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action.
Infotypes with time constraintA may not be deleted.

B = Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
Infotypes with time constraint B may be deleted.

T = The time constraint varies depending on the subtype.
Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y Time Constraint Reaction.

SAP PY-ID:Off-Cycle Payroll in the beginning of Tax Year (2)

A question from Suguna and the answer (Link: Initial Issues)

Dear Harry
“By referring to the issue, the end result will be a small amount of Tax deduction (pph21) in off-cycle pay result while then the rest would be brought forward into the next Regular Pay Run, in the same period, to recalculate the actual Tax deduction. The affect is that the employee salary in the next regular pay run could be less and/or becoming negative cause by the tax deduction.”

The above also happens in other situations such as this one below.

We have run regular payroll in 20th May, and we follow that with an off-cycle (Bonus) in May 26th. The employee has a transfer action on 1st May.

In this case, the tax is small in off-cycle pay result, while then the rest is eventually recovered in the following periods. In this case the employee is transferred for the 1st of the month. The Off-cycle is not in January, but in May.

Have you come across this type of situation.
Will SAP solve this issue, do you know.

And the Answer

Hi Suguna,
In what payroll country you’re dealing with?Me, for Indonesian Payroll (PY-ID).
In PY-ID, because Indonesia is using annualized method in their income tax calculation (PPh21) then actually there’re some factors that SAP use to calculate the income tax.

SAP TClass – The Definition

• TCLAS=A –>Transaction Class for Personnel Administration
• TCLAS=B–>Transaction class for Recruitment

This transaction class sometimes has confused us as functional consultants. We just need to understand that whenever you write a dynamic action, if you are writing one for PA infotypes that use TCLAS=A and if for Recruitment use TCLAS= B before you begin writing the code for the dynamic action. Let us compare the Personnel Administration infotypes and Recruitment Infotypes.

• Personnel Administration
• IT0000 – Personnel Actions
• IT0001- Organizational Assignment
• IT0002-Personal Data…and so on

• Recruitment
• IT4000- Applicant Actions
• IT0001- Organizational Assignment
• IT0002-Personal Data.. and so no

SAP HR Features (PE03)

Features are objects those that default values by quering different enterprise, personnel or data structure fields. The transaction code for features are pe03.

These below are the features to default and in which info type deal affected to:

1. Work Schedule Rule SCHKZ- IT0007
2. Pay Scale Data TARIF-IT0008
3. Wage Type Model LGMST-IT0008
4. Administrator groups PINCH-IT0001
5. Number Range Intervals NUMKR

SAP HR Infotypes

Infotypes are also called information types and are pre-defined templates to enter sensible related information for an employee or applicant. for eg an address infotype would have fields like street & house no, city, pin code.This infotype is unique and is represented by an infotype number eg address has infotype no 0006. There other infotypes like

1. 0000 – Actions (to capture employee movement info in the orgnization)
2. 0001 – Organizational Assignment (to capture employee positioning in the organization)
3. 0002 – Personal Data
4. 0006 – Address
5. 0007 – Planned Working Time (Store planned working hours for the employee.)
6. 0008 – Basic Salary
7. 0009 – Bank Details
8. 0014 – Recurring Payment
9. 0015 – Additional payment
10. 0016 – Contract Elements
11. 2006 – Absence Quotas

The above infotypes together in the same sequence form a part of the Hiring Action.To make you understand this better just try and recollect the contents of your offer letter which your organization might have given you. It would possibly read “We are delighted to offer you the position (IT 0001) of ______. You will belong to ______ department (IT 0001). Your joining date will be ______(IT0000 or IT0041)and you will be paid a salary of ______ (IT 0008). You will be paid monthly allowances ______ (IT 0008 or IT 0014) and we are also offering you a joining bonus of ______ (IT 0015). You will be eligible for annual leave of ______ days (IT 2006) and sick leave of ______ (IT 2006).You will be on a probation for six months from the date of joining (probation date & confirmation date in IT0016). Your working hours will be from ____ hrs to ____ hrs beginning Monday to Friday (IT 0007) and we look forward to your presence on date ______(IT 0016)……

I hope this gives you some idea of what an infotype is.

SAP HR Introduction

SAP HR or SAP Human Resource is one of the largest modules in the SAP R/3 system which consists of many submodules like

1. Organizational Management
2. Personnel Administration
3. Recruitment
4. Time Management
5. Payroll
6. Benefits
7. Compensation Management
8. Personnel Cost Planning
9. Budget Management
10. Personnel Development
11. Training & Event Management
12. Travel Management
13. Environmental Health & Safety (under the SAP HR node in SAP Easy Access)

SAP PY-ID: Issue in defining Payroll Currency through the Enterprise Structure

I’ve found another tail story of SAP bugs by accident a few days ago. Lucky me, although it’s quite paint full to trouble shoot the mistakes. It was relating to the processes in defining HR Enterprise Structure, but lead to the incorrect currency in term of payroll results. In my SAP environment, we’ve been defining some numbers of country grouping in one box, that is used by different company code, personnel area and sub areas in their enterprise structure. On top of any HR configuration, it is country group configuration at SAP global setting that becomes as the initial Default Payroll Currency definition.

Furtherly, there’re several ways to be chosen in defining Default Payroll currency at HR module, as explained as follows:

1. The definition of SAP Enterprise Structure.

• IMG : Global Setting : Country Definition (in here we can define what the default currency for the country ID)
• Enterprise Structure -> Definition -> Finance -> edit,copy,delete company code (in here we can define what the default currency for the company code)
• Enterprise Structure -> Definition -> HR -> Create personnel area and sub area (that is need to be linked with its company code)
  
• Enterprise Structure -> Assignment -> HR -> Assignment personnel area to company code (that is also need to be linked with its personnel area)

 

2. Through, Personnel Management module in HR IMG path. By defining pay scale type/area, employee sub group grouping and CAP (Collective Agreement and Provision)

SAP has the capability in using multiple payroll currency, but from what I understand so far, it is only possible to define that case only by using step 2, other than defining through the enterprise structure configuration that will may lead us to the inconsistencies configuration. Below illustration will explain the inconsistencies in more detail.