ERROR_

ERROR_DESCription FUNCTIONALITY ERROR_ANALYSIS

NO
The supervisory error "Advance Already Processed" comes when the loan terms of account have
Advance Already expired but remaining repays for the account is still non­ zero. In such cases issue needs to be
0 Processed Interest rate referred to the Service Desk for necessary rectification/further analysis.
After promotion of IR 73740 on 21/05/2013, Manual upgradation of IRAC status has restricted i.e.
now branches can downgrade the account. But they won' t be able to upgrade the account at their
end. Means if the branch is trying to change the new irac status and If the required new irac
status is l ess than the existing old IRAC status then system will not allow the same and will
raise the error "Upgradation is restricted". Hence, branch can r emove the irregularity from the
0 Upgradation is restricted NPA Tracking account and hence system will automatically upgrade the account at EOD.
The system allows one TDR and one collateral linking only one time and when the TDR gets
amended the system increments the sequence no in collateral a nd TDR account linking table.
The error comes when the same TDR is linked with two or more than two time with the collateral.
TDR/PPF ACCOUNT The branch can not make the status of the TDR with the collateral as inactive at their end. In
0 MUST BE DIFFERENT Collateral such cases refer the issue to Service Desk for necessary amendment from backend .
While doing Home branch change or Product change request from screen \\ SCR:031669 Loans:
To generate the request for product/branch change, error "Re cord already exists" will come if
Home branch change or Product change request for this account already exists. So if the request
is related with P roduct change then issue needs to be referred to the SBI BOG Team for
authorization and if the request is related with Home branch change then issue n eeds to be
Home branch change, referred to the respective LHO for authorization. After necessary process from the end of SBI
0 Record already exists Product change BOG or LHO Team, Home branch or Product of ac count will get changed.
For any product, the minimum withdrawal amount set is set at the product level.In case interest
paid to the account is lower than the minimum value then interest transfer fails with error '0107:
TRANS VALUE TOO TRANS VALUE TOO LOW'. For further assistance regarding the product level settings consult
107 LOW Transaction Details with BOG Team.
As per SBI archival policy, the entry of accounts closed during APR­2013 or before has archived
from deposit account master table. Hence, the branch i s facing mentioned error "155: PL
108 NO SUCH ACCOUNT Archived Accounts CONTACT SERVICE DESK INVM MRNF".
As per the functionality, while Subsidy appropriation error "110: Account closed" comes if the GL
account or DEP account used in Subsidy appropriation has closed. If transaction is through GL
account then while Subsidy appropriation, branch needs to enter any other GL account no which
is in open status and having current balance greater than the subsidy amount. Or if the subsidy
Account closed ( while has received into DEP account and DEP account has closed then ref er the issue to Service
110 Subsidy appropriation ) Subsidy Desk for appropriation of Subsidy from backend.
 The mentioned error comes when the TDR account, on which the collateral was created has
closed and the status of the TDR with the collateral is still active (00). Hence when branch is
authorizing the collateral they are getting the error "111: Account unavailable" .The branch can
make the TDR accou nt and collateral linking status as "09: Inactive" at their end through the
screen \\ SCR:067141 CIF:Amend/Enquiry TDR/PPF Details . Step 1: Choose M enu: DL/ TL
Accounts & Services à Security (Primary/ Collateral) à Customer à Amend/Enquire/Authorize à
Amend/Enquire Collateral The screen “\\ SCR: 067090 CIF: Amend/Enquire Collateral” appears
Step 2: Enter the Collateral Number in the field “Collateral Number.” Step 3: Fill the Collateral Nu
mber and Transmit. Screen No 67040 will be scheduled. Click on Transmit. Step 4:After that
111 Account unavailable Collateral authorize the collateral through the screen SCR:// 67157 (the nevigation mentioned above)
ACCOUNT IS LOCKED ­ The mentioned issue is temporary issue . Please try the transaction after sometime . If still issue
112 PLS. TRY AGAIN Account Related perssit for specific Transaction then escalate t he issue to TCS L2 team .
Reason: The mentioned error '112:ACCOUNT IS LOCKED; TRY AGAIN' is encountered when
there are many transactions being carried out on the same account. When one transaction is
being carried out on the account, the account is locked and no other transaction is allowed on the
account at that same instan t and the error is encountered if any other transaction is performed.
ACCOUNT IS LOCKED; Solution : Branch have to try the transaction after some time.In case proble m persists then refer
112 TRY AGAIN Transaction Related to L2 Team for further analysis.
The mentioned error comes during Sweep execution when there is active stop set in the account.
In case required, branch can remove the stop using scre en \\SCR:009092 Deposits : Remove
113 ACCOUNT STOPPED Sweep Stop.
Reason: The status of the involved BGL(s) in the transaction is(are) in STOP/HELD status , due
114 ACCOUNT HELD Transaction Related to which branch faces mentioned error. Solution: Take up the with BOG for status change
The error "126: Invalid Date" comes when there is already subvention present in the account and
branch is trying to give subvention. To avoid the e rror, branch can expire existing subvention i.e.
amend the subvention flag as 'N' and subvention end date as today's date, hence today
126 Invalid Date Subvention subvention will end. Then the branch can give the subvention next day.
The error "155: Please contact computer center BLDV XREF" comes when the repayment
shedule of the account has already expired and branch is trying to amend the repayment shedule
of the account. The solution for such situation is to delete the repayment shedule from back end
and then generate the same at branch end. For deletion of repayment shedule from backend
controller approval is needed. Issue needs to be referred to the Service Desk wi th controller
approval if branch wants the above mentioned solution. Also before that please note that the
Please contact computer repayment shedule from backend will only be deleted, if loan terms of the account have not yet
155 center BLDV XREF Repayment schedule expired.
PL CONTACT SERVICE The mentioned error comes when the customer number in the master table of the collateral and in
155 DESK RELM **** Collateral the relationship table is different .In such cases ref er the issue to Service Desk
PLEASE CONTACT
COMPUTER CENTR
155 MSAN DUPM Cheque Issueance Take up the issue with TCS L2 team for providing the datafix
 PLEASE CONTACT
COMPUTER CENTR
155 SDLV DUPM Lockers Take up the issue with TCS L2 team for providing the datafix
155: PL CONTACT The mentioned error comes when the branch is trying to update the KYC or amending the CIF
SERVICE DESK CUID and is providing the same ID's which has already been submit ted by the branch. In this case ask
155 DUPM CIF Amendment the branch to submit IDs which have not been submitted earlier.
155:PL CONTACT The mentioned error comes when a CIF with status as 002 (Deceased) has its number of
SERVICE DESK CVSV associated accounts wrongly populated. A back­end script will be provided to rectify the same by
155 RELN CIF Amendment the L2 team.
PL CONTACT SERVICE The mentioned error comes during Sweep execution when there are archived accounts linked to
155 DESK Sweep the CIF of the account. For rectification, datafix will b e provided by L2 team.
As per archival policy, the entry of accounts closed till March 2013 or before has been archived
from deposit master table. If branch enquires such ac count at their end system throws the error
PL CONTACT SERVICE Account enquiry, SI/Sweep "155: PL CONTACT SERVICE DESK INVM MRNF". In case branch wants, the archived data for
155 DESK INVM MRNF failure, MOD break the same is availa ble at DCOG.
This error comes when the account has opened under such a product whose OD Indicator is 'Y' at
product level, But no record was inserted into CC/OD de tails table. Branch can go to screen
7050 and choose the option J: Additional CC/OD details. Please ask the branch to then fill in the
PL CONTACT SERVICE Account opening, details. An ent ry into CC/OD details table will get passed. Then branch will be able to do the
155 DESK INCC MRNF transaction required transation.
The mentioned error 155: PL CONTACT SERVICE DESK CUSV XEND comes when there is no
entry in the business details table. This arises when the account wa s created through bulk
account creation no entry was passed in the table business details table. And there is a
validation while doing customer detail s amendment through screen 67000 that it checks the
entry in business details table. Hence the issue. An IR 19340 was raised for the same and now is
P rod Promoted. Description:While creating a non­personal customer through Bulk Account
creation, no record is inserted in the business details table ta ble. Hence, while amending the
Customer details through 67000 screen, an error "155: PL CONTACT COMPUTER CENTR CUSV
XEND" is displayed. If the CIF was created before the IR went into production, the branch will still
155: PL CONTACT be facing the issue. In this case ask the branch to amend the bussiness details thr ough the
SERVICE DESK CUSV screen 67102 (Scheduled through SCR//67050) and then they will be able to amend the customer
155 XEND CIF Amendment details through screen no. 67000.
The mentioned error occurs when there is an active STOP set on the mentioned account .As per
the SBI requirement , transaction data of accounts pertai ning to april 2013 and before has been
moved to an offline database by creating a new table. However during the process of data
migration stops set du ring account opening due to insufficient ids was also moved to the offline
155:PL CONTACT database. Hence although if the customer submits sufficient ids later on , the branch is not able
SERVICE DESK INVM to remove the stop at their end. Hence in such a case a datafix will be provided from L2 team to
155 X10T Stop remove the number of stops.
 The mentioned error 155 PL CONTACT SERVICE DESK PPFM MRNF comes when account is
opened on certain date DD/MMM/YYYY, but backdated details have not bee n provided. Kindly
ask the branch to perform following things:­ 1)Go to Amend Deposit Tabbed Screen > Screen
7050 will pop up ­> Give the PPF account number (11digit), select option as '1:Account details'
and transmit ­> The account amendment screen 7000 will pop up .Provide value 24 in "Booking
No field". 2)Go to Amend Deposit Tabbed Screen > Screen 7050 will pop up ­> Give the PPF
account number ,select option as 'P: backdated PPF details' and transmit ­> The '7052 PPF
backdated details' screen will appear. Give the preceding 6 years PPF balance starting from the
first column on the left sid e. In the first column give the balance as on the previous year of the
current financial year and give the balances in the subsequent columns in desce nding order .
155 : PL CONTACT (Eg : 1st Column ­ Bal on 31.03.15, 2 . 2nd Column ­ Bal on 31.03.14, 3. 3rd Column ­ Bal on
SERVICE DESK PPFM 31.03.13,4. 4th Column ­ Bal on 31.03.12,5. 5th Column ­ Bal on 31.03.11 and 6. 6th Column ­
155 MRNF PPF Bal on 31.03.10).
As per the functionality, the error "166: ABOVE MAX LOAN/CREDIT LIMIT" comes when the
ABOVE MAX LOAN/ Account opening, Loan branch tries to approve the limit to the account more than the l imit allowed at product level.
166 CREDIT LIMIT approval Branch can approve the loan for any account only upto product level maximum loan amount.
There must be an active stop set on the account. As per the SBI requirement, transaction data of
accounts pertaining to APR­2013 and before has been m oved to an offline database by creating
a new table. However during the process of data migration stops set during account opening due
to insufficient ids was also moved to the offline database. Hence, although if the customer
REQD STOP DOES submits sufficient ids later on, the branch would not able to remove the stop at their end. Hence,
172 NOT EXIST Stop a script needs to be provided to remove the number of stops.
 After prodpromotion of IR: 74681, 75354 on 11­OCT­2014, it is compulsory to first make the
