Writing Billing Extension Procedures (Oracle Projects Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Writing Billing Extension Procedures

Oracle Projects revenue and invoice generation programs call your billing extension procedures which define the logic to calculate and create automatic events according to your rules.

Your procedure can call other procedures or views. You can use predefined procedures and views, or you can write your own procedures. We discuss these predefined procedures and views in more detail in the pages that follow.

Procedure Template

Oracle Projects provides a template package and procedure that you use as the basis of your billing extension procedures.

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

PAXITMPS.pls Billing Extension Package Specification Template. This file contains the procedure that you modify to implement billing extensions. You can define as many procedures as you like within this package or within the predefined procedure.

PAXITMPB.pls Billing Extension Package Body Template. If you create procedures within the package outside the predefined procedure, you must also modify this file.

The following table lists the parameters that Oracle Projects provides for the billing extension procedure.

Parameter Usage Type Description

X_project_id IN NUMBER Identifier of the project of the billing assignment.

X_top_task_id * IN NUMBER Identifier of the top task of the billing assign. This parameter has a value in the following cases: 1) Billing extension assigned to top task 2) Project for which a billing extension is applicable is funded at the top task level. The billing extension is executed once for each authorized top task belonging to the project.

X_calling_process IN VARCHAR2 Specifies whether the revenue or invoice program is calling the billing extension. The possible values of this parameter are Revenue or Invoice.

X_calling_place IN VARCHAR2 Specifies where the billing extension is called in the revenue or invoice program. Possible values are PRE, POST, REG, or ADJ.

X_amount IN NUMBER The amount entered on the billing assignment.

X_percentage IN NUMBER The percentage entered on the billing assignment.

X_rev_or_bill_date IN DATE Specifies the accrue through date if called by revenue generation, or the bill through date if called by invoice generation.

X_bill_extn_ assignment_id IN NUMBER ID of the billing assignment being processed. Use this to select information (such as descriptive flexfield values) from the billing assignment.

X_bill_extension_id IN NUMBER ID of the billing extension being processed. Use this to select information (such as descriptive flexfield values) from the billing extension definition.

X_request_id IN NUMBER Request ID of the current run.

* You cannot create project level events for projects using task level funding. You must write your billing extensions so that they work if they are called with or without this parameter.

Table 1 - 117. (Page 2 of 2) Billing Extension Parameters

Parameter	Usage	Type	Description
X_project_id	IN	NUMBER	Identifier of the project of the billing assignment.
X_top_task_id *	IN	NUMBER	Identifier of the top task of the billing assign. This parameter has a value in the following cases: 1) Billing extension assigned to top task 2) Project for which a billing extension is applicable is funded at the top task level. The billing extension is executed once for each authorized top task belonging to the project.
X_calling_process	IN	VARCHAR2	Specifies whether the revenue or invoice program is calling the billing extension. The possible values of this parameter are Revenue or Invoice.
X_calling_place	IN	VARCHAR2	Specifies where the billing extension is called in the revenue or invoice program. Possible values are PRE, POST, REG, or ADJ.
X_amount	IN	NUMBER	The amount entered on the billing assignment.
X_percentage	IN	NUMBER	The percentage entered on the billing assignment.
X_rev_or_bill_date	IN	DATE	Specifies the accrue through date if called by revenue generation, or the bill through date if called by invoice generation.
X_bill_extn_ assignment_id	IN	NUMBER	ID of the billing assignment being processed. Use this to select information (such as descriptive flexfield values) from the billing assignment.
X_bill_extension_id	IN	NUMBER	ID of the billing extension being processed. Use this to select information (such as descriptive flexfield values) from the billing extension definition.
X_request_id	IN	NUMBER	Request ID of the current run.
* You cannot create project level events for projects using task level funding. You must write your billing extensions so that they work if they are called with or without this parameter.
Table 1 - 117. (Page 2 of 2) Billing Extension Parameters

Contents

Index

Navigation

Glossary

Library

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