Understanding Prompt Table Overrides

PeopleSoft enables you to create an override prompt table for any record field that already has a prompt table defined for it. At runtime, if an override prompt table is assigned to the record field, the override table determines the result set instead of the defined prompt table.

Using prompt table override, a user has the flexibility to make changes in the result set without any customization. This is possible by defining a new dynamic view with SQL for limiting the OPRIDs to return values based on a role. For example, if you want an OPRID to view a different result set for a record field that has a prompt table defined, then you can use a prompt table override to show different results for different users.

Similar functionality is already available in PeopleSoft, which is enabled by including derived record on the page and defining the prompt table for the record field as a dynamic prompt (%<DERIVED RECORD FIELD NAME>). Prompt table override is required only when the record fields are not delivered with a dynamic prompt capability.

See Setting Record Field Properties.

View filtering based on runtime OPRID is already available view, the %OPRCLAUSE Meta-SQL. Use of this Meta-SQL is restricted to dynamic views.

Note: All override prompt tables must be dynamic views and must use %OPRCLAUSE.

Note: Override prompt table settings will not be a formal part of the RDM managed object. However, whenever a record field is loaded from DB, this information is cached as part of the RDM managed object to improve the performance.

See %OPRCLAUSE.