Oracle FLEXCUBE interfaces with other systems installed at your bank to handle Incoming/Outgoing data using batch mechanism (Flat files). This chapter discusses the features that are supported by Oracle FLEXCUBE to streamline the exchange of data between the system and external systems.
This chapter contains the following sections:
You can set the parameters for the framework of Generic Interface processing in the following screen ‘Parameters’ screen invoked from the Application Browser. You can invoke this screen by typing ‘GIDPARAM’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can maintain the following parameters for generic interface here.
You can specify the parameters for interface processing if the schedule date falls on a holiday.
Holiday Treatment
Check this box to indicate your preference for interface processing on a holiday.
Next Run Date
Specify how the system should process if the schedule date falls on a holiday. You can select the options as either move the interface processing to previous working date or next working date if the interface processing day falls on a holiday.
Note
The default holiday treatment is movement to ‘next working date’.
Purging Days
Specify the purging days if you want to maintain any days to be purged while processing interface.
You can specify the parameters for interface processing for the incoming files.
Uploaded Record Status
Select the input status of the transaction record after upload as:
Note
By default ‘Authorized’ option is selected.
Bad File Path
Specify the path where the external tables should write the bad records, while reading from the Incoming file.
Log file Path
Specify the path where the external tables should write the Log file, while reading from the Incoming file.
You can specify the parameters for interface processing for the outgoing files.
Archival Required
Check this box to specify if the upload table data and file log data should be archived at the time of EOD or before deleting the same.
File writing process
Select the tool to write the data into output file from the following options:
Note
By default ‘Oracle’ option is selected.
You need to note the following details while selecting the tool for file writing:
This section contains the following topics:
You can prepare complex queries to use them in the outgoing interface definition for data extraction. ‘Object Definition’ screen can be used to create queries which can be invoked from the Application Browser. You can invoke this screen by typing ‘GIDOBDEF’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can maintain the objective definition for generic interface here.
Name
Specify the unique interface object name which is created here.
Description
Specify a description for the object name.
Type
Select the required object definition type from the following options:
Note
Static field gets enabled for you to specify the query when you select the type of definition as ‘static’.
Static
Specify the predefined query for the static definition here.
Note
This field gets enabled only if you select the type of definition as ‘static’.
You can map the database object details here.
Object Name
Select the database object name that is used for the dynamic query.
Note
Database object would be either table or Synonym or view.
Alias Name
The alias name for the database object gets displayed which is same as the object name by default. You can modify it.
You can map the fields of the database object selected here.
Field Name
Select the column which can be used from the database object.
Alias
The alias of the column name in the select query that is generated which by default the column name itself. You can modify it.
Data Type
The data type of the field gets displayed here.
Data Length
The data length of the field gets displayed here.
Where Clause
Specify the where clause for the resultant dynamic query here. You can define the join conditions of multiple tables along with the filter condition of the query.
Group By
Specify the group by clause for the resultant dynamic query here.
Order By
Specify the order by clause for the resultant dynamic query here.
Having Clause
Specify the having clause for the resultant dynamic query here.
Query
Specify the indexes which can be used for the query. This index gets used for the query.
You can view the details of objectives maintained in the system through ‘Object Summary’ screen. You can invoke this screen by typing ‘GISOBDEF’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can click ‘Search’ button to view all the object definition records of your bank. You can filter your search based on any of the following criteria:
Authorization Status
Select the authorization status of the object defined from the dropdown list. The options are:
Name
Select the name of the object maintained from the option list.
Order by Clause
Select the order by clause maintained for the object from the option list
Having Clause
Select the having clause maintained for the object from the option list
Record Status
Select the record status of the object from the drop-down list. The options are:
Description
Select the description maintained for the object from the option list
Group by Clause
Select the group by clause maintained for the object from the option list
Where Clause
Select the where clause maintained for the object from the option list
When you click ‘Search’ button the records matching the specified search criteria are displayed. For each record fetched by the system based on your query criteria, the following details are displayed:
The search functions available are:
Advanced - Click Advanced to specify queries with logical operators such as AND, OR and NOT.
Reset - Click Reset to empty the values in the criteria fields, so that you may begin a new search.
Query - After specifying your search criteria click Query to view the list of results which match your search criteria.
Refresh - Click Refresh to refresh the list of results.
You can maintain the AUDF (ASCII User Define Function) details in the ‘AUDF Maintenance’ screen. You can invoke this screen by typing ‘GIDAUDFM’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
Specify the following AUDF details in this screen.
AUDF Name
Specify the name of the AUDF here.
Description
Specify a description for the AUDF here.
Unit Name
Specify the invoked function name here.
AUDF Type
Select the AUDF types from the drop-down list. The following options are available:
You can view AUDF details maintained in the system using ‘AUDF Summary’ screen. You can invoke this screen by typing ‘GISAUDFM’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can click ‘Search’ button to view all the AUDF records of your bank. You can filter your search based on any of the following criteria:
Authorization Status
Select the authorization status of the AUDF you want to view the details from the drop-down list. The options are:
Record Status
Select the record status of the AUDF from the drop-down list. The options are:
AUDF Name
Select the name of the AUDF from the option list.
Description
Select the description of the AUDF from the option list.
When you click ‘Search’ button the records matching the specified search criteria are displayed. For each record fetched by the system based on your query criteria, the following details are displayed:
This section contains the following topics:
You can define the format details and properties associated with interface file in the ‘Interface Definition’ screen. You can invoke this screen by typing ‘GIDIFTDF’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can define the following interface file properties, formats and components here.
Branch Code
Specify the code of the branch to which the interface belongs.
Interface Type
Select the interface type from the following options:
File Mask
Specify the file mask for the outgoing interface file.
CRC Required
Check this box if you want to check the CRC while transferring the data.
In case of incoming interface, system checks for the CRC value in the file name maintained in ‘CRC file mask’. For outgoing interface, system generates the CRC value in a CRC file.
CRC File Algorithm
Specify the CRC algorithm which has to be used to calculate the CRC Value.
CRC File Mask
The path of CRC File mask gets displayed here.
CRC File Path
The path of CRC File gets displayed here.
External System
Specify the external system with which Oracle FLEXCUBE is interfacing.
Format Type
Select the type of data length in the interface from the following options:
Delimiting Character field gets enabled for you to specify the delimiting character if you select the format type of definition as ‘Delimited’.
File Path
Specify the path of the file.
Data Log Required
Check this box to indicate if the confirmation details are required t in logged file
Commit/Fetch Frequency
Specify the number of transaction committed or fetched at a given point of time.
Date Format
Specify the date format for the interface file.
No of Executions Day
If you select frequency type as ‘Daily’, specify the total number of interface file processing executions in a day.
This field is applicable only for incoming interface file process.
Duplication File Check Reqd for Current Date
Check this box to indicate that the duplicate files should not be added for the current date.
Interface Code
Specify a unique interface code to identify the interface as incoming or outgoing.
Delimiting Character
Specify the delimiting character if you select the format type of definition as ‘Delimited’.
When to Run
Select the stage of application the interface has to be triggered.
Mandatory
Check this box to indicate that the interface has to be mandatorily processed before moving on to the next stage of EOD. If this box is checked system checks if the interface has been processed or not and if it is not processed system will not allow movement to the next EOD stage.
Triggering
Select an appropriate option to indicate how the interface should be triggered. The options available are:
During EOD if there are any mandatory unprocessed interfaces and if the triggering type is selected as ‘System’ then the interface is triggered automatically. In case of Incoming interface if triggering type is selected as ‘System’ then system checks if the file is available in the ‘ready’ folder for that interface. If the file is present the system will process it. In case of outgoing interface if triggering type is selected as ‘System’ then, system will automatically trigger the Outgoing interface.
Note
If the interface is mandatory, the triggering type must be system. Even if the triggering type is mentioned as System, you can manually trigger the interface whenever required through Interface triggering screen.
Conformation File Required
Check this box to indicate if confirmation is required for an incoming file. If this box is checked then when incoming file is processed, system checks whether confirmation file is available in the folder specified. If the file is not available then incoming file processes will raise an error indicating the confirmation file is not available.
Conformation File Path
The path of confirmation file gets displayed here.
Conformation File Mask
The path of confirmation file mask gets displayed here.
You can specify the justification details of fixed format type interface file here.
Date
Select the justification type for date field from the drop-down list. The options are:
Number
Select the justification type for number field from the drop-down list. The options are:
Text
Select the justification type for text field from the drop-down list. The options are:
Note
Default justification type for text and date field type is Left and number field type is right.
Frequency Type
Select the frequency type for interface file processing from the following drop-down options:
Note
If Adhoc is specified it will override any existing restrictions.
Week Day
If you select frequency type as ‘Weekly’, select the day from the drop-down list for processing the interface file. The options available are:
Month
If you select frequency type as ‘Quarterly, Half Yearly and Yearly’, select the month for the interface file execution from the drop-down list. The options available are:
Date
If you select frequency type as ‘Monthly, Quarterly, Half Yearly and Yearly’, select the date of the month for the interface file execution from the drop-down list.
Last Run Date
The last run date gets displayed here
Next Run Date
The day on which the interface can be triggered gets displayed here.
You can specify the padding character of fixed length format type interface file here. All the data types can have the same padding character
Date
Specify the padding character for date field.
Number
Specify the padding character for number field..
Text
Specify the padding character for text field.
Note
All the data types can have the same padding character.
Pre Message
Specify the value that should be calculated before triggering the interface in the predefined format.
Post Message
Specify the value that should be calculated after Interface processing is done in the predefined format.
Pre Message AUDF
Specify the AUDF that needs to be invoked before triggering the interface. You can use this to add additional functionality required at the message level.
Post Message AUDF
Specify the AUDF that needs to be invoked after triggering the interface. You can use this to add additional functionality required at the message level.
You can specify the interface details applicable for incoming file details here.
Function ID
Specify the function id for which the incoming data need to be sent.
Incoming File Mask
Specify the file mask for selecting the incoming files from the file directory. System supports four types of file masking:
System searches all the files which are matching the mask criteria and process the files one by one “_” as the split separator for the file name and the mask criteria.
Note
System will continue or break the uploading of records based on the error handling defined in the 'On Override' field. If it is Continue, then the system will ignore the current record and continue with the next record. If it is Reject, then the system will stop the execution of the file and start executing the next available incoming file.
Note
By default system append the Incoming File Mask type to the file name while searching the physical file name. If an interface supports for multiple type incoming files, then same file mask is applicable for all type of incoming files.
Processed File Mask
Specify the file mask for renaming the incoming file after uploading the data.
Default Action
Select the default action which needs to be invoked to process the uploaded data in the upload table from the drop-down list below:
On Override
Select the action to be taken if an override occurs from the drop-down list below:
Outgoing Interface
Specify the corresponding outgoing interface file for the above incoming file.
Suppress Start Reference
Check this box to indicate that the start reference number should be suppressed.
If the checkbox is selected and start reference element is defined in the component definition, system raises an error message while saving the interface. System validates the start reference check for Header, Body and Footer.
For a given interface, mask and suppress start reference are applicable to all the file names configured for that interface
Log Output
Select the type of details to be updated in the log file from the adjoining drop-down list. This list displays the following values:
While processing the interface file, system verifies the log output value and the below details:
During the interface configuration, log_failure and log_success folders are created in the interface configured folder.
You can specify the parallel process details here.
Parallel Process Required
Check this box to indicate if parallel processing is required if multiple interface files has to be processed at a given time.
When you select parallel process required parallel process type field gets enabled.
Parallel Process
Select the type of parallel process you want to keep for the interface processing:
No of Records
Specify the number of records of parallel process can be performed at a given time. This field gets enabled only if you select the parallel process type as ‘Record based’.
No of Parallel Process
Specify the number of parallel process can be performed at a given time. This field gets enabled only if you select the parallel process type as ‘Process based’.
You can specify the component details here. Click ‘Component Details’ button in the ‘Interface Definition’ screen.
The following details are captured here:
You can specify the component linkage details here.
Serial Number
Specify the component position here.
Component Name
Specify a name for the component.
Component Type
Select the type of component from the options available in the drop-down list. The options available are:
If header and footer are defined in component details section and opted for suppressing start reference, then system consider the first line as header and bottom most line as the footer and continues the execution.
Parent
Specify the parent component to which component is linked
Relation
If parent component is specified, then specify the relation here.
Batch by Field
Specify the field in the component based on which you want to create a batch.
This is applicable only for Outgoing Interfaces.
Where Clause
Specify the where Clause for the component
Group By
Specify the group by clause for the component.
Order By
Specify the order by clause for the component.
Pre Component
Specify the value to be calculated before the component is processed, if any.
Pre Component AUDF
Specify the AUDF that has to be executed before the component is processed, if any.
You can use this to add any additional functionality required at the component level.
Post Component
Specify the value to be calculated after the Component is processed, if any.
Post Component AUDF
Specify the AUDF that has to be executed after the component is processed, if any.
You can use this to add any additional functionality required at the component level.
Pre Record
Specify the value that needs to be calculated before the record is processed, if any.
Pre Record AUDF
Specify the AUDF that has to be executed before the record is processed, if any.
You can use this to add any additional functionality required at the record level.
Post Record
Specify the value that needs to be calculated after the record is processed, if any.
Post Record AUDF
Specify the AUDF that has to be executed after the record is processed, if any.
You can use this to add any additional functionality required at the record level.
You can specify the component field linkage details here.
Serial Number
Specify the order of fields here.
Field Name
Specify the field name here
Field Type
Select the type of field from the options available in the drop-down list. The options available are
Default
Specify the default value for the field here.
Data type
Specify the data type of the field here.
Length
Specify the length of the field here.
Column Name
Specify the column name in the database of the field here.
Object Name
Specify the object name from which the field should be derived.
Start Position
Specify the start index of the field in the fixed length format.
Precision
If the field is of numeric type, then specify precision here.
Translation
If the field value needs to be translated then select the translation code that has to be used for the translation.
Un-translated
Specify the action to be taken if the translation value is not present
Pre Field
Specify the value that needs to be calculated before the field value is processed.
Pre Field AUDF
Specify the AUDF that should be executed before the processing of the field here.
Post Field
Specify the value that needs to be calculated after the field value is processed.
Post Field AUDF
Specify the AUDF that should be executed after the processing of the field.
Primary Key
Check this box to indicate the primary key to identify the individual record in the incoming file.
Note
System allows a maximum of 5 elements as Primary Key element for a component and it is applicable to component body alone. If the interface has multiple components, then system allows defining primary key in any one of the component.
Click on ‘Incoming File Names’ button in the ‘Interface Definition’ screen to specify the incoming interface file names.
You can specify the Incoming file names here.
The incoming file names are maintained here.
File Name
Specify the incoming interface file name here.
You can view the interface details maintained in the system using ‘Interface Definition Summary’ screen. You can invoke this screen by typing ‘GISIFTDF’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can click ‘Search’ button to view all the interface records of your bank. You can filter your search based on any of the following criteria:
Authorization Status
Select the authorization status of the Interface definition you want to view the details from the drop-down list. The options are:
Branch code
Select the branch code belonged to the interface details from the option list.
Interface code
Select the interface code belonged to the interface details from the option list
Record Status
Select the record status of the interface details from the drop-down list. The options are:
External System
Select the name of the external system belonged to the interface details from the option list.
Interface Type
Select the type of interface from the option list as incoming or outgoing.
When you click ‘Search’ button the records matching the specified search criteria are displayed. For each record fetched by the system based on your query criteria, the following details are displayed:
The search functions available are:
While saving the Interface Definition details, a dynamic package is created in the database along with external tables for each component in case of incoming file.
This section contains the following topics::
The steps involved in Outgoing interface file processing is explained below:
There are two upload tables for handling the process of incoming interface. The master Upload table is for handling the master data and detail Upload table for the child data which can have 200 VARCHAR2 (4000) fields to store data for each field in the file. Intermediate fields cannot be considered for transaction processing but could be used only for derivation/transaction of transaction data.
You can trigger file transfer process by invoking the fn_process_file function in the dynamic package. This function consists of cursors based on the external tables created. When a parent record is read from the external table a Record Identifier is generated for that record and it is assigned to the children when inserted into the upload table which helps in identifying the corresponding children for that parent record in ‘D’ Process.
If a relation is mentioned in the component definition and the relation fields are provide in the file then the corresponding fields are used for identifying the child records. Which one to use will be determined by the dynamic package generator based on the Interface Maintenance parameters.
The files taken for processing at the time of processing is decided by the incoming file mask selected for the particular interface.
For example, in Interface Definition (BIS):
if the incoming file name is defined as “CCYUPLOAD.TXT” and incoming file mask is defined as “YYYYMMDDHHMISS”, then system will search and process the file names like CCYUPLOAD_20100110201000.TXT, CCYUPLOAD_20100110202001.TXT.
If the incoming file mask is defined as “nnn” then system will search and process the file names like CCYUPLOAD_001, CCYUPLOAD_002.
If the incoming file mask is defined as “Starting with File Name”, system will search and process all the files which are starting with Incoming File name like (CCYUPLOAD_20100110200010.TXT, CCYUPLOAD_201001102020.TXT, CCYUPLOAD_001, CCYUPLOAD_002).
You can trigger data process by invoking the fn_upload function in the dynamic package. This function can be divided into two parts:
Populating the appropriate FCJ type with values from the upload tables is taken care by invoking the fn_upload_table_to_type function which populates the data from upload table to type using the cursors on upload table based on the base table columns.
Invoking the FCJ function ID package for processing the data is taken care by the function itself by invoking the appropriate function ID package’s fn_main function with the populated type and action. The validation and business process which are already incorporated as part of the function ID development.
After data processing, the log is written for the records if the primary key has been selected at the interface definition level. Else, the log is not written for that record.
Parallel processing feature is available only for Incoming file process and under incoming process it would be supported for data process i.e D-process. You need to select parallel option and the number of parallel processes or each process for processing specified number of records in the ‘Interface Definition’ screen.
During file processing stage, system would check whether parallel process is required or not. If required, based on the parallel process parameter system would internally updates the process number field of master upload table.
During data processing stage, system could check maximum number of process and submit job for each process number. System would wait till all the processes are completed. If any process is resulted in error then the interface would be considered as error.
Generic Interface supports CRC-32 and Adler-32 Checksum algorithms for generating CRC value of the file. Other CRC components which are developed in Java and PL/SQL are also supported by GI using the ‘CRC Maintenance’ screen.
You can invoke this screen by typing ‘GIDCRCFN’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can write the invocation stub along with the CRC componenet details here:
CRC Name
Specify the CRC Algorithm used to calculate the CRC value for the file.
Description
Specify the description of the CRC Algorithm here.
Invocation Stub
Specify the stub to invoke the CRC generation component.
You can view the CRC details maintained in the system using ‘CRC Summary’ screen. You can invoke this screen by typing ‘GISCRCFN’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can click ‘Search’ button to view all the CRC records of your bank. You can filter your search based on any of the following criteria:
Authorization Status
Select the authorization status of the CRC algorithm from the drop-down list. The options are:
CRC Name
Select the name of the CRC algorithm from the option list.
Record Status
Select the record status of the CRC algorithm from the drop-down list. The options are:
Description
Select the description of the CRC algorithm from the option list.
When you click ‘Search’ button the records matching the specified search criteria are displayed. For each record fetched by the system based on your query criteria, the following details are displayed:
The search functions available are:
You can maintain translation details required between the external system values to Oracle FLEXCUBE Values and vice Versa in the ‘Translation Definition’ screen. You can invoke this screen by typing ‘GIDTRANS’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can capture the following details here:
Translation Name
Specify the translation name you want to keep for the set. The translation name gets linked to the interface field whose value needs to be translated during Interface Processing.
The following details are specified here:
In Param
Specify the system value for the corresponding external systems value.
Out Param
Specify the external system’s value for the corresponding Oracle FLEXCUBE value.
You can view the translation details maintained in the system using ‘Translation Summary’ screen. You can invoke this screen by typing ‘GISTRANS’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can click ‘Search’ button to view all the translation records of your bank. You can filter your search based on any of the following criteria:
Authorization Status
Select the authorization status of the translation you want to view the details from the drop-down list. The options are:
Record Status
Select the record status of the translation from the drop-down list. The options are:
Translation Name
Select the name of the translation from the option list.
When you click ‘Search’ button the records matching the specified search criteria are displayed. For each record fetched by the system based on your query criteria, the following details are displayed:
The search functions available are:
You can use ‘Run Chart Summary’ to list the interfaces that should be processed in the branch on current branch date. You can invoke this screen by typing ‘GISRNCHT’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can click ‘Search’ button to view the list the interfaces that should be processed on the current date. You can filter your search based on any of the following criteria:
Branch Code
Select the branch code of the branch for which you want to view the run chart from the option list.
External System
Select the name of the external system to which the interface code is linked from the option list.
Interface Code
Select the name of interface code which has to be processed from the option list.
Interface Type
Select the type of interface from the option list as incoming or outgoing.
When you click ‘Search’ button the records matching the specified search criteria are displayed. For each record fetched by the system based on your query criteria, the following details are displayed:
The search functions available are:
This section contains the following topics:
You can trigger the process of Generic Interface using Gateway Messages, EOD run or through ‘Interface Trigger’ screen. You can invoke this screen by typing ‘GIDIFPRS’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can provide the following details here to invoke the GI routing package.
Branch Code
Specify the branch code from where the GI file process has to be initiated.
Interface Code
Select the Interface Code that has to be processed.
Based on the selected interface code, system defaults external system and interface type.
File Name
Specify the file name if the selected Interface Code is Incoming.
Process Code
Select the process code from the drop-down list, if the selected Interface Code is Incoming. The options available are:
Physical File Name
A physical file name is applicable if you are processing a file that is uploaded through the ‘Interface Trigger’ screen.
When the file upload is successful, the system will display the name of the file in this field.
File Mask
The system displays the incoming file mask specified during interface definition.
From the ‘Interface Trigger’ screen, you can upload a file from your machine to the server for incoming interface processing.
Click ‘File Upload’ button on the ‘Interface Trigger’ screen. The system displays the following screen.
Click ‘Browse’ button to select the file from your local machine. Once the file is selected, click ‘Upload’ button to start the file upload.
The system allows you to upload the file only if the extension of the file is ‘.txt’ and the content is plain text. If these conditions are not met, the system will display an error message.
On successful upload, the system will display a confirmation message. The file is uploaded to the DB server with the branch user ID prefixed to its name.
If the upload is successful, the system will display the file name in the filed ‘Physical File Name’ of ‘Interface Trigger’ screen. Click ‘Process’ button to process the file.
Note
You can move the incoming file to the DB server ‘Read’ folder manually or through file upload feature.
Before starting the file upload, ensure that you have sufficient access permissions/grants to move and copy the files in the following folders inside file path specified while defining the interface.
Ensure that you have sufficient access permissions to the location mentioned for CRC and confirmation.
Ensure that the Oracle directory ‘IN_WIP’ is created with java io file permissions. This corresponds to an entry in ‘ALL_DIRECTORIES’ table with directory name as ‘IN_WIP’ and directory path as ‘filepath/'wip’, where the file path is the path maintained in Interface Definition screen (GIDIFTDF).
For an outgoing file it is a single process of reading for database and writing in to file. But for incoming file there are two steps,
For scheduling uploads, you need to set the parameter ‘IS_UPLOAD_SCHEDULED’ to ‘Y’ in CSTB_PARAM table. You can schedule the uploads by creating a job in ‘Job Maintenance’ with the class name 'com.ofss.scheduler.quartz.FCGiUploadQrtz'. The block of code for input into the scheduler polling table should be present in the relevant source code.
To invoke ‘Scheduled Upload Logs’ screen, type ‘GISSULOG’ in the field at the top right corner of the application toolbar and click the adjoining arrow button.
You can search for the fields based on one or more of the following parameters:
The following details for each record are available in the results:
When you select the interface data for archiving while maintaining the parameters, the data gets archived. The upload table data and file log data is moved to archive tables. If parameter is set to delete then data is deleted from the upload/log tables without archiving.
During generic interface for an incoming file, the file is placed in the ready folder when it’s ready for upload. When Interface is triggered and after the successful file validation, it is moved to file processed folder and the interface processing unit gets triggered.
If the file validation fails the file is moved to the Error folder. After the successful processing of the file, it is renamed with actual file name and current date time stamp (YYYYMMDDHHMISS format) which is separated by underscore (_) and moved to the processed folder.
During generic interface for an outgoing file, the file writing process takes place in the WIP folder and after the successful completion of the writing process, the file is moved to the Ready folder. The file is renamed based on the file mask maintained.
You can track the status of interface processing using the ‘File Log’ screen. You can invoke this screen by typing ‘GISFILOG’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can click ‘Search’ button to view all the interface transaction records of your bank. You can filter your search based on any of the following criteria:
Branch code
Select the branch code of the interface file you want to track from the option list.
Interface Code
Select the interface code of the interface file you want to track from the option list.
Date of Processing
Select the date of the interface file transaction you want to track from the option list.
External System
Select the external system name with which the interface files transaction you want to track from the option list.
Status
Select the status of the interface file transaction you want to track from the option list.
Process code
Select the process code of the interface file you want to track from the option list.
When you click ‘Search’ button the records matching the specified search criteria are displayed. For each record fetched by the system based on your query criteria, the following details are displayed:
You can view the individual record error details of the uploaded file in the ‘View Error Details’ (GIDFILOG) screen. From the summary screen (GISFILOG), double click the selected record to view the error details screen.
You can invoke View Error Details screen by typing ‘GIDFILOG’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
Based on the upload file name and process reference number, system displays the error details here:
Following field mapping details are also displayed
During the EOD batch run, GI EOD process also gets invoked at every stage. GI EOD process would in turn check whether all the required interfaces are processed at that stage or not.
This section contains the following topics:
GI EOD process checks if all the required interfaces are process at that stage. If any interface is not processed, system process these interface and if it’s a mandatory interface system would wait till it processed.
Note
If any mandatory interface is not processed before the respective stage then system would raise an error.
Based on the interface frequency information and GI Batch would publish the Run-Chart for the present day run. Also it archives the interface data. GI Batch runs after Mark TI.
The global variables and mask attributes used in the generic interface are explained here.
This section contains the following topics:
The global variables used in the generic interface are explained below:
The mask attributes used in the generic interface are explained below: