Oracle® Fusion
Applications Project Management Implementation Guide 11g Release 1 (11.1.2) Part Number E20384-02 |
Contents |
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.