Implementing Your Own Cost Accrual Procedures and Extensions (Oracle Projects Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Implementing Your Own Cost Accrual Procedures and Extensions

Your business requirements for cost accruals may be different from those addressed in the cost accrual example that Oracle Projects provides. If this is the case, you must design and create your own billing extension and appropriate setup data to match your requirements.

Listed below are some of the business requirements for cost accruals that may vary in your company from the cost accrual example provided by Oracle Projects:

The cost accrual calculation. For example, you may calculate cost accruals to be equal the cost WIP, instead of calculating cost accruals based on the budgets as in the cost accrual example.

The number of accounts to which you charge cost WIP or cost accruals. The cost accrual example uses one account for each bucket: Cost Accrual, Cost Accrual Contra, and Cost WIP. If you charge your cost WIP to many accounts, you will need to create your own cost accrual billing extension to account for the many cost WIP accounts that you use.

What is considered cost WIP. The cost accrual example includes all costs in cost WIP. If you need to exclude certain costs from the cost WIP calculation, you need to change your cost accrual implementation.

Oracle Projects provides a template package and procedure that you use as the basis of your cost accrual extension procedures. The name of the package is pa_rev_ca.

Print out and review the following files before you begin writing cost accrual billing extensions. The files are located in the Oracle Projects admin/sql directory.

PAXICOSB.pls. Package Body Template. This file contains the procedure that you modify to implement cost accrual billing extensions. You can define as many procedures as you like within this package or within the predefined procedure.

PAXICOSS.pls Package Specification Template. If you create procedures within the package outside the predefined procedure, you must also modify this file.

Suggestion: After you write the procedure, do not forget to compile it and store it in the database. See: Storing Your Procedures.

You can base your cost accrual billing extension on the one provided by Oracle Projects. You must not change the example billing extension definition or the logic. You can copy the definition and the PL/SQL package to use as a starting point for your own billing extension. You are responsible for the support and upgrade of your cost accrual implementation, including the billing extension procedure and logic.

PAXICOSB.pls.	Package Body Template. This file contains the procedure that you modify to implement cost accrual billing extensions. You can define as many procedures as you like within this package or within the predefined procedure.
PAXICOSS.pls	Package Specification Template. If you create procedures within the package outside the predefined procedure, you must also modify this file.

Implementing Your Own Cost Accrual Procedures and Extensions

See Also