status of all closed/archived/non­SBI TDR account and colla teral linking status as 09: Inactive
then only system will allow limit approval in CC/OD account. So, now branch needs to make the
status of all cl osed/archived/non­SBI TDR account and collateral linking status as 09: Inactive at
their end. For the same branch can follow the instructions: 1. G o to screen Menu: DL/ TL
Accounts & Services ­> Security (Primary/ Collateral)­> Customer ­> Amend/Enquire/Authorize ­
> Amend/Enquire Collateral. The screen “\\ SCR:067090 CIF: Amend/Enquire Collateral” appears.
Fill the Collateral Number and Transmit. Screen No 67040 will be scheduled. 2. Select Action as
D:Details and Click on Transmit. Screen 67141 will display. 3. In Screen 67141, Select Action
A:Amend, Select Status 09:Inactive for perti cular STDR and Click on Transmit. 4. Choose Menu:
DL/ TL Accounts & Services ­> Security (Primary/ Collateral) ­> Customer ­> Amend/Enquire/
Authorize ­> Authorize Security. Screen \\ SCR:067158 CIF: Authorize Collateral appears. Enter
the Collateral Number, noted down in the previous step while e ntering the Security details, and
click on “Transmit”. Screen \\ SCR:067157 CIF: Authorize Collateral appear. Step 5: Select
“Action” as “U:Authoriz e”. The authorising officer has to Input his/ her “Password” and Click on
“Transmit. Repeat the process for all the collaterals with which closed/a rchived/non­SBI TDR
account are linked. After making the as status 09: Inactive for all closed/archived/non­SBI TDR
account and respective collater al, branch will be able to approve the limit of the CC/OD account.
Record not found ( while In case error persists issue can be referred to the Service Desk to know collateral s and TDR
188 Limit approval ) Limit accounts.
This error comes at the time of account closure/Writeoff, when branch enters closure/Writeoff
amount as some different amount that is required for acc ount closure/Writeoff. Branch needs to
go to screen \\ SCR:013000 Loans: Request Discharge Figure for loan accounts and screen \\
SCR:003000 CC/OD Account Closure Enquiry for CC/OD accounts. The branch will get the
discharge amount for the mentioned acount. Ask the branch to put this amount as th e discharge
AMOUNT DOES NOT amount at the time of closure. (Please do not add any other amount to the discharge amount).
EQUQL DISCHARGE Also, the option Waive Period/event based fee s on this closure enquiry as well as on the Closure
197 VALUE Writeoff, Closure screen should be same ( Y/N ).
INVALID ACCT TYPE, If the branch selects a product not applicable to the parameters set for the account/CIF of the
INT CAT OR account, the branch will face this error. In case of A TM card issuance, this error comes for a
201 CURRENCY ATM card type not applicable for the CIF.
As per the existing functionality, the error "308: ADJUSMENTS NOT PERMITTED/
INCA>PRINCIPAL+INT BUCKETS" comes when branch tries to do the interest adj ustment more
than the amount present in the accrued interest bucket of the account. Branch can make a short
ADJUSMENTS NOT enquiry and note down the exact amount of accrual buckets and adjust the same and then try to
PERMITTED/ transfer the account into recalled asset on the same day when they are zeroing the accruals. Pl
INCA>PRINCIPAL+INT ease suggest the branch to do not enter the amount greater then the accruals present in the
308 BUCKETS Recalled asset account.
 Reason : For an account all the modes are not allowed to be set for product corresponding to a
particular product . The modes which can be selected ar e predefined. Selection of any other
modes except the modes predefined will result in an error '314 : INVALID SELECTION'. Solution:
Kindly ask the branch to set the MOP type that is allowed for the product.. L2 Team or BOG can
314 INVALID SELECTION Account Amendment assist in selecting the proper MOP.
This error comes when branch tries to will try to give the rate increment such that the interest rate
of the account will exceed product level maximum allowed interest rate. For example for any
product minimum interest rate and maximum interest rate allowed at product level are 4 and 14.
Then int erest rate at account level can't be amended such that it will become greater than 14 or
328 Int Rate > Max Limit Interest rate less than 4.
This error comes when branch tries to give the rate increment such that the interest rate of the
account will become less than the product level minim um allowed interest rate. For example for
any product minimum interest rate and maximum interest rate allowed at product level are 4 and
INT RATE BELOW 14. Then i nterest rate at account level can't be amended such that it will become greater than 14
333 MINIMUM Interest rate or less than 4. Branch needs to follow the validation in or der to avoid the error.
The mentioned error comes during Sweep execution when the account balance is less than the
398 Insufficient funds Sweep threshold balance set as per sweep parameters.
The branch is trying to pay the cheque which is not been issued on account . In case of
CHEQUE OUT OF diwidenet warrent CCPAP account the cheque shuold be issued on account and after that the
401 RANGE Cheque Payment cheque should be loged in Diwident warrent module .
Same cheque number(irrespective of prefix ) can not be issued more than once in the same
account. If the branch is trying to issue cheque range which is already issued in this
account,branch can not Issue again these cheque ranges(with different prefix also),As there is no
CHEQUE ALREADY validation for the prefix and Instrument in system the system will check only cheque ranges
418 ISSUED Cheque Issueance issued in the account.
The issue is faced by branch when the details of product in which account is opned in not present
NO PARAMETERS SET in parameter table . Take up the issue with the SBI BOG Team to make entry for the product
511 ­ CONTACT H/O Cheque Issueance code product code of account in PSAN parameter table.
Error 557: ADVANCE EXCEEDS APROVAL comes when branch tries to disburse the amount
more than the approved amount. Hence, through notmal disbursement transaction, branch can
disburse only amount the difference of approved amount and advance value. After that if branch
wants branch can debit the acc ount using the screen \\ SCR:011050 Loans: Adjustment Debit
ADVANCE EXCEEDS through batch posting at their end. However, please note that the amount debited through t his
557 APROVAL Disbursement transaction will increase the arrear amount with the same amount.
Error "569 Rate can't be less than ZERO" comes, when branch tries to give a negative value in
Rate cant be less than Set rate. While doing limit or set rate amendment bra nch needs to follow the above validation to
569 ZERO Limit, Interest rate avoid the error.
 As per the existing functionality, the error "573: LIMIT TOO HIGH" will come when the branch
tries to set a limit for an account which is greater than what it is set for the underlying product at
the product level. For example if for any product maximum limit allowed at product level is
50000 /­, then system will not allow limit for any account greater than 50000 /­. Branch needs to
573 LIMIT TOO HIGH Limit follow this validation while limit approval to avoid the erro r.
While creating the limit, the error "574: OVERDRAFT ALREADY ESTABLISHED" comes if the
limit of the account has already created. Branch can amend th e limit details from screen \\ SCR:
OVERDRAFT ALREADY 007009 Deposits: Amend Overdraft Details instead of creating the limit and hence they can
574 ESTABLISHED Limit approve the limit if requ ired.
This error comes when no limits have been created for the account and branch is trying limit
OVERDRAFT NOT approval transaction. Branch needs to create limits using the screen \\ SCR:002009 Deposits:
575 ESTABLISHED Limit Create Overdraft Details for the mentioned account and then try the limit approval transaction.
The mentioned error "611:­invalid start date " occurs if branch gives Commencement Date/
Invalid start date ( while StockStatement Date less than the start date .So branch has t o give Commencement Date/
611 amending the collateral ) Collateral StockStatement Date more than start date in the collateral amendment screen : \\ SCR:67040 .
The error "687: INTEREST RATE TOO LOW" will come if the branch tries to do the backdating
with interest rate as 0 or less than 0. Also error will come branch is trying to give rate increment
INTEREST RATE TOO such that the effectivr interest rate will become less than 0. Branch needs to follow this validation
687 LOW Backdating, Interest rate in orde r to avoid the error.
The system will throw this error if the cheque facility is unavailable on the account but available
PRODUCT OR at product,even if the account is in 'OPEN' status . Please advise the branch to set the facility for
ACCOUNT CHEQUE this account by selecting set option on screen \\ SCR :50214 CAS : Set/Remove Cheque Facility
754 FACILITY CLOSE Cheque Issueance a nd then try the transaction.
TERM GREATER THAN The error "771: TERM GREATER THAN MAXIMUM, OR LESSER THAN MINIMUM" comes if
MAXIMUM, OR branch tries to set the loan term greater the maximum term set at the prod uct level. Hence,
LESSER THAN Repayment schedule, Loan branch needs to enter the loan terms for any account only upto maximum term set at the product
771 MINIMUM term amendment level for underlying product of th e account.
As per the functionality, The report Gl 0823­01 will appear when the DDP are in Dishonured status
and hence the mentrioned DDPs are appearing in the r eport. This report is for branch Reference
823 REPORT GL 0823­01 Report Outstanding Issue purpose only.
As per the functionality, rate increment is not allowed for the accounts, which are under such
products whose negotiable rate indicator at product lev el is 0 or 2 or 3. In such case system
RATE INCREMENT restricts the rate increment with the error "847: RATE INCREMENT MUST BE ZERO". Hence,
847 MUST BE ZERO Interest rate branch can't give rate increment for such accounts.
CANNOT CHANGE
ACCOUNT TYPE ( while Error "865: CANNOT CHANGE ACCOUNT TYPE" comes while transferring the account into
transferring into Base Base product if the existing product of the account is not with any base product at product level.
865 Product ) Product change This is as per the parameter settings at product level.
 This error comes if­ 1. There is an active SI/sweep present in the account. 2. The limit rate or/
