Understanding Mass Transaction Manager

Regular business cycles sometime require you to make the same change to a large group of assets. The ability to adjust and transfer many assets at once is essential to efficient asset management. To help you with this aspect of asset management, PeopleSoft introduces the Mass Transaction Manager tool, which can used to carry out the necessary changes to your assets.

Suppose a business restructuring requires you to transfer all assets from the marketing department to the corporate communications department. Transferring these assets manually can be onerous and likely to introduce errors. Mass Transaction Manager, on the other hand, enables you to select a particular set of assets from the database, define the desired changes on those assets, and make those changes by running the Mass Transaction application engine.

You can use Mass Transaction Manager to define mass transactions and simplify mass transaction definition by storing information that enables you to select certain data from the database and modify it in specific ways. With Mass Transaction Manager, all the SQL necessary to retrieve rows for processing is defined within each transaction. Users can then define additional selection criteria using the run control page, which, when run, will create a dynamic where clause based on the additional criteria. Asset Management is delivered with a full complement of transactions that serve the needs of most business applications.

Note: All of the former Mass Change transactions are available in Mass Transaction Manager so you can seamlessly transition to Mass Transaction Manager.

Some of the benefits of using Mass Transaction Manager include:

  • A user-centered design that is intuitive and easy to use, yet powerful.

  • An uncomplicated, streamlined process that makes it easy to capture user input and retrieve requisite rows for processing mass transactions.

    This simplified process also means you do not have to enter the same data twice.

  • Enhanced prompts with subordinate keys.

  • Ability to share common code, such as a rounding routine.

The steps required to set up and process mass transactions vary slightly depending on whether you are creating your own transactions from scratch, reconfiguring PeopleSoft-delivered transactions, or processing unaltered PeopleSoft-delivered transactions.

Creating Your Own Transactions and Processing the Data

To create your own transactions and process the data in Asset Management:

  1. Identify your requirements and the function the transaction must perform.

  2. Identify the tables or views that will be used to retrieve the rows for processing.

  3. Determine if user input is required.

    If user input is required, ensure the MTM_UEV_AM_SBR subrecord includes the fields you need. If the subrecord does not contain the fields you need, use Application Designer to add them, then build the tables that use the subrecord.

  4. In Application Designer, open the MTM_LIB_AM Application Engine.

  5. Use the Definition tab to enter information for the new transaction.

    It is useful to locate the last transaction you created and add the new transaction after it.

  6. Enter a numerical value for the Section field.

    Determine the number to use by adding 10 to the previous section value. For example, if the last transaction section value is 90000550, you would enter 90000560 for the new transaction.

    Note: Customer created transactions should be assigned section values from 90000000. This will ensure that these custom sections will not be overwritten by delivered transactions which are assigned sections from 00000010.

  7. Select the Public (Access) option.

  8. Create as many steps as you need for the transaction.

  9. If you allow the Set to Empty operator for user entered values, you must include the following PeopleCode:

    PeopleCode (ApplEng): MTM_LIB_AM.00000030GBLdefault  1900-01-01.Step05.OnExecute
    import AM_PSDMT:Enter:UserEnteredValues;
    Local AM_PSDMT:Enter:UserEnteredValues &uev = create AM_PSDMT:Enter:UserEnteredValues();;
    Local Record &aet;
    &aet = GetRecord(Record.MTM_LIB_AM_AET);
    MTM_LIB_AM_AET.PSDMT_UEV_LONG = &uev.GetUpdateStatement(MTMTOOL_AET.OPRID,
    MTMTOOL_AET.PS_OWNER, MTMTOOL_AET.PSDMUNIT_ID, MTMTOOL_AET.RUN_CNTL_ID, &aet);
  10. Enter the necessary SQL statement to retrieve the requisite rows for processing.

    Ensure that you include the %Binds that include the dynamic where clause and other common %Binds that are used in several transactions, such as transaction date, interface ID, null date, null date-time, and so forth.

  11. Save the new transaction.

  12. Using the PeopleSoft classic desktop browser UI, define individual transactions and behavior using the Mass Transaction Definition component.

    See Mass Transactions List PageTransaction Definition Page

  13. Define the list of available field filters associated with a transaction and configure filter behavior using the Mass Transaction Configuration page.

    See Mass Transaction Configuration Page

  14. (Optional) Choose the filter fields to display for a transaction using the Mass Transaction Criteria page.

    See Mass Transaction Criteria Page

  15. Set up security for a transaction by associating permission lists with the transaction.

    Note: This step can be performed any time after step 12.

    See Mass Transaction Security Page

  16. Using the Run Mass Transactions page run the Mass Transaction application engine (MTMTOOL) to generate the dynamic WHERE clause and process the transaction.

    See Run Mass Transactions Page

  17. Verify data in the loader tables.

    Note: This step is only necessary if you do not use the Auto Approval Status option on the Run Mass Transactions run control page and the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Pages Used to Verify Data in the Loader Tables

  18. Approve changes.

    Note: This step is only necessary if you do not use the Auto Approval Status option on the Run Mass Transactions run control page and the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Pages Used to Approve Changes

  19. Populate Asset Management tables with mass transaction data

    Note: This step is only necessary if the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Page Used to Populate Asset Management Tables with Mass Transaction Data

