Currency Support:The Project Cost Collector collects the costs of project-related organization's default cost group transactions, then passes these costs by project, task, and expenditure type to the Transaction Import Interface table in Oracle Projects. These transactions can then be imported into Oracle Projects.
You can view and resubmit project transactions that fail to transfer using the Cost function View Material Transactions window.
Enable Project Manufacturing costing. See: Setting Up Project Manufacturing Costing.
Perform project-related cost transactions. See: Project Manufacturing Costing Transactions.
Currency Support:When there is a separate reporting ledger, the Cost Collector collects both functional and reporting currency information. This information is passed to Projects and made available for reporting. A transaction (such as PO, Direct IO) created in a currency other than the functional currency of the organization, is transferred to Projects using the functional currency. For inventory and WIP transactions, the accounting currency is the same as the functional currency.
Transferring Project Costs:The Cost Collector collects all Project Manufacturing-related costs and inserts them into the Transaction Import Interface Table of Oracle Projects. Each of these records includes the project, task, and expenditure type reference required by Oracle Projects.
The Cost Collector derives the accounting information from the manufacturing subledger unless the accounting extension is used to customize project accounts. See: Client Extensions.
Note: If you perform Inventory or other manufacturing transactions for a project owned by an operating unit other than the operating unit of the Inventory organization, then you must run the Cost Collector from a responsibility that has the profile option (MO: Operating Unit profile), set to the project owning operating unit.
If Cost Element to Expenditure Type Association is not set up, and the profile option Project Miscellellaneous Transaction Expenditure Type is user defined, then cost collection will take place only for Project Miscellaneous transactions.
Cost collection errors out for any organization that has the cost collection feature turned off. You can turn on Cost Collection if Oracle Projects is installed.
Records in the Transaction Import Interface Table can then be imported into Oracle Projects using Transaction Import in Oracle Projects. See: Transaction Import.
To collect project related cost:Navigate to the Project Cost Transfer window. Submit a request for the Cost Collection Manager. The Parameters window appears.
Specify the project cost collection time fence, the Number of Days to Leave Costs Uncollected, by entering a whole number of days.
For example, suppose today is Thursday and project costs were collected up through Friday of the previous week. If you enter 4 as the Number of Days, costs will be collected for Saturday and Sunday.
If there are uncosted transaction records in the MTL_MATERIAL_TRANSACTIONS table within the specified time fence, then project costs for these transactions are not collected. You can check to see if transactions are uncosted, as indicated by the costed indicator, through the Material Transactions window. See: Viewing Material Transactions.
Uncosted transactions and transactions that lack complete information are flagged Error.
Choose Submit to run the request.
