You can customize the Submit Request window in several ways.

Rename the Window Title

You can change the title to reflect the requests available in the window. See: Customizing the Submit Requests Window using Codes.

Restrict Requests Available to A Request Group

You can restrict the reports and programs available to those in a specified request group. See: Customizing the Submit Requests Window using Codes.

Restrict Requests to a Single Request

You can call Submit Requests form for a single request submission by passing the program/set name as parameters

The parameters window pops up on navigation to the form when called with a program/report_set name. The form exits after the user acknowledges the displayed request ID for the submitted request.

Restrict Requests To A List of Requests

You can call Submit Requests form to submit one or more requests for a single program/set by passing the program/set name as parameters

The parameters window pops up on navigation to the form and the user can submit one or more requests for the program that was passed as a parameter. Requests for other programs cannnot be submitted in this case.

Pass Parameters Used in Value Set Parameters

You can pass additional parameters to the Submit Requests form that can be referenced in the value sets to validate the request parameters.

Pass Manufacturing "ORG" Parameters

You can pass 5 ORG related parameters and refer to them in the value set. Alternatively, you can bring up a ORG LOV on navigation to the Submit Requests form that populates the ORG parameters which can be referenced in the value sets.

Complete List of All Submit Request Paramters

Below is the comprehensive list of parameters supported by the "Run Requests"/SRS form and additional information about their usage.

• REQUEST_GROUP_CODE

• REQUEST_GROUP_APPL_SHORT_NAME (used with REQUEST_GROUP_CODE)

• CONCURRENT_PROGRAM_NAME

• PROGRAM_APPL_SHORT_NAME (used with CONCURRENT_PROGRAM_NAME)

• REQUEST_SET_NAME

• SET_APPL_SHORT_NAME (used with REQUEST_SET_NAME)

• SUBMIT_ONCE (default 'N').

  SUBMIT_ONCE can be set to either Y or N ( N is the default).

  SUBMIT_ONCE is used in conjunction with CONCURRENT_PROGRAM_NAME or REQUEST_SET_NAME.

  If SUBMIT_ONCE is set to Y, then the form will exit after the Submit button is clicked.

• TITLE

• LOOKUP (default 'N')

• USE_ORG, ORG_ID, ORG_NAME, ORG_CODE, CHART_OF_ACCOUNTS_ID (five parameters)

  If USE_ORG is set to 'Y' (default is 'N') then the Submit Requests form checks to see if the other ORG parameters are set. If the parameters are not set, then it attempts to populate the parameters from the globals (GLOBAL.FND_ORG_ID, GLOBAL.FND_ORG_NAME, etc.). If the globals have not yet been set, the an ORG LOV shows, and both the parameters and the globals are populated from the LOV.

  Values sets should always reference the parameters, not the globals.

• CHAR1, CHAR2, CHAR3, CHAR4, CHAR5

• DATE1, DATE2, DATE3, DATE4, DATE5

• NUMBER1, NUMBER2, NUMBER3, NUMBER4, NUMBER5

  In your value sets, refer to these parameters as:

  :PARAMETER.CHAR1, :PARAMETER.DATE1, :PARAMETER.NUMBER1  etc.