and expiry rate is not equal to zero ( applicable o nly for CC/OD accounts ). 3. The irac status of
CANNOT CHANGE the account is less than 04. Hence, to reslove the error branch needs to­ 1. Enquire all the SI/s
ACCOUNT TYPE ( while weep present in the account and remove them. 2. Zeroise the limit rate or/and expiry rate
transferring into Recalled ( applicable only for CC/OD accounts ). 3. If IRAC status of account is less than 04, then
865 asset ) Recalled asset downgrade the IRAC status to 04 or greater than 04.
CANNOT PROCESS
WITHOUT As the error "899: CANNOT PROCESS WITHOUT AUTHORIZATION OF COL:
AUTHORIZATION OF 00000077011797433" said that branch needs to authorize the collateral 77011797433 thro ugh
COL: screen \\ SCR: 067158 CIF: Authorize Collateral (nevigation as mentioned above). After authorize
899 00000077011797433 Collateral the collateral the branch will be able to remove the hold from the account using screen no 9095.
The mentioned error comes when the TDR/STDR linked with the collateral are closed/archived or
another banks stdr/tdr .The branch can make the TDR acco unt and collateral linking status as
"09: Inactive" at their end through the screen \\ SCR:067141 CIF:Amend/Enquiry TDR/PPF
Details : Step 1: Choose Menu: DL/ TL Accounts & Services à Security (Primary/ Collateral) à
CLOSED TDR Customer à Amend/Enquire/Authorize à Amend/Enquire Collateral The screen “\\ SCR :067090
ACCOUNT IS STILL CIF: Amend/Enquire Collateral” appears Step 2: Enter the Collateral Number in the field
LINKED AS “Collateral Number.” Step 3: Fill the Collateral N umber and Transmit. Screen No 67040 will be
COLLATERAL TO scheduled. Click on Transmit. Step 4:After that authorize the collateral through the screen SCR://
899 CCOD ACCOUNT Collateral 67157 (the nevigation mentioned above)
While amendment of IRAC status at branch end error "899: SELECTED CONDITION IS
INACTIVE/EXPIRED/INVALID COMES" appears when "Reason for change" i.e. s elected arrear
SELECTED CONDITION condition in screen they are using is disabled at product level. For example branch is selecting
IS INACTIVE/EXPIRED/ the "Reason for change" as 712. Now if this arrear condition is not active at product level then
899 INVALID NPA Tracking this error will appear. This validation is as per the existing functionality and prod uct parameter.
As per the recent functionality introduced through IR 71606,the branch will not be able to perform
the backdating i:e value dated transaction in the a gri products . The SC for which the branch is
facing mentioned error while dishonourent , kindly ask the branch to credit BGL 98655 and debit
BGL 986 56 with SC amount and revert with conformation after which script can be provided to
update sc status to dishonour and update collection amount on the customer account Now,if the
BACKDATING ON branch want to crebit/debit the BGL 98655 /98656 , they will face problem as it is restricted for
PRODUCT DISABLED manul credit/debit. He nce to resolve the Issue. kindly take up the Issue with SBI­BOG Team and
TEMPORARAILY NAME arrange to lift the flag from BGL 98655 /98656 . After that advise the branc h to do the transaction
899 IS SC on BGL 98655 /98656 .
AUCA ACC This error comes when there is an active entry for loan/CC/OD account and auca account is
NO.*********** HAS present in loan/CC/OD­AUCA account reference table. In su ch case if AUCA account has closed
ALREADY BEEN then branch needs to open a new AUCA account under the same segment code as loan/CC/OD
CREATED FOR THIS account and then issue needs to be referred to the Service Desk with new AUCA account and
899 ACCOUNT Writeoff, Recalled asset loan/CC/OD account for necessary updation from backend.
 A new functionality has introduced under IR 76044 on 20­DEC­2015 under which a new screen in
Customer Management option to capture the details of SHG members. Hence, now feeding of
details of all the SHG members is mandatory before opening the account. Branch needs to
navigate to screen SCR:067126 SHG Member Details Prompt Screen which will accept the SHG
CIF number and function ‘Create/Amend/Enquiry/Delete’. It will schedule screen 67127 where
Please Capture The details of upto 3 members can be captured and stored into SHGM table. If more records are to be
SHG Members Details CIF, CIF Creation, Account captured, the screen 67127 needs to be scheduled again . Hence, branch needs to feed the
899 Via Screen 67127 opening above details and hence try the required transaction.
As per the functionality, the error "899: Customer cisla details not present" occurs if branch has
not filled the customer cisla details or branch has not provided value for Investment In Plant and
Machinery in CISLA DETAIL1 screen. The branch can create the cisla details as per their
CUSTOMER CISLA requirement using screen \\ SCR 069452 CIF:Customer CISLA DETAIL. The navigation is as
DETAILS NOT follows: Customer Management ­ > Amend ­> 11: Customer CISLA Details in Sc reen \\ SCR:
899 PRESENT Account opening, Limit 067050 CIF: Change Details ­ > \\ SCR 069452 CIF:Customer CISLA DETAIL.
As per the existing functionality, the interest subvention is not applicable in case of account is
overdrawn. If account is overdrawn and hence system will not allow interest subvention in the
ACCOUNT IS account and system will through the error "899: ACCOUNT IS OVERDRAWN, NO
OVERDRAWN, NO SUBVENTION". Also if already t here is subvention and the account overdrawn then subvention
899 SUBVENTION Subvention period immediately terminates.
CANNOT APPROVE,
TEL. OTHER THAN Account opening, Loan As per the functionality only the loan officer can approve the account. Hence to avoid the error
899 LON OFF approval loan officer should perform the approval transaction.
The mentioned error comes when there is already an active Sweep set for the account but still
branch tries to create a new sweep. If the branch wants to delete the existing SB Plus sweep set
1146 PRI REL N EXISTS Sweep the same can be done through screen 60420. After that branch can create a new sweep.
TIER RECORD NOT
1216 FOUND Account Closure Take up the issue with TCS IMPL Team
While amending the collaterals from screen \\ SCR:067040 CIF: Amend/Enquire Collateral
Details, the mentioned error "1699: Invalid review date" comes in 3 cases­ 1. If the review date in
screen is less than collateral start date. 2. If the review date in screen is greater than collateral
expiry date. If the transaction posting date is greater than collateral review date. The branch can
also leave the review date field as blank while ame nding the collateral at their end to remove the
1699 INVALID REVIEW DATE Collateral error.
The branch is trying to issue multiple cheuqe book on account at a time using screen 51300
CHQ BOOK REQ where the field "No.of Cheque Books" enter by branch is mor e than maximam cheque book
EXCEEDS issued on account at parameter level . The branch should provide value in field "No.of Cheque
1777 PARAMETER LIMIT Cheque Issueance Books" as some lesser value . If issue still persist escalate the same to TCS L2 Team
 If the account opening balance is lesser than minimum opening balance (or) greater than the
INITIAL POSTING maximum opening balance for a particular product, the bran ch will face the error 1804:"INITIAL
OUTSIDE OPENING POSTING OUTSIDE OPENING BAL/LIMIT". Earlier the mentioned transaction was allowed with
1804 BAL/LIMIT Account Opening a supervisory override but as of now the transaction is restricted.
INITIAL POSTING The mentioned error comes during Sweep execution when the sweep amount which is to be
OUTSIDE OPENING sweeped comes out to be less than or greater than the minimum op ening balance or the
1804 BALANCE LIMIT Sweep maximum opening balance for the Sweep/MOD product set at the product level.
Cause: Branch is facing the issue 1819:INVALID CUSTOMER TYPE for a customer due to the
INVALID CUSTOMER population of wrong customer type field in the TDS related tabl es Solution: Take up the issue
1819 TYPE TDS with L2 Team for backend rectification.
Cause: As per the functionality new expiry date for temporary address of a customer should be
greater than the old expiry date. Otherwise branch faces the error "1833 : DATES CONFLICT
CIF AMENDMENT DATES CONFLICT WITH WITH OTHER TEMP. ADDRESS" during address amendment. Solution : Enter the correct expiry
1833 (ADDRESS) OTHER TEMP. ADDRESS date compatible with the previous expiry date.
The mentioned error "1920: APPLN DATE BEYOND PRODUCT DATE OR INTT CHANGE DT"
comes if the interest rate parameter is not set at the product level. For example for any product
Application date beyond all the interest rate parameters ( BASE ID, RATE ID, TIER ID, TMTI ID etc. ) are not set ( i.e. all
product date on Intt are BLANK ). Then the error will come. Issue needs to be referred to the SBI BOG team for
1920 change date Interest rate product level parameter settings or for further instructions.
The mentioned error occurs when branch is trying to perform a sweep amendment transaction but
there is exists no active sweep in the account. the bran ch can enquire about the same at their
end using screen \\ SCR:060420 CIF: Sweep Arrangements and by selecting required action as
SWEEP DETAILS NOT "E:ENQUIRE". Also , the same error arises when there is an inactive saving plus sweep but the
2066 FOUND Sweep sweep account flag is updated as 9 instead of 0. In this case datafix is p rovided by L2 team.
The mentioned error comes when the branch tries to close an account but there exists an active
MOD account linked. If the branch wants to close the me ntioned account then kindly ask the
branch to first deactivate the active linkage between the mentioned accounts and then perform
the closure transact ion. The branch can deactivate the sweep through the screen \\ SCR:060420
CIF: Sweep Arrangements by selecting required action as "E:ENQUIRE/AMMEND" w hich will
schedule screen \\ SCR:060421 CIF: List Sweep Arrangements. In this screen select the sweep
SWEEP MUST BE they want to delete and click on transmit which will schedule screen \\ SCR:060423 CIF: Maintain
DELETED BEFORE Sweep Arrangements . In this screen branch can select end date as today's date and click on
2088 CLOSURE Sweep transmit.
The mentioned error comes during Sweep execution when the maximum accumulated sweep
amount set for the sweep is lesser than the current sweep balance. This is as per the maximum
SWEEP NOT accumulated sweep amount set by the branch. Incase required branch can increase the
PROCESSED, WOULD maximum accumulated sweep amount at th eir end using screen \\ SCR:060423 CIF: Maintain
2096 EXCEED MAX ACCUM Sweep Sweep Arrangements and then wait for the next sweep execution date.
 As per the functionality set, while home branch or product or segment code change, if the branch
