Integrating with PeopleSoft Project Costing
This topic provides an overview of integrating PeopleSoft Asset Management with PeopleSoft Project Costing.
Assets that originate in Project Costing are usually the outcome of construction projects. They can accumulate cost information associated with salvage and removal costs, proceeds from sales, and the like.
When you establish integration between PeopleSoft Asset Management and PeopleSoft Project Costing, you can perform the following processes from PeopleSoft Project Costing:
Set up express capitalization.
Set up manual capitalization.
Define express assets and relate them to projects.
Capitalize assets by using express capitalization.
Capitalize assets by using manual capitalization.
Review and approve assets.
Retire assets.
PeopleSoft Project Costing can also send cost information to PeopleSoft Asset Management for group assets that have not yet been consolidated. The cost for unrealized assets is accumulated as a pseudo group member asset, and depreciated at the group asset level.
Project Costing sends asset information directly to the Asset Management Loader Tables (INTFC_FIN and INTFC_PHY_A) by means of the Project Costing-Asset Management Integration Application Engine process (RUN_PC_AM). This enables you to depreciate costs with a project before its completion.
Note: PeopleSoft Asset Management creates transactions in Asset Management tables from other feeder systems by using the Transaction Loader (AMIF1000) application engine. Transactions for existing assets that have a status of Retired or Transferred are not passed through the Transaction Loader; they are processed within their respective components.
Once you have transferred data from Project Costing, you can preview data in the loader tables, approve the load lines, approve the interface ID, and run the Transaction Loader process to transfer the data into Asset Management tables.
The Transaction Loader tables load using the express automated process.
The approval of the data in the Transaction Loader tables can be set to automatically approve or to require manual review and approval.
The Transaction Loader Approval interface enables you to review and cancel the process.
You can then go back to the source systems to correct data that may not be loading as anticipated.
The Transaction Loader process can run automatically when:
Asset profiles have been defined.
Unitization and consolidation rules have been defined for the project.
Items have been defined as serialized or nonserialized.
Asset Capitalization triggering rules have been established for the project.
One or more assets have been created from the project costs and put in service.
Depreciation schedules have been activated so that depreciation expenses are generated.
The assets have been updated in the Asset Repository.
Parent-child and component relationships have been established among the assets if needed.
Adjustments to assets have been recorded so that an existing asset's values reflect accurately.
Note: If you are sending parent-child assets from Project Costing, the Transaction Loader relies on information that you have defined on the Asset Definition page of the Capitalize Project Assets component to accurately create the asset definition in Asset Management. If you have identified an existing parent asset for the asset that you are capitalizing from Project Costing, the Transaction Loader automatically creates a child asset. If you enter an asset ID in Project Costing, and also enter that same asset ID in the Parent ID field and it does not exist in the Asset Management PARENT_ASSET table, Transaction Loader creates a parent asset.