SAP ABAP Message Class HRALX00_ORG (HR-ALE-Org Enhancement)
Basic Data
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷ CA-HR (Application Component) Cross-Application Objects in HR
⤷ BP0A_ORGX (Package) HR Application Basis: ALE Technology, Enhancement
⤷ CA-HR (Application Component) Cross-Application Objects in HR
⤷ BP0A_ORGX (Package) HR Application Basis: ALE Technology, Enhancement
Attributes
Message class | HRALX00_ORG | |
Short Description | HR-ALE-Org Enhancement | |
Changed On | 20130531 | |
Last Changed At | 092329 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | SYSTEM ERROR------------------------------------------------------------- | The short text describes the object sufficiently | |
2 | 001 | Function parameters are inconsistent with &1 &2 | Space: object requires documentation | |
3 | 002 | System error: log context &1 does not exist | Space: object requires documentation | |
4 | 003 | System error: log object &1 could not be created | Space: object requires documentation | |
5 | 005 | Workflow is not available (see long text) | Space: object requires documentation | |
6 | 006 | System error: unexpected program state (&1) | Space: object requires documentation | |
7 | 100 | BUSINESS PARTNER ERROR--------------------------------------------------- | The short text describes the object sufficiently | |
8 | 101 | Organizational unit &1 does not have an address | Space: object requires documentation | |
9 | 150 | OTHER-------------------------------------------------------------------- | The short text describes the object sufficiently | |
10 | 151 | Form-of-address key &1 could not be converted | The short text describes the object sufficiently | |
11 | 152 | Marital status &1 could not be converted | The short text describes the object sufficiently | |
12 | 153 | No line has been selected in the list | The short text describes the object sufficiently | |
13 | 174 | No business partner could be created for organizational unit &1 | The short text describes the object sufficiently | |
14 | 175 | No business partner could be created for central person &1 | The short text describes the object sufficiently | |
15 | 176 | Business partners archived (number &1) | The short text describes the object sufficiently | |
16 | 177 | Generate new business partners | The short text describes the object sufficiently | |
17 | 178 | Business partner &1 is being created | The short text describes the object sufficiently | |
18 | 179 | Business partner &1 not created | Space: object requires documentation | |
19 | 180 | Business partner &1 created | The short text describes the object sufficiently | |
20 | 181 | Business partners generated (number &1) | The short text describes the object sufficiently | |
21 | 182 | Generate new business partners | The short text describes the object sufficiently | |
22 | 183 | Business partner &1 is being created | The short text describes the object sufficiently | |
23 | 184 | Business partner &1 not created | Space: object requires documentation | |
24 | 185 | Business partner &1 created | The short text describes the object sufficiently | |
25 | 186 | Business partners generated (number &1) | The short text describes the object sufficiently | |
26 | 187 | Updating existing business partners | The short text describes the object sufficiently | |
27 | 188 | Updating business partner &1 | The short text describes the object sufficiently | |
28 | 189 | Business partner &1 not updated | Space: object requires documentation | |
29 | 190 | Business partner &1 updated | The short text describes the object sufficiently | |
30 | 191 | Business partners updated (number &1) | The short text describes the object sufficiently | |
31 | 192 | Archive Business Partners | The short text describes the object sufficiently | |
32 | 193 | Archive Business Partner &1 | The short text describes the object sufficiently | |
33 | 194 | Business partner &1 could not be archived | Space: object requires documentation | |
34 | 195 | Business partner &1 archived | The short text describes the object sufficiently | |
35 | 196 | Generate new address for business partners | The short text describes the object sufficiently | |
36 | 197 | New address is being created for business partner &1 | The short text describes the object sufficiently | |
37 | 198 | New address could not be created for business partner &1 | Space: object requires documentation | |
38 | 199 | New address created for business partner &1 | The short text describes the object sufficiently | |
39 | 200 | New addresses created (number &1) | The short text describes the object sufficiently | |
40 | 202 | No receiver could be determined | Space: object requires documentation | |
41 | 203 | Address to be deleted could not be found (partner: &) | The short text describes the object sufficiently | |
42 | 204 | Convert business partners from organizational units | The short text describes the object sufficiently | |
43 | 205 | Supplement data for organizational units from the database | Space: object requires documentation | |
44 | 206 | Supplement name for organizational unit &1 | The short text describes the object sufficiently | |
45 | 207 | It was not possible to supplement names of organizational units | Space: object requires documentation | |
46 | 208 | Names supplemented (number &1) | The short text describes the object sufficiently | |
47 | 209 | Supplement address for organizational unit &1 | The short text describes the object sufficiently | |
48 | 210 | No address available for supplementing organizational unit &1 | The short text describes the object sufficiently | |
49 | 211 | Address supplemented for organizational unit &1 | The short text describes the object sufficiently | |
50 | 212 | Supplement e-mail for organizational unit &1 | The short text describes the object sufficiently | |
51 | 213 | E-mail could not be supplemented for organizational units | Space: object requires documentation | |
52 | 214 | E-mail supplemented for organizational units (number &1) | The short text describes the object sufficiently | |
53 | 215 | Supplement data for organizational units from IDOC data | The short text describes the object sufficiently | |
54 | 216 | Name of organizational unit &1 supplemented | The short text describes the object sufficiently | |
55 | 217 | Name of organizational unit &1 not supplemented | Space: object requires documentation | |
56 | 218 | Address supplemented for organizational unit &1 | The short text describes the object sufficiently | |
57 | 219 | Address for organizational unit &1 not supplemented | Space: object requires documentation | |
58 | 220 | E-mail for organizational unit &1 supplemented | The short text describes the object sufficiently | |
59 | 221 | E-mail for organizational unit &1 not supplemented | Space: object requires documentation | |
60 | 222 | End of conversion of business partners from IDOC data | The short text describes the object sufficiently | |
61 | 223 | Locking business partner | The short text describes the object sufficiently | |
62 | 224 | Business partner &1 locked | Space: object requires documentation | |
63 | 225 | &1 business partners locked | The short text describes the object sufficiently | |
64 | 226 | Unlocking business partner | The short text describes the object sufficiently | |
65 | 227 | &1 business partner unlocked | Space: object requires documentation | |
66 | 228 | Business partner &1 could not be locked | The short text describes the object sufficiently | |
67 | 230 | Business partners completed | The short text describes the object sufficiently | |
68 | 231 | Organizational unit partners could not be determined | Space: object requires documentation | |
69 | 232 | Check address for business partner &1 | The short text describes the object sufficiently | |
70 | 233 | Business partner &1 has an address | The short text describes the object sufficiently | |
71 | 234 | Business partner &1 does not have an address | The short text describes the object sufficiently | |
72 | 235 | Address for business partner could not be read | Space: object requires documentation | |
73 | 236 | Supplement standard address | Space: object requires documentation | |
74 | 237 | Read standard address (business partner &1) | Space: object requires documentation | |
75 | 238 | Standard address could not be read | Space: object requires documentation | |
76 | 239 | Standard address supplemented | Space: object requires documentation | |
77 | 240 | Completing business partners from the database | The short text describes the object sufficiently | |
78 | 241 | Existency check for associated business partners | The short text describes the object sufficiently | |
79 | 242 | Existency check for associated business partners not possible | Space: object requires documentation | |
80 | 243 | Associated business partner &1 does not exist | Space: object requires documentation | |
81 | 244 | Determining internal business partner keys (GUID) | The short text describes the object sufficiently | |
82 | 245 | Internal business partner keys determined (number: &1) | The short text describes the object sufficiently | |
83 | 246 | Internal business partner keys could not be determined | Space: object requires documentation | |
84 | 247 | Reading business partner data | The short text describes the object sufficiently | |
85 | 248 | Data for business partners read (number &1) | The short text describes the object sufficiently | |
86 | 249 | Business partner data could not be read | Space: object requires documentation | |
87 | 250 | Start integration for organizational units (IDoc &1) | Space: object requires documentation | |
88 | 251 | Start integration for organizational units (segment &1) | Space: object requires documentation | |
89 | 252 | End of integration for organizational units (IDoc &1) | The short text describes the object sufficiently | |
90 | 253 | Reading the associated partners for organizational units | The short text describes the object sufficiently | |
91 | 254 | Read partners for organizational units (number: &1) | The short text describes the object sufficiently | |
92 | 255 | Find partner for organizational unit &1 | The short text describes the object sufficiently | |
93 | 256 | Generating business partners from organizational units | The short text describes the object sufficiently | |
94 | 257 | Generated business partners from organizational units | The short text describes the object sufficiently | |
95 | 258 | Creating business partners | The short text describes the object sufficiently | |
96 | 259 | Created business partners | The short text describes the object sufficiently | |
97 | 260 | Starting synchronizing of organizational unit/partner | The short text describes the object sufficiently | |
98 | 261 | Synchronized organizational unit/partner | The short text describes the object sufficiently | |
99 | 262 | Updating existing addresses | The short text describes the object sufficiently | |
100 | 263 | Check whether business partner &1 has an existing address | The short text describes the object sufficiently | |
101 | 267 | Address not checked for business partner &1 | Space: object requires documentation | |
102 | 268 | Updating addresses for business partner &1 | The short text describes the object sufficiently | |
103 | 269 | Address for business partner &1 not updated | Space: object requires documentation | |
104 | 270 | Address updated for business partner &1 | The short text describes the object sufficiently | |
105 | 271 | Addresses updated (number &1) | The short text describes the object sufficiently | |
106 | 275 | Adjusting assignment of partner and organizational unit | The short text describes the object sufficiently | |
107 | 276 | Assignment adjusted (&1 created, &2 deleted) | The short text describes the object sufficiently | |
108 | 277 | Generate assignment for org. unit &1 to partner &2 from &3 to &4 | The short text describes the object sufficiently | |
109 | 278 | Delete assignment for organizational unit &1 | The short text describes the object sufficiently | |
110 | 279 | Assignment cannot be updated | Space: object requires documentation | |
111 | 280 | Incorrect assignment for org. unit &1 to partner &2 from &3 to &4 | Space: object requires documentation | |
112 | 281 | Assignment for org. unit &1 to partner &2 cannot be generated | The short text describes the object sufficiently | |
113 | 286 | Deleting obsolete addresses | The short text describes the object sufficiently | |
114 | 287 | Find out internal address key for business partner &1 | The short text describes the object sufficiently | |
115 | 289 | Internal address key for business partner &1 not found | Space: object requires documentation | |
116 | 290 | Internal address key for business partner &1 found | The short text describes the object sufficiently | |
117 | 291 | Find out address relating to key for business partner &1 | The short text describes the object sufficiently | |
118 | 293 | Address of business partner &1 not found | Space: object requires documentation | |
119 | 294 | Address of business partner &1 found | Space: object requires documentation | |
120 | 295 | Address of business partner &1 is being deleted | The short text describes the object sufficiently | |
121 | 297 | Address of business partner &1 not deleted | Space: object requires documentation | |
122 | 298 | Address of business partner &1 was deleted | The short text describes the object sufficiently | |
123 | 299 | Obsolete addresses deleted (number &1) | Space: object requires documentation | |
124 | 300 | ERROR IN CONSISTENCY OF CUSTOMIZING-------------------------------------- | The short text describes the object sufficiently | |
125 | 301 | HR integration is not active | Space: object requires documentation | |
126 | 302 | Switch &2 (group &1) does not exist in table T77S0 | The short text describes the object sufficiently | |
127 | 303 | Switch &2 (group &1) has an invalid value | Space: object requires documentation | |
128 | 304 | Switch &2 (group &1) has an invalid value | Space: object requires documentation | |
129 | 305 | Switch &2 (group &1) has an invalid value | Space: object requires documentation | |
130 | 308 | Subgroup &1 for number range object BU_PARTNER does not exist | Space: object requires documentation | |
131 | 309 | The subgroup of number range BU_PARTNER is wrongly defined | Space: object requires documentation | |
132 | 310 | Enter a value between 1 - 3 | The short text describes the object sufficiently | |
133 | 311 | Enter a value between 1 - 5 | The short text describes the object sufficiently | |
134 | 312 | Choose "ON", "OFF", or "CREATE" | Space: object requires documentation | |
135 | 313 | Enter either "ON" or "OFF" | The short text describes the object sufficiently | |
136 | 314 | Enter 'X' or ' ' | The short text describes the object sufficiently | |
137 | 315 | Missing data | Space: object requires documentation | |
138 | 500 | ---Employee Integration-------------------------------------------------- | The short text describes the object sufficiently | |
139 | 501 | Start of integration for employee (IDoc &1) | The short text describes the object sufficiently | |
140 | 502 | End of integration for employee (IDoc &1) | The short text describes the object sufficiently | |
141 | 503 | Filtering data for employee(s) | The short text describes the object sufficiently | |
142 | 504 | Read assignment of employee to person | The short text describes the object sufficiently | |
143 | 506 | Transfer employee data to person | The short text describes the object sufficiently | |
144 | 507 | Filter out persons with incorrect business partners | The short text describes the object sufficiently | |
145 | 508 | Generate relationships from qualifications to business partners | The short text describes the object sufficiently | |
146 | 510 | Filtering data for employee &1 (IDoc &2, segment &3-&4) | The short text describes the object sufficiently | |
147 | 511 | Filtering relationship &1 between &2 and employee &3 | The short text describes the object sufficiently | |
148 | 512 | Filtering data for central person &1 (IDoc &2, segment &3-&4) | The short text describes the object sufficiently | |
149 | 513 | Filtering data for qualification &1 (IDoc &2, segment &3-&4) | The short text describes the object sufficiently | |
150 | 515 | Employee &1 is incomplete (infotype &2 is missing) | Space: object requires documentation | |
151 | 516 | Employee &1 is not active (anymore) | The short text describes the object sufficiently | |
152 | 517 | Person &2 is being created for employee &1 | The short text describes the object sufficiently | |
153 | 520 | Data for employee &1 transferred to person &2 | The short text describes the object sufficiently | |
154 | 521 | Infotype &1 transferred to infotype &2 | The short text describes the object sufficiently | |
155 | 522 | Infotype &1 will be ignored | The short text describes the object sufficiently | |
156 | 523 | Infotype &1 (valid from &2 to &3) will be ignored | The short text describes the object sufficiently | |
157 | 524 | Person &1 is valid as of &4 (active from &2 to &3 | Space: object requires documentation | |
158 | 525 | Employee &1 is assigned person &2 and partner &3 | The short text describes the object sufficiently | |
159 | 530 | Relationships to employees are being adjusted | The short text describes the object sufficiently | |
160 | 531 | Relationship &1 (from &2 to employee &3) changed to person &4 | The short text describes the object sufficiently | |
161 | 532 | Relationship &1 (from &2 to employee &3) will be ignored | The short text describes the object sufficiently | |
162 | 533 | Relationship &1 (from &2 to employee &3) changed to partner &4 | The short text describes the object sufficiently | |
163 | 534 | Person &1 does not have a business partner | The short text describes the object sufficiently | |
164 | 535 | Employee &1 does not have a central person | The short text describes the object sufficiently | |
165 | 540 | Start of redundancy relationship, person and employee | The short text describes the object sufficiently | |
166 | 541 | End of redundancy relationship, person and employee | The short text describes the object sufficiently | |
167 | 542 | &1 relationships are being created and &2 deleted | The short text describes the object sufficiently | |
168 | 543 | Start of redundancy relationsip, position and user | The short text describes the object sufficiently | |
169 | 544 | End of redundancy relationship, position and user | The short text describes the object sufficiently | |
170 | 550 | Start of synchronization between person and business partner | The short text describes the object sufficiently | |
171 | 551 | End of synchronization between person and business partner | The short text describes the object sufficiently | |
172 | 552 | Adjusting assignment between partner and person | The short text describes the object sufficiently | |
173 | 553 | Assignment adjusted (&1 created, &2 deleted) | The short text describes the object sufficiently | |
174 | 554 | Generate assignment for person &1 to partner &2 from &3 to &4 | The short text describes the object sufficiently | |
175 | 555 | Delete assignment for person &1 | The short text describes the object sufficiently | |
176 | 556 | Assignment cannot be updated | Space: object requires documentation | |
177 | 557 | Incorrect assignment for person &1 to partner &2 from &3 to &4 | Space: object requires documentation | |
178 | 558 | Assignment for person &1 to partner &2 cannot be created | The short text describes the object sufficiently | |
179 | 560 | Converting business partners from personnel numbers | The short text describes the object sufficiently | |
180 | 561 | Error when reading infotype &1 | The short text describes the object sufficiently | |
181 | 562 | Supplement data for persons from database | The short text describes the object sufficiently | |
182 | 563 | &2 records have been read for infotype &1 | The short text describes the object sufficiently | |
183 | 570 | Adding bank data | The short text describes the object sufficiently | |
184 | 571 | No bank data could be added for BP &1 | The short text describes the object sufficiently | |
185 | 572 | &1 bank details added | The short text describes the object sufficiently | |
186 | 573 | Updating bank data | The short text describes the object sufficiently | |
187 | 574 | No bank data could be updated for BP &1 | The short text describes the object sufficiently | |
188 | 575 | &1 bank details updated | The short text describes the object sufficiently | |
189 | 576 | Deleting bank data | The short text describes the object sufficiently | |
190 | 577 | No bank data could be deleted for BP &1 | The short text describes the object sufficiently | |
191 | 578 | &1 bank details deleted | The short text describes the object sufficiently | |
192 | 580 | Synchronizing BP-BP relationships | The short text describes the object sufficiently | |
193 | 581 | Deleting BP-BP relationships | The short text describes the object sufficiently | |
194 | 582 | Relationship between BP employee &1 and BP organization &2 deleted | The short text describes the object sufficiently | |
195 | 583 | &1 BP-BP relationships have been deleted | The short text describes the object sufficiently | |
196 | 584 | Adding BP-BP relationships | The short text describes the object sufficiently | |
197 | 585 | &1 BP-BP relationships have been added | The short text describes the object sufficiently | |
198 | 586 | Updating BP-BP relationships | The short text describes the object sufficiently | |
199 | 587 | Relationship between BP employee &1 to BP organization &2 updated | The short text describes the object sufficiently | |
200 | 588 | &1 BP-BP relationships have been updated | The short text describes the object sufficiently | |
201 | 589 | BP-BP relationships, error in FM &1, error value &2 | The short text describes the object sufficiently | |
202 | 590 | Relationship between BP &1 and BP &2 could not be created | The short text describes the object sufficiently | |
203 | 591 | Relationship between BP &1 and BP &2 could not be deleted | The short text describes the object sufficiently | |
204 | 592 | Relationship between BP &1 and BP &2 could not be updated | The short text describes the object sufficiently | |
205 | 593 | Relationship between BP employee &1 and BP organization &2 added | The short text describes the object sufficiently | |
206 | 600 | Synchronization of workplace addresses | The short text describes the object sufficiently | |
207 | 601 | Synchronization of workplace addresses completed | The short text describes the object sufficiently | |
208 | 602 | Synchronization of workplace addresses failed | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 640 |