Error Messages

370000 The <$> character is not recognized.

 

Type Error
Description

 

Action

 


370001 The "-" operator is not authorized after another operator.

 

Type Error
Description

 

Action

 


370002 The <____> symbol must not contain only underscore characters.

 

Type Error
Description

 

Action

 


370003 The Custom function name must not contain only underscore characters <$_>.

 

Type Error
Description

 

Action

 

 
370004The Custom function name must not contain only digit characters <$1>.

 

TypeError
Description

 

Action

 

 
370005The Variable name must not contain only underscore characters <@_>.

 

TypeError
Description

 

Action

 

 
370006The Variable name must not contain only digit characters <@1>.

 

TypeError
Description

 

Action

 

 
370008The Decimal constant <.> must not contain only dot characters.

 

TypeError
Description

 

Action

 

 
370009The Decimal constant <12.> must contain at least one digit after the decimal separator.

 

TypeError
Description

 

Action

 

 
370010The Decimal constant <.12> must contain at least one digit before the decimal separator.

 

TypeError
Description

 

Action

 

 
370020The expression is incomplete.

 

TypeError
Description

 

Action

 

 
370021The syntax after this <NUMERIC> symbol is incorrect.

 

TypeError
Description

 

Action

 

 
370040The <123456> Date constant is not a calendar date.

 

TypeError
Description

 

Action

 

 
370041The format of the <1> Date constant must be YYYYMMDD, CYYMMDD or YYMMDD.

 

TypeError
Description

 

Action

 

 
370042The year in the <19001213> Date constant must be between 1901 and 2099.

 

TypeError
Description

 

Action

 

 
370043The Integer constant contains <29> digits but must not exceed 28 digits.

 

TypeError
Description

 

Action

 

 
370044The String constant must contain at least one character.

 

TypeError
Description

 

Action

 

 
370045The String constant contains <257> characters but must not exceed 256 characters.

 

TypeError
Description

 

Action

 

 
370046The linefeed character is not authorized in a String constant.

 

TypeError
Description

 

Action

 

 
370047The fractional part of the Decimal constant contains <10> digits but must not exceed 9 digits.

 

TypeError
Description

 

Action

 

 
370048The Decimal constant contains <29> digits but must not exceed 28 digits.

 

TypeError
Description

 

Action

 

 
370060The Business-Document field of the Output-Event is considered to be of Date type.

 

TypeWarning
Description

 

Action

 

 
370061The expression of <Alphanumeric> type is not authorized in a Business-Document field of <Date> type.

 

TypeError
Description

 

Action

 

 
370062The (offset + length) <10> in the PPPPLLLT parameter <"0001009A"> must not exceed the length <8> of the Business-Document field <CHPA8>.

 

TypeError
Description

 

Action

 

 
370063The offset <9> in the PPPPLLLT parameter <"0009007A"> must not exceed the length <8> of the Business-Document field <CHPA8>.

 

TypeError
Description

 

Action

 

 
370064The <Alphanumeric> type of the Business-Document field <CHPA8> is not compatible with the type <N> in the PPPPLLLT parameter <"0001007N">.

 

TypeError
Description

 

Action

 

 
370065The <Alphanumeric> type of the left operand is neither numeric nor decimal.

 

TypeError
Description

 

Action

 

 
370066The <Alphanumeric> type of the right operand is neither numeric nor decimal.

 

TypeError
Description

 

Action

 

 
370067The <Signed numeric> type of the Business-Document field <CHPS8> is not authorized with the extraction operator.

 

TypeError
Description

 

Action

 

 
370068The expression of <Packed numeric> type is not recommended in a Business-Document field of <Alphanumeric> type.

 

TypeWarning
Description

 

Action

 

 
370070The length <3> of the <Alphanumeric> left operand must be equal to the length <2> of the <Unsigned numeric> right operand.

 

TypeError
Description

 

Action

 

 
370071The expression THEN of <Alphanumeric> type is not authorized in a Business-Document field of <Unsigned decimal> type.

 

TypeError
Description

 

Action

 

 
370072The expression THEN of <Packed numeric> type is not recommended in a Business-Document field of <Alphanumeric> type.

 

TypeWarning
Description

 

Action

 

 
370073The <Unsigned decimal> type of the left operand is not authorized in a concatenation expression.

 

TypeError
Description

 

Action

 

 
370074The <Unsigned decimal> type of the right operand is not authorized in a concatenation expression.

 

TypeError
Description

 

Action

 

 
370160The divisor <0> is not authorized.

 

TypeError
Description

 

Action

 

 
370161Only one condition or Mapping-Rule expression is authorized.

 

TypeError
Description

 

Action

 

 
370162The expression is not a condition (boolean expression).

 

TypeError
Description

 

Action

 

 
370163The expression of <Packed numeric> type and length 10 (external length 6) is not authorized in a Business-Document field of <Alphanumeric> type and length 5 (external length 5).

 

TypeError
Description

 

Action

 

 
370164The <ERR> Function must be used after a THEN or ELSE key word.

 

TypeError
Description

 

Action

 

 
370165The Pre-calculation <PCCN1> is not authorized in a Pre-calculation expression.

 

TypeError
Description

 

Action

 

 
370166The Business-Field or the Pre-calculation <PCCX> is not available or does not exist in the repository.

 

TypeError
Description

 

Action

 

 
370168The Table <MYTABLE> is not available or does not exist in the repository.

 

TypeError
Description

 

Action

 

 
370169The Variable <TOTO> is not available or does not exist in the repository.

 

TypeError
Description

 

Action

 

 
370170The expression of <Date> type and length 8 (external length 8) may be truncated in a Business-Document field of <Alphanumeric> type and length 4 (external length 4).

 

TypeWarning
Description

 

Action

 

 
370172The expanded scenario condition <522 characters> must not exceed 500 characters.

 

TypeError
Description

 

Action

 


370173The Custom Function definition <1233 characters> must not exceed 1200 characters.

 

TypeError
Description

 

Action

 

 
370174The variable <TOTO> cannot be used in the initialization of a Variable.

 

TypeError
Description

 

Action

 

 
370175The “//” operator will be deprecated in the next version. Replace it with the “/” operator.

 

TypeWarning
Description

 

Action

 

 
370176The expression of <Packed decimal> type and length 10 (external length 6) may be truncated or rounded in a Business-Document field of <Unsigned numeric> type and length 6 (external length 6).

 

TypeWarning
Description

 

Action

 

 
370300The parameter 1 in the Function <ENV> must be a String constant.

 

TypeError
Description

 

Action

 

 
370301The entry point parameter <"999"> in the Function <CHECK> must contain 2 characters.

 

TypeError
Description

 

Action

 

 
370302The length <00A> in the PPPPLLLT parameter <"000100AA"> is not numeric.

 

TypeError
Description

 

Action

 

 
370303The type <Z> in the PPPPLLLT parameter <"0001007Z"> is not a valid type.

 

TypeError
Description

 

Action

 

 
370304The signed Integer constant <-1> is not authorized in the parameter 2 of the <DATEPLUS> Function.

 

TypeError
Description

 

Action

 

 
370305The Function <JULIAN> is not authorized in the parameter 2 of the <DATEPLUS> Function.

 

TypeError
Description

 

Action

 

 
370306The parameter 1 <MYPARAM> in the Function <ENV> does not correspond to a valid environment code.

 

TypeError
Description

 

Action

 

 
370307The message in Function <ERR> may be truncated to 50 characters.

 

TypeWarning
Description

 

Action

 

 
370308The (offset + length - 1) <6> must not exceed the value length <5> of the Table <T_A6A5>.

 

TypeError
Description

 

Action

 

 
370309The offset <6> must not exceed the value length <5> of the Table <T_A6A5>.

 

TypeError
Description

 

Action

 

 
370310The entry point parameter <"00"> in the Function <CHECK> must be included between "01" and "78".

 

TypeError
Description

 

Action

 

 
370311The entry point parameter in the Function <CHECK> must be a two-character String constant.

 

TypeError
Description

 

Action

 

 
370312The parameter 1 in the Function <NULL> is redundant.

 

TypeError
Description

 

Action

 

 
370313The Function <DAY> must have at least 1 parameter.

 

TypeError
Description

 

Action

 

 
370314The PPPPLLLT parameter <"0001008AA"> must contain 8 characters.

 

TypeError
Description

 

Action

 

 
370315The length <0> in the PPPPLLLT parameter <"0001000A"> must be included between <1> and <256>.

 

TypeError
Description

 

Action

 

 
370316The offset <000A> in the PPPPLLLT parameter <"000A008A"> is not numeric.

 

TypeError
Description

 

Action

 

 
370317The offset <0000> in the PPPPLLLT parameter <"0000008A"> must not be equal to zero.

 

TypeError
Description

 

Action

 

 
370318The type <D> is not authorized in the PPPPLLLT parameter <"0001007D">.

 

TypeError
Description

 

Action

 

 
370319The <Alphanumeric> type of the parameter 1 is not authorized in the Function <JULIAN>.

 

TypeError
Description

 

Action

 

 
370320The length <7> of parameter 2 is incorrect when accessing Table <T_A6A5> defined with key length <6>.

 

TypeError
Description

 

Action

 

 
370321The <Signed numeric> type of parameter 2 is not authorized when accessing Table <T_A6A5> defined with <Alphanumeric> key type.

 

TypeError
Description

 

Action

 

 
370322The <Unsigned numeric> type of date parameter is not authorized when accessing Table <T_A5A5>.

 

TypeError
Description

 

Action

 

 
370323The parameter 1 in the Function <YEAR4> must be a Business-Document field or a Pre-calculation with length 8.

 

TypeError
Description

 

Action

 

 
370324The parameter 1 in the Function <DAY> must be a Business-Document field or a Pre-calculation with length 6, 7 or 8.

 

TypeError
Description

 

Action

 

 
370325The <Unsigned numeric> type of the parameter 1 is not recommended in the Function <DATEPLUS>.

 

TypeWarning
Description

 

Action

 

 
370326The <Alphanumeric> type of parameter 2 is not recommended when accessing Table <T_D6A5> defined with <Date> key type.

 

TypeWarning
Description

 

Action

 

 
370327The <Unsigned numeric> type of date parameter is not recommended when accessing Table <T_A5A5>.

 

TypeWarning
Description

 

Action

 

 
370328The length <28> of parameter 2 is not recommended when accessing Table <T_A6A5> defined with key length <6>.

 

TypeWarning
Description

 

Action

 

 
370329The length <265> of the parameter 2 in the Function <CHECK> must not be exceed 256.

 

TypeWarning
Description

 

Action

 

 
370330The Function <DATEMINUS> is not authorized in the parameter 1 of the Function <DATEPLUS>.

 

TypeError
Description

 

Action

 

 
370331The length <10> of the parameter 1 in the Function <DAY> must be equal to 6, 7 or 8.

 

TypeError
Description

 

Action

 

 
370332The Function <INT> is not available yet.

 

TypeError
Description

 

Action

 

 
370350You are not allowed to use custom Function <CUSTOM2> in the parameters of another custom function call.

 

TypeError
Description

 

Action

 

 
370352The Custom function <CUSTOM1> must be called with 2 parameter(s).

 

TypeError
Description

 

Action

 

 
370353The definition of a Custom function must not refer to another Custom function <CUSTOM1>.

 

TypeError
Description

 

Action

 

 
370354The Custom function <CUSTOM> is not available or does not exist in the repository.

 

TypeError
Description

 

Action

 

 
370357Error while expanding the Custom function <CUSTOM18>.

 

TypeError
Description

 

Action

 

 
370359The parameter <ARG> does not exist in the Custom function.

 

TypeError
Description

 

Action

 

 
600000Incorrect name: The character '{1}' is forbidden

 

TypeError
DescriptionAt least one character in the character string checked is incorrect:
The only authorized characters are:
'A', 'B', 'C', 'D', &, 'Z', '_', '0', '1', '2', &, '9' for Input-Event, Processing-Context-Out, Processing-Context-In, Rule, Mapping-Template, Business-Document, Business-Field, Financial-Tag, Table and Variable objects.
UNICODE characters, except '\t', '\f', '\r', '~', '#', '{', '[', '|', '`', '\', '\^', ']', '}', '¤', ''' for Financial-Procedure and Financial-Event objects.
Parameter(s) {1} Invalid character
ActionReplace the unauthorized character in the character string with a valid character.
 
600001The name definition must be less than or equal to {1} characters

 

TypeError
DescriptionThe definition of the character string checked must be less than or equal to the definition {1}.
Parameter(s) {1} Maximum authorized definition value
ActionModify the length of the character string to respect the limit {1}.
 
600002The object name must include at least one alphabetical character

 

TypeError
DescriptionThe character string checked must contain at least one alphabetical character ('A', 'B', 'C', &, 'Z', '_')
ActionModify the character string by adding an alphabetical character.
 
600003Maximum number of Output-Event type Financial-Tags reached!

 

TypeError
DescriptionYou cannot create more than 35 Output-Event type Financial-Tags in the entire AccountingIntegrator Enabler reference set, that is, in all the root folders.
ActionAnalyze the existing configuration to rationalize the use of the Financial-Tags and consequently delete those no longer of use.
 
600004This name is a reserved word

 

TypeError
DescriptionThe character string checked corresponds to one of the following reserved words in the AccountingIntegrator Enabler Data Manipulation Language (DML):
'ACCTABD', 'ACCTAB', 'YEAR', 'YEAR4', 'DATEMINUS', 'DATEPLUS', 'CHECKTABD', 'CHECKTAB', 'CHECK', 'SYSDATE', 'ERR', 'ENV', 'NUMSEG', 'NUMSC', 'NUMSEGSC', 'NUMSCSEG', 'SEGSTRUC', 'EVTCODE', 'SEGCODE', 'DOMAIN', 'STARTDATE', 'ENDDATE', 'SENDER', 'INSTANCE', 'GROUP', 'PHASE', 'RULE', 'FIRSTGROUP' ,'LASTGROUP', 'FIRSTPHASE', 'LASTPHASE', 'EXTTABD', 'EXTTAB', 'DAY', 'MONTH', 'NBDAYS', 'NULL', 'JULIAN', 'SEARCH', 'AND', 'OR', 'IF', 'THEN', 'ELSE', 'LOW_VALUE', 'HIGH_VALUE', 'NUMERIC', 'COND_EVT', 'COND_SEG'.
ActionEnter a new character string avoiding the list of AccountingIntegrator Enabler DML reserved words.
 
