Error List

The following table lists the errors that may occur while executing various batches in the transaction feed management process. It also indicates how you can resolve these errors.

Batch Name Message Number Error Message Message Category Possible Issues
C1-TXNHV 102 {Checksum Validation Required} field invalid. 11001 The possible issues could be:

  • The value other than 'Y', 'y', 'N' or 'n' is specified for the Checksum Validation Required parameter.
C1-TXNHV 102 {Duplicate Check Required} field invalid. 11001 The possible issues could be:

  • The value other than 'Y', 'y', 'N' or 'n' is specified for the Duplicate Check Required parameter.
C1-TXNHV 1314 The Transaction Source is mandatory. 17000 The possible issues could be:

  • The data is not available in the Transaction Source column.
C1-TXNHV 1332 Sum of transaction records in the header does not match the total number of records in the file. 17000 The possible issues could be:

  • Inappropriate file is uploaded in the system.
C1-TXNHV 1333 Sum of transaction volume in the header does not match the total transaction volume in the file. 17000 The possible issues could be:

  • Inappropriate file is uploaded in the system.
C1-TXNHV 1334 Sum of transaction amount in the header does not match the total transaction amount in the file. 17000 The possible issues could be:

  • Inappropriate file is uploaded in the system.
C1-TXNHV 1338 The Transaction Header ID already exists in the system. Please enter unique header ID. 17000 The possible issues could be:

  • The same file is uploaded multiple times in the system.
C1-TXNHV 1341 Exception occurred during the transaction header validation. 17000 The possible issues could be:

  • The data is not available in the required format.
C1-TXNHV 1421 Transaction records does not exist in the file. Please check. 17000 The possible issues could be:

  • Inappropriate file is uploaded in the system.
C1-TXNHV 1422 Sum of transaction records in the header cannot be zero. Please enter valid data in the header. 17000 The possible issues could be:

  • The value available in the Number of Transactions column is less than or equal to zero.
C1-TXNHV 1423 Sum of transaction volume in the header cannot be zero. Please enter valid data in the header. 17000 The possible issues could be:

  • The value available in the Total Transaction Volume column is less than or equal to zero.
C1-TXNHV 1663 Transaction Header External Id is missing. 17000 The possible issues could be:

  • The data is not available in the Transaction Header ID column.
C1-TXNHV 1664 Header Transaction Amount should be greater than 0. 17000 The possible issues could be:

  • The value available in the Total Transaction Amount column is less than or equal to zero.
C1-TXNIP 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-TXNIP 102 { Maximum Batch Size } field invalid 11001 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is greater than the value specified for the Chunk Size parameter.
C1-TXNIP 106 Value { Given Transaction Header Id } too long for field { transactionHeaderId }. Maximum length: 14. Found: { Length of given Transaction Header Id} 11001 The possible issues could be:

  • The value specified for the Transaction Header ID parameter exceeds the maximum length of 14 characters.
C1-TXNIP 106 Value { Given Transaction Source Code } too long for field { transactionSource }. Maximum length: 30. Found: { Length of given Transaction Source Code} 11001 The possible issues could be:

  • The value specified for the Transaction Source parameter exceeds the maximum length of 30 characters.
C1-TXNIP 106 Value { Given Transaction Division } too long for field { division }. Maximum length: 5 Found: { Length of given Transaction Division} 11001 The possible issues could be:

  • The value specified for the Division parameter exceeds the maximum length of 5 characters.
C1-TXNIP 1301 The account with the specified identifier does not exist in the system. Enter a valid identifier. 17000 The possible issues could be:

  • The account with the specified account identifier is not found in the system.
C1-TXNIP 1302 UDF_​CURRENCY_​1 is mandatory when UDF_​AMT_​1 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​1 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1303 UDF_​AMT_​1 is mandatory when UDF_​CURRENCY_​1 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​1 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1304 UDF_​CURRENCY_​2 is mandatory when UDF_​AMT_​2 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​2 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1305 UDF_​AMT_​2 is mandatory when UDF_​CURRENCY_​2 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​2 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1306 UDF_​CURRENCY_​3 is mandatory when UDF_​AMT_​3 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​3 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1307 UDF_​AMT_​3 is mandatory when UDF_​CURRENCY_​3 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​3 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1308 UDF_​CURRENCY_​4 is mandatory when UDF_​AMT_​4 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​4 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1309 UDF_​AMT_​4 is mandatory when UDF_​CURRENCY_​4 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​4 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1310 UDF_​CURRENCY_​5 is mandatory when UDF_​AMT_​5 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​5 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1311 UDF_​AMT_​5 is mandatory when UDF_​CURRENCY_​5 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​5 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1312 UDF_​CURRENCY_​6 is mandatory when UDF_​AMT_​6 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​6 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1313 UDF_​AMT_​6 is mandatory when UDF_​CURRENCY_​6 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​6 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1314 UDF_​CURRENCY_​7 is mandatory when UDF_​AMT_​7 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​7 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1315 UDF_​AMT_​7 is mandatory when UDF_​CURRENCY_​7 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​7 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1316 UDF_​CURRENCY_​8 is mandatory when UDF_​AMT_​8 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​8 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1317 UDF_​AMT_​8 is mandatory when UDF_​CURRENCY_​8 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​8 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1318 UDF_​CURRENCY_​9 is mandatory when UDF_​AMT_​9 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​9 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1319 UDF_​AMT_​9 is mandatory when UDF_​CURRENCY_​9 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​9 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1320 UDF_​CURRENCY_​10 is mandatory when UDF_​AMT_​10 is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​10 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1321 UDF_​AMT_​10 is mandatory when UDF_​CURRENCY_​10 is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the UDF_​AMT_​10 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1347 Could not derive a price item from the rules engine. 17000 The possible issues could be:

  • There is some technical issue while executing the rule or while processing the rule output.

  • No rules are effective on the processing date.

  • The rule type is not defined for the transaction source and transaction record type combination in the system.
