23-Sep-15

Oracle HR Requirements Specification Document

Page 1

Revision 1.0

Project Accounting Interface

Section Number

Author

Date

Overview
The purpose of this modification is to allow entry of project and task information on the timecard
within OTM. Once the information is entered then it is transferred to the PA system via the
PA_TRANSACTION_INTERFACE_ALL table.
It allows Oracle Project Accounting projects and tasks information to be assigned at the summary
level on the OTM timecard. LOVs for the project and tasks items will be populated by projects and
tasks from the Oracle Project Accounting tables. Transaction controls will be enforced on all
selections through the standard transaction controls API. Transfer of relevant timecard details to
Project Accounting will be implemented through stored procedures using the Oracle Applications
Concurrent Manager.
This is not an interface between Oracle Project Accounting and Oracle HRMS. The interface only
process elements entered on the OTM timecard. It does not transfer cost for elements within the
payroll system. For example, an employee had a timecard with 40 hours for project A and on his
element entries, he had a recurring element that pays him a living allowance of $40 per week. The
transfer to PA would send transactions for the 40 hours to the PA interface table. However, it would
not send any transactions for the $40 living allowance to Project Accounting.
The process is designed to run after the transfer to PayMix process within the OTM system. In
addition, the process is designed to run on the same cycle as the payroll. For example, if the payroll
cycle is weekly, then the transfer process would be ran on a weekly basis. If the cycle is bi-weekly,
then the transfer process would be ran on a bi-weekly basis.
The process does support changes to timecards that have already been transferred to Project
Accounting. Basically, there is a PA retro process that should be ran after the normal PA transfer
process. On each timecard, we maintain a payroll and Project Accounting status. This process looks
for any summary timecard records that have had any Project related information changed. Items such
as project, task, rate, number of hours, hours type, etc. The process then determines the difference
between the original record and the current record and sends the necessary transactions to Project
Accounting. For example, a summary record for project A was changed from 4 hours to 6 hours.
Then a transaction for 2 hours would be sent to the Project Accounting interface table.
Current Business Rules
The current OTM timecard accesses projects and tasks defined within the OTM product. These
projects and tasks are defined in OTM and used for reporting purposes only.
Detailed Requirements
Essential

(E - Essential, D - Desirable)

The OTM Project Accounting interface is broken down into three parts. First, is the selection
of the project and task information from the timecard. Second is the validation of the project
and task information that was entered. Finally, the last process is to transfer the information
from the timecard to the Project Accounting system.
OTM contains functionality for project and task information. This is for the customer that
does not have the Oracle Project Accounting system. This function is fairly simple and lacks
in-depth features. It is used for reporting information only. The OTM system will be
delivered with two views. One that points to the OTM project and task tables and another
one that points to the Oracle Project Accounting project and task tables. The LOVs for the
Project and Task fields are based upon these views. The customer will need to install the
latter view as a post install step if they want to use Oracle Project Accounting with OTM. The
view for the project LOV is based on the PA view PA_PROJECTS_EXPEND_V and the view
for the task LOV is base upon the PA view PA_TASK_EXPEND_V. The customer can not use
R

Company Confidential

23-Sep-15

Oracle HR Requirements Specification Document

Page 2

Revision 1.0
both the OTM project/task information and the Project Accounting information together. They
must use one or the other.
After the project and task information has been entered on the timecard, the Project
Accounting API for Transaction control is called to validate the project and task information.
This validation is based upon the Transaction Control information established within Project
Accounting. If the Transaction Control API returns an error, the user is not allowed to save
the timecard until the error is resolved. Generally, the user will need to change either his
project or task information.
The actual transfer of timecard data to Project Accounting will be done using stored
procedures and the Oracle Applications Concurrent Manager. Transfer processing will
include:
Transfer of all pending timecard details for a specified time period
Proper selection of salary rate for the employee being processed, when no override rate
has been entered
Identification and calculation of all applicable premiums and pay multiples associated
with elements entered on the timecard
Transfer of all flat amounts entered on the timecard or associated with the pay element
currently being transferred
The status of each row processed will be flagged to show completion at the detail level
Transfer of timecard adjustments will also be possible through a separate concurrent
manager process
The actual interface to Project Accounting will be done by inserting detail rows into the
PA_TRANSACTION_INTERFACE_ALL utilising the standards described in the
Oracle Financials and Oracle Government Financials Open Interfaces Manual
Below is a table mapping of the PA_TRANSACTION_INTERFACE_ALL table with the
fields from the OTM system.
PA_TRANSACTION_INTERFACE_ALL
Name
--------------------------TRANSACTION_SOURCE
BATCH_NAME
EXPENDITURE_ENDING_DATE
EMPLOYEE_NUMBER
ORGANIZATION_NAME
EXPENDITURE_ITEM_DATE
PROJECT_NUMBER
TASK_NUMBER
EXPENDITURE_TYPE

OTM Base System Source

