Previous	Next		Contents	Index	Navigation	Glossary	Library

1. Define Event Types

• Cost Accrual

• Cost Accrual Contra

• Cost WIP (for reversing entries during project closing)

Event Type	Description	Class
Cost Accrual	Cost Accrual Account	Automatic
Cost Accrual Contra	Cost Accrual Contra Account	Automatic
Cost WIP	Cost WIP Account (for reversing entries)	Automatic
Table 1 - 63. Example Cost Accrual Event Types (Page 1 of 1)

2. Define the cost accrual billing extension.

   To define the cost accrual billing extension:

Set up the value sets and descriptive flexfield used in the billing extension definition. The Cost Accrual Billing Extension example requires following five descriptive flexfield segments to be set up on the Billing Extension:

• Cost Accrual Identifier. This value is used by the project verification rules and project status columns extensions to identify events created from the cost accrual billing extension. You must define the cost accrual identifier with a value of COST-ACCRUAL in the ATTRIBUTE11 column. You can define a value set with just one value that is uppercase. The minimum and maximum value is COST-ACCRUAL, with a maximum size of 12.

• Cost Accrual Event Type in the ATTRIBUTE12 column.

• Cost Accrual Contra Event Type in the ATTRIBUTE13 column.

• Cost WIP Event Type in the ATTRIBUTE14 column.

• Cost Basis in the ATTRIBUTE15 column. The cost basis specifies whether to use raw or burdened costs as the Cost WIP and raw or burdened budgeted costs in the cost accrual calculation. The two possible values are R and B. You can define a value set with just two values that are uppercase. The minimum value is B and the maximum value is R. The maximum size is 1.

select event_type

from pa_event_types

where event_type_classification = 'AUTOMATIC'

Note: After you have defined and used the billing extension, you must not change the values of the descriptive flexfield.

b) Define the Billing Extension

You define the billing extension with the following key attributes:

• Procedure: pa_rev_ca.calc_ca_amt. This is the example procedure provided by Oracle Projects. Use your own procedure name, as appropriate.

• Calling Place: Post Regular Processing

• Calling Process: Revenue

• Transaction Independent: Yes

c) Install the Billing Extension Package

You must install the billing extension PL/SQL package. The package that Oracle Projects provides is in the Oracle Projects admin/sql directory. The file names are PAXICOSS.pls and PAXICOSB.pls.

See: Implementing Your Own Cost Accrual Procedures and Extensions.

3. Assign Billing Extension to Project Types

You can also choose to implement a billing extension that you assign to specific projects. To do this, you enable the Project Specific check box in the Billing Extension window. However, for the cost accrual example, you are expected to assign the billing extension at the project type level.

See: Defining Billing Extensions and Project Types.

4. Define AutoAccounting

Cost WIP	1280
Cost Accrual	1285
Cost Accrual Contra	1286

   To define AutoAccounting for Cost WIP and Cost Accruals:

To account for actual raw costs in cost WIP, you must perform the following steps:

• Define an AutoAccounting rule for Cost WIP.

• Assign the Cost WIP rule and other appropriate rules to the Function Transaction of Contract for the following AutoAccounting functions:

• Labor Cost Account

• Expense Report Cost Account

• Usage Cost Account

• Burden Cost Account

• Inventory Cost Account

• Miscellaneous Cost Account

• WIP Cost Account (work in process from Manufacturing)

• Supplier Invoice Cost Account

For more information about burdened costs, see: Burdening (Cost Plus Processing) and Accounting for Total Burdened Costs.

b) Cost Accrual accounts for events resulting from the billing extension

Assign the AutoAccounting rules to the Event Revenue function under the Write-On function transaction (under which Automatic events are accounted). To account for different event types under one function transaction, you must define a rule based on the event types. The rule may be a parameter-based rule that uses a lookup set, or it can be a SQL statement AutoAccounting rule that uses the SQL statement to map the event type to the account value.

Note: The AutoAcccounting rules for the Cost WIP reversing entries created via an event should result in the same accounts as the AutoAccounting rules used to derive the Cost WIP account for costs incurred via expenditure items.

5. Implement Project Verification Rules

Oracle Projects provides an example of how to enforce this requirement in the project verification extension. To implement the requirement, you remove the comments around the section for cost accruals in the project verification extension.

See: Project Verification Extension.

6. Implement Cost Accrual Columns in Project Status Inquiry

The PSI client extension includes an example of how to implement the following columns in columns 28 through 33 in the Project Status Inquiry window:

• ITD - Cost WIP

• PTD - Cost WIP

• ITD - Cost Accrual

• PTD - Cost Accrual

• ITD - Margin

• PTD - Margin

1. Remove the comments around the section for cost accruals in the project status inquiry column extensions. See: PSI Extension.

2. Define the Project Status Inquiry columns listed above, and regenerate the view in the Project Status Inquiry Columns window. See: Project Status Inquiry Setup.