SAP R/3 - XI Triggering

HI All,
We want to propose a technical solution to our client to push data from SAP R/3 to XI on realtime basis so that we can synchronize our local oracle database with the same data [SAP->XI->Database]. i.e whenever ever SAP Creates, Deletes or Updates a process order , It has to send the same data into XI and XI will then send it to Oracle through JDBC.
One solution is to use user exits in SAP.
but i dont know how to map the created PO data with the XI mapping(written in XI). I mean how i can send that PO data to XI and how to map that data with the specific scenario of XI which i have written in XI??? What code i need to write in user exit?
If anyone of you knows how to implement this SAP, please share.
Thanks in advance!!!

Hi Sumit,
data transfer from SAP to an external system is very simple using IDOCs,
YOu must configure the sap system in such a way that it triggers an IDOC that would go to the XI system, whenever a business document like a PO or a SO is created. In XI, you can recieve the idoc in xml format, which can be mapped to the structure and format that is acceptable to the oracle database(You have to use a JDBC adapter).
Regards,
Ravi

Similar Messages

Error occures while Sap R/3 sytem triggers XI message (using proxy class)

Error occures while Sap R/3 sytem triggers XI message (using proxy class)
1- I prepared message in XI side
2- I used sproxy transaction in R/3 side and generate proxy class
3- I used necessary methods in Abap program in R/3 side
4- Somethimes, message does not work and generate error like below
What must I do to solve this problem. Thanks
Error message (Reported in SXMB_MONI in Sap R/3 side)<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="112" p2="HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim Senden der Daten." p3="" p4="">HTTP.HTTP_CLIENT_SEND_FAILED</SAP:Code>
<SAP:Text language="TR">Error during http send: Error code: 112 Error text: HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim Senden der Daten.</SAP:Text>
</SAP:ErrorHeader>

Hi,
Check thiss
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Error no 2
Regards
Aashish Sinha
PS : Reward points if helpful

SAP workflow -SAP error WL210 -Error triggering default method for object &

Hi Experts,
User is encountered with the error message "Error triggering default method for object &" when he is performing approval action in SES workitem .
Could you please advise me how to avoid this issue.
Thanks in advance for your valuable help.
Rajani
Edited by: Rajani SAPABAP on Sep 13, 2011 4:50 PM

Hi Rajani,
I think that it's an authorization issue.
Please check if u find which authorization object is violated in SU53.
Regards,
Asit

Replacing customer statement form (T CodeF.27)SAP script with Smartform.

I have a requirement to automate sending customer statement form which is triggered through T-code: F.27. For this we are trying to replace the SAP script which is triggered from program RFKORD11 with Smartform. We have tried copy the program RFKORD11 to a custom one which assigned to the correspondance type in t-code OB78 and do the modifications, but we could not do so as we are not authorized to copy the program. Can anyone help us in acheiving this functionality. BR, Karthik G.

Re your question A:
F140_CUS_STAT_01 and F140_CUS_STAT_02 are SAP standard forms for customer statement. You can use either one but usually you will create your own (by copying) to add company logo and name, etc.
If you use program RFKORD11 for customer statement, you specify the form to be used in the "Correspondence" field.

Empty data from SAP

Hello,
I am using RFC_IDOC_INBOUND_ASYNCHRONOUS (BAPI OTD) in JCAPS5.1 to recieve IDOC ftrom SAP ECC6
in my JCD, i am using the following code:-
byte[] b = input.getIDOC_INBOUND_ASYNCHRONOUS().marshal();
String s1 = new String( b );
logger.info("***s1="+s1);
FileClient_1.setText( s1 );
FileClient_1.write();
here, I am getting blank data from IDOC.
ie:- when SAP sends IDOC, JCD triggered, but getting no data.
I have set all other configurations etc in eWay & environment.
Please, let me know, the solution of this problem.

how big is b.length ?
and are you shure you are getting an idoc from SAP?
are there any errors when u turn on excessive SAP logging in ICAN/CAPS?
regards chris

