If you enable the   Project Task Owning Organization   classification, you must also specify the additional organization information for the classification as follows:

Place your cursor on the Project Task Owning Organization classification.

Select the Others button.

In the Additional Organization Information window, place your cursor in the Project Type Class Information field.

In the Project Type Class Information window, enter information for the following fields:

Allow Entry Of Indirect Projects:   Select Yes from if you want this organization to own indirect projects.

Allow Entry of Capital Projects:   Select Yes from if you want this organization to own capital projects.

Allow Entry of Contract Projects:   You must select Yes.

Note:   You must select Yes, even though you cannot create contract projects in Oracle Grants Accounting. Oracle Grants Accounting uses contract projects to process revenue and invoices for awards. Oracle Grants Accounting uses an underlying award project to process revenue and invoices. The award project is a contract class project.

In the Project Type Class Information window, select the OK button.

In the Additional Organization Information window, select the OK button.

In the Forms dialog box that asks you if you want to save the changes you have made, select the Yes button to save your work.

Note:

* People resources represent named persons or any grouping of named

persons (E) by attributes such as job (C), organization, or role (A), whose time (effort)

capacity is consumed to complete the project work. Example: Amy Marlin

Note:

* Oracle Projects fully integrates with Oracle Human Resources to keep track of employees and information relevant to them, such as bill rates and mailing address.

Note:

* When you merge supplier information you have different options. You can choose to merge both invoices and purchase orders. If you choose to merge invoices, then you can merge all invoices or just unpaid invoices. When you choose to merge all invoices, any associated payments are merged as well.

* Supplier Merge

You can merge suppliers in Oracle Payables to maintain your supplier records. This functionality enables you to merge duplicate suppliers into a single, consolidated supplier. You can use it to merge transactions within the same supplier from one supplier site to a different supplier site. You can also choose to merge all transactions for a supplier into a new supplier, or you can choose to merge only unpaid invoices.

The supplier merge program in Oracle Payables updates the supplier references on related transactions in Oracle Projects.

* AutoAccounting Parameter : Class Code

AutoAccounting class code on the project.

Note: Since you can define many project classification categories, the Class Code parameter always corresponds to the one classification category that you specified as the AutoAccounting classification category.

A: If the revenue amounts are already interfaced to General Ledger (GL) through a different interface, then uncheck the ‘Interface Revenue to GL’ option in the implementation options and run the ‘Interface Revenue to GL’ process in Oracle projects. This will turn the flags in the revenue records as accepted in GL, though it is not interfaced. Once this is done, revert back the implementation option back to its original state.

After you have performed the adjustment actions, you need to run the appropriate processes to process the adjustments.

The table below notes what processes to run to process each adjustment action.