# HRF res\messages_descriptions.properties
# 

# This file contains messages descriptions arranged in sections according to HRF APIs
# These descriptions are translated.
# Adding a new message requires also update of message.xsjslib file by the new ID

#############################
# common
#############################
# 10 - 999 - common messages

# YMSG: return from resource activation, in case of a resource does not exist in repository
10=F6AxW8FTNgIczuLL2GabZg_Resource activation is not possible; resource does not exist.
# YMSG: return from resource activation, in case of a resource suffix is not one of HRF resources
11=cADW57n9PQf2q1ESU8ROfQ_Resource activation is not possible; suffix '{0}' is not supported
# YMSG: return from resource activation, in case of a resource package does not exist in repository
12=PFjy5Vmg49dCoP5fT0gwAQ_Resource activation is not possible; package '{0}' does not exist
# YMSG: return from runtime plug in, in case of invalid attribute
13=hfQFE7p3HbMl+3gepd0ISw_Resource activation is not possible; attribute  '{0}'  is not contained in schema
# YMSG: return from  runtime plug in, in case of invalid attribute
14=6YUSVqFEX4QIIUwyQ7+xnw_Resource activation is not possible; mandatory attribute value '{0}' is missing
# YMSG: return from  runtime plug in, in case none of a predefined set of fields is specified
15=401cIryjMvDudLfZAF1drA_Resource activation is not possible; at least one of the optional attributes {0} is missing
# YMSG: return from  runtime plug in, in case of invalid field (e.g vocabulary doesn't exist)
16=hhgppeMacstM6RcPblIKuw_Resource activation is not possible; value of attribute {0} is not valid
# YMSG: return from runtime plug in, in case of inconsistent fields combination(e.g. vocabulary and output names doesn't match)
17=JxNpV/JmcTsFWnOXWSC78Q_Resource activation is not possible; combination of {0} and {1} is not valid
# YMSG: return from  runtime plug in, in case of invalid resource id (e.g. package / file name is missing)
23=hBCz0fKwe6COPSFE4Po+5g_Resource activation is not possible; resource does not exist
# YMSG: return from  runtime plug in, in case of error from REL validation
24=ai/HgxJ1hmaP9XjAuVe4MA_Error in field {0}\: {1}
# YMSG: return from  REST service, in case of http request contains non supported method
25=FipGnG4wfRF5wlef5SMt2Q_Method failed; method \#{0} is not supported
# YMSG:  technical error from platform
26=LiwY1viyUsH6OzufYI0xZw_Technical error occurred - {0}
# YMSG: return from resource activation, in case of a resource does not exist in repository
27=saGIfd+b/F34a1sZdzediQ_Resource does not exist.

# 100 - 200 - Authorization

# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
100=ocP5+ixaC7Xi69E31g6/zg_You are not authorized to perform this action.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
101=HHZqwMevuyd5tIh3NWnWZw_You are not authorized to update rules.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
102=wWhEwxNXyR4d3yodtBbatA_You are not authorized to delete rules.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
103=Q8JQgSY8E+8gSRREDsdcDA_You are not authorized to create rules.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
104=trYsXfZdSWSTLF1Q7pGy/A_You are not authorized to read rules.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
105=+mbUc9R3tzrCWKRs4sI1Eg_You are not authorized to update rule services
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
106=d7aIigPVtU1j2rD16BDUrA_You are not authorized to delete rule services.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
107=Kjfai9xWcNJCd4t5wzmbFg_You are not authorized to create rule services.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
108=3PdDMEC0e9ShVjt54xOV4g_You are not authorized to read rule services.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
109=DTdT/N9QDOahi/86hOeH1Q_You are not authorized to run rule services.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
110=bDAS4rptLCQ/HsO+KQh0VA_You are not authorized to update vocabularies.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
111=0QEVq3v0SvHm+8bsOFjFLw_You are not authorized to delete vocabularies.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
112=O9smzsoCKFYOOiuNeH7fHA_You are not authorized to create vocabularies.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
113=1jYzclO6i48AoaVYfBxDng_You are not authorized to read vocabularies.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
114=2d85ksqlJ7salqoEF5Rx5g_You are not authorized to update rule templates.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
115=ffEK+1zbD0kUZgcYCJ0vpA_You are not authorized to delete rule templates.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
116=erW2deB+XLb0vH7bn2TdLA_You are not authorized to create rule templates.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
117=e2d+c6XAXdPS062PYfrDgQ_You are not authorized to read rule templates.
# XMSG: return from Request Handler, in case of unassigned privilege to perform an action 
118=v17lo2wdC9NfsLqrGJt1SA_You are not authorized to create or update rule services.
# XMSG: in case of technical user either does not exist or is not configured correctly
119=xWtk/tsdvNIg0FViLj0jeg_Technical user for SAP HANA rules framework either does not exist or is not configured correctly. {0}