600005The name of the '{1}' object is already used by another object {2}

 

TypeError
DescriptionA(n) {2} object with the same name already exists in the current namespace, that is, in the root and child folders.
Parameter(s) {1} Object name
{2} Object type
ActionModify the name of the {1} object to remove the naming conflict with the {2} object.
 
600006The object name must include at least one alphabetical character

 

TypeError
DescriptionThe character string checked must contain at least one alphabetical character ('A', 'B', 'C', &, 'Z', '_').
ActionAdd an alphabetical character to the character string.
 
600007<{0}>: The number of decimal digits must be less than the total length of the field

 

TypeError
Description For Variables of decimal type, the decimal definition is mandatory and its value must be smaller than the total definition
Parameter(s) {0} The logical name of the Variable
ActionModify the decimal definition to comply with the restriction

 

600008<{0}>: The initialization value of the Variable is not a valid decimal value. The value should respect the format: x.y

 

TypeError
DescriptionThe specified initialization value of the Variable must respect the following pattern: The only characters authorized for the Decimal data type are the 0 to 9 digits and the decimal separator ".". The decimal separator must not be the first nor the last character of the value.
Parameter(s) {0} The logical name of the Variable
ActionModify the initialization value in order to respect the format

 

600009One or more versions of the current object already exist in the folder(s): {1}. All the versions of a versioned object must be grouped in the same folder

 

TypeError
DescriptionAn object version exists relative to another version: version n+1 corresponds to an enhancement of version n. To simplify data manipulation, all versions of an object must be grouped and handled in the same folder.
Parameter(s) {1} List of folders in which at least one version of the current object has been identified.
ActionCreate this new version of the object in the same folder as the previous version, or modify the name of the current object.
 
600010A Segment Type must use a Business-Document

 

TypeError
DescriptionThe Business-Document Segment Type is not specified.
ActionSelect a Business-Document object in the Segment Type properties.
 
600011At least one Phase is mandatory

 

TypeError
DescriptionAs an Input-Event must define some operation performed in the Processing section, and a Phase must be associated with all the operations in the Processing section, the Input-Event must possess at least one Phase.
ActionCreate a Phase in the current Input-Event object.
 
600012At least one Segment Type is mandatory

 

TypeError
DescriptionThe structure of an Input-Event must possess at least one Segment Type.
ActionCreate a Segment Type in the current Input-Event object.
 
600013Maximum number of Phases reached

 

TypeError
DescriptionYou cannot specify more than 50 Phases in an Input-Event object.
ActionModify the Input-Event Phases to comply with this restriction.
 
600014Maximum number of Segment Types reached

 

TypeError
DescriptionYou cannot specify more than 100 Segment Types in an Input-Event object.
ActionModify the Segment Types in the Input-Event to comply with this restriction.
 
600015Maximum number of Rules reached

 

TypeError
DescriptionYou cannot link more than 500 Rule versions in an Input-Event object.
ActionModify the Rules to apply to the Input-Event to comply with this restriction.
 
600016Maximum number of Input-Event validity periods reached

 

TypeError
DescriptionIn an Input-Event object you cannot specify more than 500 validity periods.
ActionModify the Input-Event validity periods to comply with this restriction.
 
600019The Audit-Rule is forbidden because no Aggregation-Rule is specified

 

TypeError
DescriptionIn the Pre-processing section of the Input-Event, you only need to specify an Audit operation if you have set an Input-Event aggregation operation.
ActionIn these circumstances, it is recommended that you set either of the following:
An input Audit operation in the Processing section of the Input-Event
An Input-Event aggregation operation in the Pre-processing section
 
600020In Pre-Processing, you cannot associate any Rule with a Segment Type, if you have not defined any processing on that Segment Type

 

TypeError
DescriptionThere is no operational logic in setting Pre-processing operations in the Input-Event, if you have not defined any operations in the Processing section of the Input-Event.
ActionIt is recommended that you complete the Processing section associated with this Input-Event.
 
600021The Phase name must be unique for the current Input-Event

 

TypeError
DescriptionAll the Phases specified in an Input-Event must be identified by a unique name.
ActionModify the Phase names specified in the Input-Event to comply with this restriction.
 
600022At least one Rule must be specified in the Phase processing

 

TypeError
DescriptionAs an Input-Event Phase cannot exist if there are no operations to perform in that Phase, you must specify at least one operation in each Phase.
ActionSpecify at least one operation by selecting a Rule in the Phase concerned.
 
600023The Post Audit-Rule is forbidden because no Enrichment-Rule is specified

 

TypeError
DescriptionIn the Processing section associated with an Input-Event Phase, you only need to define an Audit operation after an Enrichment operation if you have set an Input-Event Enrichment operation.
ActionIn these circumstances, it is recommended that you either set an Input-Event Enrichment operation or remove the Audit operation that follows the Enrichment operation.
 
600024Phase {1} and Phase {2} use the same Transformation-Domain {3}

 

TypeInformation
DescriptionAn Input-Event Phase enables you to separate processing during an execution engine session, and to re-run a particular Phase if an exception occurs during the execution of that Phase. To be able to select the Input-Event Phase (s) to process, the AccountingIntegrator Enabler execution engine needs to know the list of active Transformation-Domains and thus identify the Phases attached to these Domains. Therefore, if you attach two Phases from the same Input-Event to the same Transformation-Domain, this defeats the purpose of a Phase, as the system cannot run the Phases separately.
Parameter(s) {1} Name of Phase 1
{2} Name of Phase 2
{3} Name of the Transformation-Domain used
ActionThis is an information message. You should reassess whether you need to separate the Processing operations into two Phases.
 
600025You must enter at least one validity period

 

TypeError
DescriptionAn Input-Event object must possess at least one validity period.
ActionCreate a validity period in the current Input-Event object.
 
600026The Input-Event validity periods must be separate and distinct

 

TypeError
DescriptionAll the Input-Event validity periods must be separate and distinct.
ActionModify those Input-Event validity periods that overlap.
 
600027You must modify at least one data element in the Enrichment-Rule

 

TypeError
DescriptionAn Enrichment-Rule serves to modify at least one Input-Event Segment, otherwise there is no logic to this Rule.
ActionEnter at least one mapping expression to modify an Input-Event Segment.
 
600028In an Output-Event template the variables used in the mappings are calculated only once at the beginning of the Rule processing operation.

 

TypeInformation
DescriptionThe AccountingIntegrator Enabler execution engine processes an Output-Event template in a similar way to a Pre-calculation. As with the Pre-calculation, the system:
Processes the Output-Event template at the beginning of the Rule processing operation, that is, before processing the Financial-Cases and the other Output-Events
Then stores the mappings results in memory throughout the execution of the Rule.
Thus, a Variable in an Output-Event template mapping is calculated only once even if the mapping is reused in several Output-Events. When processing the Output-Event, the system retrieves the previously stored result for the inherited mapping instead of re-running the mapping.
ActionThis is an information message. You should review your use of Variables in the Output-Event template mapping expressions.
 
600029You must modify at least one inherited expression in the Output-Event to be able to use an Output-Event template

 

TypeError
DescriptionIn circumstances where an Output-Event inherits from an Output-Event template but does not overwrite any of the inherited mapping expressions, that is, the current Output-Event and the Output-Event template are therefore identical, the configuration is incoherent. This type of configuration is not authorized.
ActionEnter or overwrite a mapping expression in the Output-Event.
 
600030Maximum number of Variables reached: {1}

 

TypeError
DescriptionYou cannot use more than 100 Variables in a Transformation-Rule or Enrichment-Rule.
Parameter(s) {1} Maximum number of Variables authorized
ActionModify the mapping expressions in the Transformation-Rule or Enrichment-Rule, to comply with this restriction.
 
600031Maximum number of Financial-Cases reached: {1}

 

TypeError
DescriptionIn a Transformation-Rule, you cannot define more than 10 Financial-Cases to run.
Parameter(s) {1} Maximum number of Financial-Cases authorized
ActionModify the Transformation-Rule to comply with this restriction.
 
600032Maximum number of Output-Events reached: {1}

 

TypeError
DescriptionIn a Transformation-Rule, you cannot define more than 90 Output-Events to run.
Parameter(s) {1} Maximum number of Output-Events authorized
ActionModify the Transformation-Rule to comply with this restriction.
 
600033Maximum number of Output-Event templates reached: {1}

 

TypeError
DescriptionIn a Transformation-Rule, you cannot define more than 10 Output-Event templates.
Parameter(s) {1} Maximum number of Output-Event templates authorized
ActionModify the Transformation-Rule to comply with this restriction.
 
600034The expression for the {3} is too long: {4} characters maximum authorized

 

TypeError
DescriptionThis is a generic message.
The mapping expression definition checked is too long: the character string must not exceed {4} characters.
Parameter(s) {3} Type of expression: Financial-Case condition, Output-Event condition, Output-Event mapping and so on
{4} Maximum number of characters authorized
ActionModify the mapping expression to comply with this restriction.
 
600035Maximum number of linked language objects reached: {1}

 

TypeError
DescriptionIn a Transformation-Rule or Enrichment-Rule, you cannot use more than 500 language objects: Variables and Tables.
Parameter(s) {1} Maximum number of language objects authorized
ActionModify the mapping expressions in the Transformation-Rule or Enrichment-Rule to comply with this restriction.
 
600036There are too many Pre-calculations in the Transformation-Rule: adding the Pre-calculations will exceed the Business-Document limits

 

TypeError
DescriptionThe execution engine incorporates the definition of a Pre-calculation in a Transformation-Rule as an additional leaf element in the Input-Event Segment Business-Document. However, the conventions applicable to Business-Documents are also valid when Pre-calculations are included: The total Business-Document definition must not exceed 4000 characters, and the number of Business-Document leaf elements must not exceed 1500.
ActionModify the Pre-calculations in the current Transformation-Rule to respect these restrictions.
 
600037A Transformation-Rule must contain at least one Financial-Case

 

TypeError
DescriptionYou must specify at least one Financial-Case in a Transformation-Rule.
ActionCreate a Financial-Case in the current Transformation-Rule.
 
600038A Transformation-Rule must contain at least one Output-Event

 

TypeError
DescriptionYou must specify at least one Output-Event in a Transformation-Rule
ActionCreate an Output-Event in the current Transformation-Rule.
 
600039The number of Output-Event {1} must be between {2} and {3}

 

TypeError
DescriptionThe number that enables the system to identify an Output-Event must be between 1 and 90 (inclusive).
Parameter(s) {1} Number of the current Output-Event
{2} Minimum number authorized
{3} Maximum number authorized
ActionModify the number of Output-Event {1} to comply with this restriction.
 
600040The number of Financial-Case {1} must be between {2} and {3}

 

TypeError
DescriptionThe number that enables the system to identify a Financial-Case must be between 1 and 10 (inclusive).
Parameter(s) {1} Number of the current Financial-Case
{2} Minimum number authorized
{3} Maximum number authorized
ActionModify the number of Financial-Case {1} to comply with this restriction.
 
600041The Pre-calculation name '{1}' is already in use by a Business-Document leaf element {2}

 

TypeError
DescriptionThe execution engine incorporates the definition of a Pre-calculation in a Transformation-Rule as an additional leaf element in the Input-Event Segment Business-Document. However, the conventions applicable to Business-Documents are also valid when Pre-calculations are included: The name of each Business-Document leaf element must be unique within the Business-Document and limited to 10 characters.
Parameter(s) {1} Name of the Pre-calculation causing the naming conflict
{2} Name of the Input-Event Segment Business-Document
ActionModify the Pre-calculations in the current Transformation-Rule to respect these restrictions.
 
600042The Pre-calculation '{2}' cannot be used in this type of expression

 

TypeError
DescriptionA Pre-calculation cannot use the value of another Pre-calculation in the mapping expression intended to update it.
Parameter(s) {2} Name of the Pre-calculation specified in the mapping expression
ActionModify the Pre-calculation mapping expression to comply with this restriction.
 
600043The Business-Document is mandatory

 

TypeError
DescriptionA Business-Document must be specified in the current Output-Event.
ActionSpecify a Business-Document in the current Output-Event.
 
600044An Output-Event template must be selected either in all the Financial-Cases, which reference at least one Output-Event that uses the Output-Event template, [{2}] or in none at all.

 

TypeError
DescriptionYou can select whether or not to associate an Output-Event template with an entry in the list of Output-Events generated after running a Rule. If you:
Do not select a given Output-Event template in any Financial-Case, there will be no list entry associated with this Output-Event template.
Select a given Output-Event template in at least all the Financial-Cases in which you selected an Output-Event that uses this template, the system generates a list entry for each of the Financial-Cases concerned.
Parameter(s) {2} List of Financial-Cases in which at least one Output-Event uses the current Output-Event template.
ActionModify the Transformation-Rule to comply with this restriction.
 
600045A Financial-Case must contain at least one Output-Event

 

TypeError
DescriptionEach Financial-Case in a Transformation-Rule must be defined with at least one Output-Event.
ActionSelect at least one Output-Event in each Financial-Case of the current Transformation-Rule.
 
600046The definition of the Pre-calculation must be between {2} and {3} characters

 

TypeError
DescriptionThe definition of the Pre-calculation of the current Transformation-Rule must be between {2} and {3} characters for the selected data type.
Parameter(s) {2} Minimum authorized definition
{3} Maximum authorized definition
ActionModify the Pre-calculation of the Transformation-Rule to comply with this restriction.
 
600047The Output-Event {1} cannot be a template if it is not used by another Output-Event

 

TypeError
DescriptionThe configuration of the Transformation-Rule is incoherent: an Output-Event template is not used by any other Output-Event.
Parameter(s) {1} Number of the Output-Event template
ActionUnselect the template option in the Output-Event {1}.
 
600048The status of the Output-Event template <{2}> must be <Checked>

 

TypeError
DescriptionTo be able to check an Output-Event, the Output-Event template from which it inherits must also have the status Checked.
Parameter(s) {2} Number of the Output-Event template
ActionCheck the Output-Event template {2}.
 
600049The number of the Output-Event must be greater than that of the Output-Event template <{2}> used

 

