SAP ABAP Message Class /TDAG/RCS_EP (Messages for endpoint management)
Basic Data
Hierarchy
☛
TDAGBCA (Software Component) TechniData Basic Components
⤷
EHS (Application Component) Environment, Health and Safety
⤷
/TDAG/RCS_EP (Package) REACH Compliance - Endpoint Management
TDAGBCA (Software Component) TechniData Basic Components⤷
EHS (Application Component) Environment, Health and Safety⤷
/TDAG/RCS_EP (Package) REACH Compliance - Endpoint Management 
Attributes
| Message class |  |
/TDAG/RCS_EP |
| Short Description |  |
Messages for endpoint management |
| Changed On |  |
20141109 |
| Last Changed At |  |
211008 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Program error; parameter table with invalid structure | The short text describes the object sufficiently | |
| 2 | 001 |
No authorization to use activity &1 on specification (RECN=&2) | The short text describes the object sufficiently | |
| 3 | 002 |
No endpoint chapter is defined in endpoint data record | The short text describes the object sufficiently | |
| 4 | 003 |
Endpoint chapter &1 is invalid | The short text describes the object sufficiently | |
| 5 | 004 |
No substance is assigned to endpoint data record | The short text describes the object sufficiently | |
| 6 | 005 |
Endpoint data record assigned to invalid substance (RECN=&1) | The short text describes the object sufficiently | |
| 7 | 006 |
GUID &1 already exists; cannot create new endpoint data record | The short text describes the object sufficiently | |
| 8 | 007 |
No primary key (GUID) of endpoint data record is supplied in update | The short text describes the object sufficiently | |
| 9 | 008 |
Primary key (GUID=&1) of endpoint data record is invalid in update | The short text describes the object sufficiently | |
| 10 | 009 |
No endpoint data record found for deletion | The short text describes the object sufficiently | |
| 11 | 010 |
Both substance and endpoint data record supplied: only one is permitted | The short text describes the object sufficiently | |
| 12 | 011 |
Neither substance nor endpoint data record supplied; one is required | The short text describes the object sufficiently | |
| 13 | 012 |
No substance assigned to letter of access | The short text describes the object sufficiently | |
| 14 | 013 |
Letter of access is assigned to invalid substance (RECN=&1) | The short text describes the object sufficiently | |
| 15 | 014 |
GUID &1 already exists; cannot create new letter of access | The short text describes the object sufficiently | |
| 16 | 015 |
Letter of access is not assigned to an endpoint data record | The short text describes the object sufficiently | |
| 17 | 016 |
Letter of access is assigned to invalid endpoint data record | The short text describes the object sufficiently | |
| 18 | 017 |
No primary key (GUID) of letter of access is supplied in update | The short text describes the object sufficiently | |
| 19 | 018 |
Primary key (GUID=&1) of letter of access is invalid in update | The short text describes the object sufficiently | |
| 20 | 019 |
Error when reading substance data (&1) | The short text describes the object sufficiently | |
| 21 | 020 |
Maximum tonnage band not defined in specification &1 | The short text describes the object sufficiently | |
| 22 | 021 |
No substance is assigned to endpoint chapter | The short text describes the object sufficiently | |
| 23 | 022 |
Endpoiont chapter is assigned to invalid substance (RECN=&1) | The short text describes the object sufficiently | |
| 24 | 023 |
GUID &1 already exists; cannot create new endpoint chapter | The short text describes the object sufficiently | |
| 25 | 024 |
Endpoint chapter does not exist (chapter: &1, recnroot: &2) | The short text describes the object sufficiently | |
| 26 | 025 |
Error creating IUCLID BAdI | The short text describes the object sufficiently | |
| 27 | 026 |
GUID &1 already exists; cannot create new IUCLID substance data | The short text describes the object sufficiently | |
| 28 | 027 |
No substance assigned to IUCLID substance data | The short text describes the object sufficiently | |
| 29 | 028 |
IUCLID substance data assigned to invalid substance (RECN=&1) | The short text describes the object sufficiently | |
| 30 | 029 |
No primary key (RECNROOT) of IUCLID substance data supplied in update | The short text describes the object sufficiently | |
| 31 | 030 |
Primary key (RECNROOT=&1) of IUCLID substance data invalid in update | The short text describes the object sufficiently | |
| 32 | 031 |
Substance unlinked | The short text describes the object sufficiently | |
| 33 | 032 |
Substance cannot be unlinked | The short text describes the object sufficiently | |
| 34 | 033 |
Substance synchronization completed | The short text describes the object sufficiently | |
| 35 | 034 |
RFC destination is not defined in environment parameter &1 | The short text describes the object sufficiently | |
| 36 | 035 |
No IUCLID instance is defined (for logical port) in Customizing | The short text describes the object sufficiently | |
| 37 | 036 |
Substance not found or not linked to IUCLID | The short text describes the object sufficiently | |
| 38 | 037 |
IUCLID substance data record already created for substance (RECN=&1) | The short text describes the object sufficiently | |
| 39 | 038 |
Encountered SYSTEM_FAILURE in RFC call; check remote system | Object does not appear in a screen | |
| 40 | 039 |
Encountered COMMUNICATION_FAILURE in RFC call; check RFC connection | Object does not appear in a screen |
History
| Last changed on/by | |
20141109 | SAP |
| SAP Release Created in | 110_600 |
