Академический Документы
Профессиональный Документы
Культура Документы
Creation Date:
28 December 2006
Last Updated:
21 June 2007
Control Number:
Version:
3.0
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 1
Contents
Contents............................................................................................................................................... 2
Preface ................................................................................................................................................. 4
Overview.............................................................................................................................................. 5
Key System Health Check Phases ..................................................................................................... 6
Audit Phase....................................................................................................................................... 6
Tuning Phase .................................................................................................................................... 6
Review & Report Phase.................................................................................................................... 7
Management Phase ........................................................................................................................... 7
Tuning Payback ................................................................................................................................ 9
Understanding The Bigger Picture............................................................................................... 12
Multi-Threaded Processes ............................................................................................................... 15
Concurrent Programs...................................................................................................................... 15
Tune The HR Application Setup & Procedures ............................................................................ 16
Security List Maintenance Process (PERSLM).............................................................................. 16
DataPump ....................................................................................................................................... 17
System Extract Process................................................................................................................... 18
System Extract Restart Process ...................................................................................................... 18
System Extract Write Process......................................................................................................... 18
Data Loading Person Records ........................................................................................................ 19
Tune The Payroll Application Setup & Procedures...................................................................... 21
Payroll Run Process........................................................................................................................ 21
QuickPay Process ........................................................................................................................... 23
Payroll Reversal.............................................................................................................................. 23
Balance Adjustment........................................................................................................................ 24
Balance Initialization...................................................................................................................... 25
Payroll Run Rollback ..................................................................................................................... 26
Pre-Payments.................................................................................................................................. 26
QuickPay Pre-Payments ................................................................................................................. 27
Costing............................................................................................................................................ 28
Transfer To GL............................................................................................................................... 30
External & Manual Payments......................................................................................................... 30
Magnetic Tape ................................................................................................................................ 31
Cheque Writer ( U.S. & U.K. )....................................................................................................... 31
Deposit Advice ( U.S. ) .................................................................................................................. 32
Cash Process................................................................................................................................... 32
RetroPay Process ............................................................................................................................ 33
Advance Pay................................................................................................................................... 33
Multi-Threaded Archiver................................................................................................................ 33
Sparse Matrix / Insignificant Run Results ...................................................................................... 34
Consolidation Sets .......................................................................................................................... 34
%_PAYMENTS Balance Database Item ( U.S. Only ).................................................................. 35
Continuous Calculation .................................................................................................................. 35
Hot Payroll Tables ....................................................................................................................... 36
Tune The Benefits Application Setup & Procedures..................................................................... 37
Compensation Object Design ......................................................................................................... 37
Plan Design..................................................................................................................................... 37
Online Processes............................................................................................................................. 38
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 2
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 3
Preface
This document is an updated version of the Oracle HCM & Benefits Tuning and System Health Check Release 11i document ( Metalink
Note Number: 226987.1 ). It has been updated to cover the latest
information for Release 11i and Release 12. Any Release 12 specific
information will be highlighted accordingly.
A major change from the previous document is that the sections that are
not specifically about HCM or Benefits have been removed e.g Useful
Network Analysis Utilities / Commands, Utlnstat & Utlestat etc. The
intention is that the document should focus on HCM & Benefits, whilst
other performance and implementation issues can be addressed by
documents to be found on Metalink,, some of which are listed in
Appendix F.
The content of the HCM and Benefits sections is largely unchanged,
however it has been verified against the latest 11i & Release 12
functionality.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 4
Overview
This document highlights the key areas and tasks required to perform a
detailed system health check of the Oracle HCM and Benefits
Application.
When talking about health checks we often mean the action or process
of optimizing an application or making it more performant.
To optimize an application implementation it is vital to understand each
of the components of the system and associated subsystems; the
operating system, database, application(s), network and client. By
discovering where each subsystem is being stressed or bottlenecked and
correctly focusing the search, the potential problem causes can be
identified quickly.
Oracle Applications are exceptionally versatile and can be integrated
into a variety of businesses with the minimum of functional setup.
Typically, the approach to tuning applications has concentrated on
optimizing the database and perhaps tuning for unusual data
distributions. Whilst this may be the primary focus of a particular
tuning effort, there may be many more system features can be tuned and
some can return far higher performance gains. A much better tuning
approach is end-to-end tuning. In other words, if the user cannot see
the change the tuning effort was not correctly focused or there is
another overriding major bottleneck still to be corrected.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 5
Audit Phase
Tuning Phase
Management Phase
Audit Phase
A full system health check cant be done without an understanding of
the whole application and all of its components and subsystems. This
is best done by bringing together representatives from each business
function involved with the application; users, system administrators,
DBAs, network administrators etc, and discussing what the system is
and does from each of their perspectives.
Any problems must be defined clearly and documented. Performance
targets must be set and agreed. Some may be essential to the business
and others may be nice to have but not essential to support the
business.
Tuning Phase
A baseline of existing operation performance must be established.
There is no point in implementing any performance enhancements
unless a baseline exists against which changes can be measured.
Perform detailed analysis on areas identified within the audit phase. A
methodical approach should be used to investigate each focused area.
Actions and results should be clearly documented. If a major
performance problem is identified and fixed but the resultant effect on
performance is minimal then there may be other overriding bottlenecks
that are being hidden by the previous problem. Baselines should then be
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 6
Management Phase
This takes place when tuning transitions from a reactive mode into a
proactive mode. An essential part of the tuning process is to involve
and possibly transfer necessary skills to the client, advise appropriate
courses and perhaps recommend books. The primary goal is to enable
clients to monitor and manage performance themselves.
This document concentrates on the first 3 phases and doesnt expand
any further on the management phase.
Tune Database
Structure
Tune Client
Tune Middle
Tier
Tune Server
Tune
Application
Tune
Network
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 7
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 8
Tuning Payback
Tuning can take place within different parts of an application.
Identifying the 6 main steps to tune an application, there is diminishing
return at each subsequent step. Tuning early in a development cycle
returns the highest gains. Significantly more effort is required in the
later stages and, in practice, it is almost impossible to tune a poorly
designed application. Diagram 3 shows the potential return on effort for
tuning at each stage.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 9
1000000
1000000
100000
10000
1000
1000
1000
100
100
10
10
1
Optimise
Data
Design
Tune SQL
Statements
Tune
Application
@ DBA
Level
Tune
Memory
Allocation
Tune Disk
I/O
Tune
Memory
Contention
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 10
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 11
Applications
What application(s) are used ( Oracle & non-Oracle )
How do applications interact with the Oracle Application ?
Exactly what part(s) of the Oracle Application is used ?
How exactly has the application been set up ( formulas, elements,
costing etc ) ?
What custom processes / procedures have been created ? Provide
explicit details.
Describe a typical Payroll run cycle / sequence of steps
performed.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 12
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 13
Infrastructure
What teams support the application ?
What is the backup and recovery strategy ?
What is the disaster recovery strategy ?
What service level agreements exists ?
What capacity planning ( hardware sizing ) has taken place ?
What system performance monitoring and workload optimization
( tuning ) takes place ?
What resource management and accounting takes place ?
Miscellaneous
What are peoples performance perceptions of the system ( users
and administrators )
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 14
Multi-Threaded Processes
Concurrent Programs
In Oracle Applications, concurrent processing simultaneously executes
programs running in the background with online operations. Using the
System Administrator responsibility, you can manage when programs
are run and how many operating system processes Oracle Applications
devotes to running programs in the background.
A concurrent manager is itself a concurrent program that starts other
concurrent programs running. When an application user submits a
request to run a program, the request is entered into a database table
that lists all of the requests. Concurrent managers read requests from
the table and start programs running.
You can define as many concurrent managers as you want. When you
define a manager, you:
-
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 15
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 16
DataPump
The Oracle HCM Data Pump supports rapid implementation by
simplifying and standardizing the common tasks associated with
loading batch data into the Oracle HCM tables. This is done by
providing a set of predefined batch tables and standard processes that
simplify the tasks of data-loading using the supported APIs.
Single / Multi Threaded
Multi threaded.
Key PAY_ACTION_PARAMETERS Settings
THREADS
CHUNK_SIZE
MAX_ERRORS_ALLOWED
PUMP_DEBUG_LEVEL
DATA_PUMP_DISABLE_CONT_CALC
DATA_PUMP_NO_FND_AUDIT
DATA_PUMP_NO_LOOKUP_CHECKS
DATA_PUMP_PURGE_CHUNK_SIZE
DATA_MIGRATOR_MODE
PUMP_DT_ENFORCE_FOREIGN_LOCKS
Observations
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 17
The datapump interface tables are like any other type of interface
table. They will grow in size over time depending on use. You
should periodically clean down these tables to aid performance.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 18
2.
3.
This mechanism is suitable when you have just got a single processor
accessing this table but if your loading mechanism supports parallel
processors ( like datapump ) you are likely to experience locking issues
from within your data loading API ( as more than one process tries to
access a sequence at the same time ). This does assume that you are
using published APIs for the creation of person details.
A way to get around this problem is to define your business group as
having manual employee and applicant number generation methods.
Your loading routine must then specify suitable values for these
attributes. Because youre using manual number generation, the create
employee / applicant API knows not to check the number generation
controls table.
Having loaded all of your data, you may need to set the number
generation method for your business group back to automatic. The form
will not allow you to do this! You have to make the change via
SQL*Plus. The following is an example of how to set the employee and
applicant number generation methods to automatic:
UPDATE HR_ORGANIZATION_INFORMATION
SET ORG_INFORMATION2 = A,
ORG_INFORMATION3 = A
WHERE ORGANIZATION_ID = < Id for business group >
AND ORG_INFORMATION_CONTEXT = Business Group
Information;
You will also have to set the next sequence value within the
PER_NUMBER_GENERATION_CONTROLS table.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 19
UPDATE PER_NUMBER_GENERATION_CONTROLS
SET NEXT_VALUE = < max(employee_number) + 1 >
WHERE BUSINESS_GROUP_ID = < Id for business group >
AND TYPE = EMP;
UPDATE PER_NUMBER_GENERATION_CONTROLS
SET NEXT_VALUE = < max(applicant_number) + 1 >
WHERE BUSINESS_GROUP_ID = < Id for business group >
AND TYPE = APL;
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 20
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 21
CHUNK SHUFFLE
Observations
If rollbacks or mark for retrys have been done / specified then the
Payroll run process is unable to use the latest balance values and
therefore has to recalculate balances. Having to recalculate the
latest balance values can have a significant affect on the Payroll
run timings. Release 11i stores the latest and latest minus 1 balance
values. This protects you from single rollbacks but multiple ones
will still cause the removal of the balance.
Within the U.S. legislation, when defining elements you are able to
specify whether the element generates a separate cheque or
whether it needs to be taxed separately. This causes additional
spawned Payroll runs to be initiated after the main Payroll run
process. Therefore, the more elements that are defined in this
manner and the more people who are assigned to these elements,
the more processing the Payroll engine has to perform .
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 22
If additional user defined database items have been created and the
associated SQL has not been thoroughly tuned then performance
problems may be experienced.
QuickPay Process
QuickPay enables you to carry out payroll processing for individual
employees. You can use QuickPay to pay employees who are leaving
and who require payment by cash or cheque. If an employee asks you
what his or her net pay will be this month, you can run QuickPay to
find the answer, then roll it back to remove all results from the
database.
Single / Multi Threaded
Single threaded.
Key PAY_ACTION_PARAMETERS Settings
As for the Payroll Run process ( excluding THREADS parameter )
plus:
QUICKPAY_INTERVAL_WAIT_SEC
QUICKPAY_MAX_WAIT_SEC
Observations
Payroll Reversal
You can retry an employee or a run only when no postrun processing
has occurred. You use reversals when you need to correct run results
after postrun actions have already occurred.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 23
In other words, reversals are useful when you need to correct run
results some time after the run has occurred. The reversal process
creates negative run results that cancel out previous entries.
Single / Multi Threaded
Single threaded.
Key PAY_ACTION_PARAMETERS Settings
None apply.
Observations
Balance Adjustment
Oracle Payroll balances do not normally need direct adjustment by
users. The most frequent cause of an incorrect balance when you have
paid the wrong amount to an employee is remedied by carrying out a
QuickPay run for the employee. How far you can manually adjust other
balances depends on whether the balance is a predefined startup
balance or is userdefined.
You can freely adjust all user balances. However, the only predefined
balances that you can adjust are those which are not above other
balances in the balance hierarchy. You can adjust a pretax deduction
balance but not the Total Deductions balance. This is to protect the
integrity of predefined balances, by preventing users from adjusting
high level balances in isolation. To ensure balance integrity, whenever
you adjust a low level predefined balance, Oracle Payroll automatically
adjusts all related higher level balances as well.
Single / Multi Threaded
Single threaded.
Key PAY_ACTION_PARAMETERS Settings
None apply.
Observations
.Can only perform balance adjustments for a single assignment at a
time.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 24
Balance Initialization
Enables the transfer of seeded and user balance values in to Oracle
Payroll for use by implementations which begin processing midfinancial year.
Single / Multi Threaded
Single threaded but you can submit multiple balance initialization
batches ( which enables it to take advantage of multiple processors ).
Key PAY_ACTION_PARAMETERS Settings
None apply.
Observations
Creates balance adjustments within the system and also creates the
necessary latest balances.
Can only be run once per assignment. All values therefore need to
be loaded at the same time.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 25
Observations
Removes all traces that the run actually took place ( removes run
results, assignment actions and latest balances etc ).
Pre-Payments
The PrePayments process prepares the payments generated by the
Payroll Run for payment. It prepares payments for each assignment and
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 26
QuickPay Pre-Payments
The PrePayments process prepares the payments generated by the
Quickpay for payment. It prepares payments for each assignment and
inserts the results into PAY_PRE_PAYMENTS for each payment
method for an assignment.
The PrePayments process also:
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 27
Costing
The Costing process accumulates results for transfer to the General
Ledger and other systems. This process sorts the run results in
accordance with the information you have selected from the Cost
Allocation flexfield at all levels, by the following:
Company
Set of books
Cost centre
General Ledger
Labour distribution accounts
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 28
COST_PLS_VAL
Observations
In Release 11i the costing code has been combined in to the same
module. The determination whether to use the C or PL/Sql flexfield
logic is controlled by the setting of COST_PLS_VAL. By default
this will use the C code.
At one site using the new PL/Sql version of the code, a trace of the
costing process showed some timing differences between the CPU
and elapsed time when trying to retrieve a sequence value from the
PAY_COSTS_S sequence. This site had THREADS set to 36 ( 1.5
times the number of CPUs on the machine ). It was suggested that
the site increase the cache size for the sequence so as to alleviate
possible contention between processes. Increasing the cache size
improved performance but did not completely resolve the CPU to
elapsed timing differences. Other things to try include:
1.
2.
The PL/Sql version of the code uses the AOL PL/Sql flexfield
routines for validation of the new costing flexfields to be created.
This performs exactly the same validation as if you were entering
the structure via one of the application forms. What this means is
that all costing flexfield segment validation will be executed. It is
therefore important to ensure that any user defined table value set
validation has been correctly tuned. This is especially important if
the validation references a user defined view.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 29
Transfer To GL
If your installation includes Oracle General ledger, you can run the
transfer to GL process to transfer the results of the Costing process for
a payroll to the Accounting flexfield of Oracle General Ledger.
Single / Multi Threaded
Multi threaded.
Key PAY_ACTION_PARAMETERS Settings
THREADS
CHUNK_SIZE
CHUNK SHUFFLE
TGL_DATE_USED
Observations
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 30
Magnetic Tape
The Magnetic Tape process generates the payment due and writes the
data to a file on magnetic tape. It is this tape that is taken to the bank for
payment.
Single / Multi Threaded
First half of the process ( creating assignment actions ) multi threaded.
Second half of the process ( creating tape file ) single threaded.
Key PAY_ACTION_PARAMETERS Settings
THREADS
CHUNK_SIZE
CHUNK SHUFFLE
ADD_MAG_REP_FILES
Observations
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 31
In the U.S. the Deposit Advice report is attached with the cheque.
This means a lot of balance retrieval is taking place ( performance
overhead ). The U.S. Deposit Advice report is very detailed and
contains lots of balance details.
Cash Process
Oracle Payroll enables you to choose Cash as a payment method and to
record cash payments to employee assignments. Oracle Payroll
automatically analyses cash payments into the largest denomination
notes and coins as part of the PrePayments process.
Single / Multi Threaded
Multi threaded.
Key PAY_ACTION_PARAMETERS Settings
THREADS
CHUNK_SIZE
CHUNK SHUFFLE
Observations
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 32
RetroPay Process
The RetroPay process reruns the payroll calculations for all the periods
affected by the retroactive change. This payroll processing is held in
memory only and the results are not saved to the database. Instead, the
system calculates the difference between the original results and the
results using the new information. There are 3 versions of RetroPay.
Single / Multi Threaded
Multi threaded.
Key PAY_ACTION_PARAMETERS Settings
Same as payroll run process.
Observations
Advance Pay
The Advance Pay process enables you to pay employees in advance for
holidays or other events. The process performs payroll runs for the
periods to be advanced, using all date effective information in place,
and stores the final net figure as the amount to be advanced. There are 2
versions of Advance Pay.
Single / Multi Threaded
Multi threaded.
Key PAY_ACTION_PARAMETERS Settings
Same as payroll run process.
Observations
Multi-Threaded Archiver
A process to extract values within the database to archive tables that
can then be reported against. Is used in EOY processing globally.
FastFormulas define what data to extract snapshot values for.
Single / Multi Threaded
Multi threaded.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 33
Consolidation Sets
Consolidation sets are the means by which you label payroll runs for
further processing. This enables you to process the results from more
than one payroll in a single action. You need only produce one tape per
payment method for several payrolls, one set of reports and one set of
costing for the whole set.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 34
Observations
is 0
SOE_PAY = MEDICAL_OPTION_B_PAYMENTS
Continuous Calculation
The continuous calculation functionality allows payroll administrators
to spread the processing of a payroll over the payroll period. This
functionality is typically suited to those payrolls which remain fairly
static from period to period ( e.g. director payrolls and payrolls where
employee entitlements do not change much from period to period and
there are no time entry feeds ). Under the continuous calculation model
you could run your payroll at the start of the period. Any changes to a
persons data, made after the initial run and before the end of the
period, which would affect their salary entitlement will cause triggers to
fire which will mark the person for retry. The payroll can them be resubmitted later in the period to re-process all of those people who have
been marked for retry. This model means that you no longer have to
wait to run your main payroll at the end of your period. The triggers
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 35
Heavy Update
Heavy Read
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 36
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 37
Eligibility/Electability
If you are NOT using derived factor MINIMUMs for participant
eligibility then you should leave the track ineligible flag off for
performance purposes. This prevents multiple writes for ineligible
compensation objects within the same program.
Eligibility has a top down hierarchy so by defining the broadest criteria
at the top and refining the criteria as you drill down you can find the
highest population ineligible at the highest level in the hierarchy to
reduce processing for participants.
Electability has a bottoms up determination. Define the most general at
highest level and restrict at the lowest levels.
Rates
Define rates at the highest possible common level to minimize
calculation and write processing. Avoid option in plan in program
(lowest level) as this has the highest processing times.
Rules
Create these at the lowest level possible. A person level rule, i.e. a
derived factor, will be fired off for every person processed verses a rate
or coverage rule that would only be fired once for the associated
compensation level.
One Business Group, Multiple Organizations
If you have a corresponding plan for each organization you will be
evaluating each plan regardless because the application stripes by
Business Group. To get around this define a role type for an
organization as Owner and attach this to a program. This allows
programs that have a corresponding organization owner to be pulled
only and not all the others.
Online Processes
Online Life Events Process
This process allows the benefits administrator to process life events in
real-time. If this processed life event results in the creation of electable
benefit choices for this person you can then enroll them into one or
more benefit plans for which they are eligible based on the processed
life event.
Single / Multi Threaded
Single threaded
Key BEN_BATCH_PARAMETER Settings
Observations
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 38
Observations
Batch Processes
Back-out Life Events Process
This process marks all electable choices and related information, such
as payroll contributions, dependent designations and communications
with a status of backed-out. Life events that have a status of started or
processed can be backed out.
Single / Multi Threaded
Multi threaded.
Key BEN_BATCH_PARAMETER Settings
THREADS
CHUNK_SIZE
MAX_ERRORS_ALLOWED
Observations
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 39
Observations
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 40
Observations
Observations
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 41
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 42
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 43
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 44
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 45
The payroll batch processes read values from this table on startup, or
provide appropriate defaults, if specific parameter values are not
specified.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 46
Parameter
Value
Default
ADD_MAG_REP_FILES
BAL BUFFER SIZE
BEE_INTERVAL_WAIT_SEC
1 or more
1 or more
1 or more
4
30
2
0 or more
0 or more
1 or more
0
600
Y
1
1
Y
N
20 (10)
20
N
Max
Value
BEE_LOCK_INTERVAL_WAIT_SEC
BEE_LOCK_MAX_WAIT_SEC
BEE_MAX_WAIT_SEC
CHUNK SHUFFLE
CHUNK_SIZE
COST BUFFER SIZE
COST_API_IMODE
COST_PLS_VAL
DATA_MIGRATOR_MODE
DATA_PUMP_DISABLE_CONT_CALC
DATA_PUMP_NO_FND_AUDIT
DATA_PUMP_NO_LOOKUP_CHECKS
DATA_PUMP_PURGE_CHUNK_SIZE
EE BUFFER SIZE
FF_MAX_OPEN_CURSORS
HRLEGDEL_SLEEP
HR_DM_DEBUG_LOG
HR_DM_DEBUG_PIPE
HR_DU_DEBUG_LOG
HR_DU_DEBUG_PIPE
HR_GL_SYNC_DEBUG
INTERLOCK
JP_DIM_EXC_REV_FLAG
JRE_LIBRARY
LOGGING
LOG_AREA
LOG_ASSIGN_END
LOG_ASSIGN_START
LOW_VOLUME
MAX SINGLE UNDO
MAX_ERRORS_ALLOWED
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
or N
16000
or more
or N
1000
16000
1000
Y or N
P, Y or N
Y or N
N
N
Y or N
Y or N
1 5000
500
5000
1 or more
32 - 128
40
128
1000
128
0 or more
10
:INFO
:SUMM
:ROUT
:PARA
:FAIL
:SUMM
:FAIL
:INFO
:SUMM
:ROUT
:PARA
:FAIL
:SUMM
:FAIL
NORMAL or
DEBUG
Y or N
Y or N
NORMAL
N
N
See Later
See Later
See Later
See Later
Y or N
1 or more
0 or more
N (for DB
9.0 and
above)
50
CHUNK_SIZ
E or 20
(if no
chunk
Page 47
MAX_ITERATIONS
Maximum Iterations
allowed per Run Action
Print Files
Process Timeout
PRINT_FILES
PROCESS_TIMEOUT
PUMP_DEBUG_LEVEL
PUMP_DT_ENFORCE_FOREIGN_LOCK
S
PURGE_SKIP_TERM_ASG
PURGE_TIMEOUT
QUICKPAY_INTERVAL_WAIT_SEC
QUICKPAY_MAX_WAIT_SEC
RANGE_PERSON_ID
REMOVE_ACT
REPORT_URL
RESET_PTO_ACCRUALS
RETRO_DELETE
RR BUFFER SIZE
RRV BUFFER SIZE
RUN_XDO
RR Buffer Size
RRV Buffer Size
Run XML Publisher for
Report Generation
Standard Payroll File
Names
STD_FILE_NAME
SUPPRESS_INSIG_INDIRECTS
Suppress Insignificant
Indirect Results
Quantum Cache Size
Override Quantum Version
Checking
Storage area for Taxation
Details (Quantum)
Quantum Debugging Flag
Override Location for Tax
Libraries (Quantum)
TAX_CACHE_SIZE
TAX_CHECK_OVERRIDE
TAX_DATA
TAX_DEBUG_FLAG
TAX_LIBRARIES
TGL_DATE_USED
TGL_REVB_ACC_DATE
THREADS
TRACE
TRACE_LEVEL
TR_BUFFER_SIZE
USER_MESSAGING
US_ADVANCED_WAGE_ATTACHMENT
UTF8_RESTRICTION_MODE
Transfer to GL Process
transfer on date earned
Accounting Date used for
Reversals and Balance
Adjustments
Threads
Trace
Trace Level
Taxability Rules Buffer
Size
User Messaging
Advanced Wage Attachment
Enabled
UTF8 Restriction Mode
0 or more
Y or N
0 or more
size)
(20)
15
Y
No
Timeout
See Later
Y or N
Y or N
0
1
1
Y
0
2
300
N
or
or
or
or
more
more
more
N
Y or N
Y or N
Now a
legislation
rule
1 or more
1 or more
Y or N
Y or N
20
30
Y
Y or N
N (if not
overridde
n by
legislati
ve rule)
N
0 or more
Y or N
0
N
1000
1000
See Later
Y or N
N
$PAY_TOP/
vendor/qu
antum/lib
E
C or P
1 or more
Y or N
1 (3)
N
100 or
above
Y or N
Y or N
500
BYTE or
CHAR or
UNRESTRICTE
D
BYTE
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 48
QuickPay Parameters
QuickPay Polling Interval
Parameter Name: QUICKPAY_INTERVAL_WAIT_SEC
Parameter Value: 1 or more
Default Value: 2
QuickPay Polling Interval.
QuickPay Timeout
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 49
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 50
EE Buffer Size
Parameter Name: EE BUFFER SIZE
Parameter Value: 1 or more
Default Value: 40
Size of the buffer used in the initial array selects of Element Entries,
Element Entry Values, Run Results and Run Result Values per
assignment.
Taxability Rules Buffer Size
Parameter Name: TR_BUFFER_SIZE
Parameter Value: 100 or above
Default Value: 500
Size of the buffer used in array selects from the
PAY_TAXABILITY_RULES table within the Run process.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 51
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 52
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 53
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 54
:FAIL,
:PARA
Default Value:
:SUMM,
:FAIL
ROUT Location in code from where the log entry was raised
is written to the log file
:SUMM,
:FAIL
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 55
cause. For processes that support assignment level errors you can use
the MAX_ERRORS_ALLOWED parameter to control the point at
which you want to stop the entire process to investigate these errors.
The processes that use this feature are:
Payroll Run
PrePayments
Costing
Rollback
Maximum Errors Allowed
Parameter Name: MAX_ERRORS_ALLOWED
Parameter Value: 0 or more
Default Value: CHUNK_SIZE or 20 (if no chunk size)
The number of consecutive actions that may have an error before the
entire process is given a status of Error.
Note: This parameter affects each thread. For example, if
MAX_ERRORS_ALLOWED is set to 10 and THREADS is set to 3,
this could result in the whole process raising up to 27 errors without
terminating with status error. The first thread to reach 10 errors will
cause the whole process to terminate.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 56
Logging Categories
Logging categories define the type of information included in the log.
This lets you focus attention on specific areas that you consider may be
causing a problem. You can set any number of these by specifying
multiple values:
- G General (no specific category) logging information.
Output messages from the PY_LOG macro for general information.
This option does not sort the output and you should normally choose a
list of specific categories.
M Entry or exit routing information
Output information to show when any function is entered and exited,
with messages such as In: pyippee, Out : pyippee. The information
is indented to show the call level, and can be used to trace the path
taken through the code at function call level. Often, this would be
useful when attempting to track down a problem such as a core dump.
P Performance information
Output information to show the number of times certain operations take
place at the assignment and run levels and why the operation took
place. For example, balance buffer array writes.
E Element entries information
Output information to show the state of the inmemory element entry
structure, after the entries for an assignment have been fetched, and
when any item of the structure changes; for example, addition of
indirects or updates. This also shows the processing of the entry.
L Balance fetching information
Output information to show the latest balance fetch and subsequent
expiry stage.
B Balance maintenance information
Output information to show the creation and maintenance of in
memory balances
- I Balance output information
Output information to show details of values written to the database
from the balance buffers.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 57
Logging Parameters
Logging Category
Parameter Name: LOGGING
Parameter Value: G, M, P, E, L, B, I, R, F,
C, Q, V, S, Z, T
Default Value: No logging
During installation and testing of your Oracle Payroll system you may
need to turn on the detailed logging options provided with the product.
Use the LOGGING parameter to provide a large volume of detailed
information that is useful for investigating problems.
Detailed logging options should only be switched on when you need to
investigate problems that are not easily identified in other ways. The
logging activities will have an impact on the overall performance of the
process you are logging. Usually, this feature is needed during your
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 58
Logging Area
Parameter Name: LOG_AREA
Parameter Value: Function to start logging
Default Value: No default
Specifies the area of code logging takes place for. The values
correspond to c-code entries in the form PY_ENTRY(env, "pyipppr");
where "pyipppr" is the functional area that will have logging enabled.
Assignment ID for Start of Logging
Parameter Name: LOG_ASSIGN_START
Parameter Value: Assignment to start logging
Default Value: All assignments
Specifies the Assignment id that logging starts on.
Assignment ID for End of Logging
Parameter Name: LOG_ASSIGN_END
Parameter Value: Assignment to end logging,
including this one
Default Value: All assignments
Specifies the Assignment id that logging ends on.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 59
Miscellaneous Parameters
User Messaging
Parameter Name: USER_MESSAGING
Parameter Value: Y/N
Default Value: N
Set this to parameter to Y to enable detailed logging of user readable
information to the pay_message_lines table. This information includes
details about the elements and overrides that are processed during the
Payroll Run.
Note: This information is useful when you are investigating problems,
but you may find that it is too detailed for normal working.
Maximum Iterations allowed per Run Action
Parameter Name: MAX_ITERATIONS
Parameter Value:
Default Value:
Used within the iterative engine to determine the number of iterations
to do before making the best guess.
Standard Payroll File Names
Parameter Name: STD_FILE_NAME
Parameter Value: Y or N
Default Value: N
Standard Payroll File Names.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 60
- Y If standard file names are required i.e. want output files to be in the
format p<request_id>.<extension>
- N If file names do not need to be standard i.e. file names can be in the
format <requestor>.<request_id>
Trace
Parameter Name: TRACE
Parameter Value: Y/N
Default Value: N
Set this parameter to Y to enable the database trace facility. Oracle
trace files will be generated and saved in the standard output directory
for your platform. Trace only applies to application C processes. The
following processes arent covered by this parameter:
Reversals
Balance Adjustments
External / Manual Payments
Payroll Rollback via Form
Mark For Retry
Warning: Only use the trace facility to help with the investigation of
problems. Setting the value to Y will cause a significant deterioration
in database performance. If you experience a significant problem with
the performance of your payroll processes, you should always check
that you have reset this parameter to the default value N.
HR Auto Orgs Debug Level
Parameter Name: HR_GL_SYNC_DEBUG
Parameter Value: NORMAL or DEBUG
Default Value: NORMAL
This parameter controls the debug level in the process that synchronizes
organizations between GL and HR. Set the value to DEBUG to turn
debugging on.
Sleep time for Disable HCM Access
Parameter Name: HRLEGDEL_SLEEP
Parameter Value: 0 or more
Default Value: 10
When HRGLOBAL is being run the system functionality is temporarily
disabled. This parameter controls the frequency with which the system
is polled to determine whether HRGLOBAL is complete. It specifies
the number of seconds between two successive loops of the program to
reduce CPU usage.
FastFormula Maximum Open Formula Cursors
Parameter Name: FF_MAX_OPEN_CURSORS
Parameter Value: 32 - 128
Default Value: 128
This parameter defines the maximum number of formula cursors that
are kept open within Fast Formula caches.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 61
Interlock
Parameter Name: INTERLOCK
Parameter Value: Y or N
Default Value: N
If this parameter is set to Y the assignment action creation phase of the
payroll processes will produce output for each assignment showing the
list of assignments belonging to the payroll that will and will not be
processed.
Enabling this parameter results in more work being performed - and
hence impacts performance. For this reason we only recommend
setting this parameter for debugging purposes.
JP Balance Dimension : Exclude Reversal/Reversed Results
Parameter Name: JP_DIM_EXC_REV_FLAG
Parameter Value: Y or N
Default Value: N
Used in JP sql script (run after perlegjp.pdt ) that deletes
PAY_DIMENSION_ROUTES entries, if this parameter is set to Y the
script does not delete entries that use the Exclude Reversal dimension.
JRE Library Path
Parameter Name: JRE_LIBRARY
Parameter Value:
Default Value:
Low Volume Optimizer Setting
Parameter Name: LOW_VOLUME
Parameter Value: Y or N
Default Value: N (for DB 9.0 and above)
If this parameter is set to Y then the balance user exit and database item
definitions are forced to use a RULE optimizer hint.
Setting this parameter should ensure that balance statements are
executed with optimum explain plans.
Print Files
Parameter Name: PRINT_FILES
Parameter Value: Y or N
Default Value: Y
Process Timeout
Parameter Name: PROCESS_TIMEOUT
Parameter Value: 0 or more
Default Value: No Timeout
Used in the Run Balance generation process to determine how long (in
minutes) to allow before the process times out. If no value is entered
then there will be no timeout limit.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 62
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 63
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 64
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 65
Parameter
Value
Default
Max
CHUNK_SIZE
MAX_ERRORS_ALLOWED
THREADS
Chunk Size
Maximum Errors Allowed
Threads
1 16000
0 or more
1 or more
10
20
3
16000
Value
Threads
Parameter Name: THREADS
Parameter Value: 1 or more
Default Value: 3
Oracle Benefits is designed to take advantage of multiprocessor
machines. This means that you can improve performance of your batch
processes by splitting the processing into a number of threads. These
threads, or subprocesses will run in parallel.
When you submit a batch process to a concurrent manager the
THREADS parameter will determine the total number of subprocesses
that will run under the concurrent manager. The master process will
submit (THREADS 1) subprocesses.
The recommended setting is 1 for each CPU.
Attention: The concurrent manager must be defined to allow the
specified number of subprocesses to run concurrently. This is a task
for your Applications System Administrator.
Chunk Size
Parameter Name: CHUNK_SIZE
Parameter Value: 1 16000
Default Value: 10
Size of each commit unit for the batch process. Each thread processes
one chunk at a time.
Recommended settings are:
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 66
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 67
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 68
As well as changing the INITRANS setting for the above tables, you
must also change the INITRANS setting for the indexes associated with
the tables.
Note: In order to set the INITRANS parameter for tables that already
contain data you MUST:
1.
2.
3.
PCTFREE
PCTFREE enables you to manage how the space within data blocks is
used. If you are running the application with a large number of
THREADS then there may not be enough room in the block header to
allocate to variable transactions if there are a lot of processes trying to
access the same data block at the same time.
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 69
For example,
INITRANS = 10
PCTFREE = 10
Block Size = 8K
THREADS = 36
Given these figures, the fixed block size is 287 bytes (57 bytes general
block information + 23 bytes for the first transaction locks (Interested
Transaction List (ITL)), leaving 790 bytes ((8192-287)*10%) of free
space for row and dynamically created ITL growth.
Given the THREADS setting of 36, it is possible that 36 separate
transactions may be trying to lock records in the same block in which
case the space required to hold information about the locks is 828
(36*23), in other words an additional 598 bytes. This will be consumed
from the available freespace, however as there is only 790 bytes
available, some of which may have been used for data growth, it is
possible that contention will occur due to the system being unable to
acquire the space it needs to take out the ITL locks.
The additional space required can be pre-allocated by increasing the
INITRANS to 36 (although this reduces the amount of freespace
available for growth in the row data.)
Alternatively the PCTFREE can be increased to cater for the additional
dynamically allocated ITL, for instance if the PCTFREE was increased
to 20 then there would be an additional 790 bytes available.
INITRANS
PCTFREE
Block Header
ITL pre-allocated
Remaining Space
Free Space based on PCTFREE
Space required for dynamic growth in
ITL (36 THREADS)
Space remaining for data growth
% remaining for data growth
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Default
Setting
Increase
INITRANS
Increase
PCTFREE
10
10
57
230
7905
790
598
36
10
57
828
7307
730
0
10
20
57
230
7905
1581
598
192
2.3%
730
8.9%
983
12.0%
Page 70
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 71
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 72
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 73
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 74
Oracle HCM & Benefits Tuning and System Health Check 11i & R12
Page 75