PAK_WB_FOUNDATION - Error messages for package SPAK_WB_FOUNDATION
The following messages are stored in message class PAK_WB_FOUNDATION: Error messages for package SPAK_WB_FOUNDATION.
It is part of development package SPAK_WB_FOUNDATION in software component BC-ABA-LA. This development package consists of objects that can be grouped under "Framework for integrating the APIs with the ABAP Workbench".
It is part of development package SPAK_WB_FOUNDATION in software component BC-ABA-LA. This development package consists of objects that can be grouped under "Framework for integrating the APIs with the ABAP Workbench".
Message Nr ▲ | Message Text |
|---|---|
| 000 | **** (messages for CX_PAK_ACTION_CANCELLED) **** |
| 001 | Action cancelled |
| 050 | **** (messages for CX_PAK_SYSTEM_ERROR) **** |
| 051 | A database error occurred while saving &1 |
| 052 | &1 was modified concurrently despite it has been locked |
| 100 | **** (messages for CX_PAK_INVALID_STATE) **** |
| 101 | &1 is already locked |
| 102 | &1 must be locked before operation &2 can be executed |
| 103 | &1 must be saved before operation &2 can be executed |
| 104 | &1 does not exist on the database yet, can't refresh data from database |
| 105 | &1 was deleted recently and doesn't exist anymore |
| 106 | &1 was reverted to active version so that current version is invalid |
| 107 | &1 does not have an active version to which to revert |
| 108 | |
| 110 | &1 must be locked before it can be modified |
| 111 | &1 must be locked before it can be saved |
| 112 | &1 must be locked before it can be activated |
| 113 | &1 must be locked before it can be deleted |
| 114 | &1 must be locked before it can be reverted to its active version |
| 117 | &1 must be saved before it can be unlocked |
| 118 | &1 must be saved before it can be activated |
| 120 | **** (messages for CX_PAK_OBJECT) **** |
| 121 | There's no object directory information available for &1 |
| 122 | Package checking was not possible for &1 |
| 123 | Detailed information not available for &1 because object type is invalid |
| 124 | The SUB_KEY part of the object key is longer than 120 characters |
| 125 | For &1, transport type "&2" is not valid. Use &3 instead |
| 130 | ** (CX_PAK_RELATED_OBJECT) |
| 131 | Needed to check data of &1 but failed to read that object |
| 150 | **** (messages for CX_PAK_NOT_AUTHORIZED) **** |
| 151 | User &2 is not authorized for activity &1 on &3 |
| 200 | **** (messages for CX_PAK_INVALID_DATA) **** |
| 201 | &1 already exists |
| 202 | Specified user &1 does not exist |
| 203 | Name "&1" not valid for object directory |
| 300 | **** (messages for CX_PAK_INVALID_OBJECT_NAME) **** |
| 301 | Invalid name "&1": Namespace prefix can only be 8 characters long |
| 302 | Invalid name "&1": Use "/" as a namespace delimiter only |
| 303 | Invalid name "&1": Space characters are not allowed |
| 304 | Invalid name: "&1" contains illegal characters |
| 305 | Invalid name: "&1" consists of the namespace prefix only |
| 306 | The specified package name is incorrect |
| 307 | The prefix of the object name &1 is illegal |
| 308 | "&1" is not a valid name for an object |
| 400 | **** (messages for CX_PAK_WB_OBJECT and subclasses) **** |
| 402 | |
| 420 | &1 does not exist |
| 421 | Active version of &1 does not exist |
| 422 | Inactive version of &1 does not exist |
| 440 | &1 is still used by other objects, its deletion will invalidate them |
| 500 | **** (messages for CX_PAK_GENERATION) **** |
| 501 | The invoking program or class is not assigned to a valid access object |
| 502 | Invoking program is not allowed to edit or inspect &1 |
| 503 | Invoking program should not edit or inspect &1 |
| 504 | There's an information message regarding editing or inspecting &1 |
| 900 | *** auxiliary messages *** |
| 901 | &1 &2 &3 &4 |