BPE_ADAPTER : MESSAGE_NOT_USED

Hello,
Scenario: Async File-> SnynRFC- AsyncFile
In SXI_CACHE I see the return code as 99 and the error as bellow.

Warning: Send step: property exception for '3DSFF99434DS89f00dsDDD' is missing.
Error: Send Step: Fault message "4dfggfs454cdf5453435nd45nfdf533bg' is not defined.
I do have the fault message defined for the abstract interface for the send step and see this in BPM.
I tried to activate several times and the return code is still 99 and giving the above warning and error. After going through some of the SDN messages I tried to reimporting into the ID and still the return code is 99 with the same messages.
Do I need to recreate the configuration completely ?
thanks
Sunil

Hi,
Warning: Send step: property exception for '3DSFF99434DS89f00dsDDD' is missing.
Error: Send Step: Fault message "4dfggfs454cdf5453435nd45nfdf533bg' is not defined
This tells , somwhere some step properties are not given correctly.
In SXMB_MONI I do not see the PE at all. Only in SXI_CACHE I see the 99 error.
Mean to say, BPM is not at all Triggered ??? Once BPM is triggered then check the status in the SXI_CAHCE.
Hope you have done, Source->BPM Reciever Determination in the ID.
First check is BPM is triggered?
Thanks,
Moorthy

Similar Messages

BPE_ADAPTER MESSAGE_NOT_USED Message is not used by any processes

We need some help on BPM flow. We are at it for last 3 days without much progress. We are able to make sync call to same BAPIs and get data without any issue. However, with BPM we have this issue
I am creating the simplest integration scenario as
1. HTML/HTTP-->BPM (Async)
2. BPM-->R/3 (Sync)
3. BPM-->File (Async)
Created all required interfaces and mapping. I have some dummy mapping for first 2 cases. I am able to activate the integration scenario and Integration Process without any error. I am able to import it in integration directory successfully without any error. When I am executing the first async request from HTML client I am invariably end up with an error from sxmb_moni as
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message is not used by any processes</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The BPM is not getting invoked. Looking at the trace it shows that there is an error after creating BPE proxy for message as
<Trace level="3" type="T">created BPE proxy for message DE5FB5802F33D3F19373005056A12466</Trace>
</Trace>
</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 = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
What I have checked so far:
1. I have checked that the developer key is assigned to my user id
2. Used SWF_XI_CUSTOMIZING to make sure that all the process are green
3. Used sxi_cache to make sure that the BPM process has return code 0 and also reactivated it numerous times. Also checked activation log and no error there
4. Used SXMP_ADM_BPEAutomatic BPM Customizing to check all the entries are green
5. There are not any message in sxmb_moni_bpe for my interface shows no message
Input call has:
1. Sender Service: MFG_BPM_BusinessSystem
2. Sender Interface: MI_Outbound_Async
3. Quality Of Service: EO
4. Sender Name space: Name space
5. Input XML:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:BAPI_SALESORDER_GETLIST xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
 <CUSTOMER_NUMBER>0000001000</CUSTOMER_NUMBER>
 <DOCUMENT_DATE/>
 <DOCUMENT_DATE_TO/>
 <MATERIAL/>
 <MATERIAL_EVG>
 <MATERIAL_EXT/>
 <MATERIAL_VERS/>
 <MATERIAL_GUID/>
 </MATERIAL_EVG>
 <PURCHASE_ORDER/>
 <PURCHASE_ORDER_NUMBER/>
 <SALES_ORGANIZATION>1000</SALES_ORGANIZATION>
 <TRANSACTION_GROUP/>
 <SALES_ORDERS>
 <item>
 </item>
 </SALES_ORDERS>
</ns0:BAPI_SALESORDER_GETLIST>
Any clue, help pointer will be of great help. Just beats me, what is wrong!!
Version:
SAP R/3 ECC 6.0
XI 7.0

Hi,
Please check these threads where they have the same issue:
Message is not used by any processes
Error: Message is not used by any processes
Error: BPE_ADAPTER Message not used in any process
Message is not used by any processes
---Satish

BPM Error: BPE_ADAPTER MESSAGE_NOT_USED

