To process a retirement request: To view retirementsgreenchain.biz/PDF/R12Projects_White_Paper_Part_II.pdf · You can initiate a retirement request in Oracle Projects to identify

GreenChain Software Solutions Pvt. Ltd. Page 67 of 210

You can initiate a retirement request in Oracle Projects to identify one or more assets that you are retiring from service. Retirement requests serve as an advice that you can use to notify your fixed asset department about assets that need to be retired in Oracle Assets.

To process a retirement request:

1. Navigate to the Capital Projects window and choose the Requests button to open the Retirement Requests window. 2. Choose the Create New Request button to open the Mass Retirements window and specify any combination of asset attributes to find one or more assets you want to retire. 3. Save your work.

After a retirement request is processed in Oracle Assets, you can return to the Retirement Requests window in Oracle Projects to view the retirement information.

To view retirements:

1. Navigate to the Capital Projects window and choose the Requests button to open the Retirement Requests window. 2. Select a retirement transaction you want to view and choose View Retirements. Allocating Asset Costs

You can specify an asset allocation method to enable Oracle Projects to automatically allocate unassigned asset lines and common costs across multiple assets. Unassigned asset lines typically occur when more than one asset is assigned to an asset grouping level.

You can specify a default asset allocation method for a capital project type and override it at the project level. You can select one of the following asset allocation methods:

Actual Units: Costs are allocated based on the number of actual units specified for each asset in the Assets window

Client Extension: Costs are allocated based on the Asset Allocation Basis extension Current Cost: Costs are allocated based on the grouped CIP cost of each asset. Estimated Cost: Costs are allocated based on the estimated cost specified for each asset in the Assets

window. Standard Unit Cost: Costs are allocated based on a standard unit cost defined for the asset book and

category in the Project Assets Standard Unit Cost window. Spread Evenly: Costs are allocated evenly based on the number of assets being capitalized for the

project or the event.

Step 1: Create a project Type with Class Capital, enter required information and go to Capitalization Information Tab enter required information as shown below.


Step 2: Create a Template using Project Type and create a Tasks One to Three for Capitalizable, Task Four for a Common Cost, Task Five for Retirement Cost and select Key member as shown below.


Step 3: Create a Project using Project Template and change status of project from Unapproved to Approved as shown below.


Step 4: Enter expenditure for Capital Project and Submit, Release the Expenditure batch as shown below.


Step 5: To distribute miscellaneous cost submit the concurrent program and find out the output as shown below


Step 6: To Interface miscellaneous costs from Projects to General Ledger submit the concurrent program and find out the output as shown below.


Step 7: To Update Project summary amounts submit the concurrent program as shown below.

Step 8: To see the Capital Project Summary Amounts enter details in Capital Projects window and click on Find button, to create Assets click on Assets button, in assets window enter assets details including Project Asset Type as Estimated, to capitalize the cost change the Project Asset Type as As-Built and enter the actual date in service, to assign assets click on Asset Assign button and enter the details in asset assign window as shown below.


Step 9: To generate asset lines click on Generate Asset Lines button, find out the output, after completion of the program Oracle creates asset lines, to see asset lines click on Lines button, and to see task amounts click on Task Amounts button as shown below.


Step 10: To interface assets lines from projects to assets submit concurrent program and find out the output as shown below.


Step 11: To find out the assets switch over to Assets, complete the Prepare, Post Mass Additions process then you can see assets in assets window as shown below.


13. Cross Charge

Enterprises face complex accounting and operational project issues that result from centralized project management through sharing of resources across organizations. Oracle Projects provides the following cross charge features to address these issues:

Borrowed and Lent Accounting: This feature creates accounting entries to pass costs and revenue across organizations without generating internal invoices.

Intercompany Billing Accounting: This feature creates internal invoices and accounting entries to pass costs and share revenue across organizations.

In addition to these two features that enable you to charge costs across organizations, Oracle Projects inter-project billing features enable you to charge costs between projects. Cross charge features depend on multiple organization support in Oracle Projects and other Oracle Applications. In addition, these features support multinational projects, which also call for other currency exchange management functionality.

Note: To use the intercompany billing feature (for cross charge) you must implement both Oracle Project Costing and Oracle Project Billing.

Figure 1: Overview of Cross Charge Processing Flow

Step 1: In Implementation Options window, select the Cross Charge tab and enter required information as shown below.


Step 2: Create a Transfer Price Rules as shown below.


Step 3: Create a Transfer Price Schedules as shown below.

Step 4: Create a Provider and Receiver Controls as shown below.


Step 5: Create a Project using existing project and enable Cross-Charge at Project, Task level as shown below.


Step 6: Enter Expenditure for project using two expenditure Organizations and submit the concurrent program to distribute costs and verify the expenditure in expenditure inquiry window as shown below.


Step 7: To distribute borrowed and lent amounts submit the concurrent program and notice the change as shown below.


Step 8: To Interface cross charge distributions to General Ledger submit the concurrent program and find out the output as shown below.


Step 9: To see the Cross Charge method, Provider, Receiver Organizations from Expenditure Inquiry window follow the process as shown below.


14. Overview of Oracle Project Billing

Oracle Project Billing provides you with the ability to define revenue and invoicing rules for your projects, generate revenue, create invoices, and integrate with other Oracle Applications to process revenue and

invoices. Oracle Project Billing also integrates with Oracle Receivables. Oracle Project Billing enables you to perform the following functions: Enter project customers and contacts with whom you have negotiated and contracted project work Enter agreements (contracts) from your customers and fund projects with those agreements Generate revenue using various methods including time and materials, percent complete, and cost plus Create draft invoices from detail transactions and milestones for online approval by your project or

accounting managers Interface revenue to Oracle General Ledger and invoices to Oracle Receivables while maintaining a

detail audit trail Report project revenue, invoice, and receivables status online and in reports You use contract projects to track activities, cost, revenue, and billing for services performed for and

reimbursed by a customer. a) Create Project Type. In Details Tab Enter Service Type, and Work Type

N) Setup-Projects-Project Types

In Budget Option Tab Enter Cost, Revenue budget entry methods and Resource List


In Billing Information Tab Select Funding Level, Billing Job Group, Rate Schedules, Invoice Formats, Billing Cycle and Enable Baseline Funding without Budget Check box.

In Distribution Rule Tab Enter One Default Rule. We can select multiple rules for one type. Only one among them can be selected as default. This will appear in the project, which can be modified as required. There are seven distribution rules, which are seeded.


In Project Status Workflow Tab Enter Starting Project Status and save your work

b) Create Template. To create template click on New button N) Setup-Projects-Project Templates

In Template window enter template number, name, and type, project owning organization, long name, date and select Task option to define tasks. We can notice that status is Unapproved, which we selected in Project Type.


In Task window enter task name, description, date. To see Task details click on Options button

In Task Options window double click on Task Detail Option.

In Task Details window for Contract Projects Billable Check box enabled and Save your work


In Templates window select Customers and Contacts option to enter customers and contacts. In Customers window enter customer and contacts. In this window, we can select one more customers and contribution can be split among customers.

