SAP ABAP Message Class /SAPSLL/PRE_VDEC (Message Class for Long-Term Vendor Declarations)
Basic Data
Hierarchy
☛
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation
⤷
SLL-LEG (Application Component) Global Trade Services
⤷
/SAPSLL/LEGAL_PRE_VDEC (Package) Legal Services: Preference Handling - Vendor Declarations
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation⤷
SLL-LEG (Application Component) Global Trade Services⤷
/SAPSLL/LEGAL_PRE_VDEC (Package) Legal Services: Preference Handling - Vendor Declarations 
Attributes
| Message class |  |
/SAPSLL/PRE_VDEC |
| Short Description |  |
Message Class for Long-Term Vendor Declarations |
| Changed On |  |
20141107 |
| Last Changed At |  |
010144 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Error: &1; notify technical support | Space: object requires documentation | |
| 2 | 001 |
Could not select any vendor/material relationships | Space: object requires documentation | |
| 3 | 002 |
The maximum number of &1 plants has been exceeded | Space: object requires documentation | |
| 4 | 003 |
Could not establish RFC connection to system &1 | Space: object requires documentation | |
| 5 | 004 |
Logical system &1 has not been assigned to a group of logical systems | Space: object requires documentation | |
| 6 | 005 |
Unable to select any business partners | Space: object requires documentation | |
| 7 | 006 |
Specify either an internal or an external partner number | Space: object requires documentation | |
| 8 | 007 |
Enter either an internal or external product number | Space: object requires documentation | |
| 9 | 008 |
Internal partner number &1 does not exist in the system | Space: object requires documentation | |
| 10 | 009 |
Unable to select a product | Space: object requires documentation | |
| 11 | 010 |
Internal product number &1 does not exist in the system | Space: object requires documentation | |
| 12 | 011 |
Purchasing info record category &1 does not exist in the system | Space: object requires documentation | |
| 13 | 012 |
The maximum number of &1 countries has been exceeded | Space: object requires documentation | |
| 14 | 013 |
Data saved successfully | Space: object requires documentation | |
| 15 | 014 |
External partner number &1 does not exist in the system | Space: object requires documentation | |
| 16 | 015 |
Processing canceled by user | Space: object requires documentation | |
| 17 | 016 |
Data has been selected but not saved | Space: object requires documentation | |
| 18 | 017 |
No data has been selected in system &1 | Space: object requires documentation | |
| 19 | 018 |
Enter group for feeder system | Space: object requires documentation | |
| 20 | 019 |
Enter external partner number and group of logical systems | Space: object requires documentation | |
| 21 | 020 |
No active vendor/material relationships exist | Space: object requires documentation | |
| 22 | 021 |
Form does not exist | Space: object requires documentation | |
| 23 | 022 |
Text module does not exist in a suitable language | Space: object requires documentation | |
| 24 | 023 |
Specified validity period exceeds one year | Space: object requires documentation | |
| 25 | 024 |
No active agreements (legal regulations) could be determined | Space: object requires documentation | |
| 26 | 025 |
Error during mapping of product number | Space: object requires documentation | |
| 27 | 026 |
Forms created successfully | Space: object requires documentation | |
| 28 | 027 |
No preference zones are assigned to agreement &1 | Space: object requires documentation | |
| 29 | 028 |
System could not select any preference zones (import country groups) | Space: object requires documentation | |
| 30 | 029 |
System could not select any import countries | Space: object requires documentation | |
| 31 | 030 |
Select at least one line | Space: object requires documentation | |
| 32 | 031 |
Documents were printed successfully | Space: object requires documentation | |
| 33 | 032 |
Could not select any vendor-based long-term vendor declarations | Space: object requires documentation | |
| 34 | 033 |
No long-term vendor declaration exists | Space: object requires documentation | |
| 35 | 034 |
Field catalog could not be generated | Space: object requires documentation | |
| 36 | 035 |
Data for model grouping &1 read successfully | Space: object requires documentation | |
| 37 | 036 |
The following agreement has been selected: | Space: object requires documentation | |
| 38 | 037 |
The following prefence zones for the agreement have been selected: | Space: object requires documentation | |
| 39 | 038 |
The following countries have been selected for the country groups: | Space: object requires documentation | |
| 40 | 039 |
Supplier-material relationships selected | Space: object requires documentation | |
| 41 | 040 |
Eternal product references selected | Space: object requires documentation | |
| 42 | 041 |
No vendor declarations selected | Space: object requires documentation | |
| 43 | 042 |
Vendor declarations selected | Space: object requires documentation | |
| 44 | 043 |
Product texts selected | Space: object requires documentation | |
| 45 | 044 |
Partner addresses selected | Space: object requires documentation | |
| 46 | 045 |
Data selection: | Space: object requires documentation | |
| 47 | 046 |
Other data: | Space: object requires documentation | |
| 48 | 047 |
Analysis of vendor declaration to be requested/dunned | Space: object requires documentation | |
| 49 | 048 |
An LTVD has been requested/reminded for the following prods by partn. &1: | Space: object requires documentation | |
| 50 | 049 |
There is not yet a valid vendor declaration for product &1 | Space: object requires documentation | |
| 51 | 050 |
Product &1 has already been requested with dunning level &2 | Space: object requires documentation | |
| 52 | 051 |
Error occurred when writing data to database | Space: object requires documentation | |
| 53 | 052 |
Product &1 has already been requested with this dunning level | Space: object requires documentation | |
| 54 | 053 |
Data is not saved in simulation mode | Space: object requires documentation | |
| 55 | 054 |
Could not save data | Space: object requires documentation | |
| 56 | 055 |
Commodity codes selected | Space: object requires documentation | |
| 57 | 056 |
No address exists for administrative unit &1 | Space: object requires documentation | |
| 58 | 057 |
Administrative unit &1 is blocked by user &2 | Space: object requires documentation | |
| 59 | 058 |
Worklist (supplier/material relationship) blocked by user &1 | Space: object requires documentation | |
| 60 | 059 |
Description of at least one agreement not maintained in required language | Space: object requires documentation | |
| 61 | 060 |
The system could not select any vendor declarations | Space: object requires documentation | |
| 62 | 061 |
The system could not select any external product references | Space: object requires documentation | |
| 63 | 062 |
'Valid from' date is earlier than the 'valid to' date | Space: object requires documentation | |
| 64 | 063 |
Country of origin converted for agreement &1 and product &2 | Space: object requires documentation | |
| 65 | 064 |
Error occurred when writing data to database | Space: object requires documentation | |
| 66 | 065 |
You cannot extend the validity of a vendor declaration | Space: object requires documentation | |
| 67 | 066 |
External product number &1 does not exist in the system | Space: object requires documentation | |
| 68 | 067 |
No vendor declaration exists for product &1 from partner &2 | Space: object requires documentation | |
| 69 | 068 |
Vendor declaration &1 / &2 / &3 blocked by user &4 | Space: object requires documentation | |
| 70 | 069 |
Select one line only | Space: object requires documentation | |
| 71 | 070 |
Texts/descriptions of countries not fully maintained | Space: object requires documentation | |
| 72 | 071 |
No data maintained for model &1 (table &2) | Space: object requires documentation | |
| 73 | 072 |
External partner references selected | Space: object requires documentation | |
| 74 | 073 |
Agreement &3 already maintained for period &1 to &2 | Space: object requires documentation | |
| 75 | 074 |
Period &1 to &2 for agreement &3 conflicts with this entry | Space: object requires documentation | |
| 76 | 075 |
Data inconsistency; data cannot be saved | Space: object requires documentation | |
| 77 | 076 |
Enter an agreement | Space: object requires documentation | |
| 78 | 077 |
Enter a validity period | Space: object requires documentation | |
| 79 | 078 |
Enter a status | Space: object requires documentation | |
| 80 | 079 |
Select a valid line | Space: object requires documentation | |
| 81 | 080 |
No objects have been assigned to administrative unit &1 | Space: object requires documentation | |
| 82 | 081 |
Partner &1 and product &2 reference different feeder system groups | Space: object requires documentation | |
| 83 | 082 |
No feeder systems have been assigned to group of logical systems &1 | Space: object requires documentation | |
| 84 | 083 |
You cannot maintain an LTVD for administrative unit &1 and partner &2 | Space: object requires documentation | |
| 85 | 084 |
Enter a sequence number | Space: object requires documentation | |
| 86 | 085 |
Sequence number &1 has already been assigned | Space: object requires documentation | |
| 87 | 086 |
Tariff number &1 does not exist | Space: object requires documentation | |
| 88 | 087 |
Tariff number &1 has already been assigned | Space: object requires documentation | |
| 89 | 088 |
Enter a currency | Space: object requires documentation | |
| 90 | 089 |
This entry has already been flagged for deletion | Space: object requires documentation | |
| 91 | 090 |
Product mapping does not exist for feeder system &1 | Space: object requires documentation | |
| 92 | 091 |
No hierarchy levels have been defined for model &1 | Space: object requires documentation | |
| 93 | 092 |
The system was unable to determine procurement types for the products | Space: object requires documentation | |
| 94 | 093 |
The system was unable to determine a procurement type for product &1 | Space: object requires documentation | |
| 95 | 094 |
No vendor declarations with status "Requested" have been selected | Space: object requires documentation | |
| 96 | 095 |
Unable to select a partner address | Space: object requires documentation | |
| 97 | 096 |
No attributes defined for dunning level &1 in Customizing | Space: object requires documentation | |
| 98 | 097 |
The system cannot make a statement for the product | Space: object requires documentation | |
| 99 | 098 |
System was unable to determine an administrative unit | Space: object requires documentation | |
| 100 | 099 |
System was unable to determine a unique administrative unit | Space: object requires documentation | |
| 101 | 100 |
&1 | Space: object requires documentation | |
| 102 | 101 |
&1 - &2 | Space: object requires documentation | |
| 103 | 102 |
&1 - &2 ( &3 ) | Space: object requires documentation | |
| 104 | 103 |
&1 ( &2 ) | Space: object requires documentation | |
| 105 | 104 |
Enter logical system of the original object | Space: object requires documentation | |
| 106 | 105 |
Enter reference application | Space: object requires documentation | |
| 107 | 106 |
The system was unable to find billing docs for newly calculated products | Space: object requires documentation | |
| 108 | 107 |
No billing documents found for the current selection criteria | Space: object requires documentation | |
| 109 | 108 |
The product has not yet been checked for re-issue | Space: object requires documentation | |
| 110 | 109 |
The application log can only be saved during an update run | Space: object requires documentation | |
| 111 | 110 |
Aggreg. records whose legal regulation was not restricted will be deleted | Space: object requires documentation | |
| 112 | 111 |
Product text not found | Space: object requires documentation | |
| 113 | 112 |
No LTVD for customer's purposes was re-issued during this run | Space: object requires documentation | |
| 114 | 113 |
No LTVDs for customer's purposes needed to be re-issued | Space: object requires documentation | |
| 115 | 114 |
Customizing in view &1 is not suitable for aggregation | Space: object requires documentation | |
| 116 | 115 |
Enter a group of logical systems | Space: object requires documentation | |
| 117 | 116 |
Complete the product texts | The short text describes the object sufficiently | |
| 118 | 117 |
"Valid from" date is the same as or later than the "Valid to" date | The short text describes the object sufficiently | |
| 119 | 118 |
No change documents found for the products | Space: object requires documentation | |
| 120 | 119 |
Printing canceled by user | The short text describes the object sufficiently | |
| 121 | 120 |
No valuation segment exists for the selected products | Space: object requires documentation | |
| 122 | 121 |
Consistency of data changes will be checked | The short text describes the object sufficiently | |
| 123 | 122 |
Enter a key date from the validity period | The short text describes the object sufficiently | |
| 124 | 123 |
Status is not valid for selection | Space: object requires documentation | |
| 125 | 124 |
Complete the detailed data for agreement &1 | The short text describes the object sufficiently | |
| 126 | 125 |
Long-term vendor declarations are blocked by user &1 | The short text describes the object sufficiently | |
| 127 | 126 |
Enter a tariff number | The short text describes the object sufficiently | |
| 128 | 127 |
Data is inconsistent; check your entries | The short text describes the object sufficiently | |
| 129 | 128 |
Agreement &1 has not been defined for this area | The short text describes the object sufficiently | |
| 130 | 129 |
Currency key &1 is not available in the system | The short text describes the object sufficiently | |
| 131 | 130 |
Unknown activity: &1 | The short text describes the object sufficiently | |
| 132 | 131 |
Enter at least one valid agreement | The short text describes the object sufficiently | |
| 133 | 132 |
No changes were made | The short text describes the object sufficiently | |
| 134 | 133 |
Status &1 is not a valid value | The short text describes the object sufficiently | |
| 135 | 134 |
Combination of simulation run and log is not supported | The short text describes the object sufficiently | |
| 136 | 135 |
Transaction has been exited | The short text describes the object sufficiently | |
| 137 | 136 |
Enter the LTVD number | The short text describes the object sufficiently | |
| 138 | 137 |
Enter the year for the LTVD number | The short text describes the object sufficiently | |
| 139 | 138 |
Enter either LTVD number/year or validity and partner | The short text describes the object sufficiently | |
| 140 | 139 |
No logical system group can be determined for administrative unit &1 | Space: object requires documentation | |
| 141 | 140 |
No items were transferred to the interface | Space: object requires documentation | |
| 142 | 141 |
No relevant partner found - processing terminated | The short text describes the object sufficiently | |
| 143 | 142 |
Enter partner number or number of long-term vendor declaration/year | The short text describes the object sufficiently | |
| 144 | 143 |
Value &1 is not a valid value for the country of origin | The short text describes the object sufficiently | |
| 145 | 144 |
Do not specify a country if the LTVD status is negative | The short text describes the object sufficiently | |
| 146 | 145 |
Plant &1 in plant group &2 not mapped - further processing not possible | Space: object requires documentation | |
| 147 | 146 |
Plant &1 is not mapped - further processing not possible | Space: object requires documentation | |
| 148 | 147 |
Plant group &1 not mapped - further processing not possible | Space: object requires documentation | |
| 149 | 148 |
No data available for issuing customer LTVDs | The short text describes the object sufficiently | |
| 150 | 149 |
Deletion not allowed; LTVD already exists for product &1 | The short text describes the object sufficiently | |
| 151 | 150 |
**** Renewal of Long-Term Vendor Declarations **** | The short text describes the object sufficiently | |
| 152 | 151 |
Transaction canceled due to errors | The short text describes the object sufficiently | |
| 153 | 152 |
&1: see application log under ext. ident &2 | The short text describes the object sufficiently | |
| 154 | 153 |
Product &1, not possible: worklist with goods receipt exists | The short text describes the object sufficiently | |
| 155 | 154 |
Product &1 is correct (&2 -> &3) | The short text describes the object sufficiently | |
| 156 | 155 |
Product &1 is incorrect (Status &2, &3 > &4) | The short text describes the object sufficiently | |
| 157 | 156 |
Renewal for partner &1 | The short text describes the object sufficiently | |
| 158 | 157 |
Renewing the LTVDs for a total of &1 product(s) | The short text describes the object sufficiently | |
| 159 | 158 |
Extension data was not saved | The short text describes the object sufficiently | |
| 160 | 159 |
Product &1 is incorrect (invalid period from &2 to &3) | The short text describes the object sufficiently | |
| 161 | 160 |
Product &1 is not relevant (&2 = &3) | The short text describes the object sufficiently | |
| 162 | 161 |
Deletion of supplier/product &1/&2 not possible - see long text | Space: object requires documentation | |
| 163 | 162 |
Administrative unit &1, selection from &3, extension to &2 | The short text describes the object sufficiently | |
| 164 | 163 |
Renewing the LTVDs for partner &1 and &2 products | The short text describes the object sufficiently | |
| 165 | 164 |
Do you really want to archive active LTVDs? | Space: object requires documentation | |
| 166 | 165 |
Analyze partners who are not exclusively aggregration-relevant | The short text describes the object sufficiently | |
| 167 | 166 |
Aggregtn-rel. entries being generated for partner &1 for follwg products | The short text describes the object sufficiently | |
| 168 | 167 |
&1 entries were selected | The short text describes the object sufficiently | |
| 169 | 168 |
No entries were selected | The short text describes the object sufficiently | |
| 170 | 169 |
Start date &1 is earlier than today's date &2 | Space: object requires documentation | |
| 171 | 170 |
Processing was completed successfully | The short text describes the object sufficiently | |
| 172 | 171 |
No data could be determined for your selection criteria | The short text describes the object sufficiently | |
| 173 | 172 |
Plant &1 or plant group &2 not qualified | Space: object requires documentation | |
| 174 | 173 |
Entry created for product &1, plant &2, indicator &3 | The short text describes the object sufficiently | |
| 175 | 174 |
Entry created for product &1, plant group &2, indicator &3 | The short text describes the object sufficiently | |
| 176 | 175 |
Entry created for product &1, plant &2, plant group &3, indicator &4 | The short text describes the object sufficiently | |
| 177 | 176 |
&1: Document was transferred | The short text describes the object sufficiently | |
| 178 | 177 |
&1: Document was not transferred - see GTS log | The short text describes the object sufficiently | |
| 179 | 178 |
Partner &1 has been defined as not relevant for maintenance of LTVDs | Space: object requires documentation | |
| 180 | 179 |
The print preview is only possible for one vendor at a time | The short text describes the object sufficiently | |
| 181 | 180 |
Print preview not possible - XI communication took place | The short text describes the object sufficiently | |
| 182 | 181 |
Print preview not possible - mail dispatch communication took place | The short text describes the object sufficiently | |
| 183 | 182 |
Requesting administrative unit: &1 / &2 | The short text describes the object sufficiently | |
| 184 | 183 |
Reminding administrative unit: &1 / &2 | The short text describes the object sufficiently | |
| 185 | 184 |
Vendor/product combinations from worklist for LTVDs: | The short text describes the object sufficiently | |
| 186 | 185 |
You must enter a name if you want to save the log | The short text describes the object sufficiently | |
| 187 | 186 |
Entry created for plant &1, flag &2 - &3 | The short text describes the object sufficiently | |
| 188 | 187 |
Entry created for plant group &1, flag &2 - &3 | The short text describes the object sufficiently | |
| 189 | 188 |
Entry created for plant group &1, plant &2, flag &3 - &4 | The short text describes the object sufficiently | |
| 190 | 189 |
Administrative unit &1 is not assigned to jurisdiction &2 | The short text describes the object sufficiently | |
| 191 | 190 |
Preference status &1 is not a valid value for jurisdiction &2 | The short text describes the object sufficiently | |
| 192 | 191 |
No data selected in buffer for processing | The short text describes the object sufficiently | |
| 193 | 192 |
The data to process under &1 is not available in the buffer | The short text describes the object sufficiently | |
| 194 | 193 |
Inconsistent data: restore the deleted entries | The short text describes the object sufficiently | |
| 195 | 194 |
Status "Archivable" set for document no. &1/year &2 | The short text describes the object sufficiently | |
| 196 | 195 |
&1 is the key date for selection for archiving | The short text describes the object sufficiently | |
| 197 | 196 |
No archived data was selected | The short text describes the object sufficiently | |
| 198 | 197 |
Vendor/material combinations for LTVDs from the database table: | The short text describes the object sufficiently | |
| 199 | 198 |
Selected vendor/material combinations from the database: | The short text describes the object sufficiently | |
| 200 | 199 |
Vendor &1 - &2 was excluded from further processing | Space: object requires documentation | |
| 201 | 200 |
Vendor/product combinations based on available LTVDs: | The short text describes the object sufficiently | |
| 202 | 201 |
LTVD requested from vendor &1 for the following products by &2 | The short text describes the object sufficiently | |
| 203 | 202 |
Reminder will be sent to vendor &1 for the following products as of &2 | The short text describes the object sufficiently | |
| 204 | 203 |
The default data is displayed instead of the maintained data | Space: object requires documentation | |
| 205 | 204 |
Specify the same country of origin &2 for product &1 | The short text describes the object sufficiently | |
| 206 | 205 |
No valid LTVD for product &1, vendor &2 | The short text describes the object sufficiently | |
| 207 | 206 |
Specify a cumulation flag for agreement &1 | The short text describes the object sufficiently | |
| 208 | 207 |
Agreement &1 does not support cumulation flags | The short text describes the object sufficiently | |
| 209 | 208 |
Cumulation flag &1 is not a valid value | The short text describes the object sufficiently | |
| 210 | 209 |
Invalid value for negative status of vendor declaration | The short text describes the object sufficiently | |
| 211 | 210 |
Invalid value for positive status of vendor declaration | The short text describes the object sufficiently | |
| 212 | 211 |
No data available to request vendor-based LTVDs | The short text describes the object sufficiently | |
| 213 | 212 |
LTVD for customer's purpose &1/&2 for the partner does not exist | The short text describes the object sufficiently | |
| 214 | 213 |
LTVD for customer's purpose number &1/&2 does not exist | The short text describes the object sufficiently | |
| 215 | 214 |
XI output not possible | The short text describes the object sufficiently | |
| 216 | 215 |
Printing in simulation mode is only possible for one vendor at a time | The short text describes the object sufficiently | |
| 217 | 216 |
The requested function is only possible for a single line | The short text describes the object sufficiently | |
| 218 | 217 |
No data available for requesting LTVDs without document reference | Space: object requires documentation | |
| 219 | 218 |
Updated for plant &1, indicators &2 - &3 | The short text describes the object sufficiently | |
| 220 | 219 |
Updated for plant group &1, indicators &2 - &3 | The short text describes the object sufficiently | |
| 221 | 220 |
Updated for plant group &1, plant &2, indicators &3 - &4 | The short text describes the object sufficiently | |
| 222 | 221 |
Deleted for plant &1, indicators &2 - &3 | The short text describes the object sufficiently | |
| 223 | 222 |
Deleted for plant group &1, indicators &2 - &3 | The short text describes the object sufficiently | |
| 224 | 223 |
Deleted for plant group &1, plant &2, indicators &3 - &4 | The short text describes the object sufficiently | |
| 225 | 224 |
The follow-on function is not possible | Space: object requires documentation | |
| 226 | 225 |
No data available for sending reminders for vendor-based LTVDs | The short text describes the object sufficiently | |
| 227 | 226 |
No data available to request vendor-based LTVDs | Space: object requires documentation | |
| 228 | 227 |
Combination of initial request and request w/o doc. ref. not allowed | The short text describes the object sufficiently | |
| 229 | 228 |
Requesting w/o document reference in background not allowed | The short text describes the object sufficiently | |
| 230 | 229 |
Request w/o document reference is not limited to partner and product | Space: object requires documentation | |
| 231 | 230 |
The function is only possible for one business partner | The short text describes the object sufficiently | |
| 232 | 231 |
Vendor declarations are not relevant for products produced in-house | The short text describes the object sufficiently | |
| 233 | 232 |
You can only request without a document reference for a single partner | The short text describes the object sufficiently | |
| 234 | 233 |
The follow-on function is not uniquely defined | Space: object requires documentation | |
| 235 | 234 |
Repeat printout is not possible for any of the selected LTVDs | Space: object requires documentation | |
| 236 | 235 |
Repeat printout is not possible for all of the selected LTVDs | Space: object requires documentation | |
| 237 | 236 |
Unknown output device | Space: object requires documentation | |
| 238 | 237 |
The status of the selected LTVDs does not allow initial request | Space: object requires documentation | |
| 239 | 238 |
Could not determine an administrative unit: logical system &1, plant &2 | Space: object requires documentation | |
| 240 | 239 |
Requested function not possible in current LTVD status | Space: object requires documentation | |
| 241 | 240 |
You can only aggregate aggregation-relevant vendor declarations | The short text describes the object sufficiently | |
| 242 | 241 |
The status of the selected LTVDs only allows initial request | Space: object requires documentation | |
| 243 | 242 |
Initial request not possible for all selected LTVDs | The short text describes the object sufficiently | |
| 244 | 243 |
The requested function is only possible for one supplier at a time | The short text describes the object sufficiently | |
| 245 | 244 |
Function will be executed for all the selected partner's products | The short text describes the object sufficiently | |
| 246 | 245 |
Selection criterion "Status of LTVD" missing | Space: object requires documentation | |
| 247 | 246 |
No data available for annual LTVD request run | The short text describes the object sufficiently | |
| 248 | 247 |
Print attempt failed | The short text describes the object sufficiently | |
| 249 | 248 |
No agreements defined in the system | The short text describes the object sufficiently | |
| 250 | 249 |
No agreement defined for country &1 | The short text describes the object sufficiently | |
| 251 | 250 |
Supplier &1 &2 | The short text describes the object sufficiently | |
| 252 | 251 |
Initial request based on the following LTVDs is not possible | Space: object requires documentation | |
| 253 | 252 |
Subsequent request of LTVD not possible | Space: object requires documentation | |
| 254 | 253 |
Maintenance based on the selected LTVDs is not possible | The short text describes the object sufficiently | |
| 255 | 254 |
No unique jurisdiction determined for administrative unit &1 | The short text describes the object sufficiently | |
| 256 | 255 |
No jurisdiction determined for administrative unit &1 | The short text describes the object sufficiently | |
| 257 | 256 |
Agreement &1 is used in different rule set types | The short text describes the object sufficiently | |
| 258 | 257 |
Different schemas &1 and &2 defined for agreement &3 | The short text describes the object sufficiently | |
| 259 | 258 |
No mapping defined for agreement &1 and indicator &2 | The short text describes the object sufficiently | |
| 260 | 259 |
Mapping for agreement &1 and indicator &2 not unique | Space: object requires documentation | |
| 261 | 260 |
No preference indicators defined for agreement &1 | The short text describes the object sufficiently | |
| 262 | 261 |
Preference indicator &1 is not a valid (internal) value | The short text describes the object sufficiently | |
| 263 | 262 |
Preference indicator &1 in schema &2 is not a valid value | The short text describes the object sufficiently | |
| 264 | 263 |
Mapping of agreement-specific indicators is not unique | Space: object requires documentation | |
| 265 | 264 |
(External) preference indicator for agreement &1 cannot be determined | The short text describes the object sufficiently | |
| 266 | 265 |
Print simulation not possible for request via e-mail | The short text describes the object sufficiently | |
| 267 | 266 |
Maximum reminder level &1 has been reached | The short text describes the object sufficiently | |
| 268 | 267 |
Invalid preference indicator &1 for agreement &2 was reset | The short text describes the object sufficiently | |
| 269 | 268 |
End date &1 lies before current date &2 | The short text describes the object sufficiently | |
| 270 | 269 |
Enter the LTVD number/year or validity | The short text describes the object sufficiently | |
| 271 | 270 |
LTVDs for partner &1 should be maintained through data exchange | The short text describes the object sufficiently | |
| 272 | 271 |
LTVDs for partner &1 should be maintained through printed documents | The short text describes the object sufficiently | |
| 273 | 272 |
LTVDs for partner &1 should be maintained by the vendor | The short text describes the object sufficiently | |
| 274 | 273 |
LTVDs for partner &1 should not be maintained through printed documents | The short text describes the object sufficiently | |
| 275 | 274 |
For plant &1, indicator &2 - &3 unchanged | The short text describes the object sufficiently | |
| 276 | 275 |
Year is required in selection by LTVD number | The short text describes the object sufficiently | |
| 277 | 276 |
For plant group &1, indicator &2 - &3 unchanged | The short text describes the object sufficiently | |
| 278 | 277 |
For plant group &1, plant &2, indicator &3 - &4 unchanged | The short text describes the object sufficiently | |
| 279 | 278 |
Validity is earlier than the today's date &1 | The short text describes the object sufficiently | |
| 280 | 279 |
Request can be made only for the current year or next year | The short text describes the object sufficiently | |
| 281 | 280 |
&1 - &2 ( &3 ) deleted | The short text describes the object sufficiently | |
| 282 | 281 |
No vendor declarations exist under &1 / &2 | The short text describes the object sufficiently | |
| 283 | 282 |
No vendor declarations exist for partner &3 under &1 / &2 | The short text describes the object sufficiently | |
| 284 | 283 |
No vendor declarations exist for partner &1 | The short text describes the object sufficiently | |
| 285 | 284 |
Administrative unit &1, partner &2 | The short text describes the object sufficiently | |
| 286 | 285 |
Vendor declarations &1 / &2 | The short text describes the object sufficiently | |
| 287 | 286 |
The step for transfer has not been reached yet | The short text describes the object sufficiently | |
| 288 | 287 |
No data available to transfer | The short text describes the object sufficiently | |
| 289 | 288 |
No data available for the GTS system | The short text describes the object sufficiently | |
| 290 | 289 |
Agreement &1 is unknown in this context in the GTS system | The short text describes the object sufficiently | |
| 291 | 290 |
Product &1 is unknown in this context in the GTS system | The short text describes the object sufficiently | |
| 292 | 291 |
Data transferred successfully from the GTS system | The short text describes the object sufficiently | |
| 293 | 292 |
The data has already been transferred from the GTS system | The short text describes the object sufficiently | |
| 294 | 293 |
&1 relevant products selected for transfer | The short text describes the object sufficiently | |
| 295 | 294 |
Invalid indicator &1 for agreement &2 | The short text describes the object sufficiently | |
| 296 | 295 |
Invalid internal indicator &1 for indicator &2 of agreement &3 | The short text describes the object sufficiently | |
| 297 | 296 |
Data was not transferred from GTS system | The short text describes the object sufficiently | |
| 298 | 297 |
Data for product &1 was checked in GTS system | The short text describes the object sufficiently | |
| 299 | 298 |
Validity for product &1 is not uniform under agreement | The short text describes the object sufficiently | |
| 300 | 299 |
Not all LTVDs have been maintained completely | The short text describes the object sufficiently | |
| 301 | 300 |
*------------ BP Vendor Declaration -----------------------------------* | The short text describes the object sufficiently | |
| 302 | 301 |
SMTP service is not active | Space: object requires documentation | |
| 303 | 302 |
The Smart Form is not formatted correctly | Space: object requires documentation | |
| 304 | 303 |
Could not determine form module for &1 | Space: object requires documentation | |
| 305 | 304 |
Error during reading of business partner &1 | Space: object requires documentation | |
| 306 | 305 |
Supplier address not maintained | Space: object requires documentation | |
| 307 | 306 |
Business partner &1 was assigned an incorrect role | Space: object requires documentation | |
| 308 | 307 |
No responsible employees exist for partner &1 | Space: object requires documentation | |
| 309 | 308 |
Business partner &1 has more than one employee responsible | Space: object requires documentation | |
| 310 | 309 |
No partner address exists for business partner &1 | Space: object requires documentation | |
| 311 | 310 |
Business partner &1 is not in the system | Space: object requires documentation | |
| 312 | 311 |
User name &1 is not in the system | Space: object requires documentation | |
| 313 | 312 |
No data is available in the worklist | The short text describes the object sufficiently | |
| 314 | 313 |
Entry was not made in field &1 | The short text describes the object sufficiently | |
| 315 | 314 |
Host &1 is already maintained | The short text describes the object sufficiently | |
| 316 | 315 |
Host name must not exceed 255 characters | The short text describes the object sufficiently | |
| 317 | 316 |
Sender &1 | The short text describes the object sufficiently | |
| 318 | 317 |
Employee responsible &1 is not available in the required role | The short text describes the object sufficiently | |
| 319 | 318 |
Error while updating table HTTPURLLOC | The short text describes the object sufficiently | |
| 320 | 319 |
The system was unable to send any form to business partner &1 | The short text describes the object sufficiently | |
| 321 | 320 |
Level of detail does not exist | The short text describes the object sufficiently | |
| 322 | 321 |
Form language option does not exist | Space: object requires documentation | |
| 323 | 322 |
The "FULL QUALIFIED SERVER NAME" is not maintained | Space: object requires documentation | |
| 324 | 323 |
No BSP application name has been maintained in table HTTPURLLOC | The short text describes the object sufficiently | |
| 325 | 324 |
Maintain the e-mail address of user &1 in the user master record | The short text describes the object sufficiently | |
| 326 | 325 |
The e-mail address of the employee responsible &1 is not specified | The short text describes the object sufficiently | |
| 327 | 326 |
Business partner &1 has not maintained an employee responsible | The short text describes the object sufficiently | |
| 328 | 327 |
Application &1 has been entered in table HTTPURLLOC more than once | Space: object requires documentation | |
| 329 | 328 |
Host name must not contain the special character '*?' | The short text describes the object sufficiently | |
| 330 | 329 |
E-mail to &1 with LTVD no. &2/&3 successfully transferred to send request | Space: object requires documentation | |
| 331 | 330 |
Define the e-mail text module in Customizing | The short text describes the object sufficiently | |
| 332 | 331 |
The system does not support communication type "e-mail" | The short text describes the object sufficiently | |
| 333 | 332 |
Communication type "e-mail" is not defined | The short text describes the object sufficiently | |
| 334 | 333 |
HTTPS service is not active | Space: object requires documentation | |
| 335 | 334 |
Action cancelled by user | The short text describes the object sufficiently | |
| 336 | 335 |
System cannot determine a free key for table HTTPURLLOC | Space: object requires documentation | |
| 337 | 336 |
HTTP service is not active | The short text describes the object sufficiently | |
| 338 | 337 |
Enter the e-mail Smart Form form in Customizing | The short text describes the object sufficiently | |
| 339 | 338 |
Administrative unit &1 has not been assigned a form for service &2 | The short text describes the object sufficiently | |
| 340 | 339 |
Administration unit &1 / partner &2 is blocked by user &3 | The short text describes the object sufficiently | |
| 341 | 340 |
Business partner &1 invalid | The short text describes the object sufficiently | |
| 342 | 341 |
URL for Web Dynpro application not found | The short text describes the object sufficiently | |
| 343 | 342 |
Plant group &1: &2 -> &3 | The short text describes the object sufficiently | |
| 344 | 343 |
Plant &1 (&2): &3 -> &4 | The short text describes the object sufficiently | |
| 345 | 344 |
Finalize requested LTVDs with aggregation relevance on &1 &2 | The short text describes the object sufficiently | |
| 346 | 345 |
LTVDs being modified for partner &1 and the following products | The short text describes the object sufficiently | |
| 347 | 349 |
Selection date &1 must lie before the extension date, &2 | The short text describes the object sufficiently | |
| 348 | 350 |
Product &1, not possible: no positive LTVD available | The short text describes the object sufficiently | |
| 349 | 351 |
Product &1, not possible: LTVD exists with validity to &2 | The short text describes the object sufficiently | |
| 350 | 352 |
Product &1, not possible: requested LTVD with aggregation relevance | The short text describes the object sufficiently | |
| 351 | 353 |
Product &1, not possible: More than one year (&2 -> &3) | The short text describes the object sufficiently | |
| 352 | 354 |
Administrative unit &1, extension to &2 | The short text describes the object sufficiently | |
| 353 | 355 |
Administrative unit &1 / time period starting at &2 | The short text describes the object sufficiently | |
| 354 | 356 |
No data exists in worklist starting at &1 | The short text describes the object sufficiently | |
| 355 | 357 |
Product &1 not possible: LTVD is not aggregation relevant | The short text describes the object sufficiently | |
| 356 | 358 |
Product &1 not possible: requested LTVD valid until &2 | The short text describes the object sufficiently | |
| 357 | 500 |
>>>>>>>>>>>>>>>>>> Electronic Vendor Declaration <<<<<<<<<<<<<<<<<<<<<<< | The short text describes the object sufficiently | |
| 358 | 501 |
Error while mapping administrative unit &1 | The short text describes the object sufficiently | |
| 359 | 502 |
Incomplete or incorrect Customizing for administrative unit | The short text describes the object sufficiently | |
| 360 | 503 |
Error while determining the numbering scheme | The short text describes the object sufficiently | |
| 361 | 504 |
Group determined; no mapping of partner ID or product ID | The short text describes the object sufficiently | |
| 362 | 505 |
Error while mapping partner &1 | The short text describes the object sufficiently | |
| 363 | 506 |
Error while mapping product &1 | The short text describes the object sufficiently | |
| 364 | 507 |
Error while mapping ISO country code &1 | The short text describes the object sufficiently | |
| 365 | 508 |
Administrative unit &1, ID in partner system &2 | The short text describes the object sufficiently | |
| 366 | 509 |
Partner &1, ID in partner system &2 | The short text describes the object sufficiently | |
| 367 | 510 |
Product &1, ID in partner system &2 | The short text describes the object sufficiently | |
| 368 | 511 |
Numbering scheme &1 | The short text describes the object sufficiently | |
| 369 | 512 |
Vendor declaration request &1 &2 | The short text describes the object sufficiently | |
| 370 | 513 |
Vendor declaration &1 &2 for request &3 &4 | The short text describes the object sufficiently | |
| 371 | 514 |
XML data cannot be processed; see application log &1 | The short text describes the object sufficiently | |
| 372 | 515 |
XML message does not contain any product data | The short text describes the object sufficiently | |
| 373 | 600 |
>>>>>>>>>>>>>>>Vendor Declaration for Customer's Purpose <<<<<<<<<<<<<<< | The short text describes the object sufficiently | |
| 374 | 601 |
Processing complete because no relevant product data exists | Space: object requires documentation | |
| 375 | 602 |
No plants have been assigned to administrative unit &1 | The short text describes the object sufficiently | |
| 376 | 603 |
No agreement has been activated for administrative unit &1 | Space: object requires documentation | |
| 377 | 604 |
No determination procedure has been assigned for preference processing | The short text describes the object sufficiently | |
| 378 | 605 |
No export partner group assigned to determination procedure &1 | The short text describes the object sufficiently | |
| 379 | 606 |
No partner function has been activated for preference processing | The short text describes the object sufficiently | |
| 380 | 607 |
Internal error while processing external master data IDs for sorting | The short text describes the object sufficiently | |
| 381 | 608 |
Internal error while generating vendor declaration lines | The short text describes the object sufficiently | |
| 382 | 609 |
Internal error while generating vendor declaration items | The short text describes the object sufficiently | |
| 383 | 610 |
Internal error while generating vendor declaration subitems | The short text describes the object sufficiently | |
| 384 | 611 |
&1 already contained in upstream VDfCP &2 &3 | The short text describes the object sufficiently | |
| 385 | 612 |
&1 already contained in downstream LTvDE &2 &3 | The short text describes the object sufficiently | |
| 386 | 613 |
Plant &1 (&2) has not been assigned to a legal unit yet | The short text describes the object sufficiently | |
| 387 | 614 |
No currency has been assigned to administrative unit &1 | The short text describes the object sufficiently | |
| 388 | 615 |
Administrative unit &1: verify the organizational structure | The short text describes the object sufficiently | |
| 389 | 616 |
Multiple preference zones assigned to administrative unit &1 | The short text describes the object sufficiently | |
| 390 | 617 |
Plants in plant group &1 are located in different preference zones | The short text describes the object sufficiently | |
| 391 | 618 |
Plants are located in different preference zones | The short text describes the object sufficiently | |
| 392 | 619 |
Administrative unit &1 assigned to multiple logical system groups | Space: object requires documentation | |
| 393 | 620 |
Group of logical systems &1 not assigned to administrative unit &2 | The short text describes the object sufficiently | |
| 394 | 621 |
C-LTVD &1 has multiple stored documents | The short text describes the object sufficiently | |
| 395 | 622 |
LTVD for customers' purposes: &1 | The short text describes the object sufficiently | |
| 396 | 627 |
Form control not maintained completely for administrative unit &1 | Space: object requires documentation | |
| 397 | 629 |
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Aggregation <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< | The short text describes the object sufficiently | |
| 398 | 630 |
Processing complete because no relevant product data exists | Space: object requires documentation | |
| 399 | 631 |
Processing complete because no relevant LTVDs exist | The short text describes the object sufficiently | |
| 400 | 632 |
Internal error while processing master data IDs for lock entries | The short text describes the object sufficiently | |
| 401 | 633 |
Products in parallel processing were excluded | The short text describes the object sufficiently | |
| 402 | 634 |
User &1 is editing product &2 | The short text describes the object sufficiently | |
| 403 | 635 |
Product &1: Check the agreement segment for LTVD vendor &2 | The short text describes the object sufficiently | |
| 404 | 636 |
Product &1: No preference available; no valid LTVD | The short text describes the object sufficiently | |
| 405 | 637 |
Product &1: Error accessing master data | The short text describes the object sufficiently | |
| 406 | 638 |
Product &1: Error during date processing | The short text describes the object sufficiently | |
| 407 | 639 |
Product &1: Invalid preference type &2 | The short text describes the object sufficiently | |
| 408 | 640 |
Product &1: LTVD maintenance missing for agreement &2 | The short text describes the object sufficiently | |
| 409 | 641 |
Product &1: LTVD vendor segment missing (GUID_PREVD &2) | The short text describes the object sufficiently | |
| 410 | 642 |
Product &1: No change of preference status | The short text describes the object sufficiently | |
| 411 | 643 |
Product &1: Different preference methods for EU jurisdiction | The short text describes the object sufficiently | |
| 412 | 644 |
Product &1: Preference method &2 not allowed for EU jurisdiction | The short text describes the object sufficiently | |
| 413 | 645 |
Product &1: Too many preference methods for NAFTA jurisdiction | The short text describes the object sufficiently | |
| 414 | 646 |
Product &1: Procurement indicator missing for plant group &2 | The short text describes the object sufficiently | |
| 415 | 647 |
Product &1: Procurement indicator missing for plant &2 (&3) | The short text describes the object sufficiently | |
| 416 | 648 |
Product &1: GUID_MODEL &2 is not allowed for aggregation | The short text describes the object sufficiently | |
| 417 | 649 |
Please notify your administrator: check lock handler resources | The short text describes the object sufficiently | |
| 418 | 650 |
Lock request for product &2 exceeds lock handler resources | The short text describes the object sufficiently | |
| 419 | 651 |
No aggregation because there are no LTVDs for key date &1 | The short text describes the object sufficiently | |
| 420 | 652 |
No aggregation because the LTVDs are no longer valid | The short text describes the object sufficiently | |
| 421 | 660 |
Procurement indicator missing for all products to process | The short text describes the object sufficiently | |
| 422 | 661 |
Inconsistent product master data in all products to be processed | The short text describes the object sufficiently | |
| 423 | 662 |
Status &1 of document &2 is not relevant for transfer to feeder system | The short text describes the object sufficiently | |
| 424 | 663 |
Incorrect assignment of numbering scheme to preference agreement rule set | The short text describes the object sufficiently | |
| 425 | 699 |
Preference status not changed for the processed products | The short text describes the object sufficiently | |
| 426 | 700 |
>>>>>>>>>>>> Log for Vendor Declaration for Customer's Purpose <<<<<<<<<< | The short text describes the object sufficiently | |
| 427 | 701 |
Vendor declaration for customer's purpose &1 &2 | The short text describes the object sufficiently | |
| 428 | 702 |
Partner &1 &2 | The short text describes the object sufficiently | |
| 429 | 703 |
Date of issue &1 | The short text describes the object sufficiently | |
| 430 | 704 |
Validity period froM &1 to &2 | The short text describes the object sufficiently | |
| 431 | 705 |
Analysis period for preference statement from &1 to &2 | The short text describes the object sufficiently | |
| 432 | 706 |
Worklist selection period to &1 (inclusive) | The short text describes the object sufficiently | |
| 433 | 707 |
Group of logical systems for master data identication &1 | The short text describes the object sufficiently | |
| 434 | 708 |
Numbering scheme &1 &2 | The short text describes the object sufficiently | |
| 435 | 709 |
Organizational structure | The short text describes the object sufficiently | |
| 436 | 710 |
Administrative unit &1 &2 | The short text describes the object sufficiently | |
| 437 | 711 |
Plant group &1, plant &2 (&3) | The short text describes the object sufficiently | |
| 438 | 712 |
Plant group &1 | The short text describes the object sufficiently | |
| 439 | 713 |
Plant &1 (&2) | The short text describes the object sufficiently | |
| 440 | 714 |
Product list | The short text describes the object sufficiently | |
| 441 | 715 |
Product &1 &2 | The short text describes the object sufficiently | |
| 442 | 716 |
Procurement indicator | The short text describes the object sufficiently | |
| 443 | 717 |
Plant group &1, plant &2 (&3): &4 | The short text describes the object sufficiently | |
| 444 | 718 |
Plant group &1: &2 | The short text describes the object sufficiently | |
| 445 | 719 |
Plant &1 (&2): &3 | The short text describes the object sufficiently | |
| 446 | 720 |
Tariff number &1 &2 | The short text describes the object sufficiently | |
| 447 | 721 |
The classification during the validity period is ambiguous | The short text describes the object sufficiently | |
| 448 | 722 |
The validity period has not been classified yet | The short text describes the object sufficiently | |
| 449 | 723 |
No data available for the preferential country of origin | The short text describes the object sufficiently | |
| 450 | 724 |
Preferential country of origin &1 | The short text describes the object sufficiently | |
| 451 | 725 |
The country of origin is ambiguous in the analysis period | The short text describes the object sufficiently | |
| 452 | 726 |
Preference agreement &1 &2 | The short text describes the object sufficiently | |
| 453 | 727 |
Determined preferential indicator: &1 | The short text describes the object sufficiently | |
| 454 | 728 |
Comparison data: | The short text describes the object sufficiently | |
| 455 | 729 |
"Worst case" preference status determined for customs product master | The short text describes the object sufficiently | |
| 456 | 730 |
No data available for analysis period of preference statement | The short text describes the object sufficiently | |
| 457 | 731 |
Preferential status based on statement from &1 | The short text describes the object sufficiently | |
| 458 | 732 |
Preference method &1 | The short text describes the object sufficiently | |
| 459 | 733 |
Relevant preference status in customs product master &1 | The short text describes the object sufficiently | |
| 460 | 734 |
Threshold value &1 &2 | The short text describes the object sufficiently | |
| 461 | 735 |
Share of origin &1 &2 | The short text describes the object sufficiently | |
| 462 | 736 |
Non-origin share &1 &2 | The short text describes the object sufficiently | |
| 463 | 737 |
RVC benefit &1 &2 | The short text describes the object sufficiently | |
| 464 | 738 |
Business transaction-related comparison data | The short text describes the object sufficiently | |
| 465 | 739 |
Best standardized price in selection period | The short text describes the object sufficiently | |
| 466 | 740 |
&1 &2 item &3 (&4) | The short text describes the object sufficiently | |
| 467 | 741 |
Transaction date &1 | The short text describes the object sufficiently | |
| 468 | 742 |
Transfer date &1 | The short text describes the object sufficiently | |
| 469 | 743 |
No transaction-related data is available for price comparison | The short text describes the object sufficiently | |
| 470 | 744 |
Standardized comparison value from document item &1 &2 | The short text describes the object sufficiently | |
| 471 | 745 |
Individual check of transactions in validity period | The short text describes the object sufficiently | |
| 472 | 746 |
Re-issued with status status &1 | The short text describes the object sufficiently | |
| 473 | 747 |
Currency &1 &2 | The short text describes the object sufficiently | |
| 474 | 748 |
Aggregation run from &1 | The short text describes the object sufficiently | |
| 475 | 749 |
Key date for selecting vendor declarations: &1 | The short text describes the object sufficiently | |
| 476 | 750 |
Manually set status &1 - System results overridden | The short text describes the object sufficiently | |
| 477 | 751 |
Preferential status determined from in-house production: &1 | The short text describes the object sufficiently | |
| 478 | 752 |
Preference status determined from vendor declarations: &1 | The short text describes the object sufficiently | |
| 479 | 753 |
Vendors | The short text describes the object sufficiently | |
| 480 | 754 |
Vendor declaration &1 &2 | The short text describes the object sufficiently | |
| 481 | 755 |
Preferential status: &1 | The short text describes the object sufficiently | |
| 482 | 756 |
No data available from preference determ. for products produced in-house | The short text describes the object sufficiently | |
| 483 | 757 |
Select at least one type of preference statement | The short text describes the object sufficiently | |
| 484 | 758 |
Vendor declaration &1/&2 for partner &3 was not selected | The short text describes the object sufficiently | |
| 485 | 759 |
Preference statement was adopted from feeder system | The short text describes the object sufficiently | |
| 486 | 760 |
Not relevant for re-issue | The short text describes the object sufficiently | |
| 487 | 761 |
Analysis of preference statement in the past: &1 days | The short text describes the object sufficiently | |
| 488 | 762 |
No preference statement exists in timeframe of issue | The short text describes the object sufficiently | |
| 489 | 800 |
>>>>>>>>>>>>>>> Log for Document Preference Determination <<<<<<<<<<<<<< | The short text describes the object sufficiently | |
| 490 | 801 |
Configuration of product &1 &2 | The short text describes the object sufficiently | |
| 491 | 802 |
Country of departure &1 | The short text describes the object sufficiently | |
| 492 | 803 |
Country of destination &3 determined based on partner &1 (&2) | The short text describes the object sufficiently | |
| 493 | 804 |
Document &1 &2 | The short text describes the object sufficiently | |
| 494 | 805 |
Item &1 | The short text describes the object sufficiently | |
| 495 | 806 |
Preference determined based on order &1 and KMAT item &2 | The short text describes the object sufficiently | |
| 496 | 807 |
Agreement &1 is not active for &2 &3 | The short text describes the object sufficiently | |
| 497 | 808 |
Preference statement for product is not price-dependent | The short text describes the object sufficiently | |
| 498 | 809 |
Only one agreement may be flagged as used (item &1) | The short text describes the object sufficiently | |
| 499 | 810 |
&1 is not a valid value for the type of rule set (item &2) | The short text describes the object sufficiently | |
| 500 | 811 |
Agreement &1 was not activated for the EU (item &2) | The short text describes the object sufficiently | |
| 501 | 812 |
Agreement &1 was not activated for NAFTA (item &2) | The short text describes the object sufficiently | |
| 502 | 813 |
&1 is not a valid value for the EU preference method (item &2) | The short text describes the object sufficiently | |
| 503 | 814 |
&1 is not a valid value for the NAFTA preference method (item &2) | The short text describes the object sufficiently | |
| 504 | 815 |
&1 is not a valid value for an EU preference indicator (item &2) | The short text describes the object sufficiently | |
| 505 | 816 |
&1 is not a valid value for a NAFTA preference indicator (item &2) | The short text describes the object sufficiently | |
| 506 | 817 |
&1 is not a valid value for the "Agreement Used" indicator (item &2) | The short text describes the object sufficiently | |
| 507 | 818 |
&1 is not a valid value for the "Price-Dependent" indicator (item &2) | The short text describes the object sufficiently | |
| 508 | 819 |
Agreement &1 was not activated (item &2) | The short text describes the object sufficiently | |
| 509 | 820 |
&1 is not a valid preference indicator for agreement &2 (item &3) | The short text describes the object sufficiently | |
| 510 | 899 |
This transaction is obsolete and should not longer be used | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141107 | SAP |
| SAP Release Created in | 300_620 |
