Sender Abap Proxy no get in PI

Hi expert,
I have an sender abap proxy scenario which working fine in development server and even staging server but when transported to production server, the data seem can't go into PI server. I have check all the setting and sure the setting was set correctly. When i check on the system log in sm21 abap ERP, it show an error.
Operating system call gethostbyname failed (error no. 0 )
Any idea on how to solve this? Thanks.

Hi,
plz check transactions sldcheck and sldapicust. Everything ok?
What about SXMB_ADM? System maintained as Application System? Destination given to PI Runtime?
Can you ckeck that destination at SM59?
Plz have a look to destinations SLD_NUC and SLD_UC. Do they work?
Regards,
Udo

Similar Messages

Error while executing sender ABAP proxy program in ECC

Hi,
We have lot of proxy to file scenarios, most of them are working fine. I am having issue with 2 interfaces, when I execute sender ABAP proxy program, we are getting following errors in ECC:
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:Stack>com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=ED1CLNT290;TS=;AN=CustTrPowersellS_Out;ANS=urn:maines-net:OTC_079E:PowersellCustomerTerms; at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:237) at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:167) at com.sap.aii.af.service.cpa.InboundRuntimeLookup.<init>(InboundRuntimeLookup.java:88) at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBinding(AbstractLookupManager.java:519) at com.sap.aii.adapter.soap.web.MessageServlet.getBinding(MessageServlet.java:875) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:439) at etc etc
Configuration should be fine because many scenarios are working. Can you please help me where could be the error?
Let me know if you need more info.
Regards,
N@v!n

Hi Naveen,
We saw your solution about this issue. We are also facing same issue. I wanted to know where we have to update scenario as simple scenario or integrated scenario.
And could you please tel me what is the main diff between in these two.
As we are are using PI 7.31 java stack so for this version what we have to use.
Thanks,
Shivdeep Kumar

Problem with sender ABAP proxy

Hi All,
I have created sender ABAP proxy (Async). I am testing the proxy from SPROXY transaction it selft .. when i provide the data and execute the proxy it is showing <b>"Services Processed Without Error"</b> , but i am not getting any error , i am not able to see any message in SXMB_MONI or RWB .. how to check where the message is failing ??

Hi,
You said you are sending message from proxy....its very easy to debug in this case. You can set a breakpoint directly in your proxy caling program. Just check if you are calling commit work after calling proxy.
Also you can do it using the abap system command '/H' or the code 'BREAK-POINT' for/in the report program triggering the iterface.
Check out this thread...
How to Debug proxies
Hope this will help you.
Ni;esh

Sender Abap Proxy -- Receiver JDBC , catch communication channel exceptions

Hi All,
I have a sender abap proxy and a receiver jdbc asynchronous interface.
Now under some circumstances when I send some junk data for an update query(which satisfies metadata requirement but wrong primary key) it shows chequered flag in both XI and r/3.
But in communication channel it shows error.
Queries:
1. How do I handle this.
2. Since this is triggered from Abap wht will be subrc when method ends in this particular case.
3. Is there any possibility of program goin into dump?
Regards,
Prem

You can catch the exception in cx_ai_system_fault.
http://help.sap.com/saphelp_nw70/helpdata/en/75/a55c3cff8ca92be10000000a114084/content.htm
DATA:
lo_mes TYPE REF TO
     [Client proxy class],
l_sys_exc TYPE REF TO
        cx_ai_system_fault,
l_app_exc TYPE REF TO
        cx_ai_application_fault.
CREATE OBJECT lo_mes.
TRY.
CALL METHOD
lo_mes->EXECUTE_SYNCHRONOUS
    EXPORTING
      OUTPUT    = ls_request
    IMPORTING
      INPUT     = ls_response.
CATCH cx_ai_system_fault
            INTO l_sys_exc.
* handle system error
    EXIT.
CATCH cx_fault_1
            INTO l_app_exc.
* handle application error 1
CATCH cx_fault_n
            INTO l_app_exc.
* handle application error n
CATCH cx_ai_application_fault
            INTO l_app_exc.
* handle other
* application errors
ENDTRY.
Thanks,
Beena.

