Oracle® Fusion Applications Project Financial Management Implementation Guide 11g Release 7 (11.1.7) Part Number E36898-02 |
Home |
Contents |
Book List |
Contact Us |
Previous |
Next |
This chapter contains the following:
Extensions for Define Cross-Charge Options
Use this client extension to enforce cross-charge rules at a higher level in the organization hierarchy than the level at which you assign resources and projects. Doing so provides a single place for you to enforce and maintain your business rules in all organizations in your enterprise.
The extension is identified by the following items:
Extension Component |
Name |
---|---|
Body template |
pjc_client_extn_cc_ident.pkb |
Specification template |
pjc_client_extn_cc_ident.pkh |
Package |
pjc_client_extn_cc_ident |
Procedure |
override_prvdr_recvr |
Important
Do not change the name of the extension procedure or parameters. Also, do not change the parameter types or parameter order in the procedure. After you write a procedure, compile it and store it in the database.
The system identifies cross-charged transactions based on the provider and receiver organizations for the transaction. It derives default values for these organizations as follows:
Provider organization: The expenditure organization or nonlabor resource organization for usage transactions.
Receiver organization: The organization that owns the task or project to which the transaction is charged.
To override the cross-charge identification, code this extension to use a higher level in the organization hierarchy to derive the appropriate provider and receiver organizations and then determine if a transaction is a cross-charge transaction.
This extension is called by the Identify Cross-Charge Transactions process. If you use the Borrowed and Lent Accounting cross-charge processing method, the application automatically calls the Identify Cross-Charge Transactions process as part of the Distribute Borrowed and Lent Amounts process. However, if you use the Intercompany Billing cross-charge processing method, you must manually run the Identify Cross-Charge Transactions process.
Use the Cross-Charge Processing Method Override Extension to have custom business rules that help you identify how to process cross-charged transactions.
Use this extension to:
Exclude certain cross-charged transactions from cross-charge processing
Change the cross-charge processing method, such as from Intercompany Billing to Borrowed and Lent Accounting
Note
Use this extension only on cross-charged transactions.
The extension is identified by the following items:
Extension Component |
Name |
---|---|
Body template |
pjc_client_extn_cc_ident.pkb |
Specification template |
pjc_client_extn_cc_ident.pkh |
Package |
pjc_client_extn_cc_ident |
Procedure |
override_cc_processing_method |
Important
Do not change the name of the extension procedure or parameters. Also, do not change the parameter types or parameter order in the procedure. After you write a procedure, compile it and store it in the database.
The system validates the value returned for the cross-charge code to ensure that it meets the following rules:
Cross-Charge Transaction Type |
Allowed Processing Methods |
---|---|
Within a business unit |
Borrowed and Lent Accounting |
Between business units |
Borrowed and Lent Accounting Intercompany Billing |
Between legal entities |
Intercompany Billing |
This extension is called by the Identify Cross-Charge Transactions process. If you use the Borrowed and Lent Accounting cross-charge processing method, the application automatically calls the Identify Cross-Charge Transactions process as part of the Distribute Borrowed and Lent Amounts process. However, if you use the Intercompany Billing cross-charge processing method, you must manually run the Identify Cross-Charge Transactions process.
The Identify Cross-Charge Transactions process:
Identifies the transaction as a cross-charged transaction.
Determines the cross-charge processing set method based on the cross-charge options.
Calls the extension to override the cross-charge processing method.
Use the Internal Payables Invoice Attribute Override Extension to override the default expenditure type and expenditure organization attributes for intercompany and interproject invoices that are created in Oracle Fusion Receivables.
The Update Invoice Details from Receivables process calls the Internal Payables Invoice Attribute Override Extension as it creates Oracle Fusion Payables invoices for intercompany and interproject contracts.
Note
Use this extension only if you want to override the receiver expenditure organization and receiver expenditure type on the Oracle Fusion Payables invoice. The source of the receiver expenditure organization and expenditure type is the intercompany or interproject contract.
The extension is identified by the following items.
Extension Component |
Name |
---|---|
Body template |
pjb_cc_ap_inv_client_extn.pkb |
Specification template |
pjb_cc_ap_inv_client_extn.pkh |
Package |
pjb_cc_ap_inv_client_extn |
Procedure |
override_exp_type_exp_org |
This billing extension can derive the receiver expenditure type and receiver expenditure organization based on the parameters you enter.
Parameters
Information about parameters for this billing extension are in the table below.
Parameter Name |
Description |
---|---|
p_internal_billing_type |
Internal billing type Valid values are:
|
p_contract_id |
Contract ID for the Oracle Fusion Receivables invoice. |
p_contract_line_id |
Contract line ID for the Oracle Fusion Receivables invoice. |
p_receiver_project_id |
Receiver project ID for the Oracle Fusion Payables invoice. |
p_receiver_task_id |
Receiver task ID for the Oracle Fusion Payables invoice. |
p_invoice_number |
Invoice number from the pjb_invoice_header table. |
p_draft_invoice_line_num |
Invoice_line_num from pjb_invoice_line. |
p_invoice_date |
Invoice date |
p_ra_invoice_number |
Oracle Fusion Receivables invoice number. The invoice number is either user-entered or created by the application, as defined in the implementation options. Refer to ra_invoice_number from pjb_invoice_headers |
p_provider_org_id |
Provider business unit ID |
p_receiver_org_id |
Receiver project organization ID |
p_cc_ar_invoice_id |
Customer transaction ID created in ra_customer_trx_all.customer_trx_id |
p_cc_ar_invoice_line_num |
Line number from ra_customer_trx_lines_all.line_number. |
p_contract_line_customer_id |
Customer ID on the bill plan associated with the contract line. |
p_vendor_id |
Supplier ID (poz_suppliers.vendor_id) |
p_vendor_site_id |
Supplier site ID (poz_supplier_sites_all_m.vendor_site_id) |
p_expenditure_type |
Expenditure type defined on the contract line internal attribute. |
p_expenditure_type_id |
Expenditure type ID defined on the contract line internal attribute. |
p_expenditure_organization_id |
Expenditure organization defined on the contract line internal attribute. |
x_expenditure_type_id |
Expenditure type ID returned by the extension. |
x_expenditure_type |
Expenditure type returned by the extension. |
x_expenditure_organization_id |
Expenditure organization ID returned by the extension. |
x_status |
Return status of the extension. |
x_Error_Stage |
Error stage returned by the extension. |
X_Error_Code |
Error code returned by the extension. |