Hr tables, transaction codes, info types, Features

Organization management
SPRO: semi program run way operations
SBWP work bench, internal mailing in sap
RHCOPLPT to compare the different plan
RHCOPL00 to copy the plans from one pv to another pv
RHCOPY00 to copy the objects with in the plan version
RHCOPY10 to copy the list of objects
RHCOPYSTRUCT to copy the structure
RHAKT100 to change the status
PSO0
to set current plan version
Maintain num ranges
OONR
Set up num assignment to PV OONC
Create plan version
OOPV
Set active p version
OOAP
Maintain objects
OOOT
Maintain essential relation relations for objects OOPS
T77S0
Maintain intps
OOIT
Maintain subtypes for itps
OOSU
Create evaluation path
OOAW
Maintain relationships
OOVK
Org units
T527X
Positions
T528B, T528T
Jobs
T513, T513S
OM info type creation - for structure -SE11
for inftp - PPCI
to create d new status _
T778S but it is not suggested.
Table reports, for data browser - SE11, SE16 (we use se16)
Abap dictionary - SE11
Creating package - SE80 abap ers creates this to store the data (it is used like transport request).it
is used to store the structure when we r creating inftp.
Relationships:
A direct
002
reports to
003
belongs to
004
subordinate to
005
is subordinate to
007
describes
008
holder
009
successor
010
substitute

B indirect
is line supervisor of
incorporates
is disc supervisor of
is supervisor of
is described by
holder
successor
substitute

011
012
013
014
015
017
031
035
083
088
250
700
290
204
262

cost center assignment

manages
staffing requirement
cost distribution
is identical to
is carried out
require s
is previous job of
is key position of
dotted line reports to
is responsible for
ii
has administrator
possible roles
reports to

cost center assignment

is managed by
staffing requirement
cost distribution
is identical to
carries out
is required
is subsequent job of
incorporates key position
dotted line supervisor
is responsibility of
ii
is administrator for
possible roles
is superior of

Info types:
1000
1001
1002
1003
1004
1006
1007
1008
1010
1011
1013
1014
1015
1016
1017
1018
1019
1028

object
relationship
description
dept and staff
character
restrictions
vacancy
account assignment
authorities
work schedules
emp grp and emp sub grp
obsolete
cost planning
standard profile
Pd profile info type
cost distribution
quota planning
address

RHINTE00
RHINTE10
RHINTE20
RHINTE30

PA to PD
OM with PA
OM with PA missing objects
assignment in the batch input folder in 0001

Other tables:
Time constraint for tmV_T554Y_B (other time constraint classes)
SE38 for tools for running the reports.
Delete personnel data PU00
Wage type copier
PU30, OH11
Change payroll status
PU03
Pay grade for planned compensation v_ t710cl
Salary structure, pay grades
v_t710cl_b
Const indirect valuation of wage types t510k
Om info type data table
HRPNNNN where NNNN is OM info type num
PA info type table for data
PANNNN where NNNN is PA info type number
Transport request
SE09, SE10
Down load requests
STMS.

Enterprise structure
Technical names:
MOLGA
country code
BUKRS
company code
WERKS
personnel area
BTRTL
personnel sub area
PERSG
employee group
PERSK
employee sub group
MASSN
action type
MASSG
reason for action
PERNR
personnel number
ORGEH
organization unit
Define company:
Define company code:
Assign company code to company:
Define personnel area:
Cerate per sub area:
Define EMP grp:
Define EMP sub grp:
Assign per area to company code
Assign EMP grp with EMP sub grp

v_t880
v_t001
v_001_Y
t500p
v_t001p
t501
t503k
t500p
v_t503z

Employee sub group grouping

Personnel sub area group groping

V_503_alll
V_001p_all

