/SMB/Q2P - Messages related to Q2P transport
The following messages are stored in message class /SMB/Q2P: Messages related to Q2P transport.
It is part of development package /SMB/Q2P_LIFECYCLE in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Lifecycle in new Q2P".
It is part of development package /SMB/Q2P_LIFECYCLE in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Lifecycle in new Q2P".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 001 | The active lifecycle project could not be determined |
| 002 | There is no lifecycle or business change project for consolidation |
| 003 | You are not authorized to consolidate the transport requests |
| 004 | Activate the new Q to P functionality to execute this step |
| 005 | Consolidation of workbench requests |
| 006 | Consolidation of customizing requests |
| 007 | No transport requests found for consolidation |
| 008 | Merged request containing all source requests: &1 |
| 009 | Merging request: &1 |
| 010 | Use transport consolidation only in project or lifecycle client |
| 011 | Setting transport attribute: &1 = &2 |
| 012 | Check transport &1 - Contains content artifacts, but not mergable |
| 013 | No workbench requests found to be merged |
| 014 | No customizing requests found to be merged |
| 015 | Releasing transport &1 |
| 016 | Transport consolidation cannot be executed |
| 017 | Transport consolidation was not executed |
| 018 | Could not determine transport target for consolidation |
| 019 | Activation is not allowed in current client of type &1 |
| 020 | Internal error: AIM trigger object put into &1 instead of &2 |
| 021 | Could not find transport attributes (Business or Lifecycle Project) |
| 022 | The SPRO project &1 cannot be used for new transport requests |
| 023 | Select at least one transport |
| 024 | The SPRO project &1 does not exist |
| 025 | Marking transports as not relevant for future consolidation |
| 026 | Transport &1 is marked as not relevant for consolidation |
| 027 | Failed to mark transport &1 as not relevant for consolidation |
| 028 | Failed to change user of transport &1 to &2 |
| 029 | Release of customer content data |
| 030 | You are not authorized to perform this function |
| 031 | Internal error in semaphore framework |
| 032 | Action cannot be performed; lifecycle operations running |
| 033 | Action is locked; please try again later |
| 034 | Another user is performing this action; please try again later |
| 035 | The release of a semaphore is locked |
| 036 | A foreign semaphore is blocking the semaphore release |
| 037 | Semaphore could not be unlocked because it does not exist |
| 038 | Cannot find semaphore &1 for release |
| 039 | Semaphore &1 was unlocked successfully |
| 040 | Restart this operation when other operations are finished |
| 041 | If no other operation is running, use transaction /SMB/Q2P_SEMM |
| 042 | Workbench request &1 created for content artifact transport |
| 043 | &1 transport(s) will be marked as not relevant |
| 044 | &1 transport(s) will be consolidated |
| 045 | No existing active Lifecycle Project |
| 046 | The active Lifecycle Project has the wrong status &1 |
| 047 | No existing active Business Change Project |
| 048 | The active Business Change Project has the wrong status &1 |
| 049 | View transport &1 |
| 050 | Q to P projects only supported with new Q to P transport functionality |
| 051 | Authorization missing to display Q to P projects |
| 052 | No existing active Lifecycle Project |
| 053 | Consolidation of transport requests |
| 054 | Authorization missing to create Lifecycle Project |
| 055 | Q to P project is locked by user &1 |
| 056 | Q to P project cannot be locked |
| 057 | An active Lifecycle Project already exists |
| 058 | Error while creating Q to P project ID |
| 059 | Client &1 is neither a project client nor a lifecycle client |
| 060 | Release process already started for Business Change Project in client &1 |
| 061 | Current client is not reference client of linked BCP; release not started |
| 062 | The active BCP is not in status 'In Progress', no changes allowed |
| 063 | Project Data could not be read |
| 064 | Client &1 is not a project client; changes not allowed |
| 065 | No existing active Business Change Project for reference client &1 |
| 066 | Q to P project cannot be changed into status &1 |
| 067 | Authorization missing to change Q to P project |
| 068 | Lifecycle Project linked to Business Change Project &1 |
| 069 | BCP can only be changed in corresponding reference client &1 |
| 070 | Client &1 is not a lifecycle client |
| 071 | Client &1 is not a project client |
| 072 | There is no active Business Change Project |
| 073 | An active Business Change Project already exists in client &1 |
| 074 | Project type &1 is not valid |
| 075 | Lifecycle client cannot be found |
| 076 | An active lifecycle project exists; status change not possible |
| 077 | Release process of BCP started; no lifecycle activity in lifecycle client |
| 078 | Q to P info client cannot be determined |
| 079 | Client copy pending in client &1; no lifecycle activity allowed |
| 080 | More than one Business Change Project not in status 'In Progress' |
| 081 | Lifecycle Project status must be changed with matching BCP |
| 082 | Use in productive system not allowed |
| 083 | No usable transport request exists; activation not allowed |
| 084 | No usable transport request exists; activation not allowed |
| 085 | Q system in initial state - Lifecycle is running in project client only |
| 086 | Enter a project ID |
| 087 | Specified project does not exist |
| 088 | Specified request status is not supported |
| 089 | Request &1 does not exist or is not valid |
| 090 | Request &1 is neither a workbench request nor a customizing request |
| 091 | Transport target &1 does not correspond to default transport target |
| 092 | Source client &1 of request does not match source client of project |
| 093 | Assigning new requests no longer possible |
| 094 | Modifiable transport requests exist; status change not possible |
| 095 | Copy object list to Transport of Copies &1 |
| 096 | Transport requests cannot be created; job scheduling failed |
| 097 | Creation of transport requests aborted |
| 098 | Q to P project could not be created |
| 099 | Specified request type is not supported |
| 100 | Tasks could not be created; job scheduling failed |
| 101 | Releasing tasks |
| 102 | Tasks could not be created; job scheduling failed |
| 103 | New task for user &1 created in transport request &2 |
| 104 | Current client is lifecycle client; no existing Lifecycle Project |
| 105 | Current client is project client; no existing Business Change Project |
| 106 | No existing Lifecycle Project in status 'In Progress'; no changes allowed |
| 107 | Modfications (such as activation) only allowed in project client |
| 108 | Report &1 cannot be executed in dialog |
| 109 | Transport consolidaton could not be started |
| 110 | Transport consolidation could not be started; job scheduling failed |
| 111 | Lifecycle Project status not 'In Progress'; cannot be released |
| 112 | No transportable changes exist; Lifecycle Project set to 'Completed' |
| 113 | Instance of class /SMB/CL_Q2P_PROJ_TRANSP_ASSGN could not be created |
| 114 | Checking whether new transport requests / tasks need to be created |
| 115 | Specify either a project ID or a project type |
| 116 | Copying object list of transport &1 to transport &2 |
| 117 | Opening of the job failed |
| 118 | Closing of the job name &1 number &2 failed |
| 119 | Submission of the job name &1 number &2 failed |
| 120 | Starting job name &1 number &2 |
| 121 | Deletion of the job failed |
| 122 | Background job: Starting release of transport &1 |
| 123 | Transport &1 released; waiting for export |
| 124 | Release of transport &1 failed with errors; changing project status to &2 |
| 125 | Transport &1 released and exported; changing project status to &2 |
| 126 | Export of transport &1 failed; changing project status to &2 |
| 127 | Could not find transport request &1 |
| 128 | LCP with assigned transp. requests cannot be released in project client |
| 129 | Transport &1 can only be released via Q to P transport consolidation |
| 130 | Transport request &1 is assigned to Q to P project &2 |
| 131 | Use transaction /SMB/Q2P_PM to consolidate the transports |
| 132 | Lifecycle without Business Change Project not possible in project client |
| 133 | Project has been successfully created. |
| 134 | Transport release has started. Refresh to see current status. |
| 135 | Starting transport consolidation; extended processing time expected |
| 136 | Transport request attributes cannot be replaced |
| 137 | Transport request attributes cannot be replaced; job scheduling failed |
| 138 | Transport &1 released and exported |
| 139 | Q2P Project is not in Status &1, no follow-up actions performed |
| 140 | Transport &1 could not be released; job scheduling failed |
| 141 | Latest Transport of Copies (&1) is not released |
| 142 | Import of transport &1 failed with errors; changing project status to &2 |
| 143 | Import of transport &1 not finished; status not changed |
| 144 | Release of consolidation request started |
| 145 | Error while starting import of transport &1 |
| 146 | No client of business type 'clean' configured |
| 147 | SPC Request API not available; no service request created |
| 148 | Creation of SPC Service Request failed |
| 149 | Transport request &1 cannot be consolidated; check attributes |
| 150 | Scheduling of SPC Service Request creation failed |
| 151 | Activation running or failed; release of transport not possible |
| 152 | Lifecycle client not ready - no transport requests created |
| 153 | No consolidation transport specified |
| 154 | No Transport of Copies specified |
| 155 | Target or status of consolidation transport &1 not consistent |
| 156 | Target or status of transport of copies &1 is not consistent |
| 157 | No transport requests assigned; Q to P Project set to 'Completed' |
| 158 | Consolidation transport request was not created |
| 159 | Workbench request was not created |
| 160 | Customizing request was not created |
| 161 | Transport of copies was not created |
| 162 | Phase could not be changed |
| 163 | Job for creation of tasks aborted |
| 164 | Job for consolidation of transport requests aborted |
| 165 | Job for adjustment of transport request description and attribute aborted |
| 166 | Consolidation transport &1 was modified; changing project status to &2 |
| 167 | Provide a reason for status change |
| 168 | Transport request &1 not successfully consolidated and deleted |
| 169 | Transp. Requ. &1 is not the latest transp of copies, no follow-up actions |
| 170 | Transp. Requ. &1 is not the latest consol. request, no follow-up actions |
| 171 | Release of transport requests is currently not allowed |
| 172 | Scheduling of project status change to 'Release_Initiated' failed |
| 173 | Log has been created for transport request &1 |
| 174 | Content lifecycle is not complete; status change not possible |
| 175 | Follow up activities required; status change not possible |
| 176 | Foreign key errors exist |
| 177 | There are no foreign key errors |
| 178 | Temporary BCP cannot be released |
| 179 | Checking assigned transport requrest &1 |
| 180 | Required status of Q2P project: &1 |
| 181 | Starting import of consolidation transport &1 |
| 182 | Target status of Q2P project: &1 |
| 183 | Import failed; Health Check created |
| 184 | Current status of Q2P project: &1 |
| 185 | Current Q2P project is of type &1 |
| 186 | Export failed; Health Check created |
| 187 | SCC4 settings inconsistent in client &1; Q2P project release not possible |
| 188 | Import buffer of clean client could not be refreshed |
| 189 | Background job for status change to 'Release Initiated' was aborted |
| 190 | BCP or LCP project &1 deleted |
| 191 | The assignment of TR &1 to project &2 is removed |
| 192 | Project of type &1 cannot be changed in current client |
| 193 | Specify a valid project ID |
| 194 | Specified selection type &1 is not supported |
| 195 | Job for deletion of transport of copies &1 aborted |
| 196 | P-System could not be determined |
| 197 | None of the specified projects exist |
| 198 | Please save your change before switching the project |
| 199 | Please save your change before executing a data refresh |
| 200 | Switch to Edit mode not possible for project with status 'Completed' |
| 201 | Please change the status before saving |
| 202 | You did not change any data |
| 203 | Status of current Q2P project cannot be changed |
| 204 | Status of current Q2P project successfully changed |
| 205 | No data regarding import of transport requests into P-System available |
| 206 | An incomplete update exists |
| 207 | Project data has been changed |
| 208 | Project data could not be changed |
| 209 | No transport request assigned to current Q2P project |
| 210 | Background job &1 for procedure '&2' on Solution &3 scheduled |
| 211 | Release of BCP prevented by external checks |
| 212 | External release checks passed successfully |
| 213 | Current project is not a Business Change Project |
| 214 | External Checks indicator has not been set yet |
| 215 | External Checks indicator has been revoked |
| 216 | Instance of class /SMB/CL_Q2P_PROJ_BATCH_JOB could not be created |
| 217 | Transport request creation only allowed from Q2P project |
| 218 | Owner of transport request &1 cannot be changed (ret-code = &2) |
| 219 | Transport request &1 could not be deleted (ret-code = &2) |
| 220 | Transport requests cannot be deleted; job scheduling failed |
| 221 | Instance of class /SMB/CL_Q2P_RELEASE_TRIGGER could not be created |
| 222 | No details about Health check issue available |
| 223 | Project name is changed |
| 224 | Changing the configuration is currently not allowed; no usable BCP exists |
| 225 | Could not read transport request &1 from import queue |
| 226 | Import is currently running. Please try again later |
| 227 | Content Lifecycle incomplete; restarting lifecycle process |
| 228 | Application Log for handle &1 not found |
| 229 | Specify report to be dispatched |
| 230 | Specified job &1 is unknown and is not supported for dispatching |
| 231 | Job for dispatching background jobs was aborted |
| 232 | P-Provisioning SPC request was already created |
| 233 | P-System requested; deploy your configuration when P-system is available |
| 234 | P-System requested; deploy your configuration when P-system is available |
| 235 | Client &1 not defined properly |
| 236 | Release of configuration changes already triggered |
| 237 | Scheduling of Q2P Status Change Broadcasting failed |
| 238 | Transport request &1 is currently being released |