ARS_STATE_HANDLER - API Release: API State Handler
The following messages are stored in message class ARS_STATE_HANDLER: API Release: API State Handler.
It is part of development package S_ARS_STATE_HANDLER in software component BC-SRV-APS-EXT-REL. This development package consists of objects that can be grouped under "API Release: API State Handler".
It is part of development package S_ARS_STATE_HANDLER in software component BC-SRV-APS-EXT-REL. This development package consists of objects that can be grouped under "API Release: API State Handler".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Data for software release &1 could not be retrieved. |
| 001 | Earliest software release for deprecation could not be determined. |
| 002 | Earliest software release for decommissioning could not be determined. |
| 003 | Data for current software release &1 could not be retrieved. |
| 004 | Software release data could not be retrieved. |
| 005 | Software release could not be determined by date. |
| 010 | Not authorized to change API state |
| 011 | Not authorized to change API state for Object &1 |
| 012 | Not authorized to display API state for Object &1. |
| 100 | State cannot be changed since unsaved changes exist. |
| 101 | API release state change for object type &1 requires a sub object |
| 102 | &1 &2 does not exist. |
| 103 | The requested API release state change is not allowed. |
| 104 | API release valid since software release &1 cannot be undone. |
| 105 | API release valid since software release &1 cannot be deprecated. |
| 106 | API release deprecated since software release &1 cannot be decommissioned |
| 107 | Object &1 is used by cloud customers and thus cannot be deleted. |
| 108 | No package could be found for object &1 &2. |
| 109 | Deleting API release in non-original system. |
| 110 | Deprecating API release in non-original system. |
| 111 | Decommissioning API release in non-original system. |
| 112 | Object Id can not be generated for object &1 &2. |
| 113 | Deprecation is not supported for objects of type &1. |
| 114 | &1 &2 is used in SAP Cloud Platform and must not be deprecated. |
| 115 | Contract &1 is not supported for object type &2 / sub object type &3. |
| 116 | System-internal release for &1 cannot be undone. |
| 117 | You are about to undo system-internal release for &1. |
| 118 | Invalid API Release State provided. |
| 119 | At least one API visibility has to be selected for release contract &1. |
| 120 | API visibility &1 must not be selected. |
| 121 | &1 &2 is released as a remote API and must not be deprecated. |
| 124 | Releasing API in non-original system. |
| 125 | Do not delete release contract if already shipped. |
| 126 | Object &1 &2 must not be changed due to system configuration. |
| 127 | Successors must have at least one common API visibility |
| 128 | Objects released with feature toggle must only have one API visibility |
| 129 | API state origin &1 is not supported. |
| 130 | API visibility &1 must not be set for contract &2. |
| 131 | API visibility &1 must not be set in this system. |
| 132 | API has been changed in another process. Please try again. |
| 133 | Existing configuration for authorization values is going to be deleted. |
| 134 | Contract &1 cannot be set for objects of type &2 in non-SAP-systems. |
| 136 | ZDO is active. The function is temporary disabled (see note 3116886). |