Sender ABAP Proxy - EOIO

Dear Experts,
I have two requirements. Requesting experts' help.
1. How to acheive Quality of Service EOIO for Sender ABAP Proxy. I know there is set_serialization_context method that we can use, but do not how to. Do we have a guide? Can you please help?
2. When I acheive EOIO as mentioned in point-1, when all the messages are sent to same queue, in case if previous message fails in PI mapping, I do not want the next message to stuck in the queue, it should continue processing. How can we do this?
Thank you.
Best Regards,
Saravanan

Hi sarvana,
For your first question:
Please see the thread:
How to determine quality of service of communication between XI and R/3
second question
In Case EOIO any kind of error Message processing will be stopped.
You cant specify that only for mapping error EOIO will not work and for other error it should work as EOIO

EOIO in sender ABAP proxy

Hi
I am referring to I am referring to /people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies for EOIO in sender abap proxy
My requirement was to send thedata and trigger messages in EOIO fashion in one Queue.
This is working fine for one interface...
but for the other interface it is always creating 2 queueids...one for data messages and other for the trigger message..
Queueid that I have given is supose "ABC"
then it is always creating 1 Q like XBQOT___ABC
and 2nd Q like XBQOH1__ABC.
ideally both the Qname should be the same...any ideas?
PS: if i check the Q name in SXMB_MONI of SAP system it is same for both the data and trigger like "ABC"
Edited by: Tarang Shah on Jun 4, 2010 5:12 PM

Any ideas ?

Make Sender ABAP proxy transport HTTPS

Hi Experts,
I have a sender ABAP proxy scenario without CC configuraiton. Now if i want to HTTPS for data transportation from R3 to PI. What could be the possible ways?

Hey,
>Now if i want to HTTPS for data transportation from R3 to PI. What could be the possible ways?
Yes,
Create the Port for HTTPS, Install the certificates , Change the parametr in Visual admin for HTTPS call.
Cheers
Agasthuri

I want to test sender ABAP proxy in AAE by SOAP client

To PI Specialists
Now I plan to test sender ABAP proxy in AAE by SOAP client system.
(we use aae so we set sender abap proxy by sender soap adapter.)
ABAP creating team and PI creating team are in other site.We cant contact easily.
I want to separate ABAP Unit test and PI Unit test, plan to use soap client for test driver.
(we use SOAPUI. )
the url is http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=party:service:channel
I noticed that sender soap adapter is started, but the messeage protocol is invalid.
we use messege of wsdl. it must be XI3.0 protocol.
Please tell me XI3.0 protocol.
Naoki

