| VT655 |
Maintain both condition exclusion groups |
| VT656 |
Maintain two different condition exclusion groups |
| VT657 |
Only fill one cond. exclusion group with this cond. exclusion procedure |
| VT658 |
Fill condition exclusion group 1 |
| VT659 |
Hierarchical access combined with customer hierarchies not possible |
| VT660 |
Access sequence &1 inconsistent; target field &3 missing in access &2 |
| VT661 |
Hierarchical access combined with target field &3 not possible |
| VT662 |
Internal error &2 when saving access sequence &1 (see long text) |
| VT663 |
Do you want access to table field &1 with the initial direct value? |
| VT700 |
The use of partners is not allowed for output not dependent on partners |
| VT800 |
Group is used in sales documents, so the sold-to party cannot be changed |
| VT801 |
Group is used in deliveries, so the ship-to party cannot be changed |
| VT802 |
Group is used in billing, so the payer cannot be changed |
| VT803 |
Partner grp & doesn't contain any sold-to parties which can't be changed |
| VT804 |
Partner grp & doesn't contain any ship-to parties which can't be changed |
| VT805 |
Partner group & does not contain any payers which cannot be changed |
| VT806 |
The cost center is not defined |
| VT807 |
Maintain in Customizing SD: Functions: Partner Determination (TCODE VOPA) |
| VT808 |
Function module ZZ_SD_USEREXIT_PARTNER does not exist |
| VT809 |
Account assignment category & is invalid |
| VT810 |
Cost center &1 does not belong to company code &2 |
| VT811 |
The flag Extend Data must not be selected |
| VT812 |
Acc. assignment category &1 only allowed for valuated sales order stock |
| VT813 |
Account assignmt cat. &1 is not permitted for evaluated sales order stock |
| VT814 |
The pricing procedure for account determination must be empty. |
| VT815 |
No errors were found in Customizing. |
| VT816 |
Billing quantity 'F' must be used for item category billing relevance 'F' |
| VT817 |
For delivery-related billing, the field 'Quantity pos/neg' must be '+'. |
| VT818 |
If access sequence not available, scale type 'D' not possible. |
| VT819 |
A maximum of 99 condition supplements are permitted in pricing procedure. |
| VT820 |
Calculation type reference cond. type not equal to calc. type cond. type |
| VT821 |
Final Settlement and Correction flds must be maint. in rebate settlement |
| VT822 |
Relevant billing type for final settlement must be: Final settlement='A' |
| VT823 |
Relevant billing type for final settlement must be: Rel. to rebate ='X' |
| VT824 |
Canc. of billing type for final settlement must be: Rel. to rebate ='X' |
| VT825 |
Relevant billing type for correctin must be: Relevant to rebate ='B' |
| VT826 |
Relevant billing type for correction must be: Relevant to rebate ='X' |
| VT827 |
Canc. of billing type for correction must be: Relevant to rebate ='X' |
| VT828 |
Relevant billing type for partial settlement must be: Rel.to rebate = 'C' |
| VT829 |
Relevant billing type for partial settlement must be: Rel.to rebate = 'X' |
| VT830 |
Canc. of billing type for partial settlement must be: Rel.to rebate = 'X' |
| VT831 |
Relevant billing type for manual accrual must be: Rel. to rebate ='D' |
| VT832 |
Relevant billing type for manual accrual must be: Rel. to rebate ='X' |
| VT833 |
Canc.of bill.type for man.accr.sal.ord.type must be: Rel. to rebate ='X' |
| VT9T010 |
Object &1 is not available |
| VT9T011 |
Object &1 is available but object table has not been maintained |
| VT9T020 |
Schema &1 is not available |
| VT9T021 |
Not all the referenced events in the procedure are available |
| VT9T400 |
Position cursor on a line |
| VT9T500 |
Events could not be added |
| VT9T501 |
The system could not delete any events |
| VT9T502 |
You cannot delete the activity |
| VT9T510 |
Action cannot be delted (internal error) |
| VT9T511 |
Action cannot be entered (internal error) |
| VT9T512 |
Action sort sequence cannot be changed (internal error) |
| VT9T520 |
No locations can be displayed (internal error) |
| VT9T530 |
Time zone cannot be changed (internal error) |
| VT9T540 |
Time stamp cannot be changed (internal error) |
| VT9T550 |
Dialog data cannot be created (internal error) |
| VT9T551 |
Application data cannot be changed (internal error) |
| VT9T552 |
Text cannot be processed (internal error) |
| VT9T553 |
Inline fields cannot be updated (internal error) |
| VT9T800 |
The sort field must be unique |
| VTBAPI001 |
You can only distribute shipments for one recipient |
| VTBAPI002 |
No shipments found with the given selection criteria |
| VTBAPI003 |
Starting distribution of shipment &1 |
| VTBAPI004 |
Delivery & has not yet been distributed |
| VTBAPI005 |
Delivery & was distributed |
| VTBAPI010 |
Transportation planning point could not be determined (delivery missing) |
| VTBAPI011 |
Transportation planning point could not be determined (TART missing) |
| VTBAPI012 |
Transportation planning point could not be determined (unsuccessful) |
| VTBAPI013 |
Parameter 'headerdeadline-time_type' (logical time) is blank |
| VTBAPI014 |
Parameter 'headerdeadline-time_type' - & - is invalid |
| VTBAPI050 |
Shipment & could not be changed by the BAPI |
| VTBAPI099 |
Program error at &1 &2 &3 &4 |
| VTBAPI100 |
Conversion of ISO to SAP failed for shipment header & |
| VTBAPI101 |
Conversion from ISO to SAP failed for stage & |
| VTBAPI102 |
Conversion from ISO to SAP failed for address & |
| VTBAPI103 |
Conversion from ISO to SAP failed for HU header & |
| VTBAPI104 |
Conversion from ISO to SAP failed for HU item & |
| VTBAPI200 |
Action table and data table have different numbers of entries (&) |
| VTBAPI201 |
Actions for unit and ISO unit are different (&1, &2, &3) |
| VTBAPI202 |
Required input field & for shipment must not be changed |
| VTBAPI203 |
Field &1 of the address entry &2 cannot be changed using the BAPI |
| VTBAPI204 |
Field &1 of the HU header entry &2 cannot be changed using the BAPI |
| VTBAPI205 |
Field &1 of HU item entry &2 cannot be changed using the BAPI |
| VTBAPI206 |
Shipment cannot be added using the Change-BAPI (incorrect action field &) |
| VTBAPI207 |
Shipment has already been planned. No changes possible |
| VTBAPI208 |
Duplicate entries for the dates/times in the shipment header |
| VTBAPI209 |
Time category & is not permitted for shipment header dates/times |
| VTBAPI210 |
You can only set, not add, shipment header dates/times (line &) |
| VTBAPI211 |
Line & of the shipment header date/time actions is inconsistent |
| VTBAPI212 |
Time zone is empty in line & for the shipment header dates/times |
| VTBAPI213 |
Line & of the shipment item actions is inconsistent |
| VTBAPI214 |
Delivery &1 is not contained in shipment (&2) |
| VTBAPI215 |
Delivery & already assigned to the shipment |
| VTBAPI216 |
You cannot add stage dates/times, you can only set them (line &) |
| VTBAPI217 |
Time category & is not permitted for stage dates/times |
| VTBAPI218 |
Duplicate entries for dates/times of stages |
| VTBAPI219 |
Reference number of the stage dates/times larger than # stages (line &) |