In Key Members window enter key member, role, date and save your work. Project Manager is mandatory for Contract Projects.


c) Create Projects. To create project, select Template and click on Find button N) Projects

Click on Copy To button

Enter Project Number, Name and click on OK button

To open project click on Open button


In Project window enter date and change the status. To change the status click on Change Status button.

Select Approved click on OK button and save your work

To enter Expenditure Batch for the contract project entered above, enter batch name, ending date, class. To enter Expenditures click on Expenditures button. As our distribution rule is Cost/ Work, we need to incur expenditure against the project to create revenue and generate invoice. N) Expenditures- Pre Approved Batches- Enter


In Expenditure window enter expenditure organization and expenditure items save your work

Submit and Release Expenditure Batch


To distribute miscellaneous cost submit concurrent program

Miscellaneous cost distributed


To see Project Expenditure Items enter project number and click on Find button N) Expenditures > Expenditure Inquiry > Project

To Interface Miscellaneous Cost from Projects to General Ledger submit concurrent program


Miscellaneous cost Transferred


15. Customer Agreements

In Oracle Projects, an agreement represents any form of contract, written or verbal, between you and one of your customers. For example, an agreement may correspond to a purchase order, a continuing service agreement, or a verbal authorization. An agreement provides the funding for projects and tasks. Each agreement you define includes the following items: A customer A hard or a soft limit for revenue and/or invoice A currency amount An organization that owns the agreement If you specify hard revenue and invoice limit on an agreement, Oracle Projects prevents revenue accrual and billing activity beyond the amount you funded to a particular project or task. If you specify soft revenue and invoice limit, Oracle Projects provides a warning telling you when revenue and billing for the project exceeds the amount you funded. Note: You can specify a hard limit for both revenue and invoice limit, or a hard limit for revenue or invoice limit. No project or task can accrue revenue without an agreement to fund its revenue budget

Entering Agreements

You can enter an agreement representing a purchase order, retainer letter, or any other funding agreement you make with a customer in any currency regardless of your project functional currency. When you record an agreement, you can specify payment terms for invoices against the agreement, and whether there are limits to the amount of revenue you can accrue and bill against the agreement. From the Agreements window, you can open the Funding window to allocate funds to one or more projects (or to top tasks within a project), and to see how much unused funding remains for an agreement. Each agreement that funds a project can be entered in a different currency. For any agreement, you can review the revenue and billing activity associated with the agreement, such as the amount of revenue accrued, the amount invoiced, and the amount of funding that is allocated and has a baseline. All revenue and invoices in Oracle Projects are recorded against an agreement, and all items that accrue revenue against an agreement subsequently bill against the same agreement. To enter an agreement: 1. Navigate to the Agreement window. 2. Enter the Customer who is providing the agreement funding. 3. Enter a Number to identify this agreement, such as the customer's purchase order number. The agreement number must be unique for this customer and agreement type, although two customers can each have an agreement with an identical agreement number. Attention: You cannot change this number once you create an invoice against this agreement and interface the invoice to Oracle Receivables. 4. Enter an agreement Type. 5. Choose the currency code of the agreement from the list of values. The list of values is restricted to the currencies defined in Oracle General Ledger. Note: The currency field can only be updated if the Multi Currency Billing implementation option is enabled at the operating unit and the funds have not been allocated. 6. Enter the Amount of this agreement. 7. Enter the payment terms (defined in Oracle Receivables) for any invoices funded by this agreement. 8. Choose the Revenue Hard Limit or/and Invoice Hard Limit check box to impose a hard limit on revenue accrual and invoice generation for projects funded by this agreement. Otherwise, Oracle Projects imposes a soft limit.


A hard limit prevents revenue accrual and invoice generation beyond the amount allocated to a project or task by this agreement. A soft limit issues a warning when revenue accrual and invoice generation exceed the amount allocated to a project or task. 9. Enter the date this agreement expires. If you do not want to enforce an expiration date, leave this field blank. If you generate draft revenue or an invoice for projects funded by this agreement after the agreement expiration date, Oracle Projects creates distribution warnings for revenue and invoices. 10. Optionally enter a Description of this agreement. 11. Enter the administrator of this agreement. Note: An agreement administrator can be a future-dated employee. However, this is not recommended or likely, because agreement owners are almost always current employees. 12. Enter the name of the organization that owns the agreement. Note: You can choose any project owning organization (in the project owning organization hierarchy assigned to the operating unit) as the organization that owns the agreement. 13. Enter a Creation Date. 14. Save your work.

Project Funding You must fund a project before the project can accrue revenue and be billed. Funding is the step that allocates an amount associated with a customer agreement to a specific project. The total amount of allocated project funding must equal the current approved project revenue budget amount in order to successfully baseline the project. Optionally, top tasks on projects can be individually funded. If top tasks are funded, then the same requirement of matching budget amounts to funding amounts applies at the top task level of the project. Oracle Projects allows you to define agreements, projects, and tasks to organize your project work represents an example of how you can use an agreement to fund multiple projects and tasks. Funding Multiple Projects and Tasks

In this example, a single agreement is used to fund four projects. The agreement has a total value of $150,000. The amount funded is $125,000. Project A, a time and materials project, is funded at $50,000 at the project level.


Project B, a fixed price project, is funded at $25,000. It has a work breakdown structure with two tasks, namely Task 1.0 and Task 2.0. Task 1.0 is funded at $10,000. The remainder of the funding for Project B is assigned to Task 2.0. Task 2.0 has three sub-tasks: Task 2.0.1, Task 2.0.2, and Task 2.0.3.

Project C, a cost plus project, is funded at $50,000. Project D, a bid and proposal project, has been funded with $0. While this does not allow the project to

generate any revenue, it gives the user a link to relate specific bid & proposal projects to agreements for reporting purposes

Funding Across Operating Units You can fund different projects across operating units by enabling the Allow Funding Across Operating Units functionality in the Billing tab of the Implementation Options window. In the Agreements window enter agreement details and to enter Funding details click on Funding button. N) Billing-Agreements

Enter agreement number, type, currency and amount. Based on the type, revenue hard limit and invoice hard limit will be populated along with payment terms. The user will be selected as administrator, which can be modified as required. Organization, product source and reference are optional.


Enter Project Number and Funding Amount. Funding Classification will be defaulted to Original. Once the details are entered for one or more projects then save the records. To Baseline Funding, click on Baseline Funding button N) Billing-Funding Inquiry

When you click on Baseline Funding button Oracle gives Error message as mentioned below:

Based on above message we need to create Cost Budget. In Budget window, enter Project Number, Budget Type, Entry Method, Resource List and click on Details button N) Budgets


To enter Budget Lines click on Budget Lines button

In Budget Lines window enter budget amounts and save your work.


In Budget window to submit budget click on Submit button after submitting budget status changed from Working to Submitted

To Baseline Budget click on Baseline button


Now Cost Budget Baselined

After completion of Cost Budget click on Baseline Funding button to Baseline funding. Now Funding amount Baselined


N) Billing-Funding Inquiry

Next Generate Draft Revenue for a Project. To Generate Draft Revenue, Submit Concurrent Program PRC: Generate Draft Revenue for a Single Project

