1.

Interface Communication Preferences

1.1. Description
The purpose of the Communication Preferences interface is to replicate changes made to customer level communication preference data for the primary borrower on a retail loan or lease in the FOCUS Application within the Siebel Application, and vice versa. In the FOCUS Application, Communication Preferences information is located in the Communication Prefs tab, and includes phone (home, work, mobile, pager, and fax), language and email. Corresponding Comments, which are primarily used to store information about authorized third parties for a given Financial Account, may also be updated at the time of a Communication Preference change. It is important to note that home and work phone numbers themselves cannot be edited in the Communication Prefs tab; rather, the CSR user has the ability to select one of these phone numbers as the primary method of contact using the radio buttons in the below screenshot. Home and work phone number updates are included in the garage address change functionality that is described in the Address Change Request section of this document.

FOCUS Application to Siebel The Communication Preferences interface will be based on a Communication Preference change in the FOCUS Application, as reflected in the FOCUS_CUSTOMER_PREF_DATA database table. For new Retail or Lease accounts, the FOCUS Application Communication Preference is defaulted to Phone (H) for the contact method and English for the language setting. Similar default settings for contact method will be applied to new Financial Accounts within the Siebel Application. For accounts with Communication Preferences set to the FOCUS Application defaults, a record does not exist in the FOCUS_CUSTOMER_PREF_DATA table. This record is created the first time a CSR clicks the Update button in the FOCUS Application Communication Prefs tab. It should be noted that a FOCUS Application error would be received upon clicking the Update button if no changes were made to the Communication Preference settings. As such, a record will not exist in the FOCUS_CUSTOMER_PREF_DATA table containing the original FOCUS Application default settings for Communication Preferences. For accounts with Communication Preferences not set to the FOCUS Application defaults, the existing record in the FOCUS_CUSTOMER_PREF_DATA table is updated with changes. Therefore, any Retail or Lease account will have one and only one record in this database table, which is repeatedly updated with changes to the Communication Preferences. The interface trigger will be initiated when a new record is generated or an update is made to an existing record in the FOCUS Application FOCUS_CUSTOMER_PREF_DATA database table. The result of the Communication Preferences interface to the Siebel Application will be a New Service Request record and a Contact Profile update.

Siebel to FOCUS Application The Communication Preferences interface will be based on a Communication Preference change in the Siebel Application, as reflected in the S_ SRV_REQ and S_ASSET_CON database tables. The interface trigger will be initiated when an update is made to an existing record in the Siebel Application S_SRV_REQ database table when the CSR puts the Communicaton Preference Service Request into a status of Submitted. The result of the Communication Preferences interface to the FOCUS Application will be a new or updated Communication Preference r ecord. Universal Application Network (UAN) The Communication Preferences interface will utilize Siebels UAN product for both directions of data flow: from the FOCUS Application to the Siebel Application and from the Siebel Application to the FOCUS Application. The Sync Service Request Business Integration Process (BIP) along with the Service Request Common object will be used for the integration of the Communication Preference data.

1.2.

Process Flow FOCUS Application to Siebel

TIBCO Initiation: Identify new or updated FOCUS database record Capture . appropriate data fields from the Communicaton Preference event . TIBCO Procedure: Transform FOCUS Communication Preference data into Siebel formatted records .

FOCUS Application Event: Update to FOCUS Communication Preferences. Result is an insert or update to focus_customer_pref_data.

Siebel
Service Request message Siebel Service Request Inbound Interface New Service Request Update Communication Preference

1.3.

Process Flow Siebel to FOCUS Application

Interface Initiation : Identify updated S _SRV_REQ database record. Capture appropriate data fields from the Communication Preference event . Siebel Service Request Outbound Interface Service Request message TIBCO Procedure: Transform Siebel Comm Pref message into FOCUS formatted data .

Siebel Application Event : New Service Request created to update the Communication Preference . Result is an insert to S _SRV_REQ and an updated to S _ASSET_CON.

FOCUS
Insert or Update focus_customer_pref_data

1.4.
Direction