C1-TXNIP 1349 Division is invalid. Please enter a valid division for the transaction. 17000 The possible issues could be:

  • Division (to which the transaction belongs) is not defined in the system.
C1-TXNIP 1351 Transaction Currency is invalid. Please enter a valid currency code. 17000 The possible issues could be:

  • The currency in which the transaction was performed is not available in the Transaction Currency column.

  • Currency is not defined in the system.
C1-TXNIP 1362 UDF Currency 1 is invalid. Please enter a valid currency code. 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 1363 UDF Currency 2 is invalid. Please enter a valid currency code. 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 1364 UDF Currency 3 is invalid. Please enter a valid currency code. 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 1365 UDF Currency 4 is invalid. Please enter a valid currency code. 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 1366 UDF Currency 5 is invalid. Please enter a valid currency code. 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 1377 Transaction currency is mandatory when transaction amount is non-zero. Enter a valid currency code. 17000 The possible issues could be:

  • The currency is not available in the Transaction Currency column.
C1-TXNIP 1378 Transaction amount is mandatory when transaction currency is specified. Enter the amount. 17000 The possible issues could be:

  • The amount is not available in the Transaction Amount column.
C1-TXNIP 1379 The user does not exist in the system. Please enter a valid user ID. 17000 The possible issues could be:

  • The user is not defined in the system.
C1-TXNIP 1380 The value entered in the Credit/Debit Indicator column is incorrect. Enter either "+" or "-". 17000 The possible issues could be:

  • The value other than “+” or “-” is available in the HOW_​TO_​USE_​TXN_​FLG column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1381 The value entered in the Manual Switch field is incorrect. Enter either "Y" or "N". 17000 The possible issues could be:

  • The value other than “Y” or “N” is available in the MANUAL_​SW column of the CI_​TXN_​DETAIL table.
C1-TXNIP 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.
C1-TXNIP 1636 Invalid batch run [%1] for [%2] division(s). %3
Note:

[%1] stands for batch code;

[%2] stands for division;

[%3] stands for expected batch code

 17000 The possible issues could be:

  • You are trying to execute the C1-TXNVP, C1-TXNEX, C1-TXNSQ, C1-TXNCM or C1-TXNCU batch instead of the C1-TXNIP batch (which is first mandatory batch in the transaction aggregation cycle).
C1-TXNIP 1637 Batch [%1] is already executed for [%2] division(s). Please complete pending batch runs before starting new cycle for [%3] division(s).
Note:

[%1] stands for batch code;

[%2] and [%3] stands for division

 17000 The possible issues could be:

  • You are trying to execute this batch once again with the same division (for example, D1) after executing any other batch in the transaction aggregation cycle which is already initiated for D1.

C1-TXNIP 1638 Transaction Feed Management cycle for individual division(s) is not yet complete. Please complete pending batch runs before starting new cycle for processing [ALL] divisions. 17000 The possible issues could be:

  • You are trying to execute this batch for all divisions before completing the transaction aggregation cycle which is initiated for a particular division.
C1-TXNIP 1639 Transaction Feed Management cycle for [ALL] divisions is not yet complete. Please complete pending batch runs before starting new cycle for individual division [%1].
Note: [%1] stands for division
 17000 The possible issues could be:

  • You are trying to execute this batch for a particular division before completing the transaction aggregation cycle which is initiated for all divisions.
C1-TXNIP 1646 Value for mandatory parameter is missing. 17000 The possible issues could be:

  • No value is defined for the mandatory price item parameter in the rule.
C1-TXNIP 1647 Mandatory parameter is missing. 17000 The possible issues could be:

  • The mandatory price item parameter is not defined as the output parameter in the rule.
C1-TXNIP 1648 Account Number derived by the rule is invalid. 17000 The possible issues could be:

  • No value is defined for either Account Identifier (ACCT_​NOX_​Val) or Account Identifier Column Name (ACCT_​NOX_​Col) output parameter in the rule.
C1-TXNIP 1649 Account Number type code derived by the rule is invalid. 17000 The possible issues could be:

  • No value is defined for either Account Identifier Type (ACCT_​NO_​TYPEX_​Val) or Account Identifier Type Column Name (ACCT_​NO_​TYPEX_​Col) output parameter in the rule.
C1-TXNIP 1650 Division derived by the rule is invalid. 17000 The possible issues could be:

  • No value is defined for either Account Division (DIVISIONX_​VAL) or Account Division Column Name (DIVISIONX_​COL) output parameter in the rule.
C1-TXNIP 1651 Not able to derive account ID. 17000 The possible issues could be:

  • The account with the specified account identifier type, account identifier, and division is not found in the system.
C1-TXNIP 1652 Product derived by the rule is invalid. 17000 The possible issues could be:

  • No value is defined for either Product Name (PRODUCTX_​Y_​Val) or Product Column Name (PRODUCTX_​Y_​Col) output parameter in the rule.
C1-TXNIP 1653 Length of the derived product is greater than 10. 17000 The possible issues could be:

  • The value specified for the Product Name (PRODUCTX_​Y_​Val) or Product Column Name (PRODUCTX_​Y_​Col) output parameter in the rule exceeds the maximum length of 10 characters.
C1-TXNIP 1654 Length of the derived variance parameter is greater than 8. 17000 The possible issues could be:

  • The value specified for the TOU (TOUX_​Y_​Val) or TOU Column Name (TOUX_​Y_​Col) output parameter in the rule exceeds the maximum length of 8 characters.
C1-TXNIP 1656 Length of the product parameter value derived by the rule is greater than 254. 17000 The possible issues could be:

  • The value specified for the Parameter Value (PVLX_​Y_​Z_​VAL) or Parameter Value Column Name (PVLX_​Y_​Z_​COL) output parameter in the rule exceeds the maximum length of 254 characters.
