Asset Integration Rules

The asset integration rules that you establish at the business unit level appear as default values when you create projects. You can override the default asset integration rules at the project level. Activities inherit asset integration rules from the project level. Some of these rules are not available to change at the activity level based on the project-level option that you select to distribute project costs to assets.

Asset integration rules consist of:

• Asset integration defaults which consist of an option to enable integration with PeopleSoft Asset Management, the integration type (capitalization or retirement), and the filter that identifies the rows from the Project Transaction table (PROJ_RESOURCE) that are eligible for retirement or capitalization.

• Rules that specify how to identify an asset.

  For example, you can instruct the system to create only one asset for each activity, or one asset from many activities, and so on.

• Timing triggers that specify when to create an asset.

  For example, you can specify that asset processing can create a new asset when a project status is approved, or an activity is 95 percent complete, and so on.

• The asset location source that indicates if the asset integration process uses the asset definition's location code or the activity definition's location code to determine the asset's location.

• Rules that specify the destination of the asset rows that result from the capitalization processes.

  For example, you can choose to: Summarize asset transaction rows in the PC to AM (Project Costing to Asset Management) Staging table (PROJ_AM), but not send the rows to the PeopleSoft Asset Management Loader tables (INTFC_FIN and INTFC_PHY_A). If you do not require asset approval prior to sending assets to PeopleSoft Asset Management, you can:

  • Summarize asset transaction rows in the PC to AM Staging table and send them to the PeopleSoft Asset Management Loader tables, but not send the rows to the PeopleSoft Asset Management transaction tables.

  • Summarize asset transaction rows in the PC to AM Staging table, send them to the PeopleSoft Asset Management Loader tables, and send the rows to the PeopleSoft Asset Management transaction tables. This option is available if you do not require asset approval prior to sending assets to PeopleSoft Asset Management.

• Rules that specify how to adjust assets.

Inherit Asset Integration Rules from Programs

You can set up a project to inherit its asset integration rules from a program instead of from the business unit by entering the program name on the Asset Integration Rules page for a project. Use this functionality if there is a summary project or program that contains child projects, each of which need to contribute transaction costs to the same asset.

When you use the program asset integration rules for a project that belongs to the program, the system:

• Overrides all of the rules on the project to match the specified program.

• Overrides all of the rules for activities that are already associated with the project to match the parent project.

• Disables all of the integration rules, except for the rules in the Asset Integration Defaults group box on the Asset Integration Rules page.

  The disabled fields are available for editing again if you deselect the Inherit from Program field and save the page.

• Prevents a change to the identification option if assets are related to the project.

When you change the asset integration rules at the program level, the system also changes the corresponding project and activity rules to keep the rules synchronized across all projects that contribute to an asset.

End-of-Year Rule

The Express Capitalization process triggers end-of-year processing. You can select one of these options that determines how the system treats asset adjustments at the end of the fiscal year:

• Ignore end of year: The system creates asset adjustments as if there is no designated end of year.

• Create parent/child assets: The system creates new assets that are children to the original (now parent) assets if adjustments are sent from the project after the specified end of the year. All adjustments belong to the child assets.

• Create new asset: The system creates new assets if adjustments are sent after the specified end of the year. All adjustments belong to new assets instead of child assets.

• Stop sending adjustments: The system does not send adjustments to PeopleSoft Asset Management after the specified end of year.

The system assigns the next available asset ID automatically when it creates a new asset during end-of-year processing. In this situation you cannot manually assign the asset ID.

The in-service date of an asset is used as the reference point to determine the end of a year. So, an asset in-service date of December 1, 2005, a last month of year of December, and a last day of year of 31, allows only one month before the end-of-year treatment occurs after December 31, 2005. An asset with an in-service date of January 1, 2006, however, has one year until the end-of-year treatment occurs after December 31, 2006.

The following table provides examples of how adjustments are treated for all four end-of-year rules. Assume in these examples that you use a 5-4-4 quarter and the current fiscal year ends on April 2, 2005:

Scenario	Ignore End of Year	Create Parent/Child Assets	Create New Asset	Stop Sending Adjustments
Project Asset 1 created and sent to PeopleSoft Asset Management with an in-service date of February 24, 2005. The cost of the asset is 10,000.00 USD.	No adjustment is made at this time	No adjustment is made at this time	No adjustment is made at this time	No adjustment is made at this time
An adjustment of 2,000.00 USD is made to asset. The run date of the PC_EXPRSS_AM process is April 1, 2005.	2,000.00 USD is added to Asset 1	2,000.00 USD is added to Asset 1	2,000.00 USD is added to Asset 1	2,000.00 USD is added to Asset 1
An adjustment of 1,500.00 USD is made to asset. The run date of the PC_EXPRSS_AM process is April 16, 2005.	1,500.00 USD is added to Asset 1	New child asset with a cost of 1,500.00 USD is created with Asset 1 as its parent	New asset with a cost of 1,500.00 USD is created and does not have Asset 1 as its parent	No adjustment is sent to PeopleSoft Asset Management