SAP ABAP Message Class W3 (Messages for WebRFC)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CI-WEBR (Application Component) WebRFC, Web Reporting
⤷
SWWW (Package) Development class for basis WWW project
⤷
⤷
Attributes
| Message class | W3 | |
| Short Description | Messages for WebRFC | |
| Changed On | 19971218 | |
| Last Changed At | 093439 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | **** Structure explosion ************** | |||
| 2 | ******* 001-009 : hierarchical display of product hierarchy ******* | |||
| 3 | Object & already exists | |||
| 4 | Specify a MIME type | |||
| 5 | Specify a processing program | |||
| 6 | Specify a name for the object | |||
| 7 | Please enter a development class. | |||
| 8 | Select an entry | |||
| 9 | Object & already processed | Space: object requires documentation | ||
| 10 | Program for editing Web object does not exist | |||
| 11 | No MIME type assigned to object & | |||
| 12 | An equipment must be entered before making an assembly selection | |||
| 13 | Only object types HTML, MIME, HTRC and SRVC are supported | |||
| 14 | Incorrect language | Space: object requires documentation | ||
| 15 | Development class &1 does not exist. | |||
| 16 | Report &1 has been successfully released for the Internet | Space: object requires documentation | ||
| 17 | Report &1 has already been released for the Internet. | Space: object requires documentation | ||
| 18 | An error has occurred releasing Report &1. | Space: object requires documentation | ||
| 19 | The release of Report &1 for the Internet has been reset | Space: object requires documentation | ||
| 20 | The release of Report &1 cannot be reset | Space: object requires documentation | ||
| 21 | No reports have been released for the Internet | Space: object requires documentation | ||
| 22 | Report &1 does not exist. Please check spelling. | Space: object requires documentation | ||
| 23 | No bill of material exists | |||
| 24 | The release of function module &1 can not be reset | Space: object requires documentation | ||
| 25 | An error has occurred resetting release of function module &1. | Space: object requires documentation | ||
| 26 | Internet release of function module &1 has been reset | Space: object requires documentation | ||
| 27 | Module &1 does not exist. Please check spelling. | Space: object requires documentation | ||
| 28 | The function module &1 has been released for the Internet. | Space: object requires documentation | ||
| 29 | The function module &1 has already been released for the Internet | Space: object requires documentation | ||
| 30 | No function modules have yet been released for the Internet. | Space: object requires documentation | ||
| 31 | The authorization group for report &1 is not maintained. | Space: object requires documentation | ||
| 32 | No report trees have yet been released for the Internet. | Space: object requires documentation | ||
| 33 | Tree &1 does not exist. Please check spelling. | Space: object requires documentation | ||
| 34 | No reference object selected | |||
| 35 | Report tree &1 has been released for the Internet | Space: object requires documentation | ||
| 36 | Report tree &1 has already been for the Internet. | Space: object requires documentation | ||
| 37 | The release of report tree &1 cannot be revoked. | Space: object requires documentation | ||
| 38 | An error has occurred when resetting the release of report tree &1. | Space: object requires documentation | ||
| 39 | Report tree &1 has been released for the Internet | Space: object requires documentation | ||
| 40 | There are no report trees in your system | Space: object requires documentation | ||
| 41 | Hierarchy type is missing: Assignments cannot be made | |||
| 42 | Error updating assignment & | |||
| 43 | Node cannot be deleted: invalid assignments would occur | |||
| 44 | Vendor & not maintained for purchasing organization & | |||
| 45 | The order was created w/o reference to a notification | |||
| 46 | Object &1 is already locked in a correction request | Space: object requires documentation | ||
| 47 | Selection date lies in the past: Data will only be displayed | |||
| 48 | Vendor $ not maintained | |||
| 49 | Vendor & not defined as being assigned to & | |||
| 50 | Please enter a purchasing organization | |||
| 51 | Purchasing organization cannot be entered without vendor number | |||
| 52 | Please enter a vendor number | |||
| 53 | Assignment not possible (higher-level vendor not maintained) | |||
| 54 | Purchasing organization assignment is not defined | |||
| 55 | The order has no reference to a functional location | |||
| 56 | Valid-from date cannot lie in the past | |||
| 57 | Validity period is not allowed (From-date lies after the to-date) | |||
| 58 | The assignment is also active outside of the given time period | |||
| 59 | The assignment is already active in the given time period | |||
| 60 | Different assignments exist outside of the given time period | |||
| 61 | Incorrect assignments cannot be processed | |||
| 62 | Select hierarchy node | |||
| 63 | Node & will be assigned to the same level | |||
| 64 | Select hierarchy header nodes for higher-level assignment | |||
| 65 | No equipment was entered in the order | |||
| 66 | Selected sub-hierarchy contains all nodes and cannot be reassigned | |||
| 67 | Nodes cannot be reassigned: unpermitted assignments would occur | |||
| 68 | Hierarchy contains no allowed alternative higher-level assignments | |||
| 69 | Higher-level node already maintained as a subordinate node | |||
| 70 | Assigned node is also a higher-level node | |||
| 71 | You cannot assign node to itself | |||
| 72 | Assignment has different attributes outside of the given time period | |||
| 73 | Partner determination error: Function not possible | |||
| 74 | There are no hierarchy nodes to be displayed | |||
| 75 | Function not possible: Maximum number of hierarchy steps (26) exceeded | |||
| 76 | Lowest hierarchy level reached (26): lower steps will be ignored | |||
| 77 | Hierarchy node cannot be removed as invalid assignments would arise | |||
| 78 | Selected hierarchy node is a header node: subhierarchy cannot be removed | |||
| 79 | Select incorrect hierarchy nodes | |||
| 80 | Rebate and pricing assignments updated | |||
| 81 | Attributes (pricing, rebate) are up-to-date for all assignments | |||
| 82 | Date cannot be changed (inconsistent validity periods) | |||
| 83 | Hierarchy type & is not defined | |||
| 84 | Node & is not active or not available for selection date | |||
| 85 | Node & is not available in the hierarchy | |||
| 86 | Hierarchy level & cannot be transferred due to inconsistencies | |||
| 87 | Hierarchy level assignment(s) updated | |||
| 88 | Hierarchy level assignment not updated or not updated for all points | |||
| 89 | Assignment not allowed: incorrect hierarchy level assignment | |||
| 90 | 'Reassigning' can lead to inconsistencies in the hierarchy lvl assignmnt | |||
| 91 | Initial Date Limit(s): a new validity period has been proposed | |||
| 92 | Objects not included in transport request | Space: object requires documentation | ||
| 93 | Schedule line category & & deleted | |||
| 94 | Default indicator for & & & & cannot be reset | |||
| 95 | The new default item category for & & & is & | |||
| 96 | The new default schedule line category for & & is & | |||
| 97 | Default indicator for & & & cannot be reset | |||
| 98 | The new default item category for & & is & | |||
| 99 | Deletion unnecessary: no assignments exist | |||
| 100 | Enter a usage for structure configuration for BOM explosion | |||
| 101 | Internal error creating assignment table: Item categ & (ret code &) | |||
| 102 | No changes made to item category assignments | |||
| 103 | Changed item category assignments saved | |||
| 104 | Partner group & does not contain any payers who cannot be changed | |||
| 105 | Entry & & & missing in Table & | |||
| 106 | Item usage must be specified for item category group 'Blank' | |||
| 107 | Defaults for Item category & & changed | |||
| 108 | Customer-specific document types should begin with 'Z or Y' | |||
| 109 | Customer-specific item categories should begin with 'Z or Y' | |||
| 110 | Item category & already exists | |||
| 111 | Item category & & has been created | |||
| 112 | No changes made to the schedule line category assignments | |||
| 113 | Changes to schedule line category assignments have been saved | |||
| 114 | System blocking error for Table & | |||
| 115 | If a storage location is required, a batch check must be carried out | |||
| 116 | Error in transferring table entries to correction | |||
| 117 | The selected table entries have been transferred to correction | |||
| 118 | A condition type's access sequence in the pricing procedure is incorrect | |||
| 119 | An assignment for & already exists | |||
| 120 | Item category & is not allowed as a higher-level item category | |||
| 121 | Possible entries can only be displayed once the doc.type has been entered | |||
| 122 | Possible entries can only be displayed if a matl item category exists | |||
| 123 | Schedule line category & deleted from Table TVEP: please enter it again | |||
| 124 | Defaults for schedule line category & & changed | |||
| 125 | Schedule line category & & has been created | |||
| 126 | Schedule line category & already exists | |||
| 127 | Availability check without transfer of requirements is not allowed | |||
| 128 | Only condition types used for 'Pricing' are allowed | |||
| 129 | *** Task list connection | |||
| 130 | Text control | |||
| 131 | Please select a text object | |||
| 132 | You can only select one text object | |||
| 133 | System error occurred reading Internal table ( & ) | |||
| 134 | The entry already exists | |||
| 135 | Text determination procedure & has not been specified | |||
| 136 | Sales document type & does not exist | |||
| 137 | System error posting an internal table ( & ) | |||
| 138 | Access sequence & does not exist | |||
| 139 | Item category & does not exist | |||
| 140 | Equipment task list selectn not possible, as order contains no equipment | |||
| 141 | Delivery type & does not exist | |||
| 142 | Billing type & does not exist | |||
| 143 | Account group & does not exist | |||
| 144 | Text ID & does not exist | |||
| 145 | The language must be clearly specified | |||
| 146 | Include & does not exist | |||
| 147 | No access sequences can be defined for customer texts | |||
| 148 | Only text types can be defined for contact persons | |||
| 149 | No separate text procedures can be defined for billing item texts | |||
| 150 | Deletion not allowed: Text ID & is still being used. | |||
| 151 | No task list selected | |||
| 152 | Only special text objects are allowed | |||
| 153 | The language does not come from the partner function AG for MVKE | |||
| 154 | This combination (&,&) already exists | |||
| 155 | Language & is not defined | |||
| 156 | Partner function & not defined | |||
| 157 | This combination (&,&) is not defined | |||
| 158 | Access generated | |||
| 159 | Text determination procedure & already exists | |||
| 160 | Enter a number for the text determination procedure | |||
| 161 | Access sequence & already exists | |||
| 162 | Task list selection for order from maintenance plan not allowed | |||
| 163 | Enter a number for the access sequence | |||
| 164 | Copying control module & does not exist | |||
| 165 | Text ID & in Procedure & & does not exist in TTXID | |||
| 166 | Text determination procedure & does not exist in Table & | |||
| 167 | Text ID & is already present in the text determination procedure | |||
| 168 | A unit must be assigned to the time period entered | |||
| 169 | Please maintain the unit only in the existing time period | |||
| 170 | Calendar ID and time period cannot be maintained at the same time | |||
| 171 | Calendar ID and time period cannot be maintained at the same time | |||
| 172 | The cancellation period can only be assigned a positive value | |||
| 173 | Task list selection not possible due to order status | |||
| 174 | Deleting not allowed: the entry is being used in another position | |||
| 175 | There are no pop-up windows for billing document texts | |||
| 176 | The FORM routine & is not active or not available | |||
| 177 | 'Last of month' field and calendar ID cannot be maintained at one time | |||
| 178 | The rule for the contract start date refers to the contract start date | |||
| 179 | The rule for the contract end date refers to the contract end date | |||
| 180 | General maint.task list & & included | |||
| 181 | Partner control | |||
| 182 | Please select a partner object | |||
| 183 | You have selected more than one object: please select only one | |||
| 184 | System error occurred reading Internal table ( & ) | |||
| 185 | The entry already exists | |||
| 186 | Partner determination procedure & does not exist | |||
| 187 | Sales document type & does not exist | |||
| 188 | System error posting an internal table ( & ) | |||
| 189 | Partner determtn procedure & is already being used for Partner object & | |||
| 190 | Item category & does not exist | |||
| 191 | Equipment task list & & included | |||
| 192 | Transport into delivery system is only possible using & | |||
| 193 | Maintaining new partner functions in & is only possible in central functn | |||
| 194 | Partner function & has not been created | |||
| 195 | Partner function & cannot be used for partner procedures | |||
| 196 | Only customer partner functions can be defined as sources | |||
| 197 | Partner function does not exist in the customer partner determtn procdr | |||
| 198 | Deletion not allowed: Function & is used elsewhere | |||
| 199 | System: No operations could be determined | |||
| 200 | Partner determination procedure & not defined for customer master | |||
| 201 | Partner determination procedure & not defined for sales document headers | |||
| 202 | Partner determination procedure & not defined for sales document items | |||
| 203 | Partner determination procedure & is not defined for deliveries | |||
| 204 | Partner determination procedure & not defined for billing header(s) | |||
| 205 | Partner determination procedure & is not defined for billing items | |||
| 206 | Partner determination procedure & is not defined for sales activities | |||
| 207 | Include task list: operation number - number overflow | |||
| 208 | Sales documents require a sold-to party that cannot be changed | |||
| 209 | Sales document items may not have a sold-to party | |||
| 210 | Deliveries require a ship-to party that cannot be changed | |||
| 211 | Billing items may not have a payer | |||
| 212 | A payer which cannot be changed is required for billing documents | |||
| 213 | No operation selected | |||
| 214 | Assignment only makes sense for customer functions | |||
| 215 | Another partner function has already been converted to & | |||
| 216 | Function & is not used in Procedure & | |||
| 217 | Function & is a higher-level function than Function & | |||
| 218 | Partner function & does not exist | |||
| 219 | You cannot block Object & in display mode | |||
| 220 | Entries saved | |||
| 221 | Partner & is not defined | |||
| 222 | Select a sort field which is greater than that assigned to source functn | |||
| 223 | Sort sequences of previously determined partners are inconsistent | |||
| 224 | *** Maintenance plan calls | |||
| 225 | Conditions, Pricing | |||
| 226 | Function & does not exist | |||
| 227 | Initialization error for View & | |||
| 228 | Maintenance error for view & | |||
| 229 | Both groups need to be defined | |||
| 230 | Procedure & requires two groups | |||
| 231 | No package for call exists | |||
| 232 | Accrual billing document type & does not exist | |||
| 233 | Only accrual billing document types w/o cancellation billing type allowed | |||
| 234 | Maintenance plan data in order header incomplete | |||
| 235 | Error in determining costs for maint.item & schedule & : -> error log | |||
| 236 | Error in order schedule for maint.item & schedule & : -> error log | |||
| 237 | Posting terminated & with SY-Subrc & | |||
| 238 | Copy control, Graphics | |||
| 239 | Table & is blocked. It can only be displayed. | |||
| 240 | ABEND due to system error | |||
| 241 | Caution: Order resulted from counter-based maintenance | |||
| 242 | Incompletion log | |||
| 243 | Procedure & does not exist | |||
| 244 | Procedure & already exists | |||
| 245 | Procedure & saved | |||
| 246 | Procedure & deleted | |||
| 247 | Procedure & referred to elsewhere | |||
| 248 | & | |||
| 249 | Procedure & is already assigned to item category & | |||
| 250 | Procedure & is already assigned to Schedule line category & | |||
| 251 | Procedure & is already assigned to Partner function & | |||
| 252 | Procedure & already has texts assigned to it | |||
| 253 | Procedure & is already assigned to Sales document type & | |||
| 254 | Procedure & will be deleted when you press 'Enter' | |||
| 255 | Select one object only for processing | |||
| 256 | Enter an incompletion procedure for editing | |||
| 257 | Incompletion procedure & is already defined for another object | |||
| 258 | Enter an incompletion procedure | |||
| 259 | Incompletion procedure & is not defined for sales document types | |||
| 260 | Incompletion procedure & is not defined for items | |||
| 261 | Incompletion procedure & is not defined for schedule lines | |||
| 262 | Changes will not be saved when you press 'Enter' | |||
| 263 | Procedure is still being used: Object & cannot be blocked | |||
| 264 | Procedure is still being used: usages will be deleted | |||
| 265 | Incompletion procedure & is not defined for sales activities | |||
| 266 | Status group & does not exist | |||
| 267 | *** Status *** | |||
| 268 | System: Status object does not exist | |||
| 269 | System: Status profile & not allowed with object type & | |||
| 270 | *** CUA Status and CUA Title *** | |||
| 271 | System: CUA status could not be determined ( & & ) | |||
| 272 | System: CUA status: & & | |||
| 273 | ** PRT *** | |||
| 274 | System: Entry in system table does not exist ( & & & & & ) |
History
| Last changed on/by | 19971218 | SAP | |
| SAP Release Created in |