SAP_NWBC - NWBC Messages
The following messages are stored in message class SAP_NWBC: NWBC Messages.
It is part of development package SAP_NWBC in software component BC-FES-BUS-RUN. This development package consists of objects that can be grouped under "NetWeaver Business Client".
It is part of development package SAP_NWBC in software component BC-FES-BUS-RUN. This development package consists of objects that can be grouped under "NetWeaver Business Client".
Message Nr ▲ | Message Text |
---|---|
000 | &1&2&3&4 |
001 | Duplicate area names exist: &1 |
002 | Do not use special characters for an area name: &1 |
003 | Area &1 does not yet exist and can therefore not be deleted |
004 | No areas entered to be generated |
005 | Invalid path for area &1 |
006 | Program must be of type 'Executable Program' |
007 | Programs were generated successfully |
008 | Programs can be generated successfully |
009 | A code line exceeds the maximum length |
010 | Error while updating program &1 |
011 | Error in popup |
012 | Generation cancelled |
013 | Short dump occurred in repository class |
014 | Create new file area &1? |
015 | Create file area &1 |
016 | Data saved successfully |
017 | Do not use apostrophes in theme names |
018 | Method &1 is not supported in &2 |
019 | Tag ID &1 is not valid |
020 | Screen number &1 is not valid |
021 | Tag ID &1 is in customer's namespace and will not be transported |
022 | Field &1 is mandatory |
023 | Program name &1 is not valid |
024 | Namespace &1 is not editable |
025 | Wrong maintenance view for namespace &1; use &2 instead |
026 | Tag &1 is in the SAP namespace; the defined tag overrules the SAP tag |
027 | Property &1 does not have a valid prefix |
028 | No errors have been determined in selected entries |
029 | A file area for theme &1 &2 already exists |
030 | The user menu tree for user &1 with role &2 is empty. |
031 | NWBC cache with &1 is invalidated. |
032 | Using smart search for resolving OBN &1.&2. Role filter is &3. |
033 | OBN Resolving failed. Source role &1. |
034 | PFCG entry type &1 of node &2 is not supported. |
035 | Target system "&1" (or "&1_HTTP" or "&1_HTTPS") for entry &2 is invalid. |
036 | Target system alias "&1" (or "&1_RFC") for entry &2 is invalid. |
037 | RFC destination for alias &1 is undefined or incomplete |
038 | External alias is missing (&1) that must point to ICF node &2 |