#############################
# API: Validate
#############################
# 1100 - 1199 - REL validation messages

# YMSG: return from REL, the beginning of any REL validation error - in case of a wrong statement 
1100=N6faxL8diWCKdUDfYO1EFQ_Error in expression;
# YMSG: return from REL parser, in case of a wrong entry (syntax) and maximum 3 option are optional instead 
1101=YoJONVDrDXyuDzQS+mriVg_Error in expression; enter {0} instead of {1}
# YMSG: return from REL parser, in case of a wrong entry (syntax) and more than 3 option are optional instead  
1102=wgAMhHCOarUOb9KF0fNq+Q_Error in expression; {0} is not a valid entry
# YMSG: return from REL parser, in case of a wrong input
1103=/89tpiWFlIRNUqhKAul2FQ_Error in expression; remove {0}
# YMSG: return from REL model, in case of collection OM when single value in needed
1104=os3BwY+Az2qCsJTmtgR0NQ_Error in expression; {0} is a list of values. Change to an expression representing a single value
# YMSG: return from REL model, in case of a wrong input
1105=+i5qUwjykBzGsueEUzipVA_Error in expression; enter valid operand instead of {0}
# YMSG: return from REL parser, in case of an incomplete expression
1106=T2jMYeqA0kSX/UF7mvDKFQ_Incomplete expression;
# YMSG: return from REL lexer, in case of missing token at EOF
1107=TsEF+lF7REZT8g0pv133hQ_Error in expression; enter {0} at the end of the expression
# YMSG: return from REL lexer, in case of wrong token
1108=I4oNV6gMLrPE/Eh737bgkg_Error in expression; enter '{0}' instead of '{1}'
# YMSG: return from REL entity, in case of missing current
1109=V3MkVWXP3chql/LeqoW2ow_Error in expression; 'current' is missing in the 'where' clause
# YMSG: return from REL entity, in case of redundant 'current'
1110=mm6/F1ZYx2Mu7aoPN3Zpsw_Error in expression; redundant 'current'; remove one 'current'
# YMSG: return from REL vocabulary utils, in case of invalid root object
1111=4w9B4idHFt99WgRoNei3Cw_Invalid root object
# YMSG: return from REL vocabulary utils, in case of invalid association
1112=PKl2LvCCvetlZ6Y2jZ3wAg_Invalid association
# YMSG: return from REL vocabulary utils, in case of invalid association or attribute
1113=yP/ik//asOoip4iDIHuD1w_Invalid association or attribute
# YMSG: return from REL vocabulary utils, in case of root is simple attribute
1114=WfBTHO3RCLDLFT3CDS+qYA_Root cannot be a simple attribute
# YMSG: return from REL vocabulary utils, in case of attribute not found
1115=jvay7gZQJxm5yzTmGP158w_Incomplete path, attribute not found
# YMSG: return from REL entity, in case of using 'current' outside of 'where'
1116=fE0UW+qhXUU5XnosBRapZw_Error in expression; the keyword 'current' can only be used within a 'where' clause.
# YMSG: return from REL entity, in case of using 'current' incorrectly with arithmetic
1117=r5GptO63SL9lB7SfPHkxdQ_Error in expression; the keyword 'current' must be applied to all operands on one side of the comparative operator in the 'where' clause.
# YMSG: return from REL parser utils, in case of using value that doen't exist in closed value list
1118=y4wJ3lGnt1RdDS2rm2fodg_Error in expression. '{0}' is not a valid value from value list '{1}'.
# YMSG: return from REL parser utils, in case of using value that doen't exist in closed value list
1119=ujQzjE6K+Vm+JtbcWs2zAg_Error in expression. The '{0}' operator cannot be used with a value-list attribute ('{1}').
# YMSG: return from REL parser utils, in case of using value that doen't exist in closed value list
1120=K/YnSChfx9S8a2U5FKlIew_Error in expression. The keyword 'all' cannot follow an operand that contains the keyword 'current'.
# YMSG: return from REL parser utils, in case of using value that doen't exist in closed value list
1121=nEPiDaFYDyjsyg0+eIObpA_Error in expression. The keyword 'all' cannot be used more than once in the same statement.
# YMSG: return from REL parser utils, in case of using 2 differemt root objects 
1122=Bd0ERhp9CQieHS/V8eBSvw_Error in expression. Expression contains more than one root data object\: {0}, {1}.
# YMSG: return from REL parser, in case of a wrong entry (syntax date) 
1123=Gy78tNNJwH0tkXD+VL6v+A_Error in expression. Enter a {0} using the application format {1} instead of {2}.
# YMSG: return from REL parser, in case of a wrong locale settings
1124=nOWDg4B/QpMsRxicGwZ4sA_{0} {1} is not supported.
# YMSG: return from REL parser utils, in case of using value that doen't exist in external value list
1125=JPiDqFy79BMhC7INctdqBg_Error in expression. Enter a valid value from value help instead of '{0}'.
# YMSG: return from REL parser, in case of a two options of wrong formats
1126=/BHa5zXe4Bhlna5QGKK/aA_Error in expression {0}. To enter a {1}, use the format {2}. To enter a {3}, use the format {4}.
# YMSG: return from REL parser, in case of string without single quotes
1127=yi3oymEESKLPHPwon/HLUw_Error in expression; enter string in single quotes\: {0} instead of {1}.
# 1200 - 1999 - validation messages

