Changing Existing Analytic Type Definitions

This section discusses how to change:

  • Optimization application records.

  • Optimization transactions.

To change optimization application records in an analytic type definition:

  1. Shut down all the running optimization engines that use this analytic type definition.

  2. Shut down other optimization engines if record definitions are being shared by other analytic type definitions.

  3. Delete all existing analytic instances using the DeleteOptProbInst PeopleCode function.

    See DeleteOptProbInst.

  4. Empty the optimization application tables.

  5. Make record definition changes and build the records in PeopleSoft Application Designer.

    See Creating and Building Optimization Records.

  6. Open the analytic type in PeopleSoft Application Designer, insert any new records or make appropriate changes to reflect changed record definitions, and save the analytic type.

    Run SYSAUDIT with the optimization options selected.

    Skip the steps about inserting transactions.

  7. Change the OPI to reflect the changes to optimization application records.

    If the records do not match the plug-in, the program will fail.

  8. Call the InsertOptProbInst PeopleCode function to re-create analytic instances.

    See InsertOptProbInst.

To change optimization transactions in an analytic type definition:

  1. Shut down all the running optimization engines that use the analytic type definition.

  2. Open the analytic type definition in PeopleSoft Application Designer, insert any new transactions or make appropriate changes to existing ones, and save the analytic type.

    Skip the steps about inserting records.

  3. Change the OPI to reflect the changes to optimization transactions.

  4. Change optimization PeopleCode to reflect the changes (add, remove, and update parameters).