CPCC_DT - Messages in Direct Input for Routings/BOMs
The following messages are stored in message class CPCC_DT: Messages in Direct Input for Routings/BOMs.
It is part of development package CP in software component PP-BD-RTG. This development package consists of objects that can be grouped under "R/3 Application Development: PP Task Lists".
It is part of development package CP in software component PP-BD-RTG. This development package consists of objects that can be grouped under "R/3 Application Development: PP Task Lists".
Message Nr ▲ | Message Text |
|---|---|
| 000 | * General Messages |
| 001 | Session record missing. No processing can take place without this. |
| 002 | The field &1 in structure &2 is a mandatory field |
| 003 | In the structure &1 you have to specify one of the fields &2 or &3 |
| 004 | Errors occured in map &1 of the data &2 |
| 005 | In structure &1 at least one object type has to be selected |
| 006 | The value in &1 of structure &3 must be smaller/equal to the value in &2 |
| 007 | No data was transfered to the import |
| 008 | Data from task list &1 was imported successfully |
| 009 | The valid-from data has been set from today's date |
| 010 | &1 IDOCS were generated |
| 011 | With the selection data IDOC &1 has been created (logical system &2) |
| 100 | * Message when converting from external to internal format |
| 101 | Field &1 of input structure &2 does not exist in output structure &3 |
| 102 | Field &1 of the input structure &2 contains unconverted data |
| 103 | The data in field &1 of the input structure &2 is invalid |
| 104 | The data in field &1 of the input structure &2 has an invalid format |
| 105 | Field &1 of the input structure &2 contains non-numerical characters |
| 106 | Field &1 of the input structure &2 can not be converted |
| 107 | Field &1 of the input structure &2 contains invalid data |
| 108 | The ISO unit &1 could not be uniquely converted |
| 109 | Do not enter ISO unit '&1' and unit '&2' simultaneously |
| 200 | * Message when loading the data using the Engineering Workbench |
| 201 | Installation of the data transfer failed |
| 202 | The defined working environment is inconsistent, loading not possible |
| 203 | The selection period specified is invalid |
| 204 | In order to process with change numbers a key date is required |
| 205 | The task list type in structure &1 does not match the task list type |
| 206 | The component to be assigned has not been completely specified |
| 207 | The operation to be assigned has not been completely specified |
| 208 | The entry of the start and/or end line of the long text is missing |
| 209 | Specified object is not supported by this run |
| 210 | For further processing, the routing entry is missing |
| 211 | The task list to be processed could not be uniquely determined |
| 212 | The object should be deleted without entering a validity |
| 213 | Without a validity entry, the object can not be processed |
| 214 | The object does not exist for scheduled deletion time |
| 215 | The flagged operation is not allowed |
| 216 | The lot size of the task list has been set to the maximum value |
| 217 | A long text assignment is not valid without entering the language |
| 218 | The operation entered is not a group operation |
| 219 | The entry of the start and/or end line of the dep. assignment is missing |
| 220 | Do not enter the start or end line for deletion |
| 221 | Global dependency name cannot be entirely numeric |
| 222 | Local dependency name already used in a different format |
| 223 | Local dependency name is out of range (&1-&2) |
| 224 | The field &1 in structure &2 is a mandatory field for global dependencies |
| 225 | Dependency index is out of range (&1-&2) |