This chapter contains the following sections:
Error Code |
Message |
BC-00200 |
At least one status has to be defined |
BC-00201 |
Status already exists |
BC-00202 |
Contracts with $1 status exist. The status cannot be deleted |
BC-00203 |
Status and status sequence cannot be null or 0 |
BC-00204 |
Status with this sequence number already exists. Do you want to shift the existing status? |
BC-00205 |
Status shift down failed |
BC-00206 |
Transfer days should be more than $1 days |
BC-00207 |
Transfer days should be less than $1 days |
BC-00208 |
Component is missing for status |
BC-00209 |
$1 is missing |
BC-00210 |
Duplicates exist |
BC-00211 |
Stop accrual has not been set |
BC-00212 |
Interest components cannot exist for a collection operation. |
BC-00213 |
Accrual start month is missing |
BC-00214 |
Accrual start day is missing |
BC-00215 |
Min tenor should be less than or equal to standard tenor, which in turn has to be less than or equal to Max tenor. |
BC-00216 |
Details of product preference screen have not be entered. Product cannot be saved without preference screen details. |
BC-00217 |
Status with status sequence =0 can be defined for only norm status. |
BC-00218 |
ICCF components have not been defined for this product |
BC-00219 |
Transfer GL cannot be duplicated. |
BC-00220 |
Their charges have not been maintained. Do you want to maintain them? |
BC-00221 |
Product code not unique |
BC-00222 |
Product code should be at least 4 characters long |
BC-00223 |
Status sequence cannot be 0 |
BC-00224 |
Their charges component has been deleted for the product |
BC-00225 |
Income/expense accounting roles cannot be defined for their charge component |
BC-00226 |
Are you sure that the product is to be back-valued? |
BC-00227 |
This product has more than two their charge components defined. Do you want to still proceed? |
BC-00228 |
Mandatory (or not null) fields are null. |
BC-00229 |
Advices have not been maintained for events. Input to FFT and instructions not allowed. |
BC-00230 |
Stop accruals field will be marked for all subsequent statuses. Do you still want to proceed? |
BC-00231 |
The stop accruals field for the present status cannot be changed as previous statuses with stop accruals field marked yes exist. |
BC-00232 |
Preferred tracer medium cannot be null. |
BC-00233 |
The operation has to be defined first. |
BC-00234 |
Product end date cannot be less than today |
BC-00235 |
No components defined for the status |
BC-00236 |
The LOV does not have any valid values |
BC-00237 |
Status sequence cannot be duplicated |
BC-00238 |
An accounting head has to be defined for every accounting role. |
BC-00239 |
Product code should have at least one non-numeric character. |
BC-00240 |
Product code cannot start with the alphabet z. |
BC-00241 |
Transfer days have not been defined |
BC-00242 |
Product code should contain only a-z and 0-9 characters only. |
BC-00243 |
Reverse accruals can be set only if a status with a lesser sequence number has stop accruals set to yes. |
BC-00244 |
The advice code linked to instruction codes have not been defined for any events of the product. |
BC-00245 |
The advice code linked to free format text codes have not been defined for any events of the product. |
BC-00246 |
The advice code linked to status codes in status screen have not been defined for the event STCH of the product. |
BC-00247 |
At least one interest component has to be shown on the contract main screen if any of them are defined for the product |
BC-00248 |
If ICCF components are collected in advance then interest component $1 linked to a floating rate code is not allowed. |
BC-00249 |
No BC product records have been maintained. |
BC-00250 |
Cannot reopen a closed product |
BC-00251 |
Active contract exists for this product. Cannot be closed. |
BC-00252 |
If the tracer generation is not required then preferred tracer medium has to be null and tracer start day has to be 0 |
BC-00253 |
$1 should be used for defining either credit or debit accounting entries for BC customer/nostro account but not both |
BC-00255 |
Tracer generation frequency cannot be 0 |
BC-00256 |
Collection bills can have interest components defined only for BPUR event. |
BC-00257 |
For a usance bill all the tenors (MIN, STD, MAX) should be greater than zero |
BC-AC001 |
Accruals failed for bills & collections contract reference number $1 |
BC-AC002 |
Accrual level not available for current branch |
BC-AC004 |
Failed to do accounting entries for bills & collections product $1 |
BC-AC005 |
Failed to get reference number for bills & collections product $1 for accounting entries |
BC-AC006 |
Interest computation for accruals failed for bills & collections contract reference number $1 |
BC-AC007 |
Are you sure you want to start accruals? |
BC-AC008 |
Reverse accrual failed for bills & collections contract reference number $1 |
BC-AC009 |
Invalid component list sent for accruals for bills & collections contract reference number $1 |
BC-AC010 |
Date until which the accrual due dates of bills & collections contracts should be picked up is not available |
BC-AC011 |
Invalid accrual type entered |
BC-AC012 |
Invalid accrual level selected for the current branch |
BC-AC013 |
Floating rate changes not processed. Run bills & collections floating rate changes batch process before starting accruals |
BC-AC014 |
Failed to lock bills & collections contract reference number $1 for ‘ACCR’ event |
BC-AC015 |
Failed to log ‘ACCR’ event into log table for bills & collections contract reference number $1 |
BC-AC016 |
Failed to get new event sequence number for reverse accrual event for bills & collections contract reference number $1 |
BC-AC017 |
Failed to get accrue till date for bills & collections product $1 |
BC-AC018 |
Failed to get commit frequency for accruals |
BC-AC019 |
Failed to insert the error code into exception table for the event ‘ACCR’ and bills & collections contract reference number $1 |
BC-AC020 |
This is an end of day process. Cannot process now |
BC-AC021 |
Failed to get end of input for the current branch |
BC-AC022 |
Accruals batch process completed |
BC-AC023 |
Accrue_till_date is null for bills & collections contract reference number $1 |
BC-AC024 |
Interest accruals process failed |
BC-AC025 |
Failed to update accrual_details after product_level accounting entries for product $1 |
BC-AC026 |
Failed to check if any floating interest rate changes for bills & collections contract reference number $1 are not processed |
BC-AC027 |
Failed to insert accrual details into table for bills & collections contract reference number $1 |
BC-AC028 |
Floating interest rate changes have not been processed for bills & collections contract reference number $1 |
BC-AC029 |
Failed to update to_date in calc table for bills & collections contract reference number $1 |
BC-AC030 |
First run the predecessor process before running this |
BC-AC031 |
Process till date is mandatory |
BC-AC032 |
Process till date cannot be greater than 365 days from today |
BC-AC033 |
Change the process till date if you like to for memo accrual |
BC-ACR01 |
No contracts were picked for accruals on this date |
BC-AP001 |
Are you sure you want to start bills & collections change of event from acceptance to advance? |
BC-AP002 |
Failed to insert the error code into exception table for the event ‘BADV’ and bills & collections contract reference number $1 |
BC-AP003 |
Failed to update processed_status_field as ‘P’ in BCTB_prod_acpadv_dates for bills & collections product $1 |
BC-AP004 |
Failed to do settlement pickup for bills & collections contract reference number $1 - event sequence number $2 - event ‘$3’ |
BC-AP005 |
Failed to process change of event from acceptance to advance for bills & collections contract reference number $1 |
BC-AP006 |
Failed to create a new version and event sequence number for the change of event from acceptance to advance for bills & collections reference number $1 |
BC-AP007 |
Failed to get end of input for current branch |
BC-AP008 |
Acceptance to advance event change process completed |
BC-AP009 |
Acceptance to advance event change process failed |
BC-AP010 |
Failed to get commit frequency for acceptance to advance event change batch process |
BC-AP011 |
Failed to insert details into BCTB_ACP_ADV_LOG table for bills & collections contract reference number $1 |
BC-AP012 |
Failed to update table for BADV event for bills & collections contract reference number $1 and event sequence number $2 |
BC-AP013 |
Failed to populate advice table for ‘BADV’ event for bills & collections contract reference number $1 and event sequence number $2 |
BC-AP014 |
Failed to get events for bills & collections contract reference number $1 and event sequence number $2 |
BC-AP015 |
Failed to process ‘$2’ event for bills & collections contract reference number $1 and event sequence number $3 during ‘BADV’ event |
BC-AP016 |
Failed to authorize bills & collections contract reference number $1 after processing ‘BADV’ event |
BC-AP017 |
From_calc_date is not available for bills & collections contract reference number $1 and event sequence number $2 |
BC-AP018 |
To_calc_date is not available for advance collection type for bills & collections contract reference number $1 and event sequence number $2 |
BC-AP019 |
From_calc_date cannot be greater than today for bills & collections contract reference number $1 and event sequence number $2 |
BC-AP020 |
Failed to get record from BCTB_contract_master for bills & collections contract reference number $1 and event sequence number $2 |
BC-AP021 |
Failed to get details for the bills & collections product $1 |
BC-AP022 |
This process can be run only during begin of day or end of day |
BC-AP023 |
First run the predecessor process before running this |
BC-AT001 |
Failed to get exchange rate between ‘$1’ currency and ‘$2’ currency |
BC-AT002 |
Failed to convert amount in ‘$1’ currency to ‘$2’ currency |
BC-AT003 |
Failed to get accounting entry details for contract reference number $1 and event ‘$2’ |
BC-AT004 |
Failed to do accounting entries for contract reference number $1 - event ‘$3’ and event sequence number $2 |
BC-AT005 |
Accounting entries have not been defined for the event ‘$3’. No accounting entries have been passed for contract reference $1 - event ‘$3’ with event sequence number $2. |
BC-AT006 |
No amount tags present for contract reference number $1 - event ‘$3’ and event sequence number $2 to send for accounting entries |
BC-AT007 |
Failed during handoff for accounting entries for contract reference number $1 - event ‘$3’ and event sequence number $2 |
BC-AT008 |
Failed to update tax details after accounting entries for contract reference number $1 - event ‘$3’ and event sequence number $2 |
BC-AT009 |
Failed to update settlement details for contract reference number $1 with event sequence number $2 |
BC-AT010 |
Failed to update charge details for contract reference number $1 with event sequence number $2 |
BC-AT011 |
Settlement referral failed for contract reference number $1 with event sequence number $2 |
BC-AU0001 |
There are no unauthorized events for the BC reference $1 pending authorization. |
BC-AU0002 |
Failed to authorize event ‘$2’ with event sequence number $3 of BC reference $1. |
BC-AU0003 |
Critical error was encountered during authorization of BC reference $1. Authorization of contract has failed and was unsuccessful. |
BC-AU0004 |
Failed to authorize accounting entries for event ‘$2’ with event sequence number $3 of BC reference $1. |
BC-AU0005 |
Failed to trigger outgoing messages for event ‘$2’ with event sequence number $3 of BC reference $1. |
BC-AU001 |
Product rekey preferences could not be got. |
BC-AU002 |
Rekey values do not match. Retry. |
BC-AU003 |
Authorizer cannot be the same as the maker. |
BC-C0001 |
Reference number could not be generated. |
BC-C0002 |
Product details could not be inherited. |
BC-C0003 |
$1 must be greater than or equal to product start date. |
BC-C0004 |
$1 must be lesser than or equal to product end date. |
BC-C0005 |
$1 : input mandatory |
BC-C0006 |
This contract will be completely deleted. Are you sure? |
BC-C0007 |
All unauthorized events in this contract will be deleted. Proceed? |
BC-C0008 |
All unauthorized events for this contract have been undone. |
BC-C0009 |
At least contract reference number is required to put the contract on hold. |
BC-C0010 |
Base date cannot be greater than application date. |
BC-C0011 |
All overrides requiring confirmation have not been confirmed. Confirm them. |
BC-C0013 |
Template id and description mandatory. |
BC-C0014 |
Tenor is less than the minimum tenor specified in the product. |
BC-C0015 |
Tenor is greater than the maximum tenor specified in the product. |
BC-C0016 |
LC details could not be copied |
BC-C0017 |
User reference number is not unique. |
BC-C0018 |
User reference number mandatory. |
BC-C0019 |
LCY equivalent of bill amount could not be got. Cannot proceed. |
BC-CA001 |
Failed to calculate amount_due for a component of the contract |
BC-CLOSE |
Do you want to close the contract? |
BC-CS001 |
Bills contract authorization failed. |
BC-DE0001 |
Critical error occurred during deletion of records for event ‘$2’ with event sequence number $3 for BC reference $1 |
BC-DE0002 |
Deletion of records from contract master table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0003 |
Deletion of records from contract parties table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0004 |
Deletion of records from contract parties addresses table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0005 |
Deletion of records from contract parties limits table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0006 |
Deletion of records from contract document table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0007 |
Deletion of records from contract document clauses table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0008 |
Deletion of records from contract goods table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0009 |
Deletion of records from contract shipment information table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0010 |
Deletion of records from contract free format text table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0011 |
Deletion of records from contract instructions table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0012 |
Deletion of records from contract discrepancy table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0013 |
Deletion of records from contract payment exception table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0014 |
Deletion of records from contract acceptance exception table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0015 |
Deletion of records from contract reserve exception table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0016 |
Deletion of records from contract payment fate table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0017 |
Deletion of records from contract acceptance fate table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0018 |
Deletion of records from contract accrual details table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0019 |
Deletion of records from contract status log table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0020 |
Deletion of records from contract interest calculation table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0021 |
Deletion of records from contract interest details table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0022 |
Deletion of records from contract interest master table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0023 |
Deletion of records from contract changes log table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0024 |
Deletion of records from contract events advices table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0025 |
Deletion of records from contract events log table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0026 |
Deletion of records from contract exceptions table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0027 |
Deletion of records from contract overrides table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0028 |
Deletion of records from contract paid details table for BC reference $1 and event ‘$2’ with event sequence number $3 failed. |
BC-DE0029 |
Only unauthorized event of contract can be deleted. Cannot delete authorized event ‘$2’ with event sequence number $3 of BC reference $1. |
BC-DE0030 |
Deletion of accounting entries for event ‘$2’ with event sequence number ‘$3’ of bills & collection reference $1 failed. |
BC-DE0031 |
Deletion of customer settlement data for event ‘$2’ with event sequence number ‘$3’ of bills & collection reference $1 failed. |
BC-DE0032 |
Deletion of ICCF sub-system data for event ‘$2’ with event sequence number ‘$3’ of bills & collection reference $1 failed. |
BC-DE0033 |
Deletion of tax sub-system data for event ‘$2’ with event sequence number ‘$3’ of bills & collection reference $1 failed. |
BC-DE0034 |
Deletion of common contract table record for event ‘$2’ with event sequence number ‘$3’ of bills & collection reference $1 failed. |
BC-DE0035 |
Deletion of limits data for event ‘$2’ with event sequence number $3 for bills & collection reference $1 failed. |
BC-DE0036 |
Deletion of letters of credit availment event linked to event ‘$2’ with event sequence number ‘$3’ for BC reference $1 failed. |
BC-DE0038 |
Deletion of records from MIS table for BC reference $1And event ‘$2’ with event sequence number $3 failed |
BC-DEBUG |
1 |
BC-DEL01 |
The latest authorized event could not be identified to rollback to. |
BC-DEL02 |
Unauthorized contract can be deleted only by the user who input it. |
BC-EV0001 |
Processing of event ‘book’ failed for BC reference $1. |
BC-EV0002 |
Processing of event ‘INIT’ failed for BC reference $1. |
BC-EV0003 |
Processing of event ‘BDIS’ failed for BC reference $1. |
BC-EV0004 |
Processing of event ‘BADV’ failed for BC reference $1. |
BC-EV0005 |
Processing of event ‘BPUR’ failed for BC reference $1. |
BC-EV0006 |
Processing of event ‘LDIS’ failed for BC reference $1. |
BC-EV0007 |
Processing of event ‘LADV’ failed for BC reference $1. |
BC-EV0008 |
Processing of event ‘LPUR’ failed for BC reference $1. |
BC-EV0009 |
Processing of event ‘LIQD’ failed for BC reference $1. |
BC-EV0010 |
Processing of event ‘AMND’ failed for BC reference $1. |
BC-EV0011 |
Processing of event ‘ACCR’ failed for BC reference $1. |
BC-EV0012 |
Processing of event ‘STCH’ failed for BC reference $1. |
BC-EV0013 |
Processing of event ‘REVR’ failed for BC reference $1. |
BC-EV0014 |
Processing of event ‘ADIS’ failed for BC reference $1. |
BC-EV0015 |
Processing of event ‘PFAT’ failed for BC reference $1. |
BC-EV0016 |
Processing of event ‘AFAT’ failed for BC reference $1. |
BC-EV0017 |
Processing of event ‘REFP’ failed for BC reference $1. |
BC-EV0018 |
Processing of event ‘REFA’ failed for BC reference $1. |
BC-EV0019 |
Processing of event ‘PRNP’ failed for BC reference $1. |
BC-EV0020 |
Processing of event ‘PRNA’ failed for BC reference $1. |
BC-EV0021 |
Processing of event ‘CLOS’ failed for BC reference $1. |
BC-EV0022 |
Processing of event ‘RRES’ failed for BC reference $1. |
BC-EV0023 |
Processing of event ‘BACP’ failed for BC reference $1. |
BC-EV0030 |
Accounting services function failed during event $2 with event sequence number $3 for BC reference $1 |
BC-EV0031 |
Failed to delete settlement details during event $2 with event sequence number $3 for BC reference $1 |
BC-EV0032 |
Failed to delete the contract details during event $2 with event sequence number $3 for BC reference $1 |
BC-EV0033 |
Failed to delete tax details during event $2 with event sequence number $3 for BC reference $1 |
BC-EV0034 |
Failed to delete the contract during event $2 with event sequence number $3 for BC reference $1 |
BC-EV0035 |
Failed to delete limit details during event $2 with event sequence number $3 for BC reference $1 |
BC-EV0036 |
Failed to delete LC availment details during event $2 with event sequence number $3 for BC reference $1 |
BC-EV0050 |
Critical error occurred during processing of event ‘$2’ for BC reference $1. |
BC-EV0051 |
Update of contract event log for event ‘$2’ failed for BC reference $1. |
BC-EV0052 |
Failed to fetch contract related data for event ‘$2’ of BC reference $1 |
BC-EV0053 |
Processing of accounting entries for event ‘$2’ of BC reference $1 failed. |
BC-EV0054 |
Processing of LC availment event failed for bills & collection reference $1 under our LC reference $2. |
BC-EV0055 |
On-line limits monitoring process failed for event ‘$2’ of bills & collection reference $1. |
BC-EV0056 |
Reversal of accounting entries for BC reference $1 failed. |
BC-EV0057 |
Accounting entries definition lookup for event ‘$2’ for BC reference $1 failed. |
BC-EV0058 |
Accounting entries hand off for event ‘$2’ with event sequence number ‘$3’ for bills & collections contract reference $1 failed. |
BC-EV0059 |
Update of contract interest tables (BCTBS_ICCF_Master) for event ‘$2’ with event sequence number $3 of BC reference $1 |
BC-EVNT1 |
Current event is : $1. Subsystems and advices will be picked up for the event. |
BC-FR001 |
Are you sure you want to process floating rate interest changes? |
BC-FR002 |
Failed to update process field for floating rate code $1 - currency $2 |
BC-FR003 |
Failed to process rate change for bills and collections contract reference number $1- rate code $2 and currency $3 |
BC-FR004 |
Failed to process rate change for bills and collections contract reference number $1 and component $2 |
BC-FR005 |
Failed to get end of input for current branch |
BC-FR006 |
Failed to get new event sequence number for bills and collections contract reference number $1 while processing floating rate code $2 with currency $3 - effective date $4 and amount $5 |
BC-FR007 |
Completed processing floating rate interest changes |
BC-FR008 |
Failed to process floating rate interest changes |
BC-FR009 |
Failed to check if any floating rate changes have to be processed |
BC-FR010 |
Failed to log FRIC event for bills and collections contract reference number $1 |
BC-FR011 |
Failed to log the exception into the exception table during FRIC event for bills and collections contract reference number $1 |
BC-FR012 |
Failed to get commit frequency for floating rate change process |
BC-FR013 |
Failed to calculate amount due for the bills and collections contract reference number $1 |
BC-FR014 |
Failed to log FRIC event for bills and collections contract reference number $1 and rate code $2 |
BC-FR015 |
Failed to calculate amount due for the bills and collections contract reference number $1 and component $2 |
BC-HOL001 |
Holiday check for base date and bill currency has failed. Please check whether holiday table has been maintained. |
BC-HOL002 |
BC contract base date $1 is a holiday for bill currency $2. OK to proceed? |
BC-HOL003 |
Local holiday check for base date has failed. Please check whether local holiday table has been maintained. |
BC-HOL004 |
BC contract base date $1 is a local holiday. OK to proceed? |
BC-HOL005 |
Holiday check for covering letter date and bill currency has failed. Please check whether holiday table has been maintained. |
BC-HOL006 |
BC contract covering letter date $1 is a holiday for bill currency $2. OK to proceed? |
BC-HOL007 |
Local holiday check for covering letter date has failed. Please check whether local holiday table has been maintained. |
BC-HOL008 |
BC contract covering letter date $1 is a local holiday. OK to proceed? |
BC-HOL009 |
Holiday check for maturity date and bill currency has failed. Please check whether holiday table has been maintained. |
BC-HOL010 |
BC contract maturity date $1 is a holiday for bill currency $2. OK to proceed? |
BC-HOL011 |
Local holiday check for maturity date has failed. Please check whether local holiday table has been maintained. |
BC-HOL012 |
BC contract maturity date $1 is a local holiday. OK to proceed? |
BC-HOL013 |
Holiday check for value date and bill currency has failed. Please check whether holiday table has been maintained. |
BC-HOL014 |
BC contract value date $1 is a holiday for bill currency $2. OK to proceed? |
BC-HOL015 |
Local holiday check for value date has failed. Please check whether local holiday table has been maintained. |
BC-HOL016 |
BC contract value date $1 is a local holiday. OK to proceed? |
BC-HOL017 |
Holiday check for liquidation date and bill currency has failed. Please check whether holiday table has been maintained. |
BC-HOL018 |
BC contract liquidation date $1 is a holiday for bill currency $2. OK to proceed? |
BC-HOL019 |
Local holiday check for liquidation date has failed. Please check whether local holiday table has been maintained. |
BC-HOL020 |
BC contract liquidation date $1 is a local holiday. OK to proceed? |
BC-HOL021 |
Holiday check for interest computation from date and bill currency has failed. Please check whether holiday table has been maintained. |
BC-HOL022 |
BC contract interest computation from date $1 is a holiday for bill currency $2. OK to proceed? |
BC-HOL023 |
Local holiday check for interest computation from date has failed. Please check whether local holiday table has been maintained. |
BC-HOL024 |
BC contract interest computation from date $1 is a local holiday. OK to proceed? |
BC-HOL025 |
Holiday check for interest computation to date and bill currency has failed. Please check whether holiday table has been maintained. |
BC-HOL026 |
BC contract interest computation to date $1 is a holiday for bill currency $2. OK to proceed? |
BC-HOL027 |
Local holiday check for interest computation to date has failed. Please check whether local holiday table has been maintained. |
BC-HOL028 |
BC contract interest computation to date $1 is a local holiday. OK to proceed? |
BC-IC001 |
Contract $1 is authorized. Cannot delete any of its details |
BC-IC002 |
ICCF referral failed for bills & collections contract reference number $1 and event sequence number $2 |
BC-IC003 |
Tax referral failed for bills & collections contract reference number $1 and event sequence number $2 |
BC-IC004 |
Failed to compute tax for bills & collections contract reference number $1 - event ‘$3’ and event sequence number $2 |
BC-IN0001 |
Failed to log the status for BC reference $1 |
BC-INT001 |
Input to from date (for interest calculation) for BC reference $1 is mandatory. |
BC-INT002 |
For interest components collected in advance, input to ‘to date’ (for interest calculation) of BC reference $1 is mandatory. |
BC-INT003 |
Rate type ‘$4’ of interest component ‘$3’ picked up during event ‘$2’ for bills & contract reference $1 is invalid. |
BC-INT004 |
Interest collection method ‘$4’ of interest component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1 is invalid. |
BC-INT005 |
Penalty field value ‘$4’ of interest component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1 is invalid. |
BC-INT006 |
Rate type ‘$5’ of penalty interest component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1 is invalid. |
BC-INT007 |
Floating interest rate code ‘$5’ should not be linked to fixed/special interest type component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1. |
BC-INT008 |
Floating interest rate component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1 should necessarily be linked to a valid floating interest rate code. |
BC-INT009 |
Input to special interest type component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1 is mandatory. (value cannot be null) |
BC-INT010 |
Interest calculation method for interest component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1 has to be actual/actual only. |
BC-INT011 |
Interest calculation from date ‘$4’ should be greater than interest calculation to date ‘$5’ for the interest component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1. |
BC-INT012 |
Interest component ‘$3’ linked to floating interest rate code picked up during event ‘$2’ for bills & collection reference $1 cannot be collected in advance. |
BC-INT013 |
Interest calculation from date and interest calculation to date for special interest component ‘$3’ picked up during event ‘$2’ for bills & collection reference $1 is mandatory. |
BC-INT014 |
Interest calculation from date ‘$2’ cannot be later than today's system date ‘$3’ for BC reference $1. |
BC-INT015 |
Interest calculation from date ‘$2’ has to be earlier than interest calculation to date ‘$3’ for BC reference $1. |
BC-INT016 |
Basis amount category type of interest components picked up during event ‘$2’ with event sequence number ‘$3’ for BC reference $1 is invalid. |
BC-INT017 |
Basis amount category of penalty interest type components picked up during event ‘$2’ ( ‘$3’) for BC contract reference $1 should be ‘overdue’ only. |
BC-INT018 |
Interest calculation method of interest type components picked up during event ‘$2’ ( ‘$3’) for BC contract reference $1 is mandatory. |
BC-INT019 |
Interest rate for a fixed interest component cannot be null |
BC-LCIF1 |
Critical errors in LC interface function. Cannot proceed. |
BC-LCIF2 |
Critical error in getting LC details. Cannot proceed. |
BC-LCIN1 |
Insert into BC tables failed. |
BC-LI001 |
From date required to liquidate bills & collections contract reference number $1 |
BC-LI002 |
Liquidation failed for bills & collections contract reference number $1 |
BC-LI003 |
Are you sure you want to start auto liquidation? |
BC-LI004 |
Failed to update table for bills & collections contract reference number $1 and event sequence number $2 for the event ‘$3’ |
BC-LI005 |
Failed to do settlement pickup for bills & collections contract reference number $1 - event sequence number $2 - event ‘$3’ |
BC-LI006 |
Failed to create a new version and event sequence number for liquidation event for bills & collections contract reference number $1 |
BC-LI007 |
ICCF pickup failed during liquidation for bills & collections contract reference number $1 |
BC-LI008 |
Failed to get liquidation event for bills & collections contract reference number $1 |
BC-LI009 |
Failed to get arrear type interest components for liquidation for bills & collections contract reference number $1 |
BC-LI010 |
Failed to update interest details for bills & collections contract reference number $1 after accounting entries was done |
BC-LI011 |
Failed to log error into exception table for bills & collections contract reference number $1 for event sequence number $2 |
BC-LI012 |
Failed to populate advice table for the event ‘$3’ for bills & collections contract reference number $1 and event sequence number $2 |
BC-LI013 |
Failed to get end of input for current branch |
BC-LI014 |
Failed to update process field as processed for product $1 during liquidation |
BC-LI015 |
Auto liquidation process completed |
BC-LI016 |
Auto liquidation process failed |
BC-LI017 |
Failed to get commit frequency for liquidation process |
BC-LI018 |
Failed to get events to be processed for the event ‘$3’ for bills & collections contract reference number $1 for the event sequence number $2 |
BC-LI019 |
Failed to process ‘$2’ event for bills & collections contract reference number $1 and event sequence number $3 during ‘$4’ event |
BC-LI020 |
Failed to authorize bills & collections contract reference number $1 after processing event ‘$2’ |
BC-LI021 |
To date required to liquidate bills & collections contract reference number $1 |
BC-LI022 |
Failed to insert details into BCTB_autoliq_details for bills & collections contract reference number $1 - event $3 - event sequence number $2 |
BC-LI023 |
This process can be run only during begin of day or end of day |
BC-LI024 |
First run the predecessor process before running this |
BC-LM-00001 |
The issuer limits details are incomplete. Complete/delete the issuer limits details. |
BC-LM-00002 |
The line code is not a limits template |
BC-LM-00003 |
The line code is not entered |
BC-LM-00004 |
The liability is not entered |
BC-LM-00005 |
The line start date cannot be later than the line expiry date |
BC-LM-00006 |
The last available date cannot be later than the line expiry date |
BC-LM-00007 |
The line currency is not entered |
BC-LM-00008 |
This tenor has been maintained for the limit |
BC-LM-00009 |
The tenor details are incomplete. Complete/delete the tenor details |
BC-LM-00010 |
The products allowed details are incomplete. Complete/delete the products allowed details |
BC-LM-00011 |
The branches allowed details are incomplete. Complete/delete the branches allowed details |
BC-LM-00012 |
The last available date cannot be less than the line start date |
BC-LM-00013 |
The customers allowed details are incomplete. Complete/delete the customers allowed details |
BC-LM-00014 |
The tenor limit amount exceeds the line limit amount |
BC-LM-00015 |
The sub line tenor limit amount cannot be greater than the next higher main line tenor limit amount. $1 - $2 |
BC-LM-00016 |
The sub line tenor cannot be greater than maximum main line tenor. $1 days |
BC-LM-00017 |
There are no tenors specified for the main line |
BC-LM-00018 |
The line code is limits template. Details will be copied from template. Continue? |
BC-LM-00019 |
The sub line limit cannot exceed the main line limit. $1-$2 |
BC-LM-00020 |
The main line limit cannot be less than any of its sub line limit. $1 -$2 |
BC-LM-00021 |
The main line tenor cannot be less than the minimum tenor of any sub lines reporting to it. - $1 days |
BC-LM-00022 |
The main line tenor limit amount cannot be less than the next lower sub line tenor limit amount. $1 - $2 |
BC-LM-00023 |
The limits copy could not be completed. |
BC-LM-00024 |
Blank spaces cannot be a part of this field |
BC-LM-00025 |
The line code should have a nine characters |
BC-LM-00026 |
The tenor mnemonic is not entered. |
BC-LM-00027 |
The limit is not entered. |
BC-LM-00028 |
The collateral start date cannot be later than the collateral expiry date |
BC-LM-00029 |
The margin computed is not between 0 and 100. |
BC-LM-00030 |
The collateral currency is not entered. |
BC-LM-00031 |
The collateral type is not entered. |
BC-LM-00032 |
The collateral review date cannot be later than the collateral expiry date |
BC-LM-00033 |
The collateral review date cannot be earlier than collateral start date |
BC-LM-00034 |
The expiry date cannot be earlier than start date. |
BC-LM-00035 |
The security code is not entered. |
BC-LM-00036 |
The security type is not entered. |
BC-LM-00037 |
The currency is not entered. |
BC-LM-00038 |
The market price details are incomplete. Complete / delete the market price details |
BC-LM-00039 |
The line code is not entered. |
BC-LM-00040 |
The computed exposure is not between 1 and 100. |
BC-LM-00041 |
There are active sub lines reporting to this main line. Main line cannot be closed. |
BC-LM-00042 |
The last price change date cannot be greater than branch date. |
BC-LM-00043 |
The security code is not entered for the MVBC. |
BC-LM-00044 |
The price code is not entered for the MVBC. |
BC-LM-00045 |
The number of units is not entered for the MVBC. |
BC-LM-00046 |
The collateral CCY is not entered for the collateral. |
BC-LM-00047 |
Security code has not been entered. |
BC-LM-00048 |
The issuer exposure details are incomplete. Complete / delete the issuer exposure details |
BC-LM-00049 |
The start date cannot be greater than the branch date. |
BC-LM-00050 |
The last price change date cannot be earlier than start date. |
BC-LM-00051 |
The expiry date cannot be earlier than branch date. |
BC-LM-00052 |
The last price change date cannot later than expiry date |
BC-LM-00053 |
The description is not entered. |
BC-LM-00054 |
The face value is not entered. |
BC-LM-00055 |
The limit contribution cannot be greater than the cap amount. |
BC-LM-00056 |
Report date should be greater than the date today |
BC-LM-00057 |
The total issuer exposure should be greater than 100 %. |
BC-LM-00058 |
Collateral exist with the issuer code. Record cannot be closed. |
BC-LM-00059 |
Securities exist with the issuer code. Record cannot be closed. |
BC-LM-00060 |
There are collaterals linked to this limit. Record cannot be closed. |
BC-LM-00061 |
There are collaterals linked to this security. Record cannot be closed. |
BC-LM-00062 |
There are collaterals linked to this price code. Record cannot be closed. |
BC-LM-00063 |
There are collaterals linked to this collateral type. Record cannot be deleted |
BC-LM-00064 |
This facility is not available at this branch |
BC-LM-00065 |
No details exist for the reference number. |
BC-LM-00066 |
Customer clean risk limit cannot be greater than liability clean risk limit |
BC-LM-00067 |
Customer clean risk limit cannot be greater than overall limit. |
BC-LM-00068 |
Liability clean risk limit cannot be greater than overall limit. |
BC-LM-00069 |
Limit currency is not entered |
BC-LM-00070 |
Overall limit is not entered |
BC-LM-00071 |
Liability clean risk limit is not entered |
BC-LM-00100 |
Line not authorized |
BC-LM-00101 |
Line closed |
BC-LM-00102 |
Line not found |
BC-LM-00103 |
Invalid customer id |
BC-LM-00104 |
Liability id. Not specified |
BC-LM-00105 |
Account id. Not specified |
BC-LM-00106 |
Reference id not specified |
BC-LM-00107 |
Amount tag not specified |
BC-LM-00108 |
Amount not specified |
BC-LM-00109 |
Currency not specified |
BC-LM-00110 |
Branch not specified |
BC-LM-00111 |
Line $1 - amount exceeds limit for specified tenor by $2 |
BC-LM-00112 |
Line $1 - amount exceeds all available tenor limits by $2 |
BC-LM-00113 |
Line $1 - amount exceeds line limit. Limit = $3 $2. Utilization = $4 $2. Overdraft = $5 $2 |
BC-LM-00114 |
Main line $1 - amount exceeds main line limit amount. Limit = $3 $2. Utilization = $4 $2. Overdraft = $5 $2 |
BC-LM-00115 |
Line has matured |
BC-LM-00116 |
Line not available |
BC-LM-00117 |
Amount exceeds limit for liability $1. Limit = $3 $2 utilization = $4 $2 overdraft = $5 $2 |
BC-LM-00200 |
Clean risk limit exceeded for customer $1 on $2. Limit = $4 $3 , utilization = $5 $3, excess = $6 $3 |
BC-LM-00201 |
Clean risk limit exceeded for liability $1 on $2. Limit = $4 $3 , utilization = $5 $3, excess = $6 $3 |
BC-LM-00202 |
Date input is a holiday, do you want to continue? |
BC-LM-99998 |
Limits: node $1 unavailable. Utilizations will be updated later. |
BC-LM-99999 |
Limits service - unexpected error - $1 |
BC-MA001 |
Record successfully deleted |
BC-MA0010 |
No detail records to view |
BC-MA002 |
Record successfully closed |
BC-MA003 |
Record successfully reopened |
BC-MA004 |
Record successfully saved |
BC-MA005 |
Document code does not match with language code |
BC-MA006 |
Discrepancy code does not match with language code |
BC-MA007 |
Goods code does not match with language code |
BC-MA008 |
Instructions code does not match with language code |
BC-MA009 |
Language code does not match with the free format text code |
BC-MA010 |
Exchange rate stop limit has to be greater than exchange rate override limit. |
BC-MA011 |
Details for this branch have already been maintained. |
BC-MA012 |
This branch code does not exist. |
BC-MA020 |
Branch parameters can be maintained only for the current branch |
BC-MA050 |
All changes made in the editor will not be incorporated. |
BC-MA250 |
Documents cannot be maintained for a clean bill |
BC-MA251 |
The operation selected is not available for the given combination of product preferences. |
BC-MAT01 |
Product code field cannot be null |
BC-PEN01 |
Customer id field cannot be null |
BC-PEN02 |
Cover date cannot be null |
BC-REG01 |
Base date $1 is a holiday |
BC-REG02 |
Maturity date $1 is a holiday |
BC-REG020 |
Counterparty field cannot be null |
BC-REG021 |
Customer party type cannot be null |
BC-REG022 |
Closure not allowed |
BC-REG023 |
Amendment not allowed |
BC-REG025 |
Bill currency cannot be null |
BC-REG026 |
Bill amount cannot be null |
BC-REG027 |
Both document original RECV field & document duplicate RECV field cannot be null |
BC-REG028 |
Covering letter date cannot be null |
BC-REG029 |
Could not get bill amount LCY |
BC-REG03 |
Value date $1 is a holiday |
BC-REG030 |
Collection reference cannot be null |
BC-REG031 |
Drawee details have to be input |
BC-REG032 |
Drawer details have to be input |
BC-REG033 |
Value date cannot be null |
BC-REG20 |
Counterparty field cannot be null |
BC-REG21 |
Customer party type cannot be null |
BC-REG22 |
Closure not allowed |
BC-REG23 |
Amendment not allowed |
BC-REP01 |
Report date cannot be greater than today's date |
BC-REP02 |
Report date cannot be null |
BC-REP03 |
Overdue days field(s) cannot be null |
BC-RVR01 |
Do you want to reverse this contract? |
BC-RVR02 |
Corresponding availment on the LC will be reversed |
BC-SAVED |
Contract $1. |
BC-SCR01 |
Parties screen not visited. |
BC-SCR02 |
Documents screen not visited. |
BC-SCR03 |
Tracers screen not visited. |
BC-SCR04 |
Advices screen not visited. |
BC-SCR05 |
Discrepancies screen not visited. |
BC-ST001 |
Could not get commit frequency |
BC-ST0010 |
Status change failed |
BC-ST002 |
BOD status change processing failed |
BC-ST003 |
EOD status change processing failed |
BC-ST004 |
Unable to update the contract |
BC-ST005 |
Unable to populate exception table |
BC-ST006 |
Unable to update ICCF master table |
BC-ST007 |
Could not determine the final status to which the contract has to be moved |
BC-ST008 |
Could not get ESN |
BC-ST009 |
Unable to update accruals field |
BC-ST011 |
Stop accruals failed |
BC-ST012 |
Reverse accruals failed |
BC-ST014 |
Critical error occurred during BC status change processing |
BC-ST100 |
End of input not marked for the branch |
BC-ST101 |
This process can be run only as a part of beginning of day(BOD) or end of day(EOD) process |
BC-ST102 |
Are you sure you want to start automatic status change processing? |
BC-ST103 |
Failed in automatic status change processing !!! |
BC-ST104 |
Status change processing completed successfully |
BC-ST105 |
Failed to get end of input status for the current branch |
BC-ST106 |
Some products are not yet processed. Cannot update status as completed in pending programs |
BC-SW001 |
There are some characters that cannot be sent through swift. Do you want to proceed? |
BC-SW002 |
‘/’ Is not allowed in this field as it can be present in a swift message. |
BC-SW003 |
Maximum number of lines allowed is only $1. Will be truncated in swift. Proceed? |
BC-SW004 |
Address format not valid for the media specified |
BC-TR001 |
Are you sure you want to start tracer generation process? |
BC-TR002 |
Failed to get payment fate details for bills & collections contract reference number $1 |
BC-TR003 |
Failed to get new event sequence number for event '$2’ for bills & collections contract reference number $1 |
BC-TR004 |
Failed to update number of payment tracers sent for bills & collections contract reference number $1 |
BC-TR005 |
Failed to get end of input for the current branch |
BC-TR006 |
This is an end of day process. Cannot process now |
BC-TR007 |
Failed to update number of payment advices sent for bills & collections contract reference number $1 |
BC-TR008 |
Tracers generation process completed |
BC-TR009 |
Failed to get acceptance fate details for bills & collections contract reference number $1 |
BC-TR010 |
Failed to update number of release of reserve tracers sent for bills & collections contract reference number $1 |
BC-TR011 |
Failed to insert the error code into exception table for the event '$2’ and bills & collections contract reference number $1 |
BC-TR012 |
Failed to log event '$1' for bills & collections contract reference number $2 |
BC-TR013 |
Failed to populate the handoff table for message type ‘$2’ for bills & collections contract reference number $1 |
BC-TR014 |
Failed to populate the advice table for message type ‘$2’ for bills & collections contract reference number $1 |
BC-TR015 |
Failed to get address details for bills & collections contract reference number $1 - party type $2 |
BC-TR016 |
Failed to update number of acceptance tracers sent for bills & collections contract reference number $1 |
BC-TR017 |
Failed to update number of acceptance advices sent for bills & collections contract reference number $1 |
BC-TR018 |
$1 tracer generation process failed |
BC-TR019 |
Failed to generate acceptance tracer for bills & collections contract reference number $1 |
BC-TR020 |
Failed to generate payment tracer for bills & collections contract reference number $1 |
BC-TR021 |
Failed to generate discrepancy tracer for bills & collections contract reference number $1 |
BC-TR022 |
Failed to get commit frequency for tracer generation process |
BC-TR023 |
First run the predecessor process before running this |
BC-UDS01 |
Product code field cannot be null |
BC-UDS02 |
Status code field cannot be null |
BC-UDS03 |
Currency code field cannot be null |
BC-UN001 |
Unauthorized contract can be amended only by the user who input or amended it. |
BC-UN003 |
This version of the contract is unauthorized. Cannot amend. |
BC-UP0001 |
Failed to get commit frequency for the BC upload function |
BC-UP0002 |
Failed to generate the process id for the current upload process |
BC-UP0003 |
Failed to lock contract for BC upload reference $1 |
BC-UP0004 |
For a documentary bill, documentary details are mandatory. The same is not true for BC upload reference $1 |
BC-UP0005 |
For a clean bill, document details cannot exist. The same is not true for BC upload reference $1 |
BC-UP0006 |
For a clean bill, document clause details cannot exist. The same is not true for BC upload reference $1 |
BC-UP0007 |
Contract amount is null or zero for BC upload reference $1 |
BC-UP0008 |
For a bill under LC, LC issue date is mandatory. The same is not true for BC upload reference $1 |
BC-UP0009 |
For a bill under LC, their LC reference or our LC reference is mandatory. The same is not true for BC upload reference $1 |
BC-UP0010 |
Maturity date cannot be null for an acceptance, discounted or advanced bill |
BC-UP0011 |
Drawer and drawee party details not existing for the contract |
BC-UP0012 |
Party details not existing for bills party type $1 |
BC-UP0013 |
Party id is not same as the customer id |
BC-UP0014 |
Party address is mandatory |
BC-UP0015 |
Country code $1 is not valid |
BC-UP0016 |
Language code $1 is not valid |
BC-UP0017 |
Goods code is mandatory |
BC-UP0018 |
Swift validation failed for bills upload reference |
BC-UP0019 |
Bills upload reference contains invalid characters |
BC-UP0020 |
Swift validation failed for bills collection reference |
BC-UP0021 |
Bills collection reference contains invalid characters |
BC-UP0022 |
Swift validation failed for their LC reference |
BC-UP0023 |
Their LC reference contains invalid characters |
BC-UP0024 |
Only a bill for collection can be in registration stage |
BC-UP0025 |
Bills for collection cannot be in initial stage |
BC-UP0026 |
Collection reference is mandatory if operation is collection |
BC-UP0027 |
From date for interest calculation is mandatory for a bill in final stage |
BC-UP0028 |
LC issue date cannot be greater than today |
BC-UP0029 |
For a incoming bill, documents should have been received and covering letter date is mandatory |
BC-UP0030 |
For a outgoing bill under LC, covering letter date is mandatory |
BC-UP0031 |
Bill liquidated amount cannot be greater than bill due amount |
BC-UP0032 |
Tenor cannot be zero for a usance bill |
BC-UP0033 |
Sight bill cannot have a tenor greater than zero days |
BC-UP0034 |
Tenor cannot be greater than the maximum tenor for the product |
BC-UP0035 |
Tenor cannot be lesser than the minimum tenor for the product |
BC-UP0036 |
Maturity date cannot be lesser than base date |
BC-UP0037 |
From and to interest calculation dates are mandatory for a bill whose interest collection in advance |
BC-UP0038 |
For a bill in final stage from interest calculation date is mandatory |
BC-UP0039 |
To interest calculation date cannot be lesser than from interest calculation date |
BC-UP0040 |
Covering letter date cannot be greater than today |
BC-UP0041 |
From interest calculation date cannot be greater than today |
BC-UP0042 |
Liquidation date cannot be null if automatic liquidation field is set |
BC-UP0043 |
Maturity date cannot be null if automatic liquidation field is set |
BC-UP0044 |
Latest shipment date cannot be lesser than shipment date. |
BC-UP0045 |
Swift validation failed for document reference $1 |
BC-UP0046 |
Document reference $1 contains invalid characters |
BC-UP0047 |
Swift validation failed for party reference $1 |
BC-UP0048 |
Party reference $1 contains invalid characters |
BC-UP0049 |
Swift validation failed for media $1 and address $2 |
BC-UP0050 |
Base date $1 is a holiday for currency $2. OK to proceed? |
BC-UP0051 |
Base date $1 is a local holiday for current branch. OK to proceed? |
BC-UP0052 |
Value date $1 is a holiday for currency $2. OK to proceed? |
BC-UP0053 |
Value date $1 is a local holiday for current branch. OK to proceed? |
BC-UP0054 |
Covering letter date $1 is a holiday for currency $2. OK to proceed? |
BC-UP0055 |
Covering letter date $1 is a local holiday for current branch. OK to proceed? |
BC-UP0056 |
Maturity date $1 is a holiday for currency $2. OK to proceed? |
BC-UP0057 |
Maturity date $1 is a local holiday for current branch. OK to proceed? |
BC-UP0058 |
Liquidation date $1 is a holiday for currency $2. OK to proceed? |
BC-UP0059 |
Liquidation date $1 is a local holiday for current branch. OK to proceed? |
BC-UP0060 |
From date for interest calculation $1 is a holiday for currency $2. OK to proceed? |
BC-UP0061 |
From date for interest calculation $1 is a local holiday for current branch. OK to proceed? |
BC-UP0062 |
To date for interest calculation $1 is a holiday for currency $2. OK to proceed? |
BC-UP0063 |
To date for interest calculation $1 is a local holiday for current branch. OK to proceed? |
BC-UP0066 |
Discrepancy resolved date cannot be greater than today |
BC-UP0067 |
Unresolved discrepancies cannot exist for a bill in final stage |
BC-UP0068 |
Discrepancies cannot exist for a clean bill not under LC |
BC-UP0069 |
Payment tracer - tracer frequency cannot exist if tracer required is no |
BC-UP0070 |
Payment tracer - tracer receiver party type cannot exist if tracer required is no |
BC-UP0071 |
Payment tracer - tracer medium cannot exist if tracer required is no |
BC-UP0072 |
Payment tracer - tracer frequency is mandatory if tracer required is yes |
BC-UP0073 |
Payment tracer - tracer receiver party type is mandatory if tracer required is yes |
BC-UP0074 |
Payment tracer - tracer medium is mandatory if tracer required is yes |
BC-UP0075 |
Payment tracer - party details not existing for tracer receiver party type $1 |
BC-UP0076 |
Payment tracer - tracer medium is mandatory for tracer receiver party $1 who is a walk-in customer |
BC-UP0077 |
Payment tracer - address details not existing for tracer medium $1 and receiver party type $2 |
BC-UP0078 |
Payment tracer - tracer medium should be null for a non walk-in customer receiver type |
BC-UP0079 |
Payment tracer - previous tracer date or tracer start date cannot be null if at least one tracer has been sent |
BC-UP0080 |
Payment tracer - tracer start date cannot be null |
BC-UP0083 |
Payment tracer - payment message date cannot be greater than today |
BC-UP0084 |
Payment tracer - non payment message date cannot be greater than today |
BC-UP0085 |
Payment advice - advice receiver party type cannot exist if advice is not required |
BC-UP0086 |
Payment advice - advice medium cannot exist if advice is not required |
BC-UP0087 |
Payment advice - manually generate field cannot exist if advice is not required |
BC-UP0088 |
Payment advice - receiver party type is mandatory if advice required is yes |
BC-UP0089 |
Payment advice - party details not existing for receiver party type $1 |
BC-UP0090 |
Payment advice - advice medium is mandatory for receiver party $1 who is a walk-in customer |
BC-UP0091 |
Payment advice - address details not existing for advice medium $1 and receiver party type $2 |
BC-UP0092 |
Payment advice - advice medium should be null for a non walk-in customer receiver type |
BC-UP0094 |
Acceptance tracer - tracer frequency cannot exist if tracer required is no |
BC-UP0095 |
Acceptance tracer - tracer receiver party type cannot exist if tracer required is no |
BC-UP0096 |
Acceptance tracer - tracer medium cannot exist if tracer required is no |
BC-UP0097 |
Acceptance tracer - tracer frequency is mandatory if tracer required is yes |
BC-UP0098 |
Acceptance tracer - tracer receiver party type is mandatory if tracer required is yes |
BC-UP0099 |
Acceptance tracer - tracer medium is mandatory if tracer required is yes |
BC-UP0100 |
Acceptance tracer - party details not existing for tracer receiver party type $1 |
BC-UP0101 |
Acceptance tracer - tracer medium is mandatory for tracer receiver party $1 who is a walk-in customer |
BC-UP0102 |
Acceptance tracer - address details not existing for tracer medium $1 and receiver party type $2 |
BC-UP0103 |
Acceptance tracer - tracer medium should be null for a non walk-in customer receiver type |
BC-UP0104 |
Acceptance tracer - previous tracer date or tracer start date cannot be null if at least one tracer has been sent |
BC-UP0105 |
Acceptance tracer - tracer start date cannot be null |
BC-UP0108 |
Acceptance tracer - acceptance message date cannot be greater than today |
BC-UP0109 |
Acceptance tracer - non acceptance message date cannot be greater than today |
BC-UP0110 |
Acceptance advice - advice receiver party type cannot exist if advice is not required |
BC-UP0111 |
Acceptance advice - advice medium cannot exist if advice is not required |
BC-UP0112 |
Acceptance advice - manually generate field cannot exist if advice is not required |
BC-UP0113 |
Acceptance advice - receiver party type is mandatory if advice required is yes |
BC-UP0114 |
Acceptance advice - party details not existing for receiver party type $1 |
BC-UP0115 |
Acceptance advice - advice medium is mandatory for receiver party $1 who is a walk-in customer |
BC-UP0116 |
Acceptance advice - address details not existing for advice medium $1 and receiver party type $2 |
BC-UP0117 |
Acceptance advice - advice medium should be null for a non walk-in customer receiver type |
BC-UP0119 |
Release of reserve tracer - tracer frequency cannot exist if tracer required is no |
BC-UP0120 |
Release of reserve tracer - tracer receiver party type cannot exist if tracer required is no |
BC-UP0121 |
Release of reserve tracer - tracer medium cannot exist if tracer required is no |
BC-UP0122 |
Release of reserve tracer - tracer frequency is mandatory if tracer required is yes |
BC-UP0123 |
Release of reserve tracer - tracer receiver party type is mandatory if tracer required is yes |
BC-UP0124 |
Release of reserve tracer - tracer medium is mandatory if tracer required is yes |
BC-UP0125 |
Release of reserve tracer - party details not existing for tracer receiver party type $1 |
BC-UP0126 |
Release of reserve tracer - tracer medium is mandatory for tracer receiver party $1 who is a walk-in customer |
BC-UP0127 |
Release of reserve tracer - address details not existing for tracer medium $1 and receiver party type $2 |
BC-UP0128 |
Release of reserve tracer - tracer medium should be null for a non walk-in customer receiver type |
BC-UP0129 |
Release of reserve tracer - previous tracer date or tracer start date cannot be null if at least one tracer has been sent |
BC-UP0130 |
Release of reserve tracer - tracer start date cannot be null |
BC-UP0133 |
Release of reserve tracer - discrepancy approved date cannot be greater than today |
BC-UP1001 |
Unhandled exception during upload |
BC-UP1002 |
Unhandled exception during upload |
BC-UP1003 |
Unhandled exception during upload |
BC-UP1004 |
Unhandled exception during upload |
BC-UP1005 |
Unhandled exception during upload |
BC-UP1006 |
Unhandled exception during upload |
BC-UP1007 |
Unhandled exception during upload |
BC-UP1008 |
Unhandled exception during upload |
BC-UP1009 |
Unhandled exception during upload |
BC-UP1010 |
Unhandled exception during upload |
BC-UP1011 |
Unhandled exception during upload |
BC-UP1012 |
Unhandled exception during upload |
BC-UP1013 |
Unhandled exception during upload |
BC-UP1014 |
Unhandled exception during upload |
BC-UP1015 |
Unhandled exception during upload |
BC-UP1016 |
Unhandled exception during upload |
BC-UP1017 |
Unhandled exception during upload |
BC-UP1018 |
Unhandled exception during upload |
BC-UP1019 |
Unhandled exception during upload |
BC-UP1020 |
Unhandled exception during upload |
BC-UP1021 |
Unhandled exception during upload |
BC-UP1022 |
Unhandled exception during upload |
BC-UT001 |
Failed to get process_till_NWD_field from BCTM_branch_parameters |
BC-UT002 |
Failed to get period_end_date from STTM_period_codes |
BC-VAL01 |
Contract cannot be saved in final stage if there are unresolved discrepancies. Either resolve the discrepancies or change the stage to initial. |
BC-VAL02 |
For an incoming documentary bill, documents (original or duplicate) should have been received and covering letter date is mandatory. |
BC-VAL03 |
$1 and $2 cannot have the same party id. |
BC-VAL04 |
Covering letter date is mandatory. |
BC-XV001 |
Interest calculation to date should be greater than from date |
BC-XV002 |
Tenor must be greater than 0 for usance bills. |
BC-XV003 |
Value date should be <= application date. |
BC-XV004 |
This customer already exists as a different party type. |
BC-XV005 |
If tracer is required, then frequency, receiver and start date are mandatory |
BC-XV006 |
If tracer is required, then number of tracers is mandatory |
BC-XV007 |
If advice of fate is required, then receiver is mandatory. |
BC-XV008 |
Drawer and drawee are mandatory |
BC-XV009 |
$1 is linked to more than one party type. |
BC-XV010 |
Limits cannot be tracked for more than one walk-in customer |
BC-XV011 |
All subsystems (ICCF, tax and settlements) will be repicked up. |
BC-XV012 |
Maturity date should be >= base date |
BC-XV013 |
Interest calculation from date is mandatory |
BC-XV014 |
Interest calculation from date and to date are mandatory. |
BC-XV015 |
Party details not complete. |
BC-XV016 |
Clean bills cannot be put in initial stage. |
BC-XV017 |
Bills cannot be registered through this function. |
BC-XV018 |
Document letter date cannot be greater than today. |
BC-XV019 |
Resolution date is mandatory for resolved discrepancies. |
BC-XV020 |
Resolution date cannot be greater than today. |
BC-XV021 |
Interest calculation from date cannot be greater than today. |
BC-XV022 |
Line details not complete. |
BC-XV023 |
If tracer is required and receiver is not a CIF, then medium is mandatory. |
BC-XV024 |
If advice of fate is required and receiver is not a CIF, then medium is mandatory. |
BC-XV025 |
There are addresses maintained for this party. Delete them before deleting the party. |
BC-XV026 |
There are clauses attached to this document code. Delete them before deleting this document code. |
BC-XV027 |
Document details not applicable for clean bills. |
BC-XV028 |
Acceptance message date cannot be greater than today. |
BC-XV029 |
Non-acceptance message date cannot be greater than today. |
BC-XV030 |
Payment message date cannot be greater than today. |
BC-XV031 |
Non-payment message date cannot be greater than today. |
BC-XV032 |
Reserve release date cannot be greater than today. |
BC-XV033 |
Discrepancy details not applicable for clean bills. |
BC-XV034 |
Line for a party type cannot be null. |
BC-XV035 |
LC issue date is mandatory. |
BC-XV036 |
LC issue date cannot be greater than today. |
BC-XV037 |
Interest calculation to date is mandatory. |
BC-XV038 |
Value date cannot be lesser than interest calculation to date. |
BC-XV039 |
Shipment date cannot be greater than arrival date. |
BC-XV040 |
Liquidation amount cannot be greater than bill due amount. |
BC-XV041 |
Liquidation amount is mandatory. |
BC-XV042 |
Collection bills cannot be put in initial stage. |
BC-XV043 |
Document details not complete. |
BC-XV044 |
Clause details not complete. |
BC-XV045 |
Goods details not complete. |
BC-XV046 |
FFT details not complete. |
BC-XV047 |
Instruction details not complete. |
BC-XV048 |
Product is not allowed. |
BC-XV049 |
Currency is not allowed for this product. |
BC-XV050 |
Customer is not allowed for this product. |
BC-XV051 |
Product is not allowed in this branch. |
BC-XV052 |
Discrepancy details not complete. |
BC-XV053 |
No valid lines available. |
BC-XV054 |
Party address details not complete. |
BC-XV055 |
A clean LC is being availed against a documentary bill. OK to proceed? |
BC-XV059 |
Input to party type is mandatory. (cannot be null) |
BC-XV060 |
Input to party id is mandatory. (cannot be null) |
BC-XV061 |
Input to party name is mandatory. (cannot be null) |
BC-XV062 |
Input to party country code is mandatory. (cannot be null) |
BC-XV063 |
Input to party language is mandatory. (cannot be null) |
BC-XV064 |
Input to party reference is mandatory. (cannot be null) |
BC-XV065 |
Input to party address is mandatory. (cannot be null) |
BC-XV066 |
Input to collection reference field is mandatory. (cannot be null) |
BC-XV067 |
For bills under LC, input to their LC reference/our LC reference is mandatory. (cannot be null) |
BC-XV068 |
For bills under LC, input to LC issue date is mandatory. (cannot be null) |
BC-XV069 |
Input to bill currency is mandatory. (cannot be null) |
BC-XV070 |
Input to bill amount is mandatory. (cannot be null) |
BC-XV071 |
Input to our customer id is mandatory. (cannot be null) |
BC-XV072 |
Input to out customer party type is mandatory. (cannot be null) |
BC-XV073 |
Either original documents/duplicate documents of the bill should have been received. |
BC-XV074 |
Input to covering letter date is mandatory. (cannot be null) |
BC-XV075 |
Input to base date is mandatory. (cannot be null) |
BC-XV076 |
For a usance bill, the tenor should be greater than 0 days. |
BC-XV077 |
For a sight bill, the tenor should always be 0 days. |
BC-XV078 |
Input to value date is mandatory. (cannot be null) |
BC-XV079 |
Input to liquidation date is mandatory. (cannot be null) |
BC-XV080 |
Input to user defined status is mandatory. (cannot be null) |
BC-XV081 |
Input to status as on date is mandatory. (cannot be null) |
BC-XV082 |
Party type $1 has not been defined in the parties screen. |
BC-XV083 |
Credit limits tracking has already been defined for some parties. |
BC-XV084 |
Cannot delete party address record, as advices to party address already exist. |
BC-XV085 |
Cannot delete party address record as party address is set to receive all payment tracers. |
BC-XV086 |
Cannot delete party address record as party address is set to receive all advices of payment fate. |
BC-XV087 |
Cannot delete party address record as party address is set to receive all acceptance tracers. |
BC-XV088 |
Cannot delete party address record as party address is set to receive all advices of acceptance fate. |
BC-XV089 |
Cannot delete party address record as party address is set to receive all discrepancy approval/release of reserve tracers. |
BC-XV090 |
Cannot delete party record, as advice records to party already exist. |
BC-XV091 |
Cannot delete party record, as party is receiver of payment tracers. |
BC-XV092 |
Cannot delete party record as party is receiver of advices of payment fate. |
BC-XV093 |
Cannot delete party record as party is receiver of acceptance tracers. |
BC-XV094 |
Cannot delete party record as party is receiver of advices of acceptance fate. |
BC-XV095 |
Cannot delete party record as party is receiver of discrepancy approval/release of reserve tracers. |
BC-XV096 |
Cannot delete party record as address records for party exist. |
BC-XV097 |
Cannot delete party record as credit limits tracking record for party exist. |
BC-XV098 |
If payment exception tracer is not required then tracer frequency should be ‘0’. |
BC-XV099 |
Payment exception tracer required field has an invalid value (should be not required/required/till resolved only). |
BC-XV100 |
If payment exception tracer is not required then tracer receiver should be not input (should be null). |
BC-XV101 |
If payment exception tracer is not required then tracer medium should be not input (should be null). |
BC-XV102 |
If payment exception tracers are required, then tracer frequency is mandatory (should be input and should not be null). |
BC-XV103 |
If payment exception tracers are required, then tracer receiver party type is mandatory (should be input and should not be null). |
BC-XV104 |
Payment exception tracer receiver party type has not been input in the parties screen. |
BC-XV105 |
Payment exception receiver party type is a walk-in customer. Tracer medium is mandatory (should be input). |
BC-XV106 |
Payment exception receiver party type is not a walk-in customer. Tracer medium should not be input. |
BC-XV107 |
Input to payment exception tracer start date is mandatory. |
BC-XV108 |
Number of payment exception tracers to be sent should be ‘0’ (should not be input). |
BC-XV109 |
Date of protest for non-payment should not be input if bill is not under protest. |
BC-XV110 |
Payment tracer receiver party's media address has not been input in the parties screen. |
BC-XV111 |
Acceptance exception tracer required field has an invalid value (should be not required/required/till resolved only). |
BC-XV112 |
If acceptance exception tracer is not required then tracer frequency should be ‘0’. |
BC-XV113 |
If acceptance exception tracer is not required then tracer receiver should be not input (should be null). |
BC-XV114 |
If acceptance exception tracer is not required then tracer medium should be not input (should be null). |
BC-XV115 |
If acceptance exception tracers are required, then tracer frequency is mandatory (should be input and should not be null). |
BC-XV116 |
If acceptance exception tracers are required, then tracer receiver party type is mandatory (should be input and should not be null). |
BC-XV117 |
Acceptance exception tracer receiver party type has not been input in the parties screen. |
BC-XV118 |
Acceptance exception receiver party type is a walk-in customer. Tracer medium is mandatory (should be input). |
BC-XV119 |
Acceptance tracer receiver party's media address has not been input in the parties screen. |
BC-XV120 |
Acceptance exception receiver party type is not a walk-in customer. Tracer medium should not be input. |
BC-XV121 |
Input to acceptance exception tracer start date is mandatory. |
BC-XV122 |
Number of acceptance exception tracers to be sent should be ‘0’ (should not be input). |
BC-XV123 |
Date of protest for non-acceptance should not be input if bill is not under protest. |
BC-XV124 |
Payment advice of fate required field has an invalid value (should be required/not required/till resolved only). |
BC-XV125 |
Payment advice of fate receiver field should not be input if payment advice of fate is not required. |
BC-XV126 |
Payment advice of fate medium field should not be input if payment advice of fate is not required. |
BC-XV127 |
Advice of payment fate cannot be generated if advice of payment fate required field has a value of not required. |
BC-XV128 |
Input to advice of payment fate receiver party type field is mandatory. |
BC-XV129 |
Advice of payment fate receiver party type has not been input in the parties screen. |
BC-XV130 |
Advice of payment fate receiver party type is a walk-in customer. Input to advice of payment fate medium is mandatory. |
BC-XV131 |
Advice of payment fate receiver party address has not been input in parties screen. |
BC-XV132 |
Advice of payment fate receiver party type is not a walk-in customer. Advice of payment fate medium should not be input. |
BC-XV133 |
Advice of payment fate cannot be generated if advice of payment fate is specified as not required. |
BC-XV134 |
Acceptance advice of fate required field has an invalid value (should be required/not required/till resolved only). |
BC-XV135 |
Acceptance advice of fate receiver field should not be input if acceptance advice of fate is not required. |
BC-XV136 |
Acceptance advice of fate medium field should not be input if acceptance advice of fate is not required. |
BC-XV137 |
Advice of acceptance fate cannot be generated if advice of acceptance fate required field has a value of not required. |
BC-XV138 |
Input to advice of acceptance fate receiver party type field is mandatory. |
BC-XV139 |
Advice of acceptance fate receiver party has not been input in the parties screen. |
BC-XV140 |
Advice of acceptance fate receiver party type is a walk-in customer. Input to advice of acceptance fate medium is mandatory. |
BC-XV141 |
Advice of acceptance fate receiver party address has not been input in parties screen. |
BC-XV142 |
Advice of acceptance fate receiver party type is not a walk-in customer. Advice of acceptance fate medium should not be input. |
BC-XV143 |
Advice of acceptance fate cannot be generated if advice of acceptance fate is specified as not required. |
BC-XV144 |
Discrepancy/reserve exception tracer required field has an invalid value (should be not required/required/till resolved only). |
BC-XV145 |
If discrepancy/reserve exception tracer is not required then tracer frequency should be ‘0’. |
BC-XV146 |
If discrepancy/reserve tracer is not required then tracer receiver should be not input (should be null). |
BC-XV147 |
If discrepancy/reserve exception tracer is not required then tracer medium should be not input (should be null). |
BC-XV148 |
If discrepancy/reserve exception tracers are required, then tracer frequency is mandatory (should be input and should not be null). |
BC-XV149 |
If discrepancy/reserve exception tracers are required, then tracer receiver party type is mandatory (should be input and should not be null). |
BC-XV150 |
Discrepancy/reserve exception tracer receiver party type has not been input in the parties screen. |
BC-XV151 |
Discrepancy/reserve exception receiver party type is a walk-in customer. Tracer medium is mandatory (should be input). |
BC-XV152 |
Discrepancy/reserve tracer receiver party's media address has not been input in the parties screen. |
BC-XV153 |
Discrepancy/reserve exception receiver party type is not a walk-in customer. Tracer medium should not be input. |
BC-XV154 |
Input to discrepancy/reserve exception tracer start date is mandatory. |
BC-XV155 |
Number of discrepancy/reserve exception tracers to be sent should be ‘0’ (should not be input). |
BC-XV156 |
Reserve release date should not be input if under reserve field is no. |
BC-XV157 |
Reserve release date cannot be later than today's system date. |
BC-XV158 |
Discrepancy approval date cannot be later than today's system date. |
BC-XV159 |
Discrepancy approval date can be entered only after all the outstanding discrepancies have been approved. |
BC-XV160 |
Discrepancy approval fields should be yes if BC contract stage is final. |
BC-XV161 |
If BC contract is in final stage, then no unresolved discrepancies should be present. |
BC-XV162 |
Unresolved discrepancies cannot have resolved dates. |
BC-XV163 |
All resolved discrepancies should have resolved dates. |
BC-XV164 |
Clean bills not under LC cannot have any discrepancies. |
BC-XV165 |
Failed to populate advices for the event $1. |
BC-XV166 |
Bill currency, bill amount and our customer id should be input. |
BC-XV167 |
BC product is unauthorized/closed. BC contract cannot be saved. |
BC-XV168 |
BC product is not allowed for the branch. |
BC-XV169 |
BC product is not available as of contract value date. |
BC-XV170 |
Input to maturity date is mandatory. |
BC-XV171 |
Documents/clauses codes should not be input for a clean bill. |
BC-XV172 |
BC contract customer party details (name/address etc.) Has not been input. |
BC-XV173 |
Input to BC contract maturity date is mandatory. |
BC-XV174 |
Party details have not been input properly. |
BCREAS-01 |
New user and current user must be different |
BCREAS-02 |
Contract $1 has been reassigned from user ‘$2’ to user ‘$3’ by user ‘$4’ |
BCREAS-03 |
New user id cannot be null |
BCREAS-04 |
Product code cannot be null |
BCREAS-05 |
Contract reference number cannot be null |
BCREAS-06 |
No unauthorized contracts exist for reassignment for product ‘$1’ |
BCREAS-07 |
The BC contract reference number is not valid for the product code selected |
BC-LD001 |
Tenor/Tenor Units/Exchange Rate is not maintained |
BC-LD002 |
Value cannot be less than 0 |
BC-LD003 |
Customer ID/Bill Currency is not entered |
BC-LD004 |
Suspense Gl/ Loan Product cannot be null when advance by loan is checked |
BC-LD005 |
Cannot delete a Loan created from a Bill |
BC-LD006 |
Cannot authorize a Loan created from a Bill until the bill is authorized |
BC-LD008 |
The loan is linked to a bill with reference no $1 |
BC-LD010 |
Loan creation is allowed only when operation is Acceptance and product type is Import |
BC-AC034 |
Acceptance Commission acp_from_date is not available for Bills and Collections Contract Reference Number $1 and Event Sequence Number $2 |
BC-AC035 |
Acceptance Commission acp_to_date is not available for Advance collection type for Bills & Collections Contract Reference Number $1 and Event Sequence Number $2 |
BC-AC036 |
Acceptance Commission acp_from_date cannot be GREATER than Today for Bills & Collections Contract Reference Number $1 and Event Sequence Number $2 |
BC-AC037 |
Acceptance Commission From and To Dates are mandatory for a Bill whose Interest Collection in Advance |
BC-AC038 |
For a Bill in Final stage Acceptance From Date is Mandatory |
BC-AC039 |
Acceptance To Date cannot be lesser than Acceptance From Date |
BC-AC040 |
Acceptance From Date cannot be greater than Today |
BC-AC060 |
Acceptance Commission From Date for Interest Calculation $1 is a holiday for Currency $2. OK to Proceed? |
BC-AC061 |
Acceptance Commission From date for Interest Calculation $1 is a Local holiday for Current branch. OK to Proceed? |
BC-AC062 |
Acceptance CommissionTo date for Interest Calculation $1 is a holiday for Currency $2. OK to Proceed? |
BC-AC063 |
Acceptance Commission To date for Interest Calculation $1 is a Local holiday for Current branch. OK to Proceed? |
BC-AC064 |
Interest From Date cannot be null when To Date is present |
BC-AC065 |
Acceptance Commission component in the preferences cannot be the main component or overdue component |
BC-AUT-001 |
Authorization failed for the product |
BC-XV181 |
Interest Liquidation Mode Cannot Be Null During Full Liquidation of Bill Amount |
BC-XV182 |
Interest Components Will Not Be Liquidated For Deferred Type Of Interest Liquidation Mode. Proceed? |
BC-PMT01 |
Amount Paid Cannot Be Greater Than Amount Due For Overdue Components |
BC-ROLL100 |
Rollover Allowed only for Import Advance Bill type |
BC-ROLL101 |
Rollover cannot be done before Maturity |
BC-ROLL102 |
Rollover not allowed for zero due bill amount |
BC-ROLL103 |
Contract status is not Active |
BC-ROLL104 |
Contract is unauthorized |
BC-ROLL105 |
ROLL event not maintained at product |
BC-ROLL106 |
Rollover not allowed for this product |
BC-ROLL110 |
Maturity Date cannot be null |
BC-ROLL111 |
From Date cannot be null |
BC-ROLL112 |
Interest Liquidation Mode cannot be null |
BC-ROLL114 |
Tenor cannot be zero |
BC-ROLL115 |
Maturity Date cannot earlier than base date |
BC-ROLL116 |
From Date cannot be in Future |
BC-ROLL117 |
To date cannot be earlier than From date |
BC-ROLL118 |
Rollover details not present for the contract |
BC-ROLL119 |
Details allowed only during Rollover event |
BC-ROLL120 |
Cannot delete the Child Contract |
BC-ROLL121 |
From date in the preferences is earlier than from date of the contract |
BC-ROLL122 |
Rollover Tab not visited |
BC-ROLL123 |
Rollover not allowed for Bills under Initial Stage |
BC-ROLL124 |
Cannot authorize child contract |
BC-ROLL130 |
Rollover is set for Auto liquidation |
BC-XV183 |
Acceptance Commission FROM DATE Should Be Less Than TO DATE |
BC-XV184 |
Acceptance Commission From Date Cannot Be Null |
BC-XV185 |
Acceptance Commission TO DATE Cannot Be Null |
BC-XV208 |
Defaulting Tenor Days To $1 Based on Maturity Date and Base Date |
BC-XV300 |
Interest calculation TO DATE And FROM DATE should be same for Sight Bills |
BC-XV301 |
Maturity Date Cannot Be Less Than Today's Date |
BC-DA001 |
BC - Discount Accrual Backup failed |
BC-LD110 |
The Bill Is Linked To A Loan With Reference no $1 |
BC-AC068 |
Acceptance Commission Preferences - Interest Component in the preferences screen will be reset |
BC-UP1023 |
Allow Rollover Is Not Maintained For The Product $1 |
BC-UP1024 |
Advance By Loan Is Not Maintained For The Product $1 |
BC-AC066 |
Both Acceptance to Advance field (at product level) and Advance by loan field are checked. Acceptance to Advance will take precedence over Advance by Loan. |
BC-AC067 |
Both Auto Liquidation field and Advance by loan field are checked. Auto Liquidation will take precedence over Advance by Loan. |
BC-30080 |
Accrual required and Consider as discount are mutually exclusive |
LCUPLD-353 |
Customer Details Should Be Provided For $1 Party Type |