does not change anything in the screen 17046 for loan accounts or 7046 for CC/OD accounts,
and just presses Transmit, then the branch will get the mentioned error "2111: HOME BRANCH
OR ACCT TYPE / INT CA T MUST BE CHANGED". Branch needs to enter the required home
branch or product or segment code and keep remaining things same as before and then Tr
HOME BRANCH OR Home branch change, ansmit. For example if branch wants to change segment code then in screen 17046/7046 in new
ACCT TYPE / INT CAT Product change, Segment details enter require segment code and select previous pro duct and enter previous home branch
2111 MUST BE CHANGED change and Trasmit.
As per the functionality, this error comes if branch tries to change more than one out of the home
branch or product or segment code change in the scr een 17046 for loan accounts or 7046 for
CC/OD accounts i.e. two things like home branch and product or home branch and segment code
or segment code an d product can not be changed in one transaction. Branch needs to enter the
ACCT TYPE/ INT required home branch or product or segment code and keep remaining thing s same as before
CATEGORY AND Home branch change, and then Transmit. For example if branch wants to change segment code then in screen
BRANCH CANNOT BE Product change, Segment 17046/7046 in new details enter require segment code and select previous product and enter
2113 CHANGED TOGETHER change previous home branch and Trasmit.
While limit approval error "2190: OD EXPIRY DATE > FACILITY END DATE" comes when the
expiry date extered by the branch exceeds the facility expiry dat e of the customer i.e. limit
expiry date for any account can't be given after the facility expiry date of customer. Branch can
amend facility expir y date of customer at their end as per their requirement in order to avoid the
OD EXPIRY DATE > error else they can enter the limit expiry date for any account only le ss than the facility expiry
2190 FACILITY END DATE Limit date of customer.
The mentioned error occurs when the CIFs of the respective account numbers are migrated
incorrectly with ID1 having incorrect value. The branch faces error "2214: NOT FOUND ID
(MICM)" while amending the CIF. For rectification, a script to change the ID1 will given by the L2
2214 NOT FOUND ID (MICM) CIF Amendment team.
ACCOUNT STOPPED. The mentioned error occurs when the minor account flag in master table for the account is '2'(i.e.
CUSTOMER MAJOR minor turned major). Kindly ask the branch to go to Screen 7440: Maintain User Codes and
NOW, DELINK change the minor flag to '0'. This error is generally encountered as a SI failure cause or interest
2857 GUARDIAN Standing Instruction transfer fai lure issue.
The issue is faced by branches if at the time of IOI issueance the IOI payment limit for drawee
branch is less than the field PO_PAY_LIMIT ,GC_PAY_LIM IT ,TT_PAY_LIMIT,DD_PAY_LIMIT in
EXCEEDING BRANCH BRSD table and PO_LIM,TC_LIM ,TT_LIM ,GC_LIM in BRHM table. Take up the issue with BOG
2885 LIMIT IOI Issueance team for parameter setting
 The mentioned error "2890: NO DISBURSEMENT SCHEDULE FOR THE ACCOUNT" occurs at
the time of Writeoff/Closure of the account when the disbursement sched ule has not creater or
migrated for the account. Branch can generate the disbursement schedule at their end using \\
SCR:012593 Loans: Disbursement Create/Maintain Screen and then try Writeoff/Closure
NO DISBURSEMENT transaction. In case even after the generation of the disbursement schedule or during the gen
SCHEDULE FOR THE eration of disbursement schedule, branch faces any error the issue can be referred to the Service
2890 ACCOUNT Writeoff, Closure Desk.
Error 2891: ADVANCE EXCEEDS LIMIT comes when branch tries to disburse the amount more
than the approved amount. Hence, through notmal disbursement transaction, branch can disburse
only amount the difference of approved amount and advance value. After that if branch wants
branch can debit the acco unt using the screen \\ SCR:011050 Loans: Adjustment Debit through
ADVANCE EXCEEDS batch posting at their end. However, please note that the amount debited through th is transaction
2891 LIMIT Disbursement will increase the arrear amount with the same amount.
The error "2909: Can not open account­minor without guardian" comes if CIF of minor is not
linked with the CIF of the guardian. The branch has to crea te the relationship between the CIF of
the guardian and the CIF of the minor using \\ SCR:060440 CIF: Relationship Enquiry by
Can not open account­ selecting required actio n as add and Relationship Reqd: as 9428:GAURDIAN MINOR CUS.
2909 minor without guardian CIF Thereafter branch can create the minor account.
The mentioned error is faced due to the parameter settings for the product type , when the allow
ACCOUNT NAME name change flag in master table is set as 'N' or 'BL ANK' for that product type the branch will be
CHANGE NOT not be able to change the name of the account and if they try to do so will face the error '2913:
2913 ALLOWED Account Name Change Name C hange not allowed'.
When the branch creates the relationship between the CIF of the guardian and the CIF of the
minor using \\ SCR:060440 CIF: Relationship Enquiry by sel ecting required action as add and
RELATIONSHIP ID Relationship Reqd: as 9428:GAURDIAN MINOR CUS and if the branch gives an incorrect
3030 DOES NOT EXIST CIF relationship code. The branch has to select a relationship code present in the list.
As per the existing functionality, the application amount of a loan account cann't be amended
CAN NOT CHANGE after approval of the account. If branch tries to ame nd the application amount after approval of
3041 APPLICATION AMT Application amount the account the error "3041: CAN NOT CHANGE APPLICATION AMT" will come.
OPEN DATE For every product, there are maximum backdating days allowed set at the product level. Hence if
BACKDATING the branch tries to backdate an account under the ment ioned product for more no. of days then
EXCEEDED MAXIMUM specified at product level, an error "3044: OPEN DATE BACKDATING EXCEEDED MAXIMUM
3044 DAYS Account Level Amendment DAYS" occurs.
As per the functionality, the mentioned error "3411: INVALID REPAYMENT SHEDULE (N.P.I)" will
come in case the repayment schedule is required for an ac count but the repayment schedule
INVALID REPAYMENT has not been generated for that account. Branch can create the repayment schedule or if
3411 SHEDULE (N.P.I) Repayment schedule repayment schedule already exists then they can amend the same to rectify the error.
EITHER PAN OR FORM As per the functionality, Pan card detail should be entered in the cbs for the cif for which ATM
60/61 IS MANDATORY card need to be issued. In case pan card is not avail able , branch has to submit FORM 60 for all
3457 FOR THIS ACCT ATM accounts(related to the atm card issue) under the CIF for which ATM card need to be issued.
 The mentioned error comes during Sweep execution when PAN details are not entered for the
mentioned account. The submission of PAN is necessary under the IR 71539 which has been
raised for the same . IR 71539 Status : PROD Promoted (05/05/2012) Description : "Quoting of
PAN or obtaining of Form 60/61 is mandatory in all new accounts, except for time deposits up to
and including Rs.50000/­.In case the user submits the PAN and structurally vali d should be
transferred to his/her CIF information. In case of existing customers, option for capturing PAN or
Form 60/61 at the account level should be made available. The branches are required to forward
Form 60/61 received for opening Term Deposits amounting to more than Rs. 50000/­, a message
to this effect should be displayed and a report should also be generated at month end. Non­
resident and few customer type (list all ready provided) are exempted. Furnishing of PAN
Either PAN or Form mandatory for those accounts in which interest payable is aggregating to Rs. 10000/­ or more in a
60/61 is mandatory for financial year. (IR 189 54 & 70901) " . The branch should submit PAN details for the customer so
3457 this acct Sweep that savings plus sweep to execute.
FACILITY This error comes when the facility has already been created for the account but facility
BREAKDOWN VALUE breakdown has not been done by the branch. So branch needs to set the facility breakdown at
NOT FOR THIS their end for the facility breakdown under which account has opened. Then the system will allow
3939 PRODUCT Limit limit approval in th e account.
When there is an active SI set from the FROM ACCOUNT to the TO ACCOUNT for a CERTAIN
amount and frequency of execution. There is a Owner indicator for this SI as 'F' (FROM
account) , 'T' (TO account) or 'E' (EITHER from or to account). When the branch tries to amend it
or goes for closing any of the TO and FROM account they face this error in case any active SI is
still present. So, to delete the SI they may delete the SI depending on the owner i ndicator from
screen SCR//947.
*****************************************************************************************************************
***** ***************** 1).If it is "F" then they can delete it from the "FROM ACCOUNT. 2).If it is "T"
ONLY OWNER CAN then they can delete it from "TO ACCOUNT". 3).I f it is "E" then it can be deleted from either of
4206 MAINTAIN OR DELETE Standing Instruction the accounts.
While transferring account into Recalled asset error "4253: PRODUCT MISMATCH" comes if
branch is transferring the account into Recalled asset through product change menu i.e. branch
has selected option "A/C type ­ Home branch change" instead of transferring the account into
PRODUCT MISMATCH Recalled asset through di rect navigation. For CC/OD accounts, branch can transfer the account
( while transferring into PB/RD selecting option "R: Transfer to PB/RD" on screen \\ SCR:007050 Dep osits: Change
account into Recalled Details. For loan accounts, through loan tracking branch can transfer the account into PB/RD
4253 asset ) Recalled asset selecting option "7: Transfer to PB/RD" on screen \\ SCR:017050 Loans: Change Details.
While product change of any account error "4253: PRODUCT MISMATCH" comes if the
parameters set at the product level for existing product is different in comparision with the product
in which branch is trying to change. This validation is as per the product parameters and existing
PRODUCT MISMATCH functionality an d hence branch will not be able to change the product into the required product
4253 ( while product change ) Product change that they are entering in the screen of product change.
 The mentioned error comes during Sweep execution when the term length selected for the MOD
a/c to be created by sweep execution is not correct as per the product specification of the MOD
a/c . The branch should set correct term length for selected MOD product by using following
INVALID FREQ, TERM navigation : 1) F rom screen \\ SCR:007050 Deposits: Change Details which will navigate to
BASIS, LENGTH screen \\ SCR: 007000 Amend Deposit Details 2) Select correct TERM A/C O PTION and enter
4346 COMBINATION Sweep correct term in 'Saving Plus Term length' field.
This error comes when there are non­zero accruals present in the account and branch is trying to
transfer the account into recalled asset. Branch c an make a short enquiry and note down the
Interest amount must exact amount of accrual buckets and adjust the same and then try to transfer the account into
4400 be=0 Recalled asset recalled asset on the same day when they are zeroing the accruals to avoid the problem.
As per existing functionality, the error "5026: REPAYMENT DATE IS EARLIER THAN TODAY"
will come if the branch is trying to create the repayment schedu le for a date which is less/earlier
REPAYMENT DATE IS than today's date. Branch needs to enter the Principal repay start date and Interest repay start
5026 EARLIER THAN TODAY Repayment schedule date following ab ove validation.
If the branch is facing error while clearing the batch on screen 2080 , then the cleaing date for the
CLEARING DATE IS branch must have been marked as HOLIDAY in Branc h Calender . Take up the issue with BOG
5048 HOLIDAY Clearing Related Issue team to make the Clearing date of branch to WORKING in Branch calender.
In the report 389A INTEREST NOT PAID ON DELAYED COLLECTIONS due to some code bug
wrong SC are getting picked up in the report due to which even branch is able to see SC in
report ,they are unable to do the delayed interest transaction on the SC . An IR will be raised for
correcting the report so t hat only required SC will be shown in the report . Meanwhile for Kindly
ask the branch to ignore the SC for which they are facing error in system an d do the delayed
CHARGE CALCULATED interest transacton on SC where branch is facing no issue while paying intrest adjustment using
SHOULD BE GREATER system . Once the for generation of proper report will get promoted ,the report will include correct
5057 THAN ZERO SC/Report related SC entries .
The mentioned error occurs when the PPF account under a CIF (CIF1) was migrated incorrectly
with joint relationship with the another CIF (CIF2) .The s ystem no longer permits PPF accounts
as joint accounts . Hence the branch is facing the error "5113:PPF account cannot be Joint" while
delinking the j oin link . As a result the branch will be unable to delink the CIF2 from the PPF
account . In order to remove the joint linkage a datafix will be prov ided by the L2 team.
*****************************************************************************************************************
PPF account cannot be *************** ******* Further the same error will also occur if the branch is trying to covert a PPF
5113 Joint PPF account into a joint account. This is not permitted and hence branch will not be able to do it.
As per the functionality, the error "5177: ROC FLAG MUST BE EQUAL TO Y OR N OR
ROC FLAG MUST BE SPACES" comes when the value for ROC flag is other than Y or N while am ending/creating
EQUAL TO Y OR N OR collateral. The error mostly comes in case of migrated collaterals. Hence, branch needs to select
5177 SPACES Collateral the ROC flag as 'N' or 'Y' as per the branch requirement and than they can amend the collateral.
 As per the functionality, the mentioned error "5180: INVALID COLLATERAL CHANGE TYPE"
