CM_EHHSS_INC_REC -
The following messages are stored in message class CM_EHHSS_INC_REC: .
It is part of development package EHHSS_BO_INC_IMPL in software component EHS-SUS-IM. This development package consists of objects that can be grouped under "Business Object Incident Implementation".
It is part of development package EHHSS_BO_INC_IMPL in software component EHS-SUS-IM. This development package consists of objects that can be grouped under "Business Object Incident Implementation".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Enter a start date and start time |
| 001 | Enter the date and time of the statement |
| 002 | Navigation is only supported in SAP NetWeaver Portal |
| 003 | Process data is not available; try again later |
| 004 | Unable to open the log; process has not been started |
| 005 | Operation canceled; implementation for category &1 missing |
| 006 | Process data for the selected task does not exist; refresh the UI |
| 007 | No person statement provided in form |
| 008 | Scheduler is not configured correctly. |
| 010 | Document &1 successfully attached |
| 012 | No incident managers found |
| 013 | No users for HR absence notifications found |
| 150 | ----------------- Messages for Checking HR-Absences --------------- |
| 151 | Check for changed HR absences started |
| 152 | Check for changed HR absences finished |
| 153 | Get absences types from EHS Customizing |
| 154 | Determine changed HR absences |
| 155 | Check processes for HR absence creation; relevant absences: &1 |
| 156 | All steps completed successfully |
| 157 | Relevant absence types are empty |
| 158 | Check incidents for automatic absence update; relevant absences: &1 |
| 159 | Create processes to inform incident manager about changed absences (#&1) |
| 160 | No changed absences available in HR |
| 161 | All absences must be maintained in HR; number of unprocessed absences: &1 |
| 162 | More than one absence found for the absence key |
| 163 | Cannot update absence assigned to the incident; locking problems |
| 200 | Communication exception |
| 201 | Inbound processing exception |
| 240 | --------- Incident Import BAPI messages ---------------- |
| 248 | Field "&1" is only imported when regulation "&2" is specified. |
| 249 | "Time Unknown" field is not imported for incidents of category "&1". |
| 250 | "&1" is not found in the system. Preliminary data is created. |
| 251 | Cannot create incident root |
| 252 | Incident "Basic Information" node not found |
| 253 | Reporting person user name "&1" does not exist |
| 254 | No involved person entries available |
| 255 | Import mapping for data source "&1" and field name "&2" is missing |
| 256 | Attribute name for field name "&1" is missing |
| 257 | Attribute name "&1" for node "&2" does not exist |
| 258 | Only preliminary data can be migrated for person ID &1 |
| 259 | Incident &1 migrated to incident ID &2 (EHS system) |
| 260 | RFC destination to source system is not specified |
| 261 | MIME type of document &1 is not recognized; it has not been migrated |
| 262 | Not authorized to import incidents |
| 263 | Functional location ID &1 does not exist; it was not imported |
| 264 | Equipment ID &1 does not exist; it was not imported |
| 265 | Damage type "&1" not valid for equipment type; damage was not imported |
| 266 | Import mapping node name for field name "&1" is missing |
| 267 | User defined text type &1 not recognized; it was not migrated |
| 268 | Expenses of safety measure migrated to action type &1 subtype &2 title &3 |
| 269 | Document "&1 &2" not determined; it was not migrated |
| 270 | Person "&1 &2" not allowed for this role |
| 271 | Safety measure "&1" not migrated due to a person role inconsistency |
| 272 | "&1" field must not be empty |
| 273 | Importing safety measure: &1 |
| 274 | Importing incident/accident: log "&1" |
| 275 | Reporting person is set as "&1" |
| 276 | Reporting person id &1 does not exist |
| 277 | Currency code &1 does not exist; the expense was not migrated |
| 278 | Reporting person with id &1 is created as preliminary person data |
| 279 | Incomplete data for person &1. Provide a Name or an ID. |
| 280 | Incident &1 cannot be migrated without a reporting person |
| 281 | Importing action: &1 |
| 282 | Document "&1" was not migrated |
| 283 | Form name "&1" does not exist; document "&2" was not imported |
| 284 | Step category "&1" does not exist; investigation step "&2" skipped |
| 285 | Step code "&1" does not exist; investigation step "&2" skipped |
| 286 | Guideline code "&1" does not exist; guideline was not imported |
| 287 | Root cause "&1", type "&2" does not exist |
| 288 | Incident node "Investigation Result" not found |
| 289 | Attribute name "&1" for node "&2" does not exist |
| 290 | Incident &1 is not migrated |
| 291 | Location with key "&1" not determined; cannot assign it to the incident |
| 292 | Incident ID &1 is migrated already; it was not imported again |
| 293 | Root Cause Hierarchy successfully migrated |
| 294 | "&1" information cannot be imported for "&2". Enter the relevant role. |
| 295 | "&1" not found in the system. Statement was imported without recorder. |
| 296 | Enter only one reporting person for incident &1. |
| 297 | Reporting person &1 is provided for anonymously reported incident &2. |
| 298 | Incident was migrated to incident ID "&1". |
| 299 | &1 &2 not found in the system. Task definition "&3" cannot be imported. |
| 300 | --------- Link Incident Import BAPI messages ---------------- |
| 301 | Link between incidents "&1" and "&2" already exists |
| 302 | Link between incidents "&1" and "&2" was imported successfully |
| 303 | Links of incident ID &1 were not imported |
| 304 | Processing links of incident ID &1 |
| 305 | Cannot find incident &1 in the target system; its links were not imported |
| 306 | Cannot find incident &1 in target system; its links cannot be imported |
| 307 | Link between incidents "&1" and "&2" is ready to be imported |
| 308 | Incident &1 is already migrated |
| 309 | Customer Enahancement BOPF Node &1 is not configured |
| 400 | ----------------- Incident Public API messages ------------------------- |
| 401 | The incident reporting person cannot be created via API. |
| 402 | "Person Name" and "Person Role" are mandatory fields. |
| 403 | "Incident Category" is a mandatory field. |
| 404 | "Incident Title" is a mandatory field. |
| 405 | "Incident Start Date/Time" is a mandatory field. |
| 406 | "Incident Category" value is not valid. Allowed values: "&1", "&2", "&3". |
| 407 | The file name must be provided as a "Slug" header variable. |
| 408 | The "Content-Type" header variable is a mandatory field. |
| 409 | The payload of the request is empty and must be provided. |
| 410 | "&1" is not an allowed value for incident category "&2". |
| 411 | You can add attachments to an existing incident only. |
| 412 | You can add persons to an existing incident only. |
| 413 | The provided incident location UUID "&1" does not exist. |
| 414 | Too many records returned. Use system query options to limit the result. |