Setting Up LCM Insights

This topic discusses:

  • Step1: Creating and consolidating metadata for setting up LCM Insights

  • Step2: Preprocessing metadata for setting up LCM Insights

To set up the LCM Insights, first use Change Assistant to create and consolidate metadata and load the resulting metadata in a database defined as Insights database.

To create and consolidate metadata:

  1. In Change Assistant, select Tools, Populate Customization Insights.

    This example shows the fields to define the settings for populating the Insights.

     Defining the settings to populate the Insights

    Field

    Description

    PUM Source Database

    This is auto-populated. Ensure to define PUM Source through Tools,Options, PUM Source tab so that the PUM Source database name is auto-populated on this page.

    Customization Source Database

    Select the Customization source database where the customizations reside.

    Project Name

    Enter a project name.

    This project will be used to collect and compare customizations identified in the Customization source database.

    Insights Database

    Select the Insights database where you intend to view and manage the LCM Insights.

    Note: As a best practice, it is recommended to use the Production database as the Insights database.

  2. Click Next. The Validation page opens where validations are done. Validations include primary checks such as verifying connection to PUM Source, verifying connection to Insights database and so on.

  3. Click Next. The page will now run a sequence of steps to create and consolidate the customization and PUM metadata needed for the LCM Insights.

This example shows the steps to create and consolidate various metadata needed for the LCM Insights.

 Steps to create and consolidate metadata

Step

Description

Creating Consolidated LCM Insights Project

This step analyzes the Customization source database, and creates a consolidated LCM Insights project with customized objects.

The project name is entered on the Settings- Populate Customization Insights page.

The consolidation of the customized objects is needed in order to complete the subsequent compare step in the process.

Exporting Consolidated LCM Insights Project to File

This step copies the consolidated LCM Insights project to a file.

Comparing the Consolidated LCM Insights Project to PUM Source database

This step runs the Compare From File process. The compare is between the Consolidated LCM Insights project file, which contains the customized objects, and the PUM source database. It results in the project definition and compare result being stored in the PUM source database.

The compare process is used to determine the true nature of the objects identified as customized in the user environment by comparing their status with PeopleSoft-delivered Managed Objects (MO).

The result of this process is then used to categorize or split the customizations in the subsequent steps.

Running the Customization Project Split

This step splits the Consolidated LCM Insights project into three projects based on the different object statuses as identified in the previous compare step.

Definition of each customization project:

  • Customization- Customer modified a PeopleSoft-delivered object.

    The object compare status will appear as CHANGED/UNCHANGED in the PUM source.

  • Custom- Customer has created a net new object.

    The object compare status will appear as ABSENT in the PUM source.

  • False Positive customization- Customer has not modified a PeopleSoft-delivered object. However, it appears as customized due to unintended saves, troubleshooting edits and so on.

    The object compare status will appear as SAME in the PUM source.

Exporting the Customization Project

This step exports only the Customization project definition to a file from the PUM source database.

Exporting the Custom Customization Project

This step exports only the Custom project definition to a file from the PUM source database.

Exporting the False Positive Customization Project

This step exports only the False Positive customization project definition to a file from the PUM source database.

Uploading Customization metadata to Insights database

This step uploads the Customization metadata to the Insights database from the file.

Uploading Custom Customization metadata to Insights database

This step uploads the Custom metadata to the Insights database from the file.

Uploading False Positive Customization metadata to Insights database

This step uploads the False Positive customization metadata to the Insights database from the file.

Exporting PUM Metadata to File

Exports the PUM metadata from the PUM source database to a file.

This step exports only a subset of the PUM metadata that is required to set up LCM Insights.

Importing PUM metadata from file into Insights database

This step imports the PUM metadata from file to the Insights database.

PUM metadata is used by the LCM Insights to provide details on how the PeopleSoft delivered maintenance (objects) impact your customizations.

Run Customization Counts Process

This step creates object count as part of the preprocessing activity to set up LCM Insights.

The setup is completed by using the PreProcessing Data for Maintenance Insights page in PIA on the Insights database. Use this page to process the incremental updates to customization, usage and PUM metadata.

Navigation

PeopleTools > Lifecycle Tools > Setup LCM Insights

Preprocessing Customization Metadata

The Customization page updates the status of previously identified objects (those identified during the comparison process in Change Assistant) based on their status in the Insights database. If a previously identified custom object is replaced with a PeopleSoft-delivered object, the Insights database reflects a decrease in the count of custom objects by one.

Note that it does not identify net new custom objects.

Currently, the only way to add net new custom objects is to complete the Change Assistant process documented in the preceding section or to manually edit the underlying project definitions and then run this process to update or re-sync.

This example illustrates the fields and controls on the PreProcessing Data for Maintenance Insights- Customization page. You can find definitions for the fields and controls later on this page.

Loading Customization Metadata for LCM Insights

Select the Load Customization Data option to enable users to update customization metadata if there are incremental customizations after the initial load by Change Assistant. The Insights database will reflect the updated customizations.

You can set a schedule with a recurrence option.

Click Run Now to run this job. The status, such as, Success or Failed, will be displayed on the History grid.

Preprocessing Usage Metadata

Use the Usage page to process the usage metadata.

This example illustrates the fields and controls on the PreProcessing Data for Maintenance Insights- Usage page. You can find definitions for the fields and controls later on this page.

Loading Usage Metadata for LCM Insights

Select Load Usage Data option to enable usage data processing.

It is recommended to collect usage data in the Production environment. An alternative option is available for customers who are unable to do so. In such cases, usage data can be retrieved and used from an alternate environment or remote database.

To retrieve this data, select the Load from Remote DB option.

Before that, configure the remote database using the Define Usage Source link.

On the Define Usage Source page you can enter the remote database details and the data gets retrieved with PeopleSoft Integration Broker.

Preprocessing PUM Metadata

To load PUM metadata, use the PUM page.

This example illustrates the fields and controls on the PreProcessing Data for Maintenance Insights- PUM page. You can find definitions for the fields and controls later on this page.

 Processing PUM Metadata for LCM Insights

Select Load PUM Data option to enable PUM metadata processing.

This option updates the PUM metadata in the Insights database to reflect changes to the PUM source that happened after the initial load in Change Assistant. The changes to the PUM source can happen either through a PRP apply or replacement of the existing PUM source with a new one.

This option removes the need to complete all the processing steps in Change Assistant to update the PUM metadata in the Insights database.

Click Define PUM Source link to configure the PUM source database.