12/5/2014 Document Display

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=a12mmoo3_9 1/6
Mails are not Received Using Delivery Option while Submitting Concurrent Request In R12.1.3
(Doc ID 1339491.1)
Modified: 08-Jul-2013 Type: PROBLEM
In this Document
Symptoms
Cause
Solution
References
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been
subject to an independent technical review.
APPLIES TO:
Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
SYMPTOMS
Using the Delivery Options feature available in R12.1.3 version, the output of the concurrent request is not being delivered
via email.
The concurrent program delivery options are not working through Delivery Opts for Email Notification.
When a request is submitted and the Delivery Opts button is selected for sending an Email Notification, there is neither an
error (in the FNDCPOPP log or REQUEST log files) nor is the email sent.
12/5/2014 Document Display
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=a12mmoo3_9 2/6

The ICM log file was showing the following errors.
#########################
Internal Concurrent Manager started : 13-JUL-2011 14:11:37
+---------------------------------------------------------------------------+
Process monitor session started : 13-JUL-2011 14:11:37
CONC-SM TNS FAIL
Call to PingProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to StopProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to PingProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to StopProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to PingProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to StopProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to PingProcess failed for FNDOPP
CONC-SM TNS FAIL
Call to StopProcess failed for FNDOPP
#########################
12/5/2014 Document Display
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=a12mmoo3_9 3/6
After the request completed normally, the email notification sending part was failing as the TNS ping failed.
+++++++++++++++++++++++++++++++++++++++++++++++
The following sample request log file extract displays an entry of the DELIVER option to the respective email id that should
be seen:-
+------------- 2) DELIVER -------------+
Emailing output to xxx.yyy@oracle.com
Beginning post-processing of request 5904473 on node ZZZZZ at 05-JUL-2011 16:21:45.
Post-processing of request 5904473 completed at 05-JUL-2011 16:23:03.
+--------------------------------------+
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 05-JUL-2011 16:23:03
+---------------------------------------------------------------------------+
#########################
The sample FNDCPOPP manager log file shown below, consists the following details for a successful email notification
delivery.
#########################
[5/19/11 10:01:21 PM] [main] Starting GSF service with concurrent process id = 2047653.
[5/19/11 10:01:21 PM] [main] Initialization Parameters: oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
[5/19/11 10:01:21 PM] [Thread-19] Service thread starting up.
[5/19/11 10:01:21 PM] [Thread-20] Service thread starting up.
[7/5/11 4:21:47 PM] [OPPServiceThread0] Post-processing request 5904473.
[7/5/11 4:21:47 PM] [2047653:RT5904473] Executing post-processing actions for request 5904473.
[7/5/11 4:21:48 PM] [2047653:RT5904473] CONC-OPP-DELIV BEGIN (REQID=5904473)
[7/5/11 4:21:48 PM] [2047653:RT5904473] Beginning email delivery
[7/5/11 4:23:03 PM] [2047653:RT5904473] Completed post-processing actions for request 5904473.
[7/5/11 4:36:09 PM] [OPPServiceThread0] Post-processing request 5904477.
#########################
Whereas in the case where an issue exists the respective log files show the following:-
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
+---------------------------------------------------------------------------+
Executing request completion options...
+------------- 1) PUBLISH -------------+
Beginning post-processing of request 433207 on node XXXXX at 08-JUL-2011 16:08:01.
Post-processing of request 433207 completed at 08-JUL-2011 16:08:02.
+--------------------------------------+
12/5/2014 Document Display
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=a12mmoo3_9 4/6
+------------- 2) PRINT -------------+
Printing output file.
Request ID : 433207
Number of copies : 0
Printer : noprint
+--------------------------------------+
+------------- 3) insert into FND_ENV_CONTEXT -------------+
+--------------------------------------+
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 08-JUL-2011 16:08:02
+---------------------------------------------------------------------------+
#########################
The FNDCPOPP manager log file was not showing any errors even though the mail was not sent, since the issue was with
the TNS ping.
#########################
[7/8/11 4:08:01 PM] [OPPServiceThread1] Post-processing request 433207.
[7/8/11 4:08:01 PM] [18924:RT433207] Executing post-processing actions for request 433207.
[7/8/11 4:08:01 PM] [18924:RT433207] Starting XML Publisher post-processing action.
[7/8/11 4:08:01 PM] [18924:RT433207]
Template code: XX
Template app: XX
Language: en
Territory: 00
Output type: EXCEL
[7/8/11 4:08:02 PM] [18924:RT433207] XML Publisher post-processing action complete.
[7/8/11 4:08:02 PM] [18924:RT433207] CONC-OPP-DELIV BEGIN (REQID=433207)
[7/8/11 4:08:02 PM] [18924:RT433207] Beginning email delivery
[7/8/11 4:08:02 PM] [18924:RT433207] Completed post-processing actions for request 433207.
#########################

