Integrated Document Solutions
for Business Applications

New Blog Posts

  • September 16th 2014 Oracle Open World 2014 Edition Read More
  • September 11th 2014 4 ways manual shop packet generation is flushing money down the drain Read More
  • September 8th 2014 My lucky find for ORA-01720: Grant Option Does Not Exist. Read More
  • August 27th 2014 3 ways to improve asset reliability with automated maintenance work order printing Read More
Home / Blog / Current Page

Oracle EBS R12.1.3 Submit Request Delivery Options Button – FTP – 5 of 6

Posted on by Brent Lowe

This is the 5th post in a series on new features in 12.1.3. See the entire series here:

Part 1 – Introduction
Part 2 – IPP Print Tab
Part 3 – Email Tab
Part 4 – Fax Tab
Part 5 – FTP Tab
Part 6 – Conclusion
Part 7 – The Presentation
Part 8 – Removing the Button

Today, the final tab… FTP.

Oracle EBS 12.1.3 Delivery Options (Opt) Form FTP Tab

Functionality
This tab allows users to transfer the Concurrent Request output to a remote host either using FTP or SFTP. The user is able to specify the following:

  • Server – Where the data is to be transferred.
  • Port – Port on which the FTP/SFTP server is listening. Not a required field, will default to the correct port.
  • User – User logon on the server in question.
  • Pwd – Password for user on the server.
  • Remote Dir – Directory on remote server to place concurrent program output.
  • Secure – Checkbox to denote SFTP vs FTP.

There is no additional configuration screen or options.

Regarding the name of the transferred file, I have found that the resulting filename is the same as what is generated by the Concurrent Manager. For example:

  • When transfering BI Publisher data, the name of the file is <PROGRAM_SHORTNAME>_<REQUEST_ID>.PDF
  • When transferring Oracle Report data, the name of the file is o<REQUESTID>.out



I also came across some interesting things regarding status when I accidently fat fingered the ‘User’ field. In most cases when entering incorrect data, the Concurrent Program would complete successfully, with no indication in the Concurrent Program log that there was a problem! For example, if the password is wrong, the request completes normally and the log has the following information:

+------------- 2) DELIVER -------------+
CONC-DELIV-FTP (SERVER=wolfmanr12)
Beginning post-processing of request 5873740 on node WOLFMANR12 at 01-SEP-2010 11:07:37.
Post-processing of request 5873740 completed at 01-SEP-2010 11:07:37.
+--------------------------------------+

Based on this, I quickly tested the other combinations and came up with the following:

Test FTP SFTP
Incorrect Server Request Completes Successfully, No mention in log Request Completes with Warning, Log acknowledges an error
Incorrect Port Request Completes Successfully, No mention in log Request Completes with Warning, Log acknowledges an error
Incorrect Username Request Completes Successfully, No mention in log Request Completes Successfully, No mention in log
Incorrect Password Request Completes Successfully, No mention in log Request Completes Successfully, No mention in log
Incorrect Directory Request Completes Successfully, No mention in log Request Completes Successfully, No mention in lo


In the 2 cases above where SFTP threw an error, the error in the log was:
+------------- 2) DELIVER -------------+
CONC-DELIV-FTP (SERVER=asdfasdf)
Beginning post-processing of request 5873744 on node WOLFMANR12 at 01-SEP-2010 11:13:22.
Post-processing of request 5873744 failed at 01-SEP-2010 11:13:22 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
+--------------------------------------+

The OPP log did have the actual exception thrown in these 2 cases.

Pros and Cons

The biggest Pro here is for those companies who have FTP programs out there that are being called to deliver concurrent program data to remote hosts such as banks, logistics companies, retail sites, other vendors, etc… They could potentially remove the need for managing a customization and utilize this new form.

Other than having no way to name the file on the remote machine, the biggest Con here is what I described above regarding status. Basically, you do not want to make a typo. If you do, there is little to no information available to tell you that there was a problem!

For more information:


Share this Article


