Mail to proxy scenario design

Hello,
In the new requirements, i need to set up mail to proxy scenario in sap PI. The mail comes in with a txt attachment. I can set up a sender mail adapter to fetch the mail and attachment. There are 5 columns in this file attachment. I need to read and map each record to the target message in message mapping. How do I do it? Any helpful answer would be really apprecaited.
Cheers,
Bai

This piece of java code will remove the TAB
//write your code here
StringTokenizer st = new StringTokenizer(record,"\t",false);
String t="";
while (st.hasMoreElements()) t += st.nextElement();
return t;
Edited by: Bai Li on Dec 17, 2010 4:49 AM

Similar Messages

Mail to Proxy scenario with attachment. AF channel error.

Hi,
We are running SAP PI 7.1. I am experiencing the following problem in a Sender Mail adapter.(POP3).Mail to Proxy Scenario.
I have configured a sender mail adapter channel as POP3. This channel is configured to use the Mail Package and to Keep attachments. When I send a mail with an attachment to the mailbox that is being monitored by this channel, then the channel collects it from the mailbox.
In channel monitoring it indicates that the message was successfully delivered. However when I click on the message ID the view the audit Log it gives an error: u201CTransmitting the message to endpoint http://HOSTNAME:8101/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.u201D The message never arrives at the integration sever to be view in sxmb_moni.
Also when I sent a message without an attachment the message does go through. Or if I send a message with a text attachment the the message goes through, but not the attachment.
Any help would be most welcome.
Regards
Willie Hugo

Hi Willem,
I'm coming back to your original problem: "com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.u201D
Actually I had the same problem here and found a solution for it. In this case it was a file to Proxy scenario. The file send was large. After structure conversion the file size was more then 100 MB as indicated in the Audit Log of the message "2009-03-02 09:27:06 Information Send binary file "<File_Name>" from ftp server "<ftpuser>", size 106706248 bytes with QoS EO.
The ICM restricts all HTTP requests larger then 102 MB via the parameter icm/HTTP/max_request_size_KB which has a default value of 102400 (100 MB). Therefore it rejects the requests and your error is thrown.
There are two ways of avoiding this:
1) Increase the parameter:
Increasing the parameter implies a risk since large messages can overload the system (e.g. during the mapping). Therefore it is good to have these safety measurement in place.
2) Split the request:
Depending on the scenario it might be possible to split the request to restrict the max. number of records for a given file. This is the prefered option because it ensures better stability of the system and also better performance.
I think this situation applies to you as well - but I'm not sure since you did not specify the request size and the size of the attachement.
Best regards,
Mike

Mail to proxy scenario with condition

Hi Experts,
I am using mail to proxy scenario.
The mail box is having differnt files suppose:
BOOKING_REF_DELIVERYNO_WB.pdf
BOOKING_REF_SALESORDER_WB.PDF
BOOKING_REF_CUSDECNO_WB.PDF
DELIVERYNO_WB.pdf
SALESORDER_WB.PDF
CUSDECNO_WB.PDF
BOOKING_REF_WB.pdf
BOOKING_REF_DELIVERYNO_BOLCOPY.PDF
BOOKING_REF_SALESORDER_BOLCOPY.PDF
BOOKING_REF_CUSDECNO_BOLCOPY.PDF
BOOKING_REF_BOLCOPY.PDF
DELIEVERYNO_BOLCOPY.PDF
CUSDECNO_BOLCOPY.PDF
SALESORDER_BOLCOPY.PDF
BOOKING_REF_AWB.PDF*
DELIVERYNO_AWB.PDF
SALESORDER_AWB.PDF
CUSDECNO_AWB.PDF
Depending upon the file name in the mail box, the file needs to be attached via proxy with particular code:(x for case 1, y for case 2 , z for case 3)..for attachment abap code wrtiiten for proxy.
how to compare the file name from the mail?
DO i need to write a UDF..mapped with filename field of the sender XSD?How to do that?
Please suggest.
Thanks,
Sushama

You can use the other UDF
public String Get_Input_File_Name(Container container) throws StreamTransformationException
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String SourceFileName = conf.get(key);
return SourceFileName;
the previous one was for XI 3.0 , may be some differnt requiement I am not sure.
http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
regards
Ninad

Filter mail account in MAIL to PROXY scenario

Hi all,
I have a MAIL to PROXY scenario, and i would like receive emails only from specific adress.
I try using Mail Package and add a condition in the receiver determination but it doesn´t work.
Is there any way for do this?
Regards,

use xpath in RD to allow only the mail address you want to follow through.
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers

FTP to ABAP Proxy Scenario - getting error CO_TXT_CHANNEL_PASSWORD_ERROR