TypeError
DescriptionAn Output-Event can only use an Output-Event template if the number of the Output-Event is greater than that of the Output-Event template.
Parameter(s) {2} Number of the Output-Event template
ActionRenumber the Output-Event to comply with this restriction.
 
600050The definition of '{1}' columns is too big ({2}). The maximum authorized definition is {3}.

 

TypeError
DescriptionThe AccountingIntegrator Enabler execution engine does not process tables whose:
Arguments are greater than 128 characters
Sum of associated values is greater than 256 characters.
Parameter(s) {1} Type of column: Argument or Value
{2} Total definition of {1} columns
{3} Maximum authorized definition for {1} columns
ActionModify the structure of the Table to comply with this restriction.
 
600051Argument '{1}' in line n°{2} is already used by another Table entry

 

TypeError
DescriptionTwo Table entries cannot have the same argument value, except if one is a version of the other.
Parameter(s) {1} Duplicated Table entry argument
{2} Line number of incorrect Table entry
ActionModify the Table entry {2} to comply with this restriction.
 
600052Incorrect label '{2}'

 

TypeError
DescriptionThe character string entered for the Table entry label is incorrect for one or more of the following reasons:
The only authorized characters are UNICODE characters, except '\t', '\f', '\r', '~', '#', '{', '[', '|', '`', '\', '\^', ']', '}', '¤', '''
The definition of the character string is greater than the maximum authorized definition: 128 characters.
Parameter(s) {2} Character string entered for the Table entry label
ActionModify the Table entry label to respect these restrictions.
 
600053Argument in line n°{1} cannot be empty

 

TypeError
DescriptionYou must always specify the Table entry argument: An empty character string is forbidden.
Parameter(s) {1} Line number of incorrect Table entry
ActionModify the Table entry to comply with this restriction.
 
600054You cannot set a default value in the Table, if you also set the AccountingIntegrator Enabler execution engine to check the existence of Table entries

 

TypeError
DescriptionThe configuration of the current Table object is incoherent: you have set a default value and also specified that AccountingIntegrator Enabler must reject access if a given entry does not exist in the Table.
ActionModify the configuration of the current Table object.
 
600055The cell value '{3}' is incorrect

 

TypeError
DescriptionThe specified cell value is incorrect for one or more of the following reasons:
The only characters authorized for the Alphanumeric data type are UNICODE characters, except '\t',' \f', '\r', '~', '#', '{', '[', '|', '`', '\', '\^', ']', '}', '¤', '''
The definition of the value entered is greater than the maximum authorized definition for the active column.
If the column is a date type, the date format entered is incompatible with the column format.
Parameter(s) {3} Incorrect cell value
ActionModify the cell value to respect these restrictions.
 
600056The end validity date for the Table entry is incorrect: the date {2} must be between {3} and {4}

 

TypeError
DescriptionThe end validity date of the current Table entry is incorrect: the end validity date must be more than or equal to the start validity date.
Parameter(s) {2} Incorrect end validity date
{3} Minimum authorized date
{4} Maximum authorized date
ActionModify the end validity date for the current Table entry to comply with this restriction.
 
600057The data type is mandatory

 

TypeError
DescriptionYou must specify the data type associated with the current column.
ActionSelect a data type in the properties of the current column.
 
600058Incorrect data type: Packed and Signed data types are not authorized

 

TypeError
DescriptionThe data type associated with the current column is incorrect: only Alphanumeric, Numeric and Date data types are authorized
ActionModify the data type in the attributes of the current column.

 

600059The definition is incorrect: the definition of the column must be between {2} and {3} characters

 

TypeError
DescriptionThe definition of the current column must be between {2} and {3} for the selected data type.
Parameter(s) {2} Minimum authorized definition
{3} Maximum authorized definition
ActionModify the definition of the column to comply with this restriction.

 

600060Import table entries: Incorrect Table entry '{1}'

 

TypeError
DescriptionAn error occurred while creating a line in the current Table from imported data {1} in the CSV import file.
Parameter(s) {1} Table entry read in import file.
ActionAnalyze the imported Table entry {1} and make the required corrections to the CSV import file.

 

600062<{0}> - Pre-calculation <{1}>: The decimal definition of the Pre-calculation must be between {2} and {3} characters

 

TypeError
DescriptionFor a Pre-Calculation of decimal type, the decimal definition is mandatory and its value must be greater than 0 and less than or equal to 9.
Parameter(s) {0} The name of the Transformation-Rule
{1} The name of the Pre-Calculation
{2} The minimum value for the decimal definition
{3} The maximum value for the decimal definition
ActionModify the decimal definition of the Pre-Calculation to comply with this restriction

 

600063"<{0}> - Pre-calculation <{1}>: The decimal definition of the Pre-calculation must be smaller than the global definition

 

TypeError
DescriptionFor a Pre-Calculation of decimal type, the decimal definition is mandatory and its value must be less than the global definition
Parameter(s) {0} The name of the Transformation-Rule
{1} The name of the Pre-Calculation
ActionModify the decimal definition of the Pre-Calculation to comply with this restriction

 

600064<{0}> - Column <{1}>: The decimal definition of the column must be between {2} and {3} characters

 

TypeError
DescriptionFor a column of decimal type the decimal definition is mandatory and its value must be greater than 0 and less than or equal to 9
Parameter(s) {0} The name of the Table
{1} The name of the Column
{2} The minimum value for the decimal definition
{3} The maximum value for the decimal definition
ActionModify the decimal definition of the Column to comply with this restriction

 

600065<{0}> - Column <{1}>: The decimal definition of the column must be less than the global definition

 

TypeError
DescriptionFor a column of decimal type the decimal definition is mandatory and its value must be less than the global definition
Parameter(s) {0} The name of the Table
{1} The name of the Column
ActionModify the decimal definition of the Column to comply with this restriction

 

600066<{0}>: The table can contain only one value column in case of decimal column definition

 

TypeError
DescriptionThe table structure must contain only one value column in case of decimal column definition
Parameter(s) {0} The name of the Table
ActionModify the structure of the Table to comply with this restriction

 

600067<{0}>: Column <{1}> / Line <{2}>: The cell value ''{3}'' is not a valid decimal value. The value should respect the format: x.y

 

TypeError
DescriptionThe specified cell value must respect the following pattern: The only characters authorized for the Decimal data type are the digits from 0 to 9 and the decimal separator ".". The decimal separator must not be the first or the last character of the value
Parameter(s) {0} The name of the Table
{1} The name of the Column
{2} The ID of the line
{3} The value of the cell
ActionModify the cell value to respect the format

 

600068<{0}>: Column <{1}> / Line <{2}>: The cell value ''{3}'' is incorrect: the number of decimal digits must not be greater than the decimal definition

 

TypeError
DescriptionThe specified cell value is incorrect for the following reason: The number of decimal digits is greater than the decimal definition of the Column
Parameter(s) {0} The name of the Table
{1} The name of the Column
{2} The ID of the Line
{3} The value of the cell
ActionModify the cell value to comply with this restriction

 

600069The link between the {1} ''{0}'' and the {2} ''{3}'' will be deleted. Caution: The status of {2} reverts to ToBeChecked

 

TypeInformation
DescriptionAn existing reference link between the rule {1} and event type {2} has been deleted. The status of {2} reverts to ToBeChecked.
Parameter(s) {0}
{1}
{2}
{3}
Rule name
Rule type
Event type
Event type name
ActionVerify that the link is no longer required.
 
600070The status of {1} ''{0}'' ({2}) prevents AccountingIntegrator Enabler from removing the latest version of this rule '' {3}''

 

TypeError
DescriptionA Rule cannot be removed from an Event type because of the event type status {2}.
Parameter(s) {0}
{1}
{2}
Event type name.
Event type
Event type status
{3} Rule name
ActionPerform a Back To Design on the Event type. Then, remove the Rule. Repeat action.
 
600071The {1} '{0}' and the {1} '{2}' have the same validity start date

 

TypeError
DescriptionTwo versions of the same Rule object are specified with identical validity start dates. This type of configuration is not authorized. The AccountingIntegrator Enabler execution engine uses the Rule version validity period to identify which version of the Rule to run: The execution engine runs the Rule version whose start validity date is closest to the processing date.
Parameter(s) {0} Name and version of the Rule
{1} Rule type: Aggregation-Rule, Audit-Rule, Balancing-Rule and so on
{2} Name and version of the Rule
ActionModify the validity start date of one of the two Rule versions.
 
600072The status of {1} '{0}' ({2}) prevents AccountingIntegrator Enabler from adding a Rule version.

 

TypeError
DescriptionDuring the creation of a new version of a Rule or the modification of the validity period of a Rule version used by an Input-Event or a Processing-Context-Out, the Input-Event object or Processing-Context-Out {0} affected, must be modified with the addition or deletion of a link. However, in these circumstances, the Input-Event object or Processing-Context-Out is not modifiable and its status {2} precludes any modification of the object.
Parameter(s) {0} Name of the Input-Event or Processing-Context-Out to modify
{1} Object type to modify: Input-Event or Processing-Context-Out
{2} Status of Input-Event or Processing-Context-Out to modify
ActionModify the status of the Input-Event or Processing-Context-Out {0} affected to send it back to development.
 
600073The {1} '{0}' will be linked to the {2} '{3}'.

 

TypeInformation
DescriptionCreating a new version of a Rule or modifying the validity period of an existing Rule version can cause modifications to the parent objects, that is, Input-Event or Processing-Context-Out, linked to it, and thereby require modifications to their status.
Parameter(s) {0} Name and version of the Rule
{1} Rule type: Aggregation-Rule, Audit-Rule, Balancing-Rule, and so on
{2} Object type to modify: Input-Event or Processing-Context-Out
{3} Name of the Input-Event or Processing-Context-Out to modify
ActionThis is an information message: Check all the Input-Event or Processing-Context-Out objects affected.
 
600074"<{0}>: Column <{1}> / Line <{2}>: The cell value ''{3}'' is incorrect: the length of the integral part must not be greater than the integral part definition

 

TypeError
DescriptionThe specified cell value is incorrect for the following reason: The number of digits of the integral part is greater than the difference between the total definition and the decimal definition of the Column
Parameter(s) {0} The name of the Table
{1} The name of the Column
{2} The ID of the Line
{3} The value of the cell
ActionModify the cell value to comply with this restriction

 

600075The validity period of the Rule version '{0}' does not correspond to that of the Input-Event '{1}'. It will therefore not be linked to this Input-Event.

 

TypeInformation
DescriptionAn Input-Event object {1} references the Rule object. However the Input-Event {1} will not use this version of the Rule because the version validity period does not overlap those in the Input-Event.
Parameter(s) {0} Name and version of the Rule
{1} Name of the Input-Event
ActionThis is an information message.
 
600076Unknown object type: It is recommended that you identify how to reproduce this error and then contact Axway Product Support.

 

TypeError
DescriptionAn internal data integrity check failed.
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
600078Unable to save {1} '{0}': Refer to the Log pane to identify the problem(s) encountered

 

TypeError
DescriptionSaving of current version Rule has been stopped as parent object is in use (Input-Event or Processing-Context-Out objects)
Parameter(s) {0} Name and version of the Rule
{1} Rule type: Aggregation-Rule, Audit-Rule, Balancing-Rule and so on
ActionRefer to the log pane to identify the problem(s) encountered and resolve them.
 
600079The link between the {1} '{0}' and the {2} '{3}' will be deleted.

 

TypeInformation
DescriptionModifying the validity period of a version of a Rule can cause modifications to the parent objects, that is Input-Event or Processing-Context-Out, linked to it, and thereby require modifications to their status.
Parameter(s) {0} Name version of the Rule
{1} Rule type: Aggregation-Rule, Audit-Rule, Balancing-Rule, and so on
{2} Object type to modify: Input-Event or Processing-Context-Out
{3} Name of the Input-Event or Processing-Context-Out to modify
ActionThis is an information message: Check all the Input-Event or Processing-Context-Out objects affected.
 
600080 608101 608102 608103 608104 608105 608108 608109 608110 608111 608112 608113 608114 608115 608116 608117The Business-Document leaf element selected for the {1} attribute must have a {2} data type and a definition between {3} and {4} characters

 

TypeError
DescriptionThis is a generic message.
The type of Business-Document leaf element used to specify an attribute of the current object is incorrect. The expected Business-Document leaf element must have a data type {2} and a definition between {3} and {4} characters.
Parameter(s) {1} Name of the attribute: name of Input-Event, instance code and so on
{2} Expected data type: Alphanumeric (lg), Numeric [9 999], Packed [9 999+/-], Date [YYYYMMDD], Date [YYYMMDD] or Date [YYMMDD]
{3} Minimum authorized definition
{4} Maximum authorized definition
ActionModify the Business-Document leaf element selected for the '{1}' attribute of the current object.
 
600081 608102 608105 608106 608107 608110 608114 608118 608119The Business-Document leaf element selected for the '{1}' attribute must have a {2} data type and a definition of {3} characters

 

TypeError
DescriptionThis is a generic message.
The type of Business-Document leaf element used to specify an attribute of the current object is incorrect. The expected Business-Document leaf element must have a(n) {2} data type and a definition of {3} characters.
Parameter(s) {1} Name of the attribute: name of Input-Event, instance code and so on
{2} Expected data type: Alphanumeric (lg), Numeric [9 999], Packed [9 999+/-], Date [YYYYMMDD], Date [YYYMMDD] or Date [YYMMDD]
{3} Authorized definition
ActionModify the Business-Document leaf element selected for the {1} attribute of the current object.
 
600082 608102 608104 608105 608108The Business-Document leaf element selected for the attribute '{1}' must have a {2} data type

 

TypeError
DescriptionThis is a generic message.
The type of Business-Document leaf element used to specify an attribute of the current object is incorrect. The expected Business-Document leaf element must have a(n) {2} data type.
Parameter(s) {1} Name of the attribute: name of Input-Event, instance code and so on
{2} Expected data type: Alphanumeric (lg), Numeric [9 999], Packed [9 999+/-], Date [YYYYMMDD], Date [YYYMMDD] or Date [YYMMDD]
ActionModify the Business-Document leaf element selected for the {1} attribute of the current object.
 
600083The definition of the printable accounting fields is incorrect: the total of all the selected Business-Document leaf element definitions must be less than or equal to {1} characters

 

