Performing Mass Changes in PeopleSoft Asset Management
Because of the extreme power Mass Change has to change large amounts of data in the database, we strongly recommend that you do not use Mass Change to write directly to the database. Rather, we suggest you write to intermediary tables, so that you can review the changes and approve, delete, or correct them. Then use another SQR to load the data into the database.
In the Asset Management implementation of Mass Change, we write to three load tables, INTFC_FIN, INTFC_PHY_A, and INTFC_PHY_B. INTFC_FIN holds financial information; INTFC_PHY_A and _B hold non-financial information.
Our AM Utilities window contains pages for reviewing, editing, and approving data in the load tables. This same window also displays pages for running the AM Transaction Loader SQR, which loads the data in the load tables into the Asset Management database.
This setup affords the user some protection against making massive erroneous changes to the database. As an example, we’ll look at how to perform mass changes in PeopleSoft Asset Management.
Processing mass changes in PeopleSoft Asset Management consists of a definition phase and a processing phase. First, you define the selection criteria and changes to be made to the selected data, then you run the SQRs that carry out the changes you defined.
In general, you’ll complete the following steps.
To run Mass Change in Asset Management:
Choose a mass change template and use it to create a mass change definition. Outline the criteria for selecting rows, and identify the columns and values to be changed.
Run the mass change SQR to select, change, and transfer the data to the load tables.
Preview the data for suitability (optional).
Run the Transaction Loader SQR to load the data from the load tables into your PeopleSoft Asset Management tables.