Aid Cri Appl V0.1

Document ID : CRI AID
Document Owner : PS Team

Version Number : 1.0
Application Information Document
Credit Risk Interface/Citi Risk Approvals (CRI)

Version 1.0
CRI
Application Information Document: Version: 0.1
Document Control Section
Version Number: 1.0
Author
Role Name
L2 & L3 Production Support Analyst Mohit Gupta
Delivery Leads
Role Name
IBM Offshore Delivery Manager Anu Aggarwal
IBM Onshore Delivery Manager Subrata Mondal
Reviewer
Role Name
L2 & L3 Production Lead Yogesh Agrawal
Revision History
Version Description of Changes Author Issue Date

#
1.0 Initial IBM L2 & L3 Support 27 JUL 2016
team
IBM Global Services Page 2 of 28

CRI
TABLE OF CONTENTS
1. OBJECTIVES............................................................................................................................................. 4
2. TERMINOLOGY AND ACRONYMS....................................................................................................... 5
3. APPLICATION OVERVIEW.................................................................................................................... 6
4. APPLICATION PLATFORM.................................................................................................................... 7
4.1 CRI APPLICATION PLATFORM.................................................................................................................... 7
4.2 TOOLS USED............................................................................................................................................. 7
4.3 CONFIGURATION MANAGEMENT................................................................................................................ 7
5. APPLICATION STRUCTURE.................................................................................................................. 8
5.1 CREDIT APPROVAL......................................................................................................................................
5.2 CREDIT MEMO............................................................................................................................................
5.3 OPERATION MEMO......................................................................................................................................
5.4 CLASSIFIED CREDIT REPORT........................................................................................................................
5.5 GLOBAL CLASSIFIED CREDIT REPORT..........................................................................................................
5.6 GENERAL MEMO.........................................................................................................................................
5.7 INDUSTRY CREDIT REVIEW.........................................................................................................................
5.8 CLIENT ON BOARDING................................................................................................................................
5.9 REPORTS.....................................................................................................................................................
6 DATABASES AND FILES....................................................................................................................... 14
6.1 INTERNAL DATA FLOW............................................................................................................................ 14
6.2 SQL JOBS............................................................................................................................................... 14
6.3 USER INTERFACES................................................................................................................................... 14
6.4 SERVER DETAILS............................................................................................................................... 14
7 APPLICATION HISTORY...................................................................................................................... 15
7.1 TYPICAL PROBLEMS:............................................................................................................................... 15
7.2 RELEASE HISTORY:................................................................................................................................. 15
7.3 CONTACTS.............................................................................................................................................. 15
8 REFERENCE DOCUMENTS.................................................................................................................. 16

CRI
1. OBJECTIVES
The objective of the Application Information Document (AID) is to provide members of the
delivery team with an overview of the Citi Risk Approval (CRI) application. The AID describes
the function, structure, configuration and the technical environment of the application. This
document refers to any existing related documentation.
The delivery team will keep the AID throughout the life of the CRI application.

CRI
2. TERMINOLOGY AND ACRONYMS
Acronyms and terminology specifically used in this document are described below. Other
acronyms commonly used can be found in the ASCP.
Terminology / Definition
Acronyms
1 AID Application Information Document

2 CRI Credit Risk Interface/CitiRisk Approvals
3 ANL Analyst
4 RM Relationship Manager
5 PP Package Preparation
6 CA Credit Approval

CRI
3. APPLICATION OVERVIEW
CRI (Credit Risk Interface) is an application that provides users with an online,
electronically-based system of built-in checks and balances for reducing the risks
associated with processing of credit approvals.
CRI expedites the process of creating, circulating, and approving credit for global
customers across diverse industries, while providing a tracking mechanism and security
features across countries around the world.
The Citi Risk Credit Risk Interface (CRI) is intended to address the limitations of current
financial analysis business processes, in order to more effectively support Credit Risk
Management’s business strategy for maximizing efficiencies and reducing overall costs
and losses
CSI App ID App Name
147581 CRI

CRI
4. APPLICATION PLATFORM
4.1 CRI Application Platform
Server Name Server Type Purpose