C1-TXNIP 1657 Length of the product parameter code derived by the rule is greater than 30. 17000 The possible issues could be:

  • The value specified for the Parameter Code (PCDX_​Y_​Z_​VAL) output parameter in the rule exceeds the maximum length of 30 characters.
C1-TXNIP 2002 Transaction is in EROR due to one or more reasons. 17000 The possible issues could be:

  • There might be one or more reasons why the status of the transaction is set to Error (EROR).
C1-TXNIP 2007 %1 cannot be blank.
Note: [%1] stands for division
 17000 The possible issues could be:

  • The division to which the transaction belongs is not available in the Division column.
C1-TXNIP 2007 %1 cannot be blank.
Note: [%1] stands for user ID
 17000 The possible issues could be:

  • No data exists in the USER_​ID column of the CI_​TXN_​DETAIL table when the MANUAL_​SW column is set to Y.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for “Currency Code”;

[%2] stands for “Transaction Amount”

 17000 The possible issues could be:

  • The currency in which the transaction was performed is not available in the CURRENCY_​CD column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 1 Currency Code";

[%2] stands for "Additional Amount 1"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​1 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 2 Currency Code";

[%2] stands for "Additional Amount 2"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​2 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 3 Currency Code";

[%2] stands for "Additional Amount 3"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​3 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 4 Currency Code";

[%2] stands for "Additional Amount 4"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​4 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 5 Currency Code";

[%2] stands for "Additional Amount 5"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​5 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 6 Currency Code";

[%2] stands for "Additional Amount 6"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​6 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 7 Currency Code";

[%2] stands for "Additional Amount 7"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​7 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 8 Currency Code";

[%2] stands for "Additional Amount 8"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​8 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 9 Currency Code";

[%2] stands for "Additional Amount 9"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​9 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2011 %1 is mandatory when %2 is non-zero. Enter a valid currency code.
Note:

[%1] stands for "Amount 10 Currency Code";

[%2] stands for "Additional Amount 10"

 17000 The possible issues could be:

  • The currency is not available in the UDF_​CURRENCY_​CD_​10 column of the CI_​TXN_​DETAIL table.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Currency Code";

[%2] stands for transaction currency

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 1 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​1

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 2 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​2

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 3 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​3

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 4 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​4

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 5 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​5

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 6 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​6

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 7 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​7

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 8 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​8

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 9 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​9

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2012 %1 %2 is invalid. Please enter a valid currency code.
Note:

[%1] stands for "Amount 10 Currency Code";

[%2] stands for UDF_​CURRENCY_​CD_​10

 17000 The possible issues could be:

  • Currency is not defined in the system.
C1-TXNIP 2013 The user %1 does not exist in the system. Please enter a valid user ID.
Note: [%1] stands for user ID
 17000 The possible issues could be:

  • The user is not defined in the system.
C1-TXNIP 2014 %1 derived using %2 by the rule is invalid.
Note:

[%1] stands for "Account Number"

[%2] stands for the ACCT_​NOX_​Val or ACCT_​NOX_​Col output parameter

 17000 The possible issues could be:

  • No value is defined for either Account Identifier (ACCT_​NOX_​Val) or Account Identifier Column Name (ACCT_​NOX_​Col) output parameter in the rule.
C1-TXNIP 2014 %1 derived using %2 by the rule is invalid.
Note:

[%1] stands for "Account Identifier Type"

[%2] stands for the ACCT_​NO_​TYPEX_​Val or ACCT_​NO_​TYPEX_​Col output parameter

 17000 The possible issues could be:

  • No value is defined for either Account Identifier Type (ACCT_​NO_​TYPEX_​Val) or Account Identifier Type Column Name (ACCT_​NO_​TYPEX_​Col) output parameter in the rule.
C1-TXNIP 2014 %1 derived using %2 by the rule is invalid.
Note:

[%1] stands for "Division"

[%2] stands for the DIVISIONX_​VAL or DIVISIONX_​COL output parameter

 17000 The possible issues could be:

  • No value is defined for either Account Division (DIVISIONX_​VAL) or Account Division Column Name (DIVISIONX_​COL) output parameter in the rule.
C1-TXNIP 2014 %1 derived using %2 by the rule is invalid.
Note:

[%1] stands for "Initial Product Code"

[%2] stands for the PRODUCTX_​Y_​Val or PRODUCTX_​Y_​Col output parameter

 17000 The possible issues could be:

  • No value is defined for either Product Name (PRODUCTX_​Y_​Val) or Product Column Name (PRODUCTX_​Y_​Col) output parameter in the rule.
C1-TXNIP 2015 Not able to derive account id for given Account Number %1, Account Number Type Code %2 and Division %3.
Note:

[%1] stands for account identifier;

[%2] stands for account identifier type;

[%3] stands for division

 17000 The possible issues could be:

  • The account with the specified account identifier type, account identifier and division is not found in the system.
C1-TXNIP 2016 Length of the derived %1 using %2 by the rule is greater than %3.
Note:

[%1] stands for "Initial Product Code";

[%2] stands for PRODUCTX_​Y_​Val or PRODUCTX_​Y_​Col output parameter;

[%3] stands for length of product code (i.e. 30)

 17000 The possible issues could be:

  • The value specified for the Product Name (PRODUCTX_​Y_​Val) or Product Column Name (PRODUCTX_​Y_​Col) output parameter in the rule exceeds the maximum length of 30 characters.
C1-TXNIP 2016 Length of the derived %1 using %2 by the rule is greater than %3.
Note:

[%1] stands for "Variance Parameter";

[%2] stands for TOUX_​Y_​Val or TOUX_​Y_​Col output parameter;

[%3] stands for length of variance parameter (i.e. 8)

 17000 The possible issues could be:

  • The value specified for the TOU (TOUX_​Y_​Val) or TOU Column Name (TOUX_​Y_​Col) output parameter in the rule exceeds the maximum length of 8 characters.
