Beruflich Dokumente
Kultur Dokumente
Release12.1.1
White Paper
Oracle Projects Suite combines multiple applications to work together to provide a complete enterprise
Project management solution. They give you a flexible approach to defining and managing your projects and
the people, schedules, deliverables, and finances associated with them.
Projects enable project managers to oversee their projects, assess progress against predetermined
milestones and budgets, staff their projects with appropriate talent, and quickly generate a wide variety of
reports. It also helps virtual and globally distributed project teams to efficiently communicate, collaborate,
and complete tasks.
Oracle Projects also gives corporate executives the ability to quickly see how projects are performing across
the enterprise. It enables them to drill down to areas of geographical interest or product specialization to
review projects that are potential problems or are in immediate need of additional attention.
Project Costing gives operations managers and finance managers complete and timely access to project
performance and resulting accounting impacts thereof. It also empowers line managers with timely, detailed
cost information to monitor project performance in a productivity-enhancing format, and enables financial
managers to track the total cost of running the business.
The project type controls how Oracle Projects creates and processes projects, and is a primary classification
for the projects your business manages. You must set up at least one project type to create projects in
Oracle Projects. Project Types are user defined and are based on project class. There are three project
classes: Indirect, Capital and Contract.
Select Classification Categories to group projects from the list, which can be selected for
project based on this type
Description Description for specified category will be displayed here
Mandatory Enable this for all projects of this project type to be associated with selected category
Non Project Budget This field is used to define top-down and bottom-up budget integration.
For Bottom-Up Budget Integration: Select a GL budget from LOV. LOV
displays budgets with a status of Open or Current.
For Top-Down Budget Integration: Select GL Funding Budget from list
For No Integration (Independent Budgetary Controls): Leave field blank
Levels – Project Select “Absolute” from the list for complete control
Levels – Tasks Select “Absolute” from the list for complete control
Levels – Resource Select “None” or “Default from Resource List” from LOV based on business needs
Groups
Levels – Resources Select “None” or “Default from Resource List” from LOV based on business needs
Time Phase – The system uses these values to calculate available funds. Select an Amount Type
Amount Type to determine the beginning budget period.
Time Phase – The system uses these values to calculate available funds. Select a Boundary Code
Boundary Code to determine the ending budget period
The project status of the new project is the same as the current status of the existing
project or project template, unless that starting project status is invalid for the project
type. In that case, the starting project status set in the Starting Project Status field for
the project type.
Use Workflow for Tick checkbox to initiate workflow based project status changes. Oracle workflow is
Project Status activated.
changes
Use Workflow for Tick checkbox to initiate workflow based budget status changes. Oracle workflow is
Budget Status activated.
changes
Once all details are entered in all the tab pages, save the record and close the window.
Use this option to create and update tasks and task details for the financial structure. Tasks are elements of
the project that are contained in the project structures. Additional tasks at same level can be created using
“Create Peer Task Button”. Subtasks can be created using “Create Subtask” button as shown above.
Once all tasks are created, save the records and close the window. Select a task and click “Options” button
to see more details about the task and edit information about the task
Once all details about the task are entered, and then close all windows to come to project main page. Click
on Classifications option to enter details.
Once details are entered, close the window and come to main page. Click on Currency to view, change
project currency.
When a new project is created, the default value for the project currency code is copied from the functional
currency defined in the Implementation Options for the project-owning operating unit. You can override the
default currency code and enter default conversion attributes for the project in the Costing tab of the
Currency window.
Once details are entered, close the window and come to main page. Click on Key Members option to add
employees to the project.
Additional Information
Use the Additional Information window to enter project-level values or default values.
Pipeline
You can track sales opportunities for your pipeline projects by recording the probability of winning each
project, the expected approval date, and the value of the project. You can define probability values based on
how your company does business. For example, you can define values such as:
100% Contract Processed
60% Expect to Win
0% Project on Hold
Pipeline Window
The Pipeline window contains the following fields, which are used to calculate the weighted project value of
jobs:
Organization Overrides
You can reassign an employee's, or an entire organization's, costs and revenue to a different organization
for a particular project. You can override all of the costs and revenue of an employee or organization, or you
can redirect costs and revenue to another organization only for the expenditure categories you specify.
When you enter an organization distribution override, the new organization you enter overrides the
expenditure organization Oracle Projects uses in AutoAccounting and to determine the organization to use
for burdening.
For AutoAccounting processing, if an organization distribution override exists, the destination organization of
the override is substituted for the actual expenditure organization of affected items.
Transaction Controls
You can use transaction controls to configure your projects and tasks to allow only charges that you expect
or plan. You can define what items are billable and non-billable on your contract projects. You can define
what items are capitalizable and non-capitalizable on your capital projects. You can configure transaction
controls by the following: Expenditure Category, Expenditure Type, Non-Labor Resource, Employee,
Scheduled Expenditure Only, Workplan Resources Only, Person Type
A burden schedule is used to derive the total cost amount. You assign the cost burden schedule to a project
type that is burdened; this default cost burden schedule defaults to projects that use the project type; and
then from the project to the tasks below the project. You can override the cost burden schedule for a project
or a task if you have defined the project type option to allow overrides of the cost burden schedule.
Press Find button, once any of the fields are entered. The template details will be displayed.
To Define New Project click on COPY TO (T) and enter Project Number and Project Name and Click on OK.
If we need more fields in Project Quick Entry, then we can add them while defining the Project Templates.
We can also decide whether these fields are mandatory or optional.
The new project is created automatically and can be viewed from the window. Click on Find button to see
the details about the project.
Once all options are entered for a project, then we can change project status from Unapproved to Approved.
N: Budgets
When Budget is Submitted status, no changes are permitted. If any changes are necessary to this budget,
then change the status to “Working” by clicking the “Rework” button. To Baseline and freeze Budget, Click
on Baseline button.
We can see all versions created for this budget in History window. We can also copy the budget to another
budget.
Costing Processes
Note: You can choose Unreleased from the Status poplist in the Find Expenditure Batches window to
retrieve both Working and Submitted expenditure batches.
Oracle Projects validates expenditure item information as you enter it. For each expenditure item, enter the
following information:
Now click on Submit/ Release buttons one by one to submit the batch for approval/ release for cost
distribution.
To Review the Expenditure Batches, Enter Required Information and Click on FIND button
2) Submit the above programs from Expenditure Inquiry window using stream line process:: To find Project
Expenditure Items
4. To Distribute Costs Click on RUN REQUST button and Select Streamline Processes (The first two are
combination and must be selected together). Once checked, Click on OK to run the programs.
Click on ITEM DETAILS button Select Cost Distribution Lines and click on OK
Submit Request (PRC: Generate Cost Accounting Events), Leave the parameters blank.
Submit Request (PRC: Create Accounting), Leave Process Category Blank, but select Report: Details to see
output.
N: Allocation
You can create the allocation pool from a fixed amount, open projects (including resources within a project),
Oracle General Ledger account balances, and projects defined by a client extension.
Important: Unless you define each source project and task individually, the results may change each time
you run the allocation. The rule accumulates the amounts for the source pool during a specific period of
time. The end date of that time period is based on the amount class. (The amount class is the period or
periods during which the amounts are accumulated and is set in the Sources window.) The start date is
determined by both the Allocation period type (either GL or PA, as set in the Allocation Rule window) and
Amount class
You must define at least one source. All source projects and tasks must be open and from the same
operating unit. This means that tasks must be the top or lowest level task. The exception report for the
allocation run lists any duplicate projects.
In the Allocation Rule window, choose Sources. The Sources window opens.
In the Allocation Pool % field, enter a percentage to specify how much of the source pool to allocate.
The default is 100%. Next, you specify the amounts that you want to include in the source pool.
(Optional) In the Fixed Source Amount field, enter an amount that you want to include in the source
pool.
For Amount Class, select from the list. The field name is preceded by GL or PA, depending on the
allocation period type you selected in the Allocation Rule window.
(Including project sources in the source pool is optional.) For Amount Type, select from the list of values.
Specify the projects whose amounts you want to include in the allocation pool. If you want to use
projects that are designated in the Allocation Source client extension, select Use Client Extension
Sources. If you want to use one or more projects that you designate, enter a number greater than 0 for
Line Num, You can enter project information in the following fields: Project Org, Project Type, Class
Category, Class Code, Project, Task. To exclude a line, select the Exclude check box on the appropriate
line.
Note: If the system does not display a list of values for Project and Task, it is possible that you entered a
combination of project organization, project type, class category, class code, or other attributes for which no
project (or task) exists. If you do not enter a task, the rule uses the amounts for all the tasks on the source
line. You can add columns (Project Name, Service Type, Task Name, and Task Org) to the Sources
window.
Target Selection When you select targets on the Targets window, you can select projects owned by the
entity. If you select Legal Entity, Business Group, or All, you must set up your system to use cross charge
and
Intercompany billing
Submit Request (PRC: Generate Allocations Transactions) and check the output
PO and AP use Account Generator to determine default account number for each project-related distribution
line based on project information that you enter in the document. For this purpose, it is necessary to
customize the work flow (Account Generator) to populate accounts.
Projects is integrated with Purchasing and Payables applications using Commitments and Budgetary
Control. As part of the demonstration, Purchase Requisitions, Purchase Orders and Supplier Invoice are
entered. Seven transactions are entered as follows:
The first six transactions appear as commitments in projects and seventh transaction as actual cost. In case
of commitments, there is no need to run any concurrent program except PRC: Update Summary Amounts to
view the balances in PSI window.
Purchase Requisitions and Purchase Orders must be entered as Expense Line Items. Project related
information Project Number, Task Number, Expenditure Organization, Expenditure Date and Quantity are
entered in Distributions area as shown below:
PO can be created using Manual and Automatic options. Try both options for testing the cycle.
Project data is available in Distributions window. Press Distributions button and go to Project tab page.
Close all windows and come to the main page. Press Approve button to approve the PO.
Once receipt is saved, note down the receipt number and then verify this in Receiving Transactions
Summary window. At this point of time, submit Create Accounting Program for PO Receipts and post them
to GL. In GL, source is Cost Management and category is Receiving.
Employee enters the time sheet in OTL and submits for approval
Supervisor approves the time sheet after verification of hours. This can also be controlled through a
profile option where auto approval is also possible (PA: Auto Approve Time Cards)
Submit the concurrent program PRC: Transaction Import with Transaction Source: Oracle Time and
Labor
Time cards are available in Expenditure Inquiry window
Login to OTL and click on Time Cards. Click on Create Timecard button.
Enter project number, task number, expenditure type and hours per day. It is possible to enter multiple
projects in a day. Press Continue button to enter for multiple days. Once all details are entered, then press
Submit button for supervisor approval. The employee and supervisor relationship is already defined in
Define Employee window. If we want to change approver, we can also override approver. Templates can
also be kept ready to save time in data entry.
Once time card is submitted for approval, login as supervisor and approve the time card. Once card is
approved by supervisor, then card status changes to Approved
Now switch over to Projects and submit the Concurrent Program. N) Transactions -> Import. The
expenditure batch name is automatically populated by Oracle. Verify the execution report output for results.
Oracle Projects is integrated with inventory for issue and receipt of material for projects. These are entered
as miscellaneous transactions. Separate Transaction Types need to be created and kept ready. Login into
Inventory (Vision Services) responsibility to complete the transaction flow demonstrated below. The steps
are as below:
You can see on-hand quantity here. Details are available in “Availability” window as well.
Step 3: Once material is issued, material costing must be performed. Launch Interface Manager (Cost
Manager) to cost the transactions
Usually the status would be inactive. In case it is active, that means the concurrent program is scheduled.
Go to View Requests window and Cancel the program. Then it becomes inactive again.
Launch the manager by clicking Tools -> Launch Manager Option. This opens the concurrent program
window. No parameters are required. Simply press submit button to run the program.
Submit the concurrent program: Accounting Close Cycle -> Project Cost Transfers
There is no output for both the programs. However log is available for Cost Collection Manager to indicate
that it has selected the item cost.
Step 4: Switch to Oracle Projects now. Submit Transaction Import Concurrent Program. Note that Batch
Name is available for selection. This is generated during previous run.
Step 5: Verify the expenditure items in the Expenditure Enquiry -> Project Window
Now click on Item Details button to all distribution details and a/c heads. Note that the a/c entries will be
transferred by Cost Management to GL directly and no entries will be generated by projects.
You define and build capital assets in capital projects using information specified in the project work
breakdown structure (WBS). You define asset grouping levels and assign assets to the grouping levels to
summarize the CIP costs for capitalization.
You can review and adjust capital project costs before and after capitalization. For example, you can
allocate costs collected under common tasks to multiple CIP assets before you place them in service. You
can also account for additional costs incurred after capitalization, since Oracle Projects allows you to place
assets in service before completion of a project.
When a CIP asset is ready to be placed in service, you send the capital project amounts to Oracle Assets as
asset lines. Oracle Assets places the asset lines in a holding area where your fixed assets department can
post the capital costs in Oracle Assets as fixed assets. You can review detail transactions associated with
the asset lines in Oracle Projects and Oracle Assets. If necessary, you can reverse capitalize an asset in a
capital project.
You capture retirement costs in a capital project by recording cost of removal and proceeds of sale amounts
to a task that is designated as a retirement cost task. To distinguish cost of removal and proceeds of sale
amounts, you must enter proceeds of sale amounts using expenditure types that you define to specifically
classify these amounts. Oracle Projects automatically classifies amounts for all other expenditure types as
cost of removal.
To associate retirement costs with a group asset in Oracle Assets, you create a retirement adjustment asset
in the capital project and identify it with a specific group asset. As with capital assets, you define asset
grouping levels and assign retirement adjustment assets to the grouping levels to summarize the retirement
cost amounts for posting to Oracle Assets.
When retirement activities are complete, you generate asset lines for the retirement cost amounts and send
the lines to Oracle Assets for posting as adjustments to the accumulated depreciation accounts for the group
assets. To communicate notice of an asset retirement to Oracle Assets, you can optionally initiate retirement
requests in Oracle Projects that are automatically passed to Oracle Assets.
Attention: To use Oracle Projects retirement cost processing windows and features, the value of the site-
level profile option PA: Retirement Cost Processing Enabled must be set to Yes.
You create retirement adjustment assets to collect cost of removal and proceeds of sale amounts for assets
associated with a group asset in Oracle Assets that you are retiring, removing, abandoning, or otherwise
disposing.
When you define a retirement adjustment asset in Oracle Projects, you must specify a valid Oracle Assets
group asset identifier as the target asset. You can create retirement adjustment assets and interface
retirement costs to Oracle Assets only for fixed assets that are classified as group assets in Oracle Assets.
To interface a retirement adjustment asset to Oracle Assets, you must specify a retirement date for the asset
in Oracle Projects.