SAP ABAP Message Class J1B_NFE (Message class for NF-e)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-LOC-BR (Application Component) Brazil
⤷
J1BA (Package) Localization Brazil
BBPCRM (Software Component) BBPCRM⤷
CRM-LOC-BR (Application Component) Brazil⤷
J1BA (Package) Localization Brazil 
Attributes
| Message class |  |
J1B_NFE |
| Short Description |  |
Message class for NF-e |
| Changed On |  |
20140121 |
| Last Changed At |  |
105425 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
*** NF-e Process Error Messages | Space: object requires documentation | |
| 2 | 001 |
Document number &1 is not authorized for cancellation | Space: object requires documentation | |
| 3 | 002 |
Cancel is not allowed for combination of doc. status &1 and SCS &2 | Space: object requires documentation | |
| 4 | 003 |
Combination of document status &1 and SCS &2 is not allowed | Space: object requires documentation | |
| 5 | 004 |
Current status &1 does not allow next status &2 for document &3 | Space: object requires documentation | |
| 6 | 005 |
Document &1 has doc. status &2; new document status &3 is not allowed | Space: object requires documentation | |
| 7 | 006 |
Document &1 is authorized to be cancelled; new SCS &2 is not allowed | Space: object requires documentation | |
| 8 | 007 |
New system communication status &1 is not allowed for previous SCS &2 | Space: object requires documentation | |
| 9 | 008 |
Enter at least one parameter (document number or access key) | Space: object requires documentation | |
| 10 | 009 |
Select only one entry | Space: object requires documentation | |
| 11 | 010 |
No status code was received for document number &1 | Space: object requires documentation | |
| 12 | 011 |
Status code &2 for document number &1 has not been defined | Space: object requires documentation | |
| 13 | 012 |
No entry exists in the Actual Status table for document number &1 | Space: object requires documentation | |
| 14 | 013 |
No entry exists in the Actual Status table for access key &1 | Space: object requires documentation | |
| 15 | 014 |
Printer configuration not found for co. code &1 bus. place &2 and form &3 | Space: object requires documentation | |
| 16 | 015 |
Contingency NF type is not maintained for NF type &1 | Space: object requires documentation | |
| 17 | 016 |
Document &1 has already been canceled; a new request is not allowed | Space: object requires documentation | |
| 18 | 017 |
Document &1 is already in contingency; cannot switch to contingency again | Space: object requires documentation | |
| 19 | 018 |
Message type &1 is not defined | Space: object requires documentation | |
| 20 | 019 |
DB error: insert of record with key &1 into J_1BNFE_ACTIVE failed | Space: object requires documentation | |
| 21 | 020 |
DB error: insert of record (key &1, &2, &3) into J_1BNFE_HISTORY failed | Space: object requires documentation | |
| 22 | 021 |
DB error: update of record with key &1 in J_1BNFE_ACTIVE failed | Space: object requires documentation | |
| 23 | 022 |
DB error: update of NF database for nota fiscal &1 failed | Space: object requires documentation | |
| 24 | 023 |
Request to cancel NF &1 not allowed for doc. status &2 and sys. status &3 | Space: object requires documentation | |
| 25 | 024 |
Error occurred during document processing; check error log | Space: object requires documentation | |
| 26 | 025 |
Text for document status is not available in logon language | Space: object requires documentation | |
| 27 | 026 |
Authorization code for authorized document &1 is missing | Space: object requires documentation | |
| 28 | 027 |
Document processed successfully | Space: object requires documentation | |
| 29 | 028 |
Switching document no. &1 with status &2 to contingency is not allowed | Space: object requires documentation | |
| 30 | 029 |
Document &1 was canceled; switching to contingency mode is not possible | Space: object requires documentation | |
| 31 | 030 |
No selection was made | Space: object requires documentation | |
| 32 | 031 |
Maximum length of document number is nine digits | Space: object requires documentation | |
| 33 | 032 |
Doc. no. can contain only numbers; doc. no. &1 contains other characters | Space: object requires documentation | |
| 34 | 033 |
Error logs were deleted successfully | Space: object requires documentation | |
| 35 | 034 |
No error logs exist for the selected documents | Space: object requires documentation | |
| 36 | 035 |
Document number &1 is already switched to contingency | Space: object requires documentation | |
| 37 | 036 |
Series for electronic fiscal documents must be numeric and not &1 | Space: object requires documentation | |
| 38 | 037 |
No error logs exist for document number &1 | Space: object requires documentation | |
| 39 | 038 |
Authorization code &1 is not numeric | Space: object requires documentation | |
| 40 | 039 |
Document number &1 has not been authorized; printing is not possible | Space: object requires documentation | |
| 41 | 040 |
Doc. &1 switched to contingency; cancel source document and post it again | Space: object requires documentation | |
| 42 | 041 |
No authorization to cancel an authorized fiscal document | Space: object requires documentation | |
| 43 | 042 |
Document must not be changed; switching to display mode | Space: object requires documentation | |
| 44 | 043 |
Contingency settings were changed successfully | Space: object requires documentation | |
| 45 | 044 |
Doc. status &3 is not allowed for document &1 with sys. comm. status &2 | Space: object requires documentation | |
| 46 | 045 |
Automatic cancellation of document &1 not possible; check source document | Space: object requires documentation | |
| 47 | 046 |
Assign only a document or a system communication status to status code | Space: object requires documentation | |
| 48 | 047 |
Assign one of the system statuses to the status code | Space: object requires documentation | |
| 49 | 048 |
Number range is not maintained for NF type &1 | Space: object requires documentation | |
| 50 | 049 |
Document &1 switched to contingency; &2 received from authorities' system | Space: object requires documentation | |
| 51 | 050 |
Incoming document without a print form cannot be set to contingency | Space: object requires documentation | |
| 52 | 051 |
Nota fiscal type could not be determined while contingency applies | Space: object requires documentation | |
| 53 | 052 |
RFC connection to messaging system is not available | Space: object requires documentation | |
| 54 | 053 |
RFC connection to messaging system is set up and working correctly | Space: object requires documentation | |
| 55 | 054 |
Check not possible | Space: object requires documentation | |
| 56 | 055 |
Current status for document &1 not found; cancellation is not possible | Space: object requires documentation | |
| 57 | 056 |
No authorization for selected action | Space: object requires documentation | |
| 58 | 057 |
No authorization for selected action | Space: object requires documentation | |
| 59 | 058 |
Nota fiscal displayed is not an electronic fiscal document | Space: object requires documentation | |
| 60 | 059 |
Switching document to normal processing is not allowed | Space: object requires documentation | |
| 61 | 060 |
DB error: insert of record with key &1, &2 into J_1BNFE_INVALID failed | Space: object requires documentation | |
| 62 | 061 |
DB error: delete of rec. with key &1, &2, &3 from J_1BNFE_HISTORY failed | Space: object requires documentation | |
| 63 | 062 |
Contingency was successfully reset for document number &1 | Space: object requires documentation | |
| 64 | 063 |
Inconsistency of inbound XML: status code not allowed | Space: object requires documentation | |
| 65 | 064 |
Inconsistency of inbound XML: elctronic fiscal document not in database | Space: object requires documentation | |
| 66 | 065 |
Request for authorization to cancel document number &1 is not allowed | Space: object requires documentation | |
| 67 | 066 |
RFC connection &1 failed during sending of request | Space: object requires documentation | |
| 68 | 067 |
Request for cancel/skip for document number &1 rejected | Space: object requires documentation | |
| 69 | 068 |
Document no. &1 manually switched to contingency is not canceled | Space: object requires documentation | |
| 70 | 069 |
Random No. must be numeric and not &1 | The short text describes the object sufficiently | |
| 71 | 070 |
For region &1, no XML version has been maintained | Space: object requires documentation | |
| 72 | 071 |
Access key &1 not unique in Actual Status (J_1BNFE_ACTIVE) table | Space: object requires documentation | |
| 73 | 072 |
Inconsistent status update from messaging system | Space: object requires documentation | |
| 74 | 073 |
Resending request for document no. &1 not allowed when MSS is &2 | Space: object requires documentation | |
| 75 | 074 |
Resending cancel request for document &1 with SCS &2 is an invalid action | Space: object requires documentation | |
| 76 | 075 |
For electronic documents, use the J1B1N, J1B2N and J1B3N transactions | Space: object requires documentation | |
| 77 | 076 |
Assignment is not complete | Space: object requires documentation | |
| 78 | 077 |
Outgoing document &1 has not been authorized; current status is &2 | Space: object requires documentation | |
| 79 | 078 |
Manually inserted check digit (&1) differs from calculated digit (&2) | Space: object requires documentation | |
| 80 | 079 |
NF BAPI: Electronic doc. settings are inconsistent for used NF type &1 | Space: object requires documentation | |
| 81 | 080 |
NF BAPI: Doc. status must be initial for doc. subject to authorization | The short text describes the object sufficiently | |
| 82 | 081 |
Not possible to resend electronic fiscal document &1 with SCS &2 | The short text describes the object sufficiently | |
| 83 | 082 |
Not possible to resend electronic fiscal document &1 with status &2 | The short text describes the object sufficiently | |
| 84 | 083 |
NF Type not allowed; form must be assigned | Space: object requires documentation | |
| 85 | 084 |
Enter an electronic fiscal document | The short text describes the object sufficiently | |
| 86 | 085 |
Document already copied | Space: object requires documentation | |
| 87 | 086 |
Electronic fiscal document not switched to contigency | Space: object requires documentation | |
| 88 | 087 |
Referenced electronic fiscal document must have been created manually | The short text describes the object sufficiently | |
| 89 | 088 |
Update Error J_1BNFENUMGAP & | The short text describes the object sufficiently | |
| 90 | 089 |
Message type &1 recieved from messaging system not allowed | Space: object requires documentation | |
| 91 | 090 |
Not possible to reset document status for this document | Space: object requires documentation | |
| 92 | 091 |
Reset not allowed for canceled electronic fiscal document | The short text describes the object sufficiently | |
| 93 | 092 |
Reset not allowed for electronic fiscal document switched to contigency | The short text describes the object sufficiently | |
| 94 | 093 |
Cannot number doc. and send it to tax authority; doc no. &1 already used | The short text describes the object sufficiently | |
| 95 | 094 |
Contingency for unnumbered electronic fiscal document not allowed | Space: object requires documentation | |
| 96 | 095 |
Sending of unnumbered electronic fiscal document not allowed | Space: object requires documentation | |
| 97 | 096 |
Numbering not possible without an assigned Form | Space: object requires documentation | |
| 98 | 097 |
Electronic fiscal document cancelled; numbering not allowed | Space: object requires documentation | |
| 99 | 098 |
Database-Error: entries deleted in J_1BNFERFCBATCH table | The short text describes the object sufficiently | |
| 100 | 099 |
Numbering in Monitor for RFC execution &1 not allowed | Space: object requires documentation | |
| 101 | 100 |
Reset not allowed when skipping request has been sent to tax authorities | Space: object requires documentation | |
| 102 | 101 |
Not possible to send document; region or business place set to contigency | The short text describes the object sufficiently | |
| 103 | 102 |
Cancellation request to authorities not necessary, cancel via application | Space: object requires documentation | |
| 104 | 103 |
Not possible to send elec. doc.; no authorization from tax auth. needed | The short text describes the object sufficiently | |
| 105 | 104 |
SCAN form is not maintained for NF-type &1 | Space: object requires documentation | |
| 106 | 105 |
Switching elec. document &1 with messaging system error is not allowed | Space: object requires documentation | |
| 107 | 106 |
Wrong doc. series for company code &1 business place &2 and doc. form &3 | Space: object requires documentation | |
| 108 | 107 |
Electronic fiscal document numbering not possible for document number &1 | Space: object requires documentation | |
| 109 | 108 |
Parameter 'RFC Execution' not considered for SCAN form | Space: object requires documentation | |
| 110 | 109 |
Elec. fiscal document for doc. &1 numbered and sent to messaging system | Space: object requires documentation | |
| 111 | 110 |
Authorities' server down; enter reason for contingency | The short text describes the object sufficiently | |
| 112 | 111 |
Messaging system down; enter reason for contingency | The short text describes the object sufficiently | |
| 113 | 112 |
The short text describes the object sufficiently | ||
| 114 | 113 |
Documents &1 and &2 cannot be cancelled within one step | Space: object requires documentation | |
| 115 | 114 |
Random no &1 exceeds allowed length of &2 | The short text describes the object sufficiently | |
| 116 | 115 |
Access key is incomplete | The short text describes the object sufficiently | |
| 117 | 116 |
Value of &1 &2 does not match value &3 in the access key | The short text describes the object sufficiently | |
| 118 | 117 |
Access key must be numeric | The short text describes the object sufficiently | |
| 119 | 118 |
Status of authorized electronic document cannot be "Waiting for Response" | The short text describes the object sufficiently | |
| 120 | 119 |
Electronic fiscal document can only be posted if cancellation flag is set | Space: object requires documentation | |
| 121 | 120 |
Issuing Type for SCAN cannot be set in document &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 122 | 121 |
Value &1 for &2 not allowed | The short text describes the object sufficiently | |
| 123 | 122 |
Doc. &1 cannot be canceled; no authorization for cancellation received | Space: object requires documentation | |
| 124 | 123 |
Electronic fiscal document &1 already canceled | Space: object requires documentation | |
| 125 | 124 |
Document &1 cannot be canceled; source document &2 locked by another user | The short text describes the object sufficiently | |
| 126 | 125 |
No entries exist for electronic fiscal document no. &1 in history table | The short text describes the object sufficiently | |
| 127 | 126 |
Not possible to complete action; doc. &1 already changed by another user | Space: object requires documentation | |
| 128 | 127 |
Request to cancel/skip already sent for electronic fiscal document no. &1 | The short text describes the object sufficiently | |
| 129 | 128 |
Electronic fiscal document no. &1 cannot be canceled | The short text describes the object sufficiently | |
| 130 | 129 |
Cannot cancel elec. fiscal documents; document &1 switched to contingency | The short text describes the object sufficiently | |
| 131 | 130 |
Cannot switch to contingency; document &1 canceled prior to authorization | The short text describes the object sufficiently | |
| 132 | 131 |
Not possible to cancel document &1 prior to auth.; other action required | Space: object requires documentation | |
| 133 | 132 |
Document &1 canceled prior to auth.; &2 received from authorities | Space: object requires documentation | |
| 134 | 133 |
Reset not possible; elec. document was canceled prior to authorization | The short text describes the object sufficiently | |
| 135 | 134 |
You cannot switch an electronic document without a form to contingency | The short text describes the object sufficiently | |
| 136 | 135 |
Cancellation prior to authorization reset for document no. &1 | The short text describes the object sufficiently | |
| 137 | 136 |
Not possible to cancel doc. &1 prior to auth. with messaging system error | Space: object requires documentation | |
| 138 | 137 |
CT-e can be created only using CT-e as reference | The short text describes the object sufficiently | |
| 139 | 138 |
Cannot copy reason; reason not allowed for this model | Space: object requires documentation | |
| 140 | 139 |
Cannot use reason '&1' for document with model '&2' | Space: object requires documentation | |
| 141 | 140 |
Cannot send cncl. req.; reason missing for company &1 branch &2 model &3 | Space: object requires documentation | |
| 142 | 141 |
Cannot send auto. cancel. req.; no long text for reason &1 language &2 | Space: object requires documentation | |
| 143 | 142 |
None of the selected documents can be printed or reprinted | Space: object requires documentation | |
| 144 | 143 |
Print program used by & is intended for electronic fiscal documents only | Space: object requires documentation | |
| 145 | 144 |
Processing of event &2 (&3) for doc. &1 with errors; refer to msg. system | Space: object requires documentation | |
| 146 | 147 |
Subsequent document exists, contingency not allowed for document &1 | The short text describes the object sufficiently | |
| 147 | 148 |
Text for cancellation reason not available in language &1 | The short text describes the object sufficiently | |
| 148 | 150 |
Incorrect environment type; Homologation not allowed in production client | The short text describes the object sufficiently | |
| 149 | 170 |
Pauta Base value out of range | The short text describes the object sufficiently | |
| 150 | 171 |
Municipal Document flag not available for Model &1 | The short text describes the object sufficiently | |
| 151 | 172 |
Electronic Doc. flag only available for documents authorized by SEFAZ | The short text describes the object sufficiently | |
| 152 | 173 |
Check if the pauta base for this item needs adjustments (tab page Taxes) | The short text describes the object sufficiently | |
| 153 | 200 |
****** Messages in range 201-250 are used for checking tools ************ | The short text describes the object sufficiently | |
| 154 | 201 |
Another business place uses already this number range for NF-e | Space: object requires documentation | |
| 155 | 202 |
In the selected range no number ranges for NF-e have conflicts | The short text describes the object sufficiently | |
| 156 | 203 |
No authorization for requested action | The short text describes the object sufficiently | |
| 157 | 204 |
No data selected | The short text describes the object sufficiently | |
| 158 | 207 |
There was no amount in the return table | The short text describes the object sufficiently | |
| 159 | 208 |
The amount could not be converted | Space: object requires documentation | |
| 160 | 209 |
Error in Call of &1 &2: &3 | The short text describes the object sufficiently | |
| 161 | 210 |
Number of inconsistent entries removed from batch report: &1 | The short text describes the object sufficiently | |
| 162 | 211 |
Removed NF-e with document number: &1 | The short text describes the object sufficiently | |
| 163 | 212 |
Cannot assign tax group &1 to structure J_1BNF&2; struc. not tax-relevant | The short text describes the object sufficiently | |
| 164 | 213 |
Cannot enter field &1; data structure has no tax group | Space: object requires documentation | |
| 165 | 214 |
Cannot enter field &1; field does not exist in structure J_1BNF&2 | The short text describes the object sufficiently | |
| 166 | 215 |
Invalid entry; tax type &1 not assigned to tax group &2 | The short text describes the object sufficiently | |
| 167 | 216 |
Content of field &1 cannot be filled using MS Excel upload | The short text describes the object sufficiently | |
| 168 | 220 |
Select #Electronic Doc.# checkbox for CT-e | The short text describes the object sufficiently | |
| 169 | 221 |
CT-e with doc. type &1 (#&2#) cannot have value annulment as CT-e type | The short text describes the object sufficiently | |
| 170 | 222 |
CT-e with document type &1 (#&2#) cannot have substitution as CT-e type | The short text describes the object sufficiently | |
| 171 | 223 |
Document type &1 ('&2') cannot be assigned together with NF model 57 | The short text describes the object sufficiently | |
| 172 | 224 |
Error in BAdI implementation; table &1 has entries with duplicate keys | The short text describes the object sufficiently | |
| 173 | 225 |
Error in BAdI implementation; table &1 references non-existing item | The short text describes the object sufficiently | |
| 174 | 300 |
***** NFe incoming - Messages 300 - 399 ***** | The short text describes the object sufficiently | |
| 175 | 301 |
Invoice and NF-e cannot be simulated; scenario not supported | Space: object requires documentation | |
| 176 | 302 |
Items in nota fiscal have several company codes; scenario not supported | Space: object requires documentation | |
| 177 | 303 |
Entry missing in obligatory field &1 | The short text describes the object sufficiently | |
| 178 | 304 |
Different currencies in NF (&1) and purchase order (&2) not supported | Space: object requires documentation | |
| 179 | 305 |
NF-e incoming automation not possible | Space: object requires documentation | |
| 180 | 306 |
Entry missing in obligatory table/field &1 | The short text describes the object sufficiently | |
| 181 | 307 |
Business process &1 not found | Space: object requires documentation | |
| 182 | 308 |
Conversion failed for unit of measure &1 in purchase order &2 line &3 | The short text describes the object sufficiently | |
| 183 | 309 |
Posting not possible; NF no. in document (&1) and access key (&2) differ | Space: object requires documentation | |
| 184 | 310 |
Posting not possible; series in NF no. (&1) and access key (&2) differ | Space: object requires documentation | |
| 185 | 311 |
No purchase order found | The short text describes the object sufficiently | |
| 186 | 312 |
Search failed; internal error | The short text describes the object sufficiently | |
| 187 | 313 |
Posting not possible; region in access key (&1) and for vendor (&) differ | Space: object requires documentation | |
| 188 | 314 |
Check digit in access key (&1) differs from calculated value (&2) | The short text describes the object sufficiently | |
| 189 | 315 |
NCM code &1 does not match search criteria | The short text describes the object sufficiently | |
| 190 | 316 |
Purchase order &1 does not exist | The short text describes the object sufficiently | |
| 191 | 317 |
Purchase order item &1 &2 does not exist | The short text describes the object sufficiently | |
| 192 | 318 |
Purchasing document &1 &2 is set for deletion | The short text describes the object sufficiently | |
| 193 | 319 |
Purchasing document &1 &2 is set to delivery completed | The short text describes the object sufficiently | |
| 194 | 320 |
Purchasing schema missing in purchase order &1 | The short text describes the object sufficiently | |
| 195 | 321 |
Entry missing in table T007a for procedure &1 tax code &2 | The short text describes the object sufficiently | |
| 196 | 322 |
Material usage consumption not allowed for &1 &2 &3 | The short text describes the object sufficiently | |
| 197 | 323 |
Evaluation of discount/insurance/other expenses failed for &1 &2 | The short text describes the object sufficiently | |
| 198 | 324 |
No entries in table T683S for usage &1 application &2 procedure &3 &4 | The short text describes the object sufficiently | |
| 199 | 325 |
Entry missing in conditions table T683S for &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 200 | 326 |
Entry missing in table J_1BNFTXCOND for procedure &1 tax type &2 | The short text describes the object sufficiently | |
| 201 | 327 |
Procedure &1 tax type &2 in table J_1BNFTXCOND not consistent | The short text describes the object sufficiently | |
| 202 | 328 |
Delivery &1 with external identification number &2 does not exist | The short text describes the object sufficiently | |
| 203 | 329 |
Several goods receipt postings exist for the same NF item &1 &2 | The short text describes the object sufficiently | |
| 204 | 330 |
Several tax codes or CFOP for one single purchase order item &1 &2 | The short text describes the object sufficiently | |
| 205 | 331 |
Invoice for nota fiscal &1&2 has status 'Entered and Held' | The short text describes the object sufficiently | |
| 206 | 332 |
Parked data in invoice &1 &2 selected for deletion | The short text describes the object sufficiently | |
| 207 | 333 |
Posting for invoice &1 &2 does not exist; deletion not possible | The short text describes the object sufficiently | |
| 208 | 334 |
Multiple assignments to the same purchase order item &1 &2 | The short text describes the object sufficiently | |
| 209 | 335 |
You are not authorized to make changes in company code &1 | The short text describes the object sufficiently | |
| 210 | 336 |
Trace data of &1 documents deleted | The short text describes the object sufficiently | |
| 211 | 337 |
Technical description of table &1 outdated; contact support | The short text describes the object sufficiently | |
| 212 | 338 |
Deletion of inbound delivery &1 not allowed; prevented by BAdI implement. | Space: object requires documentation | |
| 213 | 339 |
Inbound delivery was not found by search implementation | The short text describes the object sufficiently | |
| 214 | 340 |
Error in BAdI implementation; cannot create inbound delivery | Space: object requires documentation | |
| 215 | 341 |
Error in BAdI implementation; items in NF-e &1 from several deliveries | Space: object requires documentation | |
| 216 | 342 |
Error in BAdI implement.; items in NF-e &1 do not match delivery items | Space: object requires documentation | |
| 217 | 343 |
Error in BAdI implementation; no data returned | Space: object requires documentation | |
| 218 | 344 |
Movement type could not be determined using delivery type | Space: object requires documentation | |
| 219 | 345 |
Expected &1 tax rate is &2 but tax rate in XML is &3 | Space: object requires documentation | |
| 220 | 346 |
&1 tax not available in XML for purchase order item &2 &3 xml pos. &4 | Space: object requires documentation | |
| 221 | 347 |
Update request for document &1 &2 failed; contact system administrator | The short text describes the object sufficiently | |
| 222 | 348 |
Validation of & tax for purchase order &2 &3 not possible | The short text describes the object sufficiently | |
| 223 | 349 |
Error in BAdI implementation; inbound delivery &1 not in database | Space: object requires documentation | |
| 224 | 350 |
Inbound delivery &2 incorrect; refer. no. &1 missing/has incorrect format | The short text describes the object sufficiently | |
| 225 | 351 |
Expected &1 tax rate is &2 but tax rate in reference invoice is &3 | The short text describes the object sufficiently | |
| 226 | 352 |
Items in PO &1 assigned to several plants; system assigns RTP to plant &2 | Space: object requires documentation | |
| 227 | 353 |
UoM &1 not in material master of &2; conversion not possible | The short text describes the object sufficiently | |
| 228 | 354 |
Vendor not found; validation of RTP materials is not possible | The short text describes the object sufficiently | |
| 229 | 355 |
Vendor cannot be determined for CNPJ &1 | The short text describes the object sufficiently | |
| 230 | 356 |
Tax type &1 is not allowed | The short text describes the object sufficiently | |
| 231 | 357 |
Simulated tax rate for tax type &1 must be &2; check tax code | The short text describes the object sufficiently | |
| 232 | 358 |
CNPJ for vendor &1 (&2) does not match CNPJ in XML (&3) | Space: object requires documentation | |
| 233 | 359 |
Quantity/UoM of material &1 has changed: &2 &3 | The short text describes the object sufficiently | |
| 234 | 360 |
Vendor type not allowed; vendor &1 (purchase order &2) is one-time vendor | Space: object requires documentation | |
| 235 | 361 |
Validation process &1 has not been defined; contact system admin. | The short text describes the object sufficiently | |
| 236 | 362 |
RFC connection NFE_IN does not work; check the RFC connection | Space: object requires documentation | |
| 237 | 363 |
Vendor material &1 cannot be mapped to one ERP material and one UoM | Space: object requires documentation | |
| 238 | 364 |
Subcontracting Process is supported started from ERP 6.0 EhP4 | The short text describes the object sufficiently | |
| 239 | 365 |
Simulated tax value for tax type &1 must be 0; check tax code | The short text describes the object sufficiently | |
| 240 | 366 |
Only statistical tax for &1 is allowed; check tax code | The short text describes the object sufficiently | |
| 241 | 367 |
Item Number Increment not set for Delivery Type &1 | The short text describes the object sufficiently | |
| 242 | 368 |
Goods receipt quantity (&1) differs from XML quantity (&2) | Space: object requires documentation | |
| 243 | 369 |
Business Process could not be identified | The short text describes the object sufficiently | |
| 244 | 371 |
Only tax codes with material usage "Production/Sales" are allowed | The short text describes the object sufficiently | |
| 245 | 372 |
Message from BAdI implementation | The short text describes the object sufficiently | |
| 246 | 373 |
Enter for reason &1 a description with at least 15 characters | Space: object requires documentation | |
| 247 | 374 |
At least one descr. exists for a reason (&1) with less than 15 characters | Space: object requires documentation | |
| 248 | 375 |
Invalid combination of parameter values &1 &2 &3 &4 | Space: object requires documentation | |
| 249 | 376 |
Inbound delivery split not supported, check purchase orders | The short text describes the object sufficiently | |
| 250 | 377 |
Recipient CNPJ (&3) differs from Business place CNPJ (&4) in PO &1 &2 | Space: object requires documentation | |
| 251 | 378 |
Several goods receipts exist for purchase order &1 item &2 with MAA | Space: object requires documentation | |
| 252 | 379 |
Several NF-e items exist for purchase order &1 item &2 with MAA | Space: object requires documentation | |
| 253 | 380 |
Inconsistency in freight for PO &1 item &2 (invoice &3, NF &4) BRL | The short text describes the object sufficiently | |
| 254 | 381 |
Several NF-e items exist for the same PO item in subcontracting | Space: object requires documentation | |
| 255 | 382 |
Several NF-e items exist for the same PO item in future delivery invoice | Space: object requires documentation | |
| 256 | 383 |
Use either old or new parameters for items and taxes for invoice creation | The short text describes the object sufficiently | |
| 257 | 384 |
Several NF-e items are assigned to the same PO item | Space: object requires documentation | |
| 258 | 386 |
Process &1 is not defined for invoice verification | The short text describes the object sufficiently | |
| 259 | 387 |
More than one NF-e item exists with the same XML position number | The short text describes the object sufficiently | |
| 260 | 388 |
Table parameter &1 contains a row with an empty XML position number | The short text describes the object sufficiently | |
| 261 | 389 |
NF-e Item &1: product value &2 in NF-e differs from calculated value &3 | Space: object requires documentation | |
| 262 | 390 |
NF-e Item &1: freight value &2 in NF-e differs from calculated value &3 | Space: object requires documentation | |
| 263 | 391 |
NF-e Item &1: insurance value &2 in NF-e differs from calc. value &3 | Space: object requires documentation | |
| 264 | 392 |
NF-e Item &1: value of other expenses &2 in NF differs from calc.value &3 | Space: object requires documentation | |
| 265 | 393 |
NF-e Item &1: discount value &2 in NF-e differs from calculated value &3 | Space: object requires documentation | |
| 266 | 394 |
NF item not found for freight &3 BRL (PO &1 item &2, invoice item &4) | The short text describes the object sufficiently | |
| 267 | 395 |
Valuation type &1 does not exist yet for material &2 (PO item &3 &4) | Space: object requires documentation | |
| 268 | 396 |
Invoice &1 already exists for NF-e &2 | The short text describes the object sufficiently | |
| 269 | 397 |
Error in BAdI implementation; invalid delivery date | Space: object requires documentation | |
| 270 | 398 |
Material origin in XML &1 differs from determined origin &2 | Space: object requires documentation | |
| 271 | 399 |
Material origin in XML &1 differs from origin &2 in reference nota fiscal | The short text describes the object sufficiently | |
| 272 | 400 |
****** Messages in range 401-450 are used for Stock Transfer | The short text describes the object sufficiently | |
| 273 | 401 |
Outgoing NF-e with access key &1 does not exist | The short text describes the object sufficiently | |
| 274 | 402 |
Material document for NF-e with access key &1 does not exist | The short text describes the object sufficiently | |
| 275 | 403 |
Internal error; reference document not available for stock transfer | The short text describes the object sufficiently | |
| 276 | 404 |
User decision required to determine NF type for plant &1/movement type &2 | Space: object requires documentation | |
| 277 | 451 |
***Range 451-500 reserved for NF-e Eventing*** | The short text describes the object sufficiently | |
| 278 | 452 |
NF-e &1 not authorized/cancel request sent;correction letter not possible | The short text describes the object sufficiently | |
| 279 | 453 |
Max. number of characters is 1000; system will cut off entered text | The short text describes the object sufficiently | |
| 280 | 454 |
No authorized correction letter available for NF-e &1 | The short text describes the object sufficiently | |
| 281 | 455 |
Correction letter cannot be created or changed | Space: object requires documentation | |
| 282 | 456 |
Correction letter cannot be resent | Space: object requires documentation | |
| 283 | 457 |
Correction letter sent successfully to messaging system | The short text describes the object sufficiently | |
| 284 | 458 |
Event information not properly entered in Customizing | Space: object requires documentation | |
| 285 | 459 |
Database error; system could not update Event table for document &1 | The short text describes the object sufficiently | |
| 286 | 460 |
Correction letter does not exist for NF-e &1 | The short text describes the object sufficiently | |
| 287 | 461 |
Event &1 is not assigned to event group &2 in Customizing | Space: object requires documentation | |
| 288 | 462 |
Event &1 is already assigned to official event code | The short text describes the object sufficiently | |
| 289 | 463 |
Content of correction letter must be at least 15 characters long | The short text describes the object sufficiently | |
| 290 | 464 |
NF-e &1 is older than &2 days; correction letter cannot be created | The short text describes the object sufficiently | |
| 291 | 465 |
Sequence number is greater than 20; correction letter cannot be created | The short text describes the object sufficiently | |
| 292 | 500 |
****** Messages in range 500-549 are used for Subcontracting ****** | The short text describes the object sufficiently | |
| 293 | 501 |
No subcontracting components found for purchase order &1 &2 | The short text describes the object sufficiently | |
| 294 | 502 |
No business place found for CNPJ number &1 | The short text describes the object sufficiently | |
| 295 | 503 |
Subcontracting is not category for item &2 in purchasing document &1 | The short text describes the object sufficiently | |
| 296 | 504 |
UoM &1 for material &2, vendor &3, cannot be converted into an ERP UoM | The short text describes the object sufficiently | |
| 297 | 505 |
Error in BAdI &1 method &2 for vendor &3 and XML value &4 | The short text describes the object sufficiently | |
| 298 | 506 |
Material &1 for vendor &2 cannot be converted into an ERP material | The short text describes the object sufficiently | |
| 299 | 507 |
Movement type could not be determined | The short text describes the object sufficiently | |
| 300 | 508 |
Material &1 is not a component of purchase order &2 &3 | The short text describes the object sufficiently | |
| 301 | 509 |
The short text describes the object sufficiently | ||
| 302 | 510 |
Material &1 is not a component of purchase order &2 &3 | The short text describes the object sufficiently | |
| 303 | 511 |
No goods receipt available for purchase order &1 &2 | The short text describes the object sufficiently | |
| 304 | 512 |
Unique reference document for &1 &2 &3 not found | The short text describes the object sufficiently | |
| 305 | 513 |
Material &1 not found in reference nota fiscal &2 | The short text describes the object sufficiently | |
| 306 | 514 |
Storage location not found in original material document &1 &2 | The short text describes the object sufficiently | |
| 307 | 515 |
Material &1 is not a component of purchase order &2 &3 | The short text describes the object sufficiently | |
| 308 | 516 |
Ordered material missing for component &1 &2 &3 | The short text describes the object sufficiently | |
| 309 | 518 |
Recipient of reference nota fiscal differs from sender of incoming NF | The short text describes the object sufficiently | |
| 310 | 519 |
Reference nota fiscal &1 not issued by recipient of incoming nota fiscal | The short text describes the object sufficiently | |
| 311 | 520 |
Item &1: Material no. for component may not be empty or contain wildcards | The short text describes the object sufficiently | |
| 312 | 521 |
Material no. &1 used by vendor &2 is mapped to ERP materials &3 and &4 | Space: object requires documentation | |
| 313 | 522 |
Material &1 for CNPJ &2 cannot be converted into an ERP material | The short text describes the object sufficiently | |
| 314 | 550 |
****** Messages in range 550-599 are used for CT-e ****** | The short text describes the object sufficiently | |
| 315 | 551 |
NF partner function '&1' already mapped to CT-e partner '&2' | The short text describes the object sufficiently | |
| 316 | 552 |
Corresponding mandatory CT-e partner &1 missing | Space: object requires documentation | |
| 317 | 553 |
Invalid mapping; multiple NF partner functions mapped to CT-e partner &1 | Space: object requires documentation | |
| 318 | 554 |
Runtime error in remote system &1 | The short text describes the object sufficiently | |
| 319 | 555 |
Contingency not allowed for nota fiscal type &1 | The short text describes the object sufficiently | |
| 320 | 556 |
System cannot process doc. &1; function not supported for this doc. type | The short text describes the object sufficiently | |
| 321 | 557 |
NF partner functions not mapped to CT-e partners in Customizing | Space: object requires documentation | |
| 322 | 558 |
Tax situation &1 cannot be processed for CT-e | The short text describes the object sufficiently | |
| 323 | 559 |
Contingency not possible | Space: object requires documentation | |
| 324 | 560 |
Partner type 'Business Place' not supported | The short text describes the object sufficiently | |
| 325 | 561 |
Outbound Delivery not found for NF-e &1 | Space: object requires documentation | |
| 326 | 562 |
Shipment document not found for outbound delivery &1 | Space: object requires documentation | |
| 327 | 563 |
Cost document not found for shipment document &1 | Space: object requires documentation | |
| 328 | 564 |
Multiple shipment documents exist; automation not possible | Space: object requires documentation | |
| 329 | 565 |
Multiple cost documents exist; automation not possible | Space: object requires documentation | |
| 330 | 566 |
CNPJ of CT-e service taker &1 does not match with CNPJ of plant &2 | The short text describes the object sufficiently | |
| 331 | 567 |
CNPJ of CT-e issuer &1 does not match with CNPJ of vendor &2 | The short text describes the object sufficiently | |
| 332 | 568 |
Error when reading database; system cannot carry out CNPJ check | The short text describes the object sufficiently | |
| 333 | 601 |
The short text describes the object sufficiently |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in | 604 |