CAUSE
The cause was found to be that the following profile options need to be set in order to enable the feature.
'FND:SMTP Host' and 'FND:SMTP Port'

SOLUTION
1. The errors occurring in the ICM log file related to TNS ping needs to be corrected.
- Perform the solution steps as per Note 1312632.1
2. Set the profile options "FND:SMTP Host" and "FND:SMTP Port" by providing the right values as per Note 1240768.1
12/5/2014 Document Display
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=a12mmoo3_9 5/6
2. Set the profile options "FND:SMTP Host" and "FND:SMTP Port" by providing the right values as per Note 1240768.1
shown below
---------------------------------------------------------------
a. Log into System Administrator responsibility.
b. Navigate to Profile - System.
c. Query up the %SMTP% profiles.
d. Set the following profile values to the defined host and port:
FND:SMTP Host
FND:SMTP Port
Example
FND:SMTP Host = mail.<server_name>.com
FND:SMTP Port = 25
e. Resubmit request and monitor email delivery.
---------------------------------------------------------------
3. Ensure there is a valid email id such as xxx_yyy@zzz.com given in the FROM field of the delivery options.
4. Check whether you have received the mail in your inbox.
Note:-
1. From, Subject and To fields are mandatory.
2. In case you did not receive any mail, there might be a chance that the file-size would be high. For Example, 'Active
Users' output size will be Huge. if the email server has limitation on the file size then it rejects the email.
3. Ensure you provide a valid email-id in "from" field. In case if the from email-id is wrong and there are some issue
while delivering the email, then the report from email server will not reach you. To change the email id, Use the
below Navigation.
Login as 'System Administrator' responsibility > Security > User > Query the
user

12/5/2014 Document Display
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=a12mmoo3_9 6/6

Important:-
____________

It was found for one of the customers instance with email server using CRAM-MD5 authentication mechanism (Note
469822.1 to test SMTP connectivity).
CRAM-MD5 is not supported by notification mailer in 12.1.3 (Note 1095146.1).
The only supported authentication mechanisms so far with Workflow Mailer are - PLAIN, LOGIN, and DIGST-MD5 (+ NTLM
with extra patch 9452181).


REFERENCES
NOTE:1095146.1 - Oracle Workflow Release Notes for Release 12.1.3
NOTE:1036586.6 - How to Redirect Output from Printer to Mail Message after Running Report
NOTE:1240768.1 - R12: "PostProcessorException: Unable to determine SMTP server to use: set FND_SMTP_HOST" Error In
OPP manager log file When Selecting Delivery Opts in FNDRSRUN to Send Email Notifications
NOTE:1312632.1 - Concurrent Processing - ICM log file shows 'CONC-SM TNS FAIL', 'Call to PingProcess failed', and/or 'Call
to StopProcess failed' for FNDCPGSC/FNDOPP
NOTE:382766.1 - Concurrent Request Email Notification is Not Sending Email
NOTE:469822.1 - Oracle Workflow Release 12 Diagnostics
NOTE:1567162.1 - Concurrent Program Output is Not Sent Through Email ; Error in OPP Log When 'Delivery Opts' Chosen