Help on creating Triggers on POR1

Hi,
I have a trigger on POR1 table, which updates a UDF field when Insert/Update is done on POR1 lines.
If PO has a single line, it works great.
But, if there is more than one line, I'm getting the error message : 'Invalid Cursor' while trying to update PO.
I have stripped down the trigger, so that it is in its simplest form.
Still I'm getting the invalid cursor error.
Simplest form of Trigger:
Create Trigger AIT_FWA_POR ON POR1
AFTER INSERT
AS
Begin
Update POR1 Set U_ShipCost = '10'
FROM POR1,Inserted where POR1.DocEntry = Inserted.DocEntry
End
If I see what happens in SQL profiler, it appears that SAP is deleting the POR1 rows (and reinserts?).
Please let me know how I can fix it, or more details about the internal functionality.
Your valuable inputs in fixing the problem will be highly appreciated.
Thanks in advance.
Regards,
Geetha

Hi Geetha,
Unfortunately, SAP do not support triggers on their tables and do not support updating UDFs directly through SQL on system tables so I can't offer a solution for this.
For a solution that fits within SAP's rules, I'd recommend you have an addon that traps the event of the user clicking on the Add/Update button on the purchase order screen and then populate your UDF value through the UI API before the document is added.
Kind Regards,
Owen

Triggering SRM workflow from a web-based form (HTML)

I am a beginner in SAP, please bear with me.
I have created an online data entry form using html to populate a table in a non-SAP database. I am able to call this form in SAP EP using URL iView.
I want some help on triggering an SRM workflow from this form.
Thanks.

Hi Vadim,
I would like to explain the scenario:
1.The form would reside in the SAP Enterprise portal
2.When the form is completed and the "submit" button is clicked, I expect a workflow in SAP SRM to be triggered.
3.The workflow is a developed three-step approval workflow. It was developed using the Hierarchical Approval workflow wizard.
Questions:
1. How can the workflow be triggered when the submit button is clicked?
2. How can the data from the Form be integrated into the workflow and vice versa?

NFE Produção - Código Status 204 Rejeição

Olá, Boa tarde!
Estamos com uma NFE da Produção parada, pois não estamos conseguindo atualizar o status dela.
No monitor de GRC a NFE aparece da seguinte forma:
Status NFE (bolinha vermelha): 05 resultado recebido
Status de Erro: 90 erro de sistema PI
Código Status: 204 Rejeição: Duplicidade NFE
A opção "Consulta do Status" está disponível, porém já tentamos várias vezes, aparece a mensagem: O processo de consulta status NFE foi inicializado. Atualizar a exibição NFE.
Atualizamos a página, porém não muda nenhum status.
No monitor J1BNFE a NFE está aguardando o retorno do GRC.
Não sei se tem algo a ver, mas recentemente fizemos a atualização da Versão para 2.0.
Antes o procedimento funcionava normal... agora as NFES estão paradas...
Aguardo comentários.
Obrigada.
Adriana

