How Oracle Projects Handles Supply Chain Transactions with Multiple Cost Distributions

How Projects groups multiple cost distributions

Project-related supply chain costs with multiple cost distributions in Fusion Cost Management are imported into Projects as multiple project cost transactions and treated as a group.

The grouping is based on the inventory cost distribution layer identifier for the applicable cost distributions in Fusion Cost Management.

Within the group:

One project cost transaction, either a material or resource cost, displays the transaction quantity.
Other project cost transactions in the group display a quantity of zero.
The Source Transaction Quantity attribute retains the source quantity for every transaction in the group.

This grouping prevents the same physical quantity from being counted multiple times while preserving quantity information for each individual project cost transaction.

Source attributes for grouped transactions

Use these attributes to identify the source transaction and grouping information for project-related supply chain costs with multiple cost distributions.

Source attributes for grouped transactions

Attribute	What it identifies
Source Transaction Quantity	The source quantity associated with each transaction in the group.
Source Transaction Type	The inventory transaction type associated with the group.
Source Distribution Layer Reference	The grouping identifier associated with the cost distributions imported from Fusion Cost Management.

You can add these columns to the transaction list views on the Manage Unprocessed Costs, Manage Cost Distributions, and Manage Project Costs pages in the Project Costing and Project Management work areas.

Example: Quantity tracking for a Cable transaction

Suppose Projects imports a project-related supply chain cost for the inventory item Cable. The item has Material and Overhead cost components.

Fusion Cost Management creates cost distributions for the cost elements, and Projects imports them as individual project cost transactions. The applicable distributions are grouped using the inventory cost distribution layer identifier, represented by the Source Distribution Layer Reference attribute.

The Material transaction carries the quantity for the group. The Overhead transactions have a Quantity value of zero, while Source Transaction Quantity continues to show the original quantity on each transaction.

Material Transaction Details

Transaction Number	Project Number	Task Number	Inventory Item	Expenditure Type	Quantity	Source Transaction Quantity	Source Transaction Type	Source Distribution Layer Reference
7234500	PDSC-TEST-001	1.2.2	Cable	Material	3	3	Miscellaneous Receipt	12345
7234501	PDSC-TEST-001	1.2.2	Cable	Overhead	0	3	Miscellaneous Receipt	12345
7234502	PDSC-TEST-001	1.2.2	Cable	Overhead	0	3	Miscellaneous Receipt	12345

The example shows that Quantity is represented once for the group, while Source Transaction Quantity remains available on every transaction.

How quantity-based adjustments affect grouped transactions

When you perform a quantity-based adjustment such as Split, Split and Transfer, or Transfer on a project-based supply chain cost in a group, the adjustment affects all project cost transactions in that group.

The adjustment updates the applicable Quantity and Source Transaction Quantity values. The adjustment pages notify you about the impact and show the related transactions that will be affected.

When reconciling quantity balances with the source application after adjustments, consider the quantity information across all adjustments.

Non-quantity adjustments, including changes to billable and capitalizable values and applying or releasing invoice and revenue holds, can be performed on individual transactions.

How grouped transactions are billed

For invoicing, the application includes zero-quantity and non-zero-quantity transactions that meet the invoicing eligibility criteria.

For amount-based invoices, eligible transactions are included in invoice line distributions according to their billable or non-billable status.

Rate-based billing doesn't apply to zero-quantity transactions.

Forecast with grouped transaction quantities

The application rationalizes quantities across the project cost transactions in a group to reflect the actual quantities recorded in supply chain activities.

You can use these quantities to compare planned and actual figures and forecast requirements for supply chain inventory items planned on your project.

Report on grouped supply chain transactions

Project Costing OTBI subject areas expose quantity and grouping attributes for project-based supply chain costs.

The following subject areas provide Source Transaction Quantity, Source Transaction Type, and Source Distribution Layer Identifier:

Actual Cost Real Time
Expenditure Items Performance Real Time
Unprocessed Transactions Real Time
Projects Cross Subject Area Analysis - Cross Transaction Measures

Manage grouped transactions with REST APIs

The Project Costs and Unprocessed Project Costs REST APIs expose Source Transaction Quantity, Source Transaction Type, and Source Distribution Layer Identifier for managing supply chain transactions with multiple cost distributions.

Considerations for grouped supply chain costs

If you define the PJC_ZERO_QTY_NONBILL profile, zero-quantity transactions in the group are marked non-billable during import and adjustments. You can update billable information for applicable project cost transactions manually at the transaction level.
When you update expenditure types for transactions in a group, use an expenditure type of the same nature: rate-based to rate-based, or non-rate-based to non-rate-based.
Split and Split-and-Transfer adjustments aren't supported for supply chain-based project costs that include acquisition cost adjustments such as invoice price variances.
Equal-quantity adjustments for grouped supply chain-based project costs are supported only for Split-and-Transfer adjustments.