What is Page and Field Configurator Framework in Enterprise Component?

In the past, programmers have to customize pages and records to meet the business specific requirement to hide the field, make field display only, or make fields required. Enterprise component has delivered a flexible framework which can be utilized to achieve the above changes to meet business specific requirements without doing customization. Since it is configuration, making and tracking such changes is not treated as customization and thus, help bring down upgrade costs and efforts.

What are common applications?

PeopleSoft Page and Field Configurator feature enables the users to configure certain properties of pages and fields of classic pages based on business requirements. Page and Field Configurator allows the users to define multiple configuration for a component based on different user roles or user list. User can define multiple criteria based on the component fields and selectively apply the configuration at run time if the criteria is satisfied based on the run time values.

Using this feature, a user can hide a field/page, change label of a field, add default value to a field, make the field/page read only, or mark the field as mandatory without having to customize delivered application code or pages. Some common example are. . . making Distribution Type field mandatory on transaction page components, disabling payment terms on PO header vendor details page, validation of PO number based on PO classification on voucher component in Payables.

EC Page and Field Configurator Framework

Impact:

Use PeopleSoft delivered EC Page and Field Configurator Framework to Configure business specific rules/requirement instead of customizing Pages and records.

This is treated as configuration reducing regression testing and retrofit effort impact on future PUM updates.

Modules Impacted:

AP/PO/ePro/Inventory

Background:

Currently PeopleTools objects (PeopleCode/Records/Pages, etc.) are modified to meet the business requirements that cannot be met with delivered PeopleSoft functionality. The customizations that are in place need to be evaluated and retrofitted with future PUM updates. This makes PUM application lengthy, costly and effort intensive.

Current Scenario:

Manually compare and retrofit customization code with every PUM update.

Solution:

PeopleSoft Enterprise Component has delivered Page and Field Configurator functionality. This functionality can be utilized to move effort intensive customization including PeopleCode, Pages, and Record Field Property, etc. as configuration. These configurations can be moved to new PUM without retrofit effort.

Considerations / Impact:

This change will affect multiple modules, where delivered PeopleCode objects are modified/customized to meet the business needs that could not have been met with delivered product functionality.

Pros

  1. Ease in preforming PUM Image updates
  2. Changes can be ported to any database using Application Data Set (ADS)
  3. Reduced manual effort for retrofitting customizations during PUM Image application update

Cons

  1. Reduced manual effort for retrofitting customizations during PUM Image application update
  2. Periodic review required while performing PUM updates.

Use Case No. 1: IN85- QQ_SC_DISTRIB_TYPE_REQUIRED

Actor: Inventory Users

Process Flow / Steps:

  1. Input Inventory Business Unit and Request Type (Internal Issue) and click on Add.
  2. Add multiple
  3. Provide Item, Qty (10), Storage location, UOM information, and other applicable information (Lot ID, Serial ID, etc.) and save.
  4. User shall not be able to save without Dept. ID and Distrib Type information.

Technical Mapping Changes

Move the customization code currently on the Express issue record Save Edit that needs to be retrofitted with every PUM update, as configuration using Page and Field Configurator Functionality.

Currently customized and/or custom code on to support this business requirement is:

MSR_HDR_INV.DISTRIB_TYPE.SaveEdit

Retrofitting Code using Page and Field Configurator Framework

Define Page and Field Configuration for component EXPRESS_ISSUE_INV. Make DISTRIB_TYPE as required field.

Use Case No. 2: AP028- CR(s): 67345

Actor: AP Users

Process Flow / Steps:

  1. Add/Update Voucher
  2. Select Non-PO classification category as service/repair
  3. Do not enter Non-PO Contract information.
  4. Enter other relevant information
  5. Attempt to save the voucher transaction by clicking on Save. User shall not be able to save voucher

Technical Mapping

Move the customization code currently on the Express Issue Record Save Edit that needs to be retrofitted with every PUM update, as configuration using Page and Field Configurator Functionality.

Currently customized and/or custom code on event to support this business requirement is:

VOUCHER.VOUCHER.SaveEdit

Code retrofitting using Page and Field Configurator Framework

Define Page and field Configuration for component VCHR_EXPRESS. Set the criteria for Seq 1 using Non-PO classification value equals to “Service/Repair”. Set the PO Contract field value as Required.