C1-TXNIP 2016 Length of the derived %1 using %2 by the rule is greater than %3.
Note:

[%1] stands for "Parameter";

[%2] stands for PCDX_​Y_​Z_​VAL output parameter;

[%3] stands for length of parameter (i.e. 30)

 17000 The possible issues could be:

  • The value specified for the Parameter Code (PCDX_​Y_​Z_​VAL) output parameter in the rule exceeds the maximum length of 30 characters.
C1-TXNIP 2016 Length of the derived %1 using %2 by the rule is greater than %3.
Note:

[%1] stands for "Parameter Value";

[%2] stands for PVLX_​Y_​Z_​VAL or PVLX_​Y_​Z_​COL output parameter;

[%3] stands for length of parameter value (i.e. 254)

 17000 The possible issues could be:

  • The value specified for the Parameter Value (PVLX_​Y_​Z_​VAL) or Parameter Value Column Name (PVLX_​Y_​Z_​COL) output parameter in the rule exceeds the maximum length of 254 characters.
C1-TXNIP 2017 Mandatory parameter %1 is missing for %2 %3 and processing date %4.
Note:

[%1] stands for the product parameter code;

[%2] stands for "Initial Product Code"

[%3] stands for the product code

[%4] stands for the processing date

 17000 The possible issues could be:

  • The mandatory product parameter is not defined as the output parameter in the rule.
C1-TXNIP 2018 Value for mandatory parameter %1 is missing for product %2 and processing date %3.
Note:

[%1] stands for product parameter code;

[%2] stands for product code;

[%3] stands for processing date

 17000 The possible issues could be:

  • No value is defined for the mandatory product parameter in the rule.
C1-TXNIP 2019 Value of the derived %1 %2 contains '~' or '='.
Note:

[%1] stands for parameter code

[%2] stands for parameter value

 17000 The possible issues could be:

  • The parameter code or value contains the equal to (=) and tide (~) symbols.
C1-TXNIP 2037 Error during executing rules for transaction record type %1, transaction source %2 and processing date %3.
Note:

[%1] stands for transaction record type;

[%2] stands for transaction source;

[%3] stands for processing date

 17000 The possible issues could be:

  • There is some technical issue while executing the rule or while processing the rule output.

  • No rules are effective on the processing date.

  • The rule type is not defined for the transaction source and transaction record type combination in the system.
C1-TXNIP 2043 Unable to derive Rule Type with Transaction Source %1 and Transaction Record Type %2.
Note:

[%1] stands for transaction source;

[%2] stands for transaction record type

 17000 The possible issues could be:

  • The rule type is not defined for the transaction source and transaction record type combination in the system.
C1-TXNIP 2087 Division %1 is invalid. Please enter a valid division for the transaction.
Note: [%1] stands for division
 17000 The possible issues could be:

  • Division (to which the transaction belongs) is not defined in the system.
C1-TXNVP 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-TXNVP 106 Value { Given Transaction Header Id } too long for field { transactionHeaderId }. Maximum length: 14. Found: { Length of given Transaction Header Id} 11001 The possible issues could be:

  • The value specified for the Transaction Header ID parameter exceeds the maximum length of 14 characters.
C1-TXNVP 106 Value { Given Transaction Source Code } too long for field { transactionSource }. Maximum length: 30. Found: { Length of given Transaction Source Code} 11001 The possible issues could be:

  • The value specified for the Transaction Source parameter exceeds the maximum length of 30 characters.
C1-TXNVP 106 Value { Given Transaction Division } too long for field { division }. Maximum length: 5 Found: { Length of given Transaction Division} 11001 The possible issues could be:

  • The value specified for the Division parameter exceeds the maximum length of 5 characters.
C1-TXNVP 1636 Invalid batch run [%1] for [%2] division(s). %3
Note:

[%1] stands for batch code;

[%2] stands for division;

[%3] stands for expected batch code

 17000 The possible issues could be:

  • You are trying to execute the C1-TXNVP batch before executing the C1-TXNIP batch (which is first mandatory batch in the transaction aggregation cycle).

  • You are trying to execute the C1-TXNVP batch in between the C1-TXNCM and C1-TXNCU batches during the transaction aggregation cycle.
C1-TXNVP 1638 Transaction Feed Management cycle for individual division(s) is not yet complete. Please complete pending batch runs before starting new cycle for processing [ALL] divisions. 17000 The possible issues could be:

  • You are trying to execute this batch for all divisions before completing the transaction aggregation cycle which is initiated for a particular division.
C1-TXNVP 1639 Transaction Feed Management cycle for [ALL] divisions is not yet complete. Please complete pending batch runs before starting new cycle for individual division [%1].
Note: [%1] stands for division
 17000 The possible issues could be:

  • You are trying to execute this batch for a particular division before completing the transaction aggregation cycle which is initiated for all divisions.
C1-TXNVP 1644 Transaction Feed Management cycle for division(s) [%1] is already in progress with filter [Source= %2, Header= %3] criteria. Filter criteria must be same for complete cycle.
Note:

[%1] stands for division;

[%2] stands for transaction source;

[%3] stands for transaction header ID

 17000 The possible issues could be:

  • You are trying to execute this batch once again with the same division and different parameters.
C1-TXNEX 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-TXNEX 102 { Maximum Batch Size } field invalid 11001 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is greater than the value specified for the Chunk Size parameter.
C1-TXNEX 106 Value { Given Transaction Header Id } too long for field { transactionHeaderId }. Maximum length: 14. Found: { Length of given Transaction Header Id} 11001 The possible issues could be:

  • The value specified for the Transaction Header ID parameter exceeds the maximum length of 14 characters.
C1-TXNEX 106 Value { Given Transaction Source Code } too long for field { transactionSource }. Maximum length: 30. Found: { Length of given Transaction Source Code} 11001 The possible issues could be:

  • The value specified for the Transaction Source parameter exceeds the maximum length of 30 characters.
