RFC(ABAP Proxy)-------XI-------- FILE Asynch

Hi All,
Good evening.
Please let me clear one thing, the message automatically comes into XI when executing proxy at R/3 side? or we have to send from RWB by using the path
component monitoring-->Proxyruntime----->sendmessage
there we paste the message from SXMB_MONI of R/3?
Please clarify my doubt ASAP.
Thanks & Regards,
Nagarjuna.

Hi
You can test the scenario from SXMB_Moni of R/3.
Or you can call the execute_synchronous method and the whole scenario will work fine.
Please refer below scenarios
File to R/3 via ABAP Proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - FCC
ABAP Proxy Runtime
http://help.sap.com/saphelp_nw04s/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
Setting Up Point-to-Point Connections with proxy
http://help.sap.com/saphelp_nw04s/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/frameset.htm
Reliable Messaging EOIO in ABAP Proxies
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3dfac358-0d01-0010-5598-d4900e81a30c
Thanks
Swarup

Similar Messages

Problem with Configuration in Production ( ABAP Proxy - XI - FILE)

Hi All,
I have a ABAP Proxy -> XI -> FILE scenario wich is working perfectly in DEV and QAS environment.
When the person responsible for transporting tried to transport the objects in QAS to PRD, the following error happened:
Direction of communication channel |BS_MA_FileServer_PRD | CC_File_PedidosServ_MA_FileServer_IA is incorrect.
Correct the direction or choose another communication channel
BS_MA_FileServer_PRD - Business System (FILE)
CC_File_PedidosServ_MA_FileServer_IA - My FILE Communication Channel
This was what the Basis person sent to me. I don't have access to know exactly what happened. And I really don't know what could be wrong or if maybe a component was created wrongly in Production.
Hope you can help.
Points will be given.
tks.. Daniela

You have mentioned FILE is on the receiving side and ABAP proxy is on sender side.
But the error pasted by you clearly shows syntax of a Sender Agreement .
For receiver agreement it should be |<Sender Service>| |BS_MA_FileServer_PRD | CC_File_PedidosServ_MA_FileServer_IA
Bipin

ABAP proxy scenario file - PI7.1- ECC NO_MAPPINGPROGRAM_FOUND

Hello Experts,
I have ABAP proxy scenario file -> PI7.1->ECC . I am getting an error for communication between PI and ECC system. the error is NO_MAPPINGPROGRAM_FOUND and pointing to operation mapping in the software component.
What i found in TCODE SXMB_MONI is 2 adaptor call one from one below the other out of which one is in error.
Also when a file is passed from the file server to the SAP PI I see 2 entries in SXMB_MONI for the same Payload one from source system to target system and one from target system to source system ( ie. from business component as sender and ECC as receiver system and one entry for ECC system as receiver and business system for file as receiver ) is this how it should be
one more thing i would like to specify is that my service interface is Point to point enabled . Is it happening because of that
Request you help on urgent basics
BR Heth

Hi,
1. in PI, by hazard, your Service Interface (SI) does not the mode "synchronous"?
2. or does this SI was declared firstly with "synchronous" mode and the proxy generated with this mode, and then you decided to put "Asynchronous"... without to regenerate the proxy in ECC?
If it's the case, in ECC, select your SI, do a right-click and regenarete the proxy.
3. for the 2nd message (returned by ECC to PI), have you seen the Payload content and SOAP Header?
Could you please also check the Pipeline (e.g CENTRAL, CENTRAL_BACK) ?
4. In SXMB_MONI of ECC, how many messages have you: one ? or two ?
Regards
Mickael

ABAP proxy to file-Create package in SPROXY

hey guys
i m doin ABAP proxy to file scenario,and when i try to create a ABAP proxy its asking for the package and prefix,do any of u know how to create a package ?
also if there are any inbuilt packages that i can use
thanx
ahmad

Ahamd,
use custom packages and you can give prefix start with zxx_
thanks
Prasad

PCK XI adapter - ABAP Proxy to File Scenario How to?

