Menu

SAP Message Class J1B_NFE_ERP_GRC

Message Class for NFe ERP-GRC Communication

Recommended Now

Fire TV Stick Lite Essentials Bundle

This bundle contains Amazon Fire TV Stick Lite and Mission USB Power Cable. The USB power cable eliminates the need to find an AC outlet near your TV by powering Amazon Fire TV directly from your TV's USB port. Includes special power management circuitry that enhances the peak power capability of the USB port by storing excess energy and then releasing it as needed.

Check it out on amazon.com →

The Message Class J1B_NFE_ERP_GRC (Message Class for NFe ERP-GRC Communication) is a standard Message Class in SAP ERP and is part of the package J1BA.

Technical Information

Message Class J1B_NFE_ERP_GRC
Short Text Message Class for NFe ERP-GRC Communication
Package J1BA

Messages

ID Language Text
000 E *** Messages 001-099 are defined in GRC, 100-199 in ERP / do not use
001 E Document &1 is already in process
002 E Document &1 already exists
003 E Document &1: Customizing error: Key storage data not maintained
004 E Document &1: Customizing error: Official version not maintained
005 E Document &1: Customizing error: XML version not maintained
006 E Document &1: Signature service is not available
007 E Validation info: Field &1 in check &2 is filled
008 E Validation error: Field &2: &3 (Field &1)
009 E No entry for NF-e &1 exists in table /XNFE/NFE_HIST
010 E
012 E Document &1: The XML version &2 is not supported
013 E Status of NF-e &1 does not allow cancellation/skipping
074 E Document &1 is already in process
075 E Document &1 already exists
076 E Document &1: Customizing error: Key storage data not maintained
077 E Document &1: Customizing error: Official version not maintained
078 E Document &1: Customizing error: XML version not maintained
079 E Document &1: Signature service is not available
081 E Validation error: Field (&1) &2, &3
101 E Wrong message type for document &1
102 E Document number and Access key are empty
103 E No entry exists in the NF-e table for document number &1 / access key &2
104 E A protocol number is required for NF-e &1
105 E Message type &1 is not defined
106 E No status code was received for NF-e &1
107 E Document status &3 is not allowed for NF-e &1 with sys.comm.status &2
108 E Current status &1 does not allow next status &2 for document &3
109 E New system communication status &1 is not allowed for previous SCS &2
110 E Protocol number &1 is not numeric
111 E DB error: insert of NF-e with key &1, &2, &3 into J_1BNFE_HISTORY failed
112 E Nota Fiscal &1 not found
113 E Table &1 is locked by another user
114 E New system communication status &1 is not allowed for MsgStatus &2
115 E
116 E XML for Nota Fiscal &1 has already been processed
401 E No suitable NF-e found
402 E Corresponding NF-e event already exists
403 E Error during processing of NF-e event string
404 E NF-e is locked, NF-e event cannot be created
405 E Official NF-e event code does not correspond to expected value
406 E NF-e event cannot be created, retry or contact system administrator
410 E Validation error: Text is too short or too long
411 E Validation error in CC-e: Sequence number is greater than 20
412 E Validation error in CC-e: NF-e &1 is older than 30 days
413 E NF-e &1 is not authorized
415 E XML schema error, invalid time zone for NF-e event creation
420 E NF-e &1 has already been archived
501 E NF-e event &1 not assigned to an event code in Customizing
502 E Nf-e event &1 not defined as electronic correction letter in Customizing
503 E Database error, system could not update NF-e Event Table with key &1
504 E No electronic correction letter with sequence no. &2 found for NF-e &1
505 E NF-e event &1 not assigned to an event group &2 in Customizing
506 E No corresponding NF-e event found for document &1 event &2 int. seqno.
507 E NF-e event &2 internal seqno. &3 for doc. &1 has already been processed
508 E NF-e event &2 (&3) for &1 has already been processed with different data
509 E NF-e event &2 (&3) for document &1 has no authorization timestamp