Bom dia,
Estou com esse mesmo erro, e não sei como resolver...
Ao clicar em consultar status(Monitor GRC) da NFE em questão, o status não é atualizado(consultamos no SEFAZ e a NFe Está aprovada)..
Verifiquei as msg na MONI e temos uma com o ACK NEG, porém desconheço o erro...segue os xml que consegui verificar na mensagem:
XML INBOUND:
<?xml version="1.0" encoding="utf-8" ?>
- <n0:nfeConsultaNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:PIP:/1SAI/TASB4840BC26BF382F75BE8:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
<n0:cUF>41</n0:cUF>
<n0:tpEmis>1</n0:tpEmis>
<n0:tpAmb>1</n0:tpAmb>
<n0:type>1</n0:type>
<n0:versNum>001</n0:versNum>
<n0:mode>I</n0:mode>
- <n0:nfeDadosMsg>
- <n1:consSitNFe versao="2.00">
<n1:tpAmb>1</n1:tpAmb>
<n1:xServ>CONSULTAR</n1:xServ>
<n1:chNFe>41110300606549000124550000000231711903353574</n1:chNFe>
</n1:consSitNFe>
</n0:nfeDadosMsg>
</n0:nfeConsultaNF2>
XML RESPONSE:
<?xml version="1.0" encoding="utf-8" ?>
- <n0:nfeConsultaNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:PIP:/1SAI/TASB4840BC26BF382F75BE8:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
<n0:cUF>41</n0:cUF>
<n0:tpEmis>1</n0:tpEmis>
<n0:tpAmb>1</n0:tpAmb>
<n0:type>1</n0:type>
<n0:versNum>001</n0:versNum>
<n0:mode>I</n0:mode>
- <n0:nfeDadosMsg>
- <n1:consSitNFe versao="2.00">
<n1:tpAmb>1</n1:tpAmb>
<n1:xServ>CONSULTAR</n1:xServ>
<n1:chNFe>41110300606549000124550000000231711903353574</n1:chNFe>
</n1:consSitNFe>
</n0:nfeDadosMsg>
</n0:nfeConsultaNF2>
XML ACK 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">NEGATIVE_ACKNOWLEDGEMENT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Negative acknowledgment triggered by a process</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Alguém teria alguma dica?
Edited by: João Luis da Silva Dovigo on Mar 16, 2011 6:20 PM

Assinatura de uma NFe

Olá...
Estamos tentando enviar uma NFe, mas recebo o seguinte em SIGNN_SignNFe_OB no sxmb_monitor:
<?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">NEGATIVE_ACKNOWLEDGEMENT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Negative acknowledgment triggered by a process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
E na resposta de SIGNN_SignNFe_SYNC:
<?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>Application</SAP:Category>
<SAP:Code area="MAPPING">STREAM_TRANSFORMATION_EX</SAP:Code>
<SAP:P1>sap/com/xi/nfe/map/SIGN_SignNFeCancInutConverter</SAP:P1>
<SAP:P2>Exception in Java mapping occured while parsing t~</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Java mapping of application triggered an exception</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Isso ocorreu em apenas uma nota...
Estou tentando achar algum problema de parse, nos XMLs, mas não identifiquei nada ainda.
Obrigado.

Olá.
O problema é o da mensagem acima... o XML veio com uma informação que o GRC não conseguiu fazer o parse... daí não consegue assinar.
Por exemplo, a NF possui alguns itens, mas o total da NF fica 0,00 no GRC.
Mas no ERP, na j1bnfe, ela está em processamento.
Daí vem a dúvida...
Ela não pode ser reprocessada, por ter problemas no XML, preciso devolver algo ao ERP para que saia do status de processamento, e assim ela possa ser corrigida, e reenviada...
Basicamente é isso que eu imagino como solução.
Obrigado.

Erro no envio de Lote com NF-e em Contingência (FS) para o Paraná

Experts, bom dia.
Devido à entrada em contingência em modo SCAN na data de ontem pelo Estado do Paraná, emitimos algumas NF-e's em Contingência, porém optamos por não emitir em SCAN, mas sim em Formulário de Segurança (FS).
Com isso, as notas que foram emitidas no momento da "queda" do SEFAZ PR ficaram "travadas" com engrenagem na J1BNFE. Comutamos estas Notas para poder emitir novas notas em Contingência. Assim que o SEFAZ PR voltou, resolvemos tirar a Contingência no ECC e enviar as NF-e's emitidas em FS.
Estas Notas (FS) foram enviadas corretamente ao GRC, que montou um Lote e tentou enviar ao SEFAZ PR pelo cenário BATCH. Porém ocorreu erro neste Lote (36-Erro de Sistema PI). Verifiquei na MONI e somente ocorre erro no Acknowledgement do BATCH:
<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">NEGATIVE_ACKNOWLEDGEMENT</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage>
<SAP:Stack>Negative acknowledgment triggered by a process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Já tentei reenviar este Lote de FS diversas vezes e volta a ocorrer erro de ACK. As Notas emitidas em modo NORMAL para o PR estão sendo aprovadas normalmente.
Alguém já passou por esta situação? Ou tem idéia do que pode estar ocorrendo?
Desde já agradeço.
Pedro Baroni