We have transported PI and EP data from development server to respective production, every thing is running fine except the abap proxy scenarios i.e. PI reads file from ftp location and calls the abap proxy but we are getting following errors:
<?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>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_CHANNEL_PASSWORD_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read user password from communication channel of type Error when accessing the secure store (access ID = FD768D4A8772DB50E1000000AC10041E) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any solution?
Please note that I have searched and applied solutions given on SDN forums but didn't get any success. So I am looking for new suggestions.
Regards,
Jawed Ali

Jawed ,
Please test the HTTP destination of your receiver comm channel.
Which is the RFC connection to your R3 system.
Transaction SM59 and check the logon parameter for the connection you are using.
Regards,

EOIO is not working for file- BPM- Proxy scenario.

Hi All,
I have one File to BPM (Merge pattern ) to Proxy scenario.
I have two file communication channel at the sender side and defined QOS as EOIO for both. In SXMB_MONI it assings same queue for all messages.
BPM is merging that messages. However during that it assings different queue for merged messages.
When it comes to proxy , again different queues are assingned to the messages.
Is there any way I can define QOS in BPM or at the proxy side ( I know it should be at the sender side only , but it's not working..)
Thanks & Regards,
Dijesh Tanna.

HI,
Within the current release the BPM will always only use EO (SAP Note 833740).
May be the SAP note 905049 will help you on this ...
Thanks
Swarup

Issue in Iodc- abap proxy scenario

Hi all
I have a idoc to abap proxy scenario. The issue is ,
when we send the idoc to client A of target system, it works ifne.
But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
Is it because of any error in XI configuration or somethin else.

hi all
thanks for all your responses.
I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
I gave the conditions in Receiver Determination.
Same Server Proxy is used in both the target business sytems.
I have done all the Configuration Steps ,( Created two separate business systems also )
Also I have checked wiht all the system settings to be made in the target system B.
When i trigger the idoc to Client 100, it goes to XI and then reaches Client 100 of System B
without any problem. I get the desired result from proxy code.
When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
the Call Inbound PRoxy step. (from sxmb_moni)
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

Error in FILE 2 Proxy Scenario

Hi All,
I am doing File to Proxy Scenario i am getting following error
Could any one provide the solution for this.
*<?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>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>MI_Emp_Sender</SAP:P2>
<SAP:P3>Namespace</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_Emp_Sender, request message, namespace )</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Thanks in Advance
Mahesh
</SAP:Error>
Edited by: Mahesh Reddy on Jul 10, 2008 12:47 PM

Hi Mahesh,
1) Use SPROXY transaction.
Menu-> Proxy -> Activate All.
2) check in the interface determination if u are using correct
inbound interface.
3) If this if fine....try deleting all proxy objects of the interface
and create new.
Regards,
Praveen K

Receiver Determination Problem In Mail to File Scenario.

Hi All,
I am trying to do Mail to File Scenario. I defined two business systems, one s/w component in SLD and in IR I defined a DataType , MessageType and Two MessageInterfaces. In ID these are mail adapter settings I gave :-
Message Protocol :- POP3
Message Protocol :- XIPAYLOAD
MAIL ATTRIBUTES -- Enabled checkbox for "Use Mail Package"
 Content Encoding - "base64"
 Enabled checkbox for "Keep Attachments"
DEFAULT XI PARAMTERS --
 Default Interface Namespace -- http://mtf
 Default Interface Name -- mtf_mi1
And in Modules Tab I also defined the "PayloadSwapBean" module and swap.keyName and swap.keyValue.
Infact I followed all the steps specified in /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
But in SXMB_MONI this is the error I am getting :-
<?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>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please help me out.
Thanks All,
Madhu.

Hi,
Please verify letter by letter if you haven't make a typo here:
Default Interface Namespace -- http://mtf
Default Interface Name -- mtf_mi1
please also make a test of your scenario in integration directory
please also do not use best efort quality of service
/wg
Message was edited by:
 Wojciech Gasiorowski

Data stuck in QRFC in client proxy scenario

In client proxy scenario (proxy to file async). I triggered the report porgram from ECC and I the green flag moni in ECC but the mesage is did nto reach PI as it got stuck in qrfc. It reaches PI upon clearing the message from SMQ2. Please help solve this.

this problem persists when queues are not registered or any abapstack workitem gets into error.
select the workitem in smq2. execute it manually. after completing the execution, goto sxmb_adm tcode, there select manage queues. then register queues.

File to Proxy Scenario : Error in communication channel monitoring

Hi,
I have developed File to Proxy Scenario on PI 7.1 system and it is not working. I see the below error in communication channel monitoring.
u201CError: com.sap.engine.interfaces.messaging.api.exception.ConfigException: Some of the IS access information is not available. SLDAccess property may be set to true, but SLD is not available.u201D
File will be picked from the FTP server.
I have created File system in SLD of type "Third Party", Can this be the issue?
Please guide me on this.
Thanks,
Chandravadan

