DPR_BAPI - Messages for BAPIs in Project Management
The following messages are stored in message class DPR_BAPI: Messages for BAPIs in Project Management.
It is part of development package DEVELOPMENT_PROJECTS_BAPI in software component PPM-PRO-EXT-API. This development package consists of objects that can be grouped under "Project Management - BAPI".
It is part of development package DEVELOPMENT_PROJECTS_BAPI in software component PPM-PRO-EXT-API. This development package consists of objects that can be grouped under "Project Management - BAPI".
Message Nr ▲ | Message Text |
---|---|
000 | ===== Find BAPI ========================================================= |
001 | Search help &1 does not exist |
002 | Search help &1 is not an elementary search help |
003 | No hits exist in search help &1 for object category '&2' |
004 | Search help &2 does not contain search criterion &1 |
005 | Search criterion &1 is not a selection parameter in search help &2 |
006 | Search was canceled after &1 hits were found |
007 | No valid search criteria exist for search help &1 |
008 | &2 hits determined for search help &1 from the specified search criteria |
009 | No hits determined for search help &1 from the specified search criteria |
010 | Search help &1 cannot be used for the BAPI method 'Search' |
011 | Search criterion does not have a field name and cannot be used |
012 | Search criteria &1 is not used |
020 | ===== BAPI authorization ================================================ |
021 | Authorization activity &1 is invalid |
022 | Authorization activity &1 is not permitted for object category '&2' |
023 | Invalid authorization holder &1 |
024 | Authorization holder &1 '&2' does not exist or does not have auth. |
025 | Authorization holder &1 '&2' is not unique |
026 | &1 '&2': No error for &4 authorization activity '&3' |
027 | &1 '&2': No authorization for &4 authorization activity '&3' |
028 | &1 '&2': Error in &4 authorization activity '&3' |
029 | Authorization activity &3 '&1' is not possible for user &2 |
030 | Internal error occurred when setting an authorization activity |
031 | Authorization object &1 '&2' does not exist: &3 &4 not possible |
032 | Activity '&3' is not set for &1 '&2': Cannot reset |
033 | Authorization activity '&3' is already set for &1 '&2' |
034 | Current user does not have administration authorization |
035 | Current user is the last user with administration authorization |
036 | No authorization can be set for the folder on level 1 |
037 | Document-specific authorizations are no longer supported |
040 | ===== BAPI status ======================================================= |
041 | Current object is not linked to status management |
042 | Business transaction &1 is unknown |
043 | Business transaction &1 &2 is not allowed |
044 | Current object does not have a status profile: No user status possible |
045 | Business transaction &1 requires a user status |
046 | Business transaction &1 ignores user status &2 |
047 | Business transaction &1 was executed successfully |
048 | Status profile &1 is already active for current object |
049 | No further changes can be made to status profile for current object |
050 | No active status profile - deletion is not necessary |
051 | Status profile &1 cannot be used for the current object |
052 | Status profile &1 was set successfully |
053 | No changes are made (no data in BAPI interface) |
054 | Document status &1 from the BAPI interface is not permitted |
055 | Document status &1 is already active |
056 | Document status &1 cannot be set at present |
057 | Document statuses are not available for the document |
060 | ===== BAPI general GET messages ========================================= |
061 | Detailed data was determined |
062 | Detailed data was not determined |
063 | Statuses were determined |
064 | Statuses were not determined |
065 | Names were determined |
066 | Names were not determined |
067 | Long texts were determined |
068 | Long texts were not determined |
069 | Dependent objects were determined |
070 | No dependent objects were determined |
071 | &1 &2 is not assigned to &3 &4 |
072 | Extensions were determined |
073 | Extensions were not determined |
074 | Authorizations were determined |
075 | Authorizations were not determined |
076 | Data was determined |
077 | Responsible role was not determined |
078 | Assignment of role to project failed |
100 | ===== BAPI general services ============================================= |
101 | No object of object category '&2' exists for GUID &1 |
102 | GUID &1 is an object of object category '&2' instead of object cat. '&3' |
103 | System does not support object category '&1' |
104 | BOR object &1 '&2' (&3): BAPI method &4 |
105 | Internal error occurred when updating |
106 | Enter the GUID of the object you want to process |
107 | No changes are made (empty update structure) |
108 | Field &1 is ignored in change mode |
109 | Date is not in YYYYMMDD format |
110 | Field &1: Value &2 does not exist; check your entry |
111 | Field &1: Value &2 is invalid; check your entry |
112 | No data was changed |
113 | Valid data is changed after saving successfully |
114 | Object is created with GUID &1 after it has been successfully saved |
115 | Object is deleted after it has been successfully saved |
116 | Scheduling has been carried out |
117 | Project is unloaded |
118 | Project must not be unloaded |
119 | Project cannot be unloaded |
120 | Error occurred when creating object link: &1 |
121 | Error occurred when changing object link: &1 |
122 | Field &1 is ignored in change mode, reason: &2 |
123 | Manual severity '&1' (&2) was set |
124 | Internal error occurred when invalidating the object created |
125 | Internal error occurred when invalidating the changed object |
126 | Error occurred during creation: Object is not created |
127 | Errors occurred when changing the object: The object is not changed |
131 | No detailed data could be determined for the folder on level 1 |
132 | Folder on level 1 cannot be changed or deleted |
133 | Severity values were aggregated |
134 | Threshold values were checked |
135 | Project template is unloaded |
136 | Project template must not be unloaded |
137 | Project template cannot be unloaded |
138 | Incorrect GUID in BAPI Interface (Field &1) |
139 | Incorrect predecessor phase &1 |
140 | Changes have already been made: Action &1 is not possible |
141 | It is only possible to move objects within your own project definition |
142 | It is only possible to move objects within your own template |
143 | Folder &1 is already being edited by &2: action is not possible |
144 | Task is moved after it has been successfully saved |
145 | Task cannot be moved to itself |
146 | A relationship with &1 as predecessor and &2 as successor already exists |
147 | Task cannot be related to itself |
148 | &1 and &2 cannot be used together in the same relationship |
149 | Error occurred when creating the relationship |
150 | Error occurred when changing the relationship |
151 | Error occurred when deleting the relationship |
152 | Time interval of relationship does not only contain numbers |
153 | Factory calendar &1 does not exist |
154 | Object is created after saving successfully |
155 | Predecessor and/or successor do not allow any changes to the relationship |
156 | No relationship exists between &1 and &2 |
157 | BOR object &1 '&2': BAPI method &3 |
158 | BOR object &1: BAPI method &2 |
159 | Language key &1 does not exist |
160 | Checklist header is moved after it has been successfully saved |
161 | Error occurred when creating the folder, reason: &1 |
162 | Error occurred when changing the folder, reason: &1 |
163 | Error occurred when deleting the folder, reason: &1 |
164 | Error occurred when creating the document, reason: &1 |
165 | Error occurred when changing the document, reason: &1 |
166 | Error occurred when updating the document, reason: &1 |
167 | Error occurred when deleting the document, reason: &1 |
168 | Document is already being edited by user &1 |
169 | BOR object &1 (&2): BAPI method &3 |
170 | Checklist reference has already been resolved |
171 | Checklist reference cannot be resolved |
172 | It is not possible to resolve a checklist reference in a project template |
173 | Internal error occurred in rollback |
174 | cFolders system &1 does not exist |
175 | Connection to cFolders system &1 is not available |
176 | Your user ID is unknown in cFolders system &1 |
177 | No authorization to create collaborations in cFolders system &1 |
178 | Error occurred when converting URL to cFolders collaboration, reason: &1 |
179 | Internal error: Incorrect parameter transferred |
180 | Enter a valid collaboration or collaboration folder |
181 | Collaboration or folder is already assigned to the project element |
182 | Collaboration for collaboration folder &1 could not be determined |
183 | Rollback work was carried out successfully |
184 | Internal error occurred for action &1 |
185 | Action &3 for &1 '&2' was performed successfully |
186 | Action &3 could not be performed for &1 '&2' |
187 | There are no main objects for action &1 |
188 | Collaboration cannot be assigned, minimum 'write' authorization required |
189 | Error occurred when assigning collaboration, reason: &1 |
190 | Name of collaboration or folder cannot be initialized |
191 | Collaboration/folder cannot be changed, reason: &1 |
192 | Deletion of collaboration/folder link: &1 |
193 | No cFolders system has been defined in Customizing |
194 | Enter one of the cFolders systems specified in Customizing |
195 | cFolders system &1 is not maintained in Customizing |
196 | Field &1: Value &2 does not exist in language &3; check your entry |
197 | Checklist template is being unloaded |
198 | Checklist template does not have to be unloaded |
199 | Checklist template cannot be unloaded |
200 | Project was successfully assigned to the program |
201 | Assignment of project to program was successfully deleted |
202 | Phase was successfully assigned to the program phase |
203 | Assignment of phase to program phase was successfully deleted |
204 | Subproject was successfully assigned to the (master) task |
205 | Assignment of subproject to task was successfully deleted |
206 | Action &3 is not required for &1 '&2' |
207 | Role is assigned to obj. category '&1' instead of obj. cat. '&2' |
208 | &1 '&2' cannot be changed |
209 | Time conversion to &1 caused a numerical overflow |
210 | Time was converted from &1 &2 to &3 &4 - rounding errors are possible |
211 | Time conversion delivers 0 &1 |
212 | It is not possible to convert &1 into a recognized time unit |
213 | Invalid time unit '&1' was entered |
214 | Invalid ISO time unit '&1' was entered |
215 | Simulation version could not be created |
216 | Snapshot version could not be created |
217 | Object cannot be loaded in display mode |
218 | Object cannot be loaded in change mode |
219 | Object was successfully loaded in display mode |
220 | Object was successfully loaded in change mode |
221 | Automatic assignment of phase to program phases was successful |
222 | Number of deleted messages in the application log: &1 |
223 | Link type '&1' is not permitted |
224 | No changes are made for object &1 (update structure is empty) |
225 | No data from object &1 was changed |
226 | Valid data of the object &1 is changed after saving successfully |
227 | Object &1 is created with GUID &2 after saving successfully |
228 | Internal error occurred when invalidating the changed object &1 |
229 | Error when making changes: Object &1 is not changed |
230 | Objects directly related in a hierarchy cannot have any relationships |
231 | Object ID contains invalid character(s) |
232 | The status change only takes effects after the project has been saved |
233 | Original language key &1 is invalid |
240 | Object type &1 not active or not allowed |
260 | Function &1 is no longer supported |
500 | ===== BAPI BUS2177 ========================================== |
501 | Resource is already assigned as a candidate |
502 | Resource is already assigned to this role |
503 | Business partner with GUID &1 is invalid |
504 | Assignment of task &1 failed |
505 | Business partner &1 &2 with ID &3 is invalid |
506 | Business partner with ID &1 is invalid |
700 | ===== BAPI messages for approval ======================================== |
701 | Approval already exists and cannot be created again |
702 | Error occurred when creating approval |
703 | Approval does not exist yet and therefore cannot be made into versions |
704 | Only approvals that are canceled or rejected can be made into versions |
705 | Error occurred when creating a new version of approval |
706 | Error occurred when starting approval |
707 | According to the phase type, the phase does not require an approval |
708 | Error occurred when canceling approval |
709 | Error occurred when rejecting approval |
710 | Error occurred when granting the approval |
711 | Error occurred when repeating the approval |
712 | System cannot start approval because approval does not exist yet |
713 | System cannot cancel approval because approval does not exist yet |
714 | System cannot reject approval because approval does not exist yet |
715 | System cannot grant approval because approval does not exist yet |
716 | System cannot repeat approval because approval does not exist yet |
717 | System cannot change approval because approval does not exist yet |
718 | Approval cannot be changed |
719 | Name of approval cannot be changed |
720 | Approval does not exist yet |
721 | Role is a required entry field for creating individual approvals |
722 | Individual approval for role &1 already exists |
723 | Individual approval &1 does not exist for current phase or approval |
724 | Role &1 does not exist in current project |
725 | Decision maker &1 does not exist in the current project |
726 | Decision maker &1 does not exist in role &2 |
727 | Error occurred when creating the individual approval |
728 | Error occurred when reading project element |
729 | To delete the objects, choose "Delete" again |
800 | ===== BAPI General EXTENSION Messages =============================== |
801 | No extension editing; structure name &1 is expected instead of &2 |