Setting Up and Processing Mass Transactions

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