C1-TXNEX 106 Value { Given Transaction Division } too long for field { division }. Maximum length: 5 Found: { Length of given Transaction Division} 11001 The possible issues could be:

  • The value specified for the Division parameter exceeds the maximum length of 5 characters.
C1-TXNEX 790 The selected Member account does not have active Contracts. 17000 The possible issues could be:

  • There are no contracts for the account in Active, Pending Stop, or Stop status on the transaction date.
C1-TXNEX 1336 Effective pricing is not available for the product. Please check. 17000 The possible issues could be:

  • The effective pricing is not available for the product.
C1-TXNEX 1392 Invalid configuration of Price Search Algorithm Parameters or Contracts or Schedule Periods. 17000 The possible issues could be:

  • The parameter values are either not defined or invalid in the Price Assignment Search algorithm (which is associated with the division).

  • The period in which the transaction date falls is not defined in the aggregation schedule.

  • There are multiple effective contracts of the same contract type (available on the transaction date) in Active, Pending Stop, or Stop status.
C1-TXNEX 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.
C1-TXNEX 1588 No Schedule Period found for the transaction date. 17000 The possible issues could be:

  • The period in which the transaction date falls is not defined in the aggregation schedule.
C1-TXNEX 1611 Division specific Price Search Algorithm is not configured. 17000 The possible issues could be:

  • The Price Assignment Search algorithm is not defined for the division.
C1-TXNEX 1612 Price Search Algorithm parameters are not set or are invalid. 17000 The possible issues could be:

  • The parameter values are either not defined or invalid in the Price Assignment Search algorithm (which is associated with the division).

C1-TXNEX 1613 Multiple contracts in Active, Pending Stop, Stop status exists for same contract type. 17000 The possible issues could be:

  • There are multiple effective contracts of the same contract type in Active, Pending Stop, or Stop status on the transaction date.
C1-TXNEX 1636 Invalid batch run [%1] for [%2] division(s). %3
Note:

[%1] stands for batch code;

[%2] stands for division;

[%3] stands for expected batch code

 17000 The possible issues could be:

  • You are trying to execute the C1-TXNEX batch before executing the C1-TXNIP batch (which is first mandatory batch in the transaction aggregation cycle).

  • You are trying to execute the C1-TXNEX batch in between the C1-TXNCM and C1-TXNCU batches during the transaction aggregation cycle.
C1-TXNEX 1638 Transaction Feed Management cycle for individual division(s) is not yet complete. Please complete pending batch runs before starting new cycle for processing [ALL] divisions. 17000 The possible issues could be:

  • You are trying to execute this batch for all divisions before completing the transaction aggregation cycle which is initiated for a particular division.
C1-TXNEX 1639 Transaction Feed Management cycle for [ALL] divisions is not yet complete. Please complete pending batch runs before starting new cycle for individual division [%1].
Note: [%1] stands for division
 17000 The possible issues could be:

  • You are trying to execute this batch for a particular division before completing the transaction aggregation cycle which is initiated for all divisions.
C1-TXNEX 1644 Transaction Feed Management cycle for division(s) [%1] is already in progress with filter [Source= %2, Header= %3] criteria. Filter criteria must be same for complete cycle.
Note:

[%1] stands for division;

[%2] stands for transaction source;

[%3] stands for transaction header ID

 17000 The possible issues could be:

  • You are trying to execute this batch once again with the same division and different parameters.
C1-TXNIP 2003 One or more Sub Transactions are in EROR state. 17000 The possible issues could be:

  • One or more transaction legs are in the Error (EROR) status.
C1-TXNEX 2006 No active contract exists for account %1, product %2 and transaction date %3.
Note: [%1] stands for derived account; [%2] stands for derived product; and [%3] stands for transaction date
 17000 The possible issues could be:

  • There is no contract with the specified contract type available on the transaction date.

  • The contract is inactive.
C1-TXNEX 2020 Invalid configuration of Price Search Algorithm Parameters or Contracts or Schedule Periods for division %1, account %2, product %3, transaction date %4 and processing date %5.
Note:

[%1] stands for derived division;

[%2] stands for derived account;

[%3] stands for derived product;

[%4] stands for transaction date;

[%5] stands for processing date

 17000 The possible issues could be:

  • The parameter values are either not defined or invalid in the Price Assignment Search algorithm (which is associated with the division).

  • The period in which the transaction date falls is not defined in the aggregation schedule.

  • There are multiple effective contracts of the same contract type (available on the transaction date) in Active, Pending Stop, or Stop status.
C1-TXNEX 2021 Division specific Price Search Algorithm is not configured for division %1 and processing date %2.
Note:

[%1] stands for derived division;

[%2] stands for processing date

 17000 The possible issues could be:

  • The Price Assignment Search algorithm is not defined for the derived division on the processing date.
C1-TXNEX 2022 Price Search Algorithm parameters are not set or are invalid for division %1 and processing date %2.
Note:

[%1] stands for derived division;

[%2] stands for processing date

 17000 The possible issues could be:

  • The parameter values are either not defined or invalid in the Price Assignment Search algorithm which is associated with the derived division on the processing date.

C1-TXNEX 2023 Effective pricing is not available for account %1, product %2, parameters %3 and processing date %4.
Note:

[%1] stands for derived account;

[%2] stands for derived product;

[%3] stands for derived product parameter;

[%4] stands for processing date

 17000 The possible issues could be:

  • The effective pricing is not available for the account, product and product parameters combination on the processing date.
C1-TXNEX 2024 No Schedule Period found for product %1, price assignment id %2 and transaction date %3.
Note:

[%1] stands for derived product;

[%2] stands for price assignment ID;

[%3] stands for transaction date

 17000 The possible issues could be:

  • The period in which the transaction date falls is not defined in the aggregation schedule (which is used in the product pricing).