Hi,
we have an issue in our XI production system, where message is not reaching BPM and its giving below error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We carried out following steps:
1. Did cache refresh using Tcode 'sxi_cache', IP object is giving return code as "99".
2. We deleted the Integration Process object from Integration directory and reimported the object from Integration Reporsitory again.
3. We re-imported the IR object from QA server again in Production, but it still didn't work. (It is working fine in QA environment).
4. We went through following SAP Note 901366 & 910437 (Both have been applied).
Can you please help us resolve this issue at the earliest.
Regards,
Ashish

Hi Orit,
We had this issue because workflow customizing object for use of xml object types was not activated in our system.
This issue was resolved using tcode 'SWF_XI_CUSTOMIZING', and activate 'Activate Use of XML Object Types'.
Hope this helps!!!
Regards,
Ashish

MESSAGE_NOT_USED - ERR in BPM multi mapping process

Hi Guys,
Can any solve this issue please,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have gone through all kind of prilimanary changes like
removed IP, reimported to ID
deleted IP and I did again from scrach (BPM)
no errors in BPM, activated, SXI_cache : Process return code shows 0, cache activated several times, server bounced.
Please your valuable inputs for this!!
Thanks
San

San,
A similar issue has been resolved here ... give it a try -
BPE_ADAPTER:MESSAGE_NOT_USED
When you double-click on Integration Process, you will get an option for Repeat Activation on the right-hand side header.
Hope this helps.
Regards,
Neetesh

BPE_ADAPTER error

Kindly help in this regards.. its a file to file Bpm collect message scenario
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

can any one help me out wat the error is... i cross checked my
message interfaces and recevr and interface determination all are mentioned rite... could u please help out...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>66CF66D6-077B-4ED2-0AC9-D44FEB6F67E9</SAP:MessageId>
<SAP:TimeSent>2009-03-12T11:55:35Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>BS_Bpm_file</SAP:Service>
<SAP:Interface namespace="http://capgemini/mumbai/upgrade">BpmPatternCollectIfToBeCollected</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BPMPatternCollectMessage</SAP:Service>
<SAP:Interface namespace="http://capgemini/mumbai/upgrade">BpmPatternCollectIfCollected</SAP:Interface>
<SAP:Mapping notRequired="X" />
</SAP:Receiver>
<SAP:Interface namespace="http://capgemini/mumbai/upgrade">BpmPatternCollectIfCollected</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2009-03-12T11:55:35Z" wasRead="false">
<SAP:Engine type="AE">af.xi1.inbomsap11</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>66CF66D6-077B-4ED2-0AC9-D44FEB6F67E9</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2009-03-12T11:55:36Z" wasRead="false">
<SAP:Engine type="IS">is.00.inbomsap11</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>66CF66D6-077B-4ED2-0AC9-D44FEB6F67E9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2009-03-12T11:55:37Z" wasRead="false">
<SAP:Engine type="PE" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">PE</SAP:Adapter>
<SAP:MessageId>66CF66D6-077B-4ED2-0AC9-D44FEB6F67E9</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>

BPE-Adapter Error (MESSAGE_NOT_USED)

Hi Suraj,
I've corrected su01 and my Return Code in SXI_CACHE is now 0,still i get the error.I've sent the error log below:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message is not used by any processes</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you help me fixing out this problem?
Regards,
Prashanth.

Hi Prashanth,
Make some dummmy changes in BPM and try activating it. After that check the return code in SXI_CACHE (whether it is 0 or not). If it is 0 then test your scenario, it should work.
go thru this link :
Message is not used by any processes
BPM Error
Regards
Suraj

MESSAGE_NOT_USED

Bom dia,
Fiz a configuração dos cenários NFE.
Ao mandar as notas, elas aparecem no monitor com status amarelo (processamento).
Na moni esta o erro:
BATSR_nfeRetRecepcao_OB
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Olhei na TCODE SWF_XI_CUSTOMIZING e não tem erros.
Re-importei os cenários
Ja vimos em algumas notas aqui no SDN sobre SXI_CACHE, onde o nosso status esta verde. Tambem ja reimportamos os cenarios no Design, pois aparentemente o Message Interface nao esta sendo reconhecido pela interface

