UPS - ALE - Verteilungspaket
The following messages are stored in message class UPS: ALE - Verteilungspaket.
It is part of development package U_P_S in software component CA-GTF-UPS. This development package consists of objects that can be grouped under "ALE Distribution Unit".
It is part of development package U_P_S in software component CA-GTF-UPS. This development package consists of objects that can be grouped under "ALE Distribution Unit".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ****** General ****************************************************** |
| 001 | Posting only possible with ALE distribution unit &1 |
| 002 | &1 |
| 003 | From &1 to &2, &3 cannot be distributed according to the distrib. model |
| 004 | ALE distribution packet &1 has been successfully posted |
| 005 | Only one distribution packet can be posted at a time |
| 006 | Syntax error in message; no header information exists for package |
| 007 | No message passed |
| 008 | An error occurred in ALE inbound processing for message type UPSMAS. |
| 009 | Object message is obsolete in distribution unit &1 |
| 010 | Receipt for ALE distribution unit &1 was posted |
| 011 | ALE distribution packet &1 does not exist |
| 012 | Only one receipt at a time can be processed |
| 013 | &1 messages created |
| 014 | Error while changing the status of the ALE distribution packet |
| 015 | Error writing application log |
| 016 | Job &1 created with ID &2 |
| 030 | ****** Application Log (DSPACKAGE - OUTBOUND) *************************** |
| 031 | Instance &1 for packet &2 |
| 032 | Processed instance &1: &2 |
| 034 | Object list check (&1 objects) : |
| 035 | &1, '&2 &3' (&4) |
| 036 | ....No message has been created |
| 037 | ... A function (I, U, D) is required for the correction entry |
| 038 | ....Message &1 has been created |
| 044 | Generation of messages (&1 objects): |
| 046 | ....Objects of object type &1 are not distributed by packets |
| 047 | ....Error in the outbound processing of object type &1 |
| 048 | ....An instance of object type &1 could not be created |
| 060 | ...Error in asynchronous RFC: outbound processing terminated. |
| 080 | ****** Application Log (DSPACKAGE - INBOUND) **************************** |
| 081 | Processed ALE distribution unit from following packets: |
| 082 | ..Correction packet &1 |
| 083 | ..Original packet &1 |
| 089 | .. &1, '&2 (&3)': Posted with warning (status &4) |
| 090 | Objects in hierarchy level &1 : |
| 091 | ..Objects with errors exist |
| 092 | .. &1, '&2 (&3)': No message found |
| 093 | .. &1, '&2 (&3)' : Already processed (status 53) |
| 094 | .. &1, '&2 (&3)' : Successfully processed (status &4) |
| 095 | .. &1, '&2 (&3)' : Error during processing (status &4) |
| 096 | .. &1, '&2 (&3)' : Set to "obsolete" (status &4) |
| 097 | Preceding unit &1 is not yet posted |
| 098 | Reposting of object of type &1: |
| 099 | Only the manual selection is posted |
| 100 | ALE distribution packet &1 contains the following status: &2 |
| 101 | .. &1, '&2 (&3)' : Already errors in object instance |
| 150 | ****** API / DB Interface ****************************************** |
| 151 | Packet is released; only distribution/status information can be changed |
| 152 | Header data of the distribution packet is incomplete |
| 153 | Not all objects assigned to an object type |
| 154 | Duplicated entries are removed from the object list |
| 155 | No complete reference to the correction for the original packet exists |
| 156 | Original packet &1 does not exist |
| 157 | Original packet &1 can still be changed without correction |
| 158 | The updated ALE distribution packet &1 cannot be changed |
| 159 | Distribution direction of correction (&1) and original packet (&2) differ |
| 160 | The open correction &2 is still available for original packet &1 |
| 161 | A change function is stipulated for objects in corrections |
| 162 | ALE distribution packet number &1 is being used |
| 163 | Object type &1 does not exist |
| 164 | Distribution direction &1 not known (outbound = 1; inbound = 2) |
| 165 | Correction packet is already assigned to original packet &1 |
| 166 | Packet type &1 not known ("O": Original packet; "C": Correction packet) |
| 167 | Object type &1 cannot be distributed into units of type &2 |
| 168 | Distribution model does not allow any distribution of packets to &1 |
| 169 | No changes can be made to the rejected ALE distribution packet &1 |
| 170 | Distribution packet type &1 does not exist |
| 171 | >>>> Processing in Function Module &1 |
| 172 | <<<< Processing in Function Module &1 |
| 173 | An ALE distribution packet number could not be assigned |
| 174 | Changes to ALE distribution packet &1 posted |
| 175 | Owner "&1" is not allowed ("L": Local system; "R": Partner) |
| 176 | ALE distribution packet &1 already exists |
| 177 | Local corrections in inbound processing can only delete objects |
| 178 | Predecessor packet &1 of correction does not exist |
| 179 | Packet name &1 is already used in the unit |
| 180 | After &1 there are still more corrections for original packet &2 |
| 181 | Inbound ALE distribution packets must include message numbers |
| 182 | Status &1 is not intended for direction &2 of the distribution packet |
| 183 | Packet type &1 of distribution unit does not allow corrections |
| 184 | Packet type &1 of dist. unit does not allow corrections in target system |
| 185 | Receipt sent to source system &1 |
| 186 | Receipt could not be sent to source system &1 |
| 187 | The assigned middleware type &2 does not allow distribution to &3 |
| 188 | Invalid change function &1 of object {'I', 'U', 'D'} |
| 189 | No data exists for the object instance of the ALE distribution packet |
| 190 | Key fields &1 used by the instance |
| 191 | Packet type &1 used by the instance |
| 192 | Packet &1 has already been released and can no longer be deleted |
| 193 | Preceding packet &1 has not been distributed |
| 194 | Packet key does not correspond to the current instance |
| 195 | Only packets with direction '1' (outbound) can be distributed |
| 196 | Packet has already been distributed |
| 197 | System only distributes released packets |
| 198 | Status &1 is assigned internally and cannot be set externally |
| 199 | No packet in the distribution unit can be changed |
| 201 | Interval for number range object &1 could not be created |
| 202 | Only inbound packets can be processed |
| 203 | Not all packets released and approved |
| 204 | Packet is locked; only distribution/status information can be changed |
| 205 | Distribution unit must first be approved |
| 206 | Distribution packet has been instantiated for display only |
| 207 | Distribution unit has been instantiated for display only |
| 208 | Distribution Packet Already Exists |
| 209 | Distribution unit does not exist |
| 210 | Specify object key |
| 211 | Specify object type |
| 212 | The unit does not contain packet &1 |
| 213 | Packet type &1 of original packet allows no corrections in source system |
| 214 | Packet name &1 is not allowed for external number assignment |
| 215 | Service is not offered by object type &1 |
| 216 | Object is already in the unit and is updated |
| 217 | Previous entry for this object is deleted |
| 218 | Unit is posted or rejected; you can only display the unit |
| 219 | The service is not provided by the middleware &1 |
| 221 | No object selected |
| 222 | Only objects of released packets are respected |
| 223 | Original is not released |
| 224 | Instance &1 cannot be recreated |
| 225 | Not authorized to create an ALE distribution packet |
| 226 | Not authorized to change an ALE distribution packet |
| 227 | Not authorized to display an ALE distribution packet |
| 228 | Not authorized to delete an ALE deletion packet |
| 229 | Function call terminated with errors |
| 230 | Distribution packet exists already |
| 231 | Distribution packet does not exist |
| 232 | Instance &1 for unit |
| 233 | Job &1, ID &2 is already scheduled for this unit |
| 234 | Date for job scheduling must be in the future |
| 235 | Object &1, '&2 (&3)' cannot be distributed |
| 236 | Parameters for the batch job are incomplete |
| 237 | Posting is stopped after serialization level &1 |
| 238 | Object key &1, '&2 (&3)' is incomplete |
| 239 | &1, '&2 (&3)' were completed |
| 240 | Source objects can only be entered in the original packet |
| 241 | Object type &1 is not planned for source objects |
| 242 | Object &1, '&2 (&3)' cannot be used as a source object |
| 243 | Object already in the list |
| 244 | Enter an object validity |
| 245 | Comparison with replication table failed |
| 246 | Replication table has been successfully updated |
| 247 | Error occurred while updating the replication table |
| 248 | No objects are filtered out by the replication table |
| 249 | Following objects have been filtered out by the replication table: |
| 250 | &1, '&2 (&3)' |
| 251 | Preceding units can only be entered in the original packet |
| 252 | The name of the preceding unit must be entered |
| 253 | Preceding distribution unit &1 does not exist |
| 254 | Duplicated entries were removed from the list of predecessors |
| 255 | Distribution unit cannot have itself as a predecessor |
| 256 | .. Further posting of the instance(s) containing errors canceled |
| 257 | Serialization was updated; package can now be released |
| 258 | Release of packet was canceled |
| 259 | Object messages have been identified |
| 260 | Approval of unit was canceled |
| 261 | Specified validity was corrected |
| 262 | "Strict Serialization" and "Repostability" are mutually exclusive |
| 263 | Error in job administration |
| 264 | Correction can only be inserted in units of type &1 |
| 265 | Serialization levels have been recalculated |
| 266 | &1 messages were not yet passed to the target system |
| 267 | &1 messages have not yet been identified |
| 268 | Object &1, '&2 &3' is not valid |
| 269 | Cannot display object |
| 270 | Object can only be deleted (deactivated) with change number |
| 271 | All messages were passed to the target system |
| 272 | All messages have been identified |
| 273 | Segement definition &1 does not exist |
| 274 | UPS has been set up successfully |
| 275 | No authorization to create UPS Customizing |
| 276 | No authorization to change UPS Customizing |
| 277 | No authorization to display UPS Customizing |
| 278 | No authorization to delete UPS Customizing |
| 279 | Replication table filtered out objects without a comment in the UPS log |
| 280 | Missing queue serialization for &1 (SAP Note 1574296) |
| 300 | ****** Screen Processing ******************************************* |
| 301 | No log: Error information in text of the message status |
| 302 | Only original packets allowed; original of correction packet selected |
| 303 | Distribution unit &1 was deleted |
| 304 | Correction packet &1 was deleted |
| 330 | ******** Serialization Engine ****************************************** |
| 331 | Function Module &: Serialization Graph is Cyclical (Recursive) |
| 332 | Function Module &: Serialization Graph is Inconsistent |
| 333 | Object type &1 does not exist but a relation to &2 is maintained |
| 400 | ******** Parallelized Posting ************************************* |
| 401 | Parallel processes: &1 block size: &2 |
| 402 | Number of messages: &1 |
| 403 | Start index:&1 end index:&2 |
| 404 | Error generating a parallel process |
| 405 | Resource problem: Number of active processes: &1 |
| 406 | Resource problem: Sequential processing |
| 407 | Number of updated messages: &1 of &2 |
| 408 | ARFC_RETURN: No messages processed: &1 |
| 409 | Number of processes still active: &1 |
| 490 | ******** PROCESS FLOW *************************************************** |
| 491 | Automatic release is being executed ... |
| 492 | Automatic sending is being executed ... |
| 493 | Automatic approval is executed ... |
| 494 | Automatic posting is being executed ... |
| 500 | ******** CUSTOMIZING **************************************************** |
| 501 | Object type must be assigned to a usage |
| 502 | Enter a description |
| 503 | A description has already been entered for language &1 |
| 504 | Object type &1 is still used in packet types |
| 505 | DDIC structure &1 does not exist |
| 506 | Message type &1 does not exist |
| 507 | IDoc type &1 does not exist |
| 508 | Object type &1 was saved |
| 509 | Enter an object type |
| 510 | Object type &1 already exists |
| 511 | Related service removed |
| 512 | Enter a message type |
| 513 | Enter an IDoc type |
| 514 | Object type &1 was deleted |
| 515 | First edit dynpro &1 |
| 516 | You are not authorized to make changes |
| 517 | No display authorization |
| 520 | Enter a packet type |
| 521 | Packet type &1 already exists |
| 522 | Packet type &1 saved |
| 523 | Packet type &1 deleted |
| 524 | Packet type &1 is already used in distribution units |
| 525 | Object type &2 is already used in packets of type &1 |
| 526 | Object type &1 is already used in distribution packets |
| 527 | Posting is terminated |
| 528 | Changes to these settings are not allowed |
| 529 | Packet type &1 is assigned middleware type &2 |
| 532 | Central settings have been saved |
| 600 | No units corresponded to the selection criteria |
| 884 | A technical error occurred. Please contact support. |
| 885 | No display authorization for the object. Contact your administrator. |
| 891 | --------- used in U_P_S_C ----------------------------------------------- |
| 892 | --------- used in U_P_S_C ----------------------------------------------- |
| 895 | --------- used in U_P_S_C ----------------------------------------------- |
| 896 | --------- used in U_P_S_C ----------------------------------------------- |
| 897 | --------- used in U_P_S_C ----------------------------------------------- |
| 898 | --------- used in U_P_S_C ----------------------------------------------- |
| 899 | &1 &2 &3 &4 |