comes if the charge type of the collateral is other than '01','02 ','03','04','05','06'. To avoid the error,
branch needs to select the charge type as 01: Equitable Mortgage, 02: English Mortgage, 03:
INVALID COLLATERAL Pledge, 04: Hypothecation, 05: Lien, 06: Assignment as per the requirement in the screen they
5180 CHANGE TYPE Collateral are using in collateral amendment ( i.e. screen 67040 ).
As per the existing functionality, the error "5281: Subsidy processing not allowed" comes when
the Subsidy Indicator at the Product Level is not set t o U or B. Hence, system will not allow
subsidy processing where Subsidy Indicator at the Product Level. Subsidy Indicator at the
Product Level is a pr oduct parameter and same is not amendable at branch end. Also this error
comes when, at the product level Subsidy Indicator is 'U' or 'B' but at a ccount level, the subsidy
Required flag is not set to Y. However, in this case branch can amend the subsidy Required flag
Subsidy processing not as 'Y' at their end using th e screen \\ SCR:017048 Loans: Record additional loan details and then
5281 allowed Subsidy try the subsidy processing.
As per the functionality, the claiming subsidy amount based on the following criteria:­ 1. Certain
percentage of sanctioned amount is equal to subsid y amount. 2. Per person subsidy amount =
per person subsidy amount * No. of persons 3. Max. subsidy amount which is fixed Eligible
subsidy amount i s the least of above 3 criteria. This is as per the existing functionality and
Subsidy amount greater parameters set at product level. Hence, branch needs to follow above restrictions in order to
5287 than maximum allowed Subsidy avoid the error.
SUBSIDY RECEIVED
AMT CANT BE
GREATER THAN As per the existing functionality, branch can not not receive the subsidy amount greater than the
5289 CLAIMED AMT Subsidy subsidy claim amount. Branch needs to follow this validation in order to avoid this error.
As per the existing functionality, if the multiclaim flag at product level for the subsidy scheme
under which subsidy has given, is 'N' then subsidy c an be claimed only once in the account. If
branch has claimed the subsidy and then they have rejected the subsidy and after that once
again branch tries to claim the subsidy, system will not allow the same and will through the error
5292 Subsidy Rejected Subsidy "5292: Subsidy Rejected".
This error comes when the facility has already been created for the account and branch is not
CUSTOMER FACILITY entering the same while limit approval in the same scree n they are using. Branch needs to give
EXISTS, MULTIPLES facility number same as the customer number of the account in the screen they are using to
5307 NOT ALLOWED Limit avoid the error.
The error "5386: DISCHARGE CAN NOT BE DONE WITHOUT ADVANCE" comes when the
advanced value is 0 /­ i.e. the branch has not done any disbursment of the loan and still they are
trying to close the loan account. Please note when the status of the account is other than PART
or FULL and disbursement ha s not taken place in the account, than branch should cancel the
DISCHARGE CAN NOT account rather than closing. If loan balance is also there then branhc needs to first recover the
BE DONE WITHOUT same before calcelling the account. Also another way branch can disburse amount 1 /­ in the
5386 ADVANCE Writeoff, Closure account and hence they can close the account.
 As per the functionality, the error "5481: Amount can not be below product minimum" comes
when approved amount at account level is less than minimum l oan amount at product level.
Amount can not be Account opening, Loan Branch can approve the loan for any account only between product level minimum loan amount
5481 below product minimum approval and maximum loan amount.
The mentioned error ocuurs when branch is trying to open a PPF or SCSS or SSA account but
PPF sweep parameters are not set for the branch in which the account is opening. Incase of PPF
and SCSS accounts, branch can create the Govt Sweep Parameter using screen \\SCR
BGL/GOVT PPF 007061:DEP:Govt Sweep Parameter wh ich will navigate to screen \\SCR:007062:Govt Sweep
SWEEP ACCT NOT Parameters Screen. Further For SSA accounts take up the issue with BOG to set the sweep
5614 SET PPF/SCSS/SSA parameters so that the accounts under Sukanya Samriddhi can be opened
This error comes when the facility has already been created for the account and branch is not
CUSTOMER FACILITY entering the same while account opening in the same scre en they are using. Branch needs to
EXISTS FOR THE give facility number same as the customer number of the account in the screen they are using to
5634 CUSTOMER Account opening avoid the error.
The mentioned error occurs when there is a mismatch in the values of INTEREST FROM DATE
Invalid Currency Contra and TERM FROM DATE fields in the database. Script will be prov ided by the L2 team to rectify
5647 Account FCN Interest the same mismatch.
Reason : The error '5660: EITHER MOP NOT SET OR INVALID MOP FOR CARD TYPE' comes
EITHER MOP NOT SET when for a account product type all the modes are not allowed and branch tries to issue ATM
OR INVALID MOP FOR card by selecting the MOP which is not allowed. Solution: Kindly ask the branch to set the MOP
5660 CARD TYPE ATM CARD ISSUANCE type that is allowed f or the product.. L2 Team or BOG can assist in selecting the proper MOP.
The error "5671: TDR INTT RATE>OD INTT RATE" comes at the time of limit approval if the
interest rate of TDR account attached as collateral for that O D account is greater than the OD
account. Before limit approval, branch needs to amend the set rate or rate increment of the
TDR INTT RATE>OD account such that the interest rate of OD account should be greater than the TDR account in
5671 INTT RATE Limit order to avoid the error.
The mentioned error "5706: APPROPRIATION DATE < LOCK­IN PERIOD" comes when the
APPROPRIATION DATE branch is feeding the appropriation date less than the lockin period. B ranch needs to do the
5706 < LOCK­IN PERIOD Subsidy transaction following above validation to avoid the error.
INTEREST TO BE Before written off of PB/RD accounts, if there are accruals present in the account then branch
FORCED CAPATILIZED needs to adjust the accruals to avoid the error. In cas e supervisary error comes then branch
5719 FIRST Recalled asset needs to provide supervisary override while accrual adjustment.
The mentioned issue present if cheque book instruemnt type which branch is trying to issue
cheuqe book on account , there is no entry of the product o f account with cheque instruemnt
type in SANP parameter table for the branch . Take up the issue with SBI BOG team for setting
SAN RANGE IS the parameters in SANP parameter table for branch level SAN setting for cheque book instruemnt
5735 EXPIRED Cheque Issueance type.
 As per the existing functionality, the error "5832: WRITE OFF NOT ALLOWED (DICGC/ECGC/