Personnel Administration
Info types:
These info types are common for all countries. Apart from these some countries will have some
other info types. Fields of the info types which can b configured by us given below. These all are
the part of the PA.
0000 actions
0001 org assignment
0002 personal details
0003 pay roll status
0006 address
0007 plan working time feature for time status is TISTA
0008 basic pay
0009 bank details we configure a) type of bank, b) pay mode .FBZP
We enter the info about bank where the employee salary is credited. Mode of pay, bank details.
This info type has sub types 1 main bank 2 other bank (loans) 3 travel bank details DTAEL,
ZLSCH are the features
0016 contract elements.
0019 monitoring of task
0021 family members
0022 education
0023 previous employers
0024 skills and qualifications and preferences
0025 performance appraisal
0031 reference personnel number
0121 reference personnel number priority
0041 date specifications. Dates - V_T548Y, feature to default dates DATAR
0077 additional personal data. (Us specific)
0094 residence status. (US specific)
0105 communication
0185 personal ids. India
For UK 0069, 0070, 0032

FEATURES
NUMKR
ABKRS
PINCH
VDSK1
SCHKZ
TISTA
WWEEK
LGMST
TARIF
ANSAL
DTAEL
ZLSCH
MODDE
PFREQ
CONTR
DATAR

; to default the number range

; to default the pay roll area
0001
; to default the administrators in 0001
: organization key in 0001
; to default the work schedule rule in 0007
; to default the time management status in 0007
: to default working week in 0007
; to default the wage types in basic pay 0008
; to default the pay scale data in 0008
; to default the annual salary in0008
; admissibility for bank transfer for 0009. To show d error msg according to
Eligibility condition. X/yy/nnn/zzz. FBZP is tc for payment mode
; to default the payment method in 0009
: to default the payment model in 0014
: to maintain the payment frequency
: contract elements periods 0016
; to default the date s in 0041

Tables in PA
Actions- add required info types info grpSet up personnel actions
Dynamic actions
Screen modifications

V_T588d
T529a
T588z
T588m

Time management
Info types:
0007 plan working time
0050 Time recording info Absences
0416 quota compensation
2001 absences
2002 Attendances
2003 Substitutions
2004 Availability
2005 Overtime
2006 Absence quota
2007 Attendance quota
2010 Employee remuneration info
2011 Time events
2012 Time transfer specs
2013 Quota correction

Employee sub group groupings: For time quota types, for work schedules and for PCRs
Personnel sub area group grouping:

for attendance and absences.

For time quota types
for work schedules
For daily work schedules
For substitution and availability types
For attendance/absence counting
For time recording
For premiums

Employee grouping for time evaluation:

For time wage type selection

For time type determination
For dynamic daily work schedule assignment
For checking value limits
For automatic absence quota accrual

Time Management-related employee groupings for Payroll: For absence valuation

Process type: Indicator for time evaluation and time data processing in Payroll that controls the
selection of wage types. The processing type is formed during time evaluation.
Ex: - M,S,A,P..

Internal Tables for time data processing:

TIP

daily input table. The time pairs that have been recorded using info types or generated in
pair formation are entered in the internal work table TIP (P2011, P2000, P2002, and
P2001). Within time evaluation, the TIP entries are processed, changed and made
available for further processing.
Start and end times
decimalized start and end times
1
status from pair formation
Status 1: Status from pair formation
0 or BLANK = Pair is complete
2 = No clock-in (first time event of the day is missing)
3 = No clock-out (last time event of the day is missing)
4 = No end time for break. Employee is absent for a brief period. T he
system expects a second time event
7 = No start time for off-site work
8 = No end time for off-site work
E = Order confirmation missing
A = Delimited in time evaluation

PAIR TYPE
0 = Non-recorded time
1 = At work (Time Events infotype (2011), clock-in/clock-out entry,
planned pair according to daily work schedule)
2 = Recorded absence (Absences infotype (2001))
3 = Off-site work or recorded attendance (infotype 2002)

ID

CT

Time identifier related to daily work schedule

01 = Overtime (time outside of daily work schedule)
02 = Fill time
03 = Core time
04 = Core time break
05 = Fill time break
06 = Paid break
07 = Unpaid overtime break
08 = Paid overtime break
09 = Overtime break
The processing type/time type class is stored in the view Processing type
and time type according to attendance/absence class (T555Y).
possessing type

- = Pair is deleted at a later stage

BLANK = Pair not counted as productive time
S = Planned working time pair
M = Overtime
A = Absence pair included in the calculation of p.w.t
P = Attendance pair included in the calculation of p.w.t
K = Core night work.

