SAP ABAP Message Class J1B_NFE_ERP_GRC (Message Class for NFe ERP-GRC Communication)

Basic Data

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-LOC-BR (Application Component) Brazil
     ⤷ J1BA (Package) Localization Brazil

Attributes

Message class	J1B_NFE_ERP_GRC
Short Description	Message Class for NFe ERP-GRC Communication
Changed On	20140121
Last Changed At	105426

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	000	*** Messages 001-099 are defined in GRC, 100-199 in ERP / do not use	The short text describes the object sufficiently	☐
2	001	Document &1 is already in process	The short text describes the object sufficiently	☐
3	002	Document &1 already exists	The short text describes the object sufficiently	☐
4	003	Document &1: Customizing error: Key storage data not maintained	The short text describes the object sufficiently	☐
5	004	Document &1: Customizing error: Official version not maintained	The short text describes the object sufficiently	☐
6	005	Document &1: Customizing error: XML version not maintained	The short text describes the object sufficiently	☐
7	006	Document &1: Signature service is not available	The short text describes the object sufficiently	☐
8	007	Validation info: Field &1 in check &2 is filled	The short text describes the object sufficiently	☐
9	008	Validation error: Field &2: &3 (Field &1)	The short text describes the object sufficiently	☐
10	009	No entry for NF-e &1 exists in table /XNFE/NFE_HIST	The short text describes the object sufficiently	☐
11	010		The short text describes the object sufficiently	☐
12	012	Document &1: The XML version &2 is not supported	The short text describes the object sufficiently	☐
13	013	Status of NF-e &1 does not allow cancellation/skipping	The short text describes the object sufficiently	☐
14	014	Error occurred for document &1 during proxy transformation	The short text describes the object sufficiently	☐
15	101	Wrong message type for document &1	The short text describes the object sufficiently	☐
16	102	Document number and Access key are empty	The short text describes the object sufficiently	☐
17	103	No entry exists in the NF-e table for document number &1 / access key &2	Space: object requires documentation	☐
18	104	A protocol number is required for NF-e &1	Space: object requires documentation	☐
19	105	Message type &1 is not defined	Space: object requires documentation	☐
20	106	No status code was received for NF-e &1	Space: object requires documentation	☐
21	107	Document status &3 is not allowed for NF-e &1 with sys.comm.status &2	The short text describes the object sufficiently	☐
22	108	Current status &1 does not allow next status &2 for document &3	The short text describes the object sufficiently	☐
23	109	New system communication status &1 is not allowed for previous SCS &2	The short text describes the object sufficiently	☐
24	110	Protocol number &1 is not numeric	The short text describes the object sufficiently	☐
25	111	DB error: insert of NF-e with key &1, &2, &3 into J_1BNFE_HISTORY failed	The short text describes the object sufficiently	☐
26	112	Nota Fiscal &1 not found	The short text describes the object sufficiently	☐
27	113	Table &1 is locked by another user	The short text describes the object sufficiently	☐
28	114	New system communication status &1 is not allowed for MsgStatus &2	The short text describes the object sufficiently	☐
29	115		The short text describes the object sufficiently	☐
30	116	XML for Nota Fiscal &1 has already been processed	The short text describes the object sufficiently	☐
31	200	*** Messages 201-299 are defined in GRC for CT-e********************	The short text describes the object sufficiently	☐
32	201	Mapping error: Error during mapping of structure &1	Space: object requires documentation	☐
33	202	Mapping error: Error during mapping of the &1 field in structure &2	Space: object requires documentation	☐
34	203	Mapping error: Field &1 in structure &2 must be filled	Space: object requires documentation	☐
35	204	Error during XML transformation: &1, &2, &3	Space: object requires documentation	☐
36	205	Mapping error: One of the parameters &1, &2, &3 must be filled	Space: object requires documentation	☐
37	206	Mapping error: Error during mapping of structure &1; parameter &2 missing	Space: object requires documentation	☐
38	207	Mapping error: Value &1 in field &2 of structure &3 is not allowed	Space: object requires documentation	☐
39	208	Mapping error: No partner was found for structure &1	Space: object requires documentation	☐
40	209	Mapping error: No taxes were found for structure &1	Space: object requires documentation	☐
41	210	Mapping error: No lines were found in table &1	Space: object requires documentation	☐
42	211	Mapping error: No texts were found for structure &1	Space: object requires documentation	☐
43	212	Mapping error: No values were found for structure &1	Space: object requires documentation	☐
44	213	Status &2 of the proccess step &1 does not allow overwriting of CT-e	Space: object requires documentation	☐
45	214	Customizing error: XML version for message type &1 not defined	Space: object requires documentation	☐
46	215	Validation error: field &1: &2. Content not allowed (&3)	Space: object requires documentation	☐
47	216	Validation error: field &1: &2. Negative value not allowed (&3)	Space: object requires documentation	☐
48	217	Valid. error: CT-e ID does not match the format of tax authorites (&1)	Space: object requires documentation	☐
49	218	System environm. &1 (Homologation or Production) differs from customizing	Space: object requires documentation	☐
50	219	Customizing error: No entry found for specified tax authority system	Space: object requires documentation	☐
51	220	CT-e &1 is being edited by user &2	Space: object requires documentation	☐
52	221	CT-e &1 already exists	Space: object requires documentation	☐
53	222	ERP RFC version &1 not supported	The short text describes the object sufficiently	☐
54	223	Mode of transport &1 not supported	The short text describes the object sufficiently	☐
55	224	Combination of XML version of CT-e &1 and modal &2 not supported	The short text describes the object sufficiently	☐
56	225	CT-e XML version &1 not supported	Space: object requires documentation	☐
57	300	*** Messages 301-399 are defined in ERP for CT-e specific messages**	The short text describes the object sufficiently	☐
58	400	*** Messages 401-499 are defined in GRC for events	The short text describes the object sufficiently	☐
59	401	No suitable NF-e found	The short text describes the object sufficiently	☐
60	402	Corresponding NF-e event already exists	The short text describes the object sufficiently	☐
61	403	Error during processing of NF-e event string	Space: object requires documentation	☐
62	404	NF-e is locked; NF-e event cannot be created	Space: object requires documentation	☐
63	405	Official NF-e event code does not correspond to expected value	Space: object requires documentation	☐
64	406	NF-e event cannot be created; retry or contact system administrator	The short text describes the object sufficiently	☐
65	407	Event has been saved before RFC terminated. Resend not allowed	The short text describes the object sufficiently	☐
66	408	Error in the global table &1	The short text describes the object sufficiently	☐
67	409	Error during reading event data	The short text describes the object sufficiently	☐
68	410	Validation error: Text is too short or too long	The short text describes the object sufficiently	☐
69	411	Validation error in CC-e: Sequence number is greater than 20	The short text describes the object sufficiently	☐
70	412	Validation error in CC-e: NF-e &1 is older than 30 days	The short text describes the object sufficiently	☐
71	413	NF-e &1 is not authorized	The short text describes the object sufficiently	☐
72	414	Error during proxy transformation: &1	The short text describes the object sufficiently	☐
73	415	XML schema error; invalid time zone for NF-e event creation	Space: object requires documentation	☐
74	416	Time zone could not be determined	The short text describes the object sufficiently	☐
75	417	Not possible to process the event or change its status	The short text describes the object sufficiently	☐
76	418	Event could not be signed	The short text describes the object sufficiently	☐
77	419	No suitable entry in customizing for CNPJ &1	The short text describes the object sufficiently	☐
78	420	NF-e &1 has already been archived	The short text describes the object sufficiently	☐
79	421	Events cannot be created at this time; the CT-e is blocked	The short text describes the object sufficiently	☐
80	422	CT-e &1 is not authorized	The short text describes the object sufficiently	☐
81	423	Could not find a suitable CT-e	The short text describes the object sufficiently	☐
82	424	CT-e &1 already written to archive file	The short text describes the object sufficiently	☐
83	500	*** Messages 501-599 are defined in ERP for events	The short text describes the object sufficiently	☐
84	501	NF-e event &1 not assigned to an event code in Customizing	Space: object requires documentation	☐
85	502	Nf-e event &1 not defined as electronic correction letter in Customizing	Space: object requires documentation	☐
86	503	Database error; system could not update NF-e Event Table with key &1	The short text describes the object sufficiently	☐
87	504	No electronic correction letter with sequence no. &2 found for NF-e &1	The short text describes the object sufficiently	☐
88	505	NF-e event &1 not assigned to an event group &2 in Customizing	Space: object requires documentation	☐
89	506	No corresponding NF-e event found for document &1 event &2 int. seqno. &3	The short text describes the object sufficiently	☐
90	507	NF-e event &2 internal seqno. &3 for doc. &1 has already been processed	The short text describes the object sufficiently	☐
91	508	NF-e event &2 (&3) for &1 has already been processed with different data	The short text describes the object sufficiently	☐
92	509	NF-e event &2 (&3) for document &1 has no authorization timestamp	The short text describes the object sufficiently	☐

History

Last changed on/by	20140121	SAP
SAP Release Created in	605