Configuring PeopleSoft-Delivered Transactions and Processing the Data

To configure PeopleSoft-delivered transactions and process the data in Asset Management:

  1. Using the PeopleSoft classic desktop browser UI, reconfigure transactions and behavior using the Mass Transaction Definition component.

    See Mass Transactions List PageTransaction Definition Page

  2. Reconfigure the list of available field filters associated with a transaction and modify filter behavior using the Mass Transaction Configuration page.

    See Mass Transaction Configuration Page

  3. (Optional) Choose the filter fields to display for a transaction using the Mass Transaction Criteria page.

    See Mass Transaction Criteria Page

  4. Configure security for a transaction by associating permission lists with the transaction.

    Note: This step can be performed any time after step one.

    See Mass Transaction Security Page

  5. Using the Run Mass Transactions page run the Mass Transaction application engine (MTMTOOL) to generate the dynamic WHERE clause and process the transaction.

    See Run Mass Transactions Page

  6. Verify data in the loader tables.

    Note: This step is only necessary if you do not use the Auto Approval Status option on the Run Mass Transactions run control page and the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Pages Used to Verify Data in the Loader Tables

  7. Approve changes.

    Note: This step is only necessary if you do not use the Auto Approval Status option on the Run Mass Transactions run control page and the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Pages Used to Approve Changes

  8. Populate Asset Management tables with mass transaction data

    Note: This step is only necessary if the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Page Used to Populate Asset Management Tables with Mass Transaction Data

Processing Unaltered PeopleSoft-Delivered Transactions

To process unaltered PeopleSoft-delivered transactions in Asset Management:

  1. Configure security for a transaction by associating permission lists with the transaction.

    See Mass Transaction Security Page

  2. Using the Run Mass Transactions page run the Mass Transaction application engine (MTMTOOL) to generate the dynamic WHERE clause and process the transaction.

    See Run Mass Transactions Page

  3. Verify data in the loader tables.

    Note: This step is only necessary if you do not use the Auto Approval Status option on the Run Mass Transactions run control page and the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Pages Used to Verify Data in the Loader Tables

  4. Approve changes.

    Note: This step is only necessary if you do not use the Auto Approval Status option on the Run Mass Transactions run control page and the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Pages Used to Approve Changes

  5. Populate Asset Management tables with mass transaction data

    Note: This step is only necessary if the transaction you processed loads the Asset Management loader tables (INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B).

    See Page Used to Populate Asset Management Tables with Mass Transaction Data

