Allocation rules define how allocation transactions are to be generated, including:
The source of the amounts you are allocating
The targets-the projects and tasks to which you want to allocate amounts
How much of the source pool you want to allocate, and if you want to include a fixed amount, GL balance, or client extension (or any combination of these)
The time period during which the rule is valid
You can create as many rules as you want, and use them in as many allocation runs as you want.
You can leave the original expenditure amounts in the source project, or offset the amounts with reversing transactions. In most cases, the reversing transactions decrease the project balance by the amount of the allocation.
Note: When you define sources, if you exclude a resource, then Oracle Projects excludes the entire amount for that resource regardless of the specified percentage. See: Defining the Sources.
Each allocation rule belongs to an operating unit and cannot be shared with other operating units.
Allocation rule source projects must be from the same operating unit unless cross charge is enabled. If cross-charge is enabled, you can allocate to target projects that are in different operating units from the source project operating unit. Offset projects must always be in the same operating unit as source projects. See: Implementation Options in Oracle Projects: Cross Charge: Allow Cross Charges to All Operating Units Within Legal Entity, Oracle Projects Implementation Guide.
Other Sources
Defining Allocation Rules, Oracle Projects Implementation Guide