--------------------------------------------------------Time Management
INITIAL for regular time entry
pa_misc.get_week_ending_date (I_date_worked)
per_people_f.employee_number
hr_organization_units.name
hxt_det_hours_worked_x.date_worked
pa_projects.segment1
pa_tasks.task_number
cursor exp_type is
select eltv.hxt_expenditure_type
from hxt_pay_element_types_f_ddf_v eltv,
pay_element_types_f elt
where elt.element_type_id = I_element_type_id
and eltv.row_id = elt.rowid;
NON_LABOR_RESOURCE
NULL
NON_LABOR_RESOURCE_ORG_NAME
NULL
QUANTITY
hxt_det_hours_worked_x.hours or 1
RAW_COST
QUANTITY * RAW_COST_RATE or
pay_element_types_f_dfv.hxt_premium_amount or
hxt_det_hours_worked_x.amount
EXPENDITURE_COMMENT
NULL
TRANSACTION_STATUS_CODE
P
TRANSACTION_REJECTION_CODE
NULL
EXPENDITURE_ID
NULL
ORIG_TRANSACTION_REFERENCE
hxt_det_hours_worked_x.effective_start_date ||
Hxt_det_hours_worked_x.effective_end_date ||
hxt_det_hours_worked_x.id
ATTRIBUTE_CATEGORY
NULL
ATTRIBUTE1
NULL
ATTRIBUTE2
NULL
ATTRIBUTE3
NULL
ATTRIBUTE4
NULL
ATTRIBUTE5
NULL
ATTRIBUTE6
NULL
ATTRIBUTE7
NULL

Company Confidential

23-Sep-15

Oracle HR Requirements Specification Document

Page 3

Revision 1.0
ATTRIBUTE8
ATTRIBUTE9
ATTRIBUTE10
RAW_COST_RATE

NULL
NULL
NULL
per_pay_proposals.proposed_salary(hour rate) or
hxt_det_hours_worked_x.hourly_rate or
per_pay_proposals.proposed_salary(hour rate) *
hxt_det_hours_worked_x.rate_multiple or
per_pay_proposals.proposed_salary(hour rate) *
pay_element_types_f_dfv.hxt_premium_amount or
pay_element_types_f_dfv.hxt_premium_amount /
hxt_det_hours_worked_x.hours or
per_pay_proposals.proposed_salary(hour rate) *
(pay_element_types_f_dfv.hxt_premium_amount - 1) or
NULL
INTERFACE_ID
NULL
UNMATCHED_NEGATIVE_TXN_FLAG NULL
EXPENDITURE_ITEM_ID
NULL
ORG_ID
NULL -- PA interface does not support Multi Organization
-- set up. This interface can only be used in single Org.
DR_CODE_COMBINATION_ID
NULL
CR_CODE_COMBINATION_ID
NULL
CDL_SYSTEM_REFERENCE1
NULL
CDL_SYSTEM_REFERENCE2
NULL
CDL_SYSTEM_REFERENCE3
NULL
GL_DATE
NULL

The expenditure type is defined as a segment on the Further Information of an element. The
LOV for this segment is defined by the valid expenditure types within the Project Accounting
System. This gives the customer the flexible to assign elements to whatever expenditure
types that they have defined within the Project Accounting system.
For the calculation of yearly, monthly, period salary people the system uses a profile named
HXT_HOURS_PER_YEAR. The purpose of this profile is to define the work hours in a year
for the calculation to convert period salaries to hourly rates. For the transfer to Project
Accounting to function correctly this profile must be set, even if all employees are hourly
employees.
Rationale or Origin of the Requirement
Due to customer request
Related Requirements and Pending Enhancements (including prerequisites)
Not applicable
Special Considerations (e.g. performance, mission criticality, u/i, testing, localisation, legislation)
Not applicable
Envisaged Usage
This process will be used by customers who want to capture their time information for both payroll
and project accounting on the timecard. In its current form, it most likely will be used by customers
that are on a weekly payroll and are not concern that the dollar amounts in Project Accounting and
Payroll match to the penny.
Interfaces (with other processes, functions etc.)
Interface with Oracle Project Accounting transaction controls.
Security Issues
Entry of projects and tasks are allowed on all timecard summary level entries.
Error Handling
All transaction control errors are returned to the user at the timecard.
Project Accounting transfer errors will be reported as standard timecard errors and can be viewed on
the OTM Time Entry Errors form. Project Accounting transfer processing will continue for all
timecards not in error.
Additional Reporting Requirements
Not applicable

Company Confidential

23-Sep-15

Oracle HR Requirements Specification Document

Page 4

Revision 1.0
Rejected Alternatives to, or Parts of, the Requirement
Not applicable

-------------------------------------------------------------------------------------------------------------------------------

Appendix A:
To ensure that a successful transfer of data from OTM to PA is carried out the following steps
must be followed.

1. The HXT_HOURS_PER_YEAR is defined and has a value (This is a system profile

value; if not present, create it through app. developer).
2. The employee has a valid pay bases and salary associated to him (use
the salary admin form).
3. The element has a vaild Expenditure type (Element Description, DFF and
fill in the expenditure type from PA).
4. The project and Tasks are entered on the timecard for the element
which has already got an associated expenditure type.
5. Make sure the customer applies the hxtcrets.sql, to create
the transaction source for Oracle Time Management.
6. Validate the timecard, transfer to Paymix, and transfer to PA.
7. At this point, having done all the above steps you should be able to
see new entries in the pa_transaction_interface table.

Company Confidential