Interface Details
Source Event Target Result Serialized Source Table Name
Yes FOCUS_CUSTOMER_PREF_DATA

Target Avg Frequency Operations Volume

Update Insert

Time

Communication New Service Request FOCUS App - Siebel Preference Update Contact Profile Insert or Update New Service Request New or Update Siebel - FOCUS App Communication Communication Preference Preference Update

325 Near Records Event-driven Real-time Daily TBD upon Near release of Event-driven Real-time R1A

Yes

S_SRV_REQ, S_ASSET_CON Update

1.5.
FOCUS App

Transformation Flow FOCUS Application to Siebel


(
W Transfor 3) TI ( ync ervice equest I ) Multi-thread Transfor to o on ublish Message to ueue Finish xception Yes Yes xception xception xception 10) iebel o unication reference is updated

1) CSR makes an update to the Communication Preference information of a primary customer in the FOCUS Application. Upon invocation of the Update button, changes are reflected in a new record or to an existing record on the FOCUS_CUSTOMER_PREF_DATA database table. 2) The interface is triggered by new records or updates to existing records in the FOCUS Application FOCUS_CUSTOMER_PREF_DATA database table. Data is extracted from the appropriate tables through a combination of FOCUS PL/SQL and TIBCO processing. Extracted data must include the social security number of the corresponding primary individual on the FOCUS Customer record. 3) TIBCO BW will transform the Communication Preference record into the appropriate common object format based on the Service Request schema included in the Sync Service Request UAN BIP. Upon successful transformation to common, TIBCO BW will then transform the message to the Siebel 7.7 specific schema for Service Requests, ensuring that the operation attribute is set to insert. 4) TIBCO BW determines if all user key, non-nullable and picklist values are populated appropriately for the Service Request. Validation should include the same social security number data quality analysis, as detailed in the Appendix of this document. Exception handling will be enabled to resolve field failures. 1.5) The resulting JMS message will be delivered to the Service Request queue for this interface. Siebel Service Request (CommPref) Inbound Interface gets the JMS message from the queue.
Formatted: Indent: Left: 0.75", Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 5 + Alignment: Left + Aligned at: 1" + Tab after: 1.25" + Indent at: 1.25", Tab stops: Not at 0.5" + 1.25"

  

9) iebel ervice equest is created

End

Siebel

6) iebel Financial ccount located?

7) iebel ontact located?

Yes

   

5) iebel ervice equest ( o ref) Inbound Interface gets essage

      

TIBCO

Transfor to iebel For at

TI

4) ll user key, non-nullable and picklist values satisfied?

 

"

    

   

2) o unication reference data extracted fro F pplication database through F processing and TI

 

       

    
1) o

updates unication references

(T

8) iebel lri ( ary ontact?

Yes

2.6) Siebel Service Request (CommPref) Inbound Interface locates the corresponding Siebel Financial Account record. Exception handling will be enabled to resolve an unidentified Financial Account record. 3.7) Siebel Service Request (CommPref) Inbound Interface locates the corresponding Siebel Contact record. Exception handling will be enabled to resolve an unidentified Contact record. 4.8) Siebel Service Request (CommPref) Inbound Interface confirms the Primary Contact record. Exception handling will be enabled to resolve a Contact record that is not primary. 5.9) Siebel Service Request (CommPref) Inbound Interface generates a new Siebel Service Request record on S_SRV_REQ. 6.10) Siebel Service Request (CommPref) Inbound Interface initiates an update to the Siebel Communication Preference record on S_ASSET_CON.

1.6.
1)

Transformation Flow Siebel to FOCUS Application

3) ervice equest JM essage published to the ervice equest queue; operation = update

W Transfor 4) TI ( ync ervice equest I ) Multi-thread Transfor to o on

TIBCO

Transfor to F

For at

Yes

Yes TI

ublish Message to ueue

Finish