Hi there,
We want to implement the following sceanrio; SAP ABAP outbound proxy to Flat-File scenario. A (sender) SAP system will trigger an outbound proxy which will send outbound data to a (receiver)file system via the PCK and Central Integration Server.
SAP (ABAP proxy) -> PCK-> XI -> File System
My question is; The PCK documentation suggests that the XI adapter included in the PCK can only be used to send/forward messages to the central integration server.
Does that means that one cannot use the same XI adapter on the PCK to redirect ABAP proxy messages to the Integration server?
Thanks,
Roberto

The PCK cannot be used as a replacement for XI Integration server. PCK is only a type of adapter engine that can run independantly. It is intended for partners who cannot use XI server. So PCK can not in itself execute interfaces. It can just forward all the messages received to the XI Integration server. PCK can only run your sender or receiver adapter all the mappings can only be executed on the integration server. So PCK just converts from the native format to XI format and forwards to the Integration Server.
Hope that carifies your question .
Thanks,
Kalyan Musunuri

ABAP proxy to FILE - filename partly build from PAYLOAD

Hi
I have an ABAP proxy sent from SAPBACKEND ->PI->FILE
I need to build the filename dynamically based on a template "FILENAME"+variable1.XML
Variable 1 is from the payload - so a field in my XML - "FIELDVAL".
How to extract the value from the payload and build the filename dynamically?
Can I use substitution values in the filename in the CC? or must I build up the entire filename in UDF?
We are using PI 7.11
Cheeers

Hi,
You can do this either by Dunamic configuration (Writing a UDF) OR by variable substitution..
Check below links
http://wiki.sdn.sap.com/wiki/display/Snippets/SAPXIDynamic+Configuration
http://wiki.sdn.sap.com/wiki/display/XI/CombiningthreedifferentaspectsofPIinoneshot
/people/shabarish.vijayakumar/blog/2009/03/26/dynamic-configuration-vs-variable-substitution--the-ultimate-battle-for-the-file-name
Amol

ABAP Proxy to File - questions

Hi,
i have tried the following blog:
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
and found out that´s not possible to send the message through proxy from the IS(same client as the proxy). right ?
What settings have to be made in our SAP ERP R/3 application System to sent the message the ERP system ?
Thx,
Gordon

Hi,
i have tried the following blog:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
1387
and found out that´s not possible to send the message
through proxy from the IS(same client as the proxy).
right ?
As michal said, you can't create server or client proxies in the same client of the Integration Server, since it doesn't make sense to send a message from one logical system to itself.
What settings have to be made in our SAP ERP R/3
application System to sent the message the ERP system
Now I got confused.
You mean you want to do XI (ABAP Proxy)> R/3 scenario?
Or do you want to call one function in R/3 from another function in R/3?
Regards,
Henrique.

Abap proxy to file

I am using proxy to attach pdf file, In PI, I have 2 payloads. I want to send PDF payload to File receiver adapter.
Suggestion?

Hi,
if you cannot use payloadswapbean
http://help.sap.com/saphelp_nw04/helpdata/en/2e/bf37423cf7ab04e10000000a1550b0/content.htm
then just put the PDF into the main payload in the proxy (one field) and cut correctly in the mapping so only the PDF will be send to the file
Regards,
Michal Krawczyk

RFC Adapter or ABAP Proxy

Pls suggest me which one to use and why?
Any good blog
Regards

hi sehgal
for abap proxies see the below links
/people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies - Activate Proxy
/people/siva.maranani/blog/2005/04/03/abap-server-proxies - ABAP Server Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Client Proxy
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - ABAP Proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/41e08c90-0201-0010-9197-d8774336ea78
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0ae9874-109c-2910-f48a-e91f0cdd1c81
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
for rfc go to the below links
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
Is it possible to use the RFC sender adapter for asynchronous calls? Async call
http://help.sap.com/saphelp_nw04/helpdata/en/f6/e002416225f023e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci983752,00.html
regards
sreeni

Performance problem in File to ABAP Proxy scenario

