Id | Title |
---|---|
SALV_GRU121 | Not possible to switch to Excel display |
SALV_WD_EXCEPTION000 | &1 &2 &3 &4 |
SALV_WD_EXCEPTION001 | An error occurred in the Web Dynpro ALV |
SALV_WD_EXCEPTION002 | Error while calling &OBJECT& &KEY& (class &CLASS& Method &METHOD&) |
SALV_WD_EXCEPTION003 | Error while calling &OBJECT& &KEY& |
SALV_WD_EXCEPTION004 | Error in &OBJECT& with key &KEY& in method &METHOD& of class &CLASS& |
SALV_WD_EXCEPTION010 | **************** Config Errors ******************** |
SALV_WD_EXCEPTION011 | Configuration error |
SALV_WD_EXCEPTION012 | Method &METHOD& of class &CLASS& cannot be called at this time |
SALV_WD_EXCEPTION013 | Selection type &KEY& in combination with selection &KEY_2& of the |
SALV_WD_EXCEPTION014 | Object &OBJECT& &KEY& already exists |
SALV_WD_EXCEPTION015 | Object &OBJECT& &KEY& does not exist |
SALV_WD_EXCEPTION016 | Property &OBJECT& with attribute &KEY& is not supported by ALV |
SALV_WD_EXCEPTION300 | **************** Program Errors ******************* |
SALV_WD_EXCEPTION301 | Error in programming |
SALV_WD_EXCEPTION400 | **************** Program Errors UI **************** |
SALV_WD_EXCEPTION401 | Data no longer available when &OBJECT& &KEY& called |
SALV_WD_EXCEPTION500 | ****************** UI Messages ***************************************** |
SALV_WD_EXCEPTION501 | Error with the Data Nodes |
SALV_WD_EXCEPTION502 | The data node not found in WebDynpro context |
SALV_WD_EXCEPTION520 | Wildcards are not allowed for numerical fields. |
SALV_WD_EXCEPTION551 | Error in the configuration |
SALV_WD_EXCEPTION552 | Object &OBJECT &KEY already exists |
SALV_WD_EXCEPTION553 | Objekct &OBJECT &KEY not found |
SALV_WD_EXCEPTION600 | **************** Program Errors Services ********** |
SALV_WD_EXCEPTION899 | Error occurred in Webdnypro ALV |
SALV_WD_MSG000 | &1 &2 &3 &4 |
SALV_WD_MSG300 | ****************UI SALV_WD_TABLE ****************** |
SALV_WD_MSG301 | Wildcards are not allowed for numerical fields. |
SALV_WD_MSG303 | Input & & & is invalid. Use the input help |
SALV_WD_MSG304 | Input & & & is invalid |
SALV_WD_MSG305 | Internal message: & & & & |
SALV_WD_MSG500 | ****************Layout/Persistence***************** |
SALV_WD_MSG501 | View & could not be deleted |
SALV_WD_MSG502 | "&1" view deleted |
SALV_WD_MSG503 | "&1" view still exists as &2 |
SALV_WD_MSG504 | View & could not be stored |
SALV_WD_MSG505 | "&1" view saved |
SALV_WD_MSG506 | "&1" view properties saved |
SALV_WD_MSG600 | **************** Dialog Settings ****************** |
SALV_WD_MSG601 | A maximum of & rows can be displayed. Value is reset. |
SALV_WD_MSG602 | Table design "Alternating" is ignored for editable tables |
SALV_WD_MSG603 | Displayed columns = 0 creates an empty table without visible columns |
SALV_WD_MSG604 | Displayed rows = 0 creates an empty table without visible rows |
SALV_WD_MSG605 | Displayed rows < 0 displays all rows |
SALV_WD_MSG700 | ****************Print Version********************** |
SALV_WD_MSG701 | Print version &1: &2&3&4 |
SALV_WD_MSG702 | Print version created and sent to printer &1. |
SALV_WD_MSG703 | Column '&1' contains cell variants and cannot be exported |
SALV_WD_X_API001 | Context Node Types not equal 'Standard' are not supported! |
SALV_X899 | SALV BRAIN &1 &2 &3 &4 |
SALV_X_API000 | Unable to create export version of table data. |
SALV_X_API001 | Column &1, respectively parts of their attributes could not be set |
SALV_X_API002 | Only first column with fieldname &1 will be considered in the excel |
SALV_X_API003 | For all columns based on fieldname &1 the same valueset will be used |
SALV_X_API004 | Only first column with fieldname &1 will be considered in the excel |
SALV_X_API005 | Reference &1 does not refer to a standard internal table |
SALV_X_API006 | No header text can be provided for column &1 |
SALV_X_API007 | For column &1 no text source is provided, so column will be empty |
SALV_X_API008 | For image column &1 no image source is provided, so column will be empty |
SALV_X_INT_UI000 | Simulated error. Test message. |
SAML000 | No RFC destination specified (parameter DESTINATION) |
SAML001 | Error when communicating with RFC destination &1: &2&3&4 |
SAML002 | Invalid process code: &1&2&3&4 |
SAML003 | SAML service of the J2EE Engine (&1) not started |
SAML004 | Error in the SAML EJB (&1): &2&3&4 |
SAML005 | SAML service (&1): &2&3&4 |
SAML006 | Different name for SAML artifact parameter: &1 / &2 |
SAML007 | Communication with the SAML service on J2EE Engine &1 successful |
SAML008 | Version of the SAML service of J2EE Engine &1 is too low (&2 < &3) |
SAML009 | No SAML artifact found in URL parameter "&1" |
SAML010 | Logon method "&1" is not permitted for this resource |
SAML011 | Error when logging on for external ID "&1": &2 |
SAML2000 | An internal error occurred (message: &1) |
SAML2001 | Analysis of XML fragment &1 failed (error message: &2) |
SAML2002 | Parameter &1 was either incorrectly set or not set in method &2 |
SAML2003 | Error in ST program &1 when importing XML data |
SAML2004 | Failed to generate the XML data using ST program &1 |
SAML2005 | No entity in with &1 &2 in client &3 found |
SAML2006 | Entity &1 in client &2 already exists |
SAML2007 | Message '&1' did not arrive at the correct destination |
SAML2008 | SSF function &1 returned the error code &2 |
SAML2009 | User assignment of name ID &1 (format: &2) failed |
SAML2010 | Identity federation of user &1 (format: &2) failed |
SAML2011 | SAML2 in client &1 is not active |
SAML2012 | Index&1 does not contain an entity |
SAML2013 | Defederation of user &1 (format: &2) failed |
SAML2014 | Entity #&1' does not support the format '&2' for user assignment |
SAML2015 | Defederation of format '&1' is not supported |
SAML2016 | Federation for format '&1' is not supported |
SAML2017 | There is no trust between entities &1 and &2 in client &3 |
SAML2018 | Configuration forbids identity federation |
SAML2019 | Element '&1' is not supported |
SAML2020 | The user account of IDP [&1] is not yet federated in system &2 (&3) |
SAML2021 | The validation of message '&1' failed |
SAML2022 | The assertion issuer is not identical to the response issuer |
SAML2023 | Attribute '&1' of element '&2' is invalid |
SAML2024 | All 'SubjectConfirmation' elements are invalid |
SAML2025 | Attribute '&1' is not identical in all '&2' elements |
SAML2026 | '&1' elements reference different users |