Case Conditions

5
Supporting Regulatory Enterprise Credit Risk Reporting Audited and optimize all legacy SQL-table creation code by developing a CASE-Condition DB with OCC compliant metrics, across all consumer credit products (Card, UNS, Auto, Small Business, International, MTG, and HE). Created an EG 4.2 reporting system of specific CASE-Condition and aliases that helped establish a “common coded definition” across the enterprise. These defined key metrics (outstanding balance, active/open accounts, APR- outstanding balances, and OCC indicators) were collected monthly across all consumer credit product origination and portfolio tables. Produced optimized re-writes of production SQL resulting in up to 80% reduction in runtime and spool space utilization.

Transcript of Case Conditions

Page 1: Case Conditions

Supporting Regulatory Enterprise Credit

Risk Reporting –

• Audited and optimize all legacy SQL-table creation code by developing a CASE-Condition DB with OCC compliant metrics, across all consumer credit products (Card, UNS, Auto, Small Business, International, MTG, and HE). Created an EG 4.2 reporting system of specific CASE-Condition and aliases that helped establish a “common coded definition” across the enterprise. These defined key metrics (outstanding balance, active/open accounts, APR-outstanding balances, and OCC indicators) were collected monthly across all consumer credit product origination and portfolio tables. Produced optimized re-writes of production SQL resulting in up to 80% reduction in runtime and spool space utilization.

Page 2: Case Conditions

Add to Case Definition XLS, EVERY case condition in EVERY Table creation

Complex Case Conditions can span several lines, with other variables NOT filled down

Page 3: Case Conditions

Open NEW CASE Report EG and Run Import Data

Page 4: Case Conditions

Run Blank Fill which displays a prompt window from which to choose a metric

Page 5: Case Conditions