Draft Revenue Generated


To see Project Revenue enter details in Revenue window like Project Number and click on Find button

Here Revenue Status is Unreleased to Release Revenue click on Release button


Now Revenue Status changed from Unreleased to Released

To Interface Revenue from Projects to General Ledger, Submit Concurrent Program PRC: Interface Revenue to General Ledger

Now Revenue Transferred from PA to GL


To Import Project Journals Switch Responsibility from Projects, Vision Services (USA) to General Ledger, Vision Services (USA). To Import Journals enter details in Import Journals window like Source, and click on Import button.

Now Project Journals imported optionally to see Journals go to Journals Inquiry window.


16. Invoice Generation Process

To Generate Draft Invoices for a Project Switch Responsibility from GL to Projects and Submit Concurrent Program PRC: Generate Draft Invoices for a Single Project

Draft Invoice Generated and Approval required.

To Approve Invoices enter details in Invoices window like Project Number and click on Find button.


Here Invoices Status is Unapproved to Approve click on Approve button.

Now Invoice Status Changed from Unapproved to Approved. Next Release the Invoice to Release Invoice click on Release button. And enter details in Release Invoices window like Invoice Number and click on OK button.


Invoice Status changed from Approved to Released.

To Interface Invoices from Projects to Receivables Submit concurrent program PRC: Interface Invoices to Receivables. This will create customer invoices in interface tables.


To move invoice information from interface tables to base tables, we need to submit auto invoice master programs with appropriate invoice batch source. This invoice batch source is configured in Implementation Options window.


Once the program is completed successfully, then verify the invoice created in Transactions window. Verify the Transaction and Transaction Line Descriptive Flexfields for additional information.

Now switch over to Invoice Summary window in projects and check the invoice status. Note that AR Invoice button is disabled at this time. The button will be activated only after submission of Tieback Process.


Once Tieback process is completed, then AR Invoice button is activated and Invoice Status also changes. Click on AR Invoice button to see the details.


Notice that the amounts are no updated in PSI window at this stage as we have not submitted the concurrent program. Submit the concurrent program to see the amounts.


To see the details about the commitment amounts, click on Commitments button. To filter the data, enter the search criteria like Supplier Number or dates. Otherwise press Find button to see all commitments as shown below:


Notice in the above window that Supplier Invoice (Accounted) does not appear as commitment. This is Supplier Cost for the project. Submit the following concurrent program to move the invoice to Projects Application. After completion of program verify the output for results.


Now we can see the supplier invoice as project expenditure. The expenditure type class is Supplier Invoices. Note that it is not possible to enter these invoices as Expenditure Batches within Projects.


From Projects we can drill down to AP Invoice and see all the details about the invoice. Click on Item Details button and select AP Invoice as shown below:


17. Inter-Project Billing

Inter-project billing functionality in Oracle Projects handles inter-project billing project relationships and the billing of inter-project transactions.

Inter-project billing generates internal invoices for costs incurred between two projects. During project setup, you define an inter-project billing relationship. This relationship enables you to invoice internally between the two projects, also called provider and receiver projects.

Once the work has been performed, the provider project generates an Oracle Receivables invoice for expenses incurred. The receiver project receives this invoice as an Oracle Payables invoice during the AR invoice tieback process. The invoice, like any supplier invoice, is interfaced to Oracle Projects as cost on the receiver project.

Note: To use inter-project billing you must implement multi-organization setup even if only one operating unit is setup.

Business Needs and Examples Enterprises face complex accounting and operational issues that result from complex work breakdown structures. Multiple organizations or departments may work together on a project, yet the customer wishes to receive only one bill. Parts of the work performed may be billed externally to a customer while other work may be billed internally to another project. These types of business needs require a way to capture multiple project costs into one project regardless of where or by whom the work is performed.

With inter-project billing, projects can be managed and controlled separately, and can bill both internally and externally. Using this model to define your work structure provides flexibility in managing your projects and consolidates costs for reporting purposes.

Consider the following examples:

Example 1:

During an auto accident, a telephone pole owned by the local telephone company is knocked down. A contract project is set up to track the cost of the repair. These costs will be billed to an insurance company. While the repair is under way, the telephone company decides to replace the old transformer at the top of the downed pole. These costs will need to be capitalized and will be billed internally to an capital project. The contract project will bill the insurance company for repair work performed on the pole, and, using inter-project billing, will bill a receiver project for work performed on the transformer. The receiver project can exist anywhere in the enterprise, regardless of operating unit, set of books, or legal entity.


Example 2:

Company ABC is an advertising company with a multiple organization structure. The London operating unit, ABC's headquarters, received a contract from a German customer. The customer wants ABC to produce and air live shows in Paris, New York, and Tokyo to launch its new line of high-end women's apparel. ABC will plan and design the show using resources from the London operating unit. The Paris, New York, and Tokyo operating units are each responsible for the successful execution of these live shows with their local resources.

Using the structure shown above, the customer project is divided into several related contract projects. The London operating unit owns the primary customer project, or receiver project, and bills the external customer. The related projects, or provider projects, are subcontracted to their respective internal organizations and internally bill the London organization to recover their project costs.

Step1: Select Provider and Receiver for Internal Billing in Internal Billing Tab (N) Setup-System-Implementation Options


Step 2: Create Sub Project using Main Project in Projects window enter main projects details and click on Find button then select main project click on Copy To button and enter Project Number, Name and click on OK button then Sub Project created as shown below.


Step 3: In main Project create a separate Task for Inter-Project Invoices and Enable the Receive Inter-Project Invoices check box in Task details window as shown below.


Step 4: In Task Options window select Subproject Association and enter Subproject details as shown below.


Step 5: In Subproject select Customers and Contacts Option and enter details in Customers and Contacts window and enable Bill Another Project check box and select the Receiver Project as shown below.


Step 6: Enter expenditure for Subproject and Submit, Release the expenditure as shown below.


Step 7: To distribute Miscellaneous Costs Submit Concurrent program and find out output as shown below.


Step 8: Enter the Agreement, Funding for Subproject Customer and Submit the funding as shown below.


Step 9: To Baseline Funding click on Baseline Funding button in Funding Inquiry window as shown below.


Step 10: To Generate Draft Revenue submit concurrent program and find out the output as shown below.

Step 11: Release Draft Revenue from Revenue Summary window as shown below.


Step 12: To Interface Revenue from Projects to General Ledger submit concurrent program and find out the output as shown below.


Step 13: To Generate Draft Invoices submit concurrent program and check out results as shown below.


Step 14: Approve and Release Invoices from Invoice Summary window as shown below.

Step 15: To Interface Invoices from Projects to General Ledger submit concurrent program and find out the output as shown below.


Step 16: To Import Project Invoices in Receivables submit concurrent program from Receivables and find out invoices in Transactions window as shown below.


Step 17: To Tieback Invoices from Receivables submit concurrent program from Projects (at that time Oracle creates a Supplier Invoices) as shown below.

Step 18: To see Supplier Invoices switch over to Payables, submit the concurrent program, find out the output then you can see invoices in invoices window as shown below.