C1-TXNEX 2025 Multiple contracts in Active, Pending Stop, Stop status exists for same contract type against account %1, product %2 and transaction date %3.
Note:

[%1] stands for derived account;

[%2] stands for derived product;

[%3] stands for transaction date

 17000 The possible issues could be:

  • There are multiple effective contracts of the same contract type in Active, Pending Stop, or Stop status on the transaction date.
C1-TXNEX 2026 No active contract exists for account %1, product %2 and transaction date %3.
Note:

[%1] stands for derived account;

[%2] stands for derived product;

[%3] stands for transaction date

 17000 The possible issues could be:

  • There are no contracts for the account in Active, Pending Stop, or Stop status on the transaction date.
C1-TXNSQ 102 { Maximum Batch Size } field invalid 11001 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is greater than the value specified for the Chunk Size parameter.
C1-TXNSQ 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-TXNSQ 106 Value { Given Transaction Header Id } too long for field { transactionHeaderId }. Maximum length: 14. Found: { Length of given Transaction Header Id} 11001 The possible issues could be:

  • The value specified for the Transaction Header ID parameter exceeds the maximum length of 14 characters.
C1-TXNSQ 106 Value { Given Transaction Source Code } too long for field { transactionSource }. Maximum length: 30. Found: { Length of given Transaction Source Code} 11001 The possible issues could be:

  • The value specified for the Transaction Source parameter exceeds the maximum length of 30 characters.
C1-TXNSQ 106 Value { Given Transaction Division } too long for field { division }. Maximum length: 5 Found: { Length of given Transaction Division} 11001 The possible issues could be:

  • The value specified for the Division parameter exceeds the maximum length of 5 characters.
C1-TXNSQ 1388 Data configuration error for { ENV_​ID }. 17000 The possible issues could be:

  • No data exists in the ENV_​ID column of the CI_​INSTALLATION table.

  • The data available in the ENV_​ID column of the CI_​INSTALLATION table is not properly cached.
C1-TXNSQ 1388 Data configuration error for { SQI Fragment }. 17000 The possible issues could be:

  • No data exists in the SQL_​FRAG, TXN_​PRM, SQI_​CD, and SQL_​FUNC columns of the CI_​TXN_​SQI_​FRAG table.

  • The data available in the SQL_​FRAG, TXN_​PRM, SQI_​CD, and SQL_​FUNC columns of the CI_​TXN_​SQI_​FRAG table is not properly cached.
C1-TXNSQ 1388 Data configuration error for { Price Item SQI }. 17000 The possible issues could be:

  • No data exists in the PRICEITEM_​CD, CIS_​DIVISION, and SQI_​CD columns of the CI_​PRICEITEM_​SQI table.

  • The data available in the PRICEITEM_​CD, CIS_​DIVISION, and SQI_​CD columns of the CI_​PRICEITEM_​SQI table is not properly cached.
C1-TXNSQ 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.
C1-TXNSQ 1636 Invalid batch run [%1] for [%2] division(s). %3
Note:

[%1] stands for batch code;

[%2] stands for division;

[%3] stands for expected batch code

 17000 The possible issues could be:

  • You are trying to execute the C1-TXNSQ batch before executing the C1-TXNIP batch (which is first mandatory batch in the transaction aggregation cycle).

  • You are trying to execute the C1-TXNSQ batch in between the C1-TXNCM and C1-TXNCU batches during the transaction aggregation cycle.
C1-TXNSQ 1638 Transaction Feed Management cycle for individual division(s) is not yet complete. Please complete pending batch runs before starting new cycle for processing [ALL] divisions. 17000 The possible issues could be:

  • You are trying to execute this batch for all divisions before completing the transaction aggregation cycle which is initiated for a particular division.
C1-TXNSQ 1639 Transaction Feed Management cycle for [ALL] divisions is not yet complete. Please complete pending batch runs before starting new cycle for individual division [%1].
Note: [%1] stands for division
 17000 The possible issues could be:

  • You are trying to execute this batch for a particular division before completing the transaction aggregation cycle which is initiated for all divisions.
C1-TXNSQ 1644 Transaction Feed Management cycle for division(s) [%1] is already in progress with filter [Source= %2, Header= %3] criteria. Filter criteria must be same for complete cycle.
Note:

[%1] stands for division;

[%2] stands for transaction source;

[%3] stands for transaction header ID

 17000 The possible issues could be:

  • You are trying to execute this batch once again with the same division and different parameters.
C1-TXNSQ 2003 One or more Sub Transactions are in EROR state. 17000 The possible issues could be:

  • One or more transaction legs are in the Error (EROR) status.
C1-TXNSQ 2026 SQIs not configured for product %1 and division %2.
Note:

[%1] stands for final product code;

[%2] stands for derived division

 17000 The possible issues could be:

  • The SQIs are not defined for the product - division combination.
C1-TXNSQ 2027 Currency Conversion from Currency [%1] to Currency [%2] not successful. 17000 The possible issues could be:

  • The exchange rate is not available during currency conversion.
C1-TXNCM 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-TXNCM 102 { Maximum Batch Size } field invalid 11001 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is greater than the value specified for the Chunk Size parameter.
C1-TXNCM 106 Value { Given Transaction Header Id } too long for field { transactionHeaderId }. Maximum length: 14. Found: { Length of given Transaction Header Id} 11001 The possible issues could be:

  • The value specified for the Transaction Header ID parameter exceeds the maximum length of 14 characters.
C1-TXNCM 106 Value { Given Transaction Source Code } too long for field { transactionSource }. Maximum length: 30. Found: { Length of given Transaction Source Code} 11001 The possible issues could be:

  • The value specified for the Transaction Source parameter exceeds the maximum length of 30 characters.
C1-TXNCM 106 Value { Given Transaction Division } too long for field { division }. Maximum length: 5 Found: { Length of given Transaction Division} 11001 The possible issues could be:

  • The value specified for the Division parameter exceeds the maximum length of 5 characters.
