Run Posting (GLPPOS), or other concurrent programs from the Command line

Run Posting (GLPPOS), or other concurrent programs from the Command line?

How to Run Posting (GLPPOS), or other concurrent programs from the Command line?

You can run any GL program from the command line. Follow these steps:

1) Verify that you run this at a time when there are no incompatible Programs running. To find the incompatible programs:

Responsibility = System Administrator

GUI Navigation = Concurrent/Program/Define

Query on GLPPOS in the Short Name field.

Click on the Incompatibilities button.

2) Change the profile “Concurrent Hold Request” to Yes.

Responsibility = System Administrator

GUI Navigation = Profile/System

Query on the profile option ‘Concurrent Hold Requests’.

Set it to Yes at the User level and Save.

3) Select a journal batch for posting. The request will be put on hold.

Responsibility = General Ledger Super User

GUI Navigation = Journals/Post

4) Go to the Concurrent Requests form and get the parameters for the Posting concurrent process.

The parameters for posting are:

set of books id

chart of accounts id


5) Run posting from the command line.

$GL_TOP/bin/GLPPOS <username/pwd> 0 Y <parameters> X 2> <File name>

Where:   <username/pwd> : apps username and password

<parameters>   : The parameters for the program, separated by spaces. For NULL parameters you need to specify closed double quotes (“”).

X              : Indicates that you want to run the program in debug mode. This can be any character and is optional.

2> <File name> : Use this to redirect standard errors and output to a file. File name is the output file name it will create. It will be created in your current directory, if a full path is not specified. This is optional

but recommended.


If you go to the concurrent requests form and see in the Parameters field: 1,101,2546, you would enter the following command at the Unix prompt:

$GL_TOP/bin/GLPPOS <username/pwd> 0 Y 1 101 2546 X 2> <myfile.txt>

6) Change the profile option ‘Concurrent Hold Requests’ back to its original setting. Be sure to run the program from a directory for which you have write Privileges. That is where the log and out files will be created.

Also make sure that you are in the proper application environment.

Here is an example of the command and the output you will see.

$>$GL_TOP/bin/GLPPOS apps/apps 0 Y 8 50128 84 2 2> njpost2.out

DEBUG: started in debug_mode……

$> ls

L54536.log   L54540.log   O54536.out   O54540.out   njpost.out   post.out

L54538.logL54542.log   O54538.out   O54542.out   njpost2.out  test

$> more njpost2.out

Log filename    : L54542.log

Report filename : O54542.out

glpmai() fnd_user_id is -1

glpmai() fnd_user_name is ANONYMOUS

glpmai() req_id is 0

glpmai() sob_id is 8


selected General Ledger programs can be run in debug

mode by setting the profile option ‘GL: Debug Mode’ to Yes at the

appropriate level.

These programs are:

– GLCRVL – Revaluation

– GLPPOS – Posting

– GLTTRN – Translation

– GLCCON – Consolidation Transfer

– GLAMAS – Run MassAllocations

Working with CONCSUB

The CONCSUB is a utility which allows you to submit a concurrent program to the concurrent manager from the operating system level without having to log on to Oracle Applications.
The CONCSUB executable is located at $FND_TOP/bin/CONCSUB.

The functionality of the CONCSUB can be categorized into the following

  • Submitting Concurrent Requests
  • Controlling Concurrent Managers

Submitting Concurrent Requests
You can use the CONCSUB to execute both seeded and custom programs in Oracle Applications. In case of custom programs they must first be registered in Oracle Applications before you can execute them with CONCSUB.

The following can be used in Oracle Applications to run the active users report from the command line without logging in the  applications

Submitted request 2866136 for CONCURRENT FND FNDSCURS PROGRAM_NAME=”Active Users”

The log and out file for this program is also created at the location defined by your $APPLCSF/$APPLLOG and $APPLCSF/$APPLOUT respectively.

The WAIT=Y/N is used to specify weather to wait for the first concurrent request to be completed before the second is submitted or not.

You can also use various printing parameters with the COCNCSUB to directly print the output of your concurrent request.

PRINTER=<printer name>
NUMBER_OF_COPIES=<number of reports to be printed>
PRINT_STYLE=<printer style to be used>    
LANGUAGE=<language to be used>

Also you could specify the start date and completion options along with CONCSUB by using the following parameters

START=<Requested Start Date>
REPEAT_DAYS=<Repeat Interval>
REPEAT_END=<Request Resubmission End Date>

Controlling Concurrent Managers
Apart from submitting concurrent request the CONCSUB can also be used to shutdown your concurrent managers


Sometimes the shutdown of the concurrent managers via the CONCSUB utility using the SHUTDOWN clause hangs and you may want to terminate your concurrent managers, in such a case you can use the ABORT clause with CONCSUB to do a force shutdown of your concurrent managers.


In this case a concurrent request to terminate the concurrent managers is fired with a -75 priority. In case of the shutdown  the priority is 0 and default priority is of a concurrent request 50, by assigning a -75 priority the CONCSUB ensures abort is executed before shutdown.

Needless to say that the shutdown would fail in case the SYSADMN user or the System Administrator responsibility is inactive.

However to start the concurrent managers the CONCSUB is not used instead the startmgr executable is used.(Though possible)
This is located at $FND_TOP/bin/startmgr.

$startmgr sysmgr=apps/apps@sam
Starting icm@sam Internal Concurrent Manager
Default printer is

By default if no manager name is specified the ICM or the Internal Concurrent Manager is started. You can also start a specific manager by using the mgrname clause

To use CONCSUB to start the concurrent managers the STARTUP clause is used

Submitted request 2849496 for CONCURRENT FND STARTUP