TTYP
BR
ER

The time types are stored in view V_T555A, Time Types

Start time event type, Time event type of first entry
End time event type, Time event type of last entry

Overtime compensation type

BLANK = Remuneration
1 = Remuneration (basic pay plus overtime bonus)
2 = Basic pay
3 = Compensation (time off)

Origin indicator of time pair

E = Time event

O = Overtime from Overtime infotype (2005)

A = Absence from Absences infotype (2001)
P = Attendance from Attendances infotype (2002)
R = Availability from Availability infotype (2004)
D = Generated planned pair
C = Attendance/absence reasons
PT

pointer to attendance pair formation

In order that table TIP is not supplied with too much information, further
data which is relevant to the time pairs is stored in other tables. This
division of the data is referred to as a split. Only the pointer to the
respective data is listed in TIP.

AL

pointer to different payment

C1

pointer to cost distribution

AB

Pointer to absence pairs

NO

Number of hours of a time pair

TOP

TIP entries are processed using a PCR, their relevance to further processing is
determined. If they are relevant, the entries are transferred line by line from the
internal table TIP to the internal table TOP using operation COLOP.

TZP

contains the planned specifications for the day being evaluated from the
employees personal work schedule. The system requires two pieces of
information in order to calculate employees time balances.1 the planned
specifications, 2 the actual specifications.
At the start of time evaluation, the planned specifications - in the form of the daily
work schedule - are made accessible in table TZP. The system analyzes each point
of time in the daily work schedule, and assigns it a time identifier. The time
identifier denotes:
A) Overtime (time outside of the daily work schedule). B) Fill time
C) Core time, D) Break

TES

(Daily results of daily balances) All time types that are formed or processed in
schema processing are stored in the internal table TES (daily balances) during
time evaluation. All calculated balances are stored in TES.
In order to form daily balances, the time types that have been assigned to the time
pairs in table TIP are cumulated and converted to other time types. These time
types are stored in table TES.
The balances can be updated in table ZES (daily balances) and in table SALDO
(monthly balances). EX: -

Time type
0010
0040

text
attendance
overtime

number of hrs r days

2.00
2.0

CUMBT Function takes TES table as input and updates the resulted values in ZES and SALDO
ZES: The employees daily balances are stored in this table.
SALDO The employees cumulated time balances (PERIODIC BALANCES) are listed in this table. Like
monthly, yearly and life time balances

DZL All wage types that are generated during time evaluation are stored in the internal table DZL for
each employee and day.The wage types are updated to table ZL using function CUMBT.

Column/field

Meaning

Date

Date for which the wage type has been generated

BTime

Start time

ETime

End time

Wage Type

Wage type

Wage types are flagged using an IFTYP. The IFTYP indicates the
type of work.
IFTYP

Meaning

Planned work

Overtime

Absence

AL

Pointer to alternative payment

C1

Pointer to cost distribution

AB

Pointer to absence pairs

Number

Number of hours

ZML
FEHLER
Integration between time and payroll: The time wage types determined by time evaluation in
tables ZL, ALP, and C1 (Cluster B2) represent the interface between time evaluation and payroll.
Table ZL: contains the time wage types. Table C1: contains the data relevant for cost assignment.
Table ALP: contains the information necessary for a different payment. Function IMPRT B2
imports the time wage types determined by time evaluation from Cluster B2 to payroll.
In payroll schema U000, in sub schema UT00, schema TC00 or TC04 for the days in the
payroll run that have not yet been processed by time evaluation.
The automatic retroactive accounting recognition guarantees that the time data is
accounted without gaps. Function CHECK, parameter RPR ensures retro.
You can use report RPTEZL00 (Supply Third-Party Payroll System) to download the data
for the required period from table ZL, Cluster B2.
Time evaluation
PT6
Quota Overview
PT50
Create Work Schedule PT01. For mass generation RPTSHF00 (work Schedules).
Change Work SchedulePT02 its also used to delete the work schedule.
Pt80 time balances down loading and uploading
TMON grouping. For modifiers. It updates MODIF table
W
=02 wage type grouping from t510s
T
=02 time type determine group t555y, t555z
A
=02 abs valuation grouping from t554c
DAYMO function talks about day grouping for generating the wage types 01,02,03,04
T555a creating time type
T555y time type n process type grouping
T555z time indicators n time type
V_t555e for err msgs
FEHLR is an internal table for storing the err msgs
Abs valuation rule t544c
T554l- define valuation rules
SM36, SM37 SHCEDULE S to run the time evaluation at back end in everyday at a fixed time
PT40 time statements, ex- to have d report on how many num of hrs has been taken as OT
PCRS AND FUNCTIONALITY
T550 dws
TMON- 1st pcr in tm mgt is TMON-to set the modifier for the wagetype-t510s,time type determine
group, abs valuation grp for the emp grouping for pcr
Td20 checks whether any err occurs if any send that num to time admin
Operations:
Td10- if daily work schedule is still active then it terminates for that day