18. Processing Events

Use the Event Details window to enter and review events for a project or top task. Examples of events include an invoice reduction, a performance bonus, revenue write-off, or adjusting revenue. You can also change the bill hold status of an event using these windows. For transactions that involve foreign currencies, all amounts displayed in the Event windows are shown in the event transaction currency.

Events can be entered in any currency when multi-currency is enabled for the associated project. The currency in which the event is entered or created is called the event transaction currency. Oracle Projects uses the currency conversion attributes stored for each event to convert revenue and invoice amounts for manually entered and automatically created events from the event transaction currency to the project functional, project currency, and the funding currency.

Step 1: To enter Events for Projects navigate to Find Project Events window, enter project number and click on New button, enter Event details in Event Details window as shown below.

The following table describes how each event type classification affects revenue and billing.

Classification Revenue Effect Billing Effect

Automatic Depends on billing extension definition Depends on billing extension definition

Deferred Revenue No effect Bill for amount of event

Invoice Reduction No effect Reduce a bill by amount of event

Manual Accrue amount of event Bill for amount of event

Scheduled Payment No effect Bill for amount of event, FIFO

Write-Off Reduce by amount of event No effect

Realized Gains Increase by amount of event No effect

Realized Losses Decrease by amount of event No effect


19. Project Accounting Setup Steps

20. Define Organizations Define Project Owning Organization Define one organization for GCSS called GCSS- Project Owning Organization. Assign the classification as mentioned below.

Field Name Description

Name Enter Project Owning organization belonging to GCSS, which owns and executes projects

Type Leave this field blank Dates From Enter the start date from which the project owning organization will be effective Dates To Enter the end date to make project owning organization become closed Location Select appropriate location, where project owning organization is located and

operates Internal or External Populated by default Location Address Address of location name is populated by default Internal Address This field is empty Organization Classifications

Select Project Task Owning Organization from list and enable

Click on Others button to mention additional organization information. Click on the field to see details.

Put the cursor on field and click to open the window.



Allow Entry of Indirect Projects

Select Yes from list

Allow Entry of Capital Projects

Select No from list

Allow Entry of Contract Projects

Select No from list

Once the details are entered, close the window one by one.

Define Expenditure Owning Organization Expenditure Owning Organization is created in the same manner like Project owning Organization.


Name Enter Project Owning organization belonging to GCSS, which owns and executes projects

Type Leave this field blank Dates From Enter the start date from which the project owning organization will be effective Dates To Enter the end date to make project owning organization become closed Location Select appropriate location, where project owning organization is located and

operates Internal or External Populated by default Location Address Address of location name is populated by default Internal Address This field is empty Organization Classifications

Select Project Expenditure/ Event Organization from list and enable the checkbox

Click on Others button to mention additional organization information. Click on the field to see details.


Field Name Input Mode Description

Operating Unit LOV Select the operating unit from the list. Only one operating unit is available in the list

Default Calendar Manual Leave this field blank

Select the default operating unit as mentioned above and close the window one by one. Now these organizations become subordinates to Vision Operations or Vision Services, which will be selected as Start Organization in Implementation Options window.

Open Global Organization Hierarchy window. Retrieve Global hierarchy definition. Put the cursor in Organization Name field. Use F11 key to get into query mode and search for Vision Corporation. Once it is retrieved, then use any subordinates for adding new organizations in the list.


Ensure that these are mapped properly. Otherwise they will not appear in Projects and Expenditure batches windows.


21. Implementation Options N: Setup > System > Implementation Options > System Tab Page


Ledger If you are implementing Oracle Projects, then you must specify a ledger to tell Oracle Projects which ledger to use. Oracle General Ledger, Oracle Receivables, Oracle Payables, Oracle Purchasing, and Oracle Assets must also use this ledger. Specify the ledger you defined when you implemented Oracle General Ledger for Oracle Projects

Business Group If HR: Cross Business Group profile option is No, business group displays business group assigned to users responsibility using HR: Security Profile option. If HR: Cross Business Group profile option is Yes, business group displays value All.

Summarization Period Type

Select GL Period or PA Period from list. This will be used when updating project summary amounts

Calendar Name Select calendar used to maintain PA periods. Default option is calendar assigned to ledger. Change calendar setting during implementation only. Do not change this value after you copy your PA periods from GL to Projects

PA Period Type Specify a Period Type, which is used to copy Project Accounting Periods from the calendar associated with the ledger. If you copy PA Periods from GL, Oracle Projects copies all of the periods of this Period Type to set up the PA Periods. In a multiple organization environment, the PA Period Type is specified for each operating unit

Default Asset Book Leave this field blank Maintain Common PA and GL Periods

When this option is enabled, the system automatically maintains PA period statuses as you maintain the GL period statuses. To use this option, the following conditions must be met: PA periods and GL periods must be defined in same calendar PA period type must be same as period type defined for GL Each of PA periods and GL periods must have same status

Organization Hierarchy

Select the organization hierarchy designed for business, which will be used for reporting the balances in PSI window

Version Select the correct version, which will be used for reporting Start Organization Select the Start Organization from list. All organizations below this will be used for

reporting purpose



Functional Currency This display-only field shows the functional currency of your company's ledgers. In a multiple organization environment, the functional currency is the currency of the ledger assigned to the operating unit(s) associated with your login responsibility.

Costing Exchange Rate Date Type

Specify a default exchange rate date type for converting foreign currency transactions from the transaction currency to the functional and project currencies.

Exchange Rate Type Specify a default exchange rate type to be used for conversion of transactions from the transaction currency to the functional and project currencies. The Exchange Rate Type field is a mandatory field. Select the exchange rate type from a list of valid conversion rate types. Conversion Rate Types are entered in Oracle General Ledger.

The currency implementation options control the default values for the currency attributes that are used to calculate currency exchange rates.


Project Numbering Method

You specify whether you want Oracle Projects to number projects automatically, or whether you plan to enter project numbers manually. If you want Oracle Projects to number each project automatically upon creation, then specify a starting project number. Automatic project numbers are numeric; they do not contain letters or special characters and are sequentially numbered. If you want to choose your own project numbers, or if want your project numbers to include both alphabetic and numeric characters, choose the manual project numbering method. Manual project numbers can be either alphanumeric or numeric.

Note: Project templates are always numbered manually. The Project Numbering

implementation option does not affect how project templates are numbered. Project Numbering Type

Select Alphanumeric from two options


You assign a project/task owning organization hierarchy to operating unit to control which organizations can own projects and tasks. The organization must have following characteristics: The organization must belong to project/task organization hierarchy assigned to

operating unit.


The organization must have project/task owning organization classification enabled.

The project type class must be permitted to use organization to create projects This permission is determined when you define the organization.

The organization must be active as of the system date. Version Select the correct version, which will be used for reporting Start Organization Select the Start Organization from list. All organizations below this will be used for

reporting purpose


Expenditure Cycle Start Day

Specify an Expenditure Cycle Start Day to indicate the day your seven-day expenditure week begins. If you specify Monday as the expenditure cycle start day, the week ending date on all expenditures, including timecards and expense reports, is the following Sunday. You can choose any day of the week as your expenditure cycle start day