This table lists the mass transactions that are delivered with Asset Management:

Mass Transaction

Description

ADJ - Asset Cost Adjustment

Changes the cost of a set of assets as a percentage of the current cost.

ADJ - Asset Cost Adjustment 2

Changes the cost of a set of assets by a specified amount.

Archive Asset Depr Rpt Entries

Archives the Asset Depreciation Reporting Entries stored in PS_DEPR_RPT table inserting its rows into PS_DEPR_RPT_ARCH table.

Archive NBV Entries

Archives Asset Net Book Value Entries. It inserts rows into table PS_ASSET_NBV_ARCH, selecting from table PS_ASSET_NBV_TBL. PS_ASSET_NBV_TBL is the production asset net book value entry table. PS_ASSET_NBV_ARCH can be used to hold the old net book value entries.

Archive Asset Open Trans

Archives Asset Open Transaction entries (table PS_OPEN_TRANS). It inserts into the Open Trans Archive table (PS_OPEN_TRANS_ARCH), selecting from PS_OPEN_TRANS.

Archive Assets Acctng Entries (Archive Asset Acctng Entries)

Archives Asset Accouting Entries. It inserts rows into table PS_DIST_LN_ARCH, selecting from table PS_DIST_LN. PS_DIST_LN is the production asset accounting entry table. PS_DIST_LN_ARCH can be used to hold the old accounting entries.

ASD - Asset Deletion

Inserts asset records into the INTFC_FIN table for deletion.

AUP - Asset Update

This transaction is used to perform changes to the fields that are stored on the asset table (PS_ASSET). It inserts rows into the INTFC_PHY_A table that the Transaction Loader uses to update the asset table. Updates to the asset tag number (set equal to asset_id) and asset serial ID are some examples of how this mass transaction may be used. The physical inventory program uses this mass transaction to update several fields.

BA - Book Addition

This adds a new book to a business unit. This transaction deals with extracting the book and cost information from PeopleSoft Asset Management. Prerequisites include:

  • You must add the asset profiles for the new book before running this transaction.

  • The new book must be assigned to the business unit before running this transaction.

BC - Book Copy

This transaction is used to copy the book and cost information from one book to another. An example of when this may be used is when you want to do "what if" analysis. You may want to add a model book to a group of assets to do some reporting on. This transaction is used to copy the data you need from an existing book to your model book.

The book to which you are copying must exist for the business unit before processing this transaction.

BKD - Book Deletion

This transaction is used to delete assets from a book/business unit combination. It loads one row into the INTFC_FIN table with the business unit and book combination. The Transaction Loader (AMIF1000) deletes all rows for that BU/Book from tables BOOK, BOOK_TAX_CR, COST, DEPRECIATION, DIST_LN, OPEN_TRANS, and RETIREMENT.

The transaction does not alter the business unit setup (BU_BOOK_TBL) for the book. You may do this in the Establish Business Units pages.

BKS - Asset Book Change

Asset Book Change enables you to change the convention. For example, if you add over 40% of your assets in the final quarter, you must update the convention from Mid Year to Mid Quarter under certain US Regulations.

You can configure the Convention, Adjust Convention, Retire Convention, Retire Option, Depreciation Status, Depreciate When In Service, and the In-Service Date on the Transaction Definition.

Additional selection criteria are available for the Transaction Criteria, including asset identifiers such as Tag Number, Serial ID, and Description, as well as various Cost ChartFields.

BSD - Selective Book Delete

This transaction is used to selectively delete books for a group of assets. It differs from transaction BKD - Book Delete, in that BKD deletes book information for an ENTIRE Business Unit / Book combination. With this transaction, you may specify the Business Unit, Book, and range of Assets that you want to have deleted from the system.

CC - Capitalize Into Composite

This transaction is used to capitalize acquisition detail amounts into COMPOSITE assets.