Not yet received
Dev SN group:
4.2 Tools Used
The tools that are used for supporting the CDM application are:
 Eclipse
 Oracle Client
 SQL Developer
 Aqua Studio
 Putty
 WinSCP
 TIBCO-iProcess
 SVN Plugins
 JDK 1.6
 Adobe Flex Builder 3
 Flex Debugger
 Tectia – SSH Terminal
 Tectia – Secure File Transfer
 TIBCO – BW Designer
4.3 Configuration Management

CRI
5. APPLICATION STRUCTURE
Introduction to Credit risk management and CePac:
Credit risk refers to the probability of loss due to a borrower’s failure to make payments on any
type of debt. Credit risk management, meanwhile, is the practice of mitigating those losses by
understanding the adequacy of both a bank’s capital and loan loss reserves at any given time – a
process that has long been a challenge for financial institutions.
The global financial crisis – and the credit crunch that followed – put credit risk management
into the regulatory spotlight. As a result, regulators began to demand more transparency. They
wanted to know that a bank has thorough knowledge of customers and their associated credit
risk. And new Basel III regulations will create an even bigger regulatory burden for banks.
To comply with the more stringent regulatory requirements and absorb the higher capital costs
for credit risk, many banks are overhauling their approaches to credit risk. But banks who view
this as strictly a compliance exercise are being short-sighted. Better credit risk management also
presents an opportunity to greatly improve overall performance and secure a competitive advan-
tage. To achieve Credit Risk Management Citi Bank is using CRI application.
The purpose of the Credit Memo is for all users to prepare, circulate, approve, notify and
thereafter lodge a memo to the Customer File.
Credit Risk Interface
CRI (Credit Risk Interface) is an application that provides users with an online, electronically-
based system of built-in checks and balances for reducing the risks associated with processing
credit approvals. CRI expedites the process of creating, circulating, and approving credit for
global customers across diverse industries, while providing a tracking mechanism and security
features across countries around the world. CRI, which runs under the Citivision platform, pro-
vides a mechanism that centralizes and circulates all documents related to the credit approval
process.
CRI consist of many modules.
CePAC: This module has below mentioned flows.
Credit Approval
Credit Memo
Operation Memo
Classified Credit Report
Global Classified Credit Report

CRI
General Memo
Industry Credit Review
Client On boarding
Reports
SDC Credit Approval (Except SG & KR)
O2 Credit Approval (Asia – SG alone)
ADMIN
Customer Profile
Entity Profile
User Profile
5.1 Credit Approval
5.1.1 Introduction
The ApplicationThis workflow help Bank to identify risk associated with client’s loan.
There iares multiple type of workflow for Credit Approval. The CA workflow can be
initiated as a result of different business triggers. There may be different types of
customers and for each customer a workflow is initiated in CRI. User data is saved in
RAPIDITS and LDAP. Important customer data is stored in Cepaac table in Oracle.
5.1.2 Workflow
The following table provides descriptions of the various types of credit approvals
workflows:

CRI
Type of Credit
Approval Description
Initial Created by the Relationship Manager (RM) or an Analyst for a
new customer. Typically the new customer is loaded into CRI
from the source credit system (RAPID, CACLS, or CRMS).
However, due to normal processing delays, it is possible that
this data could be unavailable. If this happens, the CRMS
team can create a temporary customer for the RM/Analyst to
start work on the CA.
Annual Performed on a predetermined basis and is initiated
Review automatically by CRI based on predefined parameters set up in
CA the Entity and Customer Profile. Users can also create the
Annual Review CA manually on the system.
Interim Created by the RM/Analyst whenever a change in credit
facilities is required.
Extension Created by the RM/Analyst whenever the time period of
approved credit limit needs to be extended. The Extension CA
can also be initiated automatically by CRI based on predefined
parameters set up in the Entity Profile.
5.5.3 Functional Description
Technology Base of CRI:
i. It is a rich application with a front end of the java.

ii. The middle layer consists of java services using spring, jrules, cognos. The stored
procedures are called in by Java services.
iii. The application uses Oracle database to store all the customer relates data component
data and the application data.
iv. The batch jobs for downstream system flow are based and written in using Shell Script.
UI of CRI:
i. The first screen of CRI application is having CRI Dashboard.

