PPESTATUS - Nachrichten iPPE-Statusverwaltung
The following messages are stored in message class PPESTATUS: Nachrichten iPPE-Statusverwaltung.
It is part of development package CPPESTATUS in software component AP-PPE. This development package consists of objects that can be grouped under "Status of Cross-Application Object Data".
It is part of development package CPPESTATUS in software component AP-PPE. This development package consists of objects that can be grouped under "Status of Cross-Application Object Data".
Message Nr ▲ | Message Text |
|---|---|
| 000 | **************** Customizing ******************************* |
| 001 | Key field must be filled |
| 002 | Object-specific statuses should also be created for the new status |
| 003 | Data records still exist for status &1 |
| 004 | Status &1 still exists as a predecessor status |
| 005 | Object-specific statuses should also be deleted |
| 006 | Status value 'initial' can only exist once |
| 007 | There are still object-specific entries for status &1 with value &2 |
| 008 | Status value 'initial' must not be deleted |
| 009 | Values 'initial' and 'successful' must both exist |
| 010 | Status &1 must have the values 'initial' and 'successful' |
| 011 | Object-specific entries exist for status &1 and precondition &2 |
| 012 | All entries must have the same application type |
| 013 | Default status & has already been defined for this item type |
| 014 | Loop is generated with predecessor status &1 |
| 015 | Status &1 does not have the same object types as status &2 |
| 016 | You must not delete all the object types for status &1 |
| 017 | Object does not exist |
| 018 | Status graphs containing the status ID & have been updated |
| 019 | To delete, you must specify the status ID and the precondition |
| 020 | Preconditions for status ID & have been deleted |
| 021 | The description 'Successful' can exist for only one status value |
| 022 | No status management exists for this iPPE object type |
| 099 | Method &1 is not implemented |
| 100 | ******************* LI/DB ******************** |
| 101 | Status type &1 is not known |
| 102 | Precondition type &1/&2 is not known |
| 103 | Date &1 is not valid |
| 104 | User name &1 is not valid |
| 105 | Date &1 is in the past |
| 106 | Status &1/&2 has been created |
| 107 | Status &1/&2 has been changed |
| 108 | Precondition &1/&2 has been created |
| 109 | Precondition &1/&2 has been changed |
| 110 | Status does not exist |
| 111 | Value &1 is not allowed for the precondition |
| 112 | Status &1 does not exist |
| 113 | Precondition &1/&2 of status graph &3 does not exist |
| 114 | Status graph &2 has been created for object &1 |
| 115 | Status &1 is not assigned to application object &2/&3 |
| 116 | Status &1 already exists for object &2 |
| 117 | Status relevant object &1 does not exist |
| 118 | Predecessor status &1 for status object &2 does not exist |
| 119 | Predecessor status &3 of status &1/&2 is not set to fulfilled |
| 120 | Value &1 is not allowed for status &2 |
| 121 | Status &1/&2 deleted |
| 122 | Status &1/&2 could not be deleted |
| 123 | Status graph &1 deleted |
| 124 | Status graph &1 could not be deleted |
| 125 | Object type &1 is not recognized in 'person responsible' field |
| 126 | You cannot change the class of status '&1' from &2 to &3 |
| 127 | You cannot change the variant of status '&1' to &2 |
| 128 | Change number for status '&1' changed from &2 to &3 |
| 129 | You cannot change the change number for status '&1' from &2 to &3 |
| 130 | Precondition &3 is not fulfilled for status &1/&2 |
| 131 | Precondition &1: Status &2 already set to &3 |
| 132 | No target status found for object type &1, application &2 |
| 133 | Status &1 for &2 was already set to &3 |
| 134 | There is no object type defined for status &1 |
| 135 | Object type &2/&3 assigned to status &1 does not exist |
| 136 | Status '&1' for the GEN node cannot be changed to '&2' |
| 137 | Status graph is not up-to-date; Customizing has changed (TA:OPPESTATUS) |
| 138 | You cannot use this function until you have saved the data |
| 139 | The status object &1 &2 cannot be created; check the data |
| 140 | The status object &1 &2 cannot be changed; check the data |
| 141 | The status object &1 &2 cannot be deleted; check the data |
| 142 | The succeeding status &3 of status &1/&2 has already been set to complete |
| 250 | ************** Interface ****************** |
| 251 | No status logs exist yet; save your data first |
| 252 | Person responsible & does not exist |
| 300 | ************** Status cockpit****************** |
| 301 | Selection only possible using interval and single value |
| 302 | Selection only possible using template and single value |
| 303 | Select at least one field in the workflow area |
| 304 | There is no active version for include & |
| 305 | Create screen "0200" before generating the function group & |
| 306 | Data was saved |
| 307 | Function not possible; status cockpit is already loaded |
| 308 | Function module & should be accessed, but it does not exist |
| 309 | Field catalog cannot be set up; check the data |
| 314 | No status objects exist for this selection |
| 315 | Select the required rows |
| 316 | Select one row only |
| 318 | Release completed |
| 319 | The display has been updated |
| 320 | Workflows have been generated for the selected status objects |
| 321 | Data has been saved |
| 323 | Status object selected without specifying person responsible |
| 324 | Status object is already in the workflow |
| 350 | ******************* Correction *************************** |
| 351 | There is no carrier object for status GUID &; check the data |
| 352 | There is no node with GUID &; check the data |
| 353 | No alternative exists with the GUID &; check your entries |
| 354 | No variant exists with the GUID &; check your entries |
| 355 | Error when saving the status GUID & |