CM_EHFND_LOCATION -
The following messages are stored in message class CM_EHFND_LOCATION: .
It is part of development package EHFND_BO_LOC_IMPL in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Business Object Location Implementation".
It is part of development package EHFND_BO_LOC_IMPL in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Business Object Location Implementation".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Enter at least one search condition |
| 001 | No technical objects found that match your search criteria |
| 002 | Select a technical object |
| 003 | Technical object &1 does not have any subordinate objects |
| 004 | Specify a location type for technical object &1 |
| 005 | Import activity supports a maximum of &1 technical objects |
| 006 | Technical object &1 cannot be imported without its parent |
| 007 | Select location position in location structure |
| 008 | Enter a location name |
| 009 | Enter a location type |
| 010 | Technical object &1 is already integrated into another location |
| 011 | Open location &1 |
| 012 | Syncronization with PM executed |
| 013 | Syncronization with PM terminated with errors |
| 014 | Select at least one attribute to update |
| 015 | Location type &1 does not exist |
| 016 | Location has been linked to PM technical object |
| 017 | PM technical object has been removed from the location |
| 018 | Action canceled; deletion can cause inconsistency |
| 019 | Cost center &1 does not exist inside the controlling area &2 |
| 020 | Controlling area cannot be determined for cost center &1 |
| 021 | Location authority group &1 does not exist |
| 022 | Cannot add &1 because it is integrated with a technical object |
| 023 | Select at least one location to update |
| 024 | PM integration is disabled |
| 025 | Location plant &1 does not exist for revision &2 |
| 026 | Location company code &1 does not exist for revision &2 |
| 027 | Location business area &1 does not exist for revision &2 |
| 028 | Location cost center &1 does not exist for revision &2 |
| 029 | Location organizational unit &1 does not exist for revision &2 |
| 030 | PM integrated locations exist |
| 031 | Action canceled; location is part of the location structure |
| 032 | Technical object is already integrated as a location |
| 033 | &1 cannot be added to the favorites, since it is not a location |
| 034 | Data saved |
| 035 | Select at least one location for import |
| 036 | Location ready to be deleted; choose Save to delete location permanently |
| 037 | Action canceled; status of all revisions must be "New" |
| 038 | Selected locations will be imported by a back end process |
| 039 | Invalid or empty e-mail address |
| 040 | Location &1 does not exist |
| 041 | Region &1 does not exist for revision &2 |
| 042 | Country/region &1 does not exist for revision &2. |
| 043 | Storage location &1 does not exist for plant &2 |
| 044 | Warehouse number &1 does not exist in revision &2 |
| 045 | Storage type &1 does not exist for warehouse number &2 |
| 046 | You are not authorized to create locations |
| 047 | Already imported locations cannot be selected |
| 048 | No country/region entered; no OEL checks possible in risk assessment. |
| 049 | You are not authorized to modify this location |
| 050 | You are not authorized to update location &1 |
| 051 | Cannot update location &1 because it is currently locked |
| 052 | Status change on location &1 not allowed |
| 053 | You cannot change the status of locations to "New" |
| 054 | Location created with &1 time zone |
| 060 | Assigment end date &1 is before assignment start date &2 |
| 061 | Position &1 does not exist |
| 062 | Position validity &1 - &2 does not overlap with the assignment period |
| 063 | Assignment start date is before position validity begins (&1) |
| 064 | Assignment end date is later than position validity ends (&1) |
| 065 | Assignment period overlaps with another record for position &1 |
| 066 | You are not authorized to access location &1 |
| 067 | Person &1 does not exist |
| 068 | Assignment start date is before person entry date (&1) |
| 069 | Assignment period overlaps with another record for person &1 |
| 070 | Select a location |
| 071 | You are not authorized to import a location |
| 072 | You are not authorized to change location attributes |
| 073 | Role &1 has already been assigned |
| 074 | Location "&1", file "&2": Material "&3" does not exist or is not active |
| 075 | Location "&1", file "&2": Material "&3" contains invalid unit (&4) |
| 076 | Location "&1", file "&2": Material "&3" contains invalid quantity (&4) |
| 077 | Location "&1", file "&2": Quantity conversion failed for Material "&3" |
| 078 | Location "&1", file "&2": Mat. "&3" contains invalid "days present" (&4) |
| 079 | Location "&1", file "&2": Line "&3" contains invalid format |
| 080 | Location "&1", file "&2": Mat. "&3" contains invalid time format (&4) |
| 081 | Person &1 has already been assigned to role &2 |
| 082 | No country/region is assigned to location &1. |
| 083 | No assigned workforce at location �&1� and its sublocations |
| 084 | Selected My Location "&1" is neither active nor inactive |
| 085 | Revision start date must be after the start date of the superior location |
| 086 | Invalid period for the start date of the location |
| 087 | The uploaded file is larger than 50 KB |
| 088 | File type not supported |
| 089 | User &1 no longer valid; choose another user from the value help |
| 090 | Location "&1" does not exist for date specified, hence, it is not added |
| 091 | Storage section &1 does not exist for warehouse number &2 Storage Type &3 |
| 092 | Storage bin &1 does not exist for warehouse number &2 |
| 093 | Storage bin &1 does not exist for Storage Type &2 and Storage Section &3 |
| 100 | Storage Location &1 of Plant &2 has already been assigned |
| 101 | Building &1 has already been assigned |
| 175 | Cannot delete. Location property is used in the following activities: |
| 176 | Location property can be safely deleted. Do you want to proceed? |
| 177 | Assignment of &1 as &2 for &3 is locked for editing in another session. |
| 178 | Assignment of &1 as &2 for &3 already exists. |
| 179 | Reassignment from &1 to &2 was skipped. |
| 180 | The new "Person Responsible" for the location was not specified. |
| 181 | Deletion of location role assignments failed. |
| 182 | Reassignment of location roles failed. |
| 183 | The new location responsible could not be found. |
| 184 | Incorrect parameter was provided for location role assignment key. |
| 185 | You cannot modify locations that are in status Historic. |
| 186 | Error during PM import. Saving process was canceled. |
| 187 | Adding locations to structure started. Locations count: &1 |
| 188 | Adding location to structure completed. |
| 189 | PERFORM_IMPORT: Exception occurred during import from PM. &1 |
| 190 | PM was imported successfully. |
| 191 | Start creating business objects for locations. Locations count: &1 |
| 192 | Error during location node insertion. See SU53 for details. PM ID: &1 |
| 193 | Error getting location revision. See SU53 for details. PM ID: &1 |
| 194 | Error running the location EAM sync for all imported objects. PM ID: &1 |
| 195 | IMPORT_LOCATIONS_INTO_BO: Exception occurred during import from PM. &1 |
| 196 | Location business objects were created successfully. |
| 197 | IMPORT_STRUCTURE_TO_PARENT: Exception occurred during import from PM. &1 |
| 198 | GET_TARGET_REVISION: Exception occurred during import from PM. &1 |
| 199 | CHECK_PARENT_HIERARCHY_KEY: Exception occurred during import from PM. &1 |
| 200 | IMPORT_STRUCTURE_TO_TARGET: Exception occurred during import from PM. &1 |
| 201 | OVERRIDE_EVENT_GAF: Exception occurred during import from PM. &1 |
| 202 | Region "&1" does not exist for the selected country/region. |
| 203 | Waste generator &1 does not have a waste registration number maintained |
| 204 | Country/Region is mandatory for waste generator location |
| 205 | Region is mandatory for waste generator location |
| 210 | Start synchronization of PM locations: &1 locations selected |
| 211 | Processing block from &1 to &2 for synchronization |
| 212 | No update performed on location of PM &1 &2 |
| 213 | &1 &2 synchronized successfully with location |