SAP ABAP Message Class /DSD/ST (Message class for tour status)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
LE-DSD-ST (Application Component) Tour Status
⤷
/DSD/ST (Package) DSD Tour Status
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
LE-DSD-ST (Application Component) Tour Status⤷
/DSD/ST (Package) DSD Tour Status 
Attributes
| Message class |  |
/DSD/ST |
| Short Description |  |
Message class for tour status |
| Changed On |  |
20130531 |
| Last Changed At |  |
104751 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Visit plan type &1 is not possible. Only "preseller"! | The short text describes the object sufficiently | |
| 2 | 001 |
One scenario can only be assigned to one connecting medium! | The short text describes the object sufficiently | |
| 3 | 002 |
Scenario &1 is assigned already to one sales scenario! | The short text describes the object sufficiently | |
| 4 | 003 |
Shipment Type &1/Transportation Point &2 is not relevant for DSD! | The short text describes the object sufficiently | |
| 5 | 004 |
Scenario &1 is assigned already to one delivery scenario! | The short text describes the object sufficiently | |
| 6 | 005 |
Visit plan type &1 is not relevant for DSD! | The short text describes the object sufficiently | |
| 7 | 006 |
Every status ID is allowed once a scenario! | The short text describes the object sufficiently | |
| 8 | 007 |
Visit list number &1 in structure IS_STATUS is false! | The short text describes the object sufficiently | |
| 9 | 008 |
Shipment number in IS_STATUS and IS_VTTK is differently! | The short text describes the object sufficiently | |
| 10 | 009 |
Visit list number in IS_STATUS and IS_VLH is differently! | The short text describes the object sufficiently | |
| 11 | 010 |
Once of the structures (IS_STATUS, IS_VTTK, IS_VLH) must be filled! | The short text describes the object sufficiently | |
| 12 | 011 |
Shipment &1 not found! | The short text describes the object sufficiently | |
| 13 | 012 |
Scenario to shipment type &1/&2 and medium &3 is not maintained! | The short text describes the object sufficiently | |
| 14 | 013 |
Visit list &1 not found! | The short text describes the object sufficiently | |
| 15 | 014 |
Scenario to visit plan type &1 and medium &2 is not maintained! | The short text describes the object sufficiently | |
| 16 | 015 |
Profile to scenario &1 is not maintained! | The short text describes the object sufficiently | |
| 17 | 016 |
One of the parameters (TOURID, TKNUM/SHIPMENT, VLID) must be filled! | The short text describes the object sufficiently | |
| 18 | 017 |
Tour ID &1 is not available! | The short text describes the object sufficiently | |
| 19 | 018 |
The new status ID &1 is not equal to the current status ID &2! | The short text describes the object sufficiently | |
| 20 | 019 |
The tour &1 could not be locked for status &2! | The short text describes the object sufficiently | |
| 21 | 020 |
The status ID &1 isn't maintained in the scenario &2! | The short text describes the object sufficiently | |
| 22 | 021 |
For the status ID &1 an activty can't be maintained! | The short text describes the object sufficiently | |
| 23 | 022 |
Tourstatus: Predecessor status ID &1 to new status ID &2 is wrong! | The short text describes the object sufficiently | |
| 24 | 023 |
Return to status ID &1 is not allowed! (current status ID &2) | The short text describes the object sufficiently | |
| 25 | 024 |
FM IN UPDATE TASK. Start of activity is not possible! | The short text describes the object sufficiently | |
| 26 | 025 |
Parameter NO_COMMIT is flagged! Start of activity is not possible! | The short text describes the object sufficiently | |
| 27 | 027 |
The status data of tour &1 could not be deleted! | The short text describes the object sufficiently | |
| 28 | 028 |
The history status data of tour &1 could not be deleted! | The short text describes the object sufficiently | |
| 29 | 029 |
No tour scenario found! | The short text describes the object sufficiently | |
| 30 | 030 |
You are not authorized for this functionality. | The short text describes the object sufficiently | |
| 31 | 031 |
No data selected! | The short text describes the object sufficiently | |
| 32 | 032 |
Please, select only one tour ID! | The short text describes the object sufficiently | |
| 33 | 033 |
Please, select a header record! | The short text describes the object sufficiently | |
| 34 | 034 |
IDOCs to the tour &1 cannot be started with status ID &2! | The short text describes the object sufficiently | |
| 35 | 035 |
The visit list &1 with status ID &2 could not be deleted! | The short text describes the object sufficiently | |
| 36 | 039 |
The new tour status &1 is higher than the maximal allowed status &2! | The short text describes the object sufficiently | |
| 37 | 040 |
The tour is already assigned! Display mode possible only! | The short text describes the object sufficiently | |
| 38 | 041 |
The tour is already assigned! Delete not possible! | The short text describes the object sufficiently | |
| 39 | 042 |
The sequence must be higher than the presequence! | The short text describes the object sufficiently | |
| 40 | 043 |
The status ID &1 isn't maintained. One is obligatory to mobile scenario. | The short text describes the object sufficiently | |
| 41 | 044 |
Enter please one scenario! | The short text describes the object sufficiently | |
| 42 | 045 |
Enter please one medium! | The short text describes the object sufficiently | |
| 43 | 046 |
Function is not allowed! See the application log! | The short text describes the object sufficiently | |
| 44 | 047 |
No Application Log found. | The short text describes the object sufficiently | |
| 45 | 048 |
Application Log cannot be displayed due to missing authorization | The short text describes the object sufficiently | |
| 46 | 049 |
Enter please one shipment type! | The short text describes the object sufficiently | |
| 47 | 050 |
Enter please one transportation planning point! | The short text describes the object sufficiently | |
| 48 | 051 |
The tour is already assigned! No download! | The short text describes the object sufficiently | |
| 49 | 052 |
Locking for Tour &1, Status &2, Program &3, User &4 | The short text describes the object sufficiently | |
| 50 | 053 |
The status ID &1 isn't defined! | The short text describes the object sufficiently | |
| 51 | 054 |
Only Update Modules are allowed! | The short text describes the object sufficiently | |
| 52 | 055 |
Scenario &1 - You are not authorized for this functionality. | The short text describes the object sufficiently | |
| 53 | 056 |
The status data of tour &1 deleted! | The short text describes the object sufficiently | |
| 54 | 057 |
The tour met the first status ID - Return is not possible! | The short text describes the object sufficiently | |
| 55 | 058 |
Return from the current status ID &1 to ID &2 is not allowed! | The short text describes the object sufficiently | |
| 56 | 059 |
Transportation Point &1 / Connection Type &2 is not relevant for DSD! | The short text describes the object sufficiently | |
| 57 | 060 |
Sequence &1 does not exist. | The short text describes the object sufficiently | |
| 58 | 061 |
Sequence &1 can not be deleted - is presequence of sequence &2 | The short text describes the object sufficiently | |
| 59 | 062 |
Sequence &1 can not be deleted - is max. sequence of sequence &2 | The short text describes the object sufficiently | |
| 60 | 063 |
Max Sequence must be higher than sequence. | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 603 |
