is it possible to import an external file automatically by “External File Assistant” (Batch process)?
In our case the file type is ExtVoucher.
If yes which of these marked fields are necessary?
Our fiels are on a local path (not in cloud) while IFS is in cloud.
Best answer by Dammika Sandaruwan
Hi @Link
It's only possible to select batch mode if parameter SERVER_DIRECTORY in System Parameters For Accounting Rules is set to a valid directory in the database. This means that the directory is defined with a valid server path in the database.
In the window System Parameters for Accounting Rules (in Accounting Rules) it is possible to define a value for the parameter SERVER_DIRECTORY.
By default the attribute SERVER_DIRECTORY has the parameter value NULL. As long as NULL is defined it will not be possible to run the External Voucher Assistant in batch mode.
This must be a directory defined in the oracle database which is set to valid server path.
Specifying a directory example: (as appowner).
create or replace directory EXT_DIR
as 'C:\OraDB\A\ExternalFiles';
Even in cloud hosted environments, it might be possible to create a server directory in database to achieve this requirement.
You can find further information from following IFS documentation.
This Automatic loading of external files can be achieved through routing rule setup with FTP reader as well and there is a template routing rule provided in IFS cloud version as illustrated below.
The template routing rule for importing external files is named Example_External_File_Import. The API that will be called from the triggered Routing Rule is Ext_File_Server_Util_API.Load_External_File. Location based conditions have been used to trigger this Routing Rule. Currently, the unique parameter set is the file path.
File Path: EXTERNAL_FILE*
As seen here, default File Path accepts file names prefixed with EXTERNAL_FILE. It can be configured based on the user requirement.
Also you need to setup the FTP reader in IFS readers as below.
The steps in this process are,
Add file to the FTP IN folder with a file name that is accepted by the Routing Rule and one that satisfies the file name in External File Template. File will be loaded through application messages. Run the Batch Process through the schedule.
In here, the routing address connected has plsql method invocation of ‘Ext_File_Server_Util_API.Load_External_File’ and this method is not available in IFS app 10 and you may contact IFS Global support to check the possibility of implementing same routing rule setup this in app 10 version.
You can choose batch process option from the ‘External File Assistant’ dialog window.
When you complete this assistant, you will be directed to ‘New Database Task Schedule’ window automatically and you can schedule how this batch process should be executed in there.
If you run this particular external file as a batch process, then you need to fill only highlighted fields in external file template as mentioned below. (no need to fill client paths)
You can try fully qualified path of the local server which you dispatch these external files and if it doesn’t work you may contact one of IFS cloud op engineer to see how to access files from this local directory.
It's only possible to select batch mode if parameter SERVER_DIRECTORY in System Parameters For Accounting Rules is set to a valid directory in the database. This means that the directory is defined with a valid server path in the database.
In the window System Parameters for Accounting Rules (in Accounting Rules) it is possible to define a value for the parameter SERVER_DIRECTORY.
By default the attribute SERVER_DIRECTORY has the parameter value NULL. As long as NULL is defined it will not be possible to run the External Voucher Assistant in batch mode.
This must be a directory defined in the oracle database which is set to valid server path.
Specifying a directory example: (as appowner).
create or replace directory EXT_DIR
as 'C:\OraDB\A\ExternalFiles';
Even in cloud hosted environments, it might be possible to create a server directory in database to achieve this requirement.
You can find further information from following IFS documentation.
This Automatic loading of external files can be achieved through routing rule setup with FTP reader as well and there is a template routing rule provided in IFS cloud version as illustrated below.
The template routing rule for importing external files is named Example_External_File_Import. The API that will be called from the triggered Routing Rule is Ext_File_Server_Util_API.Load_External_File. Location based conditions have been used to trigger this Routing Rule. Currently, the unique parameter set is the file path.
File Path: EXTERNAL_FILE*
As seen here, default File Path accepts file names prefixed with EXTERNAL_FILE. It can be configured based on the user requirement.
Also you need to setup the FTP reader in IFS readers as below.
The steps in this process are,
Add file to the FTP IN folder with a file name that is accepted by the Routing Rule and one that satisfies the file name in External File Template. File will be loaded through application messages. Run the Batch Process through the schedule.
In here, the routing address connected has plsql method invocation of ‘Ext_File_Server_Util_API.Load_External_File’ and this method is not available in IFS app 10 and you may contact IFS Global support to check the possibility of implementing same routing rule setup this in app 10 version.
To create input directory the steps are as follows;
Create Folders in Database Server (in the environment that you want this set up, ex: PROD, TEST, TRN etc..) example folder 'F:\Data\FileUpload'
Log on to TEST/TRN/PROD database through PL/SQL to create database folder and execute the below command.
create directory AU_TO_IFS as 'F:\Data\FileUpload'
NOTE: F:\Data\FileUpload is the folder where files will be saved
If it is IFS Managed Cloud, you will have to raise a ticket with IFS Support and ask them to create one for you, and potentially ask them to create a user so you can access the folder via FTP Client
To create input directory the steps are as follows;
Create Folders in Database Server (in the environment that you want this set up, ex: PROD, TEST, TRN etc..) example folder 'F:\Data\FileUpload'
Log on to TEST/TRN/PROD database through PL/SQL to create database folder and execute the below command.
create directory AU_TO_IFS as 'F:\Data\FileUpload'
NOTE: F:\Data\FileUpload is the folder where files will be saved
If it is IFS Managed Cloud, you will have to raise a ticket with IFS Support and ask them to create one for you, and potentially ask them to create a user so you can access the folder via FTP Client
Hi @malik.sally
thank you a lot. I am waiting for the IFSAPP user password.
Yes, it means that the “Directory Path” does not exist on the file system level.
Have you created the folders manually on the database server also? The Oracle command does not create the directory in the file system, that needs to be done manually.
Yes, then I think you need to create a ticket to IFS to get that created.
Maybe there is some problem with permission if you create it with your FTP user. Then the user running Oracle might not get access to that directory. Or the path is not exactly correct.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.