This transaction sums the not yet capitalized acquisition detail line amounts for the assets associated with a composite asset. This amount is then spread as the cost to be added for an asset by chartfield, based on the cost percentage of each set of chartfields.

The cost for each set of chartfields is inserted into INTFC_FIN. INTFC_PHY_A rows are inserted for the composite member assets so that the acquisition detail lines can be updated as capitalized by the Transaction Loader.

CC - JPN Capitalize Composite

Capitalizes Japanese acquisition detail amounts into composite assets. This transaction sums the uncapitalized acquisition detail line amounts for the assets that are associated with a composite asset.

CR - Composite Retirement

This transaction is used to retire acquisition detail amounts from COMPOSITE assets.

The capitalized acquisition detail line amounts for the assets associated with a composite asset are summed and spread across the cost to be retired for an asset by chartfield set, based on the cost percentage of each set of chartfields. It inserts the retirement cost for each set of chartfields into INTFC_FIN.

CR - JPN Composite Retirement

This transaction is used to retire acquisition detail amounts from COMPOSITE assets.

The capitalized acquisition detail line amounts for the assets associated with a composite asset are summed. That amount is then spread across the cost to be retired for an asset by chartfield set, based on the cost percentage of each set of chartfields. It inserts the retirement cost for each set of chartfields into INTFC_FIN.

Delete Asset Accntg Entries (Delete Archived DIST_LN)

This transaction is used to delete entries from the assets accounting entry table (PS_DIST_LN) that have been archived.

Delete Asset Depr Rpt Entries

This transaction is used to delete entries from the Asset Depr Rpt tables PS_DEPR_RPT, PS_DEPR_RPT_PD_SUM, PS_DEPR_RPT_CF_SUM and PS_ARO_DEPR_RPT.

Delete Asset NBV Entries

This transaction is used to delete entries from the Asset Net Book Value table (PS_ASSET_NBV_TBL).

Delete Asset Open Trans

This transaction is used to delete Open Transaction entries. It should be used after they have been archived. It deletes data from the PS_OPEN_TRANS table.

EURO1 - InterUnit Trf − New Book

This transaction is used to perform mass interunit transfers to a new book. One example of when you'd use this is if you're changing from a 13 to a 12 period calendar.

InterUnit RET/Add w/Curr Conv

This mass transaction is used to perform financial asset transfers from one business unit to another, especially when the business units have different currencies and books.

Assets are retired in the "From" business unit and added in the "To" business unit. This mass transaction differs from the IUF mass transaction in that IUF does not perform currency conversions.

New asset IDs for the "To" business unit are assigned by the Transaction Loader, not by mass transaction. If you preview the load transactions prior to running the Transaction Loader, you will see that the "To" business unit assets have the "From" business unit asset IDs. Transaction Loader will assign new IDs when adding the assets to the "To" business unit.

Note: To perform currency conversion when moving assets from one business unit to another, the default profile option in the Transaction Loader is used. This means that profile IDs on the "To" business unit must exist for the assets that are being moved from the "From" business unit, and they must be the same profile IDs used in the "From" business unit. Books associated with the profile ID may be different.

Note: You cannot perform interunit transfers (retire/add) on group assets.

InterUnit TRF w/Currency Conv (InterUnit TRF w/Curr Conv)

This transaction is used to perform financial asset transfers from one business unit to another, especially when the business units have different currencies and books.

Assets are transferred out of the From business unit and transferred into the To business unit.

New asset IDs for the "To" business unit are assigned by the Transaction Loader, not by this transaction. If you preview the load transactions prior to running the Transaction Loader, you will see that the "To" business unit assets have the "From" business unit asset IDs. Transaction Loader will assign new IDs when adding the assets to the "To" business unit.

Note: To perform currency conversion when moving assets from one business unit to another, the default profile option in the Transaction Loader is used. This means that profile IDs on the "To" business unit must exist for the assets that are being moved from the "From" business unit, and they must be the same profile IDs used in the "From" business unit. Books associated with the profile ID may be different.

