Download Interface User Manual - Oracle Documentation

8.2
FCIS – AWD Interface
At the end of a day’s batch processing, Oracle FLEXCUBE Investor Servicing will produce a
file which contains all the transactions that have failed validation criteria. The FCIS – AWD
Interface will assign a unique error code for each of the failed transactions and pass the file
to another external system. This external system will translate the error codes into AWD
Worktype and produces an AWD/RIP control file for AWD/RIP.
8.2.1
Maintaining Interface Specific Details
You need to maintain the external system AWD in the FCIS Data Mapping Maintenance
screen with the code description as ERROR CODE. Consequently, the file that will be sent to
AWD by FLEXCUBE Investor Services will have the header ‘AWD’.
Refer to the section ‘Maintaining Data Mapping’ in the chapter ‘Maintaining System
Parameters’ for further details.
8.2.2
Interface Attributes
The FCIS – AWD Interface has the following attributes:
8.2.3
Trigger
EOD Activity
Transport Type
File System
File Type
Delimited
Header Row
No
Record Separator
New Line Character
Field Separator
Comma
Process Workflow
The FCIS - AWD interface will fetch all the allocation errors that have occurred on transactions
after all the validations. The interface will then transfer a file with the details in the required
format. The interface will also provide the subscriptions, redemptions and income distributions
for which the bank details are unverified.
8.2.4
File Format for FCIS – AWD Interface
The file which contains the errors that have occurred on transactions will be in the following
format:
Field Name
Data Type
Details
Error Code
Number
The FCIS error code will be translated as per the data
mapping maintenance.
Account Number
Character
The unit holder ID of the transaction.
Fund id
Character
The fund ID of the transaction.
Account Group
No
Character
Product ID of the transaction. The value will be ‘UT’ if
it is a unit trust transaction.
8-2