#############################
# API : resource CRUD
#############################
# 2100 - 2299 - vocabulary messages

# YMSG: return from vocabulary runtime plug in, in case of error in expression
2100=MVXvpSh1Re1fHr+DCZDNZg_In '{0}'- Error in parsing expression\: '{1}', '{2}'
# YMSG: return from vocabulary runtime plug in, in case of error in rule
2101=C/+wn3cGpo/T0gyYqboPzg_In '{0}' - problem in rule\: '{1}', '{2}'
# YMSG: return from vocabulary runtime plug in, in case the parameter type already exists
2102=FlvjjaNb4ZFXl/7fHax1wQ_In '{0}' \: '{1}', name\: '{2}' already exists
# YMSG: return from vocabulary runtime plug in, in case parameter name isn't valid
2103=xitsgwrhVoJGqrhqqdo14Q_In '{0}' \: '{1}', Invalid name\: '{2}'
# YMSG: return from vocabulary runtime plug in, in case one of action/output names aren't valid
2104=XmZyeoL57DEH1kd4/EZNuw_In '{0}', Invalid name\: '{1}'
# YMSG: return from vocabulary runtime plug in, in case name already exists
2105=yxOwjTlKAYzlP2RmKWQf3Q_Name '{0}' is defined more than once in '{1}'.
# YMSG : return from vocabulary runtime plug in, in case the output has no parameters
2106=GnWB4q+aY6PuM8EdyuFcaQ_Missing parameters in output
# YMSG: return from vocabulary runtime plug in, in case one of the attributes has an invalid name
2107=NPCtDv21P3VYpWAduVtvOA_Invalid attribute name '{0}'
# YMSG: return from vocabulary runtime plug in, in case object name of declare more than once
2108=QqNjcXzioNT4aYVGLx5F1A_'{0}'\: '{1}' already exists. 
# YMSG: return from vocabulary runtime plug in, in case attribute name of declare more than once
2109=xfIkaP0sUN/zwWnVdRk1/g_Attribute already exists\: object\= '{0}' attribute\= '{1}'
# YMSG: return from vocabulary runtime plug in, in case attribute name of declare more than once
2110=BkUwfE11DVWogUemI0o0DA_Association already exists\: object\= '{0}' association\= '{1}'
# YMSG : return from vocabulary runtime plug in, in case the source table isn't exists
2111=8zyAjXJ9uIuhu0xtFgoUYQ_Invalid source table '{0}'
# YMSG : return from vocabulary runtime plug in, in case of one the association is invalid
2112=nmjxeW3rxWbKj9NvZIZugA_Invalid association in object\='{0}' + association\='{1}'
# YMSG : return from vocabulary runtime plug in, in case of one the association's attributes are invalid
2113=F646ExAtBsQnWg0YmMLjgw_Invalid Attribute for association\=  '{0}' attribute\= '{1}'
# YMSG: return from rule utils, in case of invalid vocabulary assignment
2114=xGVK7Pka5NmWA4Ie8W4eDA_Vocabulary '{0}' is not valid
# YMSG: return from vocabulary runtime plug in, in case invalid alias content
2115=ti2KfAaEGVUDm/+cLn0Z/Q_Invalid content in alias '{0}'. Reason\: '{1}'
# YMSG: return from vocabulary runtime plug in, in case invalid alias name
2116=vCPtWM99cubIv62SVZ95HQ_Alias name '{0}' is invalid. Alias name can contain alphanumeric and underscore characters only, must start with an alphabetical character, and cannot be a reserved word from the rule expression language.
# YMSG: return from vocabulary runtime plug in, in case alias name collide with an data object name
2117=gHifJp9BTRCRtbKS0b+ffw_Alias name '{0}' is invalid. Alias already exists as a data object name.
# YMSG: return from vocabulary runtime plug in, in case o alias dependency to itself
2118=RYXAvdwzbu+Pu6PX58d6IA_Invalid content in alias '{0}'. Resolution of the alias will result in an infinite loop.
# YMSG: return from vocabulary runtime plug in, when name already exists in another vocabulary in the DB. Example: In 'dataObjects', name 'player' already exists in 'aliases' vocabulary 'voca2'
2120=MLUXXXdCdsZtORnQIdmv1A_In '{0}', name '{1}' already exists in '{2}' in vocabulary '{3}'.
# YMSG: return from vocabulary runtime plug in, scope name can't be Public or Private
2121=BLdfmsXhSQUfMMHps3qEIw_Invalid scope name. Scope name cannot be 'Public' or 'Private'.
# YMSG: return from vocabulary runtime plug in, embedded vocabulary can't be with scope Global
2122=EOGIrHv94hp/wKgn1K78GQ_Invalid scope type. Embedded vocabulary cannot be of type 'Global'.
# YMSG: Object does not exist
2125=Q/C5l5zCJpPklgHHGBoyDQ_Object '{0}' does not exist
# YMSG: return from vocabulary runtime plug in, in case of a wrong data object name 
2126=r4/+QKZwUUthCle8LiwCLA_Invalid name for dataObject '{0}'. dataObject name cannot be an existing rule template name or one of the following reserved words (case-sensitive only)\: rule, ruleTemplate
# YMSG: return from vocabulary runtime plug in, in case of a wrong alias name
2127=3eYND9SJ2US8U7f92UCRlA_Alias name '{0}' is invalid. Alias name cannot be an existing rule template name or one of the following reserved words (case-sensitive only)\: rule, ruleTemplate
# YMSG: return from vocabulary runtime plug in, in case invalid data object name
2128=9TaqiuEBR5vmRV7uJ/IHWg_Invalid name for dataObject '{0}'. dataObject name can contain alphanumeric and underscore characters only, must start with an alphabetical character, and cannot be a reserved word from the rule expression language.
# YMSG: return from vocabulary runtime plug in, in case of duplicate alias names
2129=er3nGx92bpWFaDBkLq5WlQ_Alias '{0}' already exists as an alias name.
# YMSG: return from vocabulary runtime plug in, in case alias content is empty
2130=42JAAu2lb30/4Tjbyh2JLQ_Content parameter in alias '{0}' is empty.
# YMSG: return from vocabulary runtime plug in, in case alias name exists as as an attribute name
2131=b4U9hRRY3z9sb9kBuHOmMw_Alias name '{0}' is invalid. Alias already exists as an attribute name.
# YMSG: return from vocabulary runtime plug in, in case alias name exists in other vocabulary with the same scope
2132=3tTXwU/XR1XWDmQkgXq/+w_Alias name '{0}' is invalid. Name already exists as an attribute for object '{1}' in vocabulary '{2}'.
# YMSG: return from vocabulary runtime plug in, in case alias name exists in objects rule or ruleTemplate
2133=7/+7hPEF2I+vyxrVpyyZCw_Alias name '{0}' is invalid. Name already exists in object '{1}'.
# YMSG: return from vocabulary runtime plug in, in case attribute name already exists as alias in other vocabulary
2134=fUHsuea9ZthyNAFjA/PVlg_Invalid name for attribute '{0}'. Name already exists as an alias in vocabulary '{1}'.
# YMSG: return from vocabulary runtime plug in, in case vocabulary declares it depends on a vocabulary which doesn't exists
2135=QBB2qL3L3XxpMGRYOFrEWA_The vocabulary specifies a dependency on vocabulary '{0}' which does not exist.
# YMSG: return from vocabulary runtime plug in, in case implementor declare global vocabulary with dependencies
2136=8KH3/5IstHK41zk4ZX8isg_A global vocabulary cannot contain dependencies to other vocabularies.
# YMSG: return from vocabulary runtime plug in, in case, in the same data object, there is association and attribute with the same name
2137=Xw47Dhv9A1TDgtCKoehBbg_In data object '{0}', the name '{1}' is used for an association and an attribute. The same name cannot be used for both properties.
# YMSG: return from vocabulary runtime plug in, in case invalid alias name
2138=vucb3XZI1BP3rJn2smBD+Q_Name of value list '{0}' is invalid. The name of a value list can contain alphanumeric and underscore characters only, must start with an alphabetical character, and cannot be a reserved word from the rule expression language.
# YMSG: return from vocabulary runtime plug in, in case alias content is empty
2139=go6PChglsnwSntss6lL3Sg_Content of value list '{0}' is empty.
# YMSG: return from vocabulary runtime plug in, in case alias content is empty
2140=mGr3x/FNEAOdQel8tFQ6/g_Value list '{0}' defined in attribute '{1}' in data object '{2}' does not exist.
# YMSG: return from vocabulary runtime plug in, in case parameter size isn't valid
2141=AFeYb8wrl5ZCp1G2OJWndA_In '{'0}, the size ({1}) of parameter '{'2} in '{'3} is not valid for the specified data type.
# YMSG: return from vocabulary - in case parameter content cannot be a collection 
2142=jLsKmzY/YCu4X7EIYA1ukg_Invalid parameter definition for action '{0}' in action parameter '{1}'. Parameters of type collection are not permitted in actions.                                                                                                                                                                   .