Enable Overtime Calculations

You specify whether you want to use the Overtime Calculation program to calculate and charge overtime hours automatically. You may need to customize the Overtime Calculation program if your business wants to use automatic overtime calculation

Import Contingent Worker Timecards with Purchase Order Integration

Enable this option if you want to import contingent worker labor costs from timecards. When you select this option, contingent workers can select a purchase order when they enter timecards. Specifying a contingent worker purchase order on a timecard allows the labor cost to be imported via the timecard, and prevents interface of labor costs to Oracle Projects from supplier invoices that are associated with the purchase order.

Default Supplier Cost Credit Account

Define a default supplier cost credit account. Oracle Projects credits the specified account when you adjust supplier cost and expense report expenditure items in Oracle Projects.

Interface Cost to GL: Oracle Projects generates accounting events for that type of cost, and creates accounting for the accounting events in Oracle Subledger Accounting. Oracle Subledger Accounting is an intermediate step in the cost accounting flow between Oracle Projects and Oracle General Ledger. Oracle Subledger Accounting transfers the accounting entries to Oracle General Ledger. Therefore, if you do not enable an interface cost option, then Oracle Projects does not generate cost accounting events for transactions of that type of cost. As a result, you cannot create accounting in Oracle Subledger Accounting


and transfer the costs to Oracle General Ledger. Interface Employee Labor Cost

If you want to send employee labor costs, then you must enable option

Interface Contingent Worker Labor Cost

If you want to send contingent worker labor costs, then you must enable option

Interface Usage Costs

If you want to send usage costs, inventory costs, WIP costs, miscellaneous costs, then you must enable option


You assign an expenditure/event organization hierarchy to the operating unit to control which organizations have the following capabilities: incur expenditures, own project events, be assigned to a resource list as a resource To incur expenditures, own events, or be assigned to a resource list, an organization must have the following characteristics: The organization must be in the expenditure/event organization hierarchy

assigned to the operating unit. The organization must have the project expenditure/event organization

classification enabled. The organization must be active as of the system date

Version Select the correct version, which will be used for reporting Start Organization Select the Start Organization from list. All organizations below this will be used for

entering expenditures


Interface Revenue to GL

If you want to send revenue to Oracle General Ledger, then you must enable the interface revenue option. When you enable the interface revenue option, Oracle Projects generates revenue accounting events and creates accounting for the accounting events in Oracle Subledger Accounting. Oracle Subledger Accounting is an intermediate step in the revenue accounting flow between Oracle Projects and


Oracle General Ledger. Oracle Subledger Accounting transfers the accounting entries to Oracle General Ledger. Therefore, if you do not enable the interface revenue option, then Oracle Projects does not generate revenue accounting events. As a result, you cannot create the accounting and transfer the revenue to Oracle General Ledger.

Invoice Numbering Invoice Numbering Method You specify whether you want Oracle Projects to number invoices automatically, or whether you plan to enter invoice numbers manually. Centralized Invoice Processing You specify whether you want invoice processing to be centralized, or if you want Oracle Projects to process your invoices at the project invoice collection organization level. By default, the Centralized Invoice Processing check box is enabled. If you want all of the project invoices for the operating unit to be processed using the Oracle Projects seeded transaction types, leave the check box enabled. With decentralized invoicing, you allow organizations to process their own invoice collections.

Invoice Batch Source

You need to specify an invoice batch source in Oracle Projects before you can interface invoices to Oracle Receivables. Oracle Projects provides a predefined batch source name PROJECTS INVOICES. You must select this batch.

Sales Credit Type You use the Sales Credit Type to interface sales credit information to Oracle Receivables for project invoices. Select the Sales Credit Type to specify the type of credit you want to allocate to salespersons in Oracle Receivables for project invoices. If there is no credit receiver defined at the project level and Allow Sales Credit is enabled for the Invoice Batch Source, your project invoices will interface to receivables with the selected Sales Credit Type with the project manager as the default credit receiver.

Customer Relationships

You can control the ability to view and select related customers of the project customer for bill and ship to purposes at the operating unit level. The choices are: Yes: You can choose a Bill To and Ship To customer based on the project customer or a related customer defined in Oracle Receivables. No: You can choose a Bill to and Ship to customer of the project customer only. All: You can choose a Bill To and Ship To customer from any customer defined in Oracle Receivables. The default value is No. You can change the option any time, but the change impacts only future customers and invoices.

Enable Multi-Currency Billing

Check this box if you want to enter agreements, rate schedules, and add billing assignments to the project type in any currency.

Require Rate and Discount Reason

Oracle Projects allows you to enter a reason for the rate or discount override to the standard bill rate schedules. Check this box if you want to require users to enter the rate and discount override reason.

Allow Bill Rate Override

Check this box if you want to be able to override bill rates for all the projects in the operating unit

Allow Bill Rate Discount Override

Check this box if you want to be able to override the bill rate discount for all the projects in the operating unit. If this functionality is enabled, Oracle Projects allows you to override the project or task level discount percentages at the following levels: Employee Job Non-Labor Resource Requirement Assignment

Share Bill Rate Schedules Across Operating Units

Check this box if you want to share bill rate schedules across operating units. This functionality allows an operating unit to share rate schedules from other operating units.

Allow Funding Across Operating Units

Check this box if you want to fund projects across operating units. If you enable this functionality, the list of values for project number includes active projects that are associated with the agreement of the customer and that have: Multi-currency billing enabled at the project level Multi-currency billing disabled at project level and functional currency same as the agreement currency or Multi-currency billing enabled with funding currency selected as the invoice processing currency, and existing funding in a currency same as the agreement currency.

Account for Unbilled Retention

To generate a different account for unbilled retention using the defined Unbilled Retention Account AutoAccounting rules, you must check this box. The unbilled retention is an asset account, separate from the unbilled receivable account, and


tracks the total amount of withheld retention that has not been billed. If this feature is not enabled, Oracle Projects uses the Unbilled Receivable Account AutoAccounting rules when interfacing project invoices and retention invoices to Oracle Receivables.

Funding Revaluation Includes Gains and Losses

Check this box if you want the funding revaluation process to include gains and losses. If you enable this functionality, you must implement the realized gain and loss function transactions and set up the AutoAccounting rules to reclassify the realized currency gain and loss accounts based on the new event type classifications. If you do not enable this functionality, the revaluation process includes only the backlog amount for revaluation. Note: This option cannot be unchecked at this level if any of the project type level or project level Funding Revaluation includes Gains and Losses option is enabled.

Require Credit Memo Reason

Enable this option if you require a user to select a credit memo reason when releasing canceled invoices, write-offs, and credit memos.

Use this window to define cross charge implementation options. Define cross charge implementation options for every operating unit that uses the cross charge feature (intercompany billing or borrowed and lent processing).


Exchange Rate Date Type

Choose Expenditure Item Date or PA Date

Exchange Rate Type Specify the rate type that the system will use as the default for transfer price conversions

Cross Charges within Operating Unit

