W3 - Nachrichten f�r WebRFC
The following messages are stored in message class W3: Nachrichten f�r WebRFC.
It is part of development package SWWW in software component BC-CI-WEBR. This development package consists of objects that can be grouped under "Package for Basis WWW Project".
It is part of development package SWWW in software component BC-CI-WEBR. This development package consists of objects that can be grouped under "Package for Basis WWW Project".
Message Nr ▲ | Message Text |
|---|---|
| 00 | **** Structure explosion ************** |
| 000 | ******* 001-009 : hierarchical display of product hierarchy ******* |
| 001 | Object & already exists |
| 01 | An equipment must be entered before making an assembly selection |
| 002 | Specify a MIME type |
| 02 | No bill of material exists |
| 003 | Specify a processing program |
| 03 | No reference object selected |
| 004 | Specify a name for the object |
| 04 | The order was created w/o reference to a notification |
| 005 | Please enter a development class. |
| 05 | The order has no reference to a functional location |
| 006 | Select an entry |
| 06 | No equipment was entered in the order |
| 007 | Object & already processed |
| 008 | Program for editing Web object does not exist |
| 009 | No MIME type assigned to object & |
| 010 | Only object types HTML, MIME, HTRC and SRVC are supported |
| 011 | Incorrect language |
| 012 | Development class &1 does not exist. |
| 013 | Report &1 has been successfully released for the Internet |
| 014 | Report &1 has already been released for the Internet. |
| 015 | Error when canceling release of report &1 |
| 016 | The release of Report &1 for the Internet has been reset |
| 017 | The release of Report &1 cannot be reset |
| 018 | No reports have been released for the Internet |
| 019 | Report &1 does not exist; check the spelling |
| 020 | The release of function module &1 cannot be undone |
| 20 | *** Task list connection |
| 021 | An error occurred when resetting the release of function module &1 |
| 21 | Equipment task list selectn not possible, as order contains no equipment |
| 022 | Internet release of function module &1 has been reset |
| 22 | No task list selected |
| 023 | Module &1 does not exist; check the spelling |
| 23 | Task list selection for order from maintenance plan not allowed |
| 024 | The function module &1 has been released for the Internet. |
| 24 | Task list selection not possible due to order status |
| 025 | The function module &1 has already been released for the Internet |
| 25 | General maint.task list & & included |
| 026 | No function modules have yet been released for the Internet. |
| 26 | Equipment task list & & included |
| 027 | The authorization group for report &1 is not defined |
| 27 | System: No operations could be determined |
| 028 | No report trees have yet been released for the Internet. |
| 28 | Include task list: operation number - number overflow |
| 029 | Tree &1 does not exist; check the spelling. |
| 29 | No operation selected |
| 030 | Report tree &1 has been released for the Internet |
| 30 | *** Maintenance plan calls |
| 031 | Report tree &1 has already been for the Internet. |
| 31 | No package for call exists |
| 032 | The release of report tree &1 cannot be revoked. |
| 32 | Maintenance plan data in order header incomplete |
| 033 | An error has occurred when resetting the release of report tree &1. |
| 33 | Error in determining costs for maint.item & schedule & : -> error log |
| 034 | Report tree &1 has been released for the Internet |
| 34 | Error in order schedule for maint.item & schedule & : -> error log |
| 035 | There are no report trees in your system |
| 35 | Posting terminated & with SY-Subrc & |
| 036 | Hierarchy type is missing: Assignments cannot be made |
| 36 | Caution: Order resulted from counter-based maintenance |
| 037 | Error updating assignment & |
| 038 | Node cannot be deleted: invalid assignments would occur |
| 039 | Vendor & not maintained for purchasing organization & |
| 040 | Object &1 is already locked in a correction request |
| 041 | Selection date lies in the past: Data will only be displayed |
| 042 | Vendor $ not maintained |
| 043 | Vendor & not defined as being assigned to & |
| 044 | Please enter a purchasing organization |
| 045 | Purchasing organization cannot be entered without vendor number |
| 046 | Please enter a vendor number |
| 047 | Assignment not possible (higher-level vendor not maintained) |
| 048 | Purchasing organization assignment is not defined |
| 050 | Valid-from date cannot lie in the past |
| 50 | *** Status *** |
| 051 | Validity period is not allowed (From-date lies after the to-date) |
| 51 | System: Status object does not exist |
| 052 | The assignment is also active outside of the given time period |
| 52 | System: Status profile & not allowed with object type & |
| 053 | The assignment is already active in the given time period |
| 054 | Different assignments exist outside of the given time period |
| 055 | Incorrect assignments cannot be processed |
| 056 | Select hierarchy node |
| 058 | Node & will be assigned to the same level |
| 059 | Select hierarchy header nodes for higher-level assignment |
| 060 | Selected sub-hierarchy contains all nodes and cannot be reassigned |
| 60 | *** CUA Status and CUA Title *** |
| 061 | Nodes cannot be reassigned: unpermitted assignments would occur |
| 61 | System: CUA status could not be determined ( & & ) |
| 062 | Hierarchy contains no allowed alternative higher-level assignments |
| 063 | Higher-level node already maintained as a subordinate node |
| 63 | System: CUA status: & & |
| 064 | Assigned node is also a higher-level node |
| 065 | You cannot assign node to itself |
| 066 | Assignment has different attributes outside of the given time period |
| 071 | Partner determination error: Function not possible |
| 073 | There are no hierarchy nodes to be displayed |
| 074 | Function not possible: Maximum number of hierarchy steps (26) exceeded |
| 075 | Lowest hierarchy level reached (26): lower steps will be ignored |
| 75 | ** PRT *** |
| 076 | Hierarchy node cannot be removed as invalid assignments would arise |
| 76 | System: Entry in system table does not exist ( & & & & & ) |
| 077 | Selected hierarchy node is a header node: subhierarchy cannot be removed |
| 078 | Select incorrect hierarchy nodes |
| 079 | Rebate and pricing assignments updated |
| 080 | Attributes (pricing, rebate) are up-to-date for all assignments |
| 081 | Date cannot be changed (inconsistent validity periods) |
| 082 | Hierarchy type & is not defined |
| 083 | Node & is not active or not available for selection date |
| 084 | Node & is not available in the hierarchy |
| 085 | Hierarchy level & cannot be transferred due to inconsistencies |
| 086 | Hierarchy level assignment(s) updated |
| 087 | Hierarchy level assignment not updated or not updated for all points |
| 088 | Assignment not allowed: incorrect hierarchy level assignment |
| 089 | 'Reassigning' can lead to inconsistencies in the hierarchy lvl assignmnt |
| 090 | Initial Date Limit(s): a new validity period has been proposed |
| 100 | Objects not included in transport request |
| 116 | Schedule line category & & deleted |
| 117 | Default indicator for & & & & cannot be reset |
| 118 | The new default item category for & & & is & |
| 119 | The new default schedule line category for & & is & |
| 120 | Default indicator for & & & cannot be reset |
| 121 | The new default item category for & & is & |
| 122 | Deletion unnecessary: no assignments exist |
| 123 | Enter a usage for structure configuration for BOM explosion |
| 124 | Internal error creating assignment table: Item categ & (ret code &) |
| 125 | No changes made to item category assignments |
| 126 | Changed item category assignments saved |
| 127 | Partner group & does not contain any payers who cannot be changed |
| 128 | Entry & & & missing in Table & |
| 129 | Item usage must be specified for item category group 'Blank' |
| 130 | Defaults for Item category & & changed |
| 131 | Customer-specific document types should begin with 'Z or Y' |
| 132 | Customer-specific item categories should begin with 'Z or Y' |
| 133 | Item category & already exists |
| 134 | Item category & & has been created |
| 135 | No changes made to the schedule line category assignments |
| 136 | Changes to schedule line category assignments have been saved |
| 137 | System blocking error for Table & |
| 138 | If a storage location is required, a batch check must be carried out |
| 139 | Error in transferring table entries to correction |
| 140 | The selected table entries have been transferred to correction |
| 141 | A condition type's access sequence in the pricing procedure is incorrect |
| 143 | An assignment for & already exists |
| 144 | Item category & is not allowed as a higher-level item category |
| 145 | Possible entries can only be displayed once the doc.type has been entered |
| 146 | Possible entries can only be displayed if a matl item category exists |
| 147 | Schedule line category & deleted from Table TVEP: please enter it again |
| 148 | Defaults for schedule line category & & changed |
| 149 | Schedule line category & & has been created |
| 150 | Schedule line category & already exists |
| 151 | Availability check without transfer of requirements is not allowed |
| 152 | Only condition types used for 'Pricing' are allowed |
| 200 | Text control |
| 201 | Please select a text object |
| 202 | You can only select one text object |
| 203 | System error occurred reading Internal table ( & ) |
| 204 | The entry already exists |
| 205 | Text determination procedure & has not been specified |
| 206 | Sales document type & does not exist |
| 207 | System error posting an internal table ( & ) |
| 208 | Access sequence & does not exist |
| 209 | Item category & does not exist |
| 210 | Delivery type & does not exist |
| 211 | Billing type & does not exist |
| 212 | Account group & does not exist |
| 213 | Text ID & does not exist |
| 214 | The language must be clearly specified |
| 215 | Include & does not exist |
| 216 | No access sequences can be defined for customer texts |
| 217 | Only text types can be defined for contact persons |
| 218 | No separate text procedures can be defined for billing item texts |
| 219 | Deletion not allowed: Text ID & is still being used. |
| 220 | Only special text objects are allowed |
| 221 | The language does not come from the partner function AG for MVKE |
| 222 | This combination (&,&) already exists |
| 223 | Language & is not defined |
| 224 | Partner function & not defined |
| 225 | This combination (&,&) is not defined |
| 226 | Access generated |
| 227 | Text determination procedure & already exists |
| 228 | Enter a number for the text determination procedure |
| 229 | Access sequence & already exists |
| 230 | Enter a number for the access sequence |
| 231 | Copying control module & does not exist |
| 232 | Text ID & in Procedure & & does not exist in TTXID |
| 233 | Text determination procedure & does not exist in Table & |
| 234 | Text ID & is already present in the text determination procedure |
| 235 | A unit must be assigned to the time period entered |
| 236 | Please maintain the unit only in the existing time period |
| 237 | Calendar ID and time period cannot be maintained at the same time |
| 238 | Calendar ID and time period cannot be maintained at the same time |
| 239 | The cancellation period can only be assigned a positive value |
| 240 | Deleting not allowed: the entry is being used in another position |
| 241 | There are no pop-up windows for billing document texts |
| 242 | The FORM routine & is not active or not available |
| 243 | 'Last of month' field and calendar ID cannot be maintained at one time |
| 244 | The rule for the contract start date refers to the contract start date |
| 245 | The rule for the contract end date refers to the contract end date |
| 250 | Partner control |
| 251 | Please select a partner object |
| 252 | You have selected more than one object: please select only one |
| 253 | System error occurred reading Internal table ( & ) |
| 254 | The entry already exists |
| 255 | Partner determination procedure & does not exist |
| 256 | Sales document type & does not exist |
| 257 | System error posting an internal table ( & ) |
| 258 | Partner determtn procedure & is already being used for Partner object & |
| 259 | Item category & does not exist |
| 260 | Transport into delivery system is only possible using & |
| 261 | Maintaining new partner functions in & is only possible in central functn |
| 263 | Partner function & has not been created |
| 264 | Partner function & cannot be used for partner procedures |
| 265 | Only customer partner functions can be defined as sources |
| 267 | Partner function does not exist in the customer partner determtn procdr |
| 269 | Deletion not allowed: Function & is used elsewhere |
| 270 | Partner determination procedure & not defined for customer master |
| 271 | Partner determination procedure & not defined for sales document headers |
| 272 | Partner determination procedure & not defined for sales document items |
| 273 | Partner determination procedure & is not defined for deliveries |
| 274 | Partner determination procedure & not defined for billing header(s) |
| 275 | Partner determination procedure & is not defined for billing items |
| 276 | Partner determination procedure & is not defined for sales activities |
| 280 | Sales documents require a sold-to party that cannot be changed |
| 281 | Sales document items may not have a sold-to party |
| 282 | Deliveries require a ship-to party that cannot be changed |
| 283 | Billing items may not have a payer |
| 284 | A payer which cannot be changed is required for billing documents |
| 290 | Assignment only makes sense for customer functions |
| 291 | Another partner function has already been converted to & |
| 292 | Function & is not used in Procedure & |
| 293 | Function & is a higher-level function than Function & |
| 294 | Partner function & does not exist |
| 295 | You cannot block Object & in display mode |
| 296 | Entries saved |
| 297 | Partner & is not defined |
| 298 | Select a sort field which is greater than that assigned to source functn |
| 299 | Sort sequences of previously determined partners are inconsistent |
| 300 | Conditions, Pricing |
| 301 | Function & does not exist |
| 302 | Initialization error for View & |
| 303 | Maintenance error for view & |
| 304 | Both groups need to be defined |
| 305 | Procedure & requires two groups |
| 310 | Accrual billing document type & does not exist |
| 311 | Only accrual billing document types w/o cancellation billing type allowed |
| 350 | Copy control, Graphics |
| 351 | Table & is blocked. It can only be displayed. |
| 352 | ABEND due to system error |
| 400 | Incompletion log |
| 401 | Procedure & does not exist |
| 402 | Procedure & already exists |
| 403 | Procedure & saved |
| 404 | Procedure & deleted |
| 405 | Procedure & referred to elsewhere |
| 406 | & |
| 407 | Procedure & is already assigned to item category & |
| 408 | Procedure & is already assigned to Schedule line category & |
| 409 | Procedure & is already assigned to Partner function & |
| 410 | Procedure & already has texts assigned to it |
| 411 | Procedure & is already assigned to Sales document type & |
| 412 | Procedure & will be deleted when you press 'Enter' |
| 413 | Select one object only for processing |
| 414 | Enter an incompletion procedure for editing |
| 415 | Incompletion procedure & is already defined for another object |
| 416 | Enter an incompletion procedure |
| 417 | Incompletion procedure & is not defined for sales document types |
| 418 | Incompletion procedure & is not defined for items |
| 419 | Incompletion procedure & is not defined for schedule lines |
| 420 | Changes will not be saved when you press 'Enter' |
| 421 | Procedure is still being used: Object & cannot be blocked |
| 422 | Procedure is still being used: usages will be deleted |
| 423 | Incompletion procedure & is not defined for sales activities |
| 424 | Status group & does not exist |