My Oracle Support Banner

RightFAX Server is Unable to Read the Directory of the PDF File (Doc ID 461357.1)

Last updated on JULY 08, 2020

Applies to:

Oracle Purchasing - Version to 12.0.4 [Release 11.5 to 12]
Information in this document applies to any platform.


The RightFax printer does not receive the Procurement document to fax.

As stated in Documentation <Bug 5990236>:

"Oracle Applications are supported across multiple Operating Systems (OS). When Oracle Applications need to communicate the document via FAX, we generate two files as of today.

1. A Control file which has content to FAX the document.
2. A pdf file which has the actual document content.

The separation of the document and control file was done because the document is in pdf (binary) format where as the control file should be an ASCII file.

Since the applications can be hosted in any OS and the RightFax is windows server, the suggestion given to Oracle customers was as follows: 

A. Set up a directory where pdf files needs to be saved
B. Set up a directory where the control files needs to be stored

Now map these directories to RightFax Server by means of any file sharing system. Then have the RightFax server listen to the directory (B), so that the RightFax server can automatically FAX the document. For example, let us the Oracle Apps is hosted in Unix OS. Now the above would be:

A. /conclog/oracle/apps/pdf/ --> pdf files will be saved here.
B. /conclog/oracle/fax/ --> the control files will be saved here.

Now, /conclog/oracle/apps/pdf/ is mapped to RightFax server as P:\ and /conclog/oracle/fax/ is mapped as F:\.
Now if we make the RightFax server listen to the directory F:\, then it will be able to pick the control files for Faxing.

Now the problem we are facing is due to the how the ATTACH command is used in the control file. The ATTACH command is used along with the complete UNIX directory structure of the pdf file. ie. the control file will look like, {{ATTACH /conclog/oracle/apps/pdf/o611472.out}}.

Since the RightFax server is a windows server, the above complete unix structure cannot be understood by the FAX server causing a failure.

So we finally decided the following solution :-

We have a profile option "PO:Fax Output Directory for the PO Document" already in place.
And we have created a new profile option: "PO:Fax Output Directory for the Control File."

The control file directory path will be set in "PO:Fax Output Directory for the Control File" profile e.g. /conclog/oracle/fax/ and the pdf file directory path will be set in "PO:Fax Output Directory for the PO Document" profile e.g. /conclog/oracle/apps/pdf/.

And in windows server these directories would be mapped to drive names say :> G: & H:

So RightFax server reads the control files from G:/filename.txt location. As previously mentioned, in the control file we have ATTACH command where we have to give the pdf document filename with the complete path. So now the ATTACH command would be as follows :- {{ ATTACH H:/filename }}

This approach fulfills the RightFax server condition too.

The values for the profile options will be set as given below :-

1) "PO:Fax Output Directory for the PO Document" This profile option would contain the Unix directory path of the document, so the value for this profile option would be like :- /conclog/oracle/apps/pdf/

2) "PO:Fax Output Directory for the Control File." This would contain the windows style directory path for the document, (this window directory would obviously be mapped to the unix directory path
of the pdf document). For this profile, the value would be like :- H:\

So the Attach command would be like :- ATTACH H:\o123.out
And as H:\ is mapped to /conclog/oracle/apps/pdf/, the o123.out file would be accessible. "


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.