1.1) CSR creates a Service Request in the Siebel Application to update the Communication Preference of the primary Contact on the Financial Account. Upon invocation of the Service Request Submit button, a new Service Request record is created on the S_SRV_REQ database table, and changes are reflected to an existing record on the S_ASSET_CON database table. 1.2) The interface is triggered by an update to arecord in the Siebel S_SRV_REQ database table.when the CSR puts the Communicaton Preference Service Request into a status of Submitted. Communication Preference data is extracted from the appropriate tables through Siebel workflow processing. 1.3) The Communication Preference record is transformed by the Siebel Service Request Outbound Interface into a JMS Service Request message and published to the Service Request queue. This message will be used for a functional update to an existing FOCUS Customer record. At a database level, the message will result in an insert or an update to an existing record in the FOCUS_CUSTOMER_PREF_DATA table.

FOCUS App

FOC S App (FCS) o

7a) F unication references data is inserted

End

2 00 ' )( '&

2 00 ' )( '&

xception

xception

5) ll user key, non-nullable and picklist values satisfied?

6) F usto er located?

CO (T C) o

2 00 ' )( '& #

0 ' )( '&

6 0 )( '& 0 00 ' 0

29 0

Siebel

Siebel (S

$ #

9 &)9 ) '

) 0 2

2) o ref data extracted fro database through iebel ervice equest utbound Interface orkflo processing.

3 3 & 1 )0 ) 2 00 '

creates a ervice equest to change o unication references. esult is a ne ervice equest record ( _ _ ) and an update to an ref record existing o ( _ T_ ).

8 &' 5 2 00))7 ) '51 1 16 4 ) ) )2 1 00 ' 1 )' )

7) F ref record exists? Yes

7b) F o unication references data is updated

Formatted: Numbered + Level: 2 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0.75" + Tab after: 1" + Indent at: 1", Tab stops: Not at 1"

1.4) TIBCO BW will transform a Communication Preference message into the appropriate common object format based on the Party schema included in the Sync Service Request UAN BIP. Upon successful transformation to common, TIBCO BW will then transform the message to the FOCUS Application specific schema for Customers. 1.5) TIBCO determines if all user key, non-nullable and picklist values are populated appropriately. Exception handling will be enabled to resolve field failures. 1.6) TIBCO locates the corresponding FOCUS Customer record. Exception handling will be enabled to resolve an unidentified Customer record. 1.7) TIBCO determines if a corresponding record exists on the FOCUS_CUSTOMER_PREF_DATA database table for the FOCUS Customer. 1.a. A new FOCUS Communication Preference record is inserted into the FOCUS_CUSTOMER_PREF_DATA database table. 1.b. An update is made to the existing FOCUS Communication Preference record on the FOCUS_CUSTOMER_PREF_DATA database table.
Formatted: Indent: Left: 1", Numbered + Level: 1 + Numbering Style: a, b, c, + Start at: 1 + Alignment: Left + Aligned at: 0.75" + Tab after: 1" + Indent at: 1", Tab stops: Not at 0.5" + 1"

1.7.

The following are key constraints and functional requirements for the Communication Preference interface: y Communication Preference updates made in the FOCUS Application will be visible in the Siebel Application in near real-time and vice versa. Communication Preferences are maintained for primary customers in the FOCUS Application and/or in the Siebel Application. No Communication Preferences are maintained for co-borrowers or other borrower types for a Financial Account in the FOCUS Application and/or in the Siebel Application. Changes to the information in the FOCUS Application Communication Prefs tab result in the creation of a new record or updates to an existing record in the FOCUS_CUSTOMER_PREF_DATA table. A FOCUS Customer with Communication Preferences not set to the FOCUS Application defaults will have one and only one record in the FOCUS_CUSTOMER_PREF_DATA table. The Communication Preferences interface does not account for historical combinations of BRANCH and ACCOUNT_NUMBER, resulting from a FOCUS branch transfer event. Since a Timestamp is not available in the FOCUS database table, the Siebel Service Request record and Contact Profile will be populated with the current system data and time.

JMS Message Dependency Since the Communication Preferences interface utilizes a single JMS message, there are no JMS message dependencies.

usiness Rules