Note: You cannot perform interunit transfers (retire/add) on group assets.

IRC - Increase Rate Change

Use this transaction to change the Increase Rate.

IUF - IU Transfer to Another BU (IUF- IU Transfer to Foreign BU)

This transaction is used to perform financial asset transfers from one business unit to another. Assets are retired in the "From" business unit and added in the "To" business unit.

This transaction differs from the IUT-InterUnit Transfer one in that IUT does a transfer out of the "From" business unit and a transfer in to the "To" business unit.

New asset IDs for the "To" business unit are assigned by the Transaction Loader, not by this transaction. If you preview the load transactions prior to running the Transaction Loader, you will see that the "To" business unit assets have the "From" business unit asset IDs. Transaction Loader will assign new IDs when adding the assets to the "To" business unit.

Note: To perform currency conversion when moving assets from one business unit to another, the default profile option in the Transaction Loader is used. This means that profile IDs on the "To" business unit must exist for the assets that are being moved from the "From" business unit, and they must be the same profile IDs used in the "From" business unit. Books associated with the profile ID may be different.

Note: You cannot perform interunit transfers (retire/add) on group assets.

IUT - Inter-Unit Transfer

This transaction is used to perform mass inter-unit transfers. Two physical transactions and two financial transactions are created per asset, one for the 'From' business unit and one for the 'To' business unit. Acquisition detail records are also transferred.

This transaction differs from the IUF-InterUnit Transfer to Another Business Unit in that IUF does a retirement from the "From" business unit and an add in the "To" business unit; IUT (this transaction) does a transfer out of the "From" business unit and a transfer in to the "To" business unit.

Note: You cannot perform interunit transfers on group assets.

IUT - Non-Capital Assets

This transaction is used to perform mass inter-unit transfers of non-capital assets. Two physical transactions and two financial transactions are created per asset, one for the 'From' business unit and one for the 'To' business unit.

The transaction loader only processes physical transactions and financial transactions are used as a reference during processing.

JVA - Joint Venture BU Addition

This transaction is used to add a new business unit to a joint venture.

For example, you currently have two business units involved in a joint venture (A at 40% and B at 60%); you want to add a third business unit (C). The new allocation percentages for A, B, and C will be 40%, 30%, and 30% respectively. This transaction will be used to retire 50% of the cost from the assets in B and it will add to C using the proceeds and removal cost specified by the end user.

Using this transaction, the book table value defaults to the profile of the joint venture business unit. To have the book table values default from the new joint venture participant business unit profile, use the JVP - Joint Vent BU Add w/Prof transaction instead.

JVP - Joint Venture BU Add (w/Prof)

This transaction is used to add a new business unit to a joint venture.

For example, you currently have two business units involved in a joint venture (A at 40% and B at 60%); you want to add a third business unit (C). The new allocation percentages for A, B, and C will be 40%, 30%, and 30% respectively. This transaction will be used to retire 50% of the cost from the assets in B and it will add to C using the proceeds and removal cost specified by the end user.

Book table values that can be populated with defaults from the profile detail table are obtained from the profile ID for the new business unit.

JVR - Joint Venture BU Removal

Removes joint venture business units.

For example, you have three joint venture business units, A at 20%, B at 70%, and C at 10%. You want to remove C as a joint venture business unit and add the cost from C to business unit A. This transaction will retire the assets in C and add the cost to the assets in business unit A so that your final JV allocation is A at 30% and B at 70%.

JVT - JV Allocation Change

Transfers the allocation percentage for a joint venture from one business unit to another.

For example, you have two business units that make up a joint venture, A at 20% and B at 80%. You need to redistribute the allocation percentage so that it is 40% and 60% respectively. This transaction is used to retire 20% from business unit B and add that cost to business unit A.

PAD - Parent Asset Cost Adjust

