APPLICATION_ERROR ExchangeFaultDataExt

[Former Member]

Olá pessoal, tudo bem?

Fiz um upgrade pra 10.0 e estou com problemas no envio do lote.

Ele me retorna o erro APPLICATION_ERROR ExchangeFaultDataExt conforme print abaixo:

Segue trace:

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

- <!--  Call Inbound Proxy

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">http content length 4251</Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

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

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.0</Trace>

<Trace level="2" type="T">Host = br01aixd4500:8000</Trace>

<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>

<Trace level="1" type="T">Remote address = 127.0.0.1</Trace>

<Trace level="1" type="T">Process ID: 12255350</Trace>

<Trace level="1" type="T">Work Process ID: 4</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

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

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

-->

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

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

-->

<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>

<Trace level="3" type="T">Getting type of XMB...</Trace>

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="2" type="T">XMB kind = SND_CENTR</Trace>

<Trace level="3" type="T">No start pipeline found (use current pipeline as start pipeline)</Trace>

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

<Trace level="3" type="T">No triggers found. OK.</Trace>

</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="3" type="T">system-ID = D45</Trace>

<Trace level="3" type="T">client = 200</Trace>

<Trace level="3" type="T">language = E</Trace>

<Trace level="3" type="T">user = PIAPPLUSER</Trace>

<Trace level="1" type="Timestamp">2012-06-05T17:35:08Z CET</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

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

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

-->

<Trace level="1" type="T">Message-GUID = 4FC8F888FDD10B80E1008000C0A8372C</Trace>

<Trace level="1" type="T">PLNAME = RECEIVER</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

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

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

-->

<Trace level="3" type="T">QOS = EO</Trace>

<Trace level="3" type="T">Message-GUID = 4FC8F888FDD10B80E1008000C0A8372C</Trace>

<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>

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

<Trace level="3" type="T">External PLID = RECEIVER</Trace>

<Trace level="3" type="T">Internal PLID = SAP_RECEIVER</Trace>

</Trace>

<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>

<Trace level="3" type="T">Generate prefixed queue name</Trace>

<Trace level="1" type="T">Queue name : XBTR0001</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="3" type="T">Setup qRFC Scheduler</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="3" type="T">Call qRFC .... MsgGuid = 4FC8F888FDD10B80E1008000C0A8372C</Trace>

<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>

<Trace level="3" type="T">Call qRFC .... Pipeline = RECEIVER</Trace>

<Trace level="3" type="T">OK.</Trace>

<Trace level="1" type="T">-----------------------------------------------------</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">-----------------------------------------------------</Trace>

<Trace level="3" type="T">Version number = 000</Trace>

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

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

-->

<Trace level="3" type="T">Persisting message Status = 001</Trace>

<Trace level="3" type="T">Message version 000</Trace>

<Trace level="3" type="T">Pipeline RECEIVER</Trace>

<Trace level="1" type="T">--start of determination of sender interface action</Trace>

<Trace level="1" type="T">select interface</Trace>

<Trace level="1" type="T">select interface namespace</Trace>

<Trace level="1" type="T">no interface action for sender found</Trace>

<Trace level="1" type="T">hence keep interface action INIT</Trace>

<Trace level="1" type="T">--end of determination of sender interface action</Trace>

<Trace level="1" type="T">--start of determination of receiver interface action</Trace>

<Trace level="1" type="T">loop 0000000001</Trace>

<Trace level="1" type="T">select interface BATCH_nfeRecepcaoLoteResponse_IB</Trace>

<Trace level="1" type="T">select interface namespace http://sap.com/xi/NFE/006</Trace>

<Trace level="1" type="T">end of loop 0000000001</Trace>

<Trace level="1" type="T">no interface action for sender or receiver found</Trace>

<Trace level="1" type="T">hence set interface action to DEL</Trace>

<Trace level="1" type="T">--end of determination of receiver interface action</Trace>

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

<Trace level="3" type="T">Trace object available again now. OK.</Trace>

<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>

<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>

<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>

<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>

</Trace>

<Trace level="1" type="T">Process ID: 12386426</Trace>

<Trace level="1" type="T">Work Process ID: 6</Trace>

<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>

<Trace level="2" type="T">Increment log sequence to 001</Trace>

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

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

-->

<Trace level="1" type="T">-----------------------------------------------------</Trace>

<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>

<Trace level="3" type="T">system-ID = D45</Trace>

