Message Number list used by SAP ABAP Class CL_GRRM_OB_API_AGGR_HIER (Aggregation hierarchy API)
SAP ABAP Class
CL_GRRM_OB_API_AGGR_HIER (Aggregation hierarchy API) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | GRFN_ENTITY_API - 032 | You are not authorized to update &1 &2 | ||
| 2 | GRFN_ENTITY_API - 033 | You are not authorized to retrieve &1 &2 | ||
| 3 | GRFN_ENTITY_API - 035 | You are not authorized to create any &1 | ||
| 4 | GRFN_ENTITY_API - 031 | You are not authorized to delete &1 &2 | ||
| 5 | GRRM_OB_REPORTING - 004 | Select corresponding RCSA Plan | ||
| 6 | GRRM_OB_REPORTING - 054 | Excluded node doesn't exist ('&1') | ||
| 7 | GRRM_OB_REPORTING - 050 | Aggregation hierarchy '&1' cannot be deleted as it is used in Aggr. Run | ||
| 8 | GRRM_OB_REPORTING - 049 | Node '&1' doesn't have Rule | ||
| 9 | GRRM_OB_REPORTING - 048 | Relation '&1' and &2 doesn't exist anymore | ||
| 10 | GRRM_OB_REPORTING - 047 | Rule exists without node ('&1') | ||
| 11 | GRRM_OB_REPORTING - 006 | Aggregation hierarchy '&1' is not locked and cannot be updated | ||
| 12 | GRRM_OB_REPORTING - 006 | Aggregation hierarchy '&1' is not locked and cannot be updated | ||
| 13 | GRRM_OB_REPORTING - 005 | Aggregation hierarchy '&1' is locked by user '&2' | ||
| 14 | GRRM_OB_REPORTING - 003 | Select corresponding hierarchy type | ||
| 15 | GRRM_OB_REPORTING - 002 | Select corresponding risk category hierarchy | ||
| 16 | GRRM_OB_REPORTING - 002 | Select corresponding risk category hierarchy | ||
| 17 | GRRM_OB_REPORTING - 001 | Select corresponding organization view | ||
| 18 | GRRM_OB_REPORTING - 001 | Select corresponding organization view | ||
| 19 | GRRM_RISK - 030 | Enter a name |