TypeError
DescriptionThere is a configurable print zone limited to 256 characters in the accounting report generated by the execution engine. The total of all the Output-Event leaf elements, that is, leaf elements to report in this print zone, is therefore limited to 256 characters.
Parameter(s) {1} Maximum total definitions authorized
ActionModify the list of selected Business-Document leaf elements to respect this limit.
 
600084Reached maximum number of selected Business-Document leaf elements in printable accounting fields: {1}

 

TypeError
DescriptionThe configurable zone in the accounting reports generated by the execution engine, cannot contain more than 20 Output-Event leaf elements.
Parameter(s) {1} Maximum number of Business-Document leaf elements authorized
ActionModify the list of selected Business-Document leaf elements to respect this limit.
 
600085 608001 608002 608003 608004 608008 608009 608012 608013 608015 608111The value of the {1} attribute must have at least one character

 

TypeError
DescriptionThis is a generic message.
No value was entered for an attribute of the current object: a non-empty character string is mandatory for this attribute.
Parameter(s) {1} Name of the attribute: name of Input-Event, instance code and so on
ActionEnter a value for the {1} attribute of the current object.
 
600086 608001 608002 608003 608004 608008 608009The maximum authorized definition for the {1} attribute must not exceed {2} characters

 

TypeError
DescriptionThis is a generic message.
No value was entered for an attribute of the current object: a non-empty character string is mandatory for this attribute.
Parameter(s) {1} Name of the attribute: name of Input-Event, instance code and so on
{2} Maximum authorized definition
ActionEnter a value for the '{1}' attribute of the current object.
 
600087 608002The value of the Input-Event version' attribute has an incorrect date format

 

TypeError
DescriptionThe value specified for the Input-Event version' attribute in the current Processing-Context-In object is incorrect. The character string entered must have an 8-character definition. The internal format is 'YYYYMMDD'.
ActionVerify that a date has been selected or entered.
 
600088The Business-Document leaf element selected for the ''{1}'' attribute must have a {2} or {3} data type and a definition of {4} characters

 

TypeError
DescriptionThe selected leaf element has not got appropriate DML type ({2} or {3}) and definition {4}.
Parameter(s) {1} Name of the attribute
{2}
{3}
{4}
Numeric DML type
Alphanumeric DML type
Maximum authorized definition
ActionModify the leaf name to comply with this restriction..

 

600091<{0}>: The length of the direction credit value must be less than or equal to the length of the direction code field

 

TypeError
DescriptionThe length of each direction credit value must be less than or equal to the length defined for the "direction" code field.
Parameter(s) {0} Logical name of the Processing-Context-Out
ActionCorrect the direction credit value.

 

600092<{0}>: The ''Credit value'' and the ''Debit value'' should not be equal

 

TypeError
DescriptionThe "Credit value" and the "Debit value" must not be equal.
Parameter(s) {0} Logical name of the Processing-Context-Out
ActionCorrect the values.

 

600093<{0}>: The ''Credit value'' and the ''Reversal debit value'' should not be equal

 

TypeError
DescriptionThe "Credit value" and the "Reversal debit value" must not be equal.
Parameter(s) {0} Logical name of the Processing-Context-Out
ActionCorrect the values.

 

600094<{0}>: The ''Reversal credit value'' and the ''Debit value'' should not be equal

 

TypeError
DescriptionThe "Reversal credit value" and the "Debit value" must not be equal.
Parameter(s) {0} Logical name of the Processing-Context-Out
ActionCorrect the values.

 

600095<{0}>: The ''Reversal credit value'' and the ''Reversal debit value'' should not be equal

 

TypeError
DescriptionThe "Reversal credit value" and the "Reversal debit value" should not be equal
Parameter(s) {0} Logical name of the Processing-Context-Out
ActionCorrect the values in order to accomplish this restriction.

 

600096<{0}>: The length of the direction debit value must be less or equal to the length of the direction code field

 

TypeError
DescriptionThe length of each direction debit value must be less than or equal to the length defined for the "direction" code field
Parameter(s) {0} Logical name of the Processing-Context-Out
ActionCorrect the direction debit value.

 

600097<{0}>: The length of the direction reversal credit value must be less or equal to the length of the direction code field

 

TypeError
DescriptionThe length of each direction reversal credit value must be less than or equal to the length defined for the "direction" code field.
Parameter(s) {0} Logical name of the Processing-Context-Out
ActionCorrect the direction reversal credit.

 

600098<{0}>: The length of the direction reversal debit value must be less than or equal to the length of the direction code field

 

TypeError
DescriptionThe length of each direction reversal debit value must be less than or equal to the length defined for the "direction" code field.
Parameter(s) {0} Logical name of the Processing-Context-Out
ActionCorrect the direction reversal debit value.

 

600100The Business-Field definition must be between {1} and {2} characters

 

TypeError
DescriptionThe definition specified is incompatible with the Business-Document leaf element data type: only values between {1} and {2} are authorized.
Parameter(s) {1} Minimum authorized definition
{2} Maximum authorized definition
ActionModify the Business-Field definition to respect the {1} to {2} limit.
 
600101The Business-Field definition must be specified

 

TypeError
DescriptionThe Business-Field definition is empty: you must specify a value
ActionSpecify a definition in the Business-Field properties.
 
600102<{0}>: The Business-Field decimal definition must be specified

 

TypeError
DescriptionFor Business-Fields of decimal type, the decimal definition is empty: you must specify a value
Parameter(s) {0} The name of the Business-Field
ActionSpecify a decimal definition in the Business-Field properties

 

600103<{0}>: The Business-Field decimal definition must be between {1} and {2} characters

 

TypeError
DescriptionFor Business-Fields of decimal type, the decimal definition is mandatory and its value must be greater than 1 and less than or equal to 9
Parameter(s) {0} The name of the Business-Field
{1} Minimum authorized decimal definition
{2} Maximum authorized decimal definition
ActionModify the Business-Field decimal definition to respect the {1} to {2} limit

 

600104<{0}>: The Business-Field decimal definition must be smaller than the global definition

 

TypeError
DescriptionFor Business-Fields of decimal type, the decimal definition is mandatory and its value must be smaller than the global definition
Parameter(s) {0} The name of the Business-Field
ActionModify the Business-Field decimal definition to comply the restriction

 

600110The definition of the Business-Document leaf element '{1}' must be between {2} and {3} characters

 

TypeError
DescriptionThe definition of the current Business-Document leaf element {1} must be between {2} and {3} for the selected data type.
Parameter(s) {1} Name of Business-Document leaf element
{2} Minimum authorized definition
{3} Maximum authorized definition
ActionModify the Business-Document leaf element definition to respect the {2} to {3} limit.
 
600111Maximum number of Business-Document leaf elements reached: {1}

 

TypeError
DescriptionYou cannot create a new leaf element in the current Business-Document: the maximum number of authorized leaf elements, 1500, has been reached.
Parameter(s) {1} Maximum number of leaf elements authorized in a Business-Document
 
600113The Business-Document must only contain one segment

 

TypeError
DescriptionAn AccountingIntegrator Enabler Business-Document can only be mono-segment.
ActionModify the Business-Document to respect this restriction.
 
600114The segment '{1}' must not contain more than {2} Business-Document leaf elements

 

TypeError
DescriptionAn AccountingIntegrator Enabler Business-Document can only be mono-segment, with a maximum number of 1500 leaf elements, including the leaf element redefinitions.
Parameter(s) {1} Name of Business-Document segment
{2} Maximum number of leaf elements authorized for an AccountingIntegrator Enabler Business-Document segment
ActionModify the Business-Document to respect this limit.
 
600115The segment '{1}' must contain a maximum of {2} characters

 

TypeError
DescriptionAn AccountingIntegrator Enabler Business-Document can only be mono-segment, with a maximum definition of 4000 characters per segment.
Parameter(s) {1} Name of Business-Document segment
{2} Maximum authorized definition for an AccountingIntegrator Enabler Business-Document segment
ActionModify the Business-Document to respect this limit.
 
600116The redefinition of the Business-Document leaf element '{1}' must be less than or equal to {2} characters

 

TypeError
DescriptionThe sum of the physical definitions of the elements in a redefinition, that is, the Business-Document leaf element and filler, must not exceed the physical definition of the redefined leaf element.
Parameter(s) {1} Name of Business-Document leaf element
{2} Maximum authorized redefinition
ActionModify the Business-Document leaf element redefinition to respect this limit.
 
600117The name of the Business-Document leaf element '{1}' is a reserved word

 

TypeError
DescriptionThe character string checked corresponds to one of the following reserved words in the AccountingIntegrator Enabler Data Manipulation Language (DML): 'ACCTABD', 'ACCTAB', 'YEAR', 'YEAR4', 'DATEMINUS', 'DATEPLUS', 'CHECKTABD', 'CHECKTAB', 'CHECK', 'SYSDATE', 'ERR', 'ENV', 'NUMSEG', 'NUMSC', 'NUMSEGSC', 'NUMSCSEG', 'SEGSTRUC', 'EVTCODE', 'SEGCODE', 'DOMAIN', 'STARTDATE', 'ENDDATE', 'SENDER', 'INSTANCE', 'GROUP', 'PHASE', 'RULE', 'FIRSTGROUP', 'LASTGROUP', 'FIRSTPHASE', 'LASTPHASE', 'EXTTABD', 'EXTTAB', 'DAY', 'MONTH', 'NBDAYS', 'NULL', 'JULIAN', 'SEARCH', 'AND', 'OR', 'IF', 'THEN', 'ELSE', 'LOW_VALUE', 'HIGH_VALUE', 'NUMERIC', 'COND_EVT', 'COND_SEG'.
Parameter(s) {1} Name of Business-Document leaf element
ActionEnter a new character string avoiding the list of AccountingIntegrator Enabler DML reserved words.
 
600118The name of the Business-Document leaf element '{1}' must include at least one alphabetical character

 

TypeError
DescriptionThe Business-Document leaf element name must contain at least one valid alphabetical character: 'A', 'B', 'C', 'D', &, 'Z' or '_'.
Parameter(s) {1} Name of Business-Document leaf element
ActionModify the name of the Business-Document leaf element to comply with this restriction.
 
600119Unauthorized character '{1}' in the name of the Business-Document leaf element '{2}'

 

TypeError
DescriptionAt least one character in the Business-Document leaf element name checked is incorrect: The only authorized characters are 'A', 'B', 'C', 'D', &, 'Z', '_', '0', '1', '2', &, '9'.
Parameter(s) {1} Invalid character
{2} Name of Business-Document leaf element
ActionReplace the unauthorized character in the character string with a valid character.
 
600120The segment '{1}' must contain at least one Business-Document leaf element

 

TypeError
DescriptionA segment is a logical representation of one or several Business-Document leaf elements: therefore a segment must contain at least one leaf element.
Parameter(s) {1} Name of Business-Document segment
ActionModify the Business-Document to comply with this restriction.
 
600121Line [{2}] in the import file is incorrectly formatted

 

TypeError
DescriptionEither the number of values identified in line {2} does not correspond to the expected number of values or the import Business-Document leaf element definition is incorrect: Only numbers are authorized.
Parameter(s) {2} Line of data read from import file
ActionVerify the data separators used to format the lines in the import file and the expected data in each line of the file.
 
600122Line [{2}] in the import file does not contain a recognized data type

 

TypeError
DescriptionUnknown data type entered in import Business-Document leaf element in line [{2}].
Parameter(s) {2} Line number of data read from the import file
ActionModify the data type of the Business-Document leaf element entered in line [{2}].
 
600124The definition of the name of segment '{1}' must be less than or equal to {2} characters

 

TypeError
DescriptionA Business-Document name is limited to 10 characters.
Parameter(s) {1} Name of Business-Document segment
{2} Maximum authorized definition for the segment name
ActionModify the Business-Document to respect this limit.
 
600125Unauthorized character '{1}' in the name of segment '{2}'

 

TypeError
DescriptionAt least one character in the segment name checked is incorrect: only the characters 'A', 'B', 'C', 'D', &, 'Z', '_', '0', '1', '2', &,' 9' are authorized.
Parameter(s) {1} Invalid character
{2} Name of Business-Document segment
ActionReplace the unauthorized character in the character string with a valid character.
 
600126The depth of the Business-Document leaf element '{1}' exceeds the maximum depth {2}

 

TypeError
DescriptionThe number of nested Business-Document leaf element redefinitions, that is the depth, is limited to 8.
Parameter(s) {1} Name of Business-Document leaf element
{2} Maximum authorized depth
ActionModify the Business-Document to respect this limit.
 
600128<{0}>: The decimal definition of the Business-Document leaf element ''{1}'' must be between {2} and {3} characters

 

TypeError
DescriptionThe decimal definition of the current Business-Document leaf element {1} must be between {2} and {3} for the selected decimal type
Parameter(s) {0} Name of Business-Document
{1} Name of Business-Document leaf element
{2} Minimum authorized decimal definition
{3} Maximum authorized decimal definition
ActionModify the Business-Document leaf element decimal definition to respect the {2} to {3} limit

 

600129<{0}>: The decimal definition of the Business-Document leaf element ''{1}'' must be smaller than the global definition

 

TypeError
DescriptionThe decimal definition of the current Business-Document leaf element {1} must be smaller than its global definition
Parameter(s) {0} Name of Business-Document
{1} Name of Business-Document leaf element
ActionModify the Business-Document leaf element decimal definition to comply the restriction

 

600130The filter value specified on the {2} plate cannot be empty

 

TypeError
DescriptionA filter value specified on the {2} plate is incorrect. Empty character strings are forbidden: you must enter at least one character.
Parameter(s) {2} Type of plate: left or right
ActionModify the Balance Set to comply with this restriction.
 
600131The filter value specified on the {2} plate is forbidden: no filter field is selected

 

TypeError
DescriptionThe filter values are specified, but the associated Output-Event leaf element is undefined.
Parameter(s) {2} Type of plate left or right
ActionModify the Balance Set to comply with this restriction.
 
600132The filter field on the {2} plate is incorrect: only Alphanumeric and Numeric leaf elements are authorized

 

TypeError
DescriptionThe Output-Event leaf element that acts as a filter for the plate is incorrect: only Alphanumeric or Numeric data types can be used as a Filter. Thus, the Business-Document leaf element selected must be either Numeric (N) or Alphanumeric (A).
Parameter(s) {2} Type of plate: left or right
ActionModify the Balance Set to comply with this restriction.
 