ii. The dashboard is divided into two panels:
a) First panel consists of the list of the customers
b) Second Panel consists of snapshots and captured information about selected
customers.
iii The menu consists of different functional that are available.
iv Each and every customer has entitlements which are access specific. The entitlements are
used for generating the ratings.
The Credit Approval Process:

CRI
The Credit Approval (CA) process involves triggering, preparation, discussion, approval,
notification, and lodging of CAs. The CA process consists of the following phases:
5.5.4 Creation of Credit Approval workflow

There are 4 types of Credit approvals.
Select any one of the following types of Credit Approvals:
1. CA-Annual Review

CRI
2. CA-Initial
3. CA-Extension

CRI
4. CA-Interim

CRI
The Create CA screen displays the following:
 List of customers associated with the user via the user’s Primary Entity
 Search facility that enables you to search for a customer using Entities to which a user is
associated (further filterable by Country/ies within the Entity), Customer Name,
Customer ID, GFCID, or Customer Type (Group, Individual or Subsidiary)
 Click the name of the customer to display on the CA screen.
 Click Save. A work item is created in the To Do list of every Analyst / RM (including
backups) associated with that customer.
5.1.5 Tables Information in DB

There are many important tables related to CA.
For Ex: cepoaac_customer
credit_documents
customer_status_history
country_documents
wf_process,wf_node
wf_item,
ceemea_ca
ca_face.
5.1.6 Frequentl Used Queries
select * from cepaac_customers /*customer related table*/

select * from credit_documents /*workflow related table*/
select * from country_documents /*workflow related table*/
select * from credit_approvals /*Credit approval workflow related table*/
select * from signers /*List of signers selected in the workflow*/
select * from signer_status_histories /*Signer status history related table*/
select * from document_status_history /*workflow status history*/
select * from document_edit_history /*workflow Edit history*/
select * from wf_process where doc_id=''; /*workflow intray distribution related table*/
select * from wf_node where process_id=''; /*workflow intray distribution related
table*/
select * from wf_item where process_id=''; /*workflow intray distribution related
table*/
select * from ceemea_ca /*RAPID CAFACE flowsn to CRI and status*/
select * from ca_face /*CAFACE related informaiton in Detail*/
select * from eca_approved /*CA utilised in the workflow / releaseing related table*/
select * from dba_jobs /*DBA jobs*/
select * from comments /*Comments shared in the workflow on each status*/
select * from mailerdata -- 3 months data only avaialble

CRI
select * from cfs_document_link /*CFS link related table*/

select * from cfs_document /*CFS document stored table*/
select * from rits_user_info-------to check user profile
5.2 Credit Memo
5.3 Operation Memo
5.3.1 Introduction
Operation Memo is a kind of workflow or type of discussion which is created when there
is any exception for credit or non credit systems.
For each such exception OT(offering ticket) or Availment tickets is created in flex cube
system, CRI handles the OT only.
Whenever OT is created in Flex cube, it flows to CRI and then OT will be attached to a
workflow.
5.3.2 Operations Memo– OT approval Workflow
5.3.3 CRI Flow for OT Workflow approval

CRI
• There are 7 possible flows within CRI that can be setup based on country requirement
• Each of these flows can be modified to exclude the stage between Signers and Operations
Operations  Signers  RA/RM  Operations

Credit Credit
Operations  Admin  Signers  Admin  Operations
Credit Credit
Operations  Admin  RA/RM  Signers  Admin  Operations
Credit Credit
Operations  Admin  RA/RM  Credit Admin  Signers  Admin  Operations
Credit
Operations  Signers  Admin  Operations
Operations  Signers  Operations
5.3.4 Implementation requirements and challenges
i. One-time setup of User profile setup

