SAP ABAP Message Class GRRM_OB_LOSEVT (GRRM OB: message class for loss events)
Basic Data
Hierarchy
☛
GRCFND_A (Software Component) GRC Foundation ABAP
⤷
GRC-RM (Application Component) GRC Risk Management
⤷
GRRM_OB_ENTITY_API (Package) Operational Risk Management for Banks: Entity API
⤷
⤷
Attributes
| Message class | GRRM_OB_LOSEVT | |
| Short Description | GRRM OB: message class for loss events | |
| Changed On | 20141106 | |
| Last Changed At | 194351 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 2 | Error when generating loss event ID. | The short text describes the object sufficiently | ||
| 3 | No objects returned for provided query. | The short text describes the object sufficiently | ||
| 4 | Query error. | The short text describes the object sufficiently | ||
| 5 | Query expression error for Loss event &1 '&2'. | The short text describes the object sufficiently | ||
| 6 | Loss event &1 '&2', loss allocation of effect '&3', Org. unit is missing | The short text describes the object sufficiently | ||
| 7 | Loss event with key &1 already exists. | The short text describes the object sufficiently | ||
| 8 | Loss event &1 '&2': Organization Unit is not valid | The short text describes the object sufficiently | ||
| 9 | Effect for loss event &1 &2 can not be created. | The short text describes the object sufficiently | ||
| 10 | Effect allocation for loss event &1 '&2' can not be created. | The short text describes the object sufficiently | ||
| 11 | Error when updating loss event &1 '&2'. | The short text describes the object sufficiently | ||
| 12 | Effect for loss event &1 '&2' can not be updated. | The short text describes the object sufficiently | ||
| 13 | Effect allocation for loss event &1 '&2' can not be updated. | The short text describes the object sufficiently | ||
| 14 | No loss event has been found. | The short text describes the object sufficiently | ||
| 15 | Time zone for the current client is not maintained. | The short text describes the object sufficiently | ||
| 16 | History entry can not be created for loss event &1 '&2'. | The short text describes the object sufficiently | ||
| 17 | Loss &1 '&2': total allocation of effect '&3' is more than effect amount | The short text describes the object sufficiently | ||
| 18 | Nothing has been changed in loss event &1 '&2'. | The short text describes the object sufficiently | ||
| 19 | Loss event &1 '&2' has been successfully created. | The short text describes the object sufficiently | ||
| 20 | Loss event &1 '&2' has been successfully saved. | The short text describes the object sufficiently | ||
| 21 | Loss event &1 '&2' has been successfully deleted. | The short text describes the object sufficiently | ||
| 22 | Loss event &1 '&2' has already been deleted. | The short text describes the object sufficiently | ||
| 23 | Loss event &1 '&2' is locked by another user. | The short text describes the object sufficiently | ||
| 24 | Loss event &1 '&2': occurrence date cannot be in the future. | The short text describes the object sufficiently | ||
| 25 | Loss event &1 '&2' is consistent. | The short text describes the object sufficiently | ||
| 26 | & events similar to '&2' has already been created. | The short text describes the object sufficiently | ||
| 27 | Similar Loss event &1 '&2' has already been created. | The short text describes the object sufficiently | ||
| 28 | Customizing error: loss event types are not maintained | The short text describes the object sufficiently | ||
| 29 | Customizing error: detection activities are not maintained | The short text describes the object sufficiently | ||
| 30 | Customizing error: effect types are not maintained | The short text describes the object sufficiently | ||
| 31 | Customizing error: loss criteria (extensions) are not maintained | The short text describes the object sufficiently | ||
| 32 | Customizing error: types of risks are not maintained | The short text describes the object sufficiently | ||
| 33 | Loss Event &1 '&2': Please enter type for effect '&3' | The short text describes the object sufficiently | ||
| 34 | Loss Event &1 '&2', effect '&3': Conversion from currency '&4' failed | The short text describes the object sufficiently | ||
| 35 | Loss Event with ID '&1' is not found | The short text describes the object sufficiently | ||
| 36 | Loss Event Type ID '&1' is not found | The short text describes the object sufficiently | ||
| 37 | Loss event &1 '&2': estimated probability should not be more than 100% | The short text describes the object sufficiently | ||
| 38 | Loss event &1 '&2', effect '&3': Loss allocation fraction is above 100% | The short text describes the object sufficiently | ||
| 39 | Loss event &1 '&2' is already assigned to organisation unit &3 '&4'. | The short text describes the object sufficiently | ||
| 40 | Assignment to root node is not allowed. | The short text describes the object sufficiently | ||
| 41 | Loss event &1 '&2' has been already reassigned. | The short text describes the object sufficiently | ||
| 42 | Reassignment of Loss Events failed. | The short text describes the object sufficiently | ||
| 43 | XML file is incorrect. | The short text describes the object sufficiently | ||
| 44 | XML file has been successfully upload. | The short text describes the object sufficiently | ||
| 45 | Please indicate an existing correct file. | The short text describes the object sufficiently | ||
| 46 | Uploading of Loss Events failed. | The short text describes the object sufficiently | ||
| 47 | All changes were cancelled. | The short text describes the object sufficiently | ||
| 48 | All changes were successfully submitted. | The short text describes the object sufficiently | ||
| 49 | Created &1 Loss Event(s). | The short text describes the object sufficiently | ||
| 50 | Updated &1 Loss Event(s). | The short text describes the object sufficiently | ||
| 51 | Deleted &1 Loss Event(s). | The short text describes the object sufficiently | ||
| 52 | Nothing has been changed. | The short text describes the object sufficiently | ||
| 53 | Error when deleting loss event &1 '&2'. | The short text describes the object sufficiently | ||
| 54 | History entry can not be created for loss event &1 '&2' | The short text describes the object sufficiently | ||
| 55 | Loss event &1 '&2' has been successfully deleted from DB. | The short text describes the object sufficiently | ||
| 56 | More than & messages occured. Check application log for more information | The short text describes the object sufficiently | ||
| 57 | Loss event &1 '&2': Risk Category is not valid | The short text describes the object sufficiently | ||
| 58 | Loss event &1 '&2', loss allocation of effect '&3', Org. unit is missing | The short text describes the object sufficiently | ||
| 59 | Loss event &1 '&2', cap. allocation of effect '&3', Org. unit is missing | The short text describes the object sufficiently | ||
| 60 | Loss event &1 '&2', loss allocation of effect '&3', Org. unit is invalid | The short text describes the object sufficiently | ||
| 61 | Loss event &1 '&2', cap. allocation of effect '&3', Org. unit is invalid | The short text describes the object sufficiently | ||
| 62 | User &1 not authorized for &2 operation for Loss Event &3 &4. | The short text describes the object sufficiently | ||
| 63 | User &1 not authorized for &2 operation. | The short text describes the object sufficiently | ||
| 64 | Error occured when saving notes for loss event &1 '&2' | The short text describes the object sufficiently | ||
| 65 | Loss Event &1 '&2' has been read for workflow id &3 | The short text describes the object sufficiently | ||
| 66 | Loss event has NOT been read for workflow id &1 | The short text describes the object sufficiently | ||
| 67 | Workflow id &1 has been started | The short text describes the object sufficiently | ||
| 68 | Subject '&1...' has been determined for Workflow id &2 | The short text describes the object sufficiently | ||
| 69 | Status customizing has been selected for Workflow id &1 | The short text describes the object sufficiently | ||
| 70 | Status customizing has NOT been selected for Workflow id &1 | The short text describes the object sufficiently | ||
| 71 | &1 role(s) were found for Workflow id &2 in customizing(&3&4...) | The short text describes the object sufficiently | ||
| 72 | &1 agent(s) were determined for Workflow id &2(&3&4...) | The short text describes the object sufficiently | ||
| 73 | Error creating the Loss Event header history. | The short text describes the object sufficiently | ||
| 74 | Error creating the Effect history. | The short text describes the object sufficiently | ||
| 75 | You are not a Workflow recipient for Loss Event &1 '&2' in status &3. | The short text describes the object sufficiently | ||
| 76 | &1 of loss events in status &2 is not possible. | The short text describes the object sufficiently | ||
| 77 | Loss event &1 '&2' does not have group type. | The short text describes the object sufficiently | ||
| 78 | Loss event &1 '&2' has group type. | The short text describes the object sufficiently | ||
| 79 | Loss event &1 '&2' is already in this group. | The short text describes the object sufficiently | ||
| 80 | Error creating the Effect allocation history. | The short text describes the object sufficiently | ||
| 81 | Error creating the CAUSE history. | The short text describes the object sufficiently | ||
| 82 | Error creating the RISK history. | The short text describes the object sufficiently | ||
| 83 | Loss event &1 '&2' is not locked and cannot be updated. | The short text describes the object sufficiently | ||
| 84 | Type field is not found during group filtering. | The short text describes the object sufficiently | ||
| 85 | Loss event ID field is not found during group filtering. | The short text describes the object sufficiently | ||
| 86 | Error creating the GROUPED LOSS history. | The short text describes the object sufficiently | ||
| 87 | Enter Org. Unit | The short text describes the object sufficiently | ||
| 88 | Loss Event &1 '&2': currency conversion from &3 to &4 failed. | The short text describes the object sufficiently | ||
| 89 | Error occured when saving customer fields for loss event &1 '&2' | The short text describes the object sufficiently | ||
| 90 | BAdI &1 is not implemented or implementation is not active. | The short text describes the object sufficiently | ||
| 91 | No risks found which are flagged as scenario loss | The short text describes the object sufficiently | ||
| 92 | Orgunits from several views are not allowed in Loss event query. | The short text describes the object sufficiently | ||
| 93 | EBA report structure cannot be generated | The short text describes the object sufficiently | ||
| 94 | Top node of Risk Catalog hierarchy '&1' is not found. | The short text describes the object sufficiently | ||
| 95 | Organizational view '&1' is not set up. | The short text describes the object sufficiently | ||
| 96 | Risk categories from several views are not allowed in Loss event query. | The short text describes the object sufficiently | ||
| 97 | KRI Instance & cannot be reassigned. Select also depend. business rules. | The short text describes the object sufficiently | ||
| 98 | Business rule & cannot be reassigned. Select also depend. KRI instances. | The short text describes the object sufficiently | ||
| 99 | KRI Instance & cannot be reassigned. Select also depend. KRI instances. | The short text describes the object sufficiently | ||
| 100 | Total fraction of all allocations of effect '&1' is too high. | The short text describes the object sufficiently | ||
| 101 | Loss event &1 '&2': estimated probability cannot be higher than 100% | The short text describes the object sufficiently | ||
| 102 | Loss event &1 '&2' is not locked and cannot be deleted. | The short text describes the object sufficiently | ||
| 103 | Loss event &1 '&2': share of Market Risk cannot be higher that 100% | The short text describes the object sufficiently | ||
| 104 | Loss event &1 '&2': share of Credit Risk cannot be higher that 100% | The short text describes the object sufficiently | ||
| 105 | Loss event &1 '&2': share of Operational Risk cannot be higher that 100% | The short text describes the object sufficiently | ||
| 106 | Workflow was triggered for Loss event &1 '&2'. Deletion is not possible. | The short text describes the object sufficiently | ||
| 107 | There's already another activity type marked as 'Process'. | The short text describes the object sufficiently | ||
| 108 | There's already another activity type marked as 'Product'. | The short text describes the object sufficiently | ||
| 109 | Loss ev. &1 '&2': total share of oper., cred. and mark. risk is not 100% | The short text describes the object sufficiently | ||
| 110 | More than one radio button is active. | The short text describes the object sufficiently | ||
| 111 | You should enable one Product AND Process. Continue...? | The short text describes the object sufficiently | ||
| 112 | One Loss Event type should have a Default type. Continue...? | The short text describes the object sufficiently | ||
| 113 | One Status of the Loss Event should have a Default Status. Continue...? | The short text describes the object sufficiently | ||
| 114 | Loss event &1 '&2' is already grouped into grouped loss event &3 '&4' | The short text describes the object sufficiently | ||
| 115 | Loss Event &1 '&2': Please enter name for effect number &3. | The short text describes the object sufficiently | ||
| 116 | Loss event &1 is already grouped into another grouped loss event | The short text describes the object sufficiently | ||
| 117 | Loss event &1 '&2', Effect '&3': amount cannot be negative | The short text describes the object sufficiently | ||
| 118 | Loss event &1 '&2', Effect '&3': capital alloc. amount cannot be negative | The short text describes the object sufficiently | ||
| 119 | Some scenario loss risks without analysis found - not useable for export | The short text describes the object sufficiently | ||
| 120 | Loss event &1 '&2', Effect '&3': loss alloc. amount cannot be negative | The short text describes the object sufficiently | ||
| 121 | No mapping hierarchy found | The short text describes the object sufficiently | ||
| 122 | Error occured when & entry in the database table &. | The short text describes the object sufficiently | ||
| 123 | No effects are selected. Please select one. | The short text describes the object sufficiently | ||
| 124 | Loss event &1 '&2' is a group and therefore cannot be grouped. | The short text describes the object sufficiently | ||
| 125 | Effect with Tracking Number &1 doesn't exist for loss event &2 &3. | The short text describes the object sufficiently | ||
| 126 | Allocation &1 doesn't exist for loss event &2 &3 and effect &4. | The short text describes the object sufficiently | ||
| 127 | No loss event data was uploaded. Please check your file. | The short text describes the object sufficiently | ||
| 128 | Enter Risk Category for this Loss event | The short text describes the object sufficiently | ||
| 129 | Loss event &1 '&2': occurrence date cannot be later then discovery date. | The short text describes the object sufficiently | ||
| 130 | Loss event &1 '&2': occurrence date cannot be later then accounting date. | The short text describes the object sufficiently | ||
| 131 | Loss event &1 '&2': Product/Process '&3' entity '&4' is not valid. | The short text describes the object sufficiently | ||
| 132 | Driver with sequence number &1 doesn't exist for loss event &2 &3. | The short text describes the object sufficiently | ||
| 133 | Risk with assignment number &1 doesn't exist for loss event &2 &3. | The short text describes the object sufficiently | ||
| 134 | Loss event with grouping sequence &1 doesn't exist for loss event &2 &3. | The short text describes the object sufficiently | ||
| 135 | ORX attribute Control 1 is mandatory for large loss events. | The short text describes the object sufficiently | ||
| 136 | ORX attribute Jurisdiction is mandatory for large loss events. | The short text describes the object sufficiently | ||
| 137 | ORX attribute Counterparty is mandatory for large loss events. | The short text describes the object sufficiently | ||
| 138 | ORX attribute Role of the firm is mandatory for large loss events. | The short text describes the object sufficiently | ||
| 139 | ORX attribute Environmental volatility is mandatory for large loss events | The short text describes the object sufficiently | ||
| 140 | ORX requires the allocation of all losses to a Level 2 Business Line | The short text describes the object sufficiently | ||
| 141 | ORX requires the allocation of all losses to a Level 2 Event Type | The short text describes the object sufficiently | ||
| 142 | ORX requires the allocation of all losses to a Level 2 Product | The short text describes the object sufficiently | ||
| 143 | ORX requires the allocation of large losses to a Level 2 Cause 1 | The short text describes the object sufficiently | ||
| 144 | ORX requires the allocation of large losses to a Level 2 Cause 2 | The short text describes the object sufficiently | ||
| 145 | ORX requires the allocation of large losses to a Level 2 Cause 3 | The short text describes the object sufficiently | ||
| 146 | ORX requires the allocation of large losses to a Level 2 Jurisdiction | The short text describes the object sufficiently | ||
| 147 | ORX requires the allocation of large losses to a Level 2 Counterparty | The short text describes the object sufficiently | ||
| 148 | ORX requires the allocation of large losses to a Level 2 Role of the firm | The short text describes the object sufficiently | ||
| 149 | ORX requires the allocation of large losses to a Level 2 Environmental | The short text describes the object sufficiently | ||
| 150 | More than 10000 consistency check errors found. | The short text describes the object sufficiently | ||
| 151 | & from & losses processed | The short text describes the object sufficiently | ||
| 152 | Loss Event &1: Assignment of own ID as a related event ID is not allowed | The short text describes the object sufficiently | ||
| 153 | Loss Event &1: Provided related event ID does not exist | The short text describes the object sufficiently | ||
| 154 | Loss Event &1: Reason for override is missing | The short text describes the object sufficiently | ||
| 155 | Loss Event &1: Reason for override is provided however flag is not set | The short text describes the object sufficiently | ||
| 156 | Loss Event &1: Same value for ORX Causes 1, 2 and 3 is not allowed | The short text describes the object sufficiently | ||
| 157 | Loss Event &1: Same value for ORX Controls 1, 2 and 3 is not allowed | The short text describes the object sufficiently | ||
| 158 | Please indicate file for export. | The short text describes the object sufficiently | ||
| 159 | ORX requires the allocation of all losses to a Level 1 Process | The short text describes the object sufficiently | ||
| 160 | Too much loss events selected. Only first & entries were displayed. | The short text describes the object sufficiently | ||
| 161 | Related loss event &1 does not pass data quality check. | Space: object requires documentation | ||
| 162 | Loss Event &1: Reason for Override must be shorter than 4000 characters. | The short text describes the object sufficiently | ||
| 163 | &1: Ref ID is not specified. | The short text describes the object sufficiently | ||
| 164 | &1: Business Line (L2) Code is not specified. | The short text describes the object sufficiently | ||
| 165 | &1: Event Category (L2) Code is not specified. | The short text describes the object sufficiently | ||
| 166 | &1: Country Code is not specified. | The short text describes the object sufficiently | ||
| 167 | &1: Date of Occurrence is not specified. | The short text describes the object sufficiently | ||
| 168 | &1: Date of Discovery is not specified. | The short text describes the object sufficiently | ||
| 169 | &1: Date of Recognition is not specified. | The short text describes the object sufficiently | ||
| 170 | &1: Cause 1 Code is not specified for a large loss. | The short text describes the object sufficiently | ||
| 171 | &1: Control 1 Code is not specified for a large loss. | The short text describes the object sufficiently | ||
| 172 | &1: Jurisdiction Code is not specified for a large loss. | The short text describes the object sufficiently | ||
| 173 | &1: Counterparty / Claimant Code is not specified for a large loss. | The short text describes the object sufficiently | ||
| 174 | &1: Role of the Firm Code is not specified for a large loss. | The short text describes the object sufficiently | ||
| 175 | &1: Environmental Volatility Code is not specified for a large loss. | The short text describes the object sufficiently | ||
| 176 | &1: Date of Discovery must be later than or equal to Date of Occurrence. | The short text describes the object sufficiently | ||
| 177 | &1: Date of Recognition must be later than or equal to Date of Discovery. | The short text describes the object sufficiently | ||
| 178 | &1: Gross Loss Amount should be equal or greater than 0. | The short text describes the object sufficiently | ||
| 179 | &1: Direct Recovery Amount should be equal or greater than 0. | The short text describes the object sufficiently | ||
| 180 | &1: Indirect Recovery Amount should be equal or greater than 0. | The short text describes the object sufficiently | ||
| 181 | Loss Database is fully compliant with ORX reporting standards. | The short text describes the object sufficiently | ||
| 182 | Loss event &1 is consistent. | The short text describes the object sufficiently | ||
| 183 | Global settings for QRR Export are not maintained. | Space: object requires documentation | ||
| 184 | There are no fields selected for QRR Export. | Space: object requires documentation |
History
| Last changed on/by | 20141106 | SAP | |
| SAP Release Created in | V1000 |