This interface provides the ability to receive various rates externally from the client and capture the data updates within Accenture Life Insurance Platform, which will invoke the AACE Application Programming Interface to add/update data in a CCL matrix.
Rates are configured using the matrix structure in AACE and each matrix may consist of one to many comma separated data files. Each data file will be stored in ALIP in a single Common Calculation Language Matrix, which consists of a set of rows and columns with “,” as the delimiter.
This interface also allows an update to the matrix configuration, if the data files contain more than the number of rows as specified by the matrix configuration.
This interface is applicable for all relevant products in ALIP wherever applicable.
The interface supports Partial and Full upload of matrix where, Partial Upload will only update the value for the rows which are part of incoming rate file and will not impact any other rows. In case of FULL upload, value for the rows which are not part of incoming file will be reset to zero or blank. This functionality must be in sync with CCL Matrix Import Functionality of ALIP.
| TR ID# | Technical Requirements | Interface Design Traceability | Test Case Traceability |
| TR1 | A batch command will be sent to ALIP by the client system, comprising of the name and path of the rates file. | ||
| TR2 | ALIP will import (add/update) the matrix configuration referenced by the rates file in the batch command. | ||
| TR3 | The status of the matrix add/update will be returned in the batch response. | ||
| TR4 | Any validation failure or failure while updating the matrix, like incoming file unreadable or malformed will render the processing as ‘Failed’ and will be returned in the batch response. | ||
| TR5 | Below validations will be performed for incoming csv file. a) Empty matrix should not be provided in inputb) No of columns in the incoming file should be correctc) Incoming file should contain headers. This validation will happen only if ALIP UI also does not support Rates Import without headers, If UI is supporting import without headers, interface will not perform this validation.d) Incoming matrix should exist in ALIP.e) Incoming matrix dimensions should be correct. |
| BR ID# | Business Requirements | Interface Design Traceability | Test Case Traceability |
| BR1 | The input will be a Comma Separated Value (csv) file containing the details of a single or multiple matrices . | ||
| BR2 | For incoming csv containing multiple matrices, ALIP will split the incoming csv to multiple csv files for each matrix, based on the grouping logic required, ALIP will then import each matrix csv file individually.Currently this split import is supported only for FixedAndCapRates, with grouping logic to split files based on unique combination of columns MarketIndex, Crediting Strategy and New/Renewal. | ||
| BR3 | If any of individual matrix file fails , all updates pertaining to that input file will be rolled back. (in case of multiple matrix processing) | ||
| BR4 | When additional rows and same number of columns are found, the matrix configuration is updated to additional data value cells, and the information would be added to existing data in the matrix. | ||
| BR5 | If the file location or file name does not exist, then the job request will fail with return code ‘19’ & job exit code value ‘INPUT_FILE_NOT_FOUND’. | ||
| BR6 | Original input csv file containing the job details will be renamed to have timestamp after successful completion of the job. |
The external system will post the delimited file containing the rates information, such that it is available on an ALIP internal location and send a trigger command to the ALIP queue.
ALIP will read the trigger command from its request queue, and trigger the Rates Upload interface processing.
If the input file location does not exist, then the job will fail with return code ‘19’ and job exit status as ‘INPUT_FILE_NOT_FOUND’.
If the incoming rate file is for fixed interest rate/cap rates, the input file is expected to contain data pertaining to multiple matrices. In this case, the interface will split the incoming CSV into multiple CSV files.
ALIP will perform the validations mentioned in TR5 on the incoming file.
If validation fails, an integration failure will be logged inside ALIP files and an error response will be sent back to alert production support, until the validation is successful for all records, the incoming file will not be processed.
If validation is successful, ALIP will use AACE’s matrix related API’s to perform the required import of the incoming matrix data into ALIP.
For fixed interest and cap rates, if any of the individual rate files fails during import, all rates that were imported to that point will be rollback. Needed information will be written to log files and an error response will be sent back to alert production support.
None
The correct rate matrix name should be provided inside the csv file matrix structure.
After successful import of matrix data, ALIP servers must be restarted for the changes to take effect.
In case of duplicate records with different rates for PARTIAL or FULL upload, the interface will upload the matrix with the latest value for the duplicate date. It is advised not to have such duplicate records in input file.
ALIP system strict matrix import policy should be reset to carry out addition of new rows to the matrix.
This interface should be tested with csv files as input, any other format testing and its behaviour is not yet assessed or documented.
N/A
Batch job will support default File System. Default File System Can be changed to AWS or SFTP File System if required using the below document
Sample Rate Upload Input Files
Sample Batch Command Request
Sample Batch Command Response
| Success | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | The Rates Upload interface was successful. | 0 | Success | Informational | This execution will return a batch job reply indicating Success. |
| Error | Error Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #2 | The Rates import execution was NOT successful due to technical errors | -1 | Internal Error | fatal | This execution will return a batch job reply indicating Technical Error |
| #3 | The Rates feed interface execution was NOT successful due to the incoming feed file being malformed /unreadable. | -1 | Internal Error | fatal | This execution will return a batch job reply indicating Technical Error |
| #4 | The Rates feed interface execution was not successful due to incorrect file location. | 1 | Internal Error | Fatal | This execution will return a batch job reply with return code 19 indication ‘Input file not found’. |
| #4 | The Rates feed interface execution was NOT successful due to incorrect dimension (i.e. incoming csv file matrix dimension is different from the one configured in ALIP.) | 1 | Internal Error | Fatal | This execution will return a batch job reply indicating Validation Error |
| #5 | Rate matrices file does not exist in defined location or path can’t be read. | -1 | Internal Error | Fatal | This execution will return a batch job reply indicating Technical Error |
| #6 | Import of any of the individual csv files (That were split) pertaining to Fixed interest/Cap Rate failed. | -1 | Internal Error | Fatal | This execution will return a batch job reply indicating Technical Error |