ii. Country to decide which Ops Memo workflow suits them
iii. OLECA configuration to sent OT to CRI for Approval
5.3.5 How to create the Ops Memo
Two types of workflow:
1. Credit Workflow Process:
OPS [Create the workflow] Forward to CRMS CRMS (if required CRMS can transfer to
RASA Submit the workflow to Signers (One approved)-[workflow comes to] CRMS
IntrayForward to OPS OPS will complete the workflow
2. Non Credit Workflow Process:
OPS Create the workflow Forward to RASA  Submit the workflow to Signers (One
approved)-[workflow comes to] CRMS IntrayForward to OPS OPS will complete the
workflow

CRI

CRI

CRI
 Viewing the Over Limit Ticket in CRI that was generated by OLECA at the time of
earmarking
5.3.6 Acronyms in OPS Memo:

CRI
FP - Forward to CRMS
FRA - Forward to RASA
FAU – Forward to Author
5.3.5 Tables for OPS memo workflow process:
select * from intra_ot_at_reg

select * from credit_document_table
select * from operation_memo_retdet
select * from operation_memo
select * from county_user_roles
select * from document_status_history
select * from credit_documents
select * from country_documents
select * from entity
5.3.6 Admin Tables:
SELECT * FROM OPS_ADDITIONAL_MAILINFO

SELECT * FROMOPS_BUSINESS_UNITS
SELECT * FROMOPS_BUS_UNITS_ASIA
SELECT * FROMOPS_BUS_UNITS_RAPID
SELECT * FROMOPS_ENTITY_POST_APROVAL
SELECT * FROMOPS_EXTN_EQUITY
SELECT * FROMOPS_MAILNOTIFICATION_RULES
SELECT * FROMOPS_MAP_WORKGROUP
SELECT * FROMOPS_PRE_MAILERDATA
SELECT * FROMOPS_PROCESSING_COUNTRY

CRI
5.4 Classified Credit Report
5.4.1 Introduction
This workflow is used to change a customer's classification or to periodically review the
status of a classified name.The Classified Credit Report (CCR) process involves
triggering, preparation, approval, notification and lodging of CCRs
5.4.2 Workflow
5.4.3 Functional Description
Classified Credit Report :

This workflow is used to change a customer's classification or to periodically review the
status of a classified name .The Classified Credit Report (CCR) process involves
triggering, preparation, approval, notification and lodging of CCRs.
Types of CCR:
1. New Classification
2. Re-classification
3. De-classification
4. Review
5.4.4 Creation of CCR Workflow
Creation of CCR workflows by batch is based on the following conditions.

Customer level parameters:
i. Customer should be active in CRI.
ii. Customer classification
 Should not be 'P'
 Should not be ‘PWL’, since as of now no logic in it.
 If the Overridden classification in CRI is empty, classification value will be
taken from RAPID

CRI
 If the classification is 'SM', CCRs will be created based on the 'Quarter Indi-
cator'
 If the classification is 'L', CCRs will be created only in January and July
months
 If the classification is other than 'SM' and 'L', CCRs will always be created ir-
respective of 'Quarter Indicator'
iii. CCR required indicator should be 'Yes'
iv. De-activate/Cancel automatic trigger should be 'No'
v. Approval code should not be 'Approved Elseware'
 Note: Source Credit Systems, CACLS and CRMS alone will continue to feed
Old Classification Codes into CRI, only RAPID will feed New Classification
Codes into CRI.
Batch parameters :
The CCR trigger batch is scheduled to run on first day of every month.
147581_SDC_AP_CCS_Create
5.4.5 Tables Information in DB & Frequently Used Queries

**Generic Workflow tables:

CRI
----------------------------
select * from credit_documents;

select * from country_documents;
select * from wf_process
select * from wf_node
select * from wf_item
select * from document_status_history ;
select * from document_edit_history;
**Lodging Files
-------------------
select * from cfs_document;
select * from cfs_document_link ;
**CCR DETAILS:
----------------
select * from CCR_EXPOSURE_DETAILS;--drct,cntgnt,psle,net exposure
select * from CCR_FACILITY_DETAILS;--cdoc_id,current and last ccr,security type details
select * from CCR_OBLIGOR_CLASSIFICATION_vw;--classification,doc_id,collateral value
and ctry_code
select * from CCR_SUMMARY_HISTORY_VW;--SUMMARY DETAILS(classificatioN)
select * from CCS_FACILITY;--
DOC_ID,FACIL_DESC,CLASSIFIACATION,AMOOUNT,OUTSTANDING,CUSTOMER_N
AME
select * from CCS_NEXT_ACTION_PLANS;--DOC_ID,PLAN,TARGET
DATE,CNTRY_CODE
select * from CCS_PREV_ACTION_PLANS;--
DOC_ID,PLAN,PERFORMANCE,TARGET_DATE
select * from CCS_SUBSIDIARIES;--CCS_CD_CDOC_ID,CC_ID,PROPOSED
CLASSIFICATION DETAILS
select * from CLASSIFIED_CREDIT_SUMMARY;--
CD_CDOC_ID,CCS_TYPE,APPROVING UNIT
select * from CLASSIFIED_CREDIT_SUPPORT_INFO;--FACILITY DETAILS
select * from crms_classified;--CCR FACILITY DETAILS
5.4.6 CCR – ReturnToAuthor Button Issue
For the Classified Credit Review(CCR) Workflow, The following basic actions are required to
get ReturnToAuthor Button.
5.4.6.1 By Attaching the Facilites:
When the workflow status will be “PendingSubmission”.

CRI
CRMS has to attach some facilities by clicking on the button 'Request Facility Info’. Once the
CRMS has saved after facilities attached, Then the Button 'Return To Author' will appear.
There are two different facility values available i.e direct facilities and adverse facilities. If the
data is available in either one of these then the return to author will be enabled once the user
saves the facility info.
Following are the steps:
i. Click on the button 'Request Facility Info'

ii. Attach the facilities and save the facility Screen
iii. Save the CCR Screen
iv. Then 'Return to Author' button gets appear.
5.4.6.2 Month End Indicators for Review Type CCR:
There are two types of CCR

i. Review Type CCR
ii. New Classification CCR
For direct and Adverse CRMS facility value, Month End indicators should be Y only for
“Review” type CCR to get the button
5.4.7 Use Cases:
Scenario:
Many of the recent VT’s has a issue describing “ReturnToAuthor” button is available after
attaching the facilities.
Solution 1:
Following are scenarios in which ReturnToAuthor button available:
CRI uses the Credit Engine View cri_v_crms_classified to get the facilities attached by the
customers. If there were no facilities feeding from RAPID for that particular entity, then the
button will not be available
When analyzed in CRI tables(CRMS_CLASSIFIED AND

CLASSIFIED_CREDIT_SUPPORT_INFO),There are no facilities available in CRI.
When checked with RAPID, there is no facilities for the Particular Entity (for which the
customer creating workflow) feeding to CRI from Credit Engine.
Solution 2 :( Based on Month End Indicator)

The Month end indicator attached to customer, facility is flowing into CRI from
RAPID/CREDIT ENGINE view named cri_v_crms_classified. The column name is
“MONTHEND_IND”. While attaching facilities to REVIEW type CCR in CRI, CRI checks for
the facilities for the particular customer with month end indicator as ON

CRI
(MONTHEND_IND=’Y’). For any entity, If there is no facility downloaded into CRI with
month end indicator as ‘Y’,Then button will not be available
5.5 Global Classified Credit Report
5.6 General Memo
5.7 Industry Credit Review
5.8 Client On boarding
5.9 Reports

CRI
5. DATABASES AND FILES
6.1 Internal Data flow
6.2 SQL Jobs

There are many batch jobs running for the CRI application which are configured in
Autosys.
6.3 User Interfaces

Given below is a basic description of the major pages.
6.4 Server Details:
6.4.1 Reporting_Service_Url:
i. Lucene Search Url:
ii. Cri_Cms_ Service_Url:
iii. Customer_Financial_ Service_Url:
iv. Cat_RestfulServiceBaseURL:
6.4.2 CRI Web Service:
Load Balancing URL:
CRI Web Services load is shared by below Citrix Servers
i. PROD IEM Server :

ii. War Name : core
iii. Batch Name :
iv. Operation Page/ Spring Job URL:
v. Direct URL :

CRI
7 APPLICATION HISTORY:
7.1 Typical Problems:
7.2 Release History:

N/A
7.3 Contacts
Office Mobile #
S.No. Name Role Telephone (Mandator Email Address
# y)
Pradip Offshore 91-
1 - pradip.jain@citi.com
Jain DPE 9810329970
Subrata Onshore
2 Subrata.mondal@citi.com
Mondal DM
Anu Offshore +91981092
3 anu.aggarwal@citi.com
Aggarwal DM 0470
Yogesh Support +91999917 yogesh.kumar.agrawal@citi
4
Aggarwal team lead 3007 .com
Support
Khushbu +919911722 Khusbhoo.singhal@citi.co
5 team
Singhal 085 m
member
Support
Mohit +919911075
6 team Mohit4.Gupta@citi.com
Gupta 200
member
Support
Mohit +91999946
team Mohit.siddhu@citi.com
Sidhu 1269
7 member
Venkates Support +91 venkateswarareddy.dasiredd
wararedy team 9886700773 y@citi.com
8 Dasiredy member
Support
Kavya team
9 member
Support
Vaamsi team
10 member

CRI
8. REFERENCE DOCUMENTS
The Project Library consists of documents that can provide further information about the
application. Documents related to the CRI application includes
Version Last
Document Name Document Location
Number Update
(YY/
MM/DD)
CRI-L2 Support Runbook 1.1

Aid Cri Appl V0.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Aid Cri Appl V0.1

Uploaded by

Copyright:

Available Formats

Document ID : CRI AID

Document Owner : PS Team

Application Information Document

Credit Risk Interface/Citi Risk Approvals (CRI)

Document Control Section

Version Number: 1.0

Version Description of Changes Author Issue Date

IBM Global Services Page 2 of 28

2. TERMINOLOGY AND ACRONYMS....................................................................................................... 5

IBM Global Services Page 3 of 28

IBM Global Services Page 4 of 28

2. TERMINOLOGY AND ACRONYMS

1 AID Application Information Document

IBM Global Services Page 5 of 28

CSI App ID App Name

IBM Global Services Page 6 of 28

4.1 CRI Application Platform

Server Name Server Type Purpose

4.3 Configuration Management

IBM Global Services Page 7 of 28

Introduction to Credit risk management and CePac:

IBM Global Services Page 8 of 28

5.1 Credit Approval

IBM Global Services Page 9 of 28

5.5.3 Functional Description

Technology Base of CRI:

i. It is a rich application with a front end of the java.

i. The first screen of CRI application is having CRI Dashboard.

The Credit Approval Process:

IBM Global Services Page 10 of 28

5.5.4 Creation of Credit Approval workflow

Select any one of the following types of Credit Approvals:

IBM Global Services Page 11 of 28

IBM Global Services Page 12 of 28

IBM Global Services Page 13 of 28

The Create CA screen displays the following:

5.1.5 Tables Information in DB

5.1.6 Frequentl Used Queries

select * from cepaac_customers /*customer related table*/

IBM Global Services Page 14 of 28

select * from cfs_document_link /*CFS link related table*/

5.2 Credit Memo

5.3 Operation Memo

5.3.2 Operations Memo– OT approval Workflow

5.3.3 CRI Flow for OT Workflow approval

IBM Global Services Page 15 of 28

Operations  Signers  RA/RM  Operations

5.3.4 Implementation requirements and challenges

i. One-time setup of User profile setup

5.3.5 How to create the Ops Memo

Two types of workflow:

1. Credit Workflow Process:

2. Non Credit Workflow Process:

IBM Global Services Page 16 of 28

IBM Global Services Page 17 of 28

IBM Global Services Page 18 of 28

5.3.6 Acronyms in OPS Memo:

IBM Global Services Page 19 of 28

5.3.5 Tables for OPS memo workflow process:

select * from intra_ot_at_reg

5.3.6 Admin Tables:

SELECT * FROM OPS_ADDITIONAL_MAILINFO

IBM Global Services Page 20 of 28

select * from cepaac_customers /customer related table/

select * from cfs_document_link /CFS link related table/