# 2300 - 2499 rule template messages

# YMSG: return from Rule Template runtime plug in, in case of rule template name starts with a number
2300=Q9WM7tqLQ5BlLG8+qJfi+A_Rule template creation or update is not possible; rule template name cannot start with a number
# YMSG: return from Rule Template runtime plug in, in case of illegal change in rule template attributes
2301=oFvQHYiGXkgCnAypS9HLGw_Rule Template Activate contains non compatible change;
# YMSG: return from Rule Template runtime plug in, in case of rule template update contains condition change
2302=l98qAtt1oMa13kx4ngpc9g_Rule template creation or update is not possible; rule template condition cannot be changed
# YMSG: return from Rule Template runtime plug in, in case of rule template contains invalid condition 
2303=NA/Uv4oaBPg5q/0pl8ITpA_Rule template creation or update is not possible; condition '{0}' is not valid
# YMSG: return from Rule Template runtime plug in, in case of rule template deletion when there are rules assigned to the rule template  
2304=LuL5Do/0L1Jr+j1jTpY4qg_Cannot delete rule template {0}. There are rules for this rule template;
# YMSG: return from Rule Template runtime plug in, in case of duplicate rule template name  
2305=+L8L3gNRqKEsDXJJdhQ8aw_Rule template creation is not possible; rule template '{0}' already exists in package '{1}'
# YMSG: return from Rule Template runtime plug in, in case that rule template name starts with a number  
2306=tUrEcOnWbAMnwznPXcVtbQ_Rule Template name - '{0}' cannot start with a number;
# YMSG: return from Rule Template runtime plug in, in case that rule template name already exist as data object  
2307=UGGIALu7I0nVGKz3Wnl/QQ_Could not create rule template '{0}'. The rule template name is already used as a data object in vocabulary '{1}'.
# YMSG: return from Rule Template runtime plug in, in case that rule template name already exist as alias
2308=IsXDHlgUsSWTFDEUKIHkwg_Could not create rule template '{0}'. The rule template name is already used as an alias in vocabulary '{1}'.


