SAP ABAP Message Class VT (SD Tables)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BF (Application Component) Basic Functions
⤷
VA0C (Package) Customizing R/3 sales
⤷
⤷
Attributes
| Message class | VT | |
| Short Description | SD Tables | |
| Changed On | 20140121 | |
| Last Changed At | 105429 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | *** General messages for sales and distribution tables | |||
| 2 | Source = A forbids specification of subsequent screen group and panel | |||
| 3 | Source = & forbids specification of subsequent parameters | |||
| 4 | Source = & requires specification of subsequent parameters | |||
| 5 | Source = & allows only saving operations that are not negative | |||
| 6 | The storage operation '0' allowed for Source=A has been set | |||
| 7 | Source = & requires a subsequent FCode. Is BLANK allowed? | |||
| 8 | Source = F requires a FORM routine without subsequent parameters | |||
| 9 | Source was set on F because only one FORM routine was specified | |||
| 10 | Source = & not defined | |||
| 11 | Source = Z requires a storage operation not equal to 0 | |||
| 12 | Source = & allows only negative storage operations | Space: object requires documentation | ||
| 13 | Please use transaction 'VFBS' to maintain next screen processing | Space: object requires documentation | ||
| 14 | Maintaining this table is currently forbidden | Space: object requires documentation | ||
| 15 | Substitution of serviceable item matl with service product not consistent | Space: object requires documentation | ||
| 16 | For safety reasons deletion is only allowed in a work area | |||
| 17 | For safety reasons deletion is only allowed in a screen group | |||
| 18 | Changes were not adopted, because no correction was entered | |||
| 19 | Billing quantity G or H is not permitted for billing relevant M | Space: object requires documentation | ||
| 20 | In language & the conversion & already exists for & | |||
| 21 | Sales document type & is not defined | Space: object requires documentation | ||
| 22 | Order type '&' is not defined for sales area <'&','&','&'> | Space: object requires documentation | ||
| 23 | Sales area conversion table has been updated | Space: object requires documentation | ||
| 24 | System error when updating sales areas | Space: object requires documentation | ||
| 25 | Required entry not made | Space: object requires documentation | ||
| 26 | In table & there is no field & | |||
| 27 | No processing location specified | |||
| 28 | Only one of the & fields may be filled | |||
| 29 | Do not make multiple entries for the processing location | |||
| 30 | The screen in the function module requires the input of a routine | |||
| 31 | Transaction & code not defined | Space: object requires documentation | ||
| 32 | Screen & does not exist | Space: object requires documentation | ||
| 33 | Menu & not defined in TSTC | |||
| 34 | The entered number range & does not exist | |||
| 35 | Internal and external number ranges may not be identical | |||
| 36 | Number range & not defined for external number assignment | |||
| 37 | Number range & not defined for internal number assignment | |||
| 38 | Number range object & does not exist | |||
| 39 | Functional area is not possible for account assignment category &1 | Space: object requires documentation | ||
| 40 | Transaction type & already exists | |||
| 41 | Account assignment category & has not been defined | Space: object requires documentation | ||
| 42 | Sales organization & is not defined | Space: object requires documentation | ||
| 43 | Dunning type & not defined in company code & | |||
| 44 | Table & could not be locked | |||
| 45 | Copying control module & newly created | |||
| 46 | Copying control module & successfully created | |||
| 47 | Copying control module & does not exist | |||
| 48 | Item category and classification type are defined | |||
| 49 | End of list screen has been reached | |||
| 50 | Beginning of list screen has been reached | |||
| 51 | New table entry generated | |||
| 52 | Sales document type & is not available | Space: object requires documentation | ||
| 53 | Checking is in process: Entry & & & is missing from TVCPA | |||
| 54 | Check completed | |||
| 55 | Delivery type '&' is not available | Space: object requires documentation | ||
| 56 | The text ID & already defined for this text group | |||
| 57 | Text object & does not have the text ID &. | |||
| 58 | Text object & not defined | |||
| 59 | Combination not allowed | |||
| 60 | Plant is already allocated to company code & | |||
| 61 | The combination (text object &, text ID &) is not defined | |||
| 62 | You can only enter one original language | |||
| 63 | The probability must be between 0 and 100% | |||
| 64 | A probability of < 100% is only allowed in inquiries and quotations | |||
| 65 | The combination of ( & , & ) is missing from Table TVKOV | |||
| 66 | The referenced distribution channel & cannot be converted | |||
| 67 | Schedule line category & is not defined | |||
| 68 | Output type & not defined | |||
| 69 | Distribution channel is proposed | |||
| 70 | Referenced sales org. & and distribution channel & do not exist | |||
| 71 | Referenced sales org & and division & do not exist | |||
| 72 | Referenced division & cannot be changed | |||
| 73 | Sales organization & does not exist | |||
| 74 | The reference sales organization & cannot be converted | |||
| 75 | Plant & is not defined | |||
| 76 | Please set the print parameters in Customizing | |||
| 77 | Sales areas are blocked by other users: You can only display them | |||
| 78 | System error: Blocking unsuccessful, can only be displayed | |||
| 79 | No addresses maintained up to now | |||
| 80 | Sales organization & is referenced by sales organiz.& | |||
| 81 | Distribution channel & is referenced by distribution channel & | |||
| 82 | Division & is referenced by division & | |||
| 83 | Distribution channel & is still required as a customer distrib. channel | |||
| 84 | Division & is still required as a customer division | |||
| 85 | The customer for inter-company billing missing in SOrg & | |||
| 86 | Organizational data for inter-company billing missing in plant & | |||
| 87 | SOrg belongs to CCode & and the plant to CCode & | |||
| 88 | Sales organization & is still required for conversion | |||
| 89 | Sales organization & is still used for division conversion | |||
| 90 | Sales organization & is still used for distribution channel conversion | |||
| 91 | Sales organization & is used for sales area conversion | |||
| 92 | Partner function & does not exist | |||
| 93 | Enter either a sales document or billing type only | |||
| 94 | The sales org. is part of company code &, plant & is part of comp.code & | |||
| 95 | The combination ( & , & ) is missing in TVKOS | |||
| 96 | Only enter an order type for assembly types '2' or '3' | Space: object requires documentation | ||
| 97 | Component avail.check/dialog control only allowed for assembly processing | |||
| 98 | Order type $ is not defined | |||
| 99 | If necessary, enter a configuration strategy | |||
| 100 | A configuration strategy is not necessary when | |||
| 101 | Configuration strategy & is not defined in Table 476 | |||
| 102 | Manual application/alternative is only allowed for struct.scope = A/B | |||
| 103 | Order type $ contains category $ which is not allowed | |||
| 104 | Order type $ has external number assignment | |||
| 105 | Assembly requires assignment category E or D or valuated special stock | Space: object requires documentation | ||
| 106 | Control for type matching is only allowed if scope of structure = D | |||
| 107 | Avail.and action f.configur.mats.only poss. when type matching is active | |||
| 108 | You need to enter an order type for assembly types '2' and '3' | Space: object requires documentation | ||
| 109 | Enter either an assembly type or order change management only | Space: object requires documentation | ||
| 110 | Sub-items for manual strategy are not supported | |||
| 111 | Account assignment category & has not been defined | |||
| 112 | In autom. single-segment planning, the transfer of requir. must be active | |||
| 113 | Autom. individual requ. planning requires an account assignment category | |||
| 114 | Account assignment category & does not result in make-to-order production | |||
| 115 | Assembly type '2' does not allow unit or product costing | |||
| 116 | Switching to assembly type &1 is not valid | |||
| 117 | Issue of a warning is not supported for product selection | |||
| 118 | The development class of condition table & & is local | |||
| 119 | Automatic calculation only possible if calculation is allowed | Space: object requires documentation | ||
| 120 | Automatic calculation only possible with a calculation variant | Space: object requires documentation | ||
| 121 | Calculation variant is not valid for automatic calculation | Space: object requires documentation | ||
| 122 | Automatic costing is only valid for product costing | Space: object requires documentation | ||
| 123 | The costing variant is not valid for this costing method | Space: object requires documentation | ||
| 124 | Transfer of preliminary costing only permitted for stat. assembly | Space: object requires documentation | ||
| 125 | Variant &2 has not been defined for transaction &1 | Space: object requires documentation | ||
| 126 | Order type &1 is not permitted | Space: object requires documentation | ||
| 127 | If default item cat. activated: Target billing type must be credit memo | Space: object requires documentation | ||
| 128 | If default item category activated: Billing quantity must be E or F | Space: object requires documentation | ||
| 129 | Only special stock with separate valuation can be marked. | Space: object requires documentation | ||
| 130 | Condition type & can only be used once per country. | Space: object requires documentation | ||
| 131 | The entry has been saved | |||
| 132 | Check the existing conversion for distribution channel and division | |||
| 133 | If configuration is copied, you are not permitted to explode BOM | Space: object requires documentation | ||
| 134 | *** Conditions: Control tables *** | |||
| 135 | Maintain the item data | |||
| 136 | Maximum number of 999 accesses in module pool & already reached | |||
| 137 | Condition maintenance for application & has not been defined | |||
| 138 | Enter a subtotal between 1 and 7 for step & | |||
| 139 | Condition type & may only be used once | |||
| 140 | Table & is not defined | |||
| 141 | Defaults adopted from the Data Dictionary | |||
| 142 | Table & not defined | |||
| 143 | Field & not defined | |||
| 144 | Select a document field for & | Space: object requires documentation | ||
| 145 | Data division (T685&) not defined for usage | |||
| 146 | The numeric constant entered is longer than the target field | |||
| 147 | Please do not set a source value for the initial value indicator | |||
| 148 | System error: Entry & missing from table & | |||
| 149 | System error: Entry & & & missing from table & | |||
| 150 | Please use transactions VK01, VK02 or VK03 | |||
| 151 | All access sequences successfully generated | |||
| 152 | Activate only between 0.00 and 8.00 | Space: object requires documentation | ||
| 153 | Entry & & & missing in table & | |||
| 154 | Condition type & not defined | |||
| 155 | Usage & not defined | |||
| 156 | Application & not defined | |||
| 157 | Usage & and application & not defined | |||
| 158 | There are no access sequences to optimize | |||
| 159 | Requirement & not defined | Space: object requires documentation | ||
| 160 | Formula & not defined | |||
| 161 | Condition type & is not defined | |||
| 162 | Item & is already listed. | |||
| 163 | Item & & is already listed | |||
| 164 | Error found in access sequence & | |||
| 165 | The condition types are being processed: They can only be displayed | |||
| 166 | Access sequences are being processed: They can only be displayed | |||
| 167 | Pricing procedures are being processed: They can only be displayed | |||
| 168 | All access sequences are already active | |||
| 169 | Unexpected FCODE = & | |||
| 170 | Referenced by pricing procedure &: Cannot be deleted | |||
| 171 | Referenced by access sequence &: Cannot be deleted | |||
| 172 | Referenced by condition type &: Cannot be deleted | |||
| 173 | Unit of measure & not defined | |||
| 174 | Please do not enter a unit of measure for a value scale | |||
| 175 | Access sequence & only reads the pre-step | |||
| 176 | Cursor not properly positioned on a condition type | |||
| 177 | There are no access sequences for condition type & | |||
| 178 | Access sequences defined by the user must begin with Y or Z | |||
| 179 | Please test with new entries only in module pool 'T' | |||
| 180 | Condition type & already listed | |||
| 181 | Initialization error for view & | |||
| 182 | Maintenance error for view & | |||
| 183 | Access sequence lies in the customer sector: It can only be displayed | |||
| 184 | Access sequence & is not defined | |||
| 185 | Procedure & is not defined | |||
| 186 | Enter a table | |||
| 187 | Account key & not defined | |||
| 188 | System error: Object could not be blocked | |||
| 189 | Enter a condition type | |||
| 190 | Access sequence & is within the SAP sector: It can only be displayed | |||
| 191 | SAP access sequences cannot begin with Y or Z | |||
| 192 | Please enter a module pool between 'A' and 'M' | |||
| 193 | Please enter a module pool between 'N' and 'Z'. | |||
| 194 | Output type & does not require any mail texts | |||
| 195 | A text already exists for output category &, language & | |||
| 196 | No text exists in language & for output & | |||
| 197 | An access sequence is not defined for the header condition | |||
| 198 | Access sequence & for output & is revoked | |||
| 199 | Tax determination procedure & does not exist | |||
| 200 | Do not use scale formulas for subsequent refunds | |||
| 201 | Output type & requires a message title | |||
| 202 | Access sequence & lies in the SAP sector. | |||
| 203 | Access sequence & lies in the customer sector. | |||
| 204 | Access sequences cannot be changed in the delivery system | |||
| 205 | Referenced by condition type & in client &: Cannot be deleted | |||
| 206 | %A No maintenance authorization for usage & application & | |||
| 207 | %A No display authorization for usage & application & | |||
| 208 | Enter a unit of measure | |||
| 209 | Group condition with calculat.type 'B' and grp.cond.routine not defined | |||
| 210 | Access sequence is not defined for condition category | |||
| 211 | GrpCndRoutine without rounding diff. not defined for calculation rule & | Space: object requires documentation | ||
| 212 | Calculation & is not defined for application | |||
| 213 | Calculation type or scale basis is not defined for condition class | |||
| 214 | Calculation type or scale basis is not defined for group conditions | |||
| 215 | Scale basis and calculation type must be identical | |||
| 216 | Unit of measure & is not defined for scale basis | |||
| 217 | Billing quantity & is not defined for delivery-related billing | |||
| 218 | Billing quantity & is not defined for the pro forma invoice | |||
| 219 | Qty/value pos/neg & not defined for billing type & | |||
| 220 | Condition update is not defined for condition class & | |||
| 221 | Condition update is not defined for calculation type & | |||
| 222 | Data field "Quantity/Value pos/neg" has the value ' ' | |||
| 223 | '+' or '-' only allowed in connection with completion rule for item cat. | |||
| 224 | Be careful when using Pricing type & | |||
| 225 | Condition class & has not been designed for structure condition & | |||
| 226 | Calculation type & has not been designed for structure condition & | |||
| 227 | Structure condition & should not be a header condition | |||
| 228 | Group condition routines not designed for structure condition & | |||
| 229 | You cannot change values manually for structure condition & | |||
| 230 | Structure condition & does not have an access sequence | |||
| 231 | Structure condition & should not be a group condition | |||
| 232 | You cannot enter & manually for structure condition & | |||
| 233 | Cumulation condition & should be a statistical value | |||
| 234 | Sales function & & & not defined | |||
| 235 | Condition type & should be assigned to calculation type 36 | |||
| 236 | Structure condition & should be a group condition | |||
| 237 | Condition category & only valid for condition class & | |||
| 238 | Condition category & has not been desigend for structure condition & | |||
| 239 | You cannot specify a pricing procedure for condition category & | |||
| 240 | The Field From &1 must be smaller than the current level number &2 | |||
| 241 | The field To &1 must be smaller than the current level number &2 | |||
| 242 | For milestone billing, the system only allows pricing types D, G and K | Space: object requires documentation | ||
| 243 | You should use the counter only for manual item conditions | |||
| 244 | Condition category & is not valid for condition class & | |||
| 245 | Unfavorable sequence of fields - Possible performance problems | Space: object requires documentation | ||
| 246 | Exclusion group & does not only contain group conditions | Space: object requires documentation | ||
| 247 | Inv. corr. requests with sls doc. cat. K must have pricing det. type 'E' | Space: object requires documentation | ||
| 248 | During inv. correction requests, second item must be a debit memo item | Space: object requires documentation | ||
| 249 | An invoice correction request must be created with ref. to an invoice | Space: object requires documentation | ||
| 250 | Rounding difference is always settled for group cond. w/o grp key rout. | Space: object requires documentation | ||
| 251 | Inv. corr. requests with sls doc cat L must have pricing det. type 'F' | Space: object requires documentation | ||
| 252 | During inv. correction requests, first item must be a credit memo item | Space: object requires documentation | ||
| 253 | Only characteristic ' ' and G can be used as price source | Space: object requires documentation | ||
| 254 | Quantity/value pos/neg field must be ' ' for credit memos to billing docs | Space: object requires documentation | ||
| 255 | The assignment and reference number fields must be ' ' or E | Space: object requires documentation | ||
| 256 | Scale type 'D' cannot be used for group condition 'X' | Space: object requires documentation | ||
| 257 | The system selects several records because they have the same evaluation | Space: object requires documentation | ||
| 258 | Enter a priority for the field marked as free | Space: object requires documentation | ||
| 259 | The same evaluation is not possible for accesses for volume-based rebates | Space: object requires documentation | ||
| 260 | For rebates, each field must be relevant to the access | Space: object requires documentation | ||
| 261 | A release block is not possible for condition class & | Space: object requires documentation | ||
| 262 | Access type C is not defined for key fields | Space: object requires documentation | ||
| 263 | Standard proposal for CTyp &1 Req = &2, Calfor = &3 Basfor = &4 | Space: object requires documentation | ||
| 264 | Standard proposal for CTyp &1, Manu = X Subtot = &2, Req =&3 Calfor =&4 | Space: object requires documentation | ||
| 265 | Standard proposal for CTyp &1 stat = X, Subtot = &2 Req = &3, Basfor=&4 | Space: object requires documentation | ||
| 266 | Standard proposal for CTyp &1 Mand = X Req = &2 Basfor = &3 AccKey = &4 | Space: object requires documentation | ||
| 267 | Standard proposal for CTyp &1, Stat = X Req = &2 Acckey = &3 | Space: object requires documentation | ||
| 268 | Determined values can only be transmitted in & | Space: object requires documentation | ||
| 269 | Pricing type & is not defined in application & | Space: object requires documentation | ||
| 270 | Enter calculation type (condition type has calc. type &2, period &3) | Space: object requires documentation | ||
| 271 | Enter calculation type (condition type has calculation type &2) | Space: object requires documentation | ||
| 272 | Maintain separate max. values for accruals (cond. type &1, calc. type A) | Space: object requires documentation | ||
| 273 | Calculation type not allowed (valid values &2 and A) | Space: object requires documentation | ||
| 274 | This function is not supported in maintaining access sequences | Space: object requires documentation | ||
| 275 | Access sequence is still being used in procedure '&' ! | Space: object requires documentation | ||
| 276 | Procedure '&' is not set up for text object '&' | Space: object requires documentation | ||
| 277 | You cannot choose 'Display' and 'Mandatory text' for the same text | Space: object requires documentation | ||
| 278 | The function has terminated | Space: object requires documentation | ||
| 279 | The system does not save the data | Space: object requires documentation | ||
| 280 | Table & is blocked by user &: Display only | Space: object requires documentation | ||
| 281 | Processing status & does not exist | Space: object requires documentation | ||
| 282 | Update document flow for quantity-related completion | Space: object requires documentation | ||
| 283 | Enter a valid name for the procedure | Space: object requires documentation | ||
| 284 | Different calculation type not allowed (cond. type &1 has calc.type &2) | Space: object requires documentation | ||
| 285 | Different calculation type not allowed (cond. type &1 has calc.type &2) | Space: object requires documentation | ||
| 286 | Period calculation rule &1 not supported for this application | Space: object requires documentation | ||
| 287 | Scale base type &1 not supported for this application | Space: object requires documentation | ||
| 288 | Choose a condition exclusion procedure | The short text describes the object sufficiently | ||
| 289 | Maintain both condition exclusion groups | The short text describes the object sufficiently | ||
| 290 | Maintain two different condition exclusion groups | The short text describes the object sufficiently | ||
| 291 | Only fill one cond. exclusion group with this cond. exclusion procedure | The short text describes the object sufficiently | ||
| 292 | Fill condition exclusion group 1 | The short text describes the object sufficiently | ||
| 293 | Hierarchical access combined with customer hierarchies not possible | Space: object requires documentation | ||
| 294 | Access sequence &1 inconsistent; target field &3 missing in access &2 | Space: object requires documentation | ||
| 295 | Hierarchical access combined with target field &3 not possible | Space: object requires documentation | ||
| 296 | Internal error &2 when saving access sequence &1 (see long text) | Space: object requires documentation | ||
| 297 | Do you want access to table field &1 with the initial direct value? | The short text describes the object sufficiently | ||
| 298 | Access sequence A not possible (access sequence &1, access &2, field &3) | Space: object requires documentation | ||
| 299 | Pricing for condition type &1, access sequence &2 not possible | The short text describes the object sufficiently | ||
| 300 | You are not authorized to execute the report | The short text describes the object sufficiently | ||
| 301 | Access sequence does not exist (check your entries) | The short text describes the object sufficiently | ||
| 302 | Error updating table T682V | The short text describes the object sufficiently | ||
| 303 | A total of &1 records were updated | The short text describes the object sufficiently | ||
| 304 | Could not calculate group conditions using CPF | The short text describes the object sufficiently | ||
| 305 | Calculation type "T" cannot be used with CPF | The short text describes the object sufficiently | ||
| 306 | Access type A is not available (access sequence &1, access &2) | Space: object requires documentation | ||
| 307 | Multi-value attributes are not supported | Space: object requires documentation | ||
| 308 | Data determination in the access is not supported: Condition &1 | Space: object requires documentation | ||
| 309 | The use of partners is not allowed for output not dependent on partners | |||
| 310 | Group is used in sales documents, so the sold-to party cannot be changed | |||
| 311 | Group is used in deliveries, so the ship-to party cannot be changed | |||
| 312 | Group is used in billing, so the payer cannot be changed | |||
| 313 | Partner grp & doesn't contain any sold-to parties which can't be changed | |||
| 314 | Partner grp & doesn't contain any ship-to parties which can't be changed | |||
| 315 | Partner group & does not contain any payers which cannot be changed | |||
| 316 | The cost center is not defined | |||
| 317 | Maintain in Customizing SD: Functions: Partner Determination (TCODE VOPA) | |||
| 318 | Function module ZZ_SD_USEREXIT_PARTNER does not exist | |||
| 319 | Account assignment category & is invalid | |||
| 320 | Cost center &1 does not belong to company code &2 | Space: object requires documentation | ||
| 321 | The flag Extend Data must not be selected | Space: object requires documentation | ||
| 322 | Acc. assignment category &1 only allowed for valuated sales order stock | Space: object requires documentation | ||
| 323 | Account assignmt cat. &1 is not permitted for evaluated sales order stock | Space: object requires documentation | ||
| 324 | The pricing procedure for account determination must be empty. | Space: object requires documentation | ||
| 325 | No errors were found in Customizing. | Space: object requires documentation | ||
| 326 | Billing quantity 'F' must be used for item category billing relevance 'F' | Space: object requires documentation | ||
| 327 | For delivery-related billing, the field 'Quantity pos/neg' must be '+'. | Space: object requires documentation | ||
| 328 | If access sequence not available, scale type 'D' not possible. | Space: object requires documentation | ||
| 329 | A maximum of 99 condition supplements are permitted in pricing procedure. | Space: object requires documentation | ||
| 330 | Calculation type reference cond. type not equal to calc. type cond. type | Space: object requires documentation | ||
| 331 | Final Settlement and Correction flds must be maint. in rebate settlement | Space: object requires documentation | ||
| 332 | Relevant billing type for final settlement must be: Final settlement='A' | Space: object requires documentation | ||
| 333 | Relevant billing type for final settlement must be: Rel. to rebate ='X' | Space: object requires documentation | ||
| 334 | Canc. of billing type for final settlement must be: Rel. to rebate ='X' | Space: object requires documentation | ||
| 335 | Relevant billing type for correctin must be: Relevant to rebate ='B' | Space: object requires documentation | ||
| 336 | Relevant billing type for correction must be: Relevant to rebate ='X' | Space: object requires documentation | ||
| 337 | Canc. of billing type for correction must be: Relevant to rebate ='X' | Space: object requires documentation | ||
| 338 | Relevant billing type for partial settlement must be: Rel.to rebate = 'C' | Space: object requires documentation | ||
| 339 | Relevant billing type for partial settlement must be: Rel.to rebate = 'X' | Space: object requires documentation | ||
| 340 | Canc. of billing type for partial settlement must be: Rel.to rebate = 'X' | Space: object requires documentation | ||
| 341 | Relevant billing type for manual accrual must be: Rel. to rebate ='D' | Space: object requires documentation | ||
| 342 | Relevant billing type for manual accrual must be: Rel. to rebate ='X' | Space: object requires documentation | ||
| 343 | Canc.of bill.type for man.accr.sal.ord.type must be: Rel. to rebate ='X' | Space: object requires documentation |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in |