C1-TXNCM 1393 Either the transaction feed management setup is incomplete, or there is no active contract available. 17000 The possible issues could be:

  • The SQIs are not defined for the product - division combination.

  • The transaction aggregation rule is not defined for the SQI.

  • There is no contract with the specified contract type available in the system.

  • The contract is inactive.
C1-TXNCM 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.
C1-TXNCM 1636 Invalid batch run [%1] for [%2] division(s). %3
Note:

[%1] stands for batch code;

[%2] stands for division;

[%3] stands for expected batch code

 17000 The possible issues could be:

  • You are trying to execute the C1-TXNCM batch before executing the C1-TXNIP batch.
C1-TXNCM 1638 Transaction Feed Management cycle for individual division(s) is not yet complete. Please complete pending batch runs before starting new cycle for processing [ALL] divisions. 17000 The possible issues could be:

  • You are trying to execute this batch for all divisions before completing the transaction aggregation cycle which is initiated for a particular division.
C1-TXNCM 1639 Transaction Feed Management cycle for [ALL] divisions is not yet complete. Please complete pending batch runs before starting new cycle for individual division [%1].
Note: [%1] stands for division
 17000 The possible issues could be:

  • You are trying to execute this batch for a particular division before completing the transaction aggregation cycle which is initiated for all divisions.
C1-TXNCM 1644 Transaction Feed Management cycle for division(s) [%1] is already in progress with filter [Source= %2, Header= %3] criteria. Filter criteria must be same for complete cycle.
Note:

[%1] stands for division;

[%2] stands for transaction source;

[%3] stands for transaction header ID

 17000 The possible issues could be:

  • You are trying to execute this batch once again with the same division and different parameters.
C1-TXNCM 2003 One or more Sub Transactions are in EROR state. 17000 The possible issues could be:

  • One or more transaction legs are in the Error (EROR) status.
C1-TXNCM 2026 SQIs not configured for product %1 and division %2.
Note:

[%1] stands for final product code;

[%2] stands for derived division

 17000 The possible issues could be:

  • The SQIs are not defined for the product - division combination.
C1-TXNCM 2027 Currency Conversion from Currency [%1] to Currency [%2] not successful. 17000 The possible issues could be:

  • The exchange rate is not available during currency conversion.
C1-TXNCU 101 { Disaggregation From Date} field missing 11001 The possible issues could be:

  • No value is specified for the Disaggregate Transactions From Date parameter when the request type is set to DISAGG.
C1-TXNCU 101 { Request Type} field missing 11001 The possible issues could be:

  • No value is specified for the Request Type parameter.
C1-TXNCU 101 { Transaction Header Id } field missing 11001 The possible issues could be:

  • No value is specified for the Transaction Header ID parameter when the request type is set to CNCL.
C1-TXNCU 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-TXNCU 102 { Maximum Batch Size } field invalid 11001 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is greater than the value specified for the Chunk Size parameter.
C1-TXNCU 102 { Request Type } field invalid 11001 The possible issues could be:

  • The value other than 'EROR', 'CNCL' or 'DISAGG' is specified for the Request Type parameter.
C1-TXNCU 102 { Transaction Division } field invalid 11001 The possible issues could be:

  • The value for the Division parameter is specified when the request type is set to CNCL.
C1-TXNCU 102 { Transaction Source Code } field invalid 11001 The possible issues could be:

  • The value for the Transaction Source parameter is specified when the request type is set to CNCL.
C1-TXNCU 102 {Account Id } field invalid 11001 The possible issues could be:

  • The value for the Account ID parameter is specified when the request type is set to CNCL.
C1-TXNCU 102 {Bill Cycle Code } field invalid 11001 The possible issues could be:

  • The value for the Bill Cycle parameter is specified when the request type is set to CNCL.
C1-TXNCU 102 {Disaggregation From Date } field invalid 11001 The possible issues could be:

  • The value for the Disaggregate Transactions From Date parameter is specified when the request type is set to CNCL.
C1-TXNCU 102 {Account Id } field invalid 11001 The possible issues could be:

  • The value for the Account ID parameter is specified when the request type is set to EROR.
C1-TXNCU 102 {Bill Cycle Code } field invalid 11001 The possible issues could be:

  • The value for the Bill Cycle parameter is specified when the request type is set to EROR.
C1-TXNCU 102 {Disaggregation From Date } field invalid 11001 The possible issues could be:

  • The value for the Disaggregate Transactions From Date parameter is specified when the request type is set to EROR.
C1-TXNCU 102 {Transaction Header Id } field invalid 11001 The possible issues could be:

  • The value for the Transaction Header ID parameter is specified when the request type is set to DISAGG.
C1-TXNCU 102 { Transaction Source Code } field invalid 11001 The possible issues could be:

  • The value for the Transaction Source parameter is specified when the request type is set to DISAGG.
C1-TXNCU 106 Value { Given Transaction Header Id } too long for field { transactionHeaderId }. Maximum length: 14. Found: { Length of given Transaction Header Id} 11001 The possible issues could be:

  • The value specified for the Transaction Header ID parameter exceeds the maximum length of 14 characters.
C1-TXNCU 106 Value { Given Transaction Source Code } too long for field { transactionSource }. Maximum length: 30. Found: { Length of given Transaction Source Code} 11001 The possible issues could be:

  • The value specified for the Transaction Source parameter exceeds the maximum length of 30 characters.
C1-TXNCU 106 Value { Given Transaction Division } too long for field { division }. Maximum length: 5 Found: { Length of given Transaction Division} 11001 The possible issues could be:

  • The value specified for the Division parameter exceeds the maximum length of 5 characters.
