SAP ABAP Message Class SAMDT_VALIDATIONS (Validations errors in S&AM design time)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-ESI-SAM (Application Component) Status and Action Management
⤷
SESF_SAM_DT_MANAGER (Package) S&AM Desing time core
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-ESI-SAM (Application Component) Status and Action Management⤷
SESF_SAM_DT_MANAGER (Package) S&AM Desing time core 
Attributes
| Message class |  |
SAMDT_VALIDATIONS |
| Short Description |  |
Validations errors in S&AM design time |
| Changed On |  |
20130531 |
| Last Changed At |  |
091346 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Relation between elements &1 and &2 is invalid | The short text describes the object sufficiently | |
| 2 | 001 |
Synchronizer between elements &1 and &2 forms loop | The short text describes the object sufficiently | |
| 3 | 002 |
Synchronizer to &1 &2 is invalid as &3 &4 has inbound derivation | The short text describes the object sufficiently | |
| 4 | 003 |
Synchronizer to non initial &1 &2 is invalid as &3 &4 has state guard | The short text describes the object sufficiently | |
| 5 | 004 |
Synchronizer is invalid as status variable &1 has inbound derivation | The short text describes the object sufficiently | |
| 6 | 005 |
Synchronizer btn status values of same status variable &1 is invalid | The short text describes the object sufficiently | |
| 7 | 006 |
Synchronizer to target status variable &1 exists from same source | The short text describes the object sufficiently | |
| 8 | 007 |
Synchronizer from initial status value &1 is invalid | The short text describes the object sufficiently | |
| 9 | 008 |
Business Object &1 does not exist | The short text describes the object sufficiently | |
| 10 | 009 |
Node &1 does not exist | The short text describes the object sufficiently | |
| 11 | 010 |
Schema element &1 does not exist | The short text describes the object sufficiently | |
| 12 | 011 |
Derivation to &1 &2 is invalid as it has already inbound derivation &3 | The short text describes the object sufficiently | |
| 13 | 012 |
Derivation to &1 &2 is invalid,it has inbound transition/synchronizer | The short text describes the object sufficiently | |
| 14 | 013 |
Derivation to &1 &2 is invalid as it has state guard | The short text describes the object sufficiently | |
| 15 | 014 |
More than one outgoing derivation from derivative &1 is invalid | The short text describes the object sufficiently | |
| 16 | 015 |
Derivation having same source and target status variable &1 is invalid | The short text describes the object sufficiently | |
| 17 | 016 |
Derivation to &1 &2 is invalid as derivative &3 has inbound derivation | The short text describes the object sufficiently | |
| 18 | 017 |
More than one inbound derivation to derivative &1 is invalid | The short text describes the object sufficiently | |
| 19 | 018 |
Derivation from &1 &2 is invalid,derivative &3 has outbound derivation | The short text describes the object sufficiently | |
| 20 | 020 |
variable value &1 for variable &2 does not exist | The short text describes the object sufficiently | |
| 21 | 021 |
Transition from action &1 to status variable &2 is invalid | The short text describes the object sufficiently | |
| 22 | 022 |
Transition to status variable &1 is invalid, it has inbound derivation | The short text describes the object sufficiently | |
| 23 | 023 |
Schema saved successfully | The short text describes the object sufficiently | |
| 24 | 026 |
Inhibhiting edge from inhibhiting status value &1 is invalid | The short text describes the object sufficiently | |
| 25 | 031 |
Relation &1 between elements &2 and &3 already exists | The short text describes the object sufficiently | |
| 26 | 032 |
Element &1 already exists | The short text describes the object sufficiently | |
| 27 | 033 |
&1 &2 does not have any &3 edge | The short text describes the object sufficiently | |
| 28 | 034 |
Status variable &1 does not have any edge | The short text describes the object sufficiently | |
| 29 | 035 |
Derivative &1 does not have any incoming or outgoing edge | The short text describes the object sufficiently | |
| 30 | 036 |
Status variable &1 should have atleast one initial status value | The short text describes the object sufficiently | |
| 31 | 037 |
Status variable &1 should have atleast two status values | The short text describes the object sufficiently | |
| 32 | 041 |
Action &1 must have atleast one enabling precondition | The short text describes the object sufficiently | |
| 33 | 051 |
Operators must have at least one outgoing edge | The short text describes the object sufficiently | |
| 34 | 052 |
Operators should not have less than two neutral edges | The short text describes the object sufficiently | |
| 35 | 061 |
State guard on status var &1 is invalid as there is inb derivation | The short text describes the object sufficiently | |
| 36 | 071 |
Status value &1 has outbound inhibhiting relation | The short text describes the object sufficiently | |
| 37 | 081 |
Depends on relation ship in sub process &1 forms loop | The short text describes the object sufficiently | |
| 38 | 090 |
The schema already exists | The short text describes the object sufficiently | |
| 39 | 091 |
The schema &1 does not exist | The short text describes the object sufficiently | |
| 40 | 092 |
JNet not installed | The short text describes the object sufficiently | |
| 41 | 093 |
No errors found | The short text describes the object sufficiently | |
| 42 | 094 |
Please enter schema name | The short text describes the object sufficiently | |
| 43 | 095 |
Parent BO schema cannot be edited in Child BO | The short text describes the object sufficiently | |
| 44 | 096 |
Runtime proxy generated successfully | The short text describes the object sufficiently | |
| 45 | 097 |
Schema &1 copied successfully to &2 | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 72L |
