Hi ,

My requirement is to email the log file after a concurrent request is complete.
I am attempting a popular workaround I have heard of - a custom printer driver
that will use the ‘mail’ OS command instead of ‘ls’

The arguments columns in the driver setup looks like this -

mail emailID.. < $APPLCSF/log/hrmsdev1_hrmst/l`echo $PROFILES$.CONC_REQUEST_ID`.req

where my logfile name is like l23456.req

Unfortunately iam missing a finer unix syntax and the OS is unable to derive and substitute the
file name and concatenate the ‘l’ and ‘.req’ . The $APPLCSF environment variable is derived properly.

Please help if you can… thanks.

Madhu

for arugments for driver use this one

uuencode $PROFILES$.FILENAME $PROFILES$.FILENAME_out|mailx -s $ $PROFILES$.FILENAME emailid

this will work , just try out

Hello Braj,

Many thanks for your time.
My requirement is to mail the log file and not the outfile. The $PROFILES$FILENAME would have the
outfile name iam sure.

Any further ideas ?

Regards,

Madhu

if you want just log file then use following

mailx -s “log of Request id :$PROFILES$.CONC_REQUEST_ID” valid_mailid <$APPLCSF/$APPLLOG/l$PROFILES$.CONC_REQUEST_ID.req

I have just tested it.

Hello Braj,

Many thanks for your solutuion. It indeed worked.
I realised that I have overlooked something fundamental in my solution. The log file will not be fully made until the OS command returns the status.
Hence, the log file that is sent in this mail will not be complete and will not have the footer and the status of the concurrent program.
for example - during my previous attempts, as a result of my wrong syntax for the mail command, the file name derivation was not happening and
the command errored out. The same error used reflect in the log file, which means that the log file is still work in progress until the ‘ls’ or ‘mail’ is complete.

Now, I plan to write a wrapper PLSQL script and use DBMS_PIPE package to call OS command in PLSQL. the wrapper program will call my interface program using FND_REQUST.SUBMIT_REQUEST () , and use the concurrent_request_id returned by the SUBMIT_REQUEST and locate the appropriate log file and
mail it using the command you helped me with ! ( If this solution fails, I have to only use UTL_SMTP - which is rather much more elaborate than the others)

Thanks once again for you time !  Please share with me any further inputs / comments if you might have.

cheers!

Madhu

Hello Braj & Anyone else following this thread,

I thought of another simple solution for my problem, please guide me further if you can -

Like I had discovered during my previous post - the LOG file is a work-in-progress at the time when the print ( or mailx) command is executed from the driver settings. This I figured is because - the Oracle Apps process waits for the response back from the command executed from the driver settings, and updates
the log file with the status that is received back from the call to the print ( or mailx) command.

Can I workaround this by spawning off another shell session by using / enclosing my mailx command in brackets ( ) and also using a WAIT of 20 seconds.. The Oracle Apps process would get a ‘SUCCESS’ response back once the second shell is spawned successfully and the log file will be complete. At the same time the
second shell would pick be able to pick the completed log file and mailx it.

Is this solution possible at all or am I just writing science fiction here

Thanks for your time and any help !

Madhu

I will propose simplest solution for you.

just write one shell script named it LOGMAIL
-------------------------------------

now put this file any where for my case , i will use $FND_TOP/bin
so file absolute path is
$FND_TOP/bin/LOGMAIL

Now define the initialization string for printer as

This is working perfectly well, you can also fine tune this script for your own requirement.

change the 5 th line of code to
WAIT=$2

or whole post again
---------------------------

I will propose simplest solution for you.

just write one shell script named it LOGMAIL
-------------------------------------

now put this file any where for my case , i will use $FND_TOP/bin
so file absolute path is
$FND_TOP/bin/LOGMAIL

Now define the initialization string for printer as

This is working perfectly well, you can also fine tune this script for your own requirement.

Hi!
A more elegant solution. Here is will pick of the emailid from user who has submitted the request.

Now printer definition

Very inspiring !
Your script works like magic, indeed
thanks a lot !

If only I can repay you for you time…

Madhu

It is good to here that this script has solved your problem.
You can contact me anytime.

Hi Madhu, Braj ,

I have a similar requirement where I need to email the concurrent log file as attachment. When I tried using a custom printer, I see that only if the request is successful the email is being sent. If the request errors out no email is sent. Can you please help me with this?

Regards,
Shewanka

you can not use this work-around if you want to send out email on failed requests.

This works only when the request ends with Success & the copies is set to 1. Does not work when copies is set to 0 either. We use this extensively to automatically email request output files (works great with text or PDF files) & log files. If anyone needs help, I will be happy to help. If someone has workaround for failed requests or for situations when the end-user fails to set copies=1, please share your thoughts.

Urgent

Hi Braj Kishore,
I want help from you. My requirement is also similar to this. I want to send the output of the report directly to email group. for email group i have to fetch the records from one table. Can you please guide me.

Thanks in advance.

email :

instead of the mailx command call a script.
inside the script you can select whatever values u need from the tabel by calling a sqlplus -s.