Changes the cost of a parent asset and some or all of its children.

To have all children affected, leave the Child Asset ID criteria blank or apply some filter to affect only a subset.

Enter the new desired cost as in the Cost Adjust component.

The transaction creates the appropriate adjustments.

Parent Retire w/Pro/RC Absolut

This transaction is used to retire a parent asset and some or all of its children. The proceeds and removal cost for each asset are set equal to the proceeds and removal cost entered by the user.

For example, if the user enters $1000 and $2000 for proceeds and removal cost, and 10 assets are retired, the proceeds and removal cost for each asset are $1000 and $2000. Total proceeds = $10,000 and total removal cost = $20,000.

The transaction 'Retire Parents w/Pro/RC Distrib', distributes the proceeds and removal cost entered by the user proportionately by retirement amount; it is most likely the more common of the two to be used.

The business unit, book(s), and department(s) to use as selection criteria for the retirements must be specified. The proceeds and removal cost should also be specified. To specify one or more children, you may use the "In List" or "Between" logical operators; otherwise, if you leave the Child Asset ID(s) criteria field blank, all children of the specified parent will be affected.

Parent Retire w/Pro/RC Distrib

This transaction performs full asset retirements for a parent asset and some or all of its children (children that are financial assets).

To specify one or more children, you may use the "In List" or "Between" logical operators; otherwise, if you leave the Child Asset ID(s) criteria field blank, all children of the specified parent will be affected.

The proceeds and removal cost specified are distributed proportionately over each asset based on the cost of each asset retired over the total cost of all assets being retired.

For example, the user enters $1,000 and $2,000 for proceeds and removal cost, and 2 assets are retired. The cost of asset A is $1,000 and the cost of asset B is $9,000. The proceeds and removal cost for asset A are $100 and $200. The proceeds and removal cost for asset B are $900 and $1,800. Total proceeds = $1,000 and total removal cost = $2,000.

Partial Parent Asset Transfer

The Partial Parent Asset Transfer transaction is used to perform partial asset transfers for a specific parent and some or all of its children.

To specify one or more children, you may use the "In List" or "Between" logical operators; otherwise, if you leave the Child Asset ID(s) criteria field blank, all children of the specified parent will be affected.

Partial Retire Parent Proc Abs

This transaction is used to partially retire parent assets and some or all of their children (children that are financial assets).

To specify one or more children, you may use the "In List" or "Between" logical operators; otherwise, if you leave the Child Asset ID(s) criteria field blank, all children of the specified parent will be affected.

The percentage of the retirement is specified by the user. Also, the proceeds and removal cost for each asset are set equal to the proceeds and removal cost entered by the user.

For example, the user enters 0.4 as the percentage of the retirement, and $100 and $200 for proceeds and removal cost, and 2 assets are retired. The cost of asset A is $1,000 and the cost of asset B is $9,000. The amount retired for asset A is $400 and the proceeds and removal cost for asset A are $100 and $200. The amount retired for asset B is $3,600 and the proceeds and removal cost for asset B are $100 and $200. Total proceeds = $200 and total removal cost = $400.

Partial Retire Parent Proc Dis

Partial Retire Parent Proceeds Distributed is used to partially retire a parent asset and some or all of its children.

To specify one or more children, you may use the "In List" or "Between" logical operators; otherwise, if you leave the Child Asset ID(s) criteria field blank, all children of the specified parent will be affected.

The percentage of the retirement is specified by the user. The proceeds and removal cost for each asset are distributed proportionately over each asset based on the cost of each asset retired over the total cost of all assets being retired.

For example, the user enters 0.4 as the percentage of the retirement, $1,000 and $2,000 for proceeds and removal cost, and 2 assets are retired. The cost of asset A is $1,000 and the cost of asset B is $9,000. The amount retired for asset A is $400 and the proceeds and removal cost for asset A are $100 and $200. The amount retired for asset B is $3,600 and the proceeds and removal cost for asset B are $900 and $1,800. Total proceeds = $1,000 and total removal cost = $2,000.