Boa tarde Henrique,
A associação dos IPs estão corretas.
Integration Process
BATSR_nfe_RetRecepcao htt://sap.com/xi/NFE/005a SAP SLL-NFE 1.0
BATCH_nfe_RecepcaoLote htt://sap.com/xi/NFE/005a SAP SLL-NFE 1.0
CANCR_nfe_CancelamentoNF htt://sap.com/xi/NFE/005a SAP SLL-NFE 1.0
NFESC_NFeStatusCheckProcess htt://sap.com/xi/NFE/005a SAP SLL-NFE 1.0
SIGNC_SignCancNFeProcess htt://sap.com/xi/NFE/005a SAP SLL-NFE 1.0
SIGNN_SignNFeProcess htt://sap.com/xi/NFE/005a SAP SLL-NFE 1.0
SIGNS_SignInutNFe htt://sap.com/xi/NFE/005a SAP SLL-NFE 1.0
SKIPR_SkippingReguestProcess htt://sap.com/xi/NFE/005a SAP SLL-NFE 1.0
[]'s

Erro no processo de cancelamento/inutilização

Amigos,
Configurei os cenários de NFe e está ocorrendo um problema no PI que ainda não havia visto. Recebo a mensagem abaixo na SXMB_MONI:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Já refiz os cenários e ainda assim não funcionou. Alguém já passou por um caso semelhante?
Abraços,
Marcos

Bom dia Phil,
Sim, você deve pegar o XML no SXI_Monitor e pode usar a ferramenta de validação do site da Sefaz RS para validá-lo.
Validador de mensagens do projeto NF-e
Porém, de antemão verifique:
- Se a justificativa de cancelamento tem no mínimo 15 caracteres
- Se a justificativa de cancelamento não possue acentos ou caracteres especiais.
Atenciosamente, Fernando Da Ró

GRC NFe 2.0 20 - Serviço de assinatura digital não acessível

Senhores,
Encontrei diversos post sobre esse problema, porem nenhum específico para o meu problema.
Meu landscape é ECC 6.0 700 SP 22 (SAP_APPL 603 - SP 6 - SAPKH60306) -> GRC/PI SAP NetWeaver 7.0 (SLL-NFE - Release 100 - SP 0015/SAP_ABA - 700 SP 22).
Apliquei inumeras notas no ECC e a princípio não aparece nenhum erro na j1bnfe nem na sxi_monitor do PI. Porem no monitor web GRC aparece a mensagem: 20 - Serviço de assinatura digital não acessível.
Realizei testes na SM59 e todas as RFC comunicam sem problemas e na db97 estão apontados corretamente.
Gostaria de saber se pode ser problemas de SP do GRC ou alguma outra coisa.
Obrigado!

Henrique, muito obrigado pela atenção.
Acabei de aplicar a nota "0001498700 Problem on signing NF-e" e o problema mudou. Agora ja temos a mensagem no sxi_monitor e o erro no Monitor GRC ja é outro. Passa a ser "Problemas de processamento PI" e na mensagem do sxmb_moni conta a mensagem:
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Para a interface: SIGNN_SignNFe_OB. Vou tentar apagar e criar o cenário novamente, porem se souberes de alguma nota ou correção para isso, seria muito bom.
Sobre a atualização de SP, devido ao curtíssimo prazo do projeto (7 dias para atualizar 1.0 para 2.0) estamos tendando buscar outras soluções, como por exemplo aplicação de notas em separado, se tiveres uma lista das que eu vou precisar seria muito bom... Obrigado!

CC-e: Etapa não está em ordem

