Client Addresses Data Loading
This section describes loading data into the RULESDBO.CLIENT_ADDRESS DB table.
Loading into the specified table occurs from all elements in the EagleML/referenceTransaction/client/clientAddress node.
Address Type Element
The Client address can be one of three types:
'Home' ('HOM')Â
'Business' ('BUS')
'Wire Profile'
These values are valid for the database field RULESDBO.CLIENT_ADDRESS.ADDRESS_TYPE (which is mapped from the EagleML/referenseTransaction/client/clientAddress/addressType element of the incoming file).
Insert/Update Modes
In case of loading (INSERT mode) a new row into the RULESDBO.CLIENT_ADDRESS database table, the set of values below should be unique and should not be present in the database table.
In case of updating (UPDATE mode) the existing row into the RULESDBO.CLIENT_ADDRESS database table, the set of values below should be should be unchained in the database table.
The set of values (client address section of the EagleML message, RULESDBO.CLIENT_ADDRESS database table):
EagleML/referenceTransaction/client/clientId (the value of client instance is calculated by client instance and mapped into RULESDBO.CLIENT_ADDRESS.CLIENT_INST database field);
EagleML/referenceTransaction/client/clientAddress/caInstance (optional value. If not present, the value of element caInstance is calculated or generated and mapped into the RULESDBO.CLIENT_ADDRESS.INSTANCE database field);
EagleML/referenceTransaction/client/clientAddress/addressType (mapped into the RULESDBO.CLIENT_ADDRESS.ADDRESS_TYPE database field);
EagleML/referenceTransaction/client/effectiveDate (mapped into the RULESDBO.CLIENT_ADDRESS.EFFECTIVE_DATE database field).
The other fields in this database table can take on any values.
Examples
The following examples are available:
An example containing Client section and one Address section and an example containing Client section and  multiple Address sections.