<Trace level="3" type="T">client = 200</Trace>

<Trace level="3" type="T">language = E</Trace>

<Trace level="3" type="T">user = PIAPPLUSER</Trace>

<Trace level="1" type="Timestamp">2012-06-05T17:35:08Z CET</Trace>

<Trace level="1" type="T">-----------------------------------------------------</Trace>

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

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

-->

<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>

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

<Trace level="3" type="T">External PLID = RECEIVER</Trace>

<Trace level="3" type="T">Internal PLID = SAP_RECEIVER</Trace>

</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T">Pipeline attributes</Trace>

<Trace level="3" type="T">PID = SAP_RECEIVER</Trace>

<Trace level="3" type="T">ENABLE = 1</Trace>

<Trace level="3" type="T">TRACELEVEL = 0</Trace>

<Trace level="3" type="T">EXEMODE = A</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T" />

<Trace level="3" type="T">Pipeline elements</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>

<Trace level="3" type="T" />

<Trace level="1" type="Timestamp">2012-06-05T17:35:08Z CET Begin of pipeline processing PLSRVID = RECEIVER</Trace>

<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />

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

-->

<Trace level="1" type="Timestamp">2012-06-05T17:35:08Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_INBOUND_PROXY</Trace>

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

<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INBOUND_PROXY</Trace>

<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>

<Trace level="3" type="T">PLSRVTYPE =</Trace>

<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>

<Trace level="3" type="T">P_CLASS = CL_PROXY_FRAMEWORK_WS_XI</Trace>

<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>

<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>

<Trace level="3" type="T">FL_LOG =</Trace>

<Trace level="3" type="T">FL_DUMMY = 0</Trace>

<Trace level="3" type="T" />

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

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

-->

<Trace level="1" type="B" name="Inbound Framework" />

</Trace>

<Trace level="3" type="System_Error">Application-Error exception return from pipeline processing!</Trace>

<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>

<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>

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

<Trace level="3" type="T">Persisting message after plsrv call</Trace>

<Trace level="3" type="T">Message-Version = 001</Trace>

<Trace level="3" type="T">Message version 001</Trace>

<Trace level="3" type="T">Pipeline RECEIVER</Trace>

</Trace>

<Trace level="3" type="System_Error">Application-Error exception return from pipeline processing!</Trace>

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

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

-->

<Trace level="3" type="T">Persisting message Status = 017</Trace>

<Trace level="3" type="T">Message version 002</Trace>

<Trace level="3" type="T">Pipeline RECEIVER</Trace>

</SAP:Trace>

Podem me ajudar?

Status de Serviço está ok!

Obrigado!

[former_member182114 · Accepted solution]

Bom dia Thamir,

Qual o payload que estava sendo chamado no Call Inbound Proxy?

Atenciosamente, Fernando Da Rós

[Former Member · Accepted solution]

Olá Fernando, obrigado pelo retorno.

Segue:

<?xml version="1.0" encoding="utf-8" ?>

- <>  <nm:ExchangeFaultDataExt xmlns:nm="http://sap.com/xi/NFE/common" xmlns:prx="urn:sap.com:proxy:D45:/1SAI/TAS4E81729E31D9EA842F65:702">

<faultText>Batch ID not available 000000000000000</faultText>

</nm:ExchangeFaultDataExt>

Obrigado!

[former_member182114 · Accepted solution]

Esse é o erro... você está recebendo a resposta de um lote "000000000000000" que não existe no SAP NFE...

Pergunta: Como este lote 000000000000000 foi solicitado?

Verifique no payload da mensagem que chama o PI.

Dica: Comece novamente com outra NF-e / Lote, pode ser que alguma configuração que estava ausente já foi feita.

Atenciosamente, Fernando Da Ros

[Former Member · Accepted solution]

Olá Fernando, obrigado pelo retorno!

Solicitamos ao SD uma nota/lote do zero. Mesmo assim o erro persiste.

Aparece número de lote no ECC porém o lote fica parada no GRC.

Obrigado mais uma vez!

[former_member187533 · Accepted solution]

Estou com o mesmo problema. Já tentei gerar uma nova nota, porem o problema persiste.

No envio, o payload contem o número de lote correto, porem ele retorna com esta mensagem de problema no ID.

Obrigado!

[former_member182114 · Accepted solution]

Bom dia Lucas,

Tentem o refresh do cache (SXI_CACHE).