Olá pessoal,
Estamos implementando a CC-e, e realizamos todas as configurações no ECC, e estamos no SP20 do GRC.
No ECC a CC-e é criada normalmente e enviada ao GRC, porém a mesma fica no monitor GRC e não é enviada à SEFAZ...
Quando checamos a aba de "síntese de status" do monitor de evento da CC-e, a mesma fica com DUAS linhas conforme abaixo:
Status Atividade Ctg.proc. Descrição do status Texto info
Assinar evento Criação Etapa não está em ordem Em branco
Criar CC-e Criação Etapa em ordem
Quando checamos a aba de "Histórico", a mesma fica com TRÊS linhas conforme abaixo:
Atividade Ctg.proc. Descrição do status Texto info Data de execução Usuário Status
Assinar evento Criação Etapa não está em ordem SAP NetWeaver PI notifica erro ao assinar o evento. 13.12.2011 16:44 PISUPER Etapa não está em ordem
Assinar evento Criação Etapa em ordem Em Branco 13.12.2011 16:44 PISUPER Etapa em ordem
Criar CC-e Criação Etapa em ordem Evento do tipo 110110 para 31111220146676000367550010000658121905067763 é criado com o nº sequencial 01 13.12.2011 16:44 PISUPER Etapa em ordem
Na grid com informações gerais sobre a CC-e, as colunas que são preenchidas ficam descritas conforme abaixo:
Coluna Status global: incorreto
Coluna Zugriffsschlüssel: 31111220146676000367550010000658121905067763
Coluna Tipo de um evento: 110110
Coluna Nº sequencial de um evento: 1 (para todas as CC-es fica 1)
Coluna Momento da emissão: 13.12.2011 15:16
Coluna Momento do registro: 13.12.2011 15:16
Coluna Nº sequencial de um evento: 1
Coluna Region des Ausstellers: 31
Coluna Ausstellungsart: 1
Coluna Systemumgebung SEFAZ: 2
Coluna Nº ID fiscal (CNPJ): 20146676000367
Coluna Momento da emissão: 2011-12-13T15:16:39-02:00
Coluna Status: 02
Coluna Booleano: X
Coluna Registro da hora: 13.12.2011 17:16:52,2310000
Coluna Eventos: ctg.proc.: ISSUING
Coluna Eventos: etapa proc.: EVENTSIN
Coluna Status: 02
Coluna GUID: 00000000000000000000000000000000
Coluna Registro da hora: 13.12.2011 17:16:39,8000000
Coluna Registro da hora: *00.00.0000 00:00:00,000000
Coluna Tipo de um evento (texto): CC-e
Na SXI_MONITOR (SOAP-Header / Error), fica com erro conforme abaixo:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Na SXI_MONITOR (Payloads / MainDocument ( application/xml )), fica com erro conforme abaixo:
<?xml version="1.0" encoding="utf-8" ?>
- <n0:SignEvent xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:PID:/1SAI/TAS80E97F9FB00E4B4CED3E:701:2011/06/16" xmlns:n1="http://www.portalfiscal.inf.br/nfe" xmlns:n2="http://www.w3.org/2000/09/xmldsig#">
<n0:KeyStoreView>CERTIFICADO</n0:KeyStoreView>
<n0:KeyStoreEntry>CERTIFICADO</n0:KeyStoreEntry>
<n0:EventID>E125BA771517E9F19D6100155D001537</n0:EventID>
- <n1:evento versao="1.00">
- <n1:infEvento Id="ID1101103111122014667600036755001000065812190506776301">
<n1:cOrgao>31</n1:cOrgao>
<n1:tpAmb>2</n1:tpAmb>
<n1:CNPJ>20146676000367</n1:CNPJ>
<n1:chNFe>31111220146676000367550010000658121905067763</n1:chNFe>
<n1:dhEvento>2011-12-13T16:44:17-02:00</n1:dhEvento>
<n1:tpEvento>110110</n1:tpEvento>
<n1:nSeqEvento>1</n1:nSeqEvento>
<n1:verEvento>1.00</n1:verEvento>
- <n1:detEvento versao="1.00">
<n1:descEvento>Carta de Correcao</n1:descEvento>
<n1:xCorrecao>teste de criacao da carta de correcao eletronica</n1:xCorrecao>
<n1:xCondUso>A Carta de Correcao e disciplinada pelo paragrafo 1o-A do art. 7o do Convenio S/N, de 15 de dezembro de 1970 e pode ser utilizada para regularizacao de erro ocorrido na emissao de documento fiscal, desde que o erro nao esteja relacionado com: I - as variaveis que determinam o valor do imposto tais como: base de calculo, aliquota, diferenca de preco, quantidade, valor da operacao ou da prestacao; II - a correcao de dados cadastrais que implique mudanca do remetente ou do destinatario; III - a data de emissao ou de saida.</n1:xCondUso>
</n1:detEvento>
</n1:infEvento>
- <n2:Signature>
- <n2:SignedInfo>
<n2:CanonicalizationMethod Algorithm="" />
<n2:SignatureMethod Algorithm="" />
- <n2:Reference URI="">
<n2:Transforms />
<n2:DigestMethod Algorithm="" />
<n2:DigestValue />
</n2:Reference>
</n2:SignedInfo>
<n2:SignatureValue />
- <n2:KeyInfo>
- <n2:X509Data>
<n2:X509Certificate />
</n2:X509Data>
</n2:KeyInfo>
</n2:Signature>
</n1:evento>
</n0:SignEvent>
Alguém poderia nos auxiliar?
Obrigado e abraços.
Mateus.