Partial Retire Proceeds Absolu

This transaction is used to partially retire assets. The percentage of the retirement is specified by the user. The proceeds and removal cost for each asset are set equal to the proceeds and removal cost that are entered by the user.

For example, the user enters 0.4 as the percentage of the retirement, $100 and $200 for proceeds and removal cost, and 2 assets are retired. The cost of asset A is $1,000 and the cost of asset B is $9,000. The amount retired for asset A is $400 and the proceeds and removal cost for asset A are $100 and $200. The amount retired for asset B is $3,600 and the proceeds and removal cost for asset B are $100 and $200. Total proceeds = $200 and total removal cost = $400.

Partial Retire Proceeds Dist (Part. Retirement Proceeds Dist)

Partially retires assets. It is important that this transaction not be used to do full retirements—if it is, RETIRE_SW will be set incorrectly.

The business unit, book(s), department(s), and percentage of the retirement are specified by the user. The proceeds and removal cost for each asset are distributed proportionately over each asset based on the cost of each asset retired over the total cost of all assets being retired.

For example, the user enters 0.4 as the percentage of the retirement, $1,000 and $2,000 for proceeds and removal cost, and 2 assets are retired. The cost of asset A is $1,000 and the cost of asset B is $9,000. The amount retired for asset A is $400 and the proceeds and removal cost for asset A are $100 and $200. The amount retired for asset B is $3,600 and the proceeds and removal cost for asset B are $900 and $1,800. Total proceeds = $1,000 and total removal cost = $2,000.

PHY - Physical Asset Changes

Changes the physical side of assets. Two main examples include asset location changes and asset custodian changes.

This mass transaction results in INTFC_PHY_A entries being created that the transaction loader (AMIF1000) then inserts into the physical asset tables (i.e. the asset location and custodian tables).

PI Extract

Extracts asset data from multiple Asset Management tables into one physical inventory extract table.

This PI extract data may be reviewed before downloading to a bar code scanner file.

PI NCP Extract

Extracts asset data from multiple Asset Management tables pertaining to Non Capital assets into one physical inventory extract table.

This PI extract data may be reviewed before downloading to a bar code scanner file.

PI NCP Scan Scope

Physical Inventory Scan Scope mass transaction for Non Capital Assets.

PI OPL Extract

Extracts asset data from multiple Asset Management tables pertaining to Operating Lease assets into one physical inventory extract table.

This PI extract data may be reviewed before downloading to a bar code scanner file.

PI OPL Scan Scope

Physical Inventory Scan Scope mass transaction for Operating Lease Assets.

PI Scan Scope

Scans scope for physical inventory mass transaction.

PRC - Parent Recategorization

Moves the cost of an asset from one asset category to another for a parent and some or all of its children.

The parent ID, business unit, book, and category(s) to use as selection criteria must be specified as well as the new category value. If you leave the Child Asset ID(s) criteria field blank, All children of the parent will be affected; otherwise you may specify one or more children using the "In List" and "Between" logical operators.

The cost of all assets in the specified selection category is transferred to the target category.

PTF - Parent Asset Transfer

Moves the cost of a Parent Asset and some or all of its children out of the From Values and into the To Values.

The Cost Balance view gives the current cost at a chartfield level and enables you to change those chartfield values. If you do not change a value, it remains the same after the transfer.

To specify action upon one or more children in addition to the parent, you may use the "In List" or "Between" logical operators; otherwise if you leave the Child Asset ID(s) criteria field blank, all children of the specified parent are affected.

RCT − Recategorization

Moves the cost of an asset from one asset category to another.

You can configure the Asset Category and Cost Type on the Transaction Definition.

Additional selection criteria are available for the Transaction Criteria, including asset identifiers such as Tag Number, Serial ID, and Description, as well as various Cost ChartFields.