600133The filter field on the {2} plate is forbidden: no Cumulative Field is selected

 

TypeError
DescriptionOn the current plate, you have defined an Output-Event leaf element to filter the Output-Events, but have not specified an Output-Event leaf element to cumulate.
Parameter(s) {2} Type of plate: left or right
ActionModify the Balance Set to comply with this restriction.
 
>
600134<{0}> - Balancing Set <{1}>: The cumulative field is incorrect on platter {2}: only Integer and Decimal leaf elements are authorized.

 

TypeError
DescriptionThe Output-Event leaf element that will be cumulated for the plate is incorrect: only Numeric, Signed or Packed data types (Integer or Decimal) can be cumulated. Thus, the Business-Document leaf element selected must be Numeric (N), Signed (S) or Packed (P) (Integer or Decimal).
Parameter(s) {0} The logical name of the Balancing-Rule
{1} The order of the Balancing-Set
{2} Type of plate: left or right
Action 

 

600135The Cumulative Field on the left plate is mandatory

 

TypeError
DescriptionUnlike the right plate, the definition of a left plate is mandatory for a Balance Set: You must therefore specify an Output-Event leaf element to cumulate on the left plate.
ActionSelect a Business-Document leaf element for the Cumulative Field attribute on the left plate of the Balance Set.
 
600136Maximum number of filter values reached on the {3} plate: {2}

 

TypeError
DescriptionOn a plate in a Balance Set, you can only specify 10 filter values for the Output-Event leaf element used as a filter.
Parameter(s) {2} Maximum number of filter values authorized
{3} Type of plate: left or right
ActionModify the Balance Set to respect this limit.
 
600137Maximum number of Criteria fields reached: {2}

 

TypeError
DescriptionIn a Balance Set you cannot define more than 20 Output-Event leaf elements as balance criteria.
Parameter(s) {2} Maximum number of authorized balance criteria.
ActionModify the Balance Set to respect this limit.
 
600138The definition of the left plate is mandatory

 

TypeError
DescriptionThe definition of a left plate is mandatory for a Balance Set.
ActionSelect a Business-Document leaf element for the Cumulative Field attribute on the left plate of the Balance Set.
 
600139At least one Criteria field must be selected

 

TypeError
DescriptionIf you do not specify the right plate, you must set at least one balance criteria.
ActionModify the Balance Set to comply with this restriction.
 
600140Maximum number of Balance Set definitions reached: {1}

 

TypeError
DescriptionA Balancing-Rule can only contain 50 Balance Sets.
Parameter(s) {1} Maximum authorized number of Balance Sets
ActionModify the Balance Set to respect this limit.
 
600141A Balancing-Rule must contain at least one Balance Set definition

 

TypeError
DescriptionA Balancing-Rule must have at least one Balance Set defined.
ActionCreate at least one Balance Set in the Balancing-Rule.
 
600142At least one filter value is mandatory on the {2} plate: a filter field is selected

 

TypeError
DescriptionOn a plate if you set an Output-Event leaf element to filter the Output-Events, you must specify at least one filter value.
Parameter(s) {2} Type of plate: left or right
ActionAdd a filter value to the plate or delete the Business-Document leaf element selected for the Filter field attribute.
 
600143You cannot select an Output-Event type Financial-Tag: delete a Criteria field first

 

TypeError
DescriptionThe execution engine incorporates the list of Output-Event type Financial-Tags selected for a Balance Set as additional balance criteria. Therefore the total number of Criteria fields in a Balance Set must not exceed 19, if you want to use Output-Event type Financial-Tags as balance criteria.
ActionModify the Balance Set to respect this limit.
 
600144Cannot select leaf element '{2}': one of the Business-Document leaf elements higher or lower in the hierarchy '{3}' is already in use

 

TypeError
DescriptionIn a Balance Set definition, you cannot reference the same or a part of the same Output-Event leaf element.
Parameter(s) {2} Name of the Business-Document leaf element
{3} Name of the conflicting Business-Document leaf element
ActionModify the Balance Set to comply with this restriction.
 
600145The multiple Business-Document leaf element selection '{2}' is forbidden

 

TypeError
DescriptionIn a Balance Set definition, you cannot make several references to the same or a part of the same Output-Event leaf element.
Parameter(s) {2} Name of the Business-Document leaf element
ActionModify the Balance Set to comply with this restriction.
 
600146The operator must be set to Equals

 

TypeError
DescriptionIf you do not specify the right plate in a Balance Set, you must set the balance operator to Equals.
ActionModify the Balance Set to comply with this restriction.
 
600147The filter value specified on the {2} plate is incorrect: The definition of the value must be between {3} and {4} characters

 

TypeError
DescriptionA filter value specified on the {2} plate is incorrect. The definition of the character string entered must be between {3} and {4}.
Parameter(s) {2} Type of plate: left or right
{3} Minimum authorized definition
{4} Maximum authorized definition
ActionModify the Balance Set to comply with this restriction.

 

 

 

600148The filter value specified on the {2} plate is incorrect: unauthorized character '{3}

 

TypeError
DescriptionA filter value specified on the {2} plate is incorrect. The {3} character is not authorized: only ASCII characters with decimal values between 32 and 126 (inclusive) are authorized for an alphanumeric data type.
Parameter(s) {2} Type of plate: left or right
{3} Character causing the exception
ActionReplace the unauthorized character in the character string with a valid character.

 

 

600149<{0}>: A Balancing-Rule should have one and only one Balancing set if the compensation process is enabled

 

TypeError
DescriptionIf the compensation option is set, the Balancing-Rule must have one (and only one) Balancing Set. If not, the check fails.
Parameter(s) {0} Logical name of the Balancing-Rule
ActionCorrect the Balancing-Rule.

 

600150The remote user is mandatory

 

TypeError
DescriptionYou can install an AccountingIntegrator Enabler execution engine on the remote machine where you installed the Broadcast Agent. Therefore, you must specify the account to use to connect to the environment of the AccountingIntegrator Enabler &#160;Rule Engine , in the properties of the AccountingIntegrator Enabler server associated with execution engine.
ActionComplete the Remote user attribute of the AccountingIntegrator Enabler server.
 
600151The AccountingIntegrator Enabler &#160;Rule Engine operating directory is mandatory

 

TypeError
DescriptionTo be able to execute operations in the AccountingIntegrator Enabler transformation execution engine, you must specify the operating directory for the target AccountingIntegrator Enabler &#160;Rule Engine (RDJ_EXEC).
ActionComplete the operating directory attribute of the AccountingIntegrator Enabler server.
 
600152The AccountingIntegrator Enabler Broadcast Agent operating directory is mandatory

 

TypeError
DescriptionThe installation directory for the Broadcast environment associated with the AccountingIntegrator Enabler server is not specified. This information is mandatory for the AccountingIntegrator Enabler Broadcast Agent to execute a transaction.
ActionComplete the Agent directory attribute of the AccountingIntegrator Enabler server.
 
600153The AccountingIntegrator Enabler manager installation directory is mandatory

 

TypeError
DescriptionTo be able to execute operations in the AccountingIntegrator Enabler transformation execution engine, you must specify the installation directory for the target transformation execution engine (RDJ_HOME).
ActionComplete the Installation directory attribute of the AccountingIntegrator Enabler server.
 
600157The Automator instance name to execute is mandatory

 

TypeError
DescriptionIn order to link AccountingIntegrator Enabler &#160;Rule Engine and AccountingIntegrator Enabler Enabler via Automator, the Automator instance name is required.
ActionEnter a value for the Instance attribute on the Automator tab for the AccountingIntegrator Enabler server.
 
600158The Automator job name to execute is mandatory

 

TypeError
DescriptionIn order to link AccountingIntegrator Enabler manager and AccountingIntegrator Enabler Enabler via Automator, the Automator job name is required.
ActionEnter a value for the Job attribute on the Automator tab for the AccountingIntegrator Enabler server.
 
600159The Automator production server installation directory is mandatory

 

TypeError
DescriptionIn order to link AccountingIntegrator Enabler manager and AccountingIntegrator Enabler Enabler via Automator, the Automator installation directory is required.
ActionEnter a value for the Instance attribute on the Automator tab for the AccountingIntegrator Enabler server.
 
600160The ISIMAN production server installation directory is mandatory

 

TypeError
DescriptionIn order to link AccountingIntegrator Enabler to ISIMAN, the ISIMAN production server directory is required.
ActionEnter a value for the Installation directory attribute on the Finance export tab for the AccountingIntegrator Enabler server.
 
600161The ISIMAN repository name is mandatory

 

TypeError
DescriptionIn order to link AccountingIntegrator Enabler to ISIMAN, the ISIMAN repository is required.
ActionEnter a value for the Repository attribute on the Finance export tab for the AccountingIntegrator Enabler server.
 
600170Maximum number of Aggregate fields reached: {1}

 

TypeError
DescriptionThe number of Input or Output-Event segments, that is Business-Document leaf elements, to aggregate cannot exceed 50.
Parameter(s) {1} Maximum number of Aggregate fields authorized
ActionModify the Aggregation-Rule to respect this limit.
 
600171Maximum number of Report fields reached: {1}

 

TypeError
DescriptionThe number of aggregated segment leaf elements in which you can set a fixed value, cannot exceed 500.
Parameter(s) {1} Maximum number of Report fields authorized
ActionModify the Aggregation-Rule to respect this limit.
 
600172Maximum number of Criteria fields reached: {1}

 

TypeError
DescriptionThe number of Input or Output-Event segments, that is Business-Document leaf elements, used, as aggregation criteria cannot exceed 100.
Parameter(s) {1} Maximum number of Criteria fields authorized
ActionModify the Aggregation-Rule to respect this limit.
 
600173The aggregation criteria definition is incorrect: the total definition of all the Business-Document leaf elements selected must be less than or equal to {1} characters

 

TypeError
DescriptionThe set of Business-Document leaf elements used as aggregation criteria must not exceed 4000 characters.
Parameter(s) {1} Maximum total definitions authorized
ActionModify the Aggregation-Rule to respect this limit.
 
600174A formula is required for the Aggregate field '{1}'

 

TypeError
DescriptionYou must specify the type of operation to perform to aggregate the same Business-Document leaf element in several segments, that is, Sum, Average, and so on.
Parameter(s) {1} Name of the Business-Document leaf element
ActionSpecify the formula to use: Sum, Average, and so on for the Business-Document leaf element to aggregate.
 
600175A value is required in the Report field '{1}'

 

TypeError
DescriptionThe fixed value in the aggregated segment for the Report field {1} is incorrect. Empty character strings are forbidden: you must enter at least one character.
Parameter(s) {1} Name of the Business-Document leaf element
ActionModify the Aggregation-Rule to comply with this restriction.
 
600176The Aggregate field '{1}' is incorrect: only Numeric, Signed and Packed Business-Document leaf elements are authorized

 

TypeError
DescriptionThe definition of the Input- or Output-Event Segment to aggregate is incorrect: only Numeric, Packed or Signed data types can be aggregated. Therefore, the data type of the selected Business-Document leaf element must be Numeric (N), Packed (P) or Signed (S).
Parameter(s) {1} Name of the Business-Document leaf element
ActionModify the Aggregation-Rule to comply with this restriction.
 
600177Cannot select leaf element {1}: one of the Business-Document leaf elements higher or lower in the hierarchy {2} is already in use

 

TypeError
DescriptionWhen defining an Aggregation-Rule you cannot make several references to the same or part of the same Input- or Output-Event Segment.
Parameter(s) {1} Name of the Business-Document leaf element
{2} Name of the Business-Document leaf element
ActionModify the Aggregation-Rule to comply with this restriction.
 
600178The multiple Business-Document leaf element selection {1} is forbidden

 

TypeError
DescriptionWhen defining an Aggregation-Rule you cannot make several references to the same or part of the same Input- or Output-Event Segment.
Parameter(s) {1} Name of the Business-Document leaf element
ActionModify the Aggregation-Rule to comply with this restriction.
 
600179Incorrect value for the Report field '{1}': The definition of the value must be between {2} and {3} characters

 

TypeError
DescriptionThe fixed value in the aggregated segment for the Report field {1} is incorrect. The definition of the character string entered must be between {2} and {3}.
Parameter(s) {1} Name of the Business-Document leaf element
{2} Minimum authorized definition
{3} Maximum authorized definition
ActionModify the Aggregation-Rule to comply with this restriction.
 
600180Incorrect value in Report field {1}: Unauthorized character '{2}'

 

TypeError
DescriptionThe fixed value in the aggregated segment for the Report field {1} is incorrect. The character {2} is not authorized: only ASCII characters with decimal values between 32 and 126 (inclusive) are authorized for an Alphanumeric data type.
Parameter(s) {1} Name of the Business-Document leaf element
{2} Character causing the exception
ActionReplace the unauthorized character in the character string with a valid character.
 
600181The Aggregation-Rule must contain at least one Aggregate field

 

TypeError
DescriptionTo aggregate Input- or Output-Event Segments, you must define at least one Business-Document leaf element to aggregate: leaf element common to all the segments to be processed.
ActionSelect one or more Business-Document leaf elements from the list of Input- or Output-Event Segments to aggregate.
 
600182The Aggregation-Rule must contain at least one Criteria field

 

TypeError
DescriptionTo aggregate Input- or Output-Event Segments, you must define at least one Business-Document leaf element to use as aggregation criteria: zone common to all the segments to be processed.
ActionSelect one or more Business-Document leaf elements in the list of Input- or Output-Event Segments to aggregate.

 

 

600183Reached maximum number of Aggregate fields printed in the aggregation report: {1}

 

TypeError
DescriptionThe configurable zone in the aggregation report generated by the execution engine cannot contain more than 10 Aggregate fields.
Parameter(s) {1} Maximum number of printable Aggregate fields
ActionModify the Aggregation-Rule to comply with this restriction.

 

 

600184<{0}>: Incorrect value in Report field ''{1}'': The value should respect the format: x.y

 

TypeError
DescriptionThe specified value must respect the following pattern: The only characters authorized for the Decimal data type are the 0 to 9 digits and the decimal separator ".". The decimal separator must not be the first or the last character of the value
Parameter(s) {0} The name of the Aggregation-Rule
{1} Name of the Business-Document leaf element
ActionModify the value in order to respect the format

 

