Overview
This operation supports returning theavailable transactions / arrangements that can be created on the contract. The type of transaction/arrangement that can be created ona contract depends on the product aswell.
| Traditional Product |
Non Traditional Product |
Annuities |
| Deposit Money (Once) |
|
Deposit Money (Once) |
| Transfer via Mail |
|
Transfer via Mail |
| Dollar cost Average |
|
Dollar cost Average |
| Automatic Rebalance |
|
Automatic Rebalance |
| One Time Withdrawal |
|
|
| EFT Draw Premium |
|
|
| Loan |
|
|
| Systematic Partial Withdrawal(Net) |
|
|
Technical Requirements
| TR ID# |
Technical Requirements |
| TR1 |
ACORDv2.36 shall be used to communicate.ACORD Tx 213 Get Available TransactionFor Contract havingtc=213” &transSubTypetc=”21300” should be used for getting the transaction/arrangement |
| TR2 |
Interface must always return an error code and desc in the event of a processing failure in addition to HTTP response code. |
| TR3 |
For a success the response for will provide for the transaction/arrangement details.The details of transaction/arrangement may change based on the product selected within the contract. |
Business Requirements
| BR ID# |
Business Requirements |
| BR1 |
The Get Available Transaction For Contract should provide the list of transaction/arrangement which can be applied on a contract. |
| BR2 |
The contract needs to be present in ALIP for the data to be returned. |
| BR3 |
Interface returns a list of funds based on the product associated with the contract, irrespective of the status of the contract. |
| BR4 |
Incase if the contract is inactive/suspended the interface will not provide any details for such contracts. |
| BR5 |
The transaction/arrangement list in the above table of section 5.1.1 will only be supported by the interface. |
Process Flow
Same as section 3.1.4
Impact on ALIP system
None
Assumptions
N/A
Dependencies
N/A
Request Data Elements
| Request Parameters |
Description |
Mandatory |
Allowed values |
| TXLife/UserAuthRequest/UserLoginName |
A username used for identifying the user from which the request has been initiated to the system |
N |
|
| TXLife/TXLifeRequest/OLifE/Holding/Policy/PolNumber |
A number which uniquely identifies a contract number within ALIP. |
Y |
|
Response Data Elements
Below table is the list of transactions which are returned within the response of this interface, based on the type of product selected irrespective of the status of the contract.
| Traditional Product |
|
Non Traditional Product |
Annuities |
| Deposit Money (Once) |
|
|
Deposit Money (Once) |
| Transfer via Mail |
|
|
Transfer via Mail |
| Dollar cost Average |
|
|
Dollar cost Average |
| Automatic Rebalance |
|
|
Automatic Rebalance |
| One Time Withdrawal |
|
|
|
| EFT Draw Premium |
|
|
|
| Systematic Partial Withdrawal(Net) |
|
|
|
| Loan |
|
|
|
| Initial Premium |
|
|
Initial Premium |
| Additional Premium |
|
|
|
| Free Look Transfer |
|
|
Free Look Transfer |
| UnPlanned Premium |
|
|
|
| Loan |
|
|
|
| Investment |
|
|
|
| Transfer |
|
|
|
Success/Error Handling
| Success |
Success Scenario Description |
Message Code |
Message Description |
Message Type |
Additional Comments |
| #1 |
The Get Available Transactionsforcontract call was successful with details being returned in the output |
1 |
Success |
Informational |
TXLife/TXLifeResponse/TransResult/ResultCode/@tc =1 |
| Error |
Error Scenario Description |
Message Code |
Message Description |
Message Type |
Additional Comments |
| #1 |
The Get Available Transactionsforcontract call was NOT successful due to a technical error or contract not found. |
5 |
Internal Error |
Informational |
TXLife/TXLifeResponse/TransResult/ResultCode/@tc =5 |