Extract Structural Changes
Overview
We are announcing upcoming structural changes to three primary data extracts, Cus_BenflOwnDetail (EXTCFFBEN), Cust_IdVerifyDetail (EXTCFIDVER), and SafeDepAcctHist (EXTSDHIST). These modifications are designed to enhance data integrity and processing efficiency and will introduce breaking changes to the record keys consumed by external systems.
These changes will affect data processing on both our core systems: Silverlake and CIF20/20.
Cus_BenflOwnDetail (EXTCFFBEN) Changes
The underlying CFFBENV2 view will be altered on both the SilverLake and CIF20/20 systems to include the row ID field.
Record Key Modification (ACTION REQUIRED)
The record key for the Cus_BenflOwnDetail (EXTCFFBEN) extract will be modified by adding a new field. Developers must update their data consumption logic to incorporate this new key component.
| Current Record Key Fields | Adjusted Record Key Fields (New Key) |
|---|---|
| CIF Number | CIF Number |
| ID Number | ID Number |
| ID Type | ID Type |
| Record Number (New Key Component) |
Cust_IdVerifyDetail (EXTCFIDVER) Changes
The structure of the Cust_IdVerifyDetail (EXTCFIDVER) extract will be modified to include a new field that will be incorporated into the record key.
Record Key Modification (ACTION REQUIRED)
The record key for the Cust_IdVerifyDetail (EXTCFIDVER) extract will be modified. Developers must update their data consumption logic to incorporate this new key component.
| Current Record Key Fields | Adjusted Record Key Fields (New Key) |
|---|---|
| CIF Number | CIF Number |
| Owner ID Number | Owner ID Number |
| Owner ID Type | Owner ID Type |
| ID Code | ID Code |
| Record Type | Record Type |
| ID Number (New Key Component) |
SafeDepAcctHist (EXTSDHIST) Changes
The SafeDepAcctHist (EXTSDHIST) extract will undergo a critical change to how its unique record key fields, SrcKey and HistRecId, are populated.
Record Key Derivation Modification (ACTION REQUIRED)
The derivation logic for the SrcKey and HistRecId fields is changing to use a reliable, unique identity column instead of the relative record number.
| Current Key Derivation Logic | **New Key Derivation Logic |
|---|---|
| $\text{AcctID} + ‘B’ + \text{Relative Record Number}$ | $\text{AcctID} + ‘B’ + \text{Identity Column Value}$ |
| Note: Relative Record Number is a sequential, non-guaranteed unique index. | Note: The Identity Column is a Big Integer data type guaranteed to be unique per record, ensuring data uniqueness. |
Developer Action and Synchronization Requirements
Mandatory Logic Update
All consuming systems must update their logic to handle the new key components and derivation logic for all three extracts (EXTCFFBEN, EXTCFIDVER, and EXTSDHIST). The update to EXTSDHIST requires changing how the SrcKey and HistRecId fields are generated or validated.
Data Synchronization Requirement
Upon the deployment of this new release, a new full set of extracts will be required to ensure your systems have the complete, updated data structure and key identifiers. This is a mandatory step for synchronization.
We anticipate running an ad-hoc full generation outside of the normal weekly schedule to provide this initial set of synchronized data. Details on the exact date and time of the deployment and the subsequent ad-hoc full extract run will be communicated via this portal.
ODISvcCred
There is a change regarding the ODISvcCred message response that will be implemented with the new version, ODI vNext. The message contract has not changed but information previously found in the response may no longer be provided. The ServerIPAddr and SQLInstcName elements may no longer contain IP addresses or SQL instance names. The primary reason for the change is due to the use of SQL Availability Groups (AG), which will provide High Availability services for the ODI data.
If SQL AG is present for the environment in use, the SQLInstcName element will be returned in the response but will be empty. If SQL AG is not used, the instance name value will be returned.