Previous	Next		Contents	Index	Navigation	Glossary	Library

Note: You cannot use the public billing extension procedures or views by themselves or from any other client extension.

In the pages that follow, we provide you with a description of each procedure, information about the parameters available for the procedure, and any additional information you need to use the procedure in your billing extension. Use these procedures and views to:

• Calculate amounts

• Identify transactions processed in the current run

• Insert events

• Retrieve budget amounts

• Handle error conditions

Calculating Amounts

• PA_BILLING_REV_TRANSACTIONS_V (use this in procedures that are called during revenue generation)

• PA_BILLING_INV_TRANSACTIONS_V (use this in procedures that are called during invoice generation)

Identifying Process Run Information

• PA_BILLING_REV_DELETION_V displays the draft revenues that will be deleted in the current draft revenue generation run. Use this view in the billing extension called during the deletion processing of revenue generation.

• PA_BILLING_REV_INV_DELETION_V displays the draft invoices that will be deleted in the current draft revenue generation run. Use this view in the billing extension called during the deletion processing of revenue generation.

• PA_BILLING_INV_DELETION_V displays the draft invoices that will be deleted in the current draft invoice generation run. Use this view in the billing extension called during the deletion processing of invoice generation.

• PA_BILLING_INV_PROCESSED_V displays the invoices that were processed in the current run.

Inserting Events

If this procedure encounters an error, it displays an error message in the log file of the process that called the procedure and does not create an event.

Package.Procedure

pa_billing_pub.insert_event

Parameter	Usage	Type	Description
X_rev_amt	IN	REAL	Revenue amount of event.
X_bill_amt	IN	REAL	Bill amount of event.
X_project_id	IN	NUMBER	ID of the project to which the event is assigned.
X_event_type	IN	VARCHAR2	Event type of event. If a default is not specified, you must provide a value. Event type must have an event type classification of AUTOMATIC.
X_top_task_id	IN	NUMBER	ID of the top task to which the event is assigned.
X_organization_id	IN	NUMBER	ID of event organization.
X_completion_ date	IN	DATE	Completion date of event.
X_event_ description	IN	VARCHAR2	Description of event. If you do not specify a default event description, you must provide a value here.
X_event_num_ reversed	IN	NUMBER	Original automatic event number.
X_attribute_ category	IN	VARCHAR2	Descriptive flexfield context.
X_attribute1-10	IN	VARCHAR2	Descriptive flexfield segments.
X_audit_ amounts1-10	IN	NUMBER	Audit amounts for events.
X_cost_budget_ type_code	IN	VARCHAR2	Audit cost budget type code.
X_rev_budget_ type_code	IN	VARCHAR2	Audit revenue budget type code.
X_error_message	OUT	VARCHAR2	Error message text.
X_status	OUT	NUMBER	Status indicating whether an error occurred. Valid values are: =0 Successful validation <0 Oracle error (message will be written into a log file) >0 Application error
Table 1 - 118. (Page 2 of 2) Insert Event Parameters

Note: If the billing extension is called by revenue generation only, you must set the revenue amount to a nonzero number. You can also set the bill amount. If the revenue amount is positive, the bill amount must also be positive.

Note: If the billing extension is called by invoice generation, you must set the bill amount to a nonzero number. You can also set the revenue amount. If the bill amount is positive, the revenue amount must also be positive.

• If the billing extension creates a new automatic event from a transaction adjustment, the billing extension looks for the original event number (X_event_num_reversed). If the billing extension finds no value, you will receive the error message "You must have specified original event number for ADJ automatic event."

Note: Oracle Projects provides a view that you can use to identify to original automatic event information of the current project, top task, and the credited invoices of the current request:

• PA_BILLING_ORIG_EVENTS_V

Retrieving Budget Amounts

Package.Procedure

pa_billing_pub.get_budget_amount

The parameters include input and output parameters for cost and revenue budget type codes.

Parameter	Usage	Type	Description
X2_project_id	IN	NUMBER	ID of project to retrieve baselined budget amounts.
X2_task_id	IN	NUMBER	ID of top task to retrieve current budget amounts; you must also specify the project ID when you use this parameter.
X2_revenue_amount	OUT	REAL	Baselined revenue budget amount for project or task.
X2_cost_amount	OUT	REAL	Baselined cost budget amount for project or task.
p_cost_budget_ type_code	IN	VARCHAR2	Cost budget type code to be used for calculating cost budget amount. If this value is not specified, the cost budget type in the billing extension setup table is used. If no value is entered in the billing extension setup table, the Approved Cost Budget is used.
p_rev_budget_ type_code>	IN	VARCHAR2	Revenue budget type code to be used for calculating revenue budget amount. If this value is not specified, the revenue budget type in the billing extension setup table is used. If no value is entered in the billing extension setup table, the Approved Revenue Budget is used.
X_cost_budget_ type_code	OUT	VARCHAR2	Cost budget type code that was used for calculating the cost budget in this public API.
X_rev_budget_ type_code	OUT	VARCHAR2	Revenue budget type code that was used for calculating the revenue budget in this public API.
X_error_message	OUT	VARCHAR2	Error message text.
X_status	OUT	NUMBER	Status indicating whether an error occurred. Valid values are: =0 Successful validation <0 Oracle error (message will be written into a log file) >0 Application error
Table 1 - 119. (Page 3 of 3) Get Budget Amount Parameters

Error Handling

Package.Procedure

pa_billing_pub.insert_message

Parameter	Usage	Type	Description
X_inserting_ procedure_name	IN	VARCHAR2	Name of procedure that is inserting the message.
X_message	IN	VARCHAR2	The free text to display as the message in the log file.
X_attribute1-15	IN	VARCHAR2	Descriptive flexfield segments of billing message. These attributes appear in the billing messages table only.
X_error_message	OUT	VARCHAR2	Error message text.
X_status	OUT	NUMBER	Status indicating whether an error occurred. Valid values are: =0 Successful validation <0 Oracle error (message will be written into a log file) >0 Application error
Table 1 - 120. (Page 2 of 2) Insert Message Parameters