Outer n -checks whether there are any errors

Reports
RPTEAB00 Attendance check
RPTCMP00 Time leveling
RPLTIM00 Time documents
RPTERR00 Error processing
RPTENT00 Multiple recording
RPTABS50 Attendance/absence data overview
RPTEDT00 Time statement
RPTEDT00 Balance overview
RPTPSH10 Personal work schedule
RPTIME00 Time evaluation
RPWI1000 Statistics on incorrect confirmations
RPWI3000 Process incorrect sessions
RPIEWT01 List of incorrect external wage type records
RPIEWT03 Incorrect sessions (external wage types)
RPCLSTPC report (Display Cluster PC: Personal Calendar).

Master Data
PA10 Personnel File
PA20 Display HR Master Data
PA30 Maintain HR Master Data
PA40 Personnel Events
PA41 Change Hiring Data
PA42 Fast Data Entry for Events
PRMD Maintain HR Master Data
PRMF Travel Expenses: Feature TRVFD
PRML Set Country Grouping via Popup
PRMM Personnel Events
PRMO Travel Expenses: Feature TRVCO
PRMP Travel Expenses: Feature TRVPA
PRMS Display HR Master Data
PRMT Update Matchcode
PSO3 Infotype overview
PSO4 Individual maintenance of infotypes

Time Management
PA51 Display Time Data
PA53 Display Time Data
PA61 Maintain Time Data
PA62 List Entry of Additional Data
PA63 Maintain Time Data
PA64 Calendar Entry
PA70 Fast Data Entry
PA71 Fast Entry of Time Data
PBAB Maintain vacancy assignments
PT01 Create Work Schedule
PT02 Change Work Schedule
PT03 Display Work Schedules

Cluster B1
Definition
All clusters for entry data are contained in file PCL1. This also includes cluster B1, which stores several
tables containing information on the employees time events and on status data for time evaluation.

Unprocessed time events

Error table ERT

Selected monthly balances

Table QT, which contains various status fields for time evaluation

Use
If the results of time evaluation are not clear, you can use cluster reports to display the data determined.
Report RPCLSTB1 allows you to view the data in c luster B1, arranged into tables.
You can also view cluster B1 via the Time Management pool. You can display the content of cluster B1
tables for individual employees in the Error handling transaction by choosing Goto Evaluation result.

Structure
File PCL1 contains only temporary clusters. Cluster B1 tables are only filled if the data contained in them
has not yet been processed by the time evaluation report.
Internal Tables in Cluster B1
Balances, wage types and quota transactions
Table
NT1

Table NT1 contains pointers to all unprocessed time events. It is used in pair formation, and to
recognize the necessity for a recalculation.The time events are stored in table TEVEN.

NT2

Table NT2 contains pointers to time events that lead to a processing error.

ERT

Table ERT contains the messages from the last evaluation run.For information on the various
types of message, see Grouping Messages.

NCT

Table NCT contains date specifications for days for which the entire pair formation process must
be carried out again.

IFT1

Table IFT1 is only used internally by SAP.

IFT2

Table IFT2 is the interface table to Incentive Wages. It describes the changes in table WST (time
tickets, other documents) from cluster B2 to the time tickets that have already been updated in
Incentive Wages. Further information can be found in the documentation on Integration with
Logistics - Plant Data Collection under the section Posting Time Tickets to Incentive Wages .

