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:
|
C1-TXNHV | 102 | {Duplicate Check Required} field invalid. | 11001 | The possible issues could be:
|
C1-TXNHV | 1314 | The Transaction Source is mandatory. | 17000 | The possible issues could be:
|
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:
|
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:
|
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:
|
C1-TXNHV | 1338 | The Transaction Header ID already exists in the system. Please enter unique header ID. | 17000 | The possible issues could be:
|
C1-TXNHV | 1341 | Exception occurred during the transaction header validation. | 17000 | The possible issues could be:
|
C1-TXNHV | 1421 | Transaction records does not exist in the file. Please check. | 17000 | The possible issues could be:
|
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:
|
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:
|
C1-TXNHV | 1663 | Transaction Header External Id is missing. | 17000 | The possible issues could be:
|
C1-TXNHV | 1664 | Header Transaction Amount should be greater than 0. | 17000 | The possible issues could be:
|
C1-TXNIP | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-TXNIP | 102 | { Maximum Batch Size } field invalid | 11001 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNIP | 1303 | UDF_AMT_1 is mandatory when UDF_CURRENCY_1 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1305 | UDF_AMT_2 is mandatory when UDF_CURRENCY_2 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1307 | UDF_AMT_3 is mandatory when UDF_CURRENCY_3 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1309 | UDF_AMT_4 is mandatory when UDF_CURRENCY_4 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1311 | UDF_AMT_5 is mandatory when UDF_CURRENCY_5 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1313 | UDF_AMT_6 is mandatory when UDF_CURRENCY_6 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1315 | UDF_AMT_7 is mandatory when UDF_CURRENCY_7 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1317 | UDF_AMT_8 is mandatory when UDF_CURRENCY_8 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1319 | UDF_AMT_9 is mandatory when UDF_CURRENCY_9 is specified. Enter the amount. | 17000 | The possible issues could be:
|
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:
|
C1-TXNIP | 1321 | UDF_AMT_10 is mandatory when UDF_CURRENCY_10 is specified. Enter the amount. | 17000 | The possible issues could be:
|
C1-TXNIP | 1347 | Could not derive a price item from the rules engine. | 17000 | The possible issues could be:
|
C1-TXNIP | 1349 | Division is invalid. Please enter a valid division for the transaction. | 17000 | The possible issues could be:
|
C1-TXNIP | 1351 | Transaction Currency is invalid. Please enter a valid currency code. | 17000 | The possible issues could be:
|
C1-TXNIP | 1362 | UDF Currency 1 is invalid. Please enter a valid currency code. | 17000 | The possible issues could be:
|
C1-TXNIP | 1363 | UDF Currency 2 is invalid. Please enter a valid currency code. | 17000 | The possible issues could be:
|
C1-TXNIP | 1364 | UDF Currency 3 is invalid. Please enter a valid currency code. | 17000 | The possible issues could be:
|
C1-TXNIP | 1365 | UDF Currency 4 is invalid. Please enter a valid currency code. | 17000 | The possible issues could be:
|
C1-TXNIP | 1366 | UDF Currency 5 is invalid. Please enter a valid currency code. | 17000 | The possible issues could be:
|
C1-TXNIP | 1377 | Transaction currency is mandatory when transaction amount is non-zero. Enter a valid currency code. | 17000 | The possible issues could be:
|
C1-TXNIP | 1378 | Transaction amount is mandatory when transaction currency is specified. Enter the amount. | 17000 | The possible issues could be:
|
C1-TXNIP | 1379 | The user does not exist in the system. Please enter a valid user ID. | 17000 | The possible issues could be:
|
C1-TXNIP | 1380 | The value entered in the Credit/Debit Indicator column is incorrect. Enter either "+" or "-". | 17000 | The possible issues could be:
|
C1-TXNIP | 1381 | The value entered in the Manual Switch field is incorrect. Enter either "Y" or "N". | 17000 | The possible issues could be:
|
C1-TXNIP | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNIP | 1646 | Value for mandatory parameter is missing. | 17000 | The possible issues could be:
|
C1-TXNIP | 1647 | Mandatory parameter is missing. | 17000 | The possible issues could be:
|
C1-TXNIP | 1648 | Account Number derived by the rule is invalid. | 17000 | The possible issues could be:
|
C1-TXNIP | 1649 | Account Number type code derived by the rule is invalid. | 17000 | The possible issues could be:
|
C1-TXNIP | 1650 | Division derived by the rule is invalid. | 17000 | The possible issues could be:
|
C1-TXNIP | 1651 | Not able to derive account ID. | 17000 | The possible issues could be:
|
C1-TXNIP | 1652 | Product derived by the rule is invalid. | 17000 | The possible issues could be:
|
C1-TXNIP | 1653 | Length of the derived product is greater than 10. | 17000 | The possible issues could be:
|
C1-TXNIP | 1654 | Length of the derived variance parameter is greater than 8. | 17000 | The possible issues could be:
|
C1-TXNIP | 1656 | Length of the product parameter value derived by the rule is greater than 254. | 17000 | The possible issues could be:
|
C1-TXNIP | 1657 | Length of the product parameter code derived by the rule is greater than 30. | 17000 | The possible issues could be:
|
C1-TXNIP | 2002 | Transaction is in EROR due to one or more reasons. | 17000 | The possible issues could be:
|
C1-TXNIP | 2007 | %1 cannot be blank. Note: [%1] stands for division
|
17000 | The possible issues could be:
|
C1-TXNIP | 2007 | %1 cannot be blank. Note: [%1] stands for user ID
|
17000 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNVP | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNEX | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-TXNEX | 102 | { Maximum Batch Size } field invalid | 11001 | The possible issues could be:
|
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:
|
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:
|
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:
|
C1-TXNEX | 790 | The selected Member account does not have active Contracts. | 17000 | The possible issues could be:
|
C1-TXNEX | 1336 | Effective pricing is not available for the product. Please check. | 17000 | The possible issues could be:
|
C1-TXNEX | 1392 | Invalid configuration of Price Search Algorithm Parameters or Contracts or Schedule Periods. | 17000 | The possible issues could be:
|
C1-TXNEX | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|
C1-TXNEX | 1588 | No Schedule Period found for the transaction date. | 17000 | The possible issues could be:
|
C1-TXNEX | 1611 | Division specific Price Search Algorithm is not configured. | 17000 | The possible issues could be:
|
C1-TXNEX | 1612 | Price Search Algorithm parameters are not set or are invalid. | 17000 | The possible issues could be:
|
C1-TXNEX | 1613 | Multiple contracts in Active, Pending Stop, Stop status exists for same contract type. | 17000 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNIP | 2003 | One or more Sub Transactions are in EROR state. | 17000 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNSQ | 102 | { Maximum Batch Size } field invalid | 11001 | The possible issues could be:
|
C1-TXNSQ | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
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:
|
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:
|
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:
|
C1-TXNSQ | 1388 | Data configuration error for { ENV_ID }. | 17000 | The possible issues could be:
|
C1-TXNSQ | 1388 | Data configuration error for { SQI Fragment }. | 17000 | The possible issues could be:
|
C1-TXNSQ | 1388 | Data configuration error for { Price Item SQI }. | 17000 | The possible issues could be:
|
C1-TXNSQ | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNSQ | 2003 | One or more Sub Transactions are in EROR state. | 17000 | The possible issues could be:
|
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:
|
C1-TXNSQ | 2027 | Currency Conversion from Currency [%1] to Currency [%2] not successful. | 17000 | The possible issues could be:
|
C1-TXNCM | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-TXNCM | 102 | { Maximum Batch Size } field invalid | 11001 | The possible issues could be:
|
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:
|
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:
|
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:
|
C1-TXNCM | 1393 | Either the transaction feed management setup is incomplete, or there is no active contract available. | 17000 | The possible issues could be:
|
C1-TXNCM | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNCM | 2003 | One or more Sub Transactions are in EROR state. | 17000 | The possible issues could be:
|
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:
|
C1-TXNCM | 2027 | Currency Conversion from Currency [%1] to Currency [%2] not successful. | 17000 | The possible issues could be:
|
C1-TXNCU | 101 | { Disaggregation From Date} field missing | 11001 | The possible issues could be:
|
C1-TXNCU | 101 | { Request Type} field missing | 11001 | The possible issues could be:
|
C1-TXNCU | 101 | { Transaction Header Id } field missing | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | { Maximum Batch Size } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | { Request Type } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | { Transaction Division } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | { Transaction Source Code } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | {Account Id } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | {Bill Cycle Code } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | {Disaggregation From Date } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | {Account Id } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | {Bill Cycle Code } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | {Disaggregation From Date } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | {Transaction Header Id } field invalid | 11001 | The possible issues could be:
|
C1-TXNCU | 102 | { Transaction Source Code } field invalid | 11001 | The possible issues could be:
|
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:
|
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:
|
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:
|
C1-TXNCU | 1388 | Data configuration error for { SQI Fragment }. | 17000 | The possible issues could be:
|
C1-TXNCU | 1388 | Data configuration error for { Price Item SQI }. | 17000 | The possible issues could be:
|
C1-TXNCU | 1391 | Bill is completed hence cant cancel the header. | 17000 | The possible issues could be:
|
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:
|
C1-TXNCU | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|
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:
|
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:
|
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:
|
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:
|
C1-TXNRB | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-TXNRB | 102 | { Maximum Batch Size } field invalid | 11001 | The possible issues could be:
|
C1-TXNRB | 102 | { Status Value } field invalid | 11001 | The possible issues could be:
|
C1-TXNRB | 102 | { RollBack From Date } field invalid | 11001 | The possible issues could be:
|
C1-TXNRB | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|
C1-DELBL | 101 | { Transaction Header Id } field missing | 11001 | The possible issues could be:
|
C1-DELBL | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
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:
|
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:
|
C1-DELBL | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|
C1-TXCNC | 101 | { Transaction Header Id } field missing | 11001 | The possible issues could be:
|
C1-TXCNC | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-TXCNC | 102 | { Maximum Batch Size } field invalid | 11001 | The possible issues could be:
|
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:
|
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:
|
C1-TXCNC | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|
C1-DISTG | 102 | {Division} field invalid | 11001 | The possible issues could be:
|
C1-DISTG | 102 | { Billing Cycle Code } field invalid | 11001 | The possible issues could be:
|
C1-IDENT | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-IDENT | 1660 | Disaggregate Transactions From Date would impose partial disaggregation for some billable charges | 17000 | The possible issues could be:
|
C1-DRSUA | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-DRSUA | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-PDTXN | 102 | {Chunk Size} field invalid | 11001 | The possible issues could be:
|
C1-PDTXN | 102 | { Maximum Batch Size } field invalid | 11001 | The possible issues could be:
|
C1-PDTXN | 1556 | {Maximum Batch Size} field should be greater than zero | 17000 | The possible issues could be:
|