Message Number list used by SAP ABAP Class CL_GRPC_API_CONTROL (Control API class)
SAP ABAP Class
CL_GRPC_API_CONTROL (Control API class) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
![]() |
![]() |
|||
1 | ![]() |
GRFN_ENTITY_API - 023 | Session not properly initialized | |
2 | ![]() |
GRFN_ENTITY_API - 023 | Session not properly initialized | |
3 | ![]() |
GRFN_ENTITY_API - 023 | Session not properly initialized | |
4 | ![]() |
GRFN_ENTITY_API - 023 | Session not properly initialized | |
5 | ![]() |
GRFN_ENTITY_API - 032 | You are not authorized to update &1 &2 | |
6 | ![]() |
GRFN_ENTITY_API - 033 | You are not authorized to retrieve &1 &2 | |
7 | ![]() |
GRFN_ENTITY_API - 023 | Session not properly initialized | |
8 | ![]() |
GRPC_ENTITY_API - 231 | Control &1 does not exist | |
9 | ![]() |
GRPC_ENTITY_API - 890 | Control delete failed because under laying response cannot be deleted | |
10 | ![]() |
GRPC_ENTITY_API - 231 | Control &1 does not exist | |
11 | ![]() |
GRPC_ENTITY_API - 233 | Control &1 is locked by user &2 | |
12 | ![]() |
GRPC_ENTITY_API - 233 | Control &1 is locked by user &2 | |
13 | ![]() |
GRPC_ENTITY_API - 233 | Control &1 is locked by user &2 | |
14 | ![]() |
GRPC_ENTITY_API - 233 | Control &1 is locked by user &2 | |
15 | ![]() |
GRPC_ENTITY_API - 233 | Control &1 is locked by user &2 | |
16 | ![]() |
GRPC_ENTITY_API - 233 | Control &1 is locked by user &2 | |
17 | ![]() |
GRPC_ENTITY_API - 233 | Control &1 is locked by user &2 | |
18 | ![]() |
GRPC_ENTITY_API - 234 | Control &1 was not created | |
19 | ![]() |
GRPC_ENTITY_API - 234 | Control &1 was not created | |
20 | ![]() |
GRPC_ENTITY_API - 243 | Business rules are assigned | |
21 | ![]() |
GRPC_ENTITY_API - 231 | Control &1 does not exist | |
22 | ![]() |
GRPC_ENTITY_API - 043 | Changing testing attributes is not possible because a case exists | |
23 | ![]() |
GRPC_ENTITY_API - 043 | Changing testing attributes is not possible because a case exists | |
24 | ![]() |
GRPC_ENTITY_API - 042 | Change of validity not possible because case exists or in a policy | |
25 | ![]() |
GRPC_ENTITY_API - 042 | Change of validity not possible because case exists or in a policy | |
26 | ![]() |
GRPC_ENTITY_API - 042 | Change of validity not possible because case exists or in a policy | |
27 | ![]() |
GRPC_ENTITY_API - 042 | Change of validity not possible because case exists or in a policy | |
28 | ![]() |
GRPC_ENTITY_API - 040 | 'Valid-from' date adjusted to parent 'Valid-from' date | |
29 | ![]() |
GRPC_ENTITY_API - 039 | 'Valid-to' date cannot be earlier than start of the timeframe | |
30 | ![]() |
GRPC_ENTITY_API - 037 | 'Valid-to' date cannot be later than that of the parent object | |
31 | ![]() |
GRPC_ENTITY_API - 037 | 'Valid-to' date cannot be later than that of the parent object | |
32 | ![]() |
GRPC_ENTITY_API - 018 | Object name cannot be empty | |
33 | ![]() |
GRPC_ENTITY_API - 017 | 'Valid-to' date must be later than the 'Valid-from' date | |
34 | ![]() |
GRPC_ENTITY_API - 015 | 'Valid-to' date cannot be extended |