600185<{0}>: Incorrect value in Report field ''{1}'': The number of decimal digits must not be greater than the decimal definition"

 

TypeError
DescriptionThe specified value is incorrect because the number of the decimal digits is greater than the decimal definition of the Business-Document leaf element
Parameter(s) {0} The name of the Aggregation-Rule
{1} Name of the Business-Document leaf element
ActionModify the value in order to comply the restriction

 

600186<{0}>: Incorrect value in Report field ''{1}'': The length of the integral part must not be greater than the integral part definition

 

TypeError
Description The specified value is incorrect because the number of digits of the integral part is greater than difference between the global definition and the decimal definition of the Business-Document leaf element
Parameter(s) {0} The name of the Aggregation-Rule
{1} Name of the Business-Document leaf element
ActionModify the value in order to comply the restriction

 

600190<{0}>: The Balancing-Rule should have two plates if the compensation process is enabled

 

TypeError
DescriptionIf the Compensation option is set in the Balancing-Rule, the Balancing-Rule must be double-plate. Both left and right plates settings must be defined. If not, the check fails.
Parameter(s) {0} Logical name of the Balancing-Rule
ActionCorrect the Balancing-Rule.

 

600191<{0}> - Balancing Set <{1}>: The operator should be Equal if the compensation process is enabled Type Error

 

TypeError
DescriptionIf the Compensation option is set in the Balancing-Rule, the Balancing Set operator must be "Equal". If not, the check fails.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Name of the Balancing-Set
ActionModify the name of the {1} object to remove the naming conflict with the {2} object.

 

600192<{0}>: The compensation process cannot be enabled if the Balancing Rule does not have an Output Business Document attached

 

TypeError
DescriptionIf the Balancing Rule does not have an Output Business Document attached, the compensation process cannot be enabled
Parameter(s) {0} Logical name of the Balancing-Rule
ActionAttach an Output Business Document to the Balancing Rule.

 

600193<{0}>: The compensation process cannot be enabled if the Balancing Rule does not have a Balancing Set

 

TypeError
DescriptionIf the Balancing Rule does not have at least one Balancing Set, the compensation process cannot be enabled.
Parameter(s) {0} Logical name of the Balancing-Rule
ActionCreate a Balancing Set for the Balancing-Rule.

 

600194<{0}>: The Balancing Rule contains more than one Balancing Set. The first Balancing Set will be taken into account for the compensation process

 

TypeWarning
DescriptionIf the Balancing-Rule contains more than one Balancing-Set, this warning message is thrown to the User in the workbench log pane.
Parameter(s) {0} Logical name of the Balancing-Rule
ActionCorrect the Balancing-Rule so as to have only a Balancing Set, or ignore the warning if you want to correct the Balancing-Rule during the check process.

 

600195<{0}>: The expression value length exceeds the length defined for the field {1}

 

TypeError
DescriptionThe length of the expression value from the left compensation mapping must not exceed the length defined on the field.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Field name
ActionCorrect the mapping expression in order to accomplish this restriction

 

600196<{0}>: Only numeric characters are allowed for the numeric field {1}

 

TypeError
DescriptionFor the numeric field from the left compensation mapping only numeric characters are allowed.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Field name
ActionCorrect the mapping expression.

 

600197<{0}>: Only numeric characters are allowed for the numeric field {1}

 