Pessoal, resolvi editar e inserir a primeira postagem pois ficou desconfigurada... segue abaixo:
Estamos implementando a CC-e, e realizamos todas as configurações no ECC, e estamos no SP20 do GRC.
No ECC a CC-e é criada normalmente e enviada ao GRC, porém a mesma fica no monitor GRC e não é enviada à SEFAZ...
Quando checamos a aba de "síntese de status" do monitor de evento da CC-e, a mesma fica com DUAS linhas conforme abaixo:
>>>>>>> LINHA 1:
Status: Assinar evento
Atividade: Criação
Ctg.proc.: Etapa não está em ordem
>>>>>>> LINHA 2:
Status: Criar CC-e
Atividade: Criação
Ctg.proc.: Etapa em ordem
Quando checamos a aba de "Histórico", a mesma fica com TRÊS linhas conforme abaixo:
>>>>>>> LINHA 1:
Atividade: Assinar evento
Ctg.proc.: Criação
Descrição do status: Etapa não está em ordem
Texto info: SAP NetWeaver PI notifica erro ao assinar o evento.
Satus: Etapa não está em ordem
>>>>>>> LINHA 2:
Atividade: Assinar evento
Ctg.proc.: Criação
Descrição do status: Etapa em ordem
Texto info: Em Branco
Satus: Etapa em ordem
>>>>>>> LINHA 3:
Atividade: Criar CC-e
Ctg.proc.: Criação
Descrição do status: Etapa em ordem
Texto info: Evento do tipo 110110 para 31111220146676000367550010000658121905067763 é criado com o nº sequencial 01
Satus: Etapa em ordem
Na grid com informações gerais sobre a CC-e, as colunas que são preenchidas ficam descritas conforme abaixo:
Coluna Status global: incorreto
Coluna Zugriffsschlüssel: 31111220146676000367550010000658121905067763
Coluna Tipo de um evento: 110110
Coluna Nº sequencial de um evento: 1 (para todas as CC-es fica 1)
Coluna Momento da emissão: 13.12.2011 15:16
Coluna Momento do registro: 13.12.2011 15:16
Coluna Nº sequencial de um evento: 1
Coluna Region des Ausstellers: 31
Coluna Ausstellungsart: 1
Coluna Systemumgebung SEFAZ: 2
Coluna Nº ID fiscal (CNPJ): 20146676000367
Coluna Momento da emissão: 2011-12-13T15:16:39-02:00
Coluna Status: 02
Coluna Booleano: X
Coluna Registro da hora: 13.12.2011 17:16:52,2310000
Coluna Eventos: ctg.proc.: ISSUING
Coluna Eventos: etapa proc.: EVENTSIN
Coluna Status: 02
Coluna GUID: 00000000000000000000000000000000
Coluna Registro da hora: 13.12.2011 17:16:39,8000000
Coluna Registro da hora: *00.00.0000 00:00:00,000000
Coluna Tipo de um evento (texto): CC-e
Na SXI_MONITOR (SOAP-Header / Error), vejam algums descritivos:
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
Alguém poderia nos auxiliar?
Muito obrigado e abraços.
Mateus.

GRC NF-e 2.0 -Status Error 20 (Serviço de Assinatura Digital não Acessivel)

