Due to data entry errors or changes in your organization or business rules, you may need to adjust certain attributes of cross charged transactions. Doing so causes Oracle Projects to reprocess the transactions or to skip the cross charge processes completely. You can adjust a cross charged transaction by:
Changing transfer price base amounts
Changing the provider or receiver organization using the mass update feature
Recompiling burden schedules
Performing splits and transfers
Performing adjustments on the Receivables or Payables invoices
You can mark one or more transactions for cross charge reprocessing in the Expenditure Items window. For example, if you have changed cross charge setup data and want this new information reflected in the affected transfer price amounts and accounting entries, select the Reprocess Cross Charge option in the Reports menu of the Expenditure Items window.
Marking a transaction for cross charge reprocessing:
Resets the cross charge type to Null
Resets the cross charge processing method to Pending
Resets the cross charge processing status to Never Processed
Resets the transfer price amount in all currencies to Null
Redetermines the cross charge type and processing method
The next time you run the cross charge processes, they will process these transactions as new cross charged transactions.
You should mark affected transactions for cross charge reprocessing if you have changed any of the following information:
Provider or receiver organization. Modifying the Provider and Receiver Organizations Override extension or changes in your organizational structure can result in changes to the provider or receiver organization of a cross charged transaction, which could affect the cross charge type, the processing method, or the transfer price rules.
Transfer price setup data. Any change to your transfer price rules could result in a new transfer price amount determined for cross charged transactions that have already been processed.
Cross-charge setup data. Any change to your cross charge or internal billing implementation options, provider and receiver controls, or cross charge project and task information can affect how Oracle Projects processes cross charged transactions.
Account codes. Changes to the provider reclassification accounting options can result in changes to the provider cost reclassification accounts. Any changes to the AutoAccounting setup for cross charge functions can also affect existing cross charge accounting entries.
Billable flag. For cross charged transactions processed by intercompany billing with the provider cost reclassification feature enabled, changes to the Billable flag of a transaction on a contract project can result in new provider cost reclassification accounting entries.
Tax classification codes. The Generate Intercompany Invoice processes determine the appropriate tax classification code for each invoice line. If you modify the logic used to derive the tax classification codes and have already released invoices, you must mark the affected transactions for cross charge reprocessing. Oracle Projects automatically creates a credit memo for the original invoice and a new invoice with the new tax classification codes.
You can mark one or more transactions so that the cross charge processes skip the specified transactions. To do this, choose Mark For No Cross Charge Processing in the Reports menu of the Expenditure Items window.
Marking a transaction as not requiring cross charge processing resets the cross charge processing method to No Cross Charge Processing and the cross charge processing status to Never Processed.
You can reconvert transfer price amounts from the transaction currency if you change the transfer price exchange rate date type and exchange rate type, which govern how Oracle Projects converts the transfer price amount from the transaction currency to the functional currency. To do this, you choose the Change Transfer Price Currency Attributes option from the Reports menu in the Expenditure Items window. A change in these conversion attributes may result in a change to the transfer price amount in the functional currency.
Both provider and receiver operating units can change the transfer price conversion attributes.
Changing your transfer price currency conversion attributes:
Replaces conversion attributes for the functional currency
Resets existing transfer price amounts in the functional currency to Null
Resets the cross charge processing status to Never processed
You can perform the following adjustments to cross charged transactions. These adjustments automatically mark the transaction for cross charge reprocessing.
Changing transfer price base amounts. If you recalculate raw or burdened cost or revenue amounts, the amount of the transfer price basis (and the final transfer price amount) of a cross charged transaction may also change. The respective cost distribution and revenue generation processes determine whether such recalculations affect the transfer price amount of any cross charged transactions and automatically mark the transactions for cross charge reprocessing.
The cost distribution and revenue generation processes automatically resets the cross charge processing status to Never Processed and blanks out the transaction's transfer price amount.
Changing the provider or receiver organization using the mass update feature. If you use the mass update feature to change the organization that owns a project or task, Oracle Projects marks all transactions (with an expenditure date after the effective date of the organization change) for cross charge reprocessing. A different project (or receiver) organization could result in a change to the transaction's cross charge processing method.
Oracle Projects automatically marks the affected items for cross charge processing.
Recompiling burden schedules. If the user changes and recompiles a burden schedule that has been used for determining the transfer price of some items, the recompile process will mark these items for cross charge reprocessing by resetting the cross charge type to Null, the cross charge processing method to Pending, and the cross charge processing status to Never Processed.
Performing transfers and splits. Transferring or splitting a cross charged transaction does not affect the cross charge processing method of the existing transactions. The reversing and new transactions will undergo the cross charge processes as usual.
The Generate Intercompany Invoice processes group the invoice details for all adjusting transactions by the invoice number and line number of the original transactions for credit memo processing.
Performing adjustments on the Receivables or Payables invoices. You can adjust invoice level accounting information for Receivables and Payables invoices, as described below:
Intercompany Receivables account (for Receivables invoices). The Interface Intercompany Invoices to Receivables process determines the intercompany receivables account for each invoice. If you change the rules used to determine this account, you must manually cancel the invoice from the Invoice Review window. Oracle Projects automatically creates a credit memo with details reversing each line in the original invoice. All items on the cancelled invoice are eligible for intercompany rebilling. Once rebilled, the Interface Intercompany Invoices to Receivables process will determine the account for the new invoice using the modified rules.
You cannot cancel an invoice if payments have been applied against it in Oracle Receivables or if an invoice has credit memos applied against it. You can cancel an invoice only if it is released and has no payments, adjustments, or crediting invoices applied against it. Once the cancellation is completed, you cannot delete the credit memo created by the cancellation action. That is, you cannot reverse an invoice cancellation.
Intercompany cost account (for Payables invoices). In Oracle Payables, reverse the invoice distribution with the incorrect intercompany cost account and create a new line with the correct account information.