Hi gurus,
    I have a scenario where the sender is sending a file and the receiver is ABAP Proxy.The file is a simple DAT file containing banking data.The file sample is as belo
00000MM21901 PYM0901021531
704401020100005510000040000D0002
704401020127147391000033500D0003
704401020127147391000045000D0004
704401020109341157000038800D0005
70420!!!!10200000182174D
704401021100006040000015158D0001
704401021100006040000005034D0002
7042010210000020192D
The above file need to be split and mapped to the fields of the ABAP Proxy after doing some validations.
Is Receiver Determination using mapping required? What is the most efficient way of splitting the file?
Please give your replies keeping better performance of the interface in mind.What is the best way of doing the validations?
regards
Debansu

Hi Satish,
    As you can see in my question above,the sender side contains a flat file(the file format is given in the question),I need to split the file into strings which can then be mapped to specific fields of the ABAP Proxy.A sample output of the xml file that is passed on to the ABAP proxy after mapping transformations is given below:
<BATCH_TOTAL_RECORD_420>
<BATCH_REPORT_DISTRICT>70</BATCH_REPORT_DISTRICT>
<KEY_VALUE>420</KEY_VALUE>
<BATCH_NUMBER>1021</BATCH_NUMBER>
<BATCH_TOTAL>0000020192</BATCH_TOTAL>
<FILLER_BATCH_TOTAL_SIGN>D</FILLER_BATCH_TOTAL_SIGN>
<FILLER />
</BATCH_TOTAL_RECORD_420>
- <BATCH_TOTAL_RECORD_420>
<BATCH_REPORT_DISTRICT>70</BATCH_REPORT_DISTRICT>
<KEY_VALUE>420</KEY_VALUE>
<BATCH_NUMBER>9999</BATCH_NUMBER>
<BATCH_TOTAL>0000202366</BATCH_TOTAL>
<FILLER_BATCH_TOTAL_SIGN>D</FILLER_BATCH_TOTAL_SIGN>
<FILLER />
</BATCH_TOTAL_RECORD_420>
I hope now you can provide me some answers.
Regards
Debansu

ABAP Client Proxy to File (File is not getting generated)

Hi All,
I'm trying out a scenario ABAP proxy --> XI --> FILE.
I have followed the given blog to create ABAP client proxy.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
While executing the ABAP client proxy, the values are properly sent to XI and in the SXMB_MONI the message shows as successful. But the correspoding file is not created.
It seems everything is fine in the receiver adpater(Monitoring) and in the SXMB_MONI also the msg shows successful(receiver side).
The directory path and the corresping file creation parameters also looks fine.
Couldn't figure out what went wrong. Please help me on this.
Thanks,
Ajay.

Hi Smitha,
Please find below the Call Adapter 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="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</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 = iscsapapp4w:8010</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="2" type="T">Remote address = 10.191.117.166</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 = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</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 = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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 = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</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 = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0000</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0000</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 = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</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 CENTRAL</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= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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 CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</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_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</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">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</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">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</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">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</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">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</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">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</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_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</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="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - ACN_LEGACY2_04_BS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</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 = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</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_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</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="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) ACN_LEGACY2_04_BS MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</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 = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</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_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</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="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOM2__0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</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">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="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</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 CENTRAL</Trace>
<Trace level="3" type="T">system-ID = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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 CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</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_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</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">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</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">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</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">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</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">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</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">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</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_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</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="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 791955998E03380CA938A0130A348AFB</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 3475AE80930811DAA18DC14C0ABF75A6</Trace>
<Trace level="1" type="T">Interface Mapping http://accenture.com/xi101/ABAPclientProxy IM_Valuemapping</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_Valuemapping_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_Valuemapping_.</Trace>
<Trace level="3" type="T">Load 3475ae80-9308-11da-a18d-c14c0abf75a6, http://accenture.com/xi101/ABAPclientProxy, -1, com/sap/xi/tf/_MM_Valuemapping_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_Valuemapping_.class (http://accenture.com/xi101/ABAPclientProxy, -1) in swcv 3475ae80-9308-11da-a18d-c14c0abf75a6.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_Valuemapping_ completed. (executeStep() of com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</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 = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</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_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</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="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-ACN_Sender_BS_XI</Trace>
<Trace level="2" type="T">-ACN_LEGACY2_04_BS</Trace>
<Trace level="2" type="T">http://accenture.com/xi101/ABAPclientProxy.MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">Channel found: - ACN_LEGACY2_04_BS - ValueMap_Repl_Receiver1</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</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 = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</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_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</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="3" type="T">Unknown channel type: File</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_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</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="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">return fresh values from cache</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): af.nw2.iscsapapp4w</Trace>
<Trace level="3" type="T">URL = http://iscsapapp4w.idcsap.com:51000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = XIISUSER</Trace>
<Trace level="3" type="T">Cached = X</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:19Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</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>
</SAP:Trace>
Thanks,
Jothivel.