# 2500 - 2699 - rule messages

# YMSG: return from Rule runtime plug in, in case of resource contains additional attributes but not assigned to rule template   
2500=cVmQdMiRgMUliKRwJOsXZw_Rule creation not possible; additional attributes entered even though rule not based on template
# YMSG: return from Rule runtime plug in, in case of rule template assignment change   
2501=QJshs8bLA9NdOxacwN+Dpw_Rule update not possible; rule template assignment cannot be changed once rule created
# YMSG: return from Rule runtime plug in, in case of vocabulary change  
2502=YJwtNxJUdjzBilOs8BCgdQ_Rule update not possible; vocabulary assignment cannot be changed once rule created
# YMSG: return from Rule runtime plug in, in case of output change   
2503=ISwH+sXs6V4jr1lJPU+zug_Rule update not possible; output assignment cannot be changed once rule created
# YMSG: return from Rule runtime plug in, in case of rule contains additional attributes where assigned rule template does not contains additional attributes
2504=jhf0Fnj2xB4L5wfXQcgAMA_Rule creation not possible; additional attributes entered which do not belong to assigned rule template.
# YMSG: return from Rule runtime plug in, in case of execution context change
2505=UuZTJ8pu7+Ead4WupwoO6A_Rule update not possible; execution context assignment cannot be changed once rule created
# YMSG: return from Rule runtime plug in, in case of invalid rule template assignment
2506=A4KTkGYLqI+CSgjS3Ep/Hg_Rule Template '{0}' is not valid;
# YMSG: return from Rule runtime plug in, in case of invalid status transition
2507=pc2qrHaWTtGAkrJ1CBTQ3A_Rule update not possible; you cannot change from status '{0}' to '{1}'
# YMSG: return from Rule runtime plug in, in case of updating single consumption to non single consumption Rule
2510=DQdUELVIfRWpTkcS+udliQ_Removing of embedded services is not allowed
# YMSG: return from Rule runtime plug in, in case of updating single embedded service in Rule
2511=t/ifZ6eEw3sKO6H+BiSAUA_Removing or changing of embedded services is not allowed
# YMSG: return from Rule runtime plug in, in case of more than one embedded services with the same name
2512=WGTEbJvqiKcCafjsBQV0TA_Embedded service name - '{0}', exists more than once
# YMSG: return from Rule runtime plug in - update/create, in case the rule body is not valid
2513=WXzpwutqCibOBwkk4lencQ_Rule creation or update not possible; rule body is not valid
# YMSG: return from Rule body validator - in case parameter is referenced to an unknown action
2514=oZV+O/rsPcePGH4KP3m8Nw_Invalid parameter definition. Parameter references an action '{0}' that does not exist in vocabulary.
# YMSG: return from Rule body validator - in case parameter name isn't a valid parameter for action
2515=ggHxx6sGeVwa5M7S32gCeQ_Invalid parameter definition. Parameter name '{0}' does not exist for action '{1}' in vocabulary.
# YMSG: return from Rule body validator - in case action doesn't exist in the vocabulary
2516=2ugUY4vvOQFA1RPWJBcW1Q_Action '{0}' does not exist in vocabulary.
# YMSG: return from Rule body validator - when the sent parameter isn't a required parameter in the sent output 
2517=UQTNF97SnwovQBsIvLwd2A_Invalid parameter definition. Parameter name '{0}' does not exist for output '{1}' in vocabulary.
# YMSG: return from Rule body validator - when the sent output doesn't exists in the vocabulary
2518=bkXKPuiF213rNVLD2GUlpg_Output '{0}' does not exist in vocabulary.
# YMSG: return from Rule body validator - when alias has more than one output parameter column
2519=GXzzNoINpYvNwPQxEXeGFA_Alias has more than one output parameter.
# YMSG: return from Rule body validator - when the alias output parameters values do not have the same type X
2520=E9L/2tb0YKUj6Ng4LS9qcg_All values of output parameter '{0}' must be of the same type. 
# YMSG: return from Rule runtime plug in, in case of assign rule to rule service that does not exist.
2521=tXe3tw5/L2lcJU6HO40ZjQ_Could not assign rule '{0}' to rule service '{1}'. The rule service does not exist.
# YMSG: return from Rule runtime plug in, in case of assign rule to rule service with different vocabulary.
2522=lmFqx/HnXHC/4hYz2x4aBA_Could not assign rule '{0}' to rule service '{1}'. The rule service and the rule must have the same vocabulary defined.
# YMSG: return from Rule runtime plug in, in case of assign rule to rule service with different output.
2523=X1Kz1is3aEN/liq7HlMzYw_Could not assign rule '{0}' to rule service '{1}'. The rule service and the rule must have the same output defined.
# YMSG: return from Rule runtime plug in, in case of assign rule to rule service that is not indicated as manually assigned.
2524=QLG2ta1qMeLkpZ9zfduXWA_Could not assign rule '{0}' to rule service '{1}'. The rule service is set for automatic rule assignments and therefore does not allow manual assignments.
# YMSG: return from Rule runtime plug in - update/create, in case a custom condition is not valid
2525=y973asK/+9nal1LsWGbB+Q_Rule cannot be created or updated; '{0}' is not a valid condition.
# YMSG: return from Rule body validator - when ruleBody of type ruleSet has more than one condition column
2526=kG1i2MW6LrFxSQIDUbRKSg_Invalid ruleset. A rule within the ruleset has more than one condition. 
# YMSG: return from Rule body validator - when ruleBody alias has parameter of type collection
2527=wcm/6kXvkM7DkbR4FsYTqQ_Invalid parameter content. Parameter '{0}' cannot be a collection.
# YMSG: return from Rule body validator - when ruleBody expressions don't have the same root object
2528=gmaVEt2q8wb7kS0+cCoZoA_Invalid decision table. All expressions in the decision table must have the same root data object '{0}'.
# XMSG: return from rule validation when not found match result data object between rule and rule service
2529=TOeqZcPjiDAoC9L/J96gqA_Result data object '{0}' in rule '{1}' does not match the result data object '{2}' in rule service '{3}'.
# XMSG: return from rule validation when the vocabulary section was not found.
2530=MPLQKfpJwAik5MLS5ljSwQ_Validation failed to complete. 'vocabulary' is missing in the OData payload.
# 2700 - 2899 - rule service messages

