This Interface will provide the ability to fetch the fund performace for the given contract and date range.
This Interface is an inbound call and is applicable for any product type in ALIP.
| TR ID# | Technical Requirements |
| TR1 | ACORDv2.36 Tx 233 “Holding Product Inquiry Transaction tc=233” is being used for getting the available funds and its details. |
| TR2 | The interface would perform the XSD validation of the input XML for mandatory field check. |
| TR3 | The interface should convert the input ACORD XML to ALIP XML format. |
| TR4 | The interface should invoke different ALIP API to fetch the fund performance. |
| TR5 | Interface must always return an error code and desc in the event of a processing failure in addition to HTTP response code. |
| TR6 | For a success, the response will provide the available funds and its details. |
| TR7 | API will be accessed through JMS/REST/ SOAP |
| TR8 | If Interface receives a duplicate record based on ‘TransRefGUID’, then ALIP will return a Duplicate Record Found Message to ESB |
| BR ID# | Business Requirements |
| BR1 | The interface should provide the list of funds and details for the given contract as per response data fields given in the section |
| BR2 | Interface returns a list of funds based on the product associated with the contract, irrespective of the status of the contract. |
| BR3 | The contract needs to be present in ALIP for the data to be returned. |
Following is the high-level description of Fund Performance integration process:
The external system would fire the REST URL containing the input parameters for retrieving the available funds on the request queue.
ALIP webadapters would pick up, process the message, convert it into XML format, and posts it onto the ALIP request queue.
ALIP process server will pick up the message, convert from ACORD to the canonical format, perform the necessary XSD validations.
Post the necessary validations, it would invoke the necessary ALIP APIs to retrieve the necessary fund performance data from the database.
The fund performance data, since it is a case of a “GET” request, would be generated in XML format, converted to ACORD format, and sent back to the REST layer
Here, it would be further converted back into the final JSON output format and returned back to the external system.
None
The interface will not do any business validations for data being received from external systems.
This interface is not going to insert or update any records in ALIP core databases, except only the standard integration tracking tables.
N/A
N/A
| No. | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | The Fund Performance interface executed successfully. | 1 | Success | Informational | Fund details for the given contract present in the output. |
| Error | Error Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | Generic System Failure due to technical errors. | 100 | Internal Server Error | Fatal | 500 |
| #2 | XSD validation failure or field level mandatory failure or allowable value check failure | 100 | XSD Validation Error | Failure | 100 |
| #3 | Contract number does not exist in ALIP. | 100 | Internal Error | Failure | 100 |
| #4 | End date given in the input is greater than today’s date. | 100 | Internal Error | Failure | 100 |
| #5 | Start date is previous to issue date. | 100 | Internal Error | Failure | 100 |