Boa tarde Srs,
Ontem tivemos uma falha no serviço de assinatura digital, conforme erro mencionado na descrição.
- Em RWB a seguinte mensagem de erro aparece:
Function LCR_GET_OWN_BUSINESS_SYSTEM failed (return code = 1)
- Qdo executava a função mencionada (SE37), não trazia nenhum dados preenchidos nos campos de valores;
- Constatei falhas executando um SLDCHECK:
Calling function LCR_GET_OWN_BUSINESS_SYSTEM
Retrieving data from the SLD server...
No corresponding business system found for system XIP client 100
- Constatei falhas de refresh na tcode SMICM, trazendo o mesmo erro mencionado:
LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM
- E o canal de comunicação de assinatura digital ficava inativo. Mesmo estando ativo no ID.
- Não gerava nenhum dump.
- Alguns erros de comunicação, apareceram no log de sistema (SM21).
Conseguimos resolver o problema efetuando um Cache Refresh Full, reiniciando o cluster J2ee Hard Shutdown com reinicio via tcode SMICM e, fazendo uma limpeza de buffer via /$sync.
Hoje pela manhã o erro voltou e novamente efetuamos o mesmo procedimento para resolvê-lo.
Nosso PI (NW04s), está com seguintes níveis:
SAP_ABA = 18
SAP_BASIS = 18
PI_BASIS = 2005_1_700 (SAPKIPYJ7I)
SLL-NFE = 17
Pesquisei algumas notas, na tentativa de resolver o problema de vez; Porém nenhuma delas nos atende:
Note 604321 - SLD: Ineffective table buffering for cache = Nota obsoleta
Note 1104341 - Termination in LCR_GET_OWN_BUSINESS_SYSTEM = Nota menciona nivel SP14 (SAP_BASIS )
Note 1176971 - Deadlock on the database for SLD access = Nota menciona nivel SP17 (SAP_BASIS)
Note 1088659 - XI business system cannot be determined = Nota menciona nivel SP14 (SAP_BASIS )
Perguntas:
Alguém já passou pelo problema e poderia compartilhar a solução?
Há alguma nota conhecida para resolver esta questão, de acordo com nosso nivel de SP que temos?
O erro pode estar atrelado à infra (tráfego de dados na rede)?
Toda ajuda, será bem vinda!
Grato,
Ricardo

Henrique, muito obrigado pela atenção.
Acabei de aplicar a nota "0001498700 Problem on signing NF-e" e o problema mudou. Agora ja temos a mensagem no sxi_monitor e o erro no Monitor GRC ja é outro. Passa a ser "Problemas de processamento PI" e na mensagem do sxmb_moni conta a mensagem:
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Para a interface: SIGNN_SignNFe_OB. Vou tentar apagar e criar o cenário novamente, porem se souberes de alguma nota ou correção para isso, seria muito bom.
Sobre a atualização de SP, devido ao curtíssimo prazo do projeto (7 dias para atualizar 1.0 para 2.0) estamos tendando buscar outras soluções, como por exemplo aplicação de notas em separado, se tiveres uma lista das que eu vou precisar seria muito bom... Obrigado!

Error: Message interface is not used by this process Netweaver PI 7.0

Hi All,
I am receiving this error in file to idoc scenario. The file is being picked up by communication channel. Then through an interface mapping IM_MET_ROUTE is being forwarded to a BPM MET_FILE_ROUTE. The MET_FILE_ROUTE forwards it to different BPM depending on file type. whenever I am posting a file it is not reaching IM_MET_ROUTE and giving an error as shown below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please suggest any solution to remove the error.

Hi All,
Thanks a lot Vikrant for your suggestion. The error is resolved. This was not a configuration problem. This was a design problem. Initially I also looked for configuration changes but that was correct hence I came to conclusion that this might be a design isuue.
These are the steps that we should follow to resolve the errors
1. First Check your configuration again and again with test tool and payload to find where exactly your configuration is failing.
2. The above step will not be successful since we are already receiving the error.
3. The above test will fail in interface determination step.
4. Please go through the interface determination in Integration repository(PI 7.0).
5. Check whether all interface mapping,source and target message interface are proper or not.
6. if receiver or sender of message is an BPM please look into their receiver and sender element message type.This must match with the one specified in Interface mapping defined within Integration directory( in the interface deterination step).
In my case the sixth step above was the solution.

File To SOAP

