In this article, let’s see how to submit a concurrent program from UNIX operating system using CONCSUB utility.


CONCSUB is UNIX operating system command prompt utility in Oracle Apps to submit concurrent program.


CONCSUB <APPS username>/<APPS password> \
<responsibility application short name> \
<responsibility name> \
<username> \
[WAIT=N|Y|<n seconds>] \
<program application short name> \
<program name> \
[PROGRAM_NAME=<description>] \
LANGUAGE - R12 onwards only \
TERRITORY - R12 onwards only
[ORG_ID=<#>] - R12 onwards only
[REPEAT_TIME=<resubmission time>] \
[REPEAT_INTERVAL= <number>] \
[REPEAT_INTERVAL_UNIT=< resubmission unit>] \
[REPEAT_INTERVAL_TYPE=< resubmission type>] \
[REPEAT_END=<resubmission end date and time>] \
[START=<date>] \
[IMPLICIT=< type of concurrent request> \
[<parameter 1> ... <parameter n>]


  • <username/password> Required. The ORACLE username and password (apps user)
  • <responsibility application short name> Required. The application short name of the responsibility
  • <responsibility name> Required. The name of the responsibility.
  • <username> Required. The uppercase username of the application user
  • <WAIT> Optional. A flag to indicate whether to wait for the submitted request to complete.

WAIT=Null or N – CONCSUB return to the operating system prompt without waiting for the request to complete

WAIT=Y – CONCSUB check the request status every 60 seconds and returns to the operating system prompt when the request is completed.

WAIT=30, for CONCSUB to check for request completion every <number> 30 seconds.

Attention: Using WAIT=Y or WAIT=<number> requires that the request completes before CONCSUB returns to the operating system. If the concurrent manager is down, the CONCSUB process waits indefinitely until the concurrent manager is started and the request completes.

  • <CONCURRENT> Required. A flag that separates the program specific parameters from the operating system parameters.
  • <program application short name> Required. The application short name of the concurrent program.
  • <program name> Required. A Short name of the concurrent program in upper case.
  • <PROGRAM_NAME> Optional. A descriptive name for your program.
  • <ORG_ID> Optional. Introduced in R12, set to org id required for the report to be run with.
  • <REPEAT TIME> Optional. The time of day to resubmit the request. The format for the time is HH24:MI or HH24:MI:SS.

For example, REPEAT_TIME=14:30 resubmits the request daily at 2:30 p.m.

Attention: Do not use REPEAT_TIME with other resubmission parameters except for the optional parameters REPEAT_END and START.

  • <REPEAT_INTERVAL> Optional. The interval between resubmission (a positive integer or real number). Use this parameter along with REPEAT_INTERVAL_UNIT to specify the time between resubmissions.
  • <REPEAT_INTERVAL_UNIT> Optional. The unit of time used for the interval between resubmissions. The available units are MINUTES, HOURS, DAYS or MONTHS. Use this parameter along with REPEAT_INTERVAL to specify the time between resubmissions.

For example, setting REPEAT_INTERVAL=12 and REPEAT_INTERVAL_UNIT=HOURS resubmits the request every twelve hours. The default value is DAYS. Attention: Do not use REPEAT_INTERVAL and REPEAT_INTERVAL_UNIT with REPEAT_TIME.

  • <REPEAT_INTERVAL_TYPE> Optional. Whether to time the resubmission interval from the requested start time of the request or from its completion. Set this parameter either to START or END. The default value is START. Attention: Use REPEAT_INTERVAL_TYPE only if one uses REPEAT_INTERVAL.
  • <REPEAT_END> Optional. The date and time to stop resubmitting the concurrent request. Use one of the following for the format of the end date: DDMONRR HH24:MI:SS (as in 07“APR02 18:32:05€™) or DDMONRRRR HH24:MI:SS (as in 07€“APR2002 18:32:05€™) Note that because this date format includes a space, one must enclose the date in double quotation marks and single quotation marks. One can also specify just the date: DDMONRR or DDMONRRRR
  • <LANGUAGE> Optional. The NLS language for the request. (LANGUAGE=SIMPLIFIED CHINESE
  • <TERRITORY> Optional. The NLS territory for the request. (TERRITORY=CHINA \)
  • <START> Optional. A start date and time for the program in this format: DDMONRR HH24:MI:SS (as in 07€“APR02 18:32:05€™) Because this date format includes a space, one must enclose the date in double quotation marks and single quotation marks. If one does not specify a start time, the program submits immediately and is processed by the next available concurrent manager. The default value is the current time.
  • <IMPLICIT> Optional. Whether to show this concurrent request on the View Requests form. Specify NO, YES, ERROR or WARNING. The value IMPLICIT=NO allows the request to appear on the View Request form. The default value is NO. The value IMPLICIT=YES means that only the System Administrators privileged View Concurrent Requests form displays this request. Use this value if the request is not interesting to the user. Specify IMPLICIT=ERROR or IMPLICIT=WARNING, respectively, if one wants the request to appear only if it fails or completes with warnings.
  • <REPEAT_DAYS> Optional. The number of days after which to repeat the concurrent request, calculated from the last requested start date. The number can be a positive integer or real number. For example, REPEAT_DAYS=1.5 resubmits the request every 36 hours.


Do not use REPEAT_DAYS with other resubmission parameters except for the optional parameters REPEAT_END and START. Suggestion: REPEAT_DAYS will become obsolete in a future release. One may, therefore, want to use REPEAT_INTERVAL, REPEAT_INTERVAL_TYPE, and REPEAT_INTERVAL_UNIT instead of REPEAT_DAYS. … Optional. The program specific parameters. If a parameter includes spaces, enclose that parameter in double quotes, then in single quotes. If a parameter contains a double quotation mark as part of the argument, precede that mark with a backslash [\]. Please note that the program-specific parameters must be explicitly passed to CONCSUB, any default values that may be used when the program is submitted via the normal screens (ie Standard Report Submission or SRS) will not be used by CONCSUB.

How to submit concurrent program using CONCSUB utility
Tagged on:


I am Oracle Certified Associate(OCA) working in Oracle Domain since last 15 Years. Started this blog to share knowledge about different Technologies mostly focussing on Oracle.

3 thoughts on “How to submit concurrent program using CONCSUB utility

  • December 4, 2017 at 11:05 am

    Thanks for Article. But I would suggest you to provide some working example of concsub.

  • December 14, 2017 at 10:27 am

    An outstanding share! I have just forwarded this to a friend who was doing a little homework on this.

  • December 15, 2017 at 3:46 am

    I would suggest adding some good working example, rather than copying the syntax and description. Sorry to say, but this is available on Oracle site as well.

Comments are closed.