ABAP Proxy Structure

Hi,
I have SAP server at sender side, XI is my middleware and two 3rd partyservers on the receiver side.
So,from SAP side data comes through proxy,I would generate a structure which contains the fields required to send the data to both the receivers.But few fields would used to send the data to one server and some fields to another server.
So, once the data is filled,there would be a segreation process internally writeen in proxy to segregate the data.
So, Now can i use the same structure for all the proxies i generate to send the data or should I generate different structures for each and every interface.
Thank you,
Kishore J.

hi,
check the below links, so that u will get complete concept in abap proxies:
/people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies - Activate Proxy
/people/siva.maranani/blog/2005/04/03/abap-server-proxies - ABAP Server Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Client Proxy
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - ABAP Proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/41e08c90-0201-0010-9197-d8774336ea78
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0ae9874-109c-2910-f48a-e91f0cdd1c81
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
reward points if helpful
regards
sreeni

Error in Proxy to File scenario

Hello All,
I m doing Client Proxy, ABAP proxy to file scenario.
I hv done all the configurations in IR & ID.
I hv also created proxy in sender R3 system.
But messages are not going successfully from R3.
when i checkin SXMB_MONI of R3 i get following error
<SAP:Stack>Error when receiving by HTTP (error code: 110, error text: )</SAP:Stack>
Message is in SYSFAIL status in SMQ2.
Any clues how it can be solved??
Thanks in adv.
Mahi

Hi Maheshwari,
Please try as mentioned below
Option 1: Go to SXMB_ADM->Manage Queues and Deregister all the Queues.Use transaction SMQR or SMQ2 to reset the status of queues
For this to initiate processing of messages stuck in the queue, make sure to set following IS configuration parameter
MONITOR QRFC_RESTART_ALLOWED to value 1
Option 2: Check the user associated with the RFC destination AI_RUNTIME_JCOSERVER in sm59 transaction. It is generally SAPJSF. Might be posisble the user password is expired or locked. Log on to j2ee admin tool on the server side and update the password and then see if it works.
Thanks
Amit
Reward points if answer is helpful

ABAP Proxy Exception

Hello everybody i have this error in my sxmb_moni of xi for a abap proxy server receiver:
<?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="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>ZFUS_CL_MI_FMGOB_CAT_FONDOS_C1</SAP:P2>
<SAP:P3>EXECUTE_SYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText>Unable to execute the dynamic application call (kernel error ID UNCAUGHT_EXCEPTION, class ZFUS_CL_MI_FMGOB_CAT_FONDOS_C1, method EXECUTE_SYNCHRONOUS)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
any suggestions?
Regards,
Julio Cesar