Select a method for processing cross charges within the operating unit. None: The system will not process intra-operating unit transactions for cross charge. Borrowed and Lent: The system creates borrowed and lent accounting entries only. The system does not generate invoices for transactions processed by borrowed and lent accounting.

Allow Cross Charges to All Operating Units Within Legal Entity

To allow cross charges to all operating units within a legal entity: 1. Select the Allow Cross Charges to all Operating Units within Legal Entity check box. 2. Choose a default processing method for cross charge transactions across operating units within the legal entity. None: The system will not process inter-operating unit transactions for cross charge. Borrowed and Lent: The system creates borrowed and lent accounting entries only. Oracle Projects uses the organization defined at Default Legal Context of the operating unit as the legal entity for cross charge processing.


Use this window to define internal billing implementation options. For each operating unit that uses internal billing, you must set up Internal Billing implementation options as either a provider or receiver organization, or both.


Provider for Internal Billing

If the current operating unit is a provider organization for internal billing, select the Provider for Internal Billing check box and complete the additional fields in this region.

Supplier Name and Number

Enter the name and number of the supplier associated with the current operating unit.

Invoice Numbering Select an invoice numbering method. Reclassify Costs for Cross Charged Transactions Cost Accrual Projects

Indicate how you want to reclassify cross charged costs for cost accrual projects (Raw or Burdened). Select None if you do not want to reclassify raw or burdened costs.

Non Cost Accrual Projects

Indicate how you want to reclassify cross charged costs for and non-cost accrual projects (Raw or Burdened). Select None if you do not want to reclassify raw or burdened costs.

Receiver for Internal Billing

If the current operating unit is a receiver organization for internal billing, select the Receiver for Internal Billing check box and enter the customer name and number to be associated with the current operating unit. If you want to identify the project as a cost accrual project, use the Cost Accrual Identification extension.


22. Project Accounting Periods Project accounting periods (PA periods) track Oracle Projects data on a periodic basis. Your PA periods may be more frequent than your GL accounting periods. You can use PA periods for budgeting and forecasting and for accounting for cost and revenue. You set a current PA reporting period for Oracle

Projects to summarize project amounts and to track project status. N > Setup > System > PA Periods

When enhanced period processing features are enabled, you must maintain the status of your GL periods for project transaction processing in Oracle Projects.


Status Select status from the list. Initially the status will be Never Opened. Change this to Open. Once period is over, then change this to Pending Close or Closed

PA Period PA periods are displayed here, which are copied from GL periods Effective Date From Start date from PA period is displayed Effective Dates To End date from PA period is displayed Reporting Period This is set based on selection from Set Reporting Period Button. This is a monthly

activity Once the changes are completed, then save the records and close the window.


23. Define GL Periods for Projects

All GL periods are defined for the ledger. We need to open these periods for each operating unit.

Change the period status to Open from Never Opened. Otherwise we can not create accounting entries for cost transactions.


