Request Set - Shared Parameter Behavior (Doc ID 2696643.1)

Last updated on APRIL 17, 2024

Applies to:

Symptoms

After patching (CPU & functional module patches) of the TEST environment the client noticed that shared parameters in a request set behave differently. In the non-upgraded environments the value of the parameter was shared between the concurrent requests in the request set while in the upgraded environment seems like the ID (from the value set) is transferred to the other requests in the set. This is causing problems during the validation of the parameters since the concurrent programs taking over the ID of the shared parameter instead of the value.

Example: request set 'OSCE Projects Billing TEST' consist of the following concurrent programs with the 'Award Number' as a shared parameter:
Concurrent program Value Set for Award Number
--------------------------------------------------------------------- --------------------------------------------
GMS: Generate Draft Invoices for a Single Award GMS_AWARD_ID_SET
GMS: Generate Draft Invoices for a Single Award GMS_AWARD_ID_SET
GMS: Interface Invoices to Receivables GMS_AW_PROJECT_NUMBER_AR (on the From Award Number and To Award Number fields)

The provided parameter is automatically taken over by the second concurrent program but on the third one I get an error :
ID 1422232 for the flexfield segment From Award Number does not exist in the value set GMS_AW_PROJECT_NUMBER_AR.

After the error was cleared the form allows the user to enter the proper award number for the From/To Award Number parameters.

This issue appears for other value sets which are used as shared parameter for concurrent programs.

Changes

 Patching (CPU & functional module patches).

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.