ST

Table ST contains selected balances which are transferred to the time recording systems for
employees information the next time a download is performed.

QT

Table QT contains various items of information which must be updated daily, for example: Date of
the last day for which pair formation and generation was carried out Start and end of planned
working time, public holiday class, day type and daily work schedule class of the day in question

Tables in Cluster B2

Basic data and work schedule

Table
WPBP

Table WPBP contains data on the employees work center and basic pay.

PSP

Table PSP contains data on the employees personal work schedule for each day.

Balances, wage types and quota transactions

Table
ZES

Table ZES contains daily balances.

SALDO

Table SALDO stores all cumulated balances. The balances are added from table TES to
SALDO in month-end processing.

ZKO

All quota transactions of the period are stored in table ZKO.

ZL

Table ZL represents the interface between time evaluation and payroll. The existing time
wage types have been derived via time wage type selection using the Time Wage Type
Selection Rule table (T510S).

The entries in table ZL contain pointers to the following tables:

ALP - alternative payment
C1 - cost distribution
AB - absences
An IFTYP is specified for the selected time wage types. The IFTYP is an indicator for
payroll. It describes the origin of the wage type:
S - planned work
M - overtime
A - absence
ALP

Table ALP contains the specifications on a different rate of payment

C1

Table C1 contains cost distribution specifications (account assignment).

VS

Table VS contains variable balances which can be defined by the user. These balances
can be entered in the table during time evaluation using operation ADDVS, where they are
available for customer-specific evaluations.

CVS

Table CVS contains the cumulated balances from table VS. Table CVS is filled
automatically.

FEHLER

All messages generated during time evaluation are stored in table FEHLER.

For information on the various types of message, see Grouping

Messages.
KNTAG

The string KNTAG shows whether or not the employee performs core night work.
(Germany only)

Automatic accrual of absence quotas

Table

QTACC

Table QTACC contains the accrual entitlements that were generated by time evaluation on
the relevant date of the accrual.
You can view detailed information on the generation by double-clicking the appropriate
line.

QTBASE

Table QTBASE contains the information on the base entitlement that was used as a basis
for calculating the accrual entitlements.
Any changes to the base entitlement within an accrual period are flagged accordingly.

QTTRANS

Table QTTRANS indicates the status of the transfer pool for each day. The cumulated
entitlements are indicated until they have been transferred to the Absence Quotas
infotype (2006) or until the entitlement has expired.
You can view detailed information on the transfer pool and on the transfer by doubleclicking the appropriate line.

URLAN

Table URLAN contains information on the updating of the Leave Entitlement infotype
(0005).

Time pairs and time tickets

Table
PT

Table PT contains the time pairs generated in pair formation. This table is only required if
you use time recording systems.

WST

Table WST contains the generated time tickets

CWST

Table CWST contains the cumulated time tickets

AT

Table AT is an assignment table which links time pairs and time tickets.

Time data
Table
AB

Table AB contains all absences

ANWES

Table ANWES contains all attendances which have been entered using the Attendances
infotype (2002).

VERT

Table VERT contains all substitutions entered in the Substitutions infotype (2003)

RUFB

Table RUFB contains all availability records entered in the Availability infotype (2004)

MEHR

Table MEHR contains all overtime data entered in the Overtime infotype (2005)

ABWKONTI

Table ABWKONTI contains all absence quotas from the Absence Quotas infotype (2006)
that fulfill one of the following conditions:

Absence quotas that are valid on at least one day of the time evaluation period

Absence quotas that are deductible on at least one day of the time evaluation
period and whose validity period is in the past

Absence quotas that are deductible on at least one day of the time evaluation
period and whose validity period starts on a day in the current time evaluation
period

ANWKONTI

Table ANKONTI contains all attendance approvals from the Attendance Quotas infotype
(2007).

SKO

Table SKO contains all time transfer specifications recorded in the Time Transfer
Specifications infotype (2012)

Status information
Table
BEZUG

This table shows the recalculation dates for time evaluation, the time statement and a
third-party payroll system.