Hi,
I am trying out a scenario from file<>BPM<>SOAP.
In the Call Adapter step I am getting the following error message:

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message is not used by any processes</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The Message is successfully reaching BPM but then the error occurs.
Please help me in this regards.
Thanks,
Abhishek.

Hi,
check these
1. Go to Transaction: SXI_CACHE and check the return code for your intergration process, it must be 0.
Might solve your issue
2. In MONI click on PE (you will find this when you scroll towards right). Now navigate like this Goto ---> Graphical workflow log. Check in which step there is a error (it will be in red colour lines).
3.Can u check whether the interface used in Sender agreement is the same as the interface used in Receiver Determination, whose receiver is BPM?
4.Check the receiver determination for file to BPM. The file message that enters the BPM i think is not able to find the receiver.
Try one more things. In your BPM, try a f7 and see if there is any syntax errors.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

BPM : Message interface is not used by this process

Hi,
In BPM : to pass the message facing error as below.
Messages not reflecting in BPM monitor.
I have configured Recveiver - transformation - sender in BPM.
In recvier in BPM is configured with Abstract Type as same in the message mapping.
Is there any thing i am missing?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have refered links but not able to get the clue for this error as its from the Call adapter.
error: Message interface is not used by this process Netweaver PI 7.0
BPE_ADAPTER: MESSAGE_NOT_USED
Regards,

Hi,
I just saw your IP design and from this I can see that you have message mapping between Sender(as in Outbound interface MIOASY) and abstract interface (as in MIAASY) and then in that you have used transformation step to utilise Interface mapping which is between same abstract interface which is not required at all as message type for both the interfaces is same. For me, what your configuration would be is
1. Sender agreement to fetch the message from outbound interface(MIOASY) utilising communication channel with whatever adapter you have used
2. Receiver Determination with Sender and sender interface as MIOASY while receiver as IP(Integration process)
3. Interface determination between
 a. Sender and Outbound interface and Abstract interface with interface mapping IM_Sender
 b. IP as sender with abstract interface MIAASY and receiver interface MIIASY with no interface mapping being used as it must be of same type as receiver interface is
4. Receiver agreement with MIIASY being used as receiver interface and communication channel utlililsed to convert it into receiver format.
If I am assuming it correct then if you see then inside BPM we are not using receiver interface MIIASY which is why I feel this error is coming.
However, if you design it something like this then I feel the error would get resolved
Design
1. Make one abstract interface (MIAASY_Sen) of same type as sender, and create another abstract interface (MIAASY_Rec) of same type as your receiver message type
2. Create message mapping between sender message type and receiver message type, Interface mapping IM_ABS - (MM_ABS_ABS) between sender abstract interface (MIAASY_Sen) and receiver abstract interface (MIAASY_Rec)
3. BPM should be something like this
 Container:*
rec Abstract Interface MIAASY_Sen
send Abstract Interface MIAASY_Rec
Receiver (rec) - Transformation (IM_ABS) - sender (send)
Configuration
1. Sender agreement to fetch the message from outbound interface(MIOASY) utilising communication channel with whatever adapter you have used
2. Receiver Determination with Sender and sender interface as MIOASY while receiver as IP(Integration process)
3. Interface determination between
 a. Sender,Outbound interface MIOASY and Abstract interface MIAASY_Sen with no interface mapping
 b. IP as sender with abstract interface MIAASY_Rec and receiver interface MIIASY with no interface mapping being used as it is of same type as receiver interface is
4. Receiver agreement with MIIASY being used as receiver interface and communication channel utlililsed to convert it into receiver format.
Let me know if it works.
Regards,
Amit

Message is not used by any processes

Hi,
I've made a BPM and in sxmb_moni I get this:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message is not used by any processes</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I check my return code in sxi_cache and it's not 0 after activating.
How could I resolve this error?
Thanks in advance,
Samantha.

Hi,
I don't understand "Is the BPM instance being created in the first place?". I've created the BPM for the first time, I don't know if you refer to this.
When I click on PE, I get: "the action is not valid for the selected message", so I can do nothing.
I think my user has developper key, although I'm going to make sure of it.
Thanks,
Samantha.
Message was edited by:
Samantha Núñez

BPE_ADAPTER : MESSAGE_NOT_USED

Similar Messages

Maybe you are looking for