23 Responses to Oracle EBS R12.1.3 Submit Request Delivery Options Button – FTP – 5 of 6

  1. Mahesh says:

    I am on 11.5.10.2, and I need to ftp a report after it has been run, to a local ftp location, how should i do it.

    • Brent Lowe says:

      Hi Mahesh, unfortunately the functionality that I’m talking about on this post is only for R12.1.3. Plus as you can see there are quite a few caveats as far as what a ‘successful’ FTP session entails. Pretty much your only options are to write a custom program yourself to do the FTP or check out Bursting Control Files if your report is BIP based. If not DataZing may also be a good alternative.

  2. Hi!

    Im working with EBS R12 using Submit Request Delivery Options Button – FTP but now my request is How to change the name of .out file to nomenclature defined.

    DNoyola

    • Brent Lowe says:

      Hi Daniel, unfortunately I do not know of a way to change the delivered name. From my testing it seems to only use the name of the actual concurrent program output.

  3. Santosh says:

    I am working with R12.1.3, when i submit the request eith FTP details getting follwoing error. Can you please help me.
    Uploading null to /infile/ftpdata/ on 10.22.216.146
    [6/15/11 9:04:50 AM] [UNEXPECTED] [110784:RT7971253] oracle.apps.xdo.delivery.MissingRequiredPropertyException: Required property missing. Property name :[FTP_REMOTE_FILENAME]

    • Brent Lowe says:

      Based on the log entry alone, it appears that the application is not setting the filename to transfer. Is your concurrent program actually generating output?

  4. Santosh says:

    Yes, concurrent program is generating the output.
    When i am checking the xdodelivery.cfg file needs to edited. But not able to find about this file.

    • Brent Lowe says:

      You should not need the xdodelivery.cfg file for this functionality. Send me your concurrent request and Output Post Processor logfiles as well as a screenshot of how you are filling out the 12.1.3 FTP tab to my email address (brent dot lowe at strsoftware.com dot com) and I’ll take a closer look.

  5. ksoule says:

    Hi Brent,
    Santosh reported similar issue but no resolution was posted here.
    I’m on R12.1.3, when I submit the report and provide the FTP details, the concurrent program completes with the status “warning” and the OPP report the error : oracle.apps.xdo.delivery.MissingRequiredPropertyException: Required property missing. Property name :[FTP_REMOTE_FILENAME].
    Any resolution for this issue?

    • Brent Lowe says:

      Hello,

      Santosh and I went back and forth a couple times via email discussing the issue. I was not able to reproduce the problem on my instance of EBS that I have at the office, I believe it must be a bug. I’ll contact you directly to get some more information.

  6. Pingback: Resolving 12.1.3 FTP error: Required property missing. Property name :[FTP_REMOTE_FILENAME] | STR Software

  7. Brent Lowe says:

    **** – Update – Oracle has addressed the error:
    oracle.apps.xdo.delivery.MissingRequiredPropertyException: Required property missing. Property name :[FTP_REMOTE_FILENAME]

    I’ve posted the information here: http://str.staging.brainrider.com/blog/resolving-12-1-3-ftp-error-required-property-missing-property-name-ftp_remote_filename/

  8. Pramod says:

    Hi,

    We are on R12.1.3. We are able to successfully FTP output files to FTP server. but is there a plsql function/API to add this delivery option while submitting a concurrent request from a plsql code.

    PRamod J

  9. Pingback: Oracle EBS R12.1.3 Submit Request Delivery Options Button – Email– 3 of 6 | STR Software

  10. Pingback: Oracle EBS R12.1.3 Submit Request Delivery Options Button – Intro – 1 of 6 | STR Software

  11. Pingback: Oracle EBS R12.1.3 Submit Request Delivery Options Button – The Presentation – 7 of 6 | STR Software

  12. Pingback: Resolving 12.1.3 FTP error: Required property missing.:[FTP_REMOTE_FILENAME] | STR Software

  13. Pingback: Oracle EBS R12.1.3 Submit Request Delivery Options Button – Conclusion – 6 of 6 | STR Software

  14. Pingback: Oracle EBS R12.1.3 Submit Request Delivery Options Button – IPP Print – 2 of 6 | STR Software

  15. Pingback: Oracle EBS R12.1.3 Submit Request Delivery Options Button – Removing the Button – 8 of 6 | STR Software

  16. Pingback: Oracle EBS R12.1.3 Submit Request Delivery Options Button – Email– 3 of 6 | STR Software

  17. JP says:

    We also need to use gpg on the file prior to sending it via FTP. Is it possible to do this with EBS FTP/SFTP function? Any ideas?

    • Brent Lowe says:

      It does not appear to be possible to utilize gpg on the file prior to FTPing the data. The options are pretty much limited to what you see on the screen and none of them involve manipulating the actual data. To do this you will probably have to write a script that gets kicked off by a concurrent program to manipulate and then FTP your file.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>