# YMSG: return from Rule service plug in, in case of wrong data object filter
2700=JvoHJNCvaAdiRuzVebzksA_Error in rule service filter
# YMSG: return from Rule service plug in, in case of different data objects in execution context and filter
2701=3Ld/CVxNk9KRs9vcLDJKhQ_Data Object - '{0}' in execution context is different from dataObject - '{1}' in filter
# YMSG: return from  runtime plug in, in case of specified data object does not have the specified attribute (e.g. data object keys in rule service definition).
2704=TjLniwOHNJkDmKGPkSGQjg_Rule service creation or update is not possible; data object {0} of vocabulary {1} does not contain attribute {2}
# YMSG: return from runtime plug in, in case of parameter mapping path contains a collection
2705=8qEXdCMdipMAXIqHDeFfLw_Path with collection is not allowed. Path\: {0};
# YMSG: return from runtime plug in, in case of data object mapping entry is not unique within an execution context .
2706=u8auPNMKTPmAlbmp4NQMSg_data object - {0} has duplicate mappings;
# YMSG: return from  runtime plug in, in case of parameter definition entry is not unique within an execution context .
2707=FRWs2+CFiSmOwiO67AgiUg_Rule service creation is not possible; parameter {0} is duplicated
# YMSG: return from  runtime plug in, in case of parameter mapping entry doesn't have a match parameter definition entry with in an execution context
2708=kHhKmUwtjdHV4T6syiilOQ_Rule service creation is not possible; parameter {0} does not exist and is associated with the data object
# YMSG: return from  runtime plug in, in case of ifentifiers in dataObject type parameter do not exist in data object from vocabulary
2709=y18btjgk5cR86yLviSvriw_Invalid parameter definition in rule service '{0}'. In parameter '{1}', '{2}' is not a valid attribute of data object '{3}' in vocabulary scope '{4}'.
# YMSG: return from runtime plug in, in case of data object definition entry is not unique within parameter definition if service.
2710=KoPc2Fu4JtWnsiZfIz2SeQ_Invalid parameter definition in rule service '{0}'. Data object '{1}' is referenced by more than one parameter.
# YMSG: return from runtime plug in, only read-only rule services can be indicated to be created with result view
2711=eAWnQq8fOUKqBeJflNbghw_Could not create rule service '{0}'. Rule service with result view must be indicated as read-only.
# YMSG: return from runtime plug in, only explicit output rule services can be indicated to be created with result view
2712=R3KmLQHL/A3jllAJ9ybt9Q_Could not create rule service '{0}'. Rule services with a result view must have an explicit output defined.
# YMSG: returned from request handler. Rule requested to be removed from rule service but the rule is not assigned to it
2713=X/Vsb8G+P+d8G4VTvvB85w_Could not remove rule assignment. Rule '{0}' is not assigned to the rule service.
# YMSG: return from  runtime plug in, in case of output contains collection parameter in event mode scenario
2714=mXsBd5HzpggBR6HWWp3LGQ_Could not create rule service '{0}'. You cannot define an output with parameters of type collection for a rule service that does not have a data object defined in its execution context.
# XMSG: return from rule service validation when not found match of result data object between rule service and the vocabulary
2715=yq1ioWXneDeCRiudQ8mH+w_Result data object '{0}' in rule service '{1}' is not defined as a RESULT usage type in the vocabulary.
# XMSG: return from rule service validation when not found match of parameter between rule service and the vocabulary
2716=m3VEjxjUj7mjhJXmgaPP2Q_Parameter '{0}' in vocabulary '{1}' is not defined as an execution context parameter of rule service '{3}'.


