[TITLE]

2010 1 6

You can run any GL program from the command line, though this would normally only be done if requested by Support or Development. 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
Consultant | Chelsea Wang

[TITLE]
chart of accounts id posting_run_id 5) Run posting from the command line.

2010 1 6

$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.

Example: 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. FIN107>$GL_TOP/bin/GLPPOS apps/apps 0 Y 8 50128 84 2 2> njpost2.out DEBUG: started in debug_mode ......

Consultant | Chelsea Wang

[TITLE]

2010 1 6

FIN107> ls L54536.log L54540.log O54536.out O54540.out njpost.out post.out L54538.logL54542.log O54538.out O54542.out njpost2.out test FIN107> 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 etc. NOTE: In Release 11.5, 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 See Note 232669.1: 'How To Run Selected General Ledger Programs In Debug Mode in R11.5' for more information.

Additional Search Words ----------------------Posting, unix, debug mode, GLPPOS, command line, General Ledger, GL POST

Cd $GL_TOP GLPPOS APPS/APPS 0 Y 2021 1000 50408 1561 X 2> POSTING.TXT

Consultant | Chelsea Wang

[TITLE]

2010 1 6

Log filename : L451794.log Report filename : O451794.out

Consultant | Chelsea Wang