FIN_CORR - Message class for fiori correspondence
The following messages are stored in message class FIN_CORR: Message class for fiori correspondence.
It is part of development package ODATA_CORRESPONDENCE_V2 in software component CA-GTF-FXU-FI-AR. This development package consists of objects that can be grouped under "oData Services - Correspondence version 2".
It is part of development package ODATA_CORRESPONDENCE_V2 in software component CA-GTF-FXU-FI-AR. This development package consists of objects that can be grouped under "oData Services - Correspondence version 2".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | Correspondence type & not supported as it requires Individual text. |
| 002 | Correspondence type & not supported as it requires Cross-company code. |
| 003 | Your request contains too many or too few parameters. |
| 004 | Correspondence output is not generated for event &. |
| 005 | For multi-customer correspondence, only Print is available. |
| 006 | Customer & does not match any records. |
| 007 | Supplier & does not match any records. |
| 008 | The correspondence could not be created. |
| 009 | Add the AccountType parameter to your request. |
| 010 | Document & & does not match any records. |
| 011 | Please specify either Customer or Supplier but not both. |
| 023 | You requested a copy of the billing document. |
| 024 | An internal error occurred. No copy has been created. |
| 031 | |
| 032 | The billing document &1 cannot be printed. No valid message type. |
| 040 | Company code &1 does not match any records. |
| 041 | Supplier &1 is not defined for company code &2. |
| 042 | The email could not be sent. Please contact your administrator. |
| 043 | The document could not be printed. Please contact your administrator. |
| 044 | Customer &1 is not defined for company code &2. |
| 100 | Application log could not be created. |
| 101 | Application log could not be loaded. |
| 300 | Input data has already been set and cannot be changed. |
| 301 | Could not create an Application Object ID. |
| 302 | Request &1 cannot be saved as new because it already exists. |
| 303 | Request &1 cannot be saved. |
| 304 | Cannot access the Output Management system. |
| 305 | Output mode &1 is not supported. |
| 306 | Mandatory parameter &1 is missing. |
| 307 | The Application Object ID could not be recognized. |
| 308 | The account and account type are determined from the document number. |
| 309 | Output management is not configured for &1. |
| 310 | Application object type &1 is invalid. |
| 311 | Application object type &1 is not active. |
| 312 | Output type &1 is invalid. |
| 313 | Could not generate correspondence using the legacy Output Management. |
| 314 | Mode &1 is not supported. |
| 315 | Email recipients were not provided and could not be determined. |
| 316 | Output Management nodes could not be created. |
| 317 | Could not process the request. |
| 318 | The correspondence has been sent to &2. &1 |
| 319 | Input parameter: &1, value: &2. |
| 320 | Output management request could not be saved. |
| 321 | Output could not be created. |
| 322 | The parameter ''&1'' has been set to ''&2''. |
| 323 | A recipient with the email address ''&1'' was added to the request. |
| 324 | The parameter &1 cannot have the value you specified (&2). |
| 325 | No output has been selected. |
| 326 | The attribute &1 of advanced parameter &2 has an invalid value "&3". |
| 330 | All requests have been processed. |
| 331 | One or more requests could not be processed. |
| 332 | No request for the specified application object ID could be found. |
| 333 | The parameters handler for the form data provider was not found. |
| 334 | Could not get a logger instance for the specified request. |
| 335 | Could not load form data provider parameters for the specified request. |
| 336 | Could not load form data provider parameters from the parameters storage. |
| 337 | Could not convert the range parameter ''&1''. |
| 338 | No bank account found for company code &, bank &, and account &. |
| 339 | Failed to load the account statement data. |
| 340 | No document is found for key ''&1'', ''&2''. |
| 341 | No document can be retrieved for key ''&1'', ''&2''. |
| 342 | Could not retrieve the PDF document from the Output Management. |
| 343 | Output Management could not generate the requested PDF document. |
| 344 | The requested PDF document could not be retrieved from Output Management. |
| 345 | Could not modify the determined parameters of the Output Management item. |
| 346 | Output Management nodes could not be created using BRF+. |
| 347 | The Output Management item does not meet the requirements. |
| 348 | An internal error occurred while getting the BOBF root item. |
| 349 | Could not retrieve the XML document from the Output Management. |
| 350 | Output Management email node can not be created for ''&1''. |
| 351 | An internal error occurred. A mandatory parameter is missing. |
| 352 | An internal error occurred. The email node cannot be deleted. |
| 353 | Print Queue &1 is invalid. |
| 354 | Could not generate the requested PDF document. |
| 355 | A recipient with the email address ''&1'' was removed from the request. |
| 400 | The subject is too long (&1 characters). Please shorten it to 50. |
| 401 | No email template found for ''&1'' correspondence in language ''&2''. |
| 402 | Communication language could not be determined. |
| 403 | The sender email address is not configured. |
| 899 | Table '&1' cannot be archived with ILM object FI_ARPCORR. |