# 2900 - 2949 - post activation / completeActivation

# 2950 - 2999 - common resource CRUD


# YMSG: return from Request Handler, in case of url parameter that isn't valid
2955=i7WEiUPvRAHhgclM0S3RSA_url parameter\: {0} is not valid
# YMSG: return from Request Handler, in case of unsupported request mode
2956=oUMWdAswdwzNIFkdSLxBeg_Mode \#{0} is not supported
# YMSG: return from Request Handler, in case of unsupported metadata
2957=9IMVGEPWINab3NWC36whmw_Metadata is not supported
# YMSG: return from Request Handler, in case of unsupported metadata for method
2958=x4WkAoEppAGkKRt+SeIsCQ_Get Metadata is only valid with request method GET


# YMSG: returned when wrong query is generated (during procedure generation). 2 causes: Bug in process or there is no mapping from vocabulary to real table / column
2970=uTPSlKYuJtjHbbr7j0wCdA_Error in query generation or invalid mapping
# YMSG: returned if for some reason the parser returned undefined parse model. Can be bad rule syntax or a bug
2971=QcPXsWn5AZIwYjZqZNOrxQ_Parse model is undefined
# YMSG: query generation needs either leading object and at least one key or a mapping to parameters. The error is returned if something is missing 
2972=huvZWVSXE9sxHP+MLDXSdw_Invalid combination of leading object, keys and mapping
# YMSG: returned when there is no association between 2 objects in vocabulary
2973=NaIv4TdHTEnR9F1GeNA7PQ_Invalid association - no attributes
# YMSG: returned when there is a use of attribute based on predictive model but the procedure for the predictive model is not defined
2974=a4oZzvDWdpkZ6Kcs4YudKQ_Prdective module procedure {0} not found
# YMSG: outputs tanle type is mandatory. error when missing 
2975=059UhK1g9LvWOIMEXJOJdA_Invalid result data
# YMSG: error when is out name is missing in vocabulary output names 
2976=j1zR422SEiuEzZ+FsLyg9g_Invalid output name
# YMSG: error when rule body type is different from text or decisionTable 
2977=PdorFqTonSYirbETsBdQ3A_invalid rule body type
# YMSG: return from Runtime plugins, in case of unsupported change mode
2978=xVmuWExsq3VznpHd6u2ewA_Change Mode '{0}' is not supported for resource
# YMSG: return from Runtime plugin - generate, for informing on the change mode for current resource
2979=Rd7x5UNc3kvuEGil4Ag1/Q_Resource generation, in change mode\: '{0}'
# YMSG: return when expression  
2980=HM0EjPz0d+Vx93k8w1pc6A_Error in parsing expression\: \: '{0}'
# YMSG: return when expression  
2981=V1kI4pbcsL2l+ieUQPAtUw_Rule template '{0}' creation is not possible. The name is already used by one of the data objects in a vocabulary '{1}'.



