Enter and update the program parameters that you wish to pass to the program executable. Program parameters defined here should match the variables in your execution file.
Enter the parameter which will hold the value of the conflict domain of the program. For information on conflict domain parameters, see Concurrent Conflict Domains.
Enter the parameter which will hold the value of the conflict domain of the program.
This field is for HRMS security only. See: Customizing, Reporting, and System Administration in Oracle HRMS.
Choose the sequence numbers that specify the order in which your program receives parameter values from the concurrent manager.
Disabled parameters do not display at request submission time and are not passed to your execution file.
You specify information about your parameter almost exactly as you define a flexfield segment.
Enter the name of the value set you want your parameter to use for validation. You can only select from independent, table, and non-validated value sets.
The maximum size of your value set is 240 characters.
Attention: If you are using a value set of dates, this value set should have a format type of either Standard Date or Standard DateTime if you are using the Multilingual Request feature.
If you want to set a default value for this parameter, identify the type of value you need.
Valid types include:
| Constant | The default value can be any literal value. |
| Profile | The default value is the current value in the user profile option defined in the Default Value field. Use the profile option name, not the end-user name. You do not need to include $PROFILE$. |
| SQL Statement | The default value is determined by the SQL statement you defined in the Default Value field. |
| Segment | The default value is the value entered in a prior segment of the same parameter window. |
You can enter a default value for the parameter. This default value for your parameter automatically appears when you enter your parameter window. You determine whether the default value is a constant or a context-dependent value by choosing the default type.
Your default value should be a valid value for your value set. Otherwise you see an error message when you enter your parameter window on the Run Request window and your default value does not appear.
Valid values for each default type include:
| Constant | Enter any literal value for the default value. |
| Profile | The default value is the current value of the user profile option you specify here. Enter the profile option name, not the end-user name. |
| Segment | The default value is the value entered in a prior segment of the same flexfield window. Enter the name of the segment whose value you want to copy. |
| SQL Statement | The default value is determined by the SQL statement you enter here. Your SQL statement must return exactly one row and one column in all cases. |
If the program executable file requires an argument, you should require it for your concurrent program.
If the value set for this parameter does not allow security rules, then this field is display only. Otherwise you can elect to apply any security rules defined for this value set to affect your parameter list.
Choose either Low or High if you want to validate your parameter value against the value of another parameter in this structure. Parameters with a range of Low must appear before parameters with a range of High (the low parameter must have a lower number than the high parameter). For example, if you plan two parameters named "Start Date" and "End Date," you may want to force users to enter an end date later than the start date. You could assign "Start Date" a range of Low and "End Date" a range of High. In this example, the parameter you name "Start Date" must appear before the parameter you name "End Date."
If you choose Low for one parameter, you must also choose High for another parameter in that structure (and vice versa). Otherwise you cannot commit your changes.
Indicate whether to display this parameter in the Parameters window when a user submits a request to run the program from the Submit Requests window.
You should provide a default type and value for any non-displayed parameter.
Enter the field length in characters for this parameter. The user sees and fills in the field in the Parameters window of the Submit Requests window.
You should ensure that the total of the value set maximum sizes (not the display sizes) for all of your parameters, plus the number of separators you need (number of parameters minus one), does not add up to more than 240. If your program values' concatenated length exceeds 240, you may experience truncation of your data in some forms.
Enter the display length in characters for the parameter value description. Your window may show fewer characters of your description than you specify here if there is not enough room (determined by the sum of your longest prompt plus your display size for this parameter plus seven). However, your window does not display more characters of the description than you specify here.
A user sees the prompt instead of the parameter name in the Parameters window of the Submit Requests window.
Enter the display length in characters for the parameter value description. The user sees the parameter value in the Parameter Description field of the Submit Requests and View Requests forms. The Parameter Description field concatenates all the parameter values for the concurrent program.
Suggestion: We recommend that you set the Concatenated Description Size for each of your parameters so that the total Concatenated Description Size for your program is 80 or less, since most video screens are 80 characters wide.
For a parameter in an Oracle Reports program, the keyword or parameter appears here. The value is case insensitive. For other types of programs, you can skip this field.