WRITE OFF NOT CGA CLAIM >= OUTSTANDING" comes while write off the accounts if the account is not in debit
ALLOWED (DICGC/ balance. As per the functionality, the account can be written off only if it is in debit balance.
ECGC/CGA CLAIM >= Branch can debit the account with such amount that the current balance of account becomes
5832 OUTSTANDING Writeoff debit balance and then try the write off transaction.
The error "5862: ADVANCE NOT ALLWD BEFORE REPAY SCHED GENERATION / NOT A DL/
ADVANCE NOT ALLWD TL" comes when the repayment schedule for any account doesn't exist. This may be due to
BEFORE REPAY repayment schedule has not migrated for migrated accounts and repayment schedule has not
SCHED GENERATION / created for core opened accounts. Branch nee ds to create the repayment schedule before doing
5862 NOT A DL/TL Repayment schedule required transaction in order to avoid the error.
Until the Old IRAC status of account is NPA i.e. 04/05/06/07/08, system will not allow debit in the
account with the error “5866: DEBIT TO AN NPA ACCO UNT”. Old IRAC status changes as per
DEBIT TO AN NPA new IRAC status on month end/Quarter end ( whichever is applicable ). Once old IRAC status will
5866 ACCOUNT NPA Tracking be less than 0 4, branch will be able to do the required debit transaction.
As per the existing functionality, if the multiclaim flag at product level for the subsidy scheme
under which subsidy has given, is 'N' then subsidy c an be claimed only once in the account. If
branch has claimed the subsidy and then they have rejected the subsidy and after that once
SUBSIDY ALREADY again branch tries to claim the subsidy, system will not allow the same and will through the error
5882 CLAIMED Subsidy "5882: SUBSIDY ALREADY CLAIMED".
While product change of any account error "5899: PRODUCT CLOSE NEW ACCOUNT
PRODUCT CLOSE NEW OPENING/PRODUCT CHANGE NOT ALLOWED" comes if the required product i.e. the product
ACCOUNT OPENING/ in which branch is trying to change has closed or does not exist. Hence branch will not be able to
PRODUCT CHANGE Product change, Segment change the product into the required pro duct that they are entering in the screen of product
5899 NOT ALLOWED code change change.
As per the existing functionality, for maxgain accounts system picks the limit reduction amount
from the principal portion of the created repayment sc hedule. Branch can enquire the repayment
schedule in order to verify the same at their end. Also system does not allow the change in limit
reduction a mount from the branch end. In case branch is facing the problem in limit or interest
FOR MAXIGAIN rate amendment in screen 7009 and they do not want to amend th e limit reduction amount then
ACCOUNTS LIMIT they can do the required transaction leaving the default values of limit reduction details. In case
REDUCTION DETAILS Maxgain account, Limit, branch is having issue related with limit reduction amount then they can refer the matter to
5913 CANNOT BE ENTERED Drawing Power Service Desk for further analysis.
As per the existing functionality, system does not allow backdating if the previous backdated
adjustement is not posted at the account level i.e.any o f the previous backdating request of
account is in 05: PROCESSED BUT NOT POSTED status. Hence system throws error "5962:
BACK DATED TXNS EXISTS­ MANNU AL ACTION REQUIRED". Branch needs to change the
BACK DATED TXNS status of the request to '01': Failed or '09': Processed successfully as per their requirement. If
EXISTS­ MANNUAL branch chooses 09: Processed successfully status then they have to manually post the
5962 ACTION REQUIRED Backdating adjustment amount to account as well.
 The above mentioned error EXCEEDS CHQ LIMITS FOR CCOD LIMITS will come if the value of
the field threshold cheuqe limit in additinal deposite details table is less than cheque amount. For
setting the threshold cheuqe limit in additinal deposite details table for a particular account the
follwing n avigation should be used 1)screen 7050 and the option J.ADDITIONAL CC/OD
EXCEEDS CHQ LIMITS DETAILS.Then the next screen \\ SCR:002015 Deposits: Record additional detail s for CC / OD
5979 FOR CCOD ACCTS Cheque Payment accounts will be scheduled.In that screen BPR Threshold Amount can be set.
The branch has manually replaced the ATM card(through the screen 9584) to the customers
created through the welcome kits before issuing the welcome ki ts to the customers. Hence when
they are making the flag "Welcome Kit Issued" as Y in the screen 7000 Amend Deposit Tabbed
screen, they are getting the error 5988 . Since the status of the ATM card manually issued on
account, the branch will not be able to issue the welcome kits to the customers. Hence the
branch needs to disregard the welcome kits and issue a new range of welcome kits to the
customers. The ATM cards already issued to the c ustomers will not be effective as the customer
NO MESSAGE TO will not be able to use them. Also please ask the branch not to amend the ATM card details
5988 DISPALY Welcome Kit manually b efore issuing the welcome kits to the customers henceforth.
REPAYMENT This error "6082 REPAYMENT SCHEDULE ALREADY CREATED" comes when the repayment
SCHEDULE ALREADY schedule already exists for the mentioned account. In such case branch s hould amend the
6082 CREATED Repayment schedule repayment schedule instead of creation, if required.
PAY LIMIT NOT Take up the issue with SBI­BOG team to check whether the entry of Drawee Branch of IOI isue
MAINTAIN FOR PAY properly present in parameter table BRSD and BRHM for IOI payment details related fields . If
6115 BRANCH IOI Issueance still issue persist escalate the issue to TCS L2 team
A new functionality has introduced after promotion of IR 75919 on 18­OCT­2015. Now set rate
interest rate option is available for CC/OD accounts and r ate increment/decrement that can be
given in a CC/OD account have parameterized. This has handled at product level by the
functionality of negotiable rate indicator at product level. Here is the definition of different
negotiable rate indicators: 0 or space: Product default interest rate applic able, no account level
rate increment or set rate can be given 1: Product default interest rate applicable, account level
rate increment possible, ac count level set rate not possible 2: Product default interest rate
applicable, account level rate increment not possible, account level set rate poss ible 3: Product
default interest rate applicable, account level rate increment and account level set rate possible
but should be between high and low rate increment set at product level. Hence, error "6167: Set
Set Rate not allowed as Rate not allowed as per the product parameters" will come if for underlying product n egotiable
per the product rate indicator is 0 or space or 1 and branch is trying to give set rate for the account. Hence, in
6167 parameters Limit, Interest rate such case system will not allow set ra te as the same is not allowed due to product parameters.
 A new functionality has introduced after promotion of IR 75919 on 18­OCT­2015. Now set rate
interest rate option is available for CC/OD accounts and r ate increment/decrement that can be
given in a CC/OD account have parameterized. This has handled at product level by the
functionality of negotiable rate indicator at product level. Here is the definition of different
negotiable rate indicators: 0 or space: Product default interest rate applic able, no account level
rate increment or set rate can be given 1: Product default interest rate applicable, account level
rate increment possible, ac count level set rate not possible 2: Product default interest rate
applicable, account level rate increment not possible, account level set rate poss ible 3: Product
default interest rate applicable, account level rate increment and account level set rate possible
but should be between high and low rate increment set at product level. Hence, error "6168:
Increment/Decrement not allowed as per the product parameters" will come if for underlyin g
Increment/Decrement product negotiable rate indicator is 0 or space or 2 and branch is trying to give rate increment for
not allowed as per the the account. Hence, in such case system will not allow rate increment as the same is not allowed
6168 product parameters Limit, Interest rate due to product parameters.
As per the functionality introduced under IR 75892, Unconditional Cancelability of Limits flag
should be 'Y' or 'N' in CISLA details for the CIF. IR D escription :"UCC flag will be a mandatory
field, wherein teller would not be able to proceed further, without selecting 'Yes' or 'No' from the
drop do wn." If this field is space then system throws the error "6179: Set UCC Flag in CIF
CISLA screen" while approving the limit of CC/OD and loan account. So branch needs to amend
the Unconditional Cancelability of Limits flag to 'Y' or 'N' as per their requirement. The path is:
Common processing ­­> Cisla2 (067153: Create/Amend/Enquire CIS/BASEL/RESTRUCTURE I)
Set UCC Flag in CIF ­­> Capital Adequacy Details. The field is Unconditional Cancelability of Limits. After amendment
6179 CISLA screen Limit of the same branch will be able to approve the loan/CCOD limit.
How many times branch can appropriate subsidy in any account is depend on the product
parameter multi appropriation allow flag at product level of sub sidy scheme under which subsidy
has given for the account. If multi appropriation allow flag at subsidy product level is 'Y' then only
branch can a ppropriate subsidy more than once. If multi appropriation allow flag at subsidy
MULTIPLE product level is 'N' then system will not allow subsidy appropriat ion more than once with the error
APPROPRIATION NOT "6192: MULTIPLE APPROPRIATIONS NOT ALLOWED". Hence to avoid such errors branch
6192 ALLOWED Subsidy needs to appropriate full subsidy amount in one time.
The mentioned error '6359: Manual change by teller not allowed for New Account' is encountered
MANUAL CHANGE BY when the branch is trying to remove posting restriction s from the account which is within the
TELLER NOT posting restriction period for that product. There is a predefined posting restriction period set for a
ALLOWED FOR NEW A/ account at the product level. The branch will not be able to amend the posting restrictions set on
6359 C Account Level Amendment the account before completion of the restriction period.
 An IR 73710 has PROD PROMOTED on 08/02/2014. IR DESC: "Internal: NPA Holiday
functionality to be parameterised." After promotion of this IR branch can not amend the holiday in
case of NPA accounts and those accounts where the product under which the mentioned account
is opened, do not have entry in the holiday parameter table or the NPA holiday allow flag is set as
'N' in the holiday parameter table. If at product level, NPA holiday is ap plicable but account is
NO HOLIDAY ON NPA NPA and branch tries to create/amend NPA holiday then system doesn't allow the same and
6659 ACCOUNT NPA Tracking throws the error “6659: NO HOLIDAY ON NPA ACCOUNT”.
In case old IRAC status of account is 04 or greater than 04 and branch tries to do interest
adjustment then system will not allow the same with the er ror “6680: INVALID TRANSACTION
INVALID ON NPA ACCOUNT”. Old IRAC status changes as per new IRAC status on month end/Quarter
TRANSACTION ON end ( whichever is applicable ) . Once old IRAC status will be less than 04, branch will be able to
6680 NPA ACCOUNT NPA Tracking do the required transaction.
Before closing the loan/ccod account it is mandatory to delink all the linked collateral and
authorize the same. So before trying the closure transac tion branch should enquire the linked
collaterals .If any of the collateral was not delinked by the branch then the branch will face this
error “6683 : COLLATERAL LINKED TO THE ACCOUNT ”. So the branch should delink the
collaterals through screen (screen nevigation as mentioned above) \\ SCR:0670 90 CIF: Amend/
Enquire Collateral,And make the DP PERCENT as zero, link flag as "N".Then authorize the
COLLATERAL LINKED collateral through screen \\ SCR:067158 CIF: A uthorize Collateral. After that branch will be able
6683 TO THE ACCOUNT Collateral to close the account.
This error is encountered if the branch has delinked the collateral but do not authorize the same.
DELINKED So it is mandatory to authorize the collateral afte r delink the collateral. So, branch should
COLLATERAL IS NOT authorize the collateral using screen no \\ SCR:067158 CIF: Authorize Collateral (screen
6684 AUTHORISED Collateral nevigation as men tioned above) and then try the closure transaction.
At the time of hold removal from TDR account error "6685: No message to display" comes when
the branch has delinked the TDR account from collateral, b ut they have not authorised the
collateral. Branch can authorize the collateral through screen \\ SCR:067158 CIF: Authorize
Collateral. After autho rize the collateral the branch will be able to remove the hold from the
6685 No message to display Hold due to Collateral account
After promotion of IR 70426, it is compulsory to complete subsidy processing then only system
allows credit/closure transactions in the account i.e. i f for Upfront type subsidy, subsidy is in
claimed status and for Backend type subsidy, subsidy is in received status but the same has not
fully approp riated then the error will come. Hence, completion of subsidy processing i.e.
appropriation of full amount is required to avoid the error. Branch n eeds to appropriate the
Please do appropriation subsidy then only system will allow any other credit/closure transaction. Navigation for the
of receipt amount before subsidy appropriation is : 1) DL/TL Accounts & Services 2) Loan Processing 3) Subsidy
6690 closure Subsidy Processing 4) Enter Account No and select A:Appropriation from drop down menu.
 A restriction has applied after the promotion of IR 73521 on 23­NOV­2013. IR description:
"Internal: Minimum and maximum cap for Interest rate incr ement / decrement value to be
parameterised." While approving the limit system will validate the interest rate of the account in
respect of high in terest rate and low interest rate of the underlying product. If branch is entering
the set rate or they are giving rate increment/decrement for the ac count in the limit approval
INTEREST RATE IS screen and the entered set rate or rate increment/decrement is such that the interest rate of the
NOT BETWEEN MIN account is not in the ra nge of high interest rate and low interest rate of the underlying product
AND MAX RATE then the error will come. Branch needs to perform the transaction with fo llowing above validation
6693 RANGE Limit, Interest rate to avoid the error.
As per the existing functionality, the branch can generate the request of product change for only
fixed rate product to floating rate product using sc reen \\ SCR:031669 Loans: To generate the
request for product change. If existing product of account is a floating rate product then branch
OLD PRODUCT IS A can not generate product change request from screen 031669. They can change the product from
FLOATING RATE Product change, Switchover screen no. \\ SCR:017050 Loans: Change Details through loan trac king by selecting option 5: A/
6719 PRODUCT fixed to floating C type/home branch change.
After promotion of IR 75177 on 18­OCT­2015 home branch change of loan and CC/OD and current
account with od 'Y' accounts has restrcited to the level o f LHO only. Branches can generate
request for home branch change at their end using screen \\ SCR:031669 Loans: To generate the
request for product/br anch change. This screen is for branches other than CPC/RACPC and
SMECC branches. CPC/RACPC and SMECC branches can directly change the home branch
from previous home branch change screen i.e. for current/CC/OD accounts using screen \\ SCR:
007050 Deposits: Change Details and for loan account scree n \\ SCR:017050 Loans: Change
FUNCTIONALITY NOT Details (through loan tracking by the option "5:A/C Type ­Home Branch Change" in screen
AVAILBLE TO CPC / 017050). These branches don't ne ed to generate request for home branch change using screen \\
6722 RACPC and SMECC Home branch change SCR:031669 Loans: To generate the request for product/branch change.
After promotion of IR 75177 on 18­OCT­2015 home branch change of loan and CC/OD and current
account with od 'Y' accounts has restricted to the level o f LHO only. Branches can generate
request for home branch change at their end using screen \\ SCR:031669 Loans: To generate the
request for product/br anch change. Capability level at Branch for this transaction will be 7 and
FUNCTIONALITY NOT group no 12 and above and the menu will be made available to user type 1. After generating the
AVAILBLE TO THE home branch change request at branch end, please take up the issue with respective LHO for
BRANCH. PLEASE GO authorization of the request. After LHO will authorize the request, home branch of the account will
6724 TO SCREEN 31669 Home branch change change.
An IR 73710 has PROD PROMOTED on 08/02/2014. IR DESC: "Internal: NPA Holiday
functionality to be parameterised." After promotion of this IR branch can not amend the holiday in
case of NPA accounts and those accounts where the product under which the mentioned account
is opened, do not have entry in the holiday parameter table or the NPA holiday allow flag is set as
NPA HOLIDAY NOT 'N' in the holiday parameter table. If at product level, NPA holiday is not applicable and branch
ALLOWED FOR THIS tries to create/amend NPA holiday then system doesn't allow the same and throws the error
6759 PRODUCT NPA Tracking “6759: NPA HOLIDAY NOT ALLOWED FOR TH IS PRODUCT”.
 As per the functionality, the error "7002: ROC FLAG MUST BE Y FOR COMPANIES" comes
when the value for ROC flag is N for the non personal customers whi le amending/creating
ROC FLAG MUST BE Y collateral. Hence, branch needs to select the ROC flag as 'Y' and give ROC file date and ROC
7002 FOR COMPANIES Collateral created date as per the branch re quirement and than they can amend the collateral.
As per the functionality, the error "7002: ROC FLAG MUST BE Y FOR COMPANIES" comes
ROC FLAG MUST BE N when the value for ROC flag is 'Y' for the personal customers while amending/creating collateral.
7003 FOR NON COMPANIES Collateral Hence, branch needs to select the ROC flag as 'N' and than they can amend the collateral.
After prodpromotion of IR: 74681, 75354 on 11­OCT­2014, it is compulsory to first make the TDR
account and collateral linking status as 09: Inactive t hen only system will allow hold removal
from TDR account. So, now branch needs to make the TDR account and collateral linking status
as 09: Inactiv e at their end. For the same branch can follow the instructions: 1. Go to screen
Menu: DL/ TL Accounts & Services ­> Security (Primary/ Collateral) ­> Customer ­> Amend/
Enquire/Authorize ­> Amend/Enquire Collateral. The screen “\\ SCR:067090 CIF: Amend/Enquire
Collateral” appears. Fill the Collat eral Number and Transmit. Screen No 67040 will be scheduled.
2. Select Action as D:Details and Click on Transmit. Screen 67141 will display. 3. In Screen
67141, Select Action A:Amend, Select Status 09:Inactive for perticular STDR and Click on
Transmit. 4. Choose Menu: DL/ TL Accounts & Services ­> Security (Primary/ Collateral) ­>
Customer ­> Amend/Enquire/Authorize ­> Authorize Security. Screen \\ SCR:067158 CIF:
Authorize Collateral appear s. Enter the Collateral Number, noted down in the previous step while
entering the Security details, and click on “Transmit”. Screen \\ SCR:067157 C IF: Authorize
Collateral appear. Step 5: Select “Action” as “U:Authorize”. The authorising officer has to Input
his/ her “Password” and Click on “Tra nsmit. Repeat the process for all the collaterals linked with
TDR/STDR account. After making the TDR account and collateral linking status as 09 : Inactive
Pl go to scr no. 67141 branch will be able to remove the hold from the mentioned account. In case error persists issue
and make status as 09 can be referred to the Service Desk to know collateral no with which the TDR/STDR account is
7017 (inactve) Hold due to Collateral linked.
ATM ALREADY ISSUED The mentioned message "7053:ATM ALREADY ISSUED TO CUSTOMER" comes when branch
7053 TO CUSTOMER ATM is trying to issue an ATM card type which is already issued to the cust omer.
In case old IRAC status of account is 04 or greater than 04 and branch tries to do force
CAN NOT DO FORCE capitalisation then system will not allow the same with the e rror “7054: CAN NOT DO FORCE
CAPITALISATION FOR CAPITALISATION FOR PB/RD/NPA ACCOUNTS”. Old IRAC status changes as per new IRAC
PB/RD/NPA status on month end/Quarter end ( whic hever is applicable ). Once old IRAC status will be less
7054 ACCOUNTS NPA Tracking than 04, branch will be able to do the required transaction.
The mentioned Error is thrown if the teller which is performing teh trasnction is not allocated to
TELLER NOT ALLOTED ACCOUNT MANAGEMENT GROUP. Please advise the BOG t o use the Screen NO :031527
TO ACCOUNT ACCOUNT MANAGEMENT CLEARING: Account Management Group which is available to the Parameter Teller of user type
7091 MANAGEMENT GROUP GROUP '5' . Advise the branch to all ocate the teller to that group and after that try to do the transaction.
 NON­HOME BRANCH Only home branch of the collateral is allowed to perform the transaction in the collateral if any
TXN NOT ALLOWED other branch tries any transaction they will face an error “7121: NON­HOME BRANCH TXN NOT
( while amending the ALLOWED”. So home branch can do the transaction and in case where the home branch of the
7121 collateral ) Collateral security is not live re fer the issue to service desk.
For every branch there is a specific IFSC code set which is enabled for RTGS and if the branch
is trying to enter IFSC code other than this ,the branc h will face the error 'Invalid IFSC'. In this
case kindly ask the branch to feed the correct IFSC code and then try the transaction. In case
INVALID RECEIVER the branc h is still facing further issue, ask the branch to revert with full screenshots displaying
7133 IFSC CODE Internet Banking the values entered and error message, so that further analy sis can be provided by the L2 team.
ALREADY ISSUED
7144 CHEQUE RANGE Cheque Issueance Escalate the issue to TCS L2 team for datafix
INSTRUMENT TYPE
DIFFERENT FROM For each product only one type of cheuqe book can be issued . If branch is trying to issue
EARLIER ISSUED cheuqe book type which is different from type of cheque bo ok set at product level then the error
7166 INSTRUMENT TYPE Cheque Issueance occurs . If still issue persist then escalate the issue to TCS L2 team
In case of ATM issuance for business cards the branch is faces the error "7197: invalid roll no/
inst code/fourth line data" due to IR­72920. IR DESC:A TM : Business Debit cards should be
made available for jointly operated account also. Further, the fourth line data capture should also
be enable for these cards.
****************************************************************************************************************
Individual name would ap pear as Emboss name and Company’s name will be input by the teller
manually in 4th line data. The validation of non­retail customer type for Business Debit Card
would be against the primary CIF of the account which is going to be linked. If the teller selects
Invalid roll no/inst code/ the account other than the account where Company is not the owner of the account business
7197 fourth line data ATM debit card should not be allowed to be issued.
After promotion of IR 75683 on 22­NOV­2015, a new screen has developed for conversion of
existing Home Loan (DL/TL) to Quick Max Gain (OD) account. Functionality is such that only
ONLY FULLY Fully disbursed loan accounts can be converted into maxgain accounts. For the loan accounts
DISBURSED LOAN Loan to maxgain having status other than Fully disbursed system throws the error "7231: ONLY FULLY
ACCOUNT ARE conversion, Maxgain DISBURSED LOAN ACCOUNT ARE ALLOWED" while converting this HL account into maxgain
7231 ALLOWED account account.
VALUATION REPORT As per the functionality introduced under IR 76160, for collateral type 1 and 2 branch can't enter
DATE CANNOT BE the valuation report date/stock commencement date b efore 3 years from date of transaction.
PAST DATE Hence, branch needs to give valuation report date/stock commencement date which is not before
7233 EXCEEDING 3 YE Collateral 3 years.
Pl cancel all active The error "7243: Pl cancel all active PDCs attached to this account" comes when there active
PDCs attached to this PDCs linked with the account. Branch needs to cancel a ll such PDCs, which are in recorded
7243 account Writeoff, Closure status. Issue can be referred to the Service Desk to know the PDCs no.
 The branch faces the error "7260: Customer is deceased" when the death date of the customer of
