Client Inbound Interface

In this section:

• Client Data Loading (Main)
  • Client (Main) Data Loading Example
• Client Addresses Data Loading
  • Client Address - Single Address Example
  • Client Address - Multiple Address Example
• Client Relationship Data Loading
  • Client Relationship - Single Relationship Example
  • Client Relationship - Multi Relationship Example

Overview

The Client inbound interface allows loading and updating the data in the following database tables:

• RULESDBO.CLIENT
• RULESDBO.CLIENT_ADDRESS
• RULESDBO.CLIENT_RELATIONSHIPS
• RULESDBO.INSTITUTION (optional)
• RULESDBO.INDIVIDUAL (optional)
• RULESDBO.CLIENT_RELATIONSHIP_DETAIL (optional)

The format of the incoming message is EagleML.

Stream Logic

Client inbound interface allows loading or updating data in CLIENT tables. Send an EagleML message to the eagle_ml-2-0_default_in_xml_reference stream to do that.

Loading the Client (main) Data into the Database

The data from the main section of the EagleML message (that is, all elements from EagleML/referenceTransaction/client complex node except clientAddress and clientRelationship elements) are loading into RULESDBO.CLIENT, RULESDBO.INSTITUTION and RULESDBO.INDIVIDUAL database tables.

Loading the Client Address Data into the Database

The data from the Client Address section of EagleML message (that is, all elements from EagleML/referenceTransaction/client/clientAddress complex node) are loading into RULESDBO.CLIENT_ADDRESS database table.

Loading the Client Relationship data into the Database

The data from the Client Relationship section of EagleML message (that is, all elements from EagleML/referenceTransaction/client/clientRelationship complex node) are loading into RULESDBO.CLIENT_RELATIONSHIPS and RULESDBO.CLIENT_RELATIONSHIP_DETAIL database tables.