Pessoal, o erro acima ocorreu devido ao SEFAZ do PARANÁ ter respondido o Servico de entrega de Lote (BATCH) sem o campo obrigatório DHRecbto:
<?xml version="1.0" encoding="UTF-8" ?>
- <nfeRecepcaoLoteResponse2 xmlns="http://sap.com/xi/NFE/006">
- <nfeRecepcaoLote2Result>
- <retEnviNFe xmlns="http://www.portalfiscal.inf.br/nfe" versao="2.00">
<tpAmb>1</tpAmb>
<verAplic>PR-v2_4_5</verAplic>
<cStat>225</cStat>
<xMotivo>Falha no Schema XML do lote de NFe. org.xml.sax.SAXParseException: cvc-pattern-valid: Value 'RSIDU77' is not facet-valid with respect to pattern '[A-Z]{3}[0-9]{4}' for type '#AnonType_placaTVeiculo'.</xMotivo>
<cUF>41</cUF>
</retEnviNFe>
</nfeRecepcaoLote2Result>
</nfeRecepcaoLoteResponse2>
Devido a isto a mensagem de erro não foi gravada no Lote e não apareceu no Monitor do GRC.
Fernando / Henrique, neste caso é necessário entrar em contato com o SEFAZ PR ou pode haver algum tratamento no SAP?
Abs.

GRC: Negative ack; PI: End tag 'enviNFe' does not match the start tag 'NFe'

Bom dia SAP Boosters!
Como muita gente estou aqui brigando com o GRC NFe. Esse forum tem resolvido meus problemas, até agora. Por isso inicio um novo tópico pois estou tendo o seguite problema que nao encontrei resposta:
O grc e o pi estao em servidores separados. Do lado do grc, na sxmb_moni mostra para a interface BATCH_nfeRecepcaoLote_OB erro no acknowledgement status. abrindo o item error do ack msg id aparece:
<SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">NEGATIVE_ACKNOWLEDGEMENT</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage>
<SAP:Stack>Negative acknowledgment triggered by a process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
No lado do PI, ao consultar esta interface e abrir o payload do item Request Message Mapping, aparece a mensagem de erro: End tag 'n0:enviNFe' does not match the start tag 'NFe'. e todo o xml fica em uma linha só.
Voltei entao no xml do sender e de fato encontrei a tag NFe, onde deveria constar os dados das notas fiscais, sendo aberta mas nao sendo fechada, e sem dados, desse jeito.
<?xml version="1.0" encoding="utf-8" ?>
- <n0:nfeRecepcaoLote2 xmlns:n0="http://sap.com/xi/NFE/006">
<n0:cUF>35</n0:cUF>
<n0:tpEmis>1</n0:tpEmis>
<n0:tpAmb>2</n0:tpAmb>
- <n0:nfeDadosMsg>
- <n0:enviNFe versao="2.00" xmlns:n0="http://www.portalfiscal.inf.br/nfe">
<n0:idLote>000000000000025</n0:idLote>
<n0:NFe asx:root="" xmlns:asx="http://www.sap.com/abapxml"></n0:NFe>
</n0:enviNFe>
</n0:nfeDadosMsg>
</n0:nfeRecepcaoLote2>
Alguém já viu esse bug? estou com grc 10 e SP 08 e das notas que sairam depois nenhuma fala disso.
Obrigado.