This is possible to do in SOAPUI. I am testing this scenario using AAE, but I am also using SOAP UI Pro. The procedure is pretty basic. Instead of sending your payload in as part of the body, you have to send it in as an attachment. You will also need to set the header correctly. Here is a sample message from my SOAP UI tests that may help. The only thing you need to do differently is load the attachment, name it, and make sure that the name of the attachment is reflected in the SAP:Payload attribute. Also, I am using a Groovy script to create a GUID.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
<soapenv:Header>
<SAP:Main versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92FFF13F5C59777FE1ABE00000A1551F7" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
            xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
   <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
   <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
   <SAP:MessageId>${Create GUID#result}</SAP:MessageId>
   <SAP:TimeSent>${=new java.text.SimpleDateFormat("yyyy'-'MM'-'dd'T'HH':'mm':'ss'Z'").format(new Date())}</SAP:TimeSent>
   <SAP:Sender>
    <SAP:Service>SVCNM</SAP:Service>
   </SAP:Sender>
   <SAP:Interface namespace="Interface_Namehttp://namespace.com">Interface_Name</SAP:Interface>
</SAP:Main>
<SAP:ReliableMessaging SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
<SAP:System SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SAP:Record namespace="http://www.sap.com/webas/712/soap/features/runtime/metering/" name="CallingType">SA</SAP:Record>
</SAP:System>
<SAP:Diagnostic SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SAP:TraceLevel>Information</SAP:TraceLevel>
   <SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
<SAP:HopList SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SAP:Hop timeStamp="${=new java.text.SimpleDateFormat("yyyy'-'MM'-'dd'T'HH':'mm':'ss'Z'").format(new Date())}" wasRead="false">
    <SAP:Engine type="BS">SVCNM</SAP:Engine>
    <SAP:Adapter namespace="XIhttp://sap.com/xi/XI/System">XI</SAP:Adapter>
    <SAP:MessageId>${Create GUID#result}</SAP:MessageId>
    <SAP:Info>3.0</SAP:Info>
   </SAP:Hop>
</SAP:HopList>
</soapenv:Header>
<soapenv:Body>
<SAP:Manifest wsu:Id="wsuid-main-92FFF13F5C59777FE1ABE00000A1551F7" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink"
                xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
   <SAP:Payload xlink:href="cid:TestPayload.xml">
    <SAP:Name>MainDocument</SAP:Name>
    <SAP:Description/>
    <SAP:Type>Application</SAP:Type>
   </SAP:Payload>
</SAP:Manifest>
</soapenv:Body>
</soapenv:Envelope>
Here is a picture of my SOAP UI project in case it help the understanding.

How to handle exceptions in sender ABAP Proxy

Hi Experts,
   I have a synchronous scenario.
   SAP R/3 System A -ABAP Proxy <-> PI <-----> SOAP< ---> Webservice
   In system 'A', a function module calls the ABAP Proxy method.
   My requirement is that if there is an exception in PI ( for example: timeout or ABAP engine error) then I want to get the exception details in the calling function module.
For example:
Exception in PI:
<SAP:Error xmlns:SAP="XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1/><SAP:P2/>
<SAP:P3/><SAP:P4/>
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack/>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the calling function module:
Try
Call to proxy-> method
Catch cx_ai_system_fault INTO v_o_fault.
       v_err_msg1 = v_o_fault->GET_TEXT( ).
       v_err_msg2 = v_o_fault->errortext.
       v_err_msg3 = v_o_fault->code.
Endtry.
Here I get value "MESSAGE.GENERAL" for v_err_msg1 and v_err_msg3. v_err_msg2 is blank.
I want to capture the info available under <SAP:AdditionalText>. How to get that?
Please help!
Thanks & Regards
Gopal

>
gopalkrishna baliga wrote:
> Hi Experts,
>
>    I have a synchronous scenario.
>
>    SAP R/3 System A -ABAP Proxy <-> PI <-----> SOAP< ---> Webservice
>
>    In system 'A', a function module calls the ABAP Proxy method.
>
>    My requirement is that if there is an exception in PI ( for example: timeout or ABAP engine error) then I want to get the exception details in the calling function module.
>
> For example:
>
> Exception in PI:
>
>   <SAP:Error xmlns:SAP="XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
> <SAP:Category>XIAdapterFramework</SAP:Category>
> <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
> <SAP:P1/><SAP:P2/>
> <SAP:P3/><SAP:P4/>
> <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
> <SAP:ApplicationFaultMessage namespace=""/>
> <SAP:Stack/>
> <SAP:Retry>M</SAP:Retry>
> </SAP:Error>
>
> In the calling function module:
> Try
> Call to proxy-> method
>
> Catch cx_ai_system_fault INTO v_o_fault.
>        v_err_msg1 = v_o_fault->GET_TEXT( ).
>        v_err_msg2 = v_o_fault->errortext.
>        v_err_msg3 = v_o_fault->code.
> Endtry.
>
> Here I get value "MESSAGE.GENERAL" for v_err_msg1 and v_err_msg3. v_err_msg2 is blank.
>
> I want to capture the info available under <SAP:AdditionalText>. How to get that?
>
> Please help!
>
> Thanks & Regards
> Gopal
Hi Gopal,
Maybe the exception is CX_SY_APPLICATION_FAULT, or you can catch by BPM in PI and send back to proxy like a message response.

How The ABAP Proxy method gets triggered

Hi All,
I have created a ABAP Proxy for inbound interface.For this interface the data is coming from XI system.So i am writing the logic to read the XI data into an internal table and am populating the same data into a BAPI.
So my question is,once the XI system sends the data, Will this ABAP Proxy Method automatically gets trigger or Do we need to make any settings?
Please Help me As early as possible.
Thanks in advance
Regards
Srinivas Kodukula

Hi srinivas,
Refer the below points for the configuration needed at R/3 side:
1. Create a HTTP connection in the business system using transaction SM59
2. Configuration Business system as local Integration Engine in SXMB_ADM
3. Connection between Business System and System Landscape Directory. For this check the RFC destinations LCRSAPRFC and SAPSLDAPI
4. Maintaining the SAP J2EE Connection Parameters for LCRSAPRFC and SAPSLDAPI in SAP J2EE engine
5. Maintain SLD access details in Transaction SLDAPICUST
Regards,
Kiran Bobbala

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,

ABAP Proxy call gets stuck in qRFC

When I execute my program to trigger an ABAP proxy, the program executes successfully, but then no message appears in the Integration Engine.
I have discovered that every time the program is executed, it ends up with an entry in the qRFC of the sending system. I can execute that manually, and the message appears in the Integration Engine.
Can somebody please tell me why this is happening?
Also, if I execute in client 110, the program works as described, but in client 100 and 120, I have a CX_AI_SYSTEM_FAULT exception raised.
Any ideas why this may be the case?
Kind Regards,
Tony.

Hi Anthony,
May i know what is the flag u got in sxmb_moni of ECC.
>>I have discovered that every time the program is executed, it ends up with an entry in the qRFC of the sending system. I can execute that manually, and the message appears in the Integration Engine.
i understood that the message is strucked in ques( i.e SMQ1 or SMQ2) always.
In order to resolve this, we need to register the ques and activate it.
some ques like XBQ1,XBQA,XBQS*,............etc.
we have QRFC Adminstration option in SMQ1,SMQ2 and SXMB_ADM.
please register and activate it ...
award the points, if it helpful to you
Regards
Mahesh.

Bpm send abap proxy problem

BPM send abstract interface sd025proxy (bapa proxy).
in sproxy only message interface outbound and inbound can create proxy, abstract interface can't create proxy.
so how can I handle this in ID?

Proxy communication needs direction....abstract interface does not have any direction.
BPM send abstract interface sd025proxy (bapa proxy).
BPM will send abstract interface...fine....however when you run config wizard for BPM --> SAP communication include the inbound message interface corresponding to your proxy wherever there is a reference for target(receiver) MI....create a new MI in IR accordingly.....this is the only option available.
Regards,
Abhishek.

AAE- Sender ABAP Proxy to SOAP - Payload not reaching PI 7.10 SP4

Hi friends,
I am developeing interface from Solman to PI to 3rd party.
I configured the interface using ABAP stack and it worked fine. Then i changed the RFC destination used in SXMB_ADM to point to adapter engine so that i can use AAE.
I configured SOAP adapter. I wonder there is no option to select BE, EO or EOIO in PI7.30 when we select XI protocol.
I can see my payload in SXMB_MONI is solution manager but the payload is not reaching SAP PI although i am receiving the message and can see error also in Adapter.
Does we need to do anything different in PI configuration to achieve it ?
Regards
Inder

Hi Baskar,
I am on 7.30 so it should work. I created another interface and it works fine.
The only difference between my interface which is not working is "Java Mappping" and also i have custom adapter module on receiver channel.
I think the reason for failure is custom Java adapter as it is called before the mapping is executed(In AAE mapping is executed by receiver adapter chain and i configured module before that)
I think i need to redesign my adapter module to manipulate input payload of mapping rather than output payload.
Regards
Inder

Sender Abap Proxy -- Receiver JDBC MaxDB

Hi Experts,
Please, PI works with MaxDB database?
What is the procedure? Need to install drivers?
SO is Linux.
Thanks for the help!

Hi,
>>>>Please, PI works with MaxDB database?
yes
>>>What is the procedure? Need to install drivers?
yes you need to install the driver - the rest is the same as with any other DB
Regards,
Michal Krawczyk

Sender Abap Proxy no get in PI

Similar Messages

Maybe you are looking for