CRM_PS_4S_BRFP - Message Class for Social Services BRF+ integration
The following messages are stored in message class CRM_PS_4S_BRFP: Message Class for Social Services BRF+ integration.
It is part of development package CRM_PS_BRFPLUS in software component CRM-S4-IPS. This development package consists of objects that can be grouped under "CRM / Social Services BRFPlus functionalties".
It is part of development package CRM_PS_BRFPLUS in software component CRM-S4-IPS. This development package consists of objects that can be grouped under "CRM / Social Services BRFPlus functionalties".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** 000-099 Reserved for common messages |
| 001 | &1 &2 &3 &4 |
| 100 | *** 100-198 Messages for Expression Type "Search" |
| 101 | BAdI CRM_BRFP_SEARCH: multiple impl. exist for filters &1 and &2 |
| 102 | The result object is not of type table |
| 103 | The result object does not represent a table of CRM object GUIDs |
| 104 | No predecessor search allowed for case search expression |
| 105 | Predecessor search has to be of expression type CRM search |
| 106 | Predecessor search has to be of search object &1 |
| 107 | No predecessor search expression set |
| 108 | Search parameter &1 not compatible to search value expression &2 |
| 109 | Missing mandatory search parameter(s): &1 |
| 110 | Missing search value(s) for the parameter &1 |
| 111 | No multivalue allowed for parameter &1 |
| 112 | Predecessor data object does not represent a table of CRM object GUIDs |
| 113 | BAdI CRM_BRFP_SEARCH: Data element &1 does not exist |
| 114 | BAdI CRM_BRFP_SEARCH: One or more field(s) are defined several times |
| 115 | No search object set |
| 116 | Select search parameters &1 and &2 together |
| 117 | Usage of search parameter &1 requires parameter &2 |
| 118 | Usage of parameter &1 disables the multivalue function of parameter &2. |
| 119 | Search value of parameter &2 is incomplete at position &1. |
| 120 | Search object changed from &1 to &2 |
| 121 | Search object set to &1 |
| 122 | Search object &1 removed |
| 123 | Predecessor search object changed from &1 to &2 |
| 124 | Predecessor search object set to &1 |
| 125 | Predecessor search object &1 removed |
| 126 | Search parameter &1 was added with &2 line(s) in the range table |
| 127 | Search parameter &1 was removed |
| 128 | Search parameter &1 changed: |
| 129 | New &1 search with &2 search parameter(s) created |
| 130 | Case type &1 has been determined |
| 131 | Search object: &1 |
| 132 | Evaluating search values of search parameter &1 |
| 133 | Evaluating search value at position &1 |
| 134 | Sign = &1, Option = &2 |
| 135 | Low expression: |
| 136 | Low simple value = &1 |
| 137 | High expression: |
| 138 | High simple value = &1 |
| 139 | Search is based upon: |
| 141 | Search failed due to parameter errors |
| 142 | End date must be later than start date |
| 160 | Parameter &1 could not be mapped to the result object |
| 161 | Only one attribute can be selected since result object is of type element |
| 162 | Result object was successfully updated |
| 163 | Save in order to make the changes to result object effective |
| 164 | You must specify a result object before it can be bound |
| 165 | Assign a context parameter or expression to the order GUID |
| 166 | The expression or data object is not compatible with the order GUID |
| 167 | The expression or data object is not compatible with business partner ID |
| 168 | Assign context parameter or expression to business partner ID |
| 169 | Mapping to non-applicable data object for parameter &1 |
| 199 | *** 199-299: Messages for Calling BRF+ |
| 200 | Error during BRFplus trace processing |
| 201 | Error during case type determination using BRFplus |
| 202 | Error during BRFplus; process type not found |
| 203 | Error during case determination using BRFplus |
| 204 | Error during item proposal using BRFplus |
| 205 | Error during SSP assignment using BRFplus |
| 206 | Error during BRFplus; main business partner not found |
| 207 | Error during web request form data validation using BRFplus |
| 208 | Error during saving of BRFplus trace |
| 209 | Error during BRFplus; Web request category not found |
| 210 | &1 is not a valid BRFplus application |
| 211 | &1 is not a valid BRFplus function within &2 |
| 212 | No BRFplus application/function customized for process step &1 |
| 213 | BRFplus application instantiation failed; check &1 Customizing |
| 214 | BRFplus function instantiation failed; check &1 Customizing |
| 215 | BRFplus application &1 instantiation failed; check &2 Customizing |
| 216 | BRFplus function &1 instantiation failed; check &2 Customizing |
| 217 | BRFplus function &1 improper for &2 (requiring context &3) |
| 218 | BRFplus application &1 contains no function &2 |
| 219 | Error during Decision Basis determination using BRFplus |
| 221 | Error during Scope Determination using BRFplus |
| 222 | BRFplus trace not supported for Scope Check |
| 223 | Error during Scope Check using BRFplus |
| 225 | Error during reduction determination using BRFplus |
| 227 | For BRF+ Function &1, versioning is turned off |
| 228 | The function &1 does not have the right context for this process step |
| 300 | *** 300-399 Messages for Action Type "Activity" |
| 301 | Enter a business transaction type |
| 302 | Enter an reason for CRM activity |
| 303 | Activity reason is incorrect |
| 304 | User status of activity is incorrect |
| 305 | Priority of activity is incorrect |
| 306 | Category of activity is incorrect |
| 307 | Goal of activity is incorrect |
| 308 | Initial free text for message &1 is not allowed |
| 309 | Enter a message type for message &1 |
| 310 | Duplicate message types are not allowed |
| 311 | Activity &1 has been created |
| 312 | No multiple field names allowed |
| 313 | Message class &1, number &2 does not have a longtext in language &3 |
| 314 | Expression &1 could not be read |
| 315 | Enter an expression for partner function &1 |
| 316 | Primary person can be used only once for each partner function &1 |
| 317 | Partner function &1 with same expression already existing |
| 318 | Partner function &1 inconsistent; &2 partners expected |
| 319 | Return type for case GUID must be of type text with length 32 |
| 320 | Elements of table for case GUID must be of type text with length 32 |
| 321 | Return type for activity template must be of type text with length 32 |
| 322 | Return type for language must be of type text with length 2 |
| 323 | Return type for transaction history must be of type text with length 32 |
| 324 | Invalid return value for date |
| 325 | Return type for business partner ID must be of type text with length 10 |
| 326 | Return type for enhanced fields must be of type text |
| 327 | BP with function &1 and expression &2 added |
| 328 | BP with function &1 and expression &2 deleted |
| 329 | Unknown exception calling function module &1 |
| 330 | New BRFplus action type for CRM activity created with transaction type &1 |
| 331 | Field &1 changed from &2 to &3 |
| 332 | Field &1 set to &2 |
| 333 | Field &1 removed |
| 334 | Text with text type &1 added |
| 335 | Text with text type &1 deleted |
| 336 | Field &1 and expression &2 added |
| 337 | Field &1 and expression &2 deleted |
| 338 | Deactivation of BP determination and call in EC are not allowed |
| 339 | Enter an expression for field &1 (Enhancements) |
| 340 | Use only one message as activity description |
| 341 | Unknown exception calling method &1 of class &2 |
| 342 | Transaction type is incorrect |
| 343 | Return type f. leading bus.trans obj. must be of type text with length 32 |
| 344 | Enter an expression for the leading business transaction object |
| 345 | Activity with ID &1 created successfully |
| 346 | Function module CRM_PS_ACTIVITY_CREATE ended with error |
| 347 | &1 case GUID found; for each case GUID one activity will be created |
| 348 | Activity will be created in language &1 |
| 349 | Field &1 changed from &2 to &3 in partner function &4 |
| 350 | Partner function &1 inconsistent; one partner expected |
| 351 | No empty entry in tab enhancements allowed |
| 352 | No multiple fields with name &1 in tab enhancements allowed |
| 353 | No multiple empty field names in tab enhancements allowed |
| 354 | No empty entry in tab business partner allowed |
| 400 | *** 400-449 Messages for Expression Type "Web Request" |
| 401 | Select Web request field from tree |
| 402 | Envelope field must be selected |
| 403 | Select a Web request category |
| 404 | The result object does not fit to the selected field |
| 405 | The Web request order GUID is not a CRM object GUID |
| 406 | Select a source type |
| 407 | A new Web request field expression with source type &1 was created |
| 408 | Web request expression error: Missing order |
| 409 | Select a valid Web request field |
| 410 | Web request order GUID needs to be of type text with length 32 |
| 411 | Request type &1 does not exist |
| 412 | Web request expression &1: Order ID cannot be assigned |
| 500 | *** 500-549 Message for Action Type "Case Note" |
| 501 | Enter a value for the number of cases |
| 502 | Expression &1 could not be read |
| 503 | Return type for case search object is not correct |
| 504 | Enter an expression for the case search |
| 505 | Number of cases found > 1; input of allowed cases = 1 |
| 506 | Number of cases found = 0; input of allowed cases = 1 |
| 507 | Number of cases found > 1; input of allowed cases max. 1 |
| 508 | Number of cases found = 0; input of allowed cases at least 1 |
| 509 | New BRFplus action of type CRM case note created |
| 510 | Type conversion error during evaluation of expression &1 |
| 511 | Action &1 contains no messages |
| 512 | Timestamp type &1 is not supported; expression &2 of function &3 |
| 513 | Type conversion error |
| 514 | No multiple empty field names allowed in note attributes |
| 515 | No multiple fields with name &1 allowed in note attributes |
| 516 | No empty entry allowed in note attributes |
| 517 | Enter an expression for field &1 in note attributes |
| 518 | &1 case GUID(s) found; one note will be created for each case |
| 519 | Note will be created in language &1 |
| 520 | Note has been created for case &1 |
| 521 | Language &1 from expression &2 is unknown.System language is used instead |
| 522 | Error occurred during eligibility period determination |
| 600 | *** 600-619 Messages for Action Type "Web Request Message" |
| 601 | Assigned expression &1 is not of type CRM Web Request Read |
| 602 | The source type of expression &1 has to be Web Request Field |
| 603 | Action failed; invalid field reference assigned |
| 604 | There was a change in message for field reference at position &1 |
| 605 | No field xpath found in web request &1 |
| 701 | Class &1 does not implement method &1 |