cancel
Showing results for 
Search instead for 
Did you mean: 

GRC conexão com SEFAZ Homologação

former_member406953
Participant
0 Kudos

Bom dia Pessoal, alguém está com problemas de conexão com a SEFAZ SP - homologação?

Em nosso ambiente de desenvolvimento a NF foi criada com sucesso, adicionada ao lote no GRC, não não foi enviada a SEFAZ:

ERRO:

*************************************

Overall Status of Nfe : 04 (Added to Batch)

Error Status: 38 (Batch: Web service unreachable)

*************************************

Batch Status : Batch Created (Batch: Web service unreachable)

When we try to resend the batch :

Web service is currently unavailable; batch will not be sent

*************************************

The latest Service Status Check shows 2 Red entries for SCAN and SEFAZ.

Error Status : 70 Error from the authorities

(MAPPING.TRANSFORMER_EXCEPTION Exception occurred during XSLT mapping of the application)

Alguma dica? muito obrigada?

Fabiana

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Obrigado pela ajuda de todos!

Acabamos de receber a resposta da OSS que abrimos, o Fernando Da Ros sugeriu a aplicação da nota 1522630 que está no SPKG 24 de Basis, e o problema foi resolvido!

Aplicamos também a nota 1608324.

Answers (3)

Answers (3)

Former Member
0 Kudos

Boa tarde Pessoal!

Estamos com o mesmo problema, alguu00E9m tem a soluu00E7u00E3o?

Segue algumas informau00E7u00F5es sobre o erro:

1)

Estamos no support package 19 do NFe 1.0 e SAP ABAP/BASIS 23.

2)

Na consulta "Status do serviu00E7o" todos os ambientes do SEFAZ que temos mapeados aqui estu00E3o com status de erro 70 - Erro do processamento da nota fiscal eletru00F4nica.

3)

Na transau00E7u00E3o SXMB_MONI temos o erro abaixo:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Inbound Message -->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>Application</SAP:Category>

<SAP:Code area="MAPPING">TRANSFORMER_EXCEPTION</SAP:Code>

<SAP:P1>GENERIC_SOAP12OutConverter</SAP:P1>

<SAP:P2>http://sap.com/xi/NFE/006</SAP:P2>

<SAP:P3>fc277224-4c15-11dc-8dc6-d7af0a115642</SAP:P3>

<SAP:P4>-1</SAP:P4>

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Exception occurred during XSLT mapping of the application</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

4)

Ainda na transau00E7u00E3o SXMB_MONI temos a mensagem:

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />

- <!-- ************************************

-->

<Trace level="1" type="T">Interface Mapping http://sap.com/xi/NFE/006 SRVSC_nfeStatusServicoNF2_TO_nfeStatusServicoNF2SoapIn</Trace>

<Trace level="1" type="T">Payload is empty</Trace>

<Trace level="1" type="T">TransfromerException during XSLT processing:</Trace>

<Trace level="1" type="T">javax.xml.transform.TransformerException: IOException occurred while parsing stream. An empty document will be used! at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:357) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:244) at com.sap.aii.ibrun.server.mapping.MappingTransformer.transform(MappingTransformer.java:153) at com.sap.aii.ibrun.server.mapping.XSLTMapping.executeStep(XSLTMapping.java:67) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at

5)

No SAP NETWEAVER ADMINISTRATION -> MONITORING -> LOGS AND TRACES temos:

Message e0c374d5-03fe-38f1-9038-000c290c52d9(INBOUND): was not delivered due to com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Forbidden

6)

Ainda no LOGS AND TRACES:

Transformer exception occurred when executing XSLT GENERIC_SOAP12OutConverter (http://sap.com/xi/NFE/006, fc277224-4c15-11dc-8dc6-d7af0a115642, -1)

Thrown:

MESSAGE ID: com.sap.aii.ibrun.server.mapping.rb_MappingRuntimeException.TRANSFORMER_EXCEPTION

com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Transformer exception occurred when executing XSLT GENERIC_SOAP12OutConverter (http://sap.com/xi/NFE/006, fc277224-4c15-11dc-8dc6-d7af0a115642, -1)

at com.sap.aii.ibrun.server.mapping.XSLTMapping.executeStep(XSLTMapping.java:82)

at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92)

at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)

at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)

at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)

at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)

at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131)

at sun.reflect.GeneratedMethodAccessor1093.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)

at $Proxy192.processFunction(Unknown Source)

at sun.reflect.GeneratedMethodAccessor1092.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284)

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)

at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Category: /Applications/ExchangeInfrastructure/IntegrationServer

Location: XIRUN.com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler

Application: sap.com/com.sap.xi.services

Thread: SAPEngine_Application_Thread[impl:3]_4

Data Source: F:\usr\sap\GRD\DVEBMGS00\j2ee\cluster\server0\log\defaultTrace.trc

Message ID: 000C290C52D900660000004D000018F00004AA29E0B6F2E2

Argument Objects: n/a

Arguments: n/a

DSR Component: n/a

DSR Transaction: dad13040c37411e0836a000c290c52d9

DSR User: n/a

Message Code: n/a

Session: 0

Transaction: SAP J2EE Engine JTA

Obrigado!

Former Member
0 Kudos

TKMCL / Fabiana,

Está aplicado o SPK19 com as notas posteriores?

Notas <a href="https://websmp130.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/spat/index.htm?sp1=SAPK-10020INSLLNFE"> SAPK-10020INSLLNFE</a>

Acredito que esteje aplicado, mas o TPZ File no repository está aplicado até o 19 ? Não ocorreu nenhum erro, pois pela mensagem que você colou o erro está no transformation mesmo, não chega na Sefaz.

No Netweaver está conseguindo fazer update no SLD?!? Consulte pelo repository se após aplicação do TPZ está com status verde nas atualizações com SLD, pode ter acontecido algo e estar parcial.

's,

Bruno Lima

henrique_pinto
Active Contributor
0 Kudos

Deve ter mudado alguma coisa então. Sugiro abrir chamado no componente SLL-NFE para avaliação.

Abs,

Henrique.

henrique_pinto
Active Contributor
0 Kudos

XSLT? Não sei se tem mapping XSLT pro SRVSC.

Dê uma verificada se nao tem algum Z em cima.

Abs,

Henrique.

former_member182114
Active Contributor
0 Kudos

Bom dia Fabiana,

Teve alguma modificação no ambiente interno? Outras Secretarias estão respondendo Ok?

Esse mapping transformation pode ser devido a uma resposta inválida da Sefaz, pegue o conteúdo do payload sincrono com a resposta da Sefaz e poste aqui, por favor.

Atenciosamente, Fernando Da Ró