Hi
Below is the full details of above links
For link 4196517?
Q) Hi All,
I have got a requirement to raise an exception from existing ABAP Proxy depending on condition. XI consultant created a fault messge type and attached to the inbound interface message type. I have regenerated the ABAP proxy but I cant find any thing in excpetion tab to raise exception.
Please let me know the solution for this.
Answers : 1) Go to Sproxy .
Select the message interface for which you generated the proxy.
Click on the Structure tab. Do you see any Exception Class generated for fault message ?
2) Just follow all the steps defined in the below Blog and you will find the solution.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
3) I can't find any exception class there in 'Structure' tab. what might be the problem.
4) In SProxy ..under the Message Interface you will see Fault Message Type.
Click on Fault Message Type and check if you can see the fault message type created by xi consultant.
Also ask your xi team to login to IR and re-activate the interface.
5) I can't find any fault message type under Fault Message Type. I will ask my XI consultant to reactivate the interface.
Is this the only problem for this or is htere any other reason for not finding this fault message type in SPROXY.
6) Ideally the fault message type should be visible unless he has defined Software Dependencies and using MT from some other SC.
Even if the fault message type is not visible everything could be all right.
Ask him to check if he selected the fault message type while activating the interface.
Do update us when you get a reply from ur xi team.
7) I have checked with XI admin, he said that he created fault message types in Development Xi but R/3 Development refers to Production XI system in exchange profiles. He asked me to change it to XI development in exhange profile settings. So I am searching info on how to set exchange profiles.
8) The following link will guide you ..
http://help.sap.com/saphelp_nw04s/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm
I dont think we need to do any changes in Exchange Profile for proxy communication.
Changing the RFC Destinations (in your R/3 system)- LCRSAPRFC & SAPSLDAPI should solve your problem.
II) For Link :4147406?
Q) Hi All,
We have an ABAP Proxy implemented for posting goods movement and it is calling BAPI function module to post good movement. We have got a requirement that if BAPI returns any error, this error message send back to SAP XI.
data call proxy
Legacy -
> XI -
> SAP R/3(call bapi)
<----
error message
Please let me know how to send the message back to XI.
Answers: 1) Refer the following
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy
2) you can utilize the fault messages for such an usage -
Ref:
Fault messages -
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
3) You have to do Fault message implementation in this case...
A no. of exception will be there.For any error proxy will catch the exception and will write it in the fault message...so....from r/3 response will go to Xi as Fault message response in case any error/exception occours......
have look here...
Fault message implementation.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
4) Please go through it is very useful.
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy --Monitoring for Processed XML messages in ABAP Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy --ABAP Proxies in XI(Client Proxy)
/people/sap.user72/blog/2005/12/29/service-enable-your-sap-application-component --- Service Enable Your SAP Application Component
5) the file adapter can work only asynchronous, so you cant have a response. You should build two asynchronous messages. File -> proxy inbound and after the bapi call an outbound proxy is called which is sending a second messge to the file adapter.
6) you can define a synchronous scenario which will include request/response messages.
send the response back to XI.
the file adapter supports BE QoS.
http://help.sap.com/saphelp_nw04s/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
7)I have an interface Z_stock_move(message interface(inbound)) and class z_STOCK_MOVE in that. I have clicked exception tab but not able to add exception there as its not enabled for change.
Please let me know how to add the exception to an existing abap proxy.so that i can raise an exception when bapi call to goods movenment returns errors.
Might be useful to U.

ABAP proxy related issue

Hi All,
Good morning,
i working with ABAP proxy to file scenario. the requirement for this scenario is we are fetching data from data base to internal table then using that table we have to write code and send data to xi. can give me past response that how to write code using internal table. i want only code related internal table not total code.
thanks for fast response.
regards
sai

Hi Sai komala,
After genrating the Proxy, you can view the calss & structures genrated by proxy.You need to create an object with refrence of Class and to be create workareas for your Message type and Data type strucutres. Create an Internal table with your desired structure and do the validations as per your mapping rules.After completion of your all validations you need to populate your final internal table data to the structure of message type and call the execute asynchronous method.
Have a look into following weblogs
/people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
TO debug u r proxy code, just like your normal R3 report program. put a breakpoint and execute the program , you can view the debugging of your proxy.
Hope it will helps to solve u r probolem
Cheers
Veera

RFC(ABAP Proxy)-------XI-------- FILE Asynch

Similar Messages

Maybe you are looking for