FOCUS User Key Strategy The following fields are considered to uniquely identify a FOCUS Communication Preference entity and should remain static and non-nullable throughout the life of the entity. The FOCUS Application utilizes a concatenation of these fields to create a unique user key in accordance with the rules established for populating the primary key on the target FOCUS_CUSTOMER_PREF_DATA FOCUS database table.
Target Entity Target UK Table
FOCUS_CUSTOMER_PREF_DATA

Target UK Column
BRANCH

Description
Target column for the Branch Code. The Siebel data from S_ASSET.BRANCH_ID is utilized to resolve this key. Full Account Number, generated by an arrangement of Branch Code, Branch Region and Retail/Lease account number. The Siebel data from S_ASSET.X_ACCT_NUM is utilized to resolve this key. Target column containing the customer type. FOCUS defaults to 0 for Primary. The Siebel data from S_ASSET_CON.RELATION_TYPE_CD is used to resolve this key.

Communication Preference

FOCUS_CUSTOMER_PREF_DATA

ACCOUNT_NUMBER

FOCUS_CUSTOMER_PREF_DATA

CUSTOMER_TYPE

Siebel User Key Strategy The following fields are considered to uniquely identify a Siebel Financial Account, Contact and Service Request entity. These fields should remain static and nonnullable throughout the life of each entity. The Siebel Application utilizes a concatenation of these fields to create a unique user key in accordance with the rules establishe d for populating the primary key on the target S_ASSET_CON Siebel database table.
Target Entity Target UK Table Target UK Column Description
S_ORG_EXT Financial Account S_ASSET X_ACCT_NUM LOC Target column for the Branch code, used to resolve the BRANCH_ID foreign key on S_ASSET. The FOCUS data from FOCUS_CUSTOMER_PREF_DATA.BRANCH is utilized to resolve this key. Target column containing the unaltered FOCUS account number on a Financial Account. The FOCUS data from FOCUS_CUSTOMER_PREF_DATA.ACCOUNT_NUMBER is utilized to resolve this key. Populated with Social Security Number corresponding to the Contact record or a concatenated sequence of Branch, Account Number and Customer Type. Validation should include the same social security number data quality analysis, as detailed in the Appendix of this document. Target column for the Branch code, used to resolve the BRANCH_ID foreign key on S_ASSET. The FOCUS data from FOCUS_CUSTOMER_PREF_DATA.BRANCH is utilized to resolve this key. Target column containing the unaltered FOCUS account number on a Financial Account. The FOCUS data from FOCUS_CUSTOMER_PREF_DATA.ACCOUNT_NUMBER is utilized to resolve this key. Populated with Social Security Number corresponding to the Contact record or a concatenated sequence of Branch, Account Number and Customer Type. Validation should include the same social security number data quality analysis, as detailed in the Appendix o f this document.

Contact

S_CONTACT

PERSON_UID

S_ORG_EXT

LOC

Service Request

S_ASSET

X_ACCT_NUM

S_CONTACT

PERSON_UID

The Communication Preference user key strategies for FOCUS and Siebel do not account for historical combinations of BRANCH and ACCOUNT_NUMBER, resulting from a FOCUS branch transfer event. The Communication Preferences interface will translate the current FOCUS

Application values for BRANCH and ACCOUNT_NUMBER to the Siebel Application, and vice versa. Data Relationships A FOCUS Communication Preference record is related to a Siebel Financial Account through the FOCUS BRANCH and ACCOUNT_ NUMBER fields. In addition, a FOCUS Communication Preference record is related to a Siebel Contact through a combination of the Siebel Financial Account (FOCUS BRANCH and ACCOUNT_NUMBER fields), and the FOCUS SSN and CUSTOMER_TYPE fields. Finally, the Siebel Application is designed in such a way to track events, such as Communication Preference (or Contact Profile) changes. As a result, a FOCUS Communication Preference record is also related to a Siebel Service Request through the Siebel Financial Account and Contact records (FOCUS BRANCH, ACCOUNT_NUMBER, SSN and CUSTOMER_TYPE fields). For the Communication Preference interface, the TIBCO processing should apply the same data quality analysis for the social security number as it does for the Retail/Lease Acc ounts interface, as described in the Appendix of this document. In summary, the primary key for the Siebel Contact will either be the social security number if it passes the data quality analysis or a combination of the Financial Account Branch, Account Number and Customer Type if the social security number is invalid. The following ERD illustrates the databse tables and relationships associated with the Communication Preference information:
S_ORG_EXT (Branch) PK ROW_ID NAME (Branch Name) LOC ( ranch Code)