The Internal Table DZL

Definition
All wage types that are generated during time evaluation are stored in the internal table DZL for each
employee and day.
The wage types are updated to table ZL using function CUMBT.

Structure
The internal table DZL
Column/field

Meaning

Date

Date for which the wage type has been generated

BTime

Start time

ETime

End time

Wage Type

Wage type

Wage types are flagged using an IFTYP. The IFTYP indicates

the type of work.

AL

IFTYP

Meaning

Planned work

Overtime

Absence

Pointer to alternative payment

C1

Pointer to cost distribution

AB

Pointer to absence pairs

Number

Number of hours

The Internal Table ZML

Definition
The internal table ZML serves as an interim table in time evaluation. All overtime wage types are stored in
ZML during time evaluation.

Use
Table ZML is processed when overtime is compensated (function POVT).
The overtime compensation type indicates whether overtime should be remunerated or compensated by
time off. The overtime compensation type can be entered for an overtime record in the Attendance
Quotas (2007) and Overtime (2005) infotypes, or is stored for the wage type in processing class 17.
If the overtime is to be remunerated, a wage type is generated and inserted in table DZL. If the employee
is granted time off for overtime, the system forms an absence quota.

Structure
The internal table ZML
Column/field

Meaning

BTime

Start of overtime

ETime

End of overtime

Wage Type

Wage type

Comp

Overtime compensation type:

BLANK

Remuneration

Remuneration

Basic pay

Compensation (time off)

IFTYP
Wage types are flagged using an IFTYP. The standard identifiers are:
S - planned work
M - overtime
A - absence

AL

Pointer to an alternative payment

C1

Pointer to cost distribution

AB

Pointer to absence pairs

Number

Number of hours

The Internal Table TZP

Definition
The internal table TZP is only used in time evaluation. The planned specifications from the employees
personal work schedule are stored in TZP.
Any substitutions, which overwrite the employees personal work schedule, are also taken
into account.

Use
The system requires two pieces of information in order to calculate employees time balances:

The planned specifications

These stipulate how the employee has to work (according to his/her work schedule).

The actual specifications

These indicate when the employee actually worked.

At the start of time evaluation, the planned specifications - in the form of the daily work schedule - are
made accessible in table TZP. The system analyzes each point of time in the daily work schedule, and
assigns it a time identifier. The time identifier denotes:

Overtime (time outside of the daily work schedule)

Fill time

Core time

Break

You can insert a PRINT TZP in the schema, after function P2011 or P2000, if you want to display the most
important contents of table TZP. If you run the time evaluation report RPTIME00 with the test utilities ON,
you can check the values calculated in the log.

Structure
The Internal Table TZP
Column/field

Meaning

CLOCK TIME

Time point:
The daily work schedule specifies start times for breaks, core time and so on as
decimalized values.
Times outside of the daily work schedule are also taken into account.

CODE

A time identifier is assigned to each time point to describe its place in the daily
work schedule. The breaks are taken from the work break schedule that is
assigned to the daily work schedule.

Time point

Time identifier

000000

01 Time outside of daily work schedule

080000

02 Fill time

090000

03 Core time

095000

04 Core time break

100000

03 Core time

BLOCK

This field is currently of no significance.

PDBEZ

Duration of paid break

The duration of the paid break period is specified. The time wage types formed
from this information are evaluated in payroll.

PDUNB

Duration of unpaid break

The duration of the unpaid break period is specified.

Further values which are accessible in TZP:

PTYP1

Break type 1 is stored in the work break schedule (T550P).

The break type 1 field indicates whether the break is during planned working time
or overtime.
The break type 1 can be processed separately using function PBRKS.

PTYP2

Break type 2 is stored in the work break schedule (T550P) and is user-definable.

The break type 2 can be processed separately using function PBRKS. Special
break processing can be performed for certain employees or employee groupings.

Using Functions and Operations to Edit Work

Tables

Use
There are specific functions and operations available to edit work tables. The name of the function or
operation indicates the purpose that it serves.

Features
Functions that edit internal tables line by line
Table

Function

Description

TIP

PTIP

Process Internal Table TIP

