CPCL - Service Layer for Plans, Sequences, Operations, and Subober.
The following messages are stored in message class CPCL: Service Layer for Plans, Sequences, Operations, and Subober..
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 | ***************************** Header *********************************** |
| 001 | Change task list: Consistency check was not successful |
| 002 | Create task list: Consistency check was not successful |
| 003 | Task list: Error during key assignment |
| 004 | No long text exists for the header |
| 005 | Task list usage has not been defined |
| 006 | Task list &1 &2 &3 already exists |
| 007 | You must assign the group counter manually |
| 008 | Header invalid |
| 009 | Task list & & & is locked by user & |
| 010 | Unlock header of the reference operation set &2 &3 |
| 011 | Header invalid |
| 012 | Header invalid on key date |
| 013 | No authorization to create task lists |
| 014 | Enter task list type |
| 015 | Header cannot be locked (lock management error) |
| 016 | Header is not locked |
| 017 | Plan can only be changed with a change number |
| 018 | No authorization to change task lists |
| 020 | Header cannot be determined, due to lack of identifying data |
| 021 | Task list header not loaded |
| 022 | Planner group &1 is not defined in plant &2 |
| 023 | No free task list group available for simulation mode |
| 100 | ***************************** Sequence ******************************** |
| 101 | Consistency check not successful when changing the sequence |
| 102 | Consistency check not successful when creating sequence |
| 103 | Error in key allocation for sequence |
| 104 | Long text for sequence missing |
| 105 | Sequence & exists already |
| 106 | Sequence invalid |
| 107 | Assign sequence number manually |
| 108 | Sequence & was created |
| 110 | Alternative or parallel sequences are not allowed for this task list type |
| 111 | Sequence invalid |
| 112 | Could not delete the standard sequence |
| 113 | Could not delete reference sequence |
| 114 | Sequence invalid on key date |
| 115 | Sequence cannot be locked (lock management error) |
| 116 | Sequence dependencies cannot be updated |
| 120 | Sequence cannot be determined, due to lack of identifying data |
| 121 | Sequence task list header invalid or not loaded |
| 122 | Defect cannot be determined, due to lack of identifying data |
| 123 | Only catalog type 9 can be used for defects |
| 124 | Code Group &1 not found |
| 125 | Code &1 of Group &2 not found |
| 126 | Defects can only be added to rework routings |
| 200 | ***************************** Operation ********************************* |
| 201 | Access to table &1 occured in programm &2 with an invalid index |
| 202 | Consistency check not successful when changing operation & |
| 203 | Consistency check not successful when creating operation & |
| 204 | Access to table &1 in program &2 with invalid key |
| 205 | Operation: Error during key assignment |
| 206 | No long text for the operation exists |
| 207 | The task list applications for the operations are not compatible |
| 208 | Operation &1 already exists |
| 209 | Operation is invalid |
| 210 | Numeric operation ID can only be assigned by the system |
| 211 | Consistency check not successful when creating a reference |
| 212 | Unlock operations in reference operation set &2 &3 |
| 213 | Operation is invalid |
| 214 | You must enter a key date, to cumulate standard values |
| 215 | Standard value cumulation not allowed in operation &1 |
| 216 | Standard value cumulation in operation &1 only allowed in the order |
| 217 | Operation invalid on key date |
| 218 | Operation cannot be locked (lock management error) |
| 219 | Operation &1 is not locked |
| 220 | Operation cannot be determined, due to lack of identifying data |
| 221 | Reduction strategy does not exist |
| 222 | Operation sequence invalid or not loaded |
| 223 | Operation is not loaded |
| 224 | Consistency check when assigning operation & to sequence & failed |
| 225 | Operation &1 in sequence &2 is not permitted |
| 226 | Operation dependencies cannot be updated |
| 228 | Suboperation is not unique |
| 229 | Operation instead of suboperation |
| 230 | Task list type & does not allow references to routings |
| 231 | Suboperation instead of operation |
| 232 | Language key & is not available |
| 233 | Operation unit of measure & does not exist |
| 234 | Printer for shop papers & is not available |
| 235 | Suitability & is not available |
| 236 | Set up group category &1 in plant &2 is not available |
| 237 | Set up group key &1 for set up group cat. &2 in plant &3 not available |
| 238 | Wage group & not available |
| 239 | The reference date for start of suboperation & is not scheduled |
| 240 | The unit for offset to start & does not exist |
| 241 | The reference date for finish of suboperation & is not scheduled |
| 242 | The unit for offset to finish & does not exist |
| 243 | The account number for vendors or creditors & does not exist |
| 244 | The currency key & does not exist |
| 245 | Material group & does not exist |
| 246 | The unit normal duration & does not exist |
| 247 | Purchasing group for external processing & does not exist |
| 248 | The unit minimum duration & does not exist |
| 249 | Date restriction & for the start of an operation does not exist |
| 250 | **************************Sub-operation ********************************* |
| 251 | Sub-operation invalid on key date |
| 252 | Sub-operation cannot be locked (lock management error) |
| 253 | Sub-operation & already exists |
| 254 | Target operation can not be locked |
| 255 | Sub-operation dependencies cannot be updated |
| 256 | Operation for the suboperation invalid or not loaded |
| 270 | *************Continuing Operation Checks****************************** |
| 271 | Date restriction & for the end of an operation does not exist |
| 272 | The unit work & does not exist |
| 273 | The distribution function for capacity requirement & does not exist |
| 274 | The usage & does not exist |
| 275 | Company code & does not exist |
| 276 | The requesting cost center & does not exist |
| 277 | Controlling area & does not exist. |
| 278 | The capacity type & does not exist |
| 279 | The calculation key & does not exist |
| 280 | The activity type & does not exist |
| 281 | The grid unit of measure & does not exist |
| 282 | The system condition & does not exist |
| 283 | The assembly & does not exist |
| 284 | The BOM type & does not exist |
| 285 | Factory calender Id & does not exist |
| 286 | Earliest possible oper. / latest possible oper.: only 1 or 2 possible |
| 287 | The performance efficiency rate key & does not exist |
| 288 | The key for rounding and additional values & does not exist |
| 289 | The order unit & for the operation does not exist |
| 290 | Priority & does not exist |
| 291 | The data entry view & does not exist |
| 292 | The type of calculation for CAP during order creation & does not exist |
| 293 | The summarization type & does not exist |
| 294 | The reference point & for the BOM transfer does not exist |
| 295 | Operation is already deleted |
| 296 | Relevancy to costing indicator & does not exist |
| 297 | Inconsistent component assignment resulting from assigning oper. to seq. |
| 298 | Operation was already assigned to this sequence |
| 299 | Reassignment only permitted with the same change number |
| 300 | ************************ Message Collector ****************************** |
| 301 | No entry has been made for message &1&2(&3) in the message collector &4 |
| 302 | Message collector &1 could not be installed |
| 303 | Unknown message collector &1 |
| 304 | Message collector is already installed |
| 305 | &1 not set as an object for message collector &2 |
| 306 | Message collector &1 could not be closed |
| 307 | Message collector &1 not reset |
| 308 | Messages that have already been collected for object &1 will be lost |
| 309 | Object &1 is not supported by message collector &2 |
| 310 | You do not have authorization for the message collector |
| 320 | ***************************** Operation ********************************* |
| 321 | Indicator for costing relevancy was changed according to control key |
| 400 | ************************ Sub-Operation ********************************** |
| 401 | Consistency check not successful when changing sub-operation & |
| 402 | Consistency check not successful when creating sub-operation & |
| 406 | Sub-routine long text is missing |
| 501 | Item dependencies cannot be updated |
| 502 | Class is locked by another user and cannot be copied |
| 800 | ************************* Others ************************************** |
| 801 | System error & in function module & (&) -> F1 |
| 802 | System error |
| 803 | Field & contains a negative value - the value has been changed |