S_ASSET (Financial Account ) PK ROW_ID ASSET_NUM (Financial Account) BRANCH_ID (Branch) COMMENTS (Comments) X_ACCT_NUM (Account Number)

S_ASSET_CON (Financial Account Contact) PK ROW_ID S_CONTACT (Contact) PK ROW_ID PERSON_UID * FST_NAME (First Name) LAST_NAME (Last Name) MID_NAME (Middle Name) SOC_SECURITY_NUM (SSN) * SSN if valid or a combination of Branch, Account Number and Customer Type

FK1

FK3 ASSET_ID (Financial Account) FK4 CONTACT_ID (Contact) RELATION_TYPE_CD ATTRIB_34 (Preferred Contact Method) ATTRIB_35 (Pager Number) ATTRIB_36 (Fax Number) ATTRIB_37 (Mobile Number) ATTRIB_38 (Language) ATTRIB_47 (Email Address)

S_SRV_REQ (Service Request) PK ROW_ID SR_NUM (SR Number) ASSET_ID (Financial Account) CST_CON_ID (Contact)

FK1 FK2

Due to branch transfers, the FOCUS BRANCH and ACCOUNT_NUMBER Fields may change, thus affecting the data relationships. The data transferred through the Communication Preferences interface will need to make use of the approach for handling changes to Account and Branch numbers resulting from branch transfers. Namely, existing records affected by a branch transfer will require a supplementary conversion for updated Financial Account Numbers (concatenation of BRANCH and ACCOUNT_NUMBER fields). This additional conversion will be required in order for associated Communication Preference records to be successfully translated through the interface.

Picklist Value Fields The following Communication Preference fields are populated with constrained picklist values. When extracted from the data batch files they must satisfy the valid values detailed below.
Source Table.Field Target Table.Field Valid Values
E Email F Fax H Home M Mobile P Pager W Work E English S Spanish A Document language transformation required 0 Primary

FOCUS_CUSTOMER_PREF_DATA.PREF_PHONE

S_ASSET_CON.ATTRIB_34

FOCUS_CUSTOMER_PREF_DATA.LANGUAGE

S_ASSET_CON.ATTRIB_38

FOCUS_CUSTOMER_PREF_DATA.CUSTOMER_TYPE

S_ASSET_CON.RELATION_TYPE_CD

FOCUS Data Transformations The following Communication Preference fields require specific data transformations as they are transported from the FOCUS Application to the Siebel Application through the Communication Preference Interface.
Source Table
FOCUS_CUSTOMER_DATA FOCUS_CUSTOMER_PREF_DATA FOCUS_CUSTOMER_PREF_DATA FOCUS_CUSTOMER_PREF_DATA

Source Column
SSN BRANCH

Transformation

Transformed to be compatible with the validation of social security ACCOUNT_NUMBER number data, as detailed in the Appendix of this document. CUSTOMER_TYPE

Siebel Data Transformations The following Communication Preference fields require specific data transformations as they are transported from the Siebel Application to the FOCUS Application through the Communication Preference Interface.
Source Table
S_ASSET_CON S_ASSET_CON S_ASSET_CON

Source Column
ATTRIB_35 ATTRIB_36 ATTRIB_37

Transformation
Transformed to exactly 10 digits; value should be truncated where necessary. Transformed to exactly 10 digits; value should be truncated where necessary. Transformed to exactly 10 digits; value should be truncated where necessary.

Additional Resources For detailed FOCUS Application Communication Preference field descriptions, please refer to the Data Definition - Focus Customer Pref Data.xls file. For specific field-level mappings between the FOCUS Application and the Siebel Application, please refer to the Customer Pref& Privacy tab in the CLP R1a Detailed Data Mapping Document.xls file.