C1-TXNCU 1388 Data configuration error for { SQI Fragment }. 17000 The possible issues could be:

  • No data exists in the SQL_​FRAG, TXN_​PRM, SQI_​CD, and SQL_​FUNC columns of the CI_​TXN_​SQI_​FRAG table.

  • The data available in the SQL_​FRAG, TXN_​PRM, SQI_​CD, and SQL_​FUNC columns of the CI_​TXN_​SQI_​FRAG table is not properly cached.
C1-TXNCU 1388 Data configuration error for { Price Item SQI }. 17000 The possible issues could be:

  • No data exists in the PRICEITEM_​CD, CIS_​DIVISION, and SQI_​CD columns of the CI_​PRICEITEM_​SQI table.

  • The data available in the PRICEITEM_​CD, CIS_​DIVISION, and SQI_​CD columns of the CI_​PRICEITEM_​SQI table is not properly cached.
C1-TXNCU 1391 Bill is completed hence cant cancel the header. 17000 The possible issues could be:

  • You are trying to cancel a transaction feed for which a bill with the Complete status already exists in the system.
C1-TXNCU 1424 There are pending bills for the feed you want to cancel. Please execute the Pending Bill Deletion (C1-DELBL) batch. 17000 The possible issues could be:

  • The Pending Bill Deletion (C1-DELBL) batch is not yet executed to delete the bills (generated for the feed) which are in the Pending status.
C1-TXNCU 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.
C1-TXNCU 1636 Invalid batch run [%1] for [%2] division(s). %3
Note:

[%1] stands for batch code;

[%2] stands for division;

[%3] stands for expected batch code

 17000 The possible issues could be:

  • You are trying to execute the C1-TXNCU batch before executing the C1-TXNIP or C1-TXNCM batch.
C1-TXNCU 1638 Transaction Feed Management cycle for individual division(s) is not yet complete. Please complete pending batch runs before starting new cycle for processing [ALL] divisions. 17000 The possible issues could be:

  • You are trying to execute this batch for all divisions before completing the transaction aggregation cycle which is initiated for a particular division.
C1-TXNCU 1639 Transaction Feed Management cycle for [ALL] divisions is not yet complete. Please complete pending batch runs before starting new cycle for individual division [%1].
Note: [%1] stands for division
 17000 The possible issues could be:

  • You are trying to execute this batch for a particular division before completing the transaction aggregation cycle which is initiated for all divisions.
C1-TXNCU 1644 Transaction Feed Management cycle for division(s) [%1] is already in progress with filter [Source= %2, Header= %3] criteria. Filter criteria must be same for complete cycle.
Note:

[%1] stands for division;

[%2] stands for transaction source;

[%3] stands for transaction header ID

 17000 The possible issues could be:

  • You are trying to execute this batch once again with the same division and different parameters.
C1-TXNRB 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-TXNRB 102 { Maximum Batch Size } field invalid 11001 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is greater than the value specified for the Chunk Size parameter.
C1-TXNRB 102 { Status Value } field invalid 11001 The possible issues could be:

  • The value other than 'ERROR' or 'IGNR' is specified for the Transaction Status parameter.
C1-TXNRB 102 { RollBack From Date } field invalid 11001 The possible issues could be:

  • The date specified in the Rollback From Date parameter is later than the date specified in the Rollback To Date parameter.
C1-TXNRB 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.
C1-DELBL 101 { Transaction Header Id } field missing 11001 The possible issues could be:

  • No value is specified for the Transaction Header ID parameter.
C1-DELBL 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-DELBL 106 Value { Given Transaction Header Id } too long for field { transactionHeaderId }. Maximum length: 14. Found: { Length of given Transaction Header Id} 11001 The possible issues could be:

  • The value specified for the Transaction Header ID parameter exceeds the maximum length of 14 characters.
C1-DELBL 1391 Bill is completed or bill segment is frozen or pending-cancelled hence can not cancel the header. 17000 The possible issues could be:

  • You are trying to cancel a transaction feed for which a bill with the Pending status is already generated in the system. This pending bill has a bill segment in either Frozen or Pending Cancel status.
C1-DELBL 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.
C1-TXCNC 101 { Transaction Header Id } field missing 11001 The possible issues could be:

  • No value is specified for the Transaction Header ID parameter.
C1-TXCNC 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-TXCNC 102 { Maximum Batch Size } field invalid 11001 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is greater than the value specified for the Chunk Size parameter.

C1-TXCNC 1391 Bill is completed or bill segment is frozen or pending-cancelled hence can not cancel the header. 17000 The possible issues could be:

  • You are trying to cancel a transaction feed for which a bill with the Pending status is already generated in the system. This pending bill has a bill segment in either Frozen or Pending Cancel status.
C1-TXCNC 1424 There are pending bills for the feed you want to cancel. Please execute the Pending Bill Deletion (C1-DELBL) batch. 17000 The possible issues could be:

  • The Pending Bill Deletion (C1-DELBL) batch is not yet executed to delete the bills (generated for the feed) which are in the Pending status.
C1-TXCNC 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.
C1-DISTG 102 {Division} field invalid 11001 The possible issues could be:

  • Division is not defined in the system.
C1-DISTG 102 { Billing Cycle Code } field invalid 11001 The possible issues could be:

  • Bill cycle is not defined in the system.
C1-IDENT 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-IDENT 1660 Disaggregate Transactions From Date would impose partial disaggregation for some billable charges 17000 The possible issues could be:

  • The identified aggregated billable charges aggregate transactions whose transaction date falls before the disaggregate transactions from date.

C1-DRSUA 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-DRSUA 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-PDTXN 102 {Chunk Size} field invalid 11001 The possible issues could be:

  • The value specified for the Chunk Size parameter is less than or equal to one.
C1-PDTXN 102 { Maximum Batch Size } field invalid 11001 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is greater than the value specified for the Chunk Size parameter.

C1-PDTXN 1556 {Maximum Batch Size} field should be greater than zero 17000 The possible issues could be:

  • The value specified for the Maximum Batch Count parameter is less than or equal to zero.