RTIP

Read Internal Table TIP

DZL

PZL

Process Table ZL

ZML

POVT

Process Overtime Table

TES

PDB

Process Daily Balance Table

SALDO

PMB

Process Monthly Balance Table

ERT

PERT

Process Error Table

The functions listed call a personnel calculation rule in which the entries in the specified table are
processed/read line by line according to the rules stipulated.
You can use the following operations within personnel calculation rules to enter the results of processing
in internal tables:
Operations that make new entries in internal tables
Table

Operation

Description

TIP

COLOP

Collect in Internal Table TOP

DZL

ADDZL

Add to Table ZL

ZML

ADDOT

Add to Overtime Table

TES

ADDDB

Add to Daily Balance Table

SALDO

ADDMB

Add to Monthly Balance Table

ERT

COLER

Collect Error

1. What is the use of implementing OM?

2. What are the sub modules that OM is integrated with?
3. How do you define the objects in OM(Org unit, job, Position, Holder, task, work center,
cost centers)
4. How many objects t are there in your previous implementation?
5. What is a reporting structure and what is the use of this?
6. What is a relation ship? Tell me few relation ships that you have used in your
implementations?
7. How you relate the position with objects like org unit, job, task, other position, task.
8. What is the difference between position and job?
9. What are the relationships 007, 008 for?
10. What are the objects that task can be assigned with?
11. How do you switch from simple maintenance to another method?
12. How do you make a position a chief of a org unit.
13. What are the planning tools?
14. What are different statuses in OM? What is the use of it?
15. How do you change the status of object? What is the report?
16. what is delimiting ? how do you delimit the validity of the object?
17. is it possible to change the start and end date of objects and infotypes ? How?
18. How do you assign the cost centers to position and org unit? To which object you have
assigned cost centers in your implementation.
19. What is master cost centre of an object?
20. What is infotype? What are the attributes of the infotype?
21. What is time constraint?
22. do you know how to create custom infotype?
23. How to create subtype? How do you assign it to a object type?
24. What is the relation and dependency between validity of the infotype and validity of the
objects?
25. What is cost distribution? What is the infotype used for it?
26. What is infotype for making position Obsolete ?
27. What is infotype for making position vacant of occupied ?
28. What is standard profile?
29. What is PD profile and the infotype for it?
30. How many you can use to create org structure?
31. How do you create positions and jobs in simple maintenance method?
32. How do you create a task in org staffing method ?
33. What is the advantage with general mode?

34. How do you create a structure in general structures?

35. How do edit the org structure using the structural graphics method?
36. What is a matrix structure?
37. What is cross functional relation ship? How do you create cross functional relation ship?
38. What are the OM infotypes that you are familiar with?
39. What all the Om infotypes you created in your implementations?
40. Did you manually create entire org structure in your previous implementation? If not then
how did you create?
41. Can you assign a specific number range for specific objects? How? What is the switch?
42. What is the integration Switch table?
43. What is the integration switch between OM and PA?
44. What is plan version and use? Where do you create plan version?
45. What is the difference between current plan version and active plan version?
46. What is the switch to maintain active plan version?
47. What is the report used to copy the org structure from one PV to and PV?
48. What is the report used to compare the org structure from one PV with another PV?
49. What is the evolution path? use of it?
50. Can you create a custom evolution path? How?
51. Tell me few reports that make use of evolution paths?
52. Can you create a custom relation ship? How? Have you ever get a chance to create a
custom relationship?
53. Is there any action in OM? How do configure actions in OM? What is the transaction
code?
54. What is detailed maintenance?
55. What are the transaction codes of all methods and objects creations?
56. What is the purpose of the reports RHINTE00?
57. What is the purpose of the reports RHINTE10?
58. What is the purpose of the reports RHINTE20?
59. What is the purpose of the reports RHINTE30?
60. in what cases you use the above reports?
61. Can we transport the org structure? How?
62. What is Manual transport and automatic transport?
63. What is the integration switch for transport?
64. What are the infotypes that are integrated with ECM?
65. Tell me few OM reports you used in you implementation?
66. Which is the method that you have trained the end user in, to create the org structure?