Hi!
Check if the tcode SLDCHECK is ok!
Check note #764176.
Also, refer to link below and execute each steps from the links there MANUALLY.
Wizard-Based Configuration:
http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/2e4c1b16bb4aa8e10000000a11466f/frameset.htm
Regards,
Caio Cagnani

File to ABAP Proxy Scenario

Hi All,
I am doing File-to-ABAP Proxy Scenario, in the sender side side it is picking the file, but in sxmb_moni it is giving the 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="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
<SAP:P1>4CFF4691EEE211DC85E30019D1522982</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message ID 4CFF4691EEE211DC85E30019D1522982 already exists in called system (pipeline CENTRAL)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Can u plz tell me why this error is occurring and how we can resolve this error.
Thanks & Regards,
Vikas

Hi Vikas
make a dummy change and activate your object then make a full refresh
you can make it through in 3 ways
1) tcode SXI_CACHE
2) go to ID -> environment and make a full cache refresh
3) http://<host>:5<sys#>00/CPACache/refresh?mode=full Full CPA cache refresh
when you do the developement then these are stored in ABAP data dictionary table which can be refreshed by delta cache
while full cache will delete this temporary object and make this cahe into runtime
hope this will help you
thanks
sandeep
if helpful reward points

SOAP - Proxy Scenario

In my SOAP to Proxy scenario I have a proxy that will return "true" or "false" depending on the logic in my method. When I execute the proxy it returns the false value for cases that are false in SAP. The scenario does not return the "true" value when the logic is true in SAP. If I go into SAP and run the method, both the true and the false logic paths work and the method returns the correct value. If I hard code the variable in the method to "test" and execute the XI scenario it will return the word "test" for both cases, true and false. I have the same scenario in my XIQ system and it works fine.
So, what I have done...
I have flushed the cache, that did not work.
I have rebooted my XI system that has the problem.
I have compared my XI broken system with the one that is working and there are no differences.
Does anyone know how I can see what is truely being sent back to the SOAP side? Is there a way to debug the ABAP code from the XI / SOAP side?
Any help would be greatly appreciated.
Thanks
Skip Ford

Hi Ford
When you try with SAP its working right. Did you see that response in XI. If not then no need to touch XI.
Take the payload and try to debug the proxy. You will come to know if it really returns the true value or there is a data issue itself and no problem with XI and SAP.
Check in XI mapping as well. if the value from source is moving to target or not. If you make any changes or found problem do regenerate and activate proxy.
Thanks
Gaurav

SOAP to Proxy scenario communication error

Hi Friends,
 Now i am developing SOAP to Proxy scenario, i am testing WSDL file using SOAP UI software and i am getting an error in SOAP UI tool.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Error Report</title>
<style>
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
A:link {color : #0059AA;}
A:visited {color : #999999;}
A:active {color : #999999;}
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
<tr bgcolor="#FFFFFF">
<td align="left" colspan="2" height="48"> 403 Forbidden</td>
</tr>
<tr bgcolor="#3F73A3">
<td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
<td height="23"><img width=1 height=1 border=0 alt=""></td>
<td align="right" height="23">SAP NetWeaver Application Server </td>
</tr>
<tr bgcolor="#9DCDFD">
<td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
</tr>
</table>
 
 Error: You are not authorized to view the requested resource.
 <a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a>
<table>
<tr>
<td valign="top"> Details:</td>
<td valign="top"><PRE>No details available.</PRE></td>
</tr>
</table>
</body>
</html>
I have tried with the same WSDL earlier it was working fine, now its not working and throwing the above error.
Kindly suggest me to overcome from this issue.
Regards,
Senthil.

Hi Senthil,
Try with the authentication preemtive. Also, check your URL because that error seems that you are accessing to wrong PI section or your user has not the enough credentials, try with PIAPPLUSER or with the same roles that this user.
Regards.

SOAP- Proxy scenario, issue with WS adapter

Hi guys,
i've set up a soap->abap proxy scenario (on 7.1) and want to use the new WS adapter. unfortunately I'm facing some issues. The proxy has been generated properly and I also set it up in soamanager. I tested it from XML Spy and it works fine. So there shouldn't be any problem with it.
But when I try to run the scenario, I get following error:
WS_ADAPTER_SYS_ERROR
<sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException><sap:ChainedException><Exception_Name>CX_SOAP_CORE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException></sap:ExceptionChain>
System error while calling Web service adapter: <sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when processing Web service
I checked the /sap/xi/engine service on both - PI & ECC and it is activated.
Any hint, what could be wrong?
Thanks a lot,
Olian

Hi,
"ICM_HTTP_CONNECTION_FAILED" this error is relaed to ICM. Does your Type H connection "INTEGRATION_SERVER_HMI" works fine.And check integration engine configuration in SXMB_ADM.
And here is a similar thread.
Re: HTTP to Enterprise Services.
Regards,
Reyaz

Mail to proxy scenario design

Similar Messages

Maybe you are looking for