the account is populated as some junk value . Kindly as k the branch to make death date field
blank by the following the mentioned steps Customer Management >> The branch facesthe error
"7260: CUST OMER IS DECEASED" as the death date of the customer might be populated with
some junk value. Branch have to make death date field blank by the followi ng the mentioned
steps "Customer Management >> Ammend >> Customer Details >> 5:Personal Details " and
then try to issue ATM card for the accoun t. In case any issue faced then take up the issue with
7260 Customer is deceased ATM L2 Team.
The mentioned error "7268 : card type not issued to customer" comes when there is no ATM card
of a particular type issued to the customer and the bran ch is selecting option "R: Replace" for
Card type not issued to the ATM CARD type which is not issued for the customer. Ask the branch to select the card
7268 customer ATM status as "N: New" a nd not "R: Replace" in the screen SCR//9584 in such a case.
While amendment of limit expiry date, error "7298: CTA EXPIRY DATE > FACILITY END DATE"
comes when the expiry date extered by the branch exceeds the f acility expiry date of the
customer i.e. limit expiry date for any account can't be given after the facility expiry date of
customer. Branch can am end facility expiry date of customer at their end as per their
CTA EXPIRY DATE > requirement in order to avoid the error else they can enter the limit expiry date for a ny account
7298 FACILITY END DATE Limit only less than the facility expiry date of customer.
As per our the existing functionality, the mentioned error "7335: Adjustment not allowed.
Repayment schedule expired." comes when the repayment schedu le of the account has expired
and branch is trying to adjust the arrear amount. This functionality has introduced under IR 75243
promoted on 10­MAY ­2015, IR Description: "Theo balance of the account should not be allowed
to increase after the expiry of term of the accounts." The solution for s uch situation is to delete
the repayment shedule from back end and then generate the same at branch end. For deletion of
repayment shedule from backen d controller approval is needed. Issue needs to be referred to the
Service Desk with controller approval if branch wants the above mentioned soluti on. Also before
Adjustment not allowed. that please note that the repayment shedule from backend will only be deleted, if loan terms of
Repayment schedule the account have not yet expired. If l oan terms have expired then system will not allow creation
7335 expired NPA Tracking of repayment shedule even after the same will be deleted from backend.
The mentioned error occurs when the account is opened under a product for which the SMS
SMS NOT ENABLE facility is not set at parameter level and thus the sms facili ty can not be made available for that
7340 FOR THIS PRODUCT SMS account.
The mentioned error "7341:THRESHOLD VALUE CANNOT BE GREATER THAN PRODUCT
PARAMETER" comes when the branch feeds SMS Threshold Balance Value greater th an the
THRESHOLD VALUE value set at the parameter level for that product. If so is the case then the branch has to be
CANNOT BE GREATER advised to set the SMS Threshold Balance less th an the parameter value. In case branch wants
THAN PRODUCT to deactivate the same the branch can deactivate it from their own end from screen SCR//
7341 PARAMETER SMS 7000(amend Deposi ts Tabbed screen).
The error "7435: SI exists" comes when there are active SI in the account. Branch needs to
7435 SI exists Writeoff, Closure remove all the SI at their end before Writeoff/Closure of t he account.
 Error "7465: TRANSFER ACCOUNT EXISTS FOR THE LOAN ACCOUNT" comes when there is
transfer account present in the loan account. Branch can remove the same through loan tracking
TRANSFER ACCOUNT ­­>> \\ SCR:017050 Loans: Change Details ­­>> Select option 1: Normal Details and Transmit ­­
EXISTS FOR THE >> screen \\ SCR:017000 Loans: Amend Loan Details ­­>> select Int Code: as :No interest
7465 LOAN ACCOUNT Writeoff, Closure transfer and transfer account as 0 and click transmit.
The error "7486: INVALID REPAYMENT DATE" comes when the branch tries to create/amend the
repayment schedule with the start as less then the sum of per iod of moratorium term and course
term. For example if for any account the moratorium period is 12 months and the course term is
INVALID REPAYMENT 36 months then bra nch can't create/amend the repayment schedule with the start date as less
7486 DATE Repayment schedule than 48 months from disbursement schedule creation date of that account.
Reason: If there is no such entry in the segment code parameter table for the product type and
segment code and policy type combination for insurance policy then the error comes when
PRODUCT/SEGMENT branch is trying to choose a policy type. Solution: Please select appropritae policy type for the
NOT ENABLED FOR product type and segment code and policy type combination.L2 Team can assist in selecting
7531 THIS TYPE OF POLICY INSURANCE POLICY proper type.
Due to promotion on 08/02/2014 for IR 74169 , The manual transaction on BGL accounts were
blocked with error : 7557 : Manual Posting not allowed . For allowing manual trasnaction on BGL ,
take up the issue with SBI BOG team . Ask BOG team to go to screen \\ SCR:027050 GL /
Manual posting not Nostro Account ­ Ame nd . Afetr that screen \\ SCR:027000 G/L: Maintenance . In the screen
7557 allowed BGL Ask BOG to make Spaces to dropdown Special Function Indicator field .
The mentioned error occurs when for the account number the REMARKS column in CBS
Database is wrongly populated. Branch faces error: " 7669 ­ NOMINEE N OT PROVIDED FOR
THIS ACCOUNT " while providing the nominee detail using screen " \\ SCR:007050 Deposits:
Change Details ". To fix this, corresponding entry in CBS Database need to be deleted. This
issue requires changes for the same and a DATAFIX will be provided by the L2 team to delete
entries fro m CBS Database . After execution of the provided script ask the branch go to screen
7000 (Use Deposit/CC/OD Accounts & Services Option from CBS MAIN M ENU then use Amend
NOMINEE NOT Option and then use Amend Deposit Tabbed Screen Option). Thereby kindly ask the branch to
PROVIDED FOR THIS set the nomination flag to 'Y'. After tha t ask the branch to use screen 7050 to fill the nomination
7669 ACCOUNT Nominee detail.
An IR 75735 has promoted and a field named as security flag at product level has introduced.
The possible values and significances of this field are: 01: Allow limit approval without security
02: Do not allow limit approval without security 03: Allow limit approval without security with
supervi sor override 04: Check security and security value prior to limit approval 05: Security
Create/authorise security Account opening, Loan cannot be attached. Hence, if security flag is 02 or 04 a t product level, branch has to create the
7677 before approval approval, Limit collaterals greater than the limit/loan amount before approval of limit/loan.
 An IR 72633 was promoted on 11/08/2012 under which it was made mandatory to transfer
accounts to corresponding Base Rate product at the time of limit amendment. Else the error
AMENDMENT NOT "7703: AMENDMENT NOT ALLOWED. FIRST TRANSFER THE ACCOUNT TO
ALLOWED. FIRST CORRESPONDING" comes while limit amendment. Thus branch needs to transfer the account
TRANSFER THE into base product before making any limit amendment. To transfer the account into base product,
ACCOUNT TO branch can navigate to screen \\ SCR:007050 Deposits: Change Details and select X: Transfer to
7703 CORRESPONDING Limit Base product and Transmit, then try limit amendment transaction.
Txn not allowed on
Limited Access transctionon account not The branch to go the screen "7000:Amend Deposit tabbed screen" and in Miscellaneous tabbed
7774 Accounts allowed screen and set LIMITED ACCESS flag as "N:No" for given ac count.
While amendment of IRAC status at branch end error "7775: THE ARREAR CONDITION
ENTERED DOES NOT MATCH WITH THE RESULTANT IR" comes when the arrear act ion
THE ARREAR required for tracking the account for entered "New Bad Debt Indicator" in screen does not match
CONDITION ENTERED with the arrear action selected for "Reason for ch ange" in the same screen. For example if
DOES NOT MATCH branch is selecting the "New Bad Debt Indicator" as 04 then in the same screen in field "Reason
WITH THE RESULTANT for change " they must select the arrear condition which triggers IRAC status 04 like 704 or 506
7775 IR NPA Tracking arrear conditions. Otherwise this error will come.
A restriction has applied after the promotion of IR 73521 on 23­NOV­2013. IR description
"Internal: Minimum and maximum cap for Interest rate incre ment / decrement value to be
parameterised." Hence, as per the functionality introduced under this IR, rate increment that can
be given for any acc ount must be between minimum rate increment and maximum rate
increment set at underlying product level. If branch tries to give the rate increment beyond the
minimum rate increment and maximum rate increment set at product level, then error "7776:
Increment not in Increment not in prescribed range" comes. Hence, branch needs to follow this validation in order
7776 prescribed range Interest rate to avoid the error.
As per the existing functionality one loan account can only be linked with one suraksha account.
In case a HL account is already linked with any surak sha account and branch tries to link the HL
account with another suraksha account then error "7811: AMENDMENT NOT ALLOWED". In
such case if branch wants they can close the existing suraksha account and hence link the HL
account with new suraksha account. If existing suraksha account is already cl osed and still
AMENDMENT NOT branch is facing the error then branch can make a request to Service Desk to delink the relation
7811 ALLOWED Suraksha account of existing suraksha account with HL a ccount from backend.
As per the functionality, the product of home loan account should be mapped to the product of
suraksha account in suraksha housing loan parameter reco rds and should be in active status.
HLHP MAPPING NOT Then only system allows the linking of home loan account with the suraksha account. The
AVAILABLE FOR THIS validation is as per th e product parameter and hence branch needs to follow the same in order to
7812 HL PRODUCT Suraksha account avoid the error.
 The mentioned error occurs when the branch is trying to issue ATM card to the mentioned
account and the selected card type is not allowed for that pro duct . Additionally, bulk list of card
NRO & NRE­CHQ/ type which is NOT allowed for NRO account is VGY,VGE,PVZ,MGP,MGS,PMQ. However, in
DOMESTIC CHQ A/C order to get the correct card type to be issued under the product code the issue can be taken up
7816 CANNOT BE ATM with the Functional team.
As per the functionality, the home branch of the LC/BG/AUCA accounts can not be changed at
HOME BRANCH branch end. Only for AUCA accounts, branch can refer the matter with Service Desk with
CHANGE NOT AUCA, Home branch controller approval for home branch change from backend. For LC/BG account home branch
7844 ALLOWED change, Contigent accounts change can't be done from bac kend as well.
As per the existing functionality, branch can give subvention in any account upto the maximum
Subvention period subvention terms defined at product level. Else the erro r "7889: Subvention period exceeds
exceeds maximum maximum subvention term" while giving subvention. If the maximum subvention terms are 000 at
7889 subvention term Subvention product level then branch will not be able to give subvention for the account.
As per the existing system, the home branch change/product code/segment code change in
Overdraft account is only allowed when its lending status is '0
3:Approved','05:Accepted','08:Advanced','90:Limit Expired'. For the lending status of the account
other than above lending status, system doesn't allow home branch change in the account and
7908 LIMIT NOT APPROVED Limit throws the error "7908: LIMIT NOT APPROVED".
As per the existing functionality, the system will not allow segment code or product change if the
account is either linked as loan account or insuran ce account with any account and throws the
Product change not error "7914: Product change not allowed for Surasha linked A/c's". Hence, segment code or
allowed for suraksha Product change, Suraksha product change is restricted for accounts linked as loan account or insurance account with any
7914 linked A/Cs account, Recalled asset account.
The mentioned error comes during Sweep execution when the Sweep/MOD product set for the
account is already inactive. The branch should set the new Swe ep/MOD product using screen \\
INVALID ACCT SCR: 007000 Amend Deposit Details and by selecting correct "Saving Plus Acct Type" and
9199 STATUS/TYPE Sweep "Savings Plus Sub Category".
As per the functionality incorporated in the IR 72879 , In case of RTGS and NEFT transaction the
commission amount should be populated in the commissi on field automatically once the teller
tabs out from the transaction amount field. The commission amount should be fetched from
commission database ta ble based on the value band in which the transaction amount is falling
in.Once the commission amount is populated in the commission amount field of re spective
RTGS/NEFT transaction screen; the same commission amount will be editable. Thereafter when
9721 COMMISSION the transaction will be transmitted; in CBS the co mmission amount received will be validated.
AMOUNT EXCEEDS The commission received from RTGS/NEFT channels should never exceed the maximum
9721 MAXIMUM LIMIT.txt NEFT/RTGS commission defined in the database for the respective channels.