ksc_concsub

This command submits Oracle Application concurrent requests from the operating system command line. It is treated as a special command because the command engine must capture the concurrent request ID, which is an output of successful submission. To work properly, this command must be called within a ksc_connect - ksc_exit command block.

If ksc_concsub is used to submit a concurrent request to an Oracle Applications database other than where PPM Center is currently installed, the ORA_APPS_DB_LINK parameter must be added to the ksc_concsub command. Otherwise, the status of the concurrent request cannot be determined after submission.

The following syntax is supported:

ksc_concsub ORA_APPS_DB_LINK="DB_LINK" CONCSUB

DB_LINK corresponds to the database link from the PPM Center schema to the APPS schema of the database to which the concurrent request is submitted.

Example using ksc_concsub

ksc_concsub ORA_APPS_DB_LINK=[DEST_ENV.ORA_APPS_DB_LINK] 
CONCSUB [DEST_ENV.APP.DB_USERNAME]/[DEST_ENV.APP.DB_ 
PASSWORD]@[DEST_ENV.DB_CONNECT_STRING] FND 'Application 
Developer' SYSADMIN WAIT=N CONCURRENT FND FNDFMREG [DEST_ 
ENV.APP_CODE] [P.P_FILENAME]       

Note: The special command ksc_concsub is followed by the exact CONCSUB call that will be executed directly at the command line.

The complete syntax for Oracle's CONCSUB is shown below. Optional parameters are in square brackets.

CONCSUB

<ORACLE ID>

<Responsibility Application Short Name>

<Responsibility Name>

<User Name>

[WAIT=N]

CONCURRENT

<Concurrent Program Application Short Name>

<Concurrent Program Name>

[START=<Requested Start Date>]

[REPEAT_DAYS=<Repeat Interval>]

[REPEAT_END=<Request Resubmission End Date>]

<Concurrent Program Arguments...>

For additional information on using the CONCSUB command, see the Oracle documentation.

Note: It is not possible to retrieve the concurrent request logs from a ksc_concsub submission submitted against a remote database.