TypeError
DescriptionThe defined date for the date field from the left compensation mapping is not valid (for instance, there cannot be any "February, 30th”).
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Field name
ActionCorrect the mapping expression.

 

600198<{0}>: Only numeric characters are allowed for the date field {1}

 

TypeError
DescriptionThe date expression for the date field from the left compensation mapping must contain only numeric characters.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Field name
ActionCorrect the mapping expression.

 

600199<{0}>: The field {1} does not accept the \" character

 

TypeError
DescriptionThe field from the left compensation mapping does not accept double quote (") characters.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Field name
ActionCorrect the mapping expression.

 

600200The Audit trace must contain at least one Business-Document leaf element

 

TypeError
DescriptionTo audit the Input- or Output-Event Segments, you must define at least one Business-Document leaf element to audit: leaf element common to all the segments to be processed.
ActionSelect one or more Business-Document leaf elements in the list of Input- or Output-Event Segments to audit.
 
600201The Audit trace definition is incorrect: The total definition of all the Business-Document leaf elements selected must be less than or equal to {1} characters

 

TypeError
DescriptionThe total Business-Document leaf elements audited by the execution engine for an Input- or Output-Event Segment cannot exceed 4000 characters.
Parameter(s) {1} Maximum authorized definition
ActionModify the Audit-Rule to respect this limit.
 
600202Cannot select leaf element {1}: One of the Business-Document leaf elements higher or lower in the hierarchy {2} is already in use

 

TypeError
DescriptionWhen defining an Audit-Rule, you cannot make several references to the same or part of the same Input- or Output-Event Segments.
Parameter(s) {1} Name of the Business-Document leaf element
{2} Name of the Business-Document leaf element
ActionModify the Audit-Rule to comply with this restriction.
 
600203The multiple Business-Document leaf element selection {1} is forbidden

 

TypeError
DescriptionWhen defining an Audit-Rule, you cannot make several references to the same or part of the same Input- or Output-Event Segments.
Parameter(s) {1} Name of the Business-Document leaf element
ActionModify the Audit-Rule to comply with this restriction.

 

600205<{0}>: The decimal field {1} does not contain a valid decimal value. The value should respect the format: x.y

 

TypeError
DescriptionThe specified value must respect the following pattern: The only characters authorized for the Decimal data type are the 0 to 9 digits and the decimal separator ".". The decimal separator must not be the first or the last character of the value
Parameter(s) {0} The logical name of the Balancing-Rule
{1} The order of the decimal field
ActionModify the value in order to respect the format

 

600206<{0}>: The number of decimal digits must not be greater than the decimal definition of the leaf element {1}

 

TypeError
DescriptionThe specified value is incorrect because the number of decimal digits is greater than the decimal definition of the leaf element
Parameter(s) {0} The logical name of the Balancing-Rule
{1} The name of the leaf element
ActionModify the value to comply the restriction

 

600207<{0}> - Balancing Set <{1}>: The filter value specified on the {2} platter is incorrect: The value should respect the format: x.y

 

TypeError
DescriptionThe specified filter value must respect the following pattern: The only characters authorized for the Decimal data type are the 0 to 9 digits and the decimal separator "." The decimal separator must not be the first or the last character of the value
Parameter(s) {0} The logical name of the Balancing-Rule
{1} The order of the Balancing-Set
{2} The name of the platter: left or right
ActionModify the filter value to respect the format

 

600208<{0}> - Balancing Set <{1}>: The filter value specified on the {2} platter is incorrect: The number of decimal digits must not be greater than the decimal definition

 

TypeError
Description The specified filter value is incorrect for one or more of the following reasons: The number of decimal digits is greater than the decimal definition
Parameter(s) {0} The logical name of the Balancing-Rule
{1} The order of the Balancing-Set
{2} The name of the platter: left or right
ActionModify the filter value to comply the restriction

 

600209<{0}>: The length of the integral part must not be greater than the integral part definition of the leaf element {1}

 

TypeError
DescriptionThe specified value is incorrect for the following reason: The number of digits of the integral part is greater than the difference between the global definition and the decimal definition
Parameter(s) {0} The logical name of the Balancing-Rule
{1} The name of the leaf element
ActionModify the value to comply this restriction

 

600210<{0}>: The field {1} does not accept the \" character

 

TypeError
DescriptionThe field from the left compensation mapping does not accept double quote (") characters.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Field name
ActionCorrect the mapping expression.

 

600211<{0}>: Only numeric characters are allowed for the numeric field {1}

 

TypeError
DescriptionFor the numeric field from the right compensation mapping only numeric characters are allowed.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Name of the Balancing-Set
ActionCorrect the mapping expression.

 

600212<{0}>: The date field {1} does not contain a valid date

 

TypeError
DescriptionThe date specified for the date field in the right compensation mapping is not valid (for instance, there cannot be any "February, 30th”)
Parameter(s) {0} Logical name of the Balancing-Rule
ActionCorrect the mapping expression.

 

600213<{0}>: Only numeric characters are allowed for the date field {1}

 

TypeError
DescriptionThe date expression for the date field in the right compensation mapping must contain only numeric characters.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Field name
ActionCorrect the mapping expression.

 

600214<{0}>: The field {1} does not accept the \" character

 

TypeError
DescriptionThe field from the right compensation mapping does not accept double quote (") characters.
Parameter(s) {0} Logical name of the Balancing-Rule
{1} Field name
ActionCorrect the mapping expression.

 

600215<{0}>: The mapping value for the filter field must not be the same on left and right plate

 

TypeError
DescriptionWith or without the "Apply same mapping as left plate" option, the value of the FILTER field must not be the same on left and right plates.
Parameter(s) {0} Logical name of the Balancing-Rule
ActionCorrect the mapping expression for the FILTER.

 

600219<{0}> - Balancing Set <{1}>: The filter value specified on the {2} platter is incorrect: The length of the ''entire part'' must not be greater than the ''entire part definition''

 

TypeError
DescriptionThe specified filter value is incorrect for one or more of the following reasons: The number of the digits of the "entire part" is greater than the difference between the global definition and the decimal definition
Parameter(s) {0} The logical name of the Balancing-Rule
{1} The order of the Balancing-Set
{2} The name of the platter: left or right
ActionModify the filter value to comply this restriction

 

600500The configuration of the current server is incorrect

 

TypeError
DescriptionThe server associated with the current transaction executed by AccountingIntegrator Enabler Broadcast Agent is either not specified or incorrectly specified.
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
600501The operating directory path is not defined in the properties of the current AccountingIntegrator Enabler server

 

TypeError
DescriptionThe installation directory for the Broadcast environment associated with the AccountingIntegrator Enabler server is not specified. This information is mandatory for the AccountingIntegrator Enabler Broadcast Agent to execute a transaction.
ActionEnter a value for the Agent directory attribute of the AccountingIntegrator Enabler server.
 
600502The directory path [{0}] either does not exist or access is forbidden

 

TypeError
DescriptionThe {0} directory either does not exist or the AccountingIntegrator Enabler Broadcast Agent does not have sufficient rights to access it.
Parameter(s) {0} Incorrect directory path
ActionThis is a generic message.
Either the {0} directory does not exist or the AccountingIntegrator Enabler Broadcast Agent does not have sufficient rights to access the directory.
 
600503The server is incorrect

 

TypeError
DescriptionThe current transaction is not linked to a known AccountingIntegrator Enabler server: Processing halted.
ActionCheck that the AccountingIntegrator Enabler Broadcast Agent port is not being used by another Axway Composer Enabler to manage its server. If the problem persists, contact Axway Product Support.
 
600504The '{0}' operation failed!

 

TypeError
DescriptionThe current transaction {0} executed by the AccountingIntegrator Enabler Broadcast Agent failed.
Parameter(s) {0} Name of the current transaction executed by the Agent
ActionCheck the log file concerning the transaction executed by the Agent and contact Axway Product Support if the problem persists.
 
600506Error writing data to the mvt.mvt or ctx.mvt files in the directory: {0}

 

TypeError
DescriptionAn error occurred while creating the data file generated by the Agent
Parameter(s) {0} Directory path
ActionCheck the log file concerning the transaction executed by the Agent and contact Axway Product Support if the problem persists.
 
600507Error while deleting a directory: {0}

 

TypeError
DescriptionThe directory {0} cannot be deleted: either the directory is not empty or the Broadcast Agent does not have sufficient rights to delete this directory.
Parameter(s) {0} Directory path
ActionCheck the log file concerning the transaction executed by the Agent and contact Axway Product Support if the problem persists.
 
600508The current directory of data waiting for the execution engine [ *_{0}], does not exist in the directory: {1}

 

TypeError
DescriptionThe data with the ToBeCommitted status has been deleted in the execution environment. An external operation has corrupted the generated data in the Broadcast environment of the current server. You must remove from Production the entire configuration that has the ToBeCommitted status.
Parameter(s) {0} Transaction internal Identifier
{1} Directory path
ActionIn the Production Browser, select all the objects with the ToBeCommitted status for the current AccountingIntegrator Enabler server and run the Back to Design command on all the selected objects.
 
600509Purge the directory of all data waiting for the execution engine. You must retain the correct time-stamped directory associated with the object whose identifier is: {0}

 

TypeError
DescriptionA data coherence problem occurred while committing the data. A principal object, that is Input-Event, Processing-Context-In, or Processing-Context-Out object can have several associated configurations. You must manually restart the transaction.
Parameter(s) {0} Transaction internal identifier
ActionDelete the duplicated data directory [*_{0}] in the \ToBeCommited directory of the Broadcast environment associated with the AccountingIntegrator Enabler server.
 
600510{0}: object status incorrect

 

TypeError
Description{0} Object processed by the current transaction does not have the minimum status required.
Parameter(s) {0} Object name responsible for the error message
ActionIn Composer, check the status of the object {0}. If the status is incoherent send this object Back to Design, if necessary, then recheck it. If the problem persists, contact Axway Product Support.
 
600511AccountingIntegrator Enabler Broadcast Agent is not authorized to perform this operation

 

TypeError
DescriptionThis operation is not implemented for AccountingIntegrator Enabler Broadcast Agent.
 
600512The current AccountingIntegrator Enabler server is incorrect

 

TypeError
DescriptionThe server associated with the current transaction executed by AccountingIntegrator Enabler Broadcast Agent is either not specified or incorrectly specified.
ActionAnalyze the log file associated with the transaction executed by the Broadcast Agent and contact Axway Product Support if the problem persists.
 
600516Impossible to open or create the log file: {0}

 

TypeError
DescriptionAn error occurred while creating or opening the log file {0} associated with the current transaction.
Parameter(s) {0} Directory path of log file
ActionCheck the available system resources and make sure that if the file exists an external process has not locked it and AccountingIntegrator Enabler Broadcast Agent has sufficient rights to handle the file. If the problem persists, contact Axway Product Support.
 
600517Error while clearing the temporary working directory: {0}

 

TypeError
DescriptionThe working directory {0} used by AccountingIntegrator Enabler Broadcast Agent to generate data files, could not be cleared at the start or the end of the transaction: Either a file to delete is currently in use by another process or the Broadcast Agent does not have sufficient rights to delete the files.
Parameter(s) {0} Working directory path
ActionCheck the log file associated with the transaction executed by the Agent and contact Axway Product Support if the problem persists.
 
600518The current transaction in the AccountingIntegrator Enabler server [{0}] will be interrupted ...

 

TypeInformation
DescriptionA user in Composer has requested the interruption of the current transaction executed by the Agent.
Parameter(s) {0} Name of the AccountingIntegrator Enabler server
 
600519The current transaction in the AccountingIntegrator Enabler server [{0}] is already being interrupted by user [{1}] ...

 

TypeInformation
DescriptionA user in Composer has requested the interruption of the current transaction executed by the Agent. However the current transaction is already being interrupted.
Parameter(s) {0} Name of the AccountingIntegrator Enabler server
{1} User identifier
 
600520User [{1}] has interrupted the current transaction [{0}]!

 

TypeInformation
DescriptionUser {1} has interrupted the current transaction executed by AccountingIntegrator Enabler Broadcast Agent: the transaction is cancelled.
Parameter(s) {0} Name of the current transaction executed by the Agent
{1} User identifier
 
600521File with the specified pathname does not exist: [{0}]

 

TypeError
DescriptionThe file does not exist
Parameter(s) {0} Name of concerned file
ActionVerify that AccountingIntegrator Enabler is installed correctly.
 
600522Read access to the file [{0}] denied!

 

TypeError
DescriptionRead file access is denied, modification cannot be saved.
Parameter(s) {0} Name of concerned file
ActionVerify the file properties.
 
600523Internal error while opening or closing file [{0}]

 

TypeError
DescriptionThe file cannot be opened or closed during the operation.
Parameter(s) {0} Name of concerned file
ActionVerify that the file exists and repeat the action.
 
600524The size of file [{0}] exceeds the maximum size allowed [{1}]. The file content will be truncated.

 

TypeError
DescriptionThe file size is greater than maximum authorized size (1Mo).
Parameter(s) {0} Name of concerned file
{1} Maximum size allowed
 
600525The total number of bytes read is not equal to the total number of bytes available: the file content is incomplete.

 

TypeError
DescriptionAn error occurred while AccountingIntegrator Enabler agent was reading a file.
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
600526File with the specified pathname cannot be created or cannot be opened in write mode: [{0}]

 

TypeError
DescriptionWrite file access is denied, modification cannot be saved.
Parameter(s) {0} Name of concerned file
ActionVerify the file properties.
 
600527Write access to the file [{0}] denied!

 

TypeError
DescriptionWrite file access is denied, modification cannot be saved.
Parameter(s) {0} Name of concerned file
ActionVerify the file properties and repeat the modification.
 
600528The [{0}] path is not defined in the properties of the current AccountingIntegrator Enabler server

 

TypeError
DescriptionThe directory for AccountingIntegrator Enabler server is required.
Parameter(s) {0} Name of concerned directory
ActionEnter a value for the directory attribute on the Parameters tab for the AccountingIntegrator Enabler server.
 
600529Invalid file [{0}]

 

TypeError
DescriptionThe file format is incorrect.
Parameter(s) {0} Name of concerned file
ActionVerify the file and contact Axway Support.
 
600530Before you can execute a transaction on an AI Server, your objects must have at least the Checked status.

 

TypeError
DescriptionThe server status is not appropriate to execute this action.
ActionAccountingIntegrator Enabler server must be checked.
 
600531At most one Sentinel 'CommAdapter' can be declared for one AccountingIntegrator Enabler server

 

TypeError
DescriptionAn AccountingIntegrator Enabler server requires only one Sentinel CommAdapter
ActionVerify the CommAdapter number.
 
600532At most one TCP/IP 'CommNetwork' can be used by a Broadcast Agent to update a remote AccountingIntegrator Enabler server

 

TypeError
DescriptionAn AccountingIntegrator Enabler server requires only one TCP/IP CommNetwork
ActionVerify the TCP/IP CommNetwork number.
 
600533A Broadcast Agent requires a TCP/IP 'CommNetwork' to update & To update a remote AccountingIntegrator Enabler server, Broadcast Agent needs using a TCP/IP 'CommNetwork'

 

TypeError
DescriptionA TCP/IP CommNetwork is required to update a remote AccountingIntegrator Enabler server.
ActionVerify the TCP/IP CommeNetwork number.
 
600600Data type is mandatory for the Variable

 

TypeError
DescriptionYou must specify the data type associated with the current Variable object.
ActionSelect a data type in the attributes of the current Variable object.
 
600601The definition of the Variable must be between {1} and {2} characters

 

TypeError
DescriptionThe definition of the current Variable must be between {1} and {2} for the selected data type.
Parameter(s) {1} Minimum authorized definition
{2} Maximum authorized definition
ActionModify the definition of the Variable to comply with this restriction.
 
600602The initialization value of the Variable must be specified

 

TypeError
DescriptionYou must specify the Initial value attribute for all data types other than Alphanumeric (A)
ActionModify the default value value of the Variable to comply with this restriction.
 
600603The initialization value of the Variable is incorrect: the definition of the value must be between {1} and {2} characters

 

TypeError
DescriptionThe specified initialization value for the current Variable current is incorrect. The character string definition entered must be between {1} and {2}.
Parameter(s) {1} Minimum authorized definition
{2} Maximum authorized definition
ActionModify the initialization value of the Variable to comply with this restriction.
 
600604The initialization value of the Variable is incorrect: Unauthorized character '{1}'

 

TypeError
DescriptionThe specified initialization value for the current Variable is incorrect. The character {1} is not authorized: The only characters authorized in Alphanumeric data types are UNICODE (except '\t', '\f', '\r',)
Parameter(s) {1} Character causing the exception
ActionReplace the unauthorized character in the character string with a valid character.
 
600605<{0}>: The decimal definition of the Variable must be between {1} and {2} characters

 

TypeError
DescriptionFor the Variables of decimal type the decimal definition is mandatory and its value must be greater than 0 and less than or equal to 9
Parameter(s) {0} The logical name of the Variable
{1} The minimum authorized decimal definition value
{2} The maximum authorized decimal definition value
ActionModify the decimal definition to comply with this restriction

 

600700The version number '{1}' must be between {2} and {3}

 

TypeError
DescriptionThe version identifier of the versioned object must be a number between 1 and 999 (inclusive).
Parameter(s) {1} Value of the version number
{2} Minimum authorized value
{3} Maximum authorized value
ActionModify the object version number to comply with this restriction.
 
600701The date value '{1}' must be between {2} and {3}

 

TypeError
DescriptionThe date is incorrect. The date entered {1} must be between {2} and {3}.
Parameter(s) {1} Date value entered
{2} Minimum authorized value
{3} Maximum authorized value
ActionModify the date to comply with this restriction.
 
600800The selection of a Financial-Procedure is mandatory

 

TypeError
DescriptionThe Financial-Procedure attribute of the Financial-Event object must be specified.
ActionOpen the Financial-Event object and select a Financial-Procedure object.
 
600850Processing halted: This case is not processed correctly

 

TypeError
DescriptionThis message is generated after a data coherence test, which prevents saving the current transaction until all the objects affected have been processed correctly.
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
600852Processing halted: A version of the '{0}' Rule already exists in the target directory tree. All the versions of a Rule must be grouped in the same folder.

 

TypeError
DescriptionThe target directory tree contains a version of the Rule you want to move, but it is not in the target folder. In AccountingIntegrator Enabler all the versions of a Rule must be grouped in the same folder under a given root folder. If this convention is not respected, the current transaction is halted.
Parameter(s) {0} Rule name
ActionIt is recommended that you either:
First move the version(s) of the Rule you want to move to the folder where other versions of this Rule are already located, that is, in the target directory tree.
Move the versions of the Rule in the target directory tree to the target folder.
 
600854Processing halted: Object {0} '{1}' cannot be moved. An object in Production cannot be moved to a different directory tree.

 

TypeError
DescriptionIn AccountingIntegrator Enabler, the transformation execution engine only uses data from the unique root folder. This root folder ensures that the AccountingIntegrator Enabler object names are unique. Therefore, an object in production must always be in the root folder dedicated to the execution engine on which it was sent to production.
Parameter(s) {0} Object type
{1} Object name
ActionUse the Copy/Paste function instead of the Cut function.
 
600856Processing halted: Object {0} '{1}' cannot be moved. The target folder {2} is not in the same entity as the source folder {3}.

 

TypeError
DescriptionYou can only move objects from one entity to another.
Parameter(s) {0} Object type
{1} Object name
{2} Name of the target folder
{3} Name of the source folder
ActionUse the Copy/Paste function instead of the Cut function.
 
600857Processing halted: Object {0} '{1}' cannot be moved. An object with the same type and name already exists in the target namespace and the current object is not modifiable.

 

TypeError
DescriptionIf you change the root folder this has an impact on the object namespace. Therefore in the new namespace, you must verify the uniqueness of the names of the objects you want to move. If a conflict occurs, that is, an object of the same type and with the same name already exists, the object name is modified and you must Check the object again.
You can therefore only modify the names of objects that are In Design. If a conflict occurs when moving an object and the object is not In Design, the system does not allow you to move the object.
Parameter(s) {0} Object type
{1} Object name
ActionUse the Copy/Paste function instead of the Cut function.
 
600858Processing halted: {0}

 

TypeError
DescriptionThe current transaction has been halted following the exception {0}
Parameter(s) {0} Internal message error
ActionDepending on the exception {0}, it is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
601000Expression analysis is correct

 

TypeInformation
DescriptionNo errors or warnings encountered when analyzing the expression.
 
601500File not found ...

 

TypeError
DescriptionThe data file to import does not exist.
ActionCheck that the file exists.
 
601501An error occurred while reading the file...

 

TypeError
DescriptionThe specified file is unreadable.
ActionCheck the data integrity in the specified file.
 
601502An unknown error occurred: {0}

 

TypeError
DescriptionAn unknown error occurred.
Parameter(s) {0} Internal message error
ActionDepending on the exception {0}, it is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
601505An unknown error occurred

 

TypeError
DescriptionAn unknown error occurred.
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
601506The data type '{0}' in a Business-Document leaf element to import is incorrect: The Alphanumeric data type is specified by default

 

TypeInformation
DescriptionWhen importing a Business-Document, if the data type of one of the Business-Document leaf elements is incorrect, the Alphanumeric data type (A) will be used by default.
Parameter(s) {0} Data type read in the import file
ActionThis is an information message. After you import the Business-Document, verify all the data types used in the Business-Document leaf elements.
 
601507An error occurred while saving Business-Document '{0}': {1}

 

TypeError
DescriptionAn unknown error occurred saving imported data
Parameter(s) {0} Name of the Business-Document being created
{1} Internal message error
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
601508An error occurred while saving the Mapping-Template '{0}'

 

TypeError
DescriptionAn unknown error occurred while saving imported data.
Parameter(s) {0} Name of the Mapping-Template being created
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
601509An error occurred while processing the data '{0}'

 

TypeError
DescriptionAn unknown error occurred while processing line {0} in the import data file.
Parameter(s) {0} Data being processed
ActionAnalyze the imported line {0} and make the necessary corrections.
 
601510An error occurred while loading the Business-Document leaf elements: {0}

 

TypeError
DescriptionAn unknown error occurred loading data from the AccountingIntegrator Enabler reference table.
Parameter(s) {0} Internal message error
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
601512An error occurred while saving Business-Document leaf element '{0}'

 

TypeError
DescriptionAn unknown error occurred saving the imported data.
Parameter(s) {0} Name of Business-Document leaf element being created
ActionIt is recommended that you identify how to reproduce this error and then contact Axway Product Support.
 
601513Ignored Business-Document leaf element '{0}' because its definition exceeds {1} characters

 

TypeInformation
DescriptionYou cannot import a Business-Document leaf element whose definition is greater than the 9999 limit. It is technically impossible to create a leaf element with a definition that exceeds this limit.
Parameter(s) {0} Name of Business-Document leaf element being created
{1} Maximum authorized Business-Document leaf element definition
ActionAfter importing the file, verify the data and either manually create the information not imported or modify the import file and restart the import.
 
601514Ignored Business-Document '{0}' because its definition exceeds {1} characters

 

TypeInformation
DescriptionThe total definition of imported Business-Document leaf elements is greater than the 9999 limit. It is technically impossible to create a Business-Document with a definition that exceeds this limit.
Parameter(s) {0} Name of the Business-Document being created
{1} Maximum authorized Business-Document definition
ActionAfter importing the file, verify the data and either manually create the information not imported or modify the import file and restart the import.
 
601515Stopped generating leaf elements in the 'OCCURS' clause <{0}> in the Business-Document '{1}' because the Business-Document definition exceeds {2} characters

 

TypeInformation
DescriptionThe total definition of Business-Document leaf elements generated after processing the OCCURS clause, and associated with other imported leaf elements exceeds the 9999 limit. It is technically impossible to create a Business-Document with a definition that exceeds this limit.
Parameter(s) {0} Name of Business-Document leaf element associated with the 'OCCURS' clause
{1} Name of the Business-Document being created
{2} Maximum authorized Business-Document definition
ActionAfter importing the file, verify the data and either manually create the information not imported or modify the import file and restart the import.
 
601600File '{0}' missing

 

TypeError
DescriptionThe file {0}, used to dynamically load the AccountingIntegrator Enabler DML functions into the DML Browser, either does not exist or the data in this file is incorrect.
Parameter(s) {0} File path of data used.
ActionIt is recommended that you contact Axway Product Support to run diagnostic tests on the Composer client environment.
 
602000No Transformation-Environment / Processing-Context-Out pair specified

 

TypeError
DescriptionTo activate a Transformation-Domain when the AccountingIntegrator Enabler execution engine executes a session, you must associate the Transformation-Domain with the Transformation-Environment run by the execution engine, by default this is BATCH. Therefore, you must specify the Transformation-Environment name in the properties of the current Transformation-Domain object; otherwise none of the Input-Event Phases that reference this Transformation-Domain object will be processed by an execution engine session.
ActionSpecify a Transformation-Environment, for example BATCH, in the properties of the current Transformation-Domain.
 
602001The default Transformation-Environment 'BATCH' is not specified

 

TypeError
DescriptionEach Transformation-Domain must specify the default Transformation-Environment BATCH.
ActionIn normal product use, this default Transformation-Environment is always specified and cannot be deleted. There is therefore a data integrity problem in the AccountingIntegrator Enabler reference table. It is recommended that you contact Axway Product Support to run diagnostic tests on the AccountingIntegrator Enabler reference table.
 
602002Transformation-Environment is not specified

 

TypeError
DescriptionThe name of at least one Transformation-Environment is not specified in the Transformation-Environment / Processing-Context-Out pair in the current Transformation-Domain object.
ActionEnter a character string for the name of the Transformation-Environment for each Transformation-Environment / Processing-Context-Out pair.
 
602003Duplicate Transformation-Environment / Processing-Context-Out pair specified

 

TypeError
DescriptionYou cannot specify duplicate Transformation-Environment/ Processing-Context-Out in a given Transformation-Domain; otherwise the AccountingIntegrator Enabler execution engine session ends with an error.
ActionDelete the duplicated Transformation-Environment / Processing-Context-Out pairs.
 
602004The Transformation-Environment' {1} ' must be unique

 

TypeError
DescriptionYou cannot specify the same Transformation-Environment twice in a given Transformation-Domain: once with the associated Processing-Context-Out and a second time without:
In the first case, you can apply the Input-Event redirection function to the Input-Events responsible for the Output-Event processed by the specified Processing-Context-Out.
In the second case, the Routing function is not applicable. This is an unauthorized configuration because the Transformation-Domain configuration is contradictory.
Parameter(s) {1} Name of duplicated Transformation-Environment
ActionUpdate the Transformation-Domain configuration to respect this convention.
 
602500The Java Virtual Machine is out of memory

 

TypeError
DescriptionUnable to continue running current processes correctly due to lack of system resources or available memory relative to the Java Virtual Machine (JVM) configuration used. That is, maximum authorized memory memory used < 5MB
ActionIt is recommended that you first check the physical amount of RAM available on the client machine:
If the memory is insufficient, upgrade the memory.
If the memory is sufficient, increase the maximum allocated memory for the JVM used by the client machine. To do this, modify the -Xms parameter in the launch scripts for the Composer, Server or Broadcast Agent depending on the canceled operation.
 
602502Find operation halted: {0}

 

TypeError
DescriptionAn internal error occurred during the Find operation.
Parameter(s) {0} Internal message error
ActionCheck the error message {0} and contact Axway Product Support if the problem persists.
 
602503Replace operation halted

 

TypeError
DescriptionAn internal error occurred during the Replace operation.
ActionCheck the report associated with the Replace transation and contact Axway Product Support if the problem persists.
 
602550Processing halted: an affected object is already locked by another process. Refer to the log pane for more details

 

TypeError
DescriptionA running process has locked an object affected by the current transaction. This object is potentially being modified. As the current transaction cannot use this object, the current transaction is halted.
ActionA message in the log pane indicates the locked object and the type of transaction causing the lock. It is recommended that you either wait for this transaction to finish or contact the AccountingIntegrator Enabler administrator to remove the lock. The administrator can only remove the lock if it is a residual lock.
 
602551Processing halted: an affected object is already locked by another process

 

TypeError
DescriptionA running process has locked an object affected by the current transaction. This object is potentially being modified. As the current transaction cannot use this object, the current transaction is halted.
ActionA message in the log pane indicates the locked object and the type of transaction causing the lock. It is recommended that you either wait for this transaction to finish or contact the AccountingIntegrator Enabler administrator to remove the lock. The administrator can only remove the lock if it is a residual lock.
 
602553Object {1} <{2}> was modified on <{3}> by user <{4}>

 

TypeInformation
DescriptionA child object linked to the current object has been modified since the current object was opened: intrinsic properties of the child object (name, label, status, signature) have been updated. Updating a child object can lead to modifications in the current object and thus change its status.
Parameter(s) {1} Type of modified object
{2} Name of modified object
{3} Date of the latest modification to the modified object
{4} Identifier of user responsible for the latest modification
ActionThis is an information message. Visually check the contents of the current object before saving the latest modifications to it.
 
602554Object {0} <{1}> has been removed from the selection

 

TypeInformation
DescriptionAfter reloading the current objects list: The selected object has been removed from the selection following its deletion by an external operation.
Parameter(s) {0} Object type
{1} Object name
ActionThis is an information message. Visually check the contents of the current object before saving the latest modifications to it.
 
602555At least one version of object {1} <{2}> has been modified, deleted or created

 

TypeInformation
DescriptionIn Rule {2} selected in the current Input-Event type, a version of this Rule has been modified, deleted or created since you opened the Input-Event.
Parameter(s) {1} Type of modified object
{2} Name of modified object
ActionThis is an information message. Visually check the contents of the current object before saving the latest modifications to it.
 
602557Object {1} <{2}> was removed from the selection

 

TypeInformation
DescriptionAfter reloading the current objects list: The selected object has been removed from the selection following its deletion by an external operation.
Parameter(s) {1} Object type
{2} Object name
ActionThis is an information message. Visually check the contents of the current object before saving the latest modifications to it.
 
602600Terminus of this Channel must have the same host

 

TypeError
DescriptionThe Channel has Terminus in different physical machines.
ActionVerify Channel Terminus.
 
602650A mandatory field on the Direction Tab value of Direction tab is missing for the connection point <{1}>.

 

TypeError
DescriptionA mandatory CommPoint field has not been specified.
Parameter(s) {1} Required parameter
ActionVerify the CommPoint values.
 
602675Invalid parameter setting for Sentinel Terminus. Port number or logical Host name for Sentinel 'CommAdapter' type ''{1}'' is undefined

 

TypeError
DescriptionSentinel Terminus parameters are incorrect: either the Port or the Host name is missing.
Parameter(s) {1} Sentinel CommAdapter type
ActionVerify the Sentinel CommAdapter parameters.
 
602676Invalid parameter setting for AccountingIntegrator Enabler Terminus. Values of AccountingIntegrator Enabler ''CommAdapter'' of ''{1}'' type are undefined

 

TypeError
DescriptionAccountingIntegrator Enabler Terminus is incorrect.
Parameter(s) {1} AccountingIntegrator Enabler CommAdapter type
ActionVerify the AccountingIntegrator Enabler CommAdapter parameters.
 
602677Invalid parameter setting for Sentinel Terminus. The type {1} of the selected CommAdapter is invalid

 

TypeError
DescriptionSentinel Terminus parameters are incorrect
Parameter(s) {1} Sentinel CommAdapter type
ActionVerify the Sentinel CommAdapter parameters (QLT-XML or Auto type).
 
602700The file path is mandatory

 

TypeError
DescriptionThe CommPoint file path is mandatory.
ActionVerify the CommPoint parameters.
 
602701The file name is mandatory

 

TypeError
DescriptionThe CommPoint file name is mandatory
ActionVerify the CommPoint parameters.
 
602702The user name is mandatory

 

TypeError
DescriptionThe CommPoint user name is mandatory.
ActionVerify the CommPoint parameters.
 
602703The user password is mandatory

 

TypeError
DescriptionThe CommPoint user password is mandatory.
ActionVerify the CommPoint parameters.
 
602800Business-Document <{1}> is not compatible with {2}

 

TypeError
DescriptionA Sentinel Business-Document has been selected for a Mapping Template. However, he Businesss-Document does not comply with AccountingIntegrator Enabler standards (checked status / only one segment / name with only uppercase).
Parameter(s) {1} {2} Business-Document name
Business-Document type
ActionChange the Business-Document in order to be able to check the MappingTemplate.
 
602900Output-Event <{1}>: Business-Document <{2}> is not compatible with {3}

 

TypeError
DescriptionA Sentinel Business-Document has been selected for an Output-Event. However, he Businesss-Document does not comply with AccountingIntegrator Enabler standards (checked status / only one segment / name with only uppercase).
Parameter(s) {1} {2} {3} Output-Event name
Business-Document name
Business-Document type
ActionSelect another Business-Document to validate the Output-Event.
 
603000Unexpected error during Finance XML Export: {0}

 

TypeError
DescriptionAn error occurred during XML export.
Parameter(s) {0} Error details
ActionIdentify the scenario that produced this error and contact Axway support.
 
603001Error whilst mapping the object to XML : {0}

 

TypeError
DescriptionAn error occurred while transforming object to XML file.
Parameter(s) {0} Error details
ActionIdentify the scenario that produced this error and contact Axway support.
 
603002Error whilst writing the export file to disk: {0}

 

TypeError
DescriptionAn error occurred while writing XML export result file.
Parameter(s) {0} Error details
ActionIdentify the scenario that produced this error and contact Axway Support.
 
603003Finance XML export operation halted by the user

 

TypeWarning
DescriptionThe XML export has been interrupted by the user.
 
603004Finance XML export finished. File saved to {0}

 

TypeInformation
DescriptionThe XML export is finished and the file {0} has been created.
Parameter(s) {0} File name
 
603005Finance XML export: the status of <{0}> - <{1}> is <ToBeChecked>

 

TypeError
DescriptionThe object {0} with type {1} has not got the appropriate status to be exported.
Parameter(s) {0} {1} Object name
Object type
ActionCheck the object before exporting it.
 
603006Finance XML Export aborted: Object array to be exported is empty or null

 

TypeError
DescriptionThere are no objects to export.
ActionSelect at least one object to export.
 
603007{0} Error(s): the Finance XML Export was aborted. Refer to the log pane for more details.

 

TypeError
DescriptionErrors {0} occurred during XML export
Parameter(s) {0} Error number
ActionCheck the object before exporting it.
 
603008Finance XML export: insufficient authorizations for reading the object <{0}> - <{1}>

 

TypeError
DescriptionThe current user has not got the appropriate rights to display the Object {0} of type {1}.
Parameter(s) {0} {1} Object name
Object type
ActionRequest the appropriate rights from your administrator.
 
603009Incorrect file name or file is read-only

 

TypeError
DescriptionThe export file cannot be written to successfully.
ActionVerify the export file properties (read/write).
 
603010Error while writing the file <{0}> : {1}

 

TypeError
DescriptionA writing error {1} on file {0} occurred during XML export.
Parameter(s) {0} {1} File name
Error detail
ActionVerify that file can be accessed. and that the disk is not full. If the error reoccurs, identify the scenario that produced the error and contact Axway Support.
 
603011Report file saved to {0}

 

TypeInformation
DescriptionThe XML report file {0} is saved.
 
603012Finance XML export: more than {0} errors were encountered. Finance XML Export was aborted.

 

TypeError
DescriptionThe number of errors that occurred exceeded the maximum number allowed {0}.
Parameter(s) {0} Maximal number of errors reached
ActionIdentify the scenario that produced this error and contact Axway Support.
 
603013Finance XML export started

 

TypeInformation
DescriptionXML export start.
 
609001All the activation dates must be within the validity period dates

 

TypeError
DescriptionThe activation date does not match the rules validity.
ActionCheck all implicated rules and correct the activation date.
 
609002An activation date defined for a specific server and a rule version must not be equal to the beginning validity date of another version of the same rule

 

TypeError
DescriptionThe activation date should be different from the rule validity period start date.
ActionCheck all implicated rules and correct the activation date.
 
609003There is another version of the rule with the same activation date for this server

 

TypeError
DescriptionTwo versions of the same rule should not have the same start date for the validity period represented here by the activation date.
ActionCheck all implicated rules and correct the activation date.
 
609004The start date of the validity period must not be equal to an activation date of another version of the same rule

 

TypeError
DescriptionTwo rule versions should have two different validity period start date represents here by the activation date.
ActionCheck all implicated rules and correct the activation date.
 
609100Error while retrieving rule description

 

TypeError
DescriptionA problem occurred while retrieving the rule description.
ActionRedo the action.
 
609110<{0}>: The initialization value of the Variable is incorrect: the number of decimal digits must not be greater than the decimal definition

 

TypeError
DescriptionThe initialization value of the Variable is incorrect because the number of the decimal digits is greater than its decimal definition
Parameter(s) {0} The logical name of the Variable
ActionModify the initialization value to comply with this restriction

 

609111<{0}>: The initialization value of the Variable is incorrect: the length of the integral part must not be greater than the integral part definition

 

TypeError
DescriptionThe initialization value of the Variable is incorrect because the number of digits of the integral part is greater than the difference between the global definition and the decimal definition
Parameter(s) {0} The logical name of the Variable
ActionModify the initialization value to comply with this restriction

 

610001The <{0}> Tracking Object leaf name ''{1}'' exceeds 10 characters

 

TypeError
DescriptionA leaf element name must have the length less than 10 characters.
Parameter(s) {0} {1} Logical name of the tracking object
Leaf name
ActionCorrect the leaf element name.
 
610002The <{0}> Tracking Object leaf name ''{1}'' must be uppercase

 

TypeError
DescriptionA leaf element name must have uppercase characters.
Parameter(s) {0} {1} Logical name of the tracking object
Leaf name
ActionCorrect the leaf element name.
 
610003The <{0}> Tracking Object public name cannot be empty

 

TypeError
DescriptionThe public name of a tracking object must not be empty.
Parameter(s) {0} Logical name of the tracking object
ActionCorrect the tracking object.
 
610004The <{0}> Tracking Object public name ''{1}'' must contain at most 3 characters

 

TypeError
DescriptionThe public name length of a tracking object must not be greater than 3 characters
Parameter(s) {0} {1} Logical name of the tracking object
Public name
ActionCorrect the tracking object.
 
610101Invalid value <{0}> for <{1}> option

 

TypeError
DescriptionAn error occurred while setting the value for the XRDJ Package option.
Parameter(s) {0} {1} Option value
Option name
ActionRedo the action.
 
610102Invalid option <{0}>

 

TypeError
DescriptionAn error occurred while setting the XRDJ Package option.
Parameter(s) {0} Option name
ActionRedo the action.
 
600061The current working folder is of type multibyte. Argument length cannot exceed ''{1}'' characters

 

TypeError
DescriptionDue to a technical constraint on the MVS platform with the UTF-16 management, the "Table" objects cannot support more than 110 characters in the argument.
Parameter(s) {1} Maximum length of the table argument columns in case of UTF16 management
ActionCorrect the table object.
 
600127The Business document contains packed data but current working Folder is an UTF-16 one

 

TypeError
DescriptionA Business-Document that contains packed data is not supported in UTF16 folder.
ActionCorrect the Business-Document.

 

Related Links