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

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

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.

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

etc.

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

Important things to focus as you are 0 to 2 Year experience in Oracle Applications Technical

Important things to focus as you are 0 to 2 Year experience in Oracle Applications Technical

1.Learn SQL – Writing Queries

2.Be Proficient in PL/SQL Programming

3.Learn more or more on System Admin and Application Developer module

4.Learn Unix – at least basics !

Difference Between Technical and Functional and Techno Functional

Difference Between Technical and Functional and Techno Functional

Oracle Technical – Improve Import/ Export performance?

EXPORT:     

 

Ø       Set the BUFFER parameter to a high value (e.g. 2M)

 

 

Ø       Set the RECORDLENGTH parameter to a high value (e.g. 64K)

Ø       Stop unnecessary applications to free-up resources for your job.

Ø       If you run multiple export sessions, ensure they write to different physical disks.

Ø       DO NOT exports to an NFS mount filesystem. It will take forever.

 

IMPORT:

Ø       Create an indexfile so that you can create indexes AFTER you have imported data. Do this by setting INDEXFILE to a filename and then import. No data will be imported but a file containing index definitions will be created. You must edit this file afterwards and supply the passwords for the schemas on all CONNECT statements.

Ø       Place the file to be imported on a separate physical disk from the oracle data files

Ø       Increase DB_CACHE_SIZE (DB_BLOCK_BUFFERS prior to 9i) considerably in the init$SID.ora file

Ø       Set the LOG_BUFFER to a big value and restart oracle.

Ø       Stop redo log archiving if it is running (ALTER DATABASE NOARCHIVELOG)

Ø       Create a BIG tablespace with a BIG rollback segment inside. Set all other rollback segments offline (except the SYSTEM rollback segment of course). The rollback segment must be as big as your biggest table (I think?)

Ø       Use COMMIT=N in the import parameter file if you can afford it

Ø       Use ANALYZE=N in the import parameter file to avoid time consuming ANALYZE statements

Ø       Remember to run the indexfile previously created

 Thanks – Shivmohan Purohit