#############################
# API: Get params
#############################

# 3100 - 3999 - get params messages

# YMSG: return from  ruleBodyAnalyzer, in case of businessRule.type is not text
3100=e9qEMPuQeurTAcmYsJPGUA_Business rule type should be text
# YMSG: return from  ruleBodyAnalyzer, in case of Vocabulary is missing
3101=LFhqnYeDihhFYM4RA9d2TQ_Vocabulary is missing

#############################/
# API: Rule service consumption
#############################/
# 4100 - 4999 messages

# YMSG: return message in case the output is partial
4100=WkdRi4xbKOROnWLQJUqJRQ_{0} items shown. Note this is only a partial set of the results. If the saveResult flag is set to TRUE, the full set of results can be found in '{'1}.output table.

#############################/
# Halm and Installation
#############################/

# YMSG: Post Activation API success
10000=iaUC1ZkNaBZQxI4xSWZx3A_Configuration script for SAP HANA rules framework completed successfully.
# YMSG: Post Activation API failed
10001=n3RFgo7dHu5tSXs5vhgoyQ_An error occurred in configuration script of SAP HANA rules framework. {0}
# YMSG: Post Activation API failed
10002=MuqICw7uoJ6Bgn0+7hK8KA_An existing configuration for the web application of SAP HANA rules framework has been detected. Setting the default configuration for the web application is therefore not allowed.
# YMSG: Post Activation API failed
10003=OaWe6TU+dIfsPPRDPyBG7A_Configuration of the web application for SAP HANA rules framework failed due to a technical error. Reason\: {0}
# YMSG: Post Activation API failed
10004=JHNBy8CL/3IYYquhVhoc4g_A rule service or rule with an embedded service already exists in the system. Updating the time zone is therefore not allowed.
# YMSG: Post Activation API failed
10005=ePN68VqMwbUoavzADDRZBQ_A rule service or rule with an embedded service already exists in the system. Updating the runtime schema is therefore not allowed.
