Skip to Main Content
Return to Navigation

Using Data from PeopleSoft Asset Management

Using existing in-service asset and depreciation information from your source database is optional. This section lists prerequisites and discusses how to:

Prerequisites

In addition to the prerequisites listed at the beginning of this topic, you can activate the PeopleSoft Application Messaging Enterprise Integration Point (EIP), process asset depreciation calculations, and use asset catalog items in Asset Management by completing these steps:

  1. To synchronize capital acquisition plan (CAP) data between Asset Management and Planning and Budgeting, activate the PeopleSoft Application Messaging EIP for BUDGET_CAP_SYNC using PeopleSoft Application Designer.

    Note: Using the transformation program is an optional step in the EIP setup. Because Planning and Budgeting does not support transformations, Version 1 should be set as a default in both the EPM and Financial Management databases. The purpose is to subscribe and publish CAP information, when required, between the two databases because no asset or depreciation detail data is exported back to PeopleSoft Asset Management.

    If you decide to use the CAP information in Planning and Budgeting, the CAP status values (Approval 1, Approval 2, Approval 3, Closed, Entered, On Hold, and Open) have no effect when used in an asset activity during budgeting.

  2. Run the Depreciation Calculation process (AMDPCALC, but AM_DEPR_CAL application engine in later PeopleSoft releases) to populate the PS_DEPRECIATION record with annual depreciation amounts.

    This process moves stored depreciation amounts from department to department or category to category depending on the transaction that you are performing and the dimensions that you specify.

  3. Run the Asset Period Allocation Setup process (AMALLOC application engine) in the Financial Management database to populate the PS_DEPR_ALLOC_TBL with calendar information used to divide annual depreciation amounts into period amounts.

    Run the Asset Period Allocation Setup process only once after you create a new calendar or modify an existing calendar. When you perform subsequent runs of the Depreciation Calculation process, you do not need to run the Period Allocation process again.

  4. To import asset profiles into the Planning and Budgeting Asset Catalog asset profiles that you create using PeopleSoft Asset Management, run the Load Asset Catalog (AEBDASSTITEM) application engine process that populates the asset catalog record (PS_BD_ASSET_ITEMS) with data from the profile tables (PS_PROFILE_DET_TBL and PS_PROFILE_TBL) in PeopleSoft Asset Management.

  5. Run the Budgets Interface (AMBD1000) SQR process to load in-service assets and their associated depreciation from PeopleSoft Asset Management into the assets (PS_BD_ASSET) and depreciation (PS_BD_ASSET_DEPR) records for mapping to Planning and Budgeting in EPM database.

    Note: Asset depreciation calculations that you run in your financial database for import into Planning and Budgeting should use the same number of periods as that defined for your proposed asset budget.

    The asset activity in Planning and Budgeting cannot support the distribution of amounts across multiple dimensions (ChartFields) for a single asset ID. This rule applies to all in-service asset data from other data sources and newly added assets by preparers during the planning and budgeting process.

    Asset information from any data source should have the same business unit as those used by your planning model.

After you have finished preparing the in-service asset and depreciation data for use by Planning and Budgeting, complete the following steps:

  • Load the asset-related data into the PeopleSoft EPM Warehouses using the delivered ETL tool.

  • In Planning and Budgeting, define asset and account defaults to be used by the asset activities in a planning model on the Asset Budgeting Defaults, Asset Accounts, and Depreciation Accounts pages. To access these pages, from the Planning and Budgeting menu, select select Planning and Budgeting Setup, then select Asset Budgeting Defaults, then select Asset Budgeting Defaults.

  • If you loaded the asset catalog table from PeopleSoft Asset Management, use the Asset Catalog maintenance page in Planning and Budgeting to update any required asset budget defaults or create new catalog items. To access this page, from the Planning and Budgeting menu, select select Planning and Budgeting Setup, then select Asset Budgeting Defaults, then select Asset Catalog.

  • Finally, when creating an asset activity in a planning model that will use the in-service asset and depreciation data, be sure to use a dimension for planning center that corresponds to what is available in the source data loaded from the asset management database.

    For example, if department is the only dimension associated with the asset ID, you will need to use it as your planning center for the asset activity because no process is delivered to map the department ID to a different dimension.

See the product documentation for PeopleSoft FSCM: Asset Management

Setting Up Asset Data Sources

In preparation for staging asset data, you must define the data sources for the asset activity scenario in the planning model. Select select Planning and Budgeting, then select Planning and Budgeting Setup, then select Setup Model, then select Planning Models, then select Activity Scenario, then select and then click the Data Source link for an asset activity scenario.

See Data Source Page.

Note: The imported, in-service asset data in the Planning and Budgeting interface tables is the source data during the model staging process.

You cannot edit in-service assets that you import from PeopleSoft Asset Management in PeopleSoft Planning and Budgeting.

Staging Asset Data

From

To

PS_BD_ASSET

PS_BP_ASSET

PS_BD_ASSET_DEPR

PS_BP_ASSET_DEPR

Note: The asset catalog table does not require staging. When you select an asset catalog item for a new asset, the asset catalog defaults are retrieved from the PS_BP_ASSET_ITEMS table.

The staging process assigns an account for a depreciation row for in-service assets when missing an account value for depreciation. The system populates the depreciation account according to the following hierarchy:

  1. If the field is blank, the system uses the BP_DEPR_ACCOUNT from PS_BP_ASSET.

  2. If the field is blank and the catalog item can be found, the system uses the BP_DEPR_ACCOUNT from the asset catalog for the profile ID assigned to the asset.

  3. The system uses the depreciation account that you specify on the Data Source page.

These rules also apply to in-service asset data when you are running the staging process:

  • Only in-service assets that have a related depreciation impact are supported and processed during data staging.

  • When the dimension member for planning center is missing from the source data, the asset and depreciation rows are dropped and not processed.

  • Only in-service assets that have a depreciation impact to the proposed budget year are processed. This means that the assets must have a budget impact in the time-frame defined by the bottom-up scenario to be staged for an asset activity.

  • Any single asset ID shared by more than one planning center (or any other dimension) cannot be supported and, therefore, will not be processed into the budgeting tables.

    These assets, and any other type of asset in an error condition, are stored in the error table PS_BP_CF_ASSET_ERR, if you want to review them.