FTR_TCORF_MSG - Correspondence Messaging Interface: Messages
The following messages are stored in message class FTR_TCORF_MSG: Correspondence Messaging Interface: Messages.
It is part of development package FTR_CORRESPONDENCE_FW in software component FIN-FSCM-TRM-TM. This development package consists of objects that can be grouped under "Treasury Correspondence (Message Interface and Framework)".
It is part of development package FTR_CORRESPONDENCE_FW in software component FIN-FSCM-TRM-TM. This development package consists of objects that can be grouped under "Treasury Correspondence (Message Interface and Framework)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 002 | Profile '&1' not found |
| 003 | No BADI '&1' for filter '&2' implemented |
| 004 | Corresponce Class '&1' not found |
| 005 | Recipient '&1' not found |
| 006 | Channel '&1' not found |
| 007 | Format '&1' not found |
| 008 | No channel assigned to profile '&1', class '&2', recipient '&3' |
| 009 | No format assigned to class '&1', recipient '&2', channel '&3' |
| 010 | No metatype assigned to profile '&1', channel '&2' |
| 011 | Configuration node '&1' not found |
| 012 | Configuration table '&1' not found |
| 013 | No value provided for key field '&2' in configuration node '&1' |
| 014 | Key field '&2' of parent for configuration node '&1' not found |
| 015 | Configuration table not defined for node '&1' |
| 016 | No value provided for filter object '&2' in configuration node '&1' |
| 017 | Channel attribute can not be read for channel '&1', profile '&2' |
| 018 | Format attribute can not be read for format '&1', profile '&2' |
| 019 | Message &1 &2 not found |
| 020 | Message &1 &2 can not be cancelled (already sent or cancelled) |
| 021 | Error reading profiles |
| 022 | Error reading channels |
| 023 | Error reading recipients |
| 024 | Error reading correspondence classes |
| 025 | Error reading formats |
| 026 | Error reading channel assignments |
| 027 | Error reading format assignments |
| 028 | Profile missing |
| 029 | Correspondence class missing |
| 030 | Recipient type missing |
| 031 | Select a line before deleting |
| 032 | Enter the Position number of the Rule |
| 033 | Position number already used. Choose another number. |
| 034 | Node &1 used in Mapping rule |
| 036 | No Message Format is chosen. |
| 037 | No mapping rules found for format &1 direction &2 condition &3 |
| 038 | No mapping rules found for format &1 direction &2 parameter &3 |
| 039 | No mapping rules found for format &1 direction &2 service method &3 |
| 051 | Configuration saved |
| 052 | Configuration already saved |
| 053 | Error while saving configuration |
| 101 | Mapping not defined for format &1, direction &2 |
| 102 | Parameter group &1 not defined |
| 103 | Condition &1 not defined |
| 104 | Invalid condition operation &1 |
| 105 | Constant/system access on target object side is not possible |
| 106 | Source sequence &1 not available (parent closed) |
| 107 | Source table &1 not available; not part of parent source |
| 108 | Table &1 not accessible; already open or not a table |
| 109 | Sequence &1 is not open; can not be accessed |
| 110 | Target sequence &1 is not a table (LOOP operation) |
| 111 | Invalid mapping side: &1 |
| 112 | Access to closed sequence &1 is not possible |
| 113 | Sequence &1 closed; field &2 not accessible |
| 114 | Sequence &1 not found in DDIC-type map object |
| 115 | Target &1 not in open sequence; access not possible |
| 116 | Invalid component type; sequence: &1 |
| 117 | Simulation not allowed for source objects |
| 118 | Veto raised in BADI "CHECK_PAYLOAD" (see messages) |
| 119 | No new incoming message imported |
| 120 | Incoming messages imported successfully |
| 121 | Field &2 not found in sequence &1 |
| 122 | Obligatory line of &1 not found; mapping line: &2 |
| 123 | System code-page not found |
| 124 | Either metatype or format required |
| 125 | Mapping tool failed: direction &3, format &1, line &2 |
| 201 | Select exactly one entry of the parent level '&1' |
| 202 | Key-field '&1' with value '&2' already exists |
| 203 | Fill key-field '&1' |
| 204 | Current view is consistent |
| 205 | No selection value found for field '&1' |
| 206 | No implementation found for configuration node '&1' |
| 207 | No table found for the combination &1 = '&2' |
| 208 | Invalid selection field '&1' in configuration |
| 209 | Unknown key field '&1' in link structure |
| 210 | BADI error for config node '&1' and field '&2' |
| 251 | Component &1 exists already |
| 252 | Component &1 is still in use; all mapping rules will be deleted |
| 253 | Configuration saved |
| 254 | No changes to be saved |
| 255 | Error while saving configuration |
| 256 | Mapping for &1 &2 exists already |
| 257 | Service class &1 not found |
| 258 | Direction, format and service class are mandatory |
| 259 | Configuration contains error; see &1 mapping for format &2 |
| 260 | Component name can not contain special characters a spaces |
| 261 | Parameter &1 not found |
| 262 | Condition &1 not found |
| 263 | Component &1 not found in source &2 |
| 264 | Component &1 referenced earlier than defined in generic target |
| 265 | Target component &1 contains rule with error |
| 266 | Rule with Position number &1 contains error |
| 267 | Source component missing for the operation &1 |
| 268 | Source &1 is not a node; for operation &2 a node source is required |
| 269 | Source &2 is not a field; for operation &2 a field source is required |
| 270 | No method assigned for the operation &1 |
| 271 | No parameter assigned for the operation &1 |
| 272 | Operand &1 contains error |
| 273 | Referenced parameter &1 contains error |
| 274 | Referenced parameter &1 not found |
| 275 | Parameter &1: target component &2 not defined |
| 276 | Parameter &1: source component &2 not found |
| 277 | Parameter &1: source component &2 invalid |
| 278 | Condition &1 Position &2: target component &3 not defined |
| 279 | Condition &1, side &2: source component &3 not found |
| 280 | Condition &1, side &2: source component &3 invalid |
| 281 | Mapping for &1 &2 format is consistent |
| 282 | Condition &1, side &2: field is required as left operand (&3) |
| 283 | Condition &1, side &2: node is required as left operand (&3) |
| 284 | Condition &1, side &2: field is required as right operand (&3) |
| 285 | Condition &1, side &2: operator required in each line (except last one) |
| 286 | Condition &1, side &2: operation &3 allows only one side |
| 287 | Parameter &1: generic target component &2 is pre-referenced |
| 288 | Condition &1, side &2: generic target component &3 is pre-referenced |
| 289 | Node &1 has sub-component with error |
| 290 | Inserting a child to a field is not possible |
| 291 | Source type is mandatory for outbound messages |
| 292 | Target type is mandatory for inbound messages |
| 301 | Internal error |
| 302 | Internal error: key structure can not be created |
| 303 | Internal error: invalid type descriptor |
| 304 | Internal error: invalid BADI type: '&1' |
| 305 | Internal error: filter not specified |
| 306 | Internal error: format or meta-type must be specified |
| 307 | Internal error: exactly one type of mapping object required |
| 308 | Internal error: invalid line &1 in mapping |
| 309 | Internal error: field control info missing for field &1 |
| 310 | Internal error: invalid type descriptor |
| 311 | Internal error: structure &1 without line reference |
| 312 | Internal error: context change failed |
| 313 | Internal error: target read without escape character |
| 314 | Internal error: no message created for format &2 |
| 315 | Internal error: message not formatted for meta-type &1 |
| 316 | Internal error: DMS document &1 &2 not created or not saved |
| 317 | Internal error: Unable to create output request |
| 401 | BADI error: field &1 is not supported in configuration exit of &2 |
| 402 | No format defined for profile &4, corr.class &1, recipient &2, channel &3 |
| 501 | Please fill BP ROLE or check internal field |