5- - HR-ALE: Fehlermeldungen
The following messages are stored in message class 5-: HR-ALE: Fehlermeldungen.
It is part of development package SP01 in software component BC-BMT-OM. This development package consists of objects that can be grouped under "HR: ALE Distibution with Message Type HRMD (Basis+Appl.)".
It is part of development package SP01 in software component BC-BMT-OM. This development package consists of objects that can be grouped under "HR: ALE Distibution with Message Type HRMD (Basis+Appl.)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | HR: ALE inbound processing for HR master data |
| 001 | ALE inbound processing: Object & saved |
| 002 | ALE inbound processing: Incorrect message type & in FM & & & |
| 003 | You cannot use message type & |
| 004 | There is no model view for the distribution of HR master data |
| 005 | The original system mechanism is inactive |
| 006 | Object type & is not supported for original system mechanism |
| 010 | Allowed operators: I(nsert), U(pdate), D(elete) |
| 011 | Infotype &, subtype & is not allowed |
| 012 | Infotype & is not allowed |
| 013 | The active plan version is &, but the entry is & |
| 014 | & is not a recipient of message type & in the distribution model |
| 030 | Receiver &: IDoc & on & at & |
| 031 | No data distributed |
| 032 | Data distributed in parallel processing |
| 033 | No data selected for distribution |
| 034 | Some data was not distributed because of conversion errors |
| 035 | No data distributed because of conversion errors |
| 050 | Conversion error: infotype &, object &,&,& |
| 051 | For ISO code &, more than one currency key was found in field & |
| 092 | For personnel number &, payroll area & is locked |
| 093 | Object & & is locked |
| 094 | Changes saved for relationships to unlocked objects |
| 095 | Changes successfully saved |
| 096 | Changes to HRMDORIGIN saved for objects that are not locked |
| 097 | No changes, so saving is unnecessary |
| 098 | Changes to HRMDORIGIN saved successfully |
| 100 | Errors in subroutine & for & & |
| 101 | Object is locked (plan ver. &, obj.ty. &, obj.ID &) |
| 102 | Object type & is locked by T77TR |
| 103 | Object type &, infotype &, subtype & is locked by T77TR |
| 104 | No structural authorization for obj. (plan vers. &, obj.type &, obj.ID &) |
| 105 | Object &,&,& does not exist: infotype & cannot be created |
| 106 | Database update not possible, data record &, RC & |
| 107 | Relationship starting from & impossible - & does not exist/is not active |
| 108 | Infotype & cannot be updated on database table & |
| 109 | Error in subroutine & for structure & of infotype & |
| 110 | No entry in HR_INFOTYPE_HEADER for infotype & for object &,&,& |
| 111 | No entry in HR_OBJECT_HEADER for object &,&,& |
| 112 | Object &,&,& not created; not all parent infotypes exist |
| 113 | No data available for creating/changing object &,&,& |
| 114 | IDoc is inconsistent |
| 115 | Enter a numerical value between 1 and 200 |
| 116 | Valid values: X or no entry |
| 117 | Object is not registered (plan version &, object type &, object ID &) |
| 118 | Object &,&,& exists as an original, and is not overwritten |
| 119 | Local relationship for object &,&,& overwritten |
| 120 | In infotype &, the required field & is not filled (&) |
| 121 | Relationship with nonexistent object |
| 122 | Passed company code & is inconsistent and was replaced by & |
| 123 | The & field is not filled for & & & |
| 124 | The & field is not maintainable in dialog, so it is ignored |
| 126 | _________errors in object: & & &, infotype & -> |
| 127 | _________warning in object: & & &, infotype & -> |
| 129 | Error: update for obj. (pl.vers. &, obj.type &, obj.ID &) (return code &) |
| 130 | Error: update for infotype & (return code &) |
| 131 | Error: deletion of pl.vers. &, obj.type &, obj.ID & object (ret.code &) |
| 132 | Error: deletion of objects (return code &) |
| 133 | Error: insertion of infotype & (return code &) |
| 134 | Error: insertion of pl.vers. &, obj.type &, obj.ID & object (ret.code &) |
| 135 | The object (plan version &, obj.type &, obj.ID &) is locked (IDoc &) |
| 150 | Object is locked at present |
| 151 | Account number missing |
| 152 | Chart of accounts & does not exist in account & |
| 153 | Unknown language key in name of account & |
| 154 | Account & has no name |
| 155 | Account no. & from segment A is different from account no. & in segment B |
| 156 | Company code & from account & does not exist |
| 157 | Language not installed in this system |
| 158 | Only background processing is possible in HR standalone |
| 159 | This object has a different address number (field ADRNR) |
| 170 | The IDoc &1 does not contain any HR master data; the message type is &2 |
| 171 | Inbound processing for the IDoc &1 takes place in the logical system & |
| 200 | Object &,&,& is not original in this system |
| 201 | Object &,&,& has no entry in table HRMDORIGIN |
| 202 | Error when updating table HRMDORIGIN for object &,&,& |
| 203 | Warning: You are editing a non-original version (replication) |
| 204 | Warning: You are editing a non-original (replicated/local) relationship |
| 220 | Originals could not be transferred |
| 221 | Originals transferred successfully |
| 222 | No originals selected |
| 223 | You started importing originals in simulation mode |
| 224 | System & is not allowed as a recipient |
| 225 | No entry for relationship & & & in view V_77ALECOM |
| 226 | Processing canceled for infotype & subtype & |
| 300 | Serialization error for object &. Expected counter & < & in IDoc |
| 301 | Serialization error for object &. Expected counter & > & in IDoc |
| 302 | Changes to & were saved for objects that are not locked |
| 303 | Changes to & successfully saved |
| 304 | Serialization for sender & is not active |
| 305 | Enter a sender |
| 306 | Serialization for recipient & is not active |
| 307 | Enter a recipient |
| 308 | The object &,&,& is locked |