SAP Message Class S~
Repository API Business Navigator
Recommended Now
Fire TV Stick Lite Essentials Bundle
This bundle contains Amazon Fire TV Stick Lite and Mission USB Power Cable. The USB power cable eliminates the need to find an AC outlet near your TV by powering Amazon Fire TV directly from your TV's USB port. Includes special power management circuitry that enhances the peak power capability of the USB port by storing excess energy and then releasing it as needed.
Check it out on amazon.com →
The Message Class S~ (Repository API Business Navigator) is a standard Message Class in SAP ERP and is part of the package SDFI.
Technical Information
| Message Class | S~ |
| Short Text | Repository API Business Navigator |
| Package | SDFI |
Messages
| ID | Language | Text |
|---|---|---|
| 000 | D | Modell existiert nicht for Objekttyp & |
| 001 | D | Objekt/Modell ist nicht vorhanden |
| 002 | D | Interner Fehler & |
| 003 | D | Es gibt keine I/O-Zuordnungen für EPC-Typ BMEP - nur für BMSP |
| 004 | D | Es gibt keine SysOrg-Zuordnungen für EPC-Typ BMEP - nur für BMSP |
| 005 | D | Keine Informationsflüsse von oder zu diesem Objekt |
| 006 | D | In Tabelle DFPRX konnte kein aktives Nummernkreispräfix gefunden werden |
| 007 | D | Funktion ist für diesen Objekttyp nicht möglich |
| 008 | D | Menge muß größer 0 sein |
| 015 | D | Objekt ist nicht vorhanden |
| 016 | D | Objekt ist bereits vorhanden |
| 017 | D | Modell ist bereits vorhanden |
| 129 | D | Pfad von epc & zu epc & mit Ereignis & und unerlaubtem Knoten & |
| 130 | D | Pfad von Prozeß zu Szenario & (&) |
| 131 | D | Pfad von Szenario zu Prozeß & (&) |
| 132 | D | Pfad von Prozeß zu Funktion & (&) |
| 133 | D | Pfad von Szenario zu Funktion & (&) |
| 134 | D | Pfad zu unbekanntem epc & (&) |
| 135 | D | In & Pfad nicht verbunden mit Ereignis & (&) |
| 136 | D | Ereignis & startet Prozeß & nicht |
| 137 | D | Startereignis & in Prozeß & nicht vorhanden |
| 138 | D | Ereignis & beendet Prozeß & nicht |
| 139 | D | Endereignis & in Prozeß & nicht vorhanden |
| 140 | D | Link von Szenario & zu Szenario & |
| 141 | D | Link von Szenario & zu Funktion & |
| 142 | D | Link von Szenario & zu unbekanntem & |
| 143 | D | Objekt hat keine Definition (Knotentyp &, interne ID &) |
| 144 | D | Link von Prozeß & zu Szenario & |
| 145 | D | Link von Prozeß & zu Prozeß & |
| 146 | D | Keine Eingangsentität für & |
| 147 | D | Keine Ausgangsentität für & |
| 148 | D | Keine Systemorganisation für & |
| 149 | D | Keine Eingangsentität für & erlaubt |
| 150 | D | Keine Ausgangsentität für & erlaubt |
| 151 | D | Keine Systemorganisation für & erlaubt |
| 152 | D | Zyklus vorhanden |
| 153 | D | Fehler - Abbruch prüfen |
| 154 | D | Falsche Anzahl Zeilen (&). Zeilen müssen zwischen & und & sein. |
| 155 | D | Falsche Anzahl Objekte. Nur & Ereignisse und & Funktionen in epc |
| 156 | D | Fehler &1 &2 zurückgegeben bei Änderung von Entw.-Klasse für &3 &4 |
| 000 | E | Model does not exist for object type & |
| 001 | E | Object/Model does not exist |
| 002 | E | Internal error & |
| 003 | E | There are no I/O assignments for EPC-Type BMEP - only for BMSP |
| 004 | E | There are no SysOrg Assignments for EPC-Type BMEP - only for BMSP |
| 005 | E | There are no information flows from or to this object |
| 006 | E | No active prefix for object numbers determined (see long text) |
| 007 | E | Function is not possible for this object type |
| 008 | E | Quantity must be greater than 0 |
| 009 | E | Only 50.000 free numbers are left over |
| 010 | E | The number range is full now |
| 011 | E | The number range is full now. Only & numbers can be provided. |
| 012 | E | Date base error - please check system log for details |
| 013 | E | Model type does not exist or is not allowed |
| 014 | E | Object does not exist in language & |
| 015 | E | Object does not exist |
| 016 | E | Object already exists |
| 017 | E | Model already exists |
| 018 | E | Object type does not exist |
| 019 | E | View type does not exist |
| 020 | E | Different parent objects in diagram_info and nodes/lines/linepoints |
| 021 | E | There is already a component &1 that refers on component &2 |
| 022 | E | There is already an org unit &1 that refers to org unit &2 |
| 023 | E | SAP objects may not be changed at all and can't be locked |
| 024 | E | Filter type does not exist |
| 025 | E | Selection & does not exist |
| 026 | E | Invalid parameter combination |
| 027 | E | No object model assigned to application component & |
| 028 | E | One of the tables contains duplicate keys. |
| 029 | E | Object has wrong prefix |
| 030 | E | You read data with version &1 with API of version &2 |
| 031 | E | Field &1 contains invalid entry &2 |
| 032 | E | Anbiguity: there are more than one model assigned o component &1 |
| 033 | E | String to convert contains unknown characters |
| 034 | E | String to convert contains syntax error |
| 035 | E | Invalid combination of parameters |
| 036 | E | GUID &1 does not exist in R/3 |
| 037 | E | GUID &1 not found for object |
| 038 | E | Ident &1 does already exist |
| 039 | E | Objects with field IDENT - SPACE can not be inserted |
| 100 | E | Object position & & is used & times |
| 101 | E | On node & (typ &) exists a loop |
| 102 | E | From node & to node & exists more than one line |
| 103 | E | No endnode found & & & & |
| 104 | E | No startnode found & & & & |
| 105 | E | Endnode (&) with typ & is not allowed |
| 106 | E | Object & with nodetyp & is not allowed in model & |
| 107 | E | Can't read epc & (&) |
| 108 | E | Path from & (&) with event & (&), but no reverse path |
| 109 | E | Node & (&/&) is in model definition, but not used. |
| 110 | E | Line from node & & to unknown successor node. |
| 111 | E | Line from unknown predecessor node to node & &. |
| 112 | E | Startnode (&) with typ & is not allowed |
| 113 | E | Only one predecessor allowed node & with typ & |
| 114 | E | Only one successor allowed node & with typ & |
| 115 | E | Nodetyp & (&) followed nodetyp & (&) |
| 116 | E | Node & (successor from & type &) is obsolute |
| 117 | E | Node & has more than one predecessor and more than one successor |
| 118 | E | Function & not defined |
| 119 | E | No attributes for function & |
| 120 | E | Function (&) attribute name is empty |
| 121 | E | Transactioncode & not defined (Function &) |
| 122 | E | Function (&) has a transactioncode with attribut manuell |
| 123 | E | Function (&) has no transactioncode and no attribut manuell |
| 124 | E | Event & not defined |
| 125 | E | No attributes for event & |
| 126 | E | Event (&) attribute name is empty |
| 127 | E | Path to & (&) with event & (&), but no reverse path |
| 128 | E | Path from epc & to epc & with event & |
| 129 | E | Path from epc & to epc & with event & and not allowed node & |
| 130 | E | Path from process to scenario & (&) |
| 131 | E | Path from scenario to process & (&) |
| 132 | E | Path from process to function & (&) |
| 133 | E | Path from scenario to function & (&) |
| 134 | E | Path to unknown epc & (&) |
| 135 | E | In & path not connected with event & (&) |
| 136 | E | Event & does not start process & |
| 137 | E | Startevent & not exists in process & |
| 138 | E | Event & does not end process & |
| 139 | E | Endevent & not exist in process & |
| 140 | E | Link from scenario & to scenario & |
| 141 | E | Link from scenario & to function & |
| 142 | E | Link from scenario & to unknown & |
| 143 | E | Object has no definition (nodetyp &, internal id &) |
| 144 | E | Link from process & to scenario & |
| 145 | E | Link from process & to process & |
| 146 | E | No input entity for & |
| 147 | E | No output entity for & |
| 148 | E | No systemorganisation for & |
| 149 | E | No input entity for & allowed |
| 150 | E | No output entity for & allowed |
| 151 | E | No systemorganisation for & allowed |
| 152 | E | An cycle exist |
| 153 | E | An error occured - check abort |
| 154 | E | Wrong number of lines (&). Lines must between & and & |
| 155 | E | Wrong number of objects. Only & events and & functions in epc |
| 156 | E | Error &1 &2 returned on change of package for &3 &4 |