2.1.2 Detailed Flow
Table 2-1 Detailed Flow
| Entity | Existing length | Proposed length |
|---|---|---|
| Branch Code | VARCHAR2(3) | VARCHAR2(6) |
| User ID | VARCHAR2(12) | VARCHAR2(320) |
| Customer Number | VARCHAR2(9) | VARCHAR2(20) |
| Customer Name | VARCHAR2(35) | VARCHAR2(140) |
| Account Number | VARCHAR2(20) | VARCHAR2(34) |
| Account Description | VARCHAR2(105) | VARCHAR2(140) |
| GL Code | VARCHAR2(20) | |
| Entity Code | VARCHAR2(20) |
- Maintenance screens enhanced to support the same
- Online screens and related processing enhanced to support the same :
- Contract reference number generation
- Process reference number generation
- Transaction processing
- EOD processing
- APIs enhanced to support the same
- Simulation and handoff APIs
- OBDX APIs enhanced to provide branch code
- Branch code – Increase field length from VARCHAR2(3) to VARCHAR2(6)
Table 2-2 Branch code – Increase field length from VARCHAR2(3) to VARCHAR2(6)
| Existing Design | Proposed Design |
|---|---|
| Branch code column definition : VARCHAR2(3) | Branch code column definition :VARCHAR2(6) |
| Branch code length - Static 3 digits only for instance PK1, 001 | Branch code length will be Static. Length can be 3/4/5/6 only. Branch code length will be parameterized in CSTB_PARAM. BRANCH_CODE_LENGTH - Common core parameter. |
| Contract Reference number : VARCHAR2(16) Branch Code – PK1 (First 3
digits) Product Code – ILUN (Next 4 digits ) Julian date – 24019
(YYDDD)
Sequence number – 0017 (NNNN) |
Contract Reference number : VARCHAR2(16). Contract Reference number will be derived based on Common Core parameter - CSTB_PARAM.REF_NUM_GEN_FORMAT If REF_NUM_GEN_FORMAT is O – Contract Reference Number will be generated as per existing functionality. If REF_NUM_GEN_FORMAT is N – Contract Reference Number will be generated in new format namely Product / Process Code + Julian Date + Sequence Number |
| Sequence generation based on branch and product code : trsq_pk1ilun | Sequence generation will be as below : TRSQ<Product/Process Code><Julian Date> TRSQILUN<RRDDD> TRSQZRLQ<RRDDD> Sequence will be dropped during EOD as per existing functionality |
- All maintenance screens with branch code enhanced to support 6 digit branch code.
- All online screens with branch code enhanced to support 6 digit
branch code.
UI display will continue to be the same.
- Processing impact :
- Currently branch code and product code is derived from Contract reference number withsubstr (contract_ref_no,1,3) and substr(contract_ref_no,4,4). Dependency of contract referencenumber for branch code and product code derivation is removed. New functions created toderive the same from cstb_tf_contract.
- Processing impact :
- APIs enhanced to support branch code up to 6 digit
- <obt:BRANCH>OBTF02</obt:BRANCH>
- OBDX APIs enhanced to provide Branch code in response
| SlNo | Service Name | Operation Code | Branch Tag |
|---|---|---|---|
| 1 | OBTFLCService | QueryGuaranteeClmDtl | <BRANCH> |
| 2 | OBTFLCService | QueryAmendDtls | <BRANCH> |
| 3 | OBTFLCService | QueryContractListDtl | <BRANCH> |
| 4 | OBTFLCService | QueryTransLCAmend | <BRANCH> |
| 5 | OBTFLIService | QueryLiContractLstDt | <BRANCH> |
| 6 | OBTFIFService | QueryIFDTFCustDisp | <BRANCH> |
- User Id – Increase field length from VARCHAR2(12) to VARCHAR2(320)
| Existing design | Proposed design | Recommended display |
| User Id code column definition : VARCHAR2(12) | User Id code column definition : VARCHAR2(320) | 40 characters |
- Provision to create user id with length of 320 characters to support email id
- Maker and Checker id in audit trail to display user id appropriately
- Handoff and simulation APIs support the same