24. Define Project Status Workflow: If you want to initiate workflow when an object is updated to this status, select the Workflow tab. Check the Enable Workflow check box and enter the following fields: Item Type. Enter the name of the Workflow Item Type to be used for this status. Process. Enter the name of the workflow process to submit for this status. Success Status. Enter the status to assign to the object upon successful completion of workflow. Failure Status. Enter the status to assign to the object if workflow fails. (This can be the same as the

current status Status Controls: The Status Controls region contains a list of actions that are allowed or restricted for each status. Next Allowable Statuses: Use this region to define the next allowable statuses for each status. Four radio buttons control the next allowable statuses you can enter: All: The current status can be changed to any status. This is the default value. None: The current status cannot be changed. System Status: The Next Allowable Statuses are all system statuses. Status: The Next Allowable Statuses are all user-defined statuses. If you choose System Status or Status, you can then enter as many next allowable statuses as you want.

N: Setup > System > Statuses


Status Type Select Project from the list Status Enter status name, which is unique System Status Select predefined status from the list Description Enter meaningful description for status Effective Date From Enter Start date from which status would be effective


Effective Dates To Enter End date from which status would be ineffective Status Controls Action

All actions are predefined. Tick Allow check box if the action is to be permitted for a particular status

Next Allowable Status

Select one of the four options based on requirement.


Status Type Select Project from the list Status Enter status name, which is unique System Status Select predefined status from the list Enable Workflow Enable the check box where workflow is required Item Type Select PA Project Status Change Workflow from list Process Select Project from list. This is selected by default Success Status Select project status from list. This status is selected by workflow when process is

successful Failure Status Select project status from list. This status is selected by workflow when process is

failure


25. Define Budget Status All budget statuses are predefined. New statuses can not be defined in the application. However the status and description can be edited, if required. In the instance the description field is empty. Copy status name to description N: Setup > System > Statuses


Status Type LOV Select Control Item from the list Status Manual Edit status name, which is unique. It is not possible to create new

status codes in application System Status LOV Select predefined status from the list Description Manual Enter meaningful description for status. Copy the status name here Effective Date From Manual Enter Start date from which status would be effective Effective Dates To Manual Enter End date from which status would be ineffective Starting Status Tick Only one status will have this status Draft Workflow: If you want to initiate workflow when an object is updated to this status, select the Workflow tab. Check the Enable Workflow check box and enter the following fields: Item Type. Enter the name of the Workflow Item Type to be used for this status. Process. Enter the name of the workflow process to submit for this status. Success Status. Enter the status to assign to the object upon successful completion of workflow. Failure Status. Enter the status to assign to the object if workflow fails. (This can be the same as the

current status)



Status Type LOV Select Control Item from the list Status Manual Edit status name, which is unique. It is not possible to create new

status codes in application System Status LOV Select predefined status from the list Enable Workflow Tick Enable the check box where workflow is required Item Type LOV Select PA Budget Workflow from list Process LOV Select Budget from list. This is selected by default Success Status LOV Select Budget status from list. This status is selected by workflow

when process is successful Failure Status LOV Select Budget status from list. This status is selected by workflow

when process is failure


26. Define Budget Types N: Setup > Budgets > Budget Types

Oracle provides four seeded budget types in application. For GCSS, we need to create one cost budget as shown:


Budget Type Enter budget type, which represents the nature of budget Description Enter description for budget type Effective Date From Enter Start date from which budget type would be effective Effective Dates To Enter End date from which budget type would be ineffective Amount Type Select Cost Budget always Use Workflow for Budget Status Changes

Enable the check box, where workflow will be used to change the status of budgets using this budget type


27. Define Budget Entry Methods N: Setup > Budgets > Budget Entry Methods

Budget entry method decides at what level we are going to enter budgets for projects.


Budget Entry Method

Enter budget entry method, which represents the entry level of budget

Description Enter detailed description for budget entry method Effective Date From Enter Start date from which budget entry method would be effective Effective Dates To Enter End date from which budget entry method would be ineffective Entry Level Select any entry level as appropriate from four choices Quantity Enable the check box Raw Cost Enable the check box Burdened Cost Disable the check box Categorize By Resources

Enable the check box

Time Phase By Select None from the list Quantity Disable the check box Revenue Disable the check box Enter entry methods one by one. Once all methods are entered, then save the records and close the window.


28. Define Resource Lists N: Setup > Budgets > Resource Lists

Resource lists are used to enter budgets for each resource against a task/ project. Resources can be grouped based expenditure category or organization. Each resource group will be broken into resource type and resource.


Resource List Enter unique list name Description Enter detailed description for list name Effective Date From Enter Start date from which list would be effective Effective Dates To Enter End date from which list would be ineffective Job Group Select None as job group from the list Group Resources By Select Expenditure Category from the list Group Select Expenditure Category as group from the list Alias Expenditure Category will be defaulted as alias Control Levels Select control level from list of Absolute, Advisory and None Order Mention the order in which the list should appear in budget entry window Enabled Enable the check box for all active resource groups Resource Type Select resource type for a resource group from the list. Repeat the selection for each

group Resource Select resource for a type from the list Alias Resource name is populated as alias, but can be edited anytime Control Levels Select control level from list of Absolute, Advisory and None Order Mention the order in which the list should appear in budget entry window Enabled Enable the check box for all active resources


29. Define Project Classifications

You define project classifications to group your projects according to categories you define. A project classification includes a class category and a class code. The category is a broad subject within which you can classify projects. The code is a specific value of the category.

N: Setup > Projects > Classifications


Class Category Enter class category, which can be assigned to projects Description Enter description for each class category Mandatory Specify whether the class category is mandatory for every project you define.

Enable if all projects must have a code assigned to this class category. Do not enable if this class category is optional

AutoAccounting Specify whether you want to use the class category in your AutoAccounting rules Allow 1 Code Only Specify whether you want to allow entry of only one class code with this class

category for a project Allow Percent Entry The Allow Percent Entry attribute controls the ability to associate percentages with

classification codes Total Percent Equal 100

Total Percent Equal 100 attribute controls the ability to associate percentages with classification codes

For All Project Types Select each Project Type that you would like to associate with this class category. Enable the Mandatory check box for a project type if you want the system to require all projects of the project type to be associated with the selected class category

Effective Date From Enter Start date from which category would be effective Effective Dates To Enter End date from which category would be ineffective Name Enter code name. Multiple code name can be entered for one category Description Enter meaningful description for each code Effective Date From Enter Start date from which code would be effective Effective Dates To Enter End date from which code would be ineffective



Project Type Select project type from list, for which class categories will be assigned Description Description of project type is displayed here for reference Mandatory Do not enable checkbox

Once all class categories and codes are entered, close the window.


30. Define Service Types

Use the Oracle Projects Lookups window to review and maintain lookups that you use in Projects. Service Types can be attached to Tasks for classification purpose.

N: Setup > Projects > Service Types


Type LOV Select SERVICE TYPE from list Meaning Display Enter SERVICE TYPE. Do not edit this Application Display Oracle Projects will be displayed Description Manual Enter SERVICE TYPE. Do not edit this Code Manual Enter service type codes, which will be used to classify the task in a

project Meaning Manual Enter meaning of code, which can be understood by all Description Manual Enter description of code Tag LOV Leave this field blank Effective Date From Manual Enter Start date from which code would be effective Effective Dates To Manual Enter End date from which code would be ineffective Once all codes are entered, review the codes and close the window.


In some fields in Projects windows, you are required to enter a value from a predefined list of values. Sometimes the values on the list are items you have defined in a setup window such as Credit Types. Other predefined sets of values are lookups, which you can view, and in some cases, update, in the Oracle Projects Lookups window. Each lookup category is identified by its lookup type. For example, UNIT is a lookup type for which Currency and Hours are allowable codes.


31. Define Expenditure Categories

In the Expenditure Categories window, enter a unique name for the expenditure category and enter its description. Save your work. N: Setup > Expenditures > Expenditure Categories


Name Enter unique name for each category Description Enter detailed description for each category Effective Date From Enter Start date from which category would be effective Effective Dates To Enter End date from which category would be ineffective

32. Define Revenue Categories

N: Setup > Expenditures > Revenue Categories

One seeded category is provided and this can be used for creating the expenditure types. Revenue Category is mandatory for creating Expenditure Category.


Type LOV Select REVENUE TYPE from list Meaning Display Enter REVENUE TYPE. Do not edit this Application Display Oracle Projects will be displayed Description Manual Enter REVENUE TYPE. Do not edit this Access Level Selection Extensible is selected. Do not edit this Code Manual Enter Revenue type codes, which will be used to classify the task in

a project Meaning Manual Enter meaning of code, which can be understood by all Description Manual Enter description of code Tag LOV Leave this field blank Effective Date From Manual Enter Start date from which code would be effective Effective Dates To Manual Enter End date from which code would be ineffective


33. Expenditure Types N: Setup > Expenditures > Expenditure Types

Field Name Description Name Enter Expenditure Type Name Expenditure Category

Select Expenditure Category, which will be assigned to type

Revenue Category Select Revenue Category, which will be assigned to type UOM Enter the unit of measure you want Oracle Projects to use when calculating the cost

for this expenditure type. You must enter Hours for labor expenditure types Output Tax Code Leave this field blank Rate Required If this expenditure type requires a cost rate, check the Rate Required check box,

then choose Cost Rate to navigate to the Expenditure Cost Rates window and enter a cost rate and its effective date(s). The rates can be defined by operating unit.

Note: If you create a non-labor expenditure type without checking the Rate Required check box, you cannot subsequently require and enter a cost rate for that expenditure type. Instead, you must disable the expenditure type and create a new one that requires a cost rate and has a unique name. If you check the Rate Required check box when you create a non-labor expenditure type, you can change the cost rate at any time.

Expenditure Type Class

Select one or more classes, which will be assigned to type

Effective Date From Enter Start date from which type class would be effective for selected type Effective Dates To Enter End date from which type class would be ineffective for selected type


Name Enter Expenditure Type Name Description Enter meaningful description for selected type name Effective Date From Enter Start date from which type would be effective for selected type Effective Dates To Enter End date from which type would be ineffective for selected type


34. Define Non Labor Resources

To define non-labor resources: 1. In the Non-Labor Resources window enter a name, description, effective date(s), and a usage expenditure type for each non-labor resource your organization owns. 2. For each non-labor resource you define, enter the organization(s) to which the resource is assigned in the Organizations region. Enter the effective dates during which the resource is owned by each organization. The organizations you enter can include any organization from your organization hierarchy, regardless of whether the organization has the Expenditure Organization classification, and regardless of the start and end dates for the organization. 3. If you want to override the cost rate of the expenditure type by the resource and organization combination, choose Cost Rates and enter the cost rate for the operating unit in question, and the effective date(s) in the Cost Rates Overrides window. 4. Save your work. Attention: A non-labor resource may be a piece of equipment whose capacity is consumed, such as a training room, or equipment whose physical output is consumed, such as a copier. You can plan and report for non-labor resources as equipment whose capacity is consumed by enabling the equipment resource class.


35. Define Transaction Sources


Transaction Source Enter Transaction Source Name. Ex: Hyperion. Transaction sources identify the source of external transactions that you import into Oracle Projects. The transaction source determines how Oracle Projects imports the transactions. Oracle Projects provides a set of predefined transaction sources that you use to import transactions from other Oracle Applications.

Default Expenditure Type Class

Oracle Projects uses the default expenditure type class that you assign to a transaction source if an expenditure type class is not specified in the interface table. Oracle Projects provides this option to facilitate the migration of data from earlier releases of Oracle Projects.

Raw Cost GL Accounted

Select this option to indicate whether transactions imported from this transaction source are already accounted. When you select this option, Oracle Projects processes do not generate accounting events to send the transactions to Oracle Subledger Accounting. When you select this option, the Import Raw Cost Amounts option is automatically selected. Examples of transactions for which this option is enabled are manufacturing and inventory transactions with the transaction source Inventory, Inventory Misc, or Work In Process.

Import Raw Cost Amounts

When a transaction source has this option enabled, the raw cost amount of the transactions has already been calculated (costed). These are not modified after being imported into Oracle Projects. None of the Oracle Projects processes will calculate raw cost amounts for these transactions.

The designation of a transaction as costed does not affect burdening, accounting, or interfacing to GL or AP. These processes are still performed on the transaction as they would be if it were imported as a non-costed transaction.

Import Burdened Amounts

When this option is selected for a transaction source, Oracle Projects expects the external system to provide burdened costs. If the transaction does not have a burdened cost amount, Transaction Import will reject the transaction.

When you select this option, the Import Raw Cost Amounts option is automatically selected.

Import MRC Amounts

Do not enable the check box

Allow Duplicate Reference

Enable this option to allow multiple transactions with this transaction source to use the same original system reference. If you enable this option, you cannot uniquely identify the item by transaction source and original system reference.

Import Employee Organization

If you enable this option, the external system can optionally provide an expenditure organization that is different from the employee owning organization. If no expenditure organization is provided, Transaction Import will populate the expenditure organization with the employee owning organization.



Transaction Source Enter Transaction Source Name. Ex: Hyperion Default Expenditure Type Class

Mention default type class for oracle to use while importing data from third party systems

Allow Interface Modifications

This option allows you to modify rejected transactions in the Review Transactions window after the import process is completed. Note: You must enable this option for predefined supplier cost transaction sources to use the Review Transactions window to modify the expenditure item date for expenditure items that fail date validation during import.

Purge After Import If you select this option, items successfully imported from the transaction source are automatically purged from the interface table when the import process is completed.

Allow Reversals If you enable this option, Oracle Projects allows reversals of expenditure batches or expenditure items for the transaction source. When you enable this option, the Allow Adjustments option is automatically enabled.

Allow Adjustments If you enable this option, then you can adjust imported transactions in Oracle Projects after you load them via Transaction Import.

Process Cross Charge

If you import cross charge transactions that are processed by an external system, enable this option for that system's transaction source. If this option is enabled for a transaction source, Oracle Projects performs cross charge processing for transactions originating from that transaction source.


36. Define Labor Costing Labor Cost Multipliers A labor cost multiplier is a value by which Oracle Projects multiplies an employee's labor cost rate to calculate the employee's overtime premium cost rate: Labor Cost Rate * Labor Cost Multiplier = Overtime Premium Labor Cost Rate Oracle Projects then multiplies this overtime premium labor cost rate by the number of overtime hours an employee works to calculate the overtime premium for that employee: Overtime Premium Labor Cost Rate * OT Hours = Overtime Premium You define a labor cost multiplier for each kind of overtime your business uses such as double time, or time and a half. For example, if you pay an employee double time for all overtime hours, you define a labor cost multiplier of 1.0. You multiply the employee's labor cost rate by 1.0 to calculate the employee's overtime premium labor cost rate. If you pay an employee time and a half for all overtime hours, you define a labor cost multiplier of 0.5 to calculate the employee's overtime premium labor cost rate. An employee's total labor cost is the overtime premium plus the total number of hours that employee worked multiplied by the employee's labor cost rate: Overtime Premium + (Total Hours x Labor Cost Rate) = Total Labor Cost


Name Enter Name Multiplier Enter Multiplier value. Effective Date From Enter Start date from which multiplier would be effective Effective Dates To Enter End date from which multiplier would be ineffective Labor Costing Rules

A labor costing rule determines how an employee is paid. You define a labor costing rule for each pay type your business uses. For example, you can define a labor costing rule for pay types such as exempt, non-exempt, uncompensated, compensated, or hourly.



Labor Costing Rule Enter Labor Costing rule name Costing Method Select Rates or Extension method from list. When you select Rates, Oracle Projects

calculates the labor costs for entered hours using hourly cost rates. When you select Extension, labor costs are calculated by the labor costing extension. When using this option you are not required to maintain hourly cost rates in Oracle Projects.

Effective Date From Enter Start date from which multiplier would be effective Effective Dates To Enter End date from which multiplier would be ineffective Overtime Cost Multipliers Expenditure Type Select Overtime expenditure type from list Labor Cost Multiplier Enter the multiplier in fraction here


Costing Rules and Rate Schedules To calculate labor costs, you must assign a costing rule to each expenditure organization. If a costing rule has a costing method of Rates, you must also assign a cost rate schedule to each organization using the costing rule. 1. Select a labor costing rule. If the labor costing rule has a costing method of Rates, select the cost rate schedule that defines the hourly cost rates for employees in the selected organization. 2. Enter a default job rate schedule to be used when forecasting costs for unstaffed positions. 3. Enter the Effective Dates during which the assignment of the costing rule and rate schedule are valid for the organization. 4. If you use the overtime calculation extension, optionally enter a default project and task for system generated transactions. 5. If your cost rate schedule currency is different from your operating unit currency, enter the currency conversion attributes in the Currency Conversion Attributes region. If you do not specify currency attributes,

the rate attributes defined in the Implementation Options window are applied.

Labor Costing Overrides For individual employees, you can enter labor costing overrides. You can: Override the assigned costing rule. Override the assigned cost rate schedule. Enter an overriding cost rate. To override labor costing: 1. In the Labor Costing Overrides window, enter either the Employee Name or Employee Number for the operating unit under question. Then select Find. The current overrides for the selected employee are displayed. 2. Specify whether you wish to override the assigned rate schedule or enter an overriding cost rate by choosing an override type: Schedule: Enter the overriding rate schedule in the Cost Rate Schedule field. Rate: Enter an overriding rate. Optionally, select a new currency code and define currency conversion attributes. 3. Enter the Effective Dates during which the labor costing override is valid for this employee. 4. Save your work.


37. Define Burden Costs Define Cost Base Cost bases refer to the bases of raw costs used for applying burden costs. You assign cost bases to burden structures, and then specify the types of raw costs that are included in the cost base along with the types of burden costs that are applied to the cost base.


Cost Base Enter unique Cost Base Code name Report Order Enter 10, 20 etc for them to appear in order Type Cost base types refer to the use of cost bases. Oracle Projects predefines the cost

base types Burden Cost and Other. Cost bases with the type Burd

Documents

To process a retirement request: To view retirementsgreenchain.biz/PDF/R12Projects_White_Paper_Part_II.pdf · You can initiate a retirement request in Oracle Projects to identify