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
⤷
⤷
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 | SYSTEM ERROR------------------------------------------------------------- | The short text describes the object sufficiently | ||
| 2 | Function parameters are inconsistent with &1 &2 | Space: object requires documentation | ||
| 3 | System error: log context &1 does not exist | Space: object requires documentation | ||
| 4 | System error: log object &1 could not be created | Space: object requires documentation | ||
| 5 | Workflow is not available (see long text) | Space: object requires documentation | ||
| 6 | System error: unexpected program state (&1) | Space: object requires documentation | ||
| 7 | BUSINESS PARTNER ERROR--------------------------------------------------- | The short text describes the object sufficiently | ||
| 8 | Organizational unit &1 does not have an address | Space: object requires documentation | ||
| 9 | OTHER-------------------------------------------------------------------- | The short text describes the object sufficiently | ||
| 10 | Form-of-address key &1 could not be converted | The short text describes the object sufficiently | ||
| 11 | Marital status &1 could not be converted | The short text describes the object sufficiently | ||
| 12 | No line has been selected in the list | The short text describes the object sufficiently | ||
| 13 | No business partner could be created for organizational unit &1 | The short text describes the object sufficiently | ||
| 14 | No business partner could be created for central person &1 | The short text describes the object sufficiently | ||
| 15 | Business partners archived (number &1) | The short text describes the object sufficiently | ||
| 16 | Generate new business partners | The short text describes the object sufficiently | ||
| 17 | Business partner &1 is being created | The short text describes the object sufficiently | ||
| 18 | Business partner &1 not created | Space: object requires documentation | ||
| 19 | Business partner &1 created | The short text describes the object sufficiently | ||
| 20 | Business partners generated (number &1) | The short text describes the object sufficiently | ||
| 21 | Generate new business partners | The short text describes the object sufficiently | ||
| 22 | Business partner &1 is being created | The short text describes the object sufficiently | ||
| 23 | Business partner &1 not created | Space: object requires documentation | ||
| 24 | Business partner &1 created | The short text describes the object sufficiently | ||
| 25 | Business partners generated (number &1) | The short text describes the object sufficiently | ||
| 26 | Updating existing business partners | The short text describes the object sufficiently | ||
| 27 | Updating business partner &1 | The short text describes the object sufficiently | ||
| 28 | Business partner &1 not updated | Space: object requires documentation | ||
| 29 | Business partner &1 updated | The short text describes the object sufficiently | ||
| 30 | Business partners updated (number &1) | The short text describes the object sufficiently | ||
| 31 | Archive Business Partners | The short text describes the object sufficiently | ||
| 32 | Archive Business Partner &1 | The short text describes the object sufficiently | ||
| 33 | Business partner &1 could not be archived | Space: object requires documentation | ||
| 34 | Business partner &1 archived | The short text describes the object sufficiently | ||
| 35 | Generate new address for business partners | The short text describes the object sufficiently | ||
| 36 | New address is being created for business partner &1 | The short text describes the object sufficiently | ||
| 37 | New address could not be created for business partner &1 | Space: object requires documentation | ||
| 38 | New address created for business partner &1 | The short text describes the object sufficiently | ||
| 39 | New addresses created (number &1) | The short text describes the object sufficiently | ||
| 40 | No receiver could be determined | Space: object requires documentation | ||
| 41 | Address to be deleted could not be found (partner: &) | The short text describes the object sufficiently | ||
| 42 | Convert business partners from organizational units | The short text describes the object sufficiently | ||
| 43 | Supplement data for organizational units from the database | Space: object requires documentation | ||
| 44 | Supplement name for organizational unit &1 | The short text describes the object sufficiently | ||
| 45 | It was not possible to supplement names of organizational units | Space: object requires documentation | ||
| 46 | Names supplemented (number &1) | The short text describes the object sufficiently | ||
| 47 | Supplement address for organizational unit &1 | The short text describes the object sufficiently | ||
| 48 | No address available for supplementing organizational unit &1 | The short text describes the object sufficiently | ||
| 49 | Address supplemented for organizational unit &1 | The short text describes the object sufficiently | ||
| 50 | Supplement e-mail for organizational unit &1 | The short text describes the object sufficiently | ||
| 51 | E-mail could not be supplemented for organizational units | Space: object requires documentation | ||
| 52 | E-mail supplemented for organizational units (number &1) | The short text describes the object sufficiently | ||
| 53 | Supplement data for organizational units from IDOC data | The short text describes the object sufficiently | ||
| 54 | Name of organizational unit &1 supplemented | The short text describes the object sufficiently | ||
| 55 | Name of organizational unit &1 not supplemented | Space: object requires documentation | ||
| 56 | Address supplemented for organizational unit &1 | The short text describes the object sufficiently | ||
| 57 | Address for organizational unit &1 not supplemented | Space: object requires documentation | ||
| 58 | E-mail for organizational unit &1 supplemented | The short text describes the object sufficiently | ||
| 59 | E-mail for organizational unit &1 not supplemented | Space: object requires documentation | ||
| 60 | End of conversion of business partners from IDOC data | The short text describes the object sufficiently | ||
| 61 | Locking business partner | The short text describes the object sufficiently | ||
| 62 | Business partner &1 locked | Space: object requires documentation | ||
| 63 | &1 business partners locked | The short text describes the object sufficiently | ||
| 64 | Unlocking business partner | The short text describes the object sufficiently | ||
| 65 | &1 business partner unlocked | Space: object requires documentation | ||
| 66 | Business partner &1 could not be locked | The short text describes the object sufficiently | ||
| 67 | Business partners completed | The short text describes the object sufficiently | ||
| 68 | Organizational unit partners could not be determined | Space: object requires documentation | ||
| 69 | Check address for business partner &1 | The short text describes the object sufficiently | ||
| 70 | Business partner &1 has an address | The short text describes the object sufficiently | ||
| 71 | Business partner &1 does not have an address | The short text describes the object sufficiently | ||
| 72 | Address for business partner could not be read | Space: object requires documentation | ||
| 73 | Supplement standard address | Space: object requires documentation | ||
| 74 | Read standard address (business partner &1) | Space: object requires documentation | ||
| 75 | Standard address could not be read | Space: object requires documentation | ||
| 76 | Standard address supplemented | Space: object requires documentation | ||
| 77 | Completing business partners from the database | The short text describes the object sufficiently | ||
| 78 | Existency check for associated business partners | The short text describes the object sufficiently | ||
| 79 | Existency check for associated business partners not possible | Space: object requires documentation | ||
| 80 | Associated business partner &1 does not exist | Space: object requires documentation | ||
| 81 | Determining internal business partner keys (GUID) | The short text describes the object sufficiently | ||
| 82 | Internal business partner keys determined (number: &1) | The short text describes the object sufficiently | ||
| 83 | Internal business partner keys could not be determined | Space: object requires documentation | ||
| 84 | Reading business partner data | The short text describes the object sufficiently | ||
| 85 | Data for business partners read (number &1) | The short text describes the object sufficiently | ||
| 86 | Business partner data could not be read | Space: object requires documentation | ||
| 87 | Start integration for organizational units (IDoc &1) | Space: object requires documentation | ||
| 88 | Start integration for organizational units (segment &1) | Space: object requires documentation | ||
| 89 | End of integration for organizational units (IDoc &1) | The short text describes the object sufficiently | ||
| 90 | Reading the associated partners for organizational units | The short text describes the object sufficiently | ||
| 91 | Read partners for organizational units (number: &1) | The short text describes the object sufficiently | ||
| 92 | Find partner for organizational unit &1 | The short text describes the object sufficiently | ||
| 93 | Generating business partners from organizational units | The short text describes the object sufficiently | ||
| 94 | Generated business partners from organizational units | The short text describes the object sufficiently | ||
| 95 | Creating business partners | The short text describes the object sufficiently | ||
| 96 | Created business partners | The short text describes the object sufficiently | ||
| 97 | Starting synchronizing of organizational unit/partner | The short text describes the object sufficiently | ||
| 98 | Synchronized organizational unit/partner | The short text describes the object sufficiently | ||
| 99 | Updating existing addresses | The short text describes the object sufficiently | ||
| 100 | Check whether business partner &1 has an existing address | The short text describes the object sufficiently | ||
| 101 | Address not checked for business partner &1 | Space: object requires documentation | ||
| 102 | Updating addresses for business partner &1 | The short text describes the object sufficiently | ||
| 103 | Address for business partner &1 not updated | Space: object requires documentation | ||
| 104 | Address updated for business partner &1 | The short text describes the object sufficiently | ||
| 105 | Addresses updated (number &1) | The short text describes the object sufficiently | ||
| 106 | Adjusting assignment of partner and organizational unit | The short text describes the object sufficiently | ||
| 107 | Assignment adjusted (&1 created, &2 deleted) | The short text describes the object sufficiently | ||
| 108 | Generate assignment for org. unit &1 to partner &2 from &3 to &4 | The short text describes the object sufficiently | ||
| 109 | Delete assignment for organizational unit &1 | The short text describes the object sufficiently | ||
| 110 | Assignment cannot be updated | Space: object requires documentation | ||
| 111 | Incorrect assignment for org. unit &1 to partner &2 from &3 to &4 | Space: object requires documentation | ||
| 112 | Assignment for org. unit &1 to partner &2 cannot be generated | The short text describes the object sufficiently | ||
| 113 | Deleting obsolete addresses | The short text describes the object sufficiently | ||
| 114 | Find out internal address key for business partner &1 | The short text describes the object sufficiently | ||
| 115 | Internal address key for business partner &1 not found | Space: object requires documentation | ||
| 116 | Internal address key for business partner &1 found | The short text describes the object sufficiently | ||
| 117 | Find out address relating to key for business partner &1 | The short text describes the object sufficiently | ||
| 118 | Address of business partner &1 not found | Space: object requires documentation | ||
| 119 | Address of business partner &1 found | Space: object requires documentation | ||
| 120 | Address of business partner &1 is being deleted | The short text describes the object sufficiently | ||
| 121 | Address of business partner &1 not deleted | Space: object requires documentation | ||
| 122 | Address of business partner &1 was deleted | The short text describes the object sufficiently | ||
| 123 | Obsolete addresses deleted (number &1) | Space: object requires documentation | ||
| 124 | ERROR IN CONSISTENCY OF CUSTOMIZING-------------------------------------- | The short text describes the object sufficiently | ||
| 125 | HR integration is not active | Space: object requires documentation | ||
| 126 | Switch &2 (group &1) does not exist in table T77S0 | The short text describes the object sufficiently | ||
| 127 | Switch &2 (group &1) has an invalid value | Space: object requires documentation | ||
| 128 | Switch &2 (group &1) has an invalid value | Space: object requires documentation | ||
| 129 | Switch &2 (group &1) has an invalid value | Space: object requires documentation | ||
| 130 | Subgroup &1 for number range object BU_PARTNER does not exist | Space: object requires documentation | ||
| 131 | The subgroup of number range BU_PARTNER is wrongly defined | Space: object requires documentation | ||
| 132 | Enter a value between 1 - 3 | The short text describes the object sufficiently | ||
| 133 | Enter a value between 1 - 5 | The short text describes the object sufficiently | ||
| 134 | Choose "ON", "OFF", or "CREATE" | Space: object requires documentation | ||
| 135 | Enter either "ON" or "OFF" | The short text describes the object sufficiently | ||
| 136 | Enter 'X' or ' ' | The short text describes the object sufficiently | ||
| 137 | Missing data | Space: object requires documentation | ||
| 138 | ---Employee Integration-------------------------------------------------- | The short text describes the object sufficiently | ||
| 139 | Start of integration for employee (IDoc &1) | The short text describes the object sufficiently | ||
| 140 | End of integration for employee (IDoc &1) | The short text describes the object sufficiently | ||
| 141 | Filtering data for employee(s) | The short text describes the object sufficiently | ||
| 142 | Read assignment of employee to person | The short text describes the object sufficiently | ||
| 143 | Transfer employee data to person | The short text describes the object sufficiently | ||
| 144 | Filter out persons with incorrect business partners | The short text describes the object sufficiently | ||
| 145 | Generate relationships from qualifications to business partners | The short text describes the object sufficiently | ||
| 146 | Filtering data for employee &1 (IDoc &2, segment &3-&4) | The short text describes the object sufficiently | ||
| 147 | Filtering relationship &1 between &2 and employee &3 | The short text describes the object sufficiently | ||
| 148 | Filtering data for central person &1 (IDoc &2, segment &3-&4) | The short text describes the object sufficiently | ||
| 149 | Filtering data for qualification &1 (IDoc &2, segment &3-&4) | The short text describes the object sufficiently | ||
| 150 | Employee &1 is incomplete (infotype &2 is missing) | Space: object requires documentation | ||
| 151 | Employee &1 is not active (anymore) | The short text describes the object sufficiently | ||
| 152 | Person &2 is being created for employee &1 | The short text describes the object sufficiently | ||
| 153 | Data for employee &1 transferred to person &2 | The short text describes the object sufficiently | ||
| 154 | Infotype &1 transferred to infotype &2 | The short text describes the object sufficiently | ||
| 155 | Infotype &1 will be ignored | The short text describes the object sufficiently | ||
| 156 | Infotype &1 (valid from &2 to &3) will be ignored | The short text describes the object sufficiently | ||
| 157 | Person &1 is valid as of &4 (active from &2 to &3 | Space: object requires documentation | ||
| 158 | Employee &1 is assigned person &2 and partner &3 | The short text describes the object sufficiently | ||
| 159 | Relationships to employees are being adjusted | The short text describes the object sufficiently | ||
| 160 | Relationship &1 (from &2 to employee &3) changed to person &4 | The short text describes the object sufficiently | ||
| 161 | Relationship &1 (from &2 to employee &3) will be ignored | The short text describes the object sufficiently | ||
| 162 | Relationship &1 (from &2 to employee &3) changed to partner &4 | The short text describes the object sufficiently | ||
| 163 | Person &1 does not have a business partner | The short text describes the object sufficiently | ||
| 164 | Employee &1 does not have a central person | The short text describes the object sufficiently | ||
| 165 | Start of redundancy relationship, person and employee | The short text describes the object sufficiently | ||
| 166 | End of redundancy relationship, person and employee | The short text describes the object sufficiently | ||
| 167 | &1 relationships are being created and &2 deleted | The short text describes the object sufficiently | ||
| 168 | Start of redundancy relationsip, position and user | The short text describes the object sufficiently | ||
| 169 | End of redundancy relationship, position and user | The short text describes the object sufficiently | ||
| 170 | Start of synchronization between person and business partner | The short text describes the object sufficiently | ||
| 171 | End of synchronization between person and business partner | The short text describes the object sufficiently | ||
| 172 | Adjusting assignment between partner and person | The short text describes the object sufficiently | ||
| 173 | Assignment adjusted (&1 created, &2 deleted) | The short text describes the object sufficiently | ||
| 174 | Generate assignment for person &1 to partner &2 from &3 to &4 | The short text describes the object sufficiently | ||
| 175 | Delete assignment for person &1 | The short text describes the object sufficiently | ||
| 176 | Assignment cannot be updated | Space: object requires documentation | ||
| 177 | Incorrect assignment for person &1 to partner &2 from &3 to &4 | Space: object requires documentation | ||
| 178 | Assignment for person &1 to partner &2 cannot be created | The short text describes the object sufficiently | ||
| 179 | Converting business partners from personnel numbers | The short text describes the object sufficiently | ||
| 180 | Error when reading infotype &1 | The short text describes the object sufficiently | ||
| 181 | Supplement data for persons from database | The short text describes the object sufficiently | ||
| 182 | &2 records have been read for infotype &1 | The short text describes the object sufficiently | ||
| 183 | Adding bank data | The short text describes the object sufficiently | ||
| 184 | No bank data could be added for BP &1 | The short text describes the object sufficiently | ||
| 185 | &1 bank details added | The short text describes the object sufficiently | ||
| 186 | Updating bank data | The short text describes the object sufficiently | ||
| 187 | No bank data could be updated for BP &1 | The short text describes the object sufficiently | ||
| 188 | &1 bank details updated | The short text describes the object sufficiently | ||
| 189 | Deleting bank data | The short text describes the object sufficiently | ||
| 190 | No bank data could be deleted for BP &1 | The short text describes the object sufficiently | ||
| 191 | &1 bank details deleted | The short text describes the object sufficiently | ||
| 192 | Synchronizing BP-BP relationships | The short text describes the object sufficiently | ||
| 193 | Deleting BP-BP relationships | The short text describes the object sufficiently | ||
| 194 | Relationship between BP employee &1 and BP organization &2 deleted | The short text describes the object sufficiently | ||
| 195 | &1 BP-BP relationships have been deleted | The short text describes the object sufficiently | ||
| 196 | Adding BP-BP relationships | The short text describes the object sufficiently | ||
| 197 | &1 BP-BP relationships have been added | The short text describes the object sufficiently | ||
| 198 | Updating BP-BP relationships | The short text describes the object sufficiently | ||
| 199 | Relationship between BP employee &1 to BP organization &2 updated | The short text describes the object sufficiently | ||
| 200 | &1 BP-BP relationships have been updated | The short text describes the object sufficiently | ||
| 201 | BP-BP relationships, error in FM &1, error value &2 | The short text describes the object sufficiently | ||
| 202 | Relationship between BP &1 and BP &2 could not be created | The short text describes the object sufficiently | ||
| 203 | Relationship between BP &1 and BP &2 could not be deleted | The short text describes the object sufficiently | ||
| 204 | Relationship between BP &1 and BP &2 could not be updated | The short text describes the object sufficiently | ||
| 205 | Relationship between BP employee &1 and BP organization &2 added | The short text describes the object sufficiently | ||
| 206 | Synchronization of workplace addresses | The short text describes the object sufficiently | ||
| 207 | Synchronization of workplace addresses completed | The short text describes the object sufficiently | ||
| 208 | Synchronization of workplace addresses failed | The short text describes the object sufficiently |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in | 640 |