Cross charge controls specify:
Which projects and tasks in which operating units can receive transactions from a provider operating unit
How Oracle Projects processes these cross charged transactions
Cross-charge controls affect all cross charge transactions, regardless of how you enter them. For maximum control, you can use a combination of cross charge and transaction controls to ensure that only valid cross charges are charged to a specific project and task.
Cross charge controls are defined at the operating unit, project, and task levels. Oracle Projects applies these controls based on a transaction's cross charge type and cross charge processing method.
You can charge intra-operating unit cross charges (that is, charges within an operating unit) to any project and task owned by your expenditure operating unit. You can modify the transaction control extension to restrict intra-operating unit cross charge transactions.
Oracle Projects provides controls to identify:
Which projects and tasks in a receiver operating unit can receive inter-operating unit cross charges from a provider operating unit
Which cross charge processing method to apply to these transactions.
Steps performed by the provider operating unit:
Define cross charge implementation options: Specify whether to allow cross charge and select a default processing method.
Define internal billing implementation options: Specify whether the operating unit is a provider for internal billing.
Define provider controls: Select a processing method and specify the name of the intercompany billing project.
Steps performed by the receiver operating unit:
Define internal billing implementation options: Specify whether the operating unit is a receiver for internal billing.
Define receiver controls: Specify the name of each provider operating unit that can charge transactions to the specified receiver operating unit.
Enable cross charge for projects: In the Projects window (Cross Charge option), select Allow Charges from other Operating Units.
Oracle Projects provides flexible controls to identify:
Which projects and tasks in a receiver operating unit can receive intercompany cross charges from a provider operating unit
Which cross charge processing method to apply to these transactions.
Optionally, when you enable the Derive Legal Entity from Organization Setup check box, the legal entities are derived from the respective provider or receiver organizations, if associated with legal entity establishment
Note: You can charge intercompany cross charge transactions only to indirect and contract projects. You cannot charge intercompany cross charge transactions to capital projects.
Steps performed by the provider operating unit
Define internal billing implementation options: Specify whether the operating unit is a provider for internal billing.
Define provider controls: Specify the name of each receiver operating unit that can receive transactions from the specified provider operating unit. Also, select a processing method and specify the name of the intercompany billing project.
Note: If the Derive Legal Entity from Organization Setup check box is enabled, you can select the respective legal entity along with operating unit.
Steps performed by the receiver operating unit
Define internal billing implementation options: Specify whether the operating unit is a receiver for internal billing.
Define receiver controls: Specify the name of each provider operating unit that can charge transactions to the specified receiver operating unit.
Enable cross charge for projects: In the Projects window (Cross Charge option), select Allow Charges from other Operating Units.
Note: If Cross Business Group Access is enabled, the provider and receiver operating units can be in different business groups. See: Oracle HRMS Configuring, Reporting, and System Administration Guide.