Fiz um teste que parou de dar erro de acknowledgement e chegou a enviar o lote para a sefaz, que retornou erro de schema porque o xml continua vazio:
Na interface determination gerada quando criei o cenário NFE_BATCH_WebAS_Outbound_Batch, a que contém a interface BATCH_nfeRecepcaoLote_OB, tirei o operation mapping BATCH_nfeRecepcaoLote2_TO_nfeRecepcaoLote2. Embora não seja mais retornada a mensagem de erro na tag, o payload continua no mesmo formato postado acima. Entao coloquei de volta.
Bem, pesquisando vi que a função que gera o xml é a /XNFE/006_SIGN_NFE_OUT. As notas aparecem como assinadas no monitor do grc, mas vou ter que ver entao como esta ocorrendo a geraçao do xml por esta funçao, certo?

NEGATIVE_ACKNOWLEDGEMENT

Pessoal, boa tarde,
O GRC funcioava normalmente e derepente parou de funcionar somente para MG no senario de LOTE, no monitor o Status de MG está OK, sendo que não fiz nenhuma alteração.
Estou com o seguiente erro,
Quando está sendo executado o Senario -(BATCH_WebAS_Outbound_Batch ) está me gerando a seguinte msg
<SAP:Code area="BPE_ADAPTER">NEGATIVE_ACKNOWLEDGEMENT</SAP:Code>
<SAP:Stack>Negative acknowledgment triggered by a process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Verifiquei algumas treads aqui e fiz a veriicação nos dois ambientes tanto PI tanto GRC e me aparece a mesma msg.
Debugando o Programa /XNFE/PROCESS_REPORTS vi que ele me dá uma msg 085 e depois ele muda para 36 conforme o Henrique mensionou que ele faz isso para podermos reenviar o LOTE com erro.
Esse erro acontece comigo sempre quando gero uma nota para MG ou tento Reenviar o LOTE com erro.
não sei mais o que fazer , e estou com esse erro a 3 dias.
alguem pode me ajudar???
abraços

