FTR0 - Treasury: Financial Transaction
The following messages are stored in message class FTR0: Treasury: Financial Transaction.
It is part of development package FTTR in software component FIN-FSCM-TRM-TM-TR. This development package consists of objects that can be grouped under "Treasury: Financial Transaction".
It is part of development package FTTR in software component FIN-FSCM-TRM-TM-TR. This development package consists of objects that can be grouped under "Treasury: Financial Transaction".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Transaction &2 in company code &1 already being edited by user &3 |
| 002 | You are already editing transaction &2 in company code &1 |
| 003 | A system error occurred when blocking the transaction |
| 004 | Transaction &2 does not exist in company code &1 |
| 005 | Number range &1 in company code &2 does not exist |
| 006 | Number range &1 in company code &2 is assigned internally |
| 007 | Number range &1 in company code &2 is assigned externally |
| 008 | Numbers are in critical assignment area |
| 009 | Assigned number is the last one in the number range |
| 010 | You are requesting more numbers than are available |
| 011 | Number &1 not between &2 and &3 |
| 012 | Transaction &2 in company code &1 already exists |
| 013 | Transaction &2 in company code &1 has status &3 |
| 014 | Transaction &2 in company code &1: Activity &3 has status &4 |
| 015 | Unknown error when posting transaction &1 &2 |
| 016 | Transaction &2 in company code &1: Activity &3 inactive |
| 017 | Transaction &2 in co.code &1: Activity &3 replaced by subsequent activity |
| 018 | Transaction &2 in company code &1 &: Activity &3 reversed |
| 019 | Transaction &2 in company code &1 has been created |
| 020 | Transaction &2 in company code &1 has been changed |
| 021 | Transaction &2 in company code &1 has been reversed |
| 022 | Transaction &2 in company code &1: Activity &3 reversed |
| 023 | Transaction data has been transferred |
| 024 | Product category & cannot be processed with this function |
| 025 | Transaction &1 is not supported |
| 026 | Program &1 is not supported |
| 027 | Function (&1 &2) is not supported |
| 028 | Security class &1 of product category &2 is not supported |
| 029 | Product category &1 is not supported |
| 030 | No payment details entered for transaction |
| 031 | Payment details are incomplete (&) |
| 032 | Payment details: Bank &1 has a deletion flag |
| 033 | Value date in transaction 1 is later than value date in transaction 2 |
| 034 | Transaction &1 should be posted before transaction &2 |
| 035 | No payment details entered for transaction &1 &2 |
| 036 | Caution: Field &1 contains value "0" |
| 037 | At least one transaction skipped, it is not relevant for payment w/o post |
| 038 | At least one flow skipped because it is not relevant for payment w/o post |
| 039 | Not possible to create or change prod. categ. &1; functions not supported |
| 040 | Error in the alert framework container |
| 041 | Error while sending alert message; Alert was not sent |
| 042 | Alert was sent successfully |
| 043 | Customizing is not available for assigning the alert category |
| 044 | Container element is not defined |
| 046 | Alert category is not defined correctly |
| 047 | Error in the transaction data |
| 048 | Notification is not required |
| 049 | Alert was sent successfully for co key &1 to Alert Category &2 |
| 050 | The co key &1 has not yet reached alert waiting time,alert not sent |
| 051 | Error while sending alert message. Alert was not sent. |
| 052 | No information is available for selected transaction. |
| 053 | No security account information is available for selected transaction |
| 054 | Transaction &1 settled successfully |
| 055 | Settlement of transaction &1 terminated due to errors |
| 056 | This function is not possible for product category &1 |
| 057 | Order execution for transaction &1 terminated due to errors |
| 058 | Order execution for transaction &1 completed successfully |
| 059 | Select entries |
| 060 | Order expiry for transaction &1 completed successfully |
| 061 | |
| 062 | Output language for documents is &1 |
| 063 | Interest rate passed with more than & digits after decimal point |
| 066 | Not possible to create corporate action categ. &1; function not supported |
| 067 | Not possible to use number range &1; function not supported |
| 100 | ****************** Financial transaction archiving 100 - 149 ************ |
| 101 | Error while creating archive file |
| 102 | Partner &1 is still used in role &2 in Treasury transactions |
| 103 | Minimum retention period of transactions &1 &2 not achieved |
| 104 | Transaction &2 in CC &1 contains inconsistent data |
| 105 | Transaction &2 in CC &1 contains flows that have not been posted |
| 106 | Transaction &2 in CC &1 has insufficient confirmation status |
| 107 | Transaction &2 in CC &1 has insufficient settlement status |
| 108 | Transaction &2 in CC &1 is assigned to an active facility |
| 109 | Customizing setting missing for min. retention per.; trans. &2 in CC &1 |
| 110 | Transactions with this product category cannot be archived |
| 111 | Payment detail is still in use; see transaction &2 in CC &1 |
| 112 | Residence time not over for transaction &2 in CC &1 |
| 113 | No residence time defind for company code &1 |
| 126 | |
| 150 | ***************** Financial transaction BUS2042 150 - 199 *************** |
| 151 | Transaction has not been changed |
| 152 | X-comparison parameters not up-to-date |
| 153 | No authorization for product type & |
| 154 | MoneyMarket parameter contains no changes for X-comparison parameter |
| 155 | ForeignExchange parameter contains no changes for X-comparison parameter |
| 156 | Counterconfirmation of transaction & via BAPI not possible |
| 157 | No main flows can be maintained with BAPIs for this transaction |
| 158 | No flows can be maintained in the cash flow for this transaction |
| 159 | No other flows can be maintained for this transaction |
| 160 | No conditions can be maintained for this transaction |
| 161 | BAPI processing was terminated |
| 162 | BAPI was executed successfully |
| 163 | API was not called correctly |
| 164 | Internal error in API |
| 165 | Title element is not active |
| 166 | &1 entry &2 no change since no change information in &3 |
| 167 | Company code &1 in BAPI structure differs from method parameter &2 |
| 168 | BAPI processing was terminated for item with index &1 of table BAPIDATA |
| 169 | Can not match mainflow from mainflow table supplied |
| 181 | Financial transaction &1 activity &2 not found |
| 182 | No confirmation yet sent for financial transaction &1 activity &2 |
| 183 | No counter-confirmation required for financial transaction &1 activity &2 |
| 184 | Financial transaction &1 activity &2 is already counter-confirmed |
| 185 | Incorrect counter-confirmation status of financial trans. &1 activity &2 |
| 200 | ************************ Transaction release 200 - 250 ****************** |
| 201 | Customizing data for release procedure incomplete |
| 202 | Customizing data for release conditions incomplete |
| 203 | Transaction &2 in company code &1 in release: Processing not permitted |
| 204 | Release condition &1 for transaction processing unknown |
| 205 | Workflow error &1, function module &2 |
| 206 | Transaction &2 in CoCd &1 is in release; processing only in workflow |
| 250 | ***************** Correspondence transactions 250 - 400 ***************** |
| 251 | Error in form &1, language &2 (see log for the form) |
| 252 | Correspondence data for transaction & being formatted |
| 253 | Form &1: Text &2 (language &3) not found |
| 254 | Text &1; Text ID: &2 in language &3 not up-to-date |
| 255 | Standard texts only delivered in languages 'DE' and 'EN' |
| 256 | Correspondence planned record created manually is deleted in background |
| 257 | Copy form &? |
| 258 | Correspondence planned record deleted in background |
| 259 | Info: Languages form &1 from &2 to &3 |
| 260 | Communication interface for telefax not yet configured |
| 261 | Select one line only |
| 262 | E-mail address of business partner &1 not available |
| 263 | E-mail address of business partner &1 (address &2) not available |
| 264 | Select at least one correspondence medium |
| 265 | Fax number of business partner &1 (default address) does not exist |
| 266 | Fax number of business partner &1 (address &2) not available |
| 267 | No SWIFT code specified for business partner &1 (see long text) |
| 268 | No SWIFT code defined in company code &1 |
| 269 | Selection restricted to &1 hits |
| 270 | No data is available for the selection criteria entered |
| 271 | Further processing only possible after 'refresh' in monitor |
| 272 | SWIFT files cannot be generated from monitor |
| 273 | Repeat function not permitted for planned record |
| 274 | Planned record created for repeat; start the SWIFT report |
| 275 | Repeat function for activity &1 (function &2) is not permitted |
| 276 | Internal error: Function module & not called |
| 277 | Internal error: Function module & not called correctly |
| 278 | Specify an internal correspondence type for conversion |
| 279 | No correspondence exists for the selections |
| 280 | Correspondence type does not impact on maintenance view (see long text) |
| 281 | test |
| 282 | Correspondence status assignment not unique (Customizing error) |
| 283 | Partner profiles for the IDoc send process are not maintained |
| 284 | IDoc entries not permitted for internal correspondence type |
| 285 | Select at least one valid entry (see long text) |
| 286 | Communication method SAPconnect set! |
| 287 | Function module &1 called up incorrectly (see long text) |
| 288 | Indicator for automatic correspondence is not permitted (field: CORAUT) |
| 289 | Enter just one correspondence medium per data record |
| 290 | Status-relevant planned record for activity &1 not deleted |
| 291 | E-mail address of user &1 (-> sender) not maintained |
| 292 | Correspondence planned records were deleted |
| 293 | Info: 'Preview' not possible for medium &1 |
| 294 | Check results for business partner & |
| 295 | Check results for company code & |
| 296 | Standing instructions do not exist for the selection criteria |
| 297 | Check results for company code &1 / correspondence type &2 |
| 298 | The data record selected does not have status &1 |
| 299 | Counterconfirmation could not be reset |
| 300 | You are not permitted to reset counterconfirmation |
| 301 | Counterconfirmation was reset (&1 -> &2) |
| 302 | Unable to find transactions with reset counterconfirmations |
| 303 | Correspondence planned record for transaction &1 was created |
| 304 | INFO: Printer replacement &1 -> &2 is active |
| 305 | Activity category &1 to product category &2 not a fixing activity |
| 306 | No output device has been defined in the fixed values for user & |
| 307 | Settings incorrect for optical archiving (see long text) |
| 308 | No texts could be selected in source system |
| 309 | Business partner &1 neither exists in role &2 nor &3 |
| 310 | Customizing is not necessary for PType &1, TType &2, ACat &3, function &4 |
| 311 | No SWIFT code: Business partner &1 not defined as a bank |
| 312 | INFO: Redundant Customizing for printing (see long text) |
| 313 | Activity cat. &1 for prod. type &2/trans.type &3 obsolete (see long text) |
| 314 | Caution: Printer replacement only affects printer defined in Customizing |
| 315 | Outgoing confirmation has not yet been made (Medium: &) |
| 316 | Incoming confirmation is still open (for last &1 days and &2 hours) |
| 317 | Date/time may not be in the future |
| 318 | &1: No messages exist |
| 319 | Specify a correspondence type before you select the address ID |
| 320 | Choose the correspondence type using the F4 help |
| 321 | Correspondence type &1 is not permitted (see long text) |
| 322 | Spool request &1 from &2 no longer exists |
| 323 | Automatic correspondence only possible for current activity |
| 324 | Activity &1 is not permitted |
| 325 | Counter confirm. has not occurred since correspondence obj.&1(channel &2) |
| 326 | Outgoing confirmation &1 has not yet been sent (channel: &2) |
| 327 | Incoming confirmation &1 is not complete (&2 days and &3 hours) |
| 328 | Incoming confirmation &1 for sec.acct &2 is not complete (&3 days &4 hrs) |
| 329 | Counterconfirmation of &1 has not occurred for sec. acct &2 (channel &3) |
| 330 | Outgoing confirmation &1 for sec. acct &2 has not been sent (channel: &3) |
| 350 | Form &1 is not a SAPScript form but a PDF form |
| 351 | Form &1 is not a PDF form but a SAPScript form |
| 352 | PDF form &1 does not exist |
| 353 | PDF form &1 does not exist in language &2 |
| 354 | No PDF form found in Customizing |
| 355 | PDF form &1 is not activated |
| 356 | E-mail has been generated and sent |
| 357 | Fax has been generated and sent |
| 400 | ************* Financial transaction incoming IDoc 400 - 500 ************ |
| 401 | Product category &1 cannot be processed on the incoming side |
| 402 | No suitable transaction found for matching |
| 403 | INFO: Only transactions with missing outgoing confirmation found (no.:&1) |
| 404 | INFO: Only transactions that have already been matched were found (no.&1) |
| 405 | INFO: Transactions without confirmation or with counterconf.found (&1/&2) |
| 406 | INFO: 1 suitable transaction and several potential candidates found |
| 407 | INFO: &1 suitable transactions were found (see long text) |
| 408 | Transaction &1; company code &2, activity &3 counterconfirmed |
| 409 | SWIFT code &1 (sender) could not be assigned to any business partner |
| 410 | No open counterconfirmation found for partner &1 |
| 411 | Product category &1 is not supported |
| 412 | No business partner was assigned in inbound processing |
| 413 | The IDoc assignment/counterconfirmation was reversed |
| 420 | The nominal amount cannot be determined for product category 530 |
| 430 | **** Structure messages for assignment logic ************** (up to 448) |
| 431 | Processing log for confirmation IDoc &1 |
| 432 | Processing log for confirmation of receipt &1 |
| 433 | Level &1: &2 |
| 434 | Check OK! |
| 435 | Product category &1 (&2) |
| 436 | Step &1: Which transactions require counterconfirmation? |
| 437 | Number: &1 |
| 438 | Counterconfirmation possible for transaction &1/&2 (activity &3) |
| 439 | Step &1: The database is scanned with the following values: |
| 440 | &1: &2 (&3) |
| 441 | Step &1: Remaining transactions after matching with transaction data: |
| 442 | Step &1: Summary/results analysis: see long text |
| 443 | Transaction &1 from company code &2 (activity &3) was assigned |
| 444 | No premium data was specified for the option |
| 445 | Following the assignment attempt, there are no more suitable transactions |
| 446 | BAdI: Correspondence data record was deleted for transaction &1, CoCd &2 |
| 447 | BAdI: Correspondence data record was included for transaction &1, CoCd &2 |
| 448 | IDoc no. &1 does not have the logical message type &2 |
| 449 | IDoc status &1: Manual linking is only permitted for status '51' |
| 450 | IDoc no. &1 is not an inbound IDoc; manual linking is not permitted |
| 451 | IDoc status &1 cannot be set (see long text) |
| 452 | Transaction &1 (company code &2) successfully linked |
| 453 | External reference was changed from &1 to &2 |
| 454 | Contact person was changed from &1 to &2 |
| 455 | TARO with &1 was not yet sent to trade repository &2 |
| 456 | TARO with &1 was rejected from trade repository &2 |
| 457 | TARO with &1 could not be reconciled by trade repository &2 |
| 458 | No TARO exists for trade repository &1 |
| 459 | TARO (&1) was created for non-matchable message from trade repository &2 |
| 460 | After termination at trade repository &1, no new TARO was created |
| 461 | Backloading not performed for trade repository &1 |
| 500 | ************* Report 500 - 550 Integration Hedge Accounting ************* |
| 501 | Hedge Accounting: You must not change the contract date |
| 502 | Hedge Accounting: You must not change the value date |
| 503 | Hedge Accounting: Rate must not be changed |
| 504 | Hedge Accounting: Underlying data must not be changed |
| 505 | Hedge Accounting: Swap rate must not be changed |
| 550 | Data destruction report for entity 'Contact Person' |
| 551 | Report mode: &1 |
| 552 | Table &1: number of anonymized entries is &2 |
| 553 | Specified contact person: &1 |
| 554 | Internal error. Please contact SAP. |
| 555 | Table &1: Number of entries after key date is &2 |
| 556 | Key date for data destruction: &1 (retention period in months: &2) |
| 557 | Only data before key date will be deleted/anonymized |
| 558 | Table &1: Number of deleted entries is &2 |
| 559 | Retention period is not specified for entity 'Trader' |
| 560 | Retention period is not specified for entity 'Contact Person' |
| 561 | You do not have the authorization to run this report |
| 562 | Specified trader: &1 |
| 563 | Data destruction report for entity 'Trader' |
| 564 | Data destruction report for entity 'Email Address' |
| 565 | Table &1: Number of entries is &2 |
| 566 | Entries in table &1 cannot be deleted (data exists after cut-off date) |
| 567 | Entries in table &1 must be deleted using ILM deletion program |
| 568 | Entries in table &1 cannot be deleted (data exists in ILM objects) |
| 569 | Caution: Input for contact person is case-sensitive |
| 570 | Caution: Input for trader is case-sensitive |
| 571 | Total number of entries to be deleted/anonymized is &1 |
| 572 | Total number of deleted/anonymized entries is &1 |
| 573 | No data was selected to be deleted/anonymized |
| 574 | Data destruction report for entity 'Email Address' |
| 575 | Caution: Input for email address is case-sensitive |
| 600 | Not Permitted |
| 601 | Successfully executed |
| 602 | Do not enter a Contract ID for a multi contract mandate |
| 603 | Specify a finance project |
| 604 | Only mandate type 3 is allowed if a finance project is specified |
| 605 | Choose contract type &1 for financial transaction &2 |
| 606 | Repetitive code &1: Release date is in the future |
| 700 | This program no longer works; please contact SAP support |
| 701 | Hedge request ID &1 with request category &2 cannot be used |
| 702 | Hedge request ID &1 with status &2 cannot be used |
| 703 | & does not exist |
| 704 | Hedge request ID &1 with value date &2 cannot be used |
| 705 | Hedging class. &1 does not match hedging class. &2 of hedge request. |
| 706 | Hedging classification must be specified. |
| 707 | Value date &1 does not match value date &2 of hedge request. |
| 708 | Traded amount exceeds the available amount of the hedge request. |
| 709 | Product category doesn't match instrument category (&1) of hedge request. |
| 710 | Traded currency &1 doesn't match currency &2 of hedge request. |
| 711 | Buy/Sell indicator of traded amt doesn't match indicator of hdg. req. amt |
| 712 | Termination request &1 isn't released yet. Release the request first. |
| 713 | Strike rate doesn't match strike rate &1 of hedge request. |
| 714 | Fixing date &1 doesn't match fixing date &2 of hedge request. |
| 715 | Expiry date &1 doesn't match expiry date &2 of hedge request. |
| 717 | Hedge request currency &1 does not match the transaction currency &2 |
| 718 | Company code &1 of hedge request &2 does not match company code &3 |
| 719 | Portfolio &1 of hedge request &2 does not match portfolio &3 |
| 720 | Profit center &1 of hedge request &2 does not match profit center &3 |
| 721 | Cost center &1 of hedge request &2 does not match cost center &3 |
| 722 | WBS Element &1 of hedge request &2 does not match WBS Element &3 |
| 723 | On behalf of company code &1 of hedge req. &2 does not match transaction |
| 724 | Business area &1 of hedge request &2 does not match business area &3 |
| 725 | Country/Region &1 of hedge request &2 does not match country/region &3 |
| 726 | Segment &1 of hedge request &2 does not match segment &3 |
| 727 | Product type (&1) doesn't match instrument category (&2) of hedge req. &3 |
| 728 | Buy/Sell indicator of &2 doesn't match the indicator of the hdg. req. &1. |
| 875 | Cannot change CURRENCY or CURRENCY_ISO |
| 895 | IBAN for housebank &1 account ID &2 set valid from &3 |
| 896 | Error in Customizing for product type &1; Facility category is missing |
| 897 | Error during calculation of accrued interest in transaction &1 (&2) |
| 898 | No BAPI support available for transaction &1 &2 |
| 899 | Field &1 contains invalid field value &2 |