A configuração das interfaces foi toda refeita? Digo, sem aproveitar a do 1.0, deve-se rodar o wizard novamente como primeira vez.

Atenciosamente, Fernando Da Ros

[former_member187533 · Accepted solution]

Fernando,

Muito obrigado pela ajuda!

Vou fazer esse refresh no cache, sobre os cenários, uma dúvida. Mesmo tendo que recria-los, posso seguir a mesma idéia certo? Só que com os pacotes da solução 10.0 certo?

Vou apaga-los e recria-los novamente!

Muito obrigado!

[former_member182114 · Accepted solution]

Sim, o procedimento é o mesmo.

[Former Member · Accepted solution]

Bom dia pessoal,

Vocês ainda não resolveram isso ou já resolveram e simplesmente abandonaram a thread?

[Former Member · Accepted solution]

Senhores, pra deixar registrado na thread,

Me parece que é caso de falta de configuração das sequences (number ranges) para os números de lote. Entrando na SNRO, criei intervalos para os objetos /XNFE/* e tudo está funcionando.

Isso deveria ser atividade funcional? Caso afirmativo, não devia existir SPRO pra isso?

Um abraço!

Waldemar Roberti

[Former Member · Accepted solution]

Fernando, tudo bem?

O problema foi encontrado mas qual a solução para tal? Estou com o mesmo problema ocorrendo em um ambiente que acabou de ser atualizado para SP 17 do GRC (Content do PI está no 17 tambem), comparei o payload da BATCH e BATSR antes e depois da atualização do SP e está igual.

No aguardo, obrigado.

Danilo

[Former Member · Accepted solution]

Pessoal,

Problema resolvido aqui, limpei Cache no GRC e no PI e funcionou!!!

Abraços

[former_member227638]

Estamos passando pelo mesmo problema ao atualizar o GRC para a versão 10.

• Tentamos verificar os spk do PI e cr content do SLD, mas ambos estão no ultimo nível;
• Limpamos o cache;
• Recriamos o cenário BATCH_Webas_Outbound_batch;
• Reiniciamos o servidor;

Vocês conseguiram alguma solução para o caso?

A solução do Alessandro Silveira não se aplica ao nosso ambiente pois o campo dhRecbto ja estava com o tipo indicado por ele.

[former_member183069]

Dear please post in english then it will be usefull to every one

[former_member182114]

Bom dia karthikeyan,

Este fórum é de conteúdo em língua Portuguesa.

Participantes que não dominam a língua podem utilizar-se do google translator que ofecere um excelente suporte à tradução Português-Inglês-Português. Veja:

http://translate.googleusercontent.com/translate_c?hl=pt-BR&ie=UTF8&prev=_t&rurl=translate.google.co...

Grato pela compreensão.

Atenciosamente, Fernando Da Rós

[Former Member]

Fala galera, to tendo o mesmo problema com as notas do Cte.

Segue logs do GRC:

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

- <!--

 Call Inbound Proxy 

-->

- <SAP:Manifest wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

- <SAP:Payload xlink:href="cid:payload-4FE2327BE5B60085E1008000CC36BE42@sap.com">

<SAP:Name>MainDocument</SAP:Name>

<SAP:Description />

<SAP:Type>Application</SAP:Type>

</SAP:Payload>

</SAP:Manifest>

<?xml version="1.0" encoding="utf-8" ?>

- <n0:ExchangeFaultDataExt xmlns:n0="http://sap.com/xi/NFE/common">

<faultText>Element '{http://www.portalfiscal.inf.br/cte}cMunE</faultText>

</n0:ExchangeFaultDataExt>

percebi que no XML não existe o campo cMunE, apenas o cMunEnv.

any ideias?

Obrigado

[Former Member]

Conseguimos resolver o problema utilizando este procedimento sugerido pela SAP:

1. Use transaction SE80 to display the following Server Proxy

'CFB2B_procCTe_IB' in package /XNFE/IXIB2B.

2. Switch to tab 'External View'.

3. Navigate to field 'dhRecbto', located in Input

- protCTe - infProt.

4. Switch to Edit Mode.

5. Change the Attribute 'Techn. Type' from 'XSDDATETIME_Z' to 'STRG

STRING' for field 'dhRecbto'.

6. Press button 'Activate'.

[Former Member]

Legal registrar isso Alessandro,

Mas esse não era o problema original da thread... ou era?