| XE025 |
Function module & could not determine any data |
| XE026 |
Function module &1: default value '&2' used |
| XE027 |
RFC destination & is not defined |
| XE028 |
Table &1 is blocked by user &2 - no changes possible |
| XE029 |
RFC problem: & |
| XE030 |
Product code & is not defined |
| XE031 |
Data type '&' could not be replaced |
| XE032 |
RFC destination & was found and suggested as default |
| XE033 |
Entries saved |
| XE034 |
Express delivery company &2 is already assigned to service agent &1 |
| XE035 |
Parcel tracking is not active for forwarding agent & |
| XE036 |
The parcel tracking function is not active for shipment & |
| XE040 |
There are &1 entries, but only &2 entries were displayed |
| XE041 |
Enter complete item data |
| XE050 |
Handling unit & is not unique |
| XE051 |
Handling unit & does not exist |
| XE060 |
The assigned XSI tracking number (&1) is in critical area |
| XE061 |
The last XSI tracking number (&1) has been assigned |
| XE080 |
There were no small parcel carriers found on server & |
| XI000 |
Processing was terminated |
| XI001 |
A program or include already exists with the name & |
| XI002 |
A message class already exists with the name & |
| XI003 |
Program & does not exist. Please create |
| XI004 |
Object & not found |
| XI005 |
& already exists with name & |
| XI006 |
Object & has already been logically deleted |
| XI007 |
Internal error when writing & & |
| XI008 |
Name &$ not allowed for & |
| XI009 |
Parameters incomplete or blank |
| XI010 |
Name conflict with Dictionary object of type & |
| XI011 |
Internal error when deleting & & |
| XI012 |
Illegal activation type |
| XI013 |
& |
| XI014 |
Program & already exists in target system & |
| XI100 |
Screen header cannot be used in R/2: Size/type not allowed |
| XI101 |
& cannot be used in R/2: Attribute & not allowed |
| XI102 |
Unable to save screen &. Error during EXPORT DYNPRO. |
| XI110 |
In & mandatory field & has no value |
| XI111 |
In & field & has the invalid value & |
| XI112 |
In container & a field of type & is not allowed |
| XI113 |
In &, field & in component & has invalid value & |
| XI114 |
Field & exceeds the maintenance area (&/&) of the screen |
| XI115 |
Field & overlaps with or touches other fields |
| XI120 |
Internal error in & with & & |
| XI166 |
& & |
| XI200 |
Parameter & has the invalid value & |
| XI201 |
When locking / changing objects, you must specify CICO request |
| XI202 |
Request & does not exist |
| XI203 |
Request & has no tasks |
| XI204 |
Specify request to be closed |
| XI205 |
Request not created with RPY_CICO_REQUEST_OPEN |
| XI206 |
Object not checked out with CICO request & |
| XI207 |
Object catalogue entry not created since development class is initial |
| XI208 |
Could not create objecz cataloogue entry |
| XI209 |
Object transport layer and CICO request (&) do not go together |
| XI701 |
& is a correction. (Please enter a transport request) |
| XI702 |
& is not a transport request |
| XI703 |
Transport request & has not yet been released |
| XI_GRMG001 |
Component running: Name=&1, Vendor=&2 |
| XI_GRMG002 |
Error during heartbeat request: Component: Name=&1, Vendor=&2 |
| XI_GRMG003 |
RFC destination &1 does not exist |
| XI_GRMG004 |
RFC destination &1 exists but has the wrong type &2 |
| XI_GRMG005 |
Serious error in function &1 |
| XI_GRMG006 |
SLD ping gets exception: &1 |
| XI_GRMG007 |
SLD ping gets unknown exception |
| XI_GRMG008 |
No LCR server address maintained (see transaction LCRSERVADDR) |
| XI_GRMG009 |
Function LCR_LIST_BUSINESS_SYSTEMS failed (return code = &1) |
| XI_GRMG010 |
No business systems defined in SLD |
| XI_GRMG011 |
Business system name = &1, Role = &2 |
| XI_GRMG012 |
Function &1 failed (return code = &2) |
| XI_GRMG013 |
Tested: RFC destination, ping, getLCR server, read cache, BS defined |
| XI_GRMG014 |
Destination '&1' to the Integration Server created |
| XI_GRMG015 |
No role for business system defined in &1 |
| XI_GRMG016 |
Inconsistent roles. System Landscape: &1. SXMSGLOBAL: &2 |
| XI_GRMG017 |
Role = &1 |
| XI_GRMG018 |
Component initialized: Name=&1, vendor=&2 |
| XI_GRMG019 |
Component started: Name=&1, vendor=&2 |
| XI_GRMG020 |
Component &1 not started. Exception: &2 |
| XI_GRMG021 |
Component &1 not started. Element: &2. Exception: &3 |
| XI_GRMG022 |
Component &1 not started |
| XI_GRMG023 |
Component &1 not initialized |
| XI_GRMG024 |
Component &1 not initialized. Exception: &2 |
| XI_GRMG025 |
Component &1 not initialized. Element: &2. Exception: &3 |
| XI_GRMG026 |
Component &1. Block: &2. Value: &3 |
| XI_GRMG027 |
Web Service Security not configured on this component |
| XLPO000 |
Planned order &1 does not exist |
| XLPO001 |
Planned order number has not been entered |
| XLPO002 |
Invalid plant entry |
| XLPO003 |
No authorization for &1 to delete planned order |
| XLPO004 |
Planned order &1 not deleted |
| XLPO005 |
Planned order &1 is blocked by user &2 |
| XLPO006 |
Planned order with quantity 0 cannot be created |
| XLPO007 |
Unable to lock planned order &1 |
| XLPO008 |
Planned order &1 not found |
| XLPO009 |
No changes to planned order &1 identified |
| XLPO010 |
Version & not valid for material & in plant & |
| XLPO011 |
Please enter storage location |
| XLPO012 |
Please enter work center |
| XLPO013 |
Please enter unit of measure |
| XLPO014 |
No demands exists for the material &1 plant &2 |