Obtive o seguinte retorno da SEFAZ MG:
Prezado Bernardo,
Informamos que a versão 4.0.0 do Manual de Integração (acessado através do link http://www.nfe.fazenda.gov.br/portal/integracao.aspx ) foi publicada em 21/09/2009 (Ato Cotepe nº 39, de 19/11/2009) e que tem sua vigência em homologação para janeiro de 2010 (conforme pág. 3 do referido Manual).
Todos os contribuintes deverão se adaptar à nova versão do manual no ambiente de homologação.
Informações sobre a nova versão de homologação, para adaptação de aplicativos desenvolvidos por terceiros, podem ser observadas no referido Manual.
Atenciosamente,
......etc.
Lí a página 3 do referido Manual (versão 4.0.0) e não consta data de vigência de homologação. Apenas produção.
Na versão 4.0.1 consta a data de vigência de homologação: Janeiro/2010.
Independente do problema da SEFAZ MG, deveriamos estar na versão nova?
Na mesma página tem a seguinte linha: Data final de vigência do PL_005d 30/09/2010
Isso vale para Homologação tambem?
At.,
Bernardo Tavares Braga
Edited by: BERNARDO TAVARES BRAGA on Feb 5, 2010 12:15 PM

FI Clearing for the Account Receivable document

Hi All,
I am having issue in the clearing document, the AR document open line item does not gets cleared.
Scenario goes likes this.
SAP A System posts the AR document to Central SAP System and AR Document gets created with same number range.
When the customer/vendor payments comes in form of wire/check, user goes to F-32/F-28/F-04 and posts the payment for that particular AR document. After posting, Clearing Document gets created and the AR Open Line items are cleared and same gets updated in BSAD/BSAK and BSEG i.e. Clearing Document field is updated. Once the clearing document is created in Central SAP System, I am triggering the IDOC to post in SAP A System but in the IDoc only the Clearing Document information are populated. When the same clearing document gets created in the SAP A system, it does not clears the AR Document which i sent across. But only new entry is created in BSEG table and AR documents shows still as Open Line items. Here only I am finding the disconnect. Could you please let me what configuration needs to be done so that they have link. I figure there automatic clearing done based on customers/vendors/gl accounts using the Tcode - F.13 But could find the link between the clearing document and AR Account.
Looking forward for your response.
Thank you,
Regards,
Dinesh.

any update on this ?

Purchase Order Response in SRM from R/3 through XI

Hello friends,
While sending Purchase Order Response from R/3 to SRm through XI Iam getting this error in SXMB_MONI of XI and also in SRM:
<?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>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><?xml version="1.0" encoding="utf-8"?><nr1:StandardMessageFault xmlns:nr1="http://sap.com/xi/SRM/Basis/Global"><standard><faultText>An error occured within an XI interface: Exception occurredE:BBP_PD:069 -Product data could not be intepreted E:BS:013 -System status INCM is active (Purchase Order Response 1000000037) Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</faultText></standard></nr1:StandardMessageFault></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SRM/Basis/Global">StandardMessageFault</SAP:ApplicationFaultMessage>
<SAP:Stack>The application triggered an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can anyone please help me out in this...........
Thanks in Advance...

Dear Friends,
I am SAP MM Certified Consultant & did my training for MM Module from Siemens ( Sapient College )& paid 2.5 lac for that and Since then I am working as a SAP MM consultant in an MNC since past 2 years, done 2 implementations and had a functional experience of 4 years in purchasing .
Had work for MNCs only & having good expertise in Domain area .Total Experience 5 years out of that 2 years SAP MM experience .
Dear all can you tell me what should i do so as to make a successful career in SRM.? How long should i stay in MM and what should I learn besides MM.I have already started working on SRM .
I wish to do SRM training again from Siemens but this point of time , I dont have enough money to do SRM training from Siemens . Could anyone suggest , where I can learn SRM in Bangalore & get trained in this New thing and do i need some programming knowledge in it.
Could anybody send me some SRM documentation on my mail id [email protected]
Thanks in advance.
Regards,
Savita Munshi

Conversion customer to Business partner: R/3 -- XI -- R/3

Dears,
For the implementation of Credit Management, we needed following setup:
1. Customer data is sent to XI by IDOC
2. The IDOC is mapped to a Business partner in XI
3. The business partner is sent back to the R/3 system with the ABAP proxy.
SXMB_MONI in XI gives a message that everything is correct.
SXMB_MONI in the R/3 system gives an application error with following trace:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<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="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="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<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="1" type="T">system-ID = SBX</Trace>
<Trace level="1" type="T">client = 111</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BWETNDC2</Trace>
<Trace level="1" type="Timestamp">2008-02-12T15:19:54Z 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 = 47B0345957F4B4B8E1008001AC150D90</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="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="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0007</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0007</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler 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="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 016</Trace>
<Trace level="3" type="T">Message version 004</Trace>
<Trace level="3" type="T">Pipeline RECEIVER</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">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<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 = SBX</Trace>
<Trace level="3" type="T">client = 111</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = BWETNDC</Trace>
<Trace level="1" type="Timestamp">2008-02-12T15:25:47Z 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">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-02-12T15:25:47Z CET Begin of pipeline processing PLSRVID = RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
<Trace level="1" type="Timestamp">2008-02-12T15:25:47Z 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</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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config</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 005</Trace>
<Trace level="3" type="T">Pipeline RECEIVER</Trace>
</SAP:Trace>
Any idea what the problem can be?
Thanks
Nicolas

Hi Agasthuri,
Thanks for your reply, but it didn't get me much further
1. There are no queues in SMQ2
2. All necessary services are activated in SICF
3. The HTTP connection works (returns "Empty HTTP request received" )
Any more idea's?
Maybe this can help:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/ABA">ABABusinessPartnerFault</SAP:ApplicationFaultMessage>
<SAP:Stack>The application triggered an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

SAP R/3 - XI Triggering

Similar Messages

Maybe you are looking for