REI - Reinstate Assets (REI - Reinstatement)

Reinstates retired assets.

REP - Reinstate Parent Assets

Reinstates retired assets for a parent and some or all of its children.

The Parent ID, business unit, book(s), and department(s) to be used as selection criteria must be entered.

To specify one or more children, you may use the "In Subset" or "Between" logical operators; otherwise, if you leave the Child Asset ID(s) criteria field blank, all children of the specified parent will be affected.

Retire Non-Capital Assets

Retires non-capital assets. One physical transaction is created per asset.

Retire w/Proceeds/RC Absolute

Retires assets. The proceeds and removal cost for each asset are set equal to the proceeds and removal cost entered by the user.

For example, if the user enters $1000 and $2000 for proceeds and removal cost, and 10 assets are retired, the proceeds and removal cost for each asset are $1000 and $2000. Total proceeds = $10,000 and total removal cost = $20,000.

Transaction 'Retire w/Proceeds/RC Distrib' distributes the proceeds and removal cost entered by the user proportionately by retirement amount; it is most likely the more common of the two to be used.

Retire w/Proceeds/RC Distribut

Enables you to perform full asset retirement. The proceeds and removal cost for each asset are distributed proportionately over each asset, based on the cost of each asset divided by the total cost of all assets being retired.

For example, the user enters $1,000 and $2,000 for proceeds and removal cost, and 2 assets are retired. The cost of asset A is $1,000 and the cost of asset B is $9,000. The proceeds and removal cost for asset A are $100 and $200. The proceeds and removal cost for asset B are $900 and $1,800. Total proceeds = $1,000 and total removal cost = $2,000.

The transaction 'Retire w/Proceeds/RC Absolut' sets the proceeds and removal cost for each asset equal to the proceeds and removal cost entered by the user. This one, 'Retire w/Proceeds/RC Distribut', is most likely the more common of the two to be used.

TM - Acctg Entry Template Copy

Copies Accounting Entry (AE) templates from one SetID to another.

TM - Actg Ent Tmpl Copy w/in Set (TM - Acctg Entry Template Copy)

Copies Accounting Entry (AE) templates from one category to another within the same Set ID.

Defining AE templates can be tedious but if you have similar templates across some categories, this mass transaction can make the task easier.

This transaction differs from "TM - Acctg Entry Template Copy" in that this one copies from one category to another within the same Set ID. "TM - Acctg Entry Template Copy" is used to copy Accounting Entry templates from one Set ID to another Set ID.

TRF - Full Asset Transfer (TRF - Asset Transfer)

Moves the cost of an asset out of the From Values and into the To Values. The Cost Balance views give the current cost at a chartfield level and enable you to change those chartfield values.

If you do not change a value, it remains the same after the transfer.

TRF - Partial Asset Transfer

Performs partial asset transfers. A percentage of cost and quantity are transferred between the chartfields specified.

The main difference between PTR - Partial Asset Transfer and TRF - Asset Transfer is that the activity switch on a full transfer (TRF) is set to 1 on the from side. It is set to 0 for partial transfers.

Unload DIST_LN_ARCH to file (Archive DIST_LN_ARCH to file)

Archives the table PS_DIST_LN_ARCH to a sequential file.

The end user should enter the Archive ID and Archive Date as selection criteria.

Unload Open Trans to file (Unload Open Trans Archive)

Unloads entries from the Asset Open Transaction Archive table to a sequential file.

The end user should enter the Archive ID and Archive Date to be used as selection criteria.

Upload Asset Acctng Entries (Load Archived DIST_LN)

Loads the production asset accounting entry table (PS_DIST_LN) from the accounting entry archive table (PS_DIST_LN_ARCH).

Upload Asset Open Trans (Upload Archive Open Trans)

Uploads open transactions into the PS_OPEN_TRANS table from the PS_OPEN_TRANS_ARCH table.