ABAP Clinet Proxy issue

Hi Frnds,
I am working on ABAP Client proxy , when i am sending data to PI getting error message in ECC moni
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
did any one experieced this type of issue??
i have used service user in RFC destinations.
thanks,
Raj

Hi Frnds,
Thanks for your valuable inputs.
SLD check working for my user id, but my id does not have SAP_XI_IS_SERV_ROLE, I used other user id(XI_RFC)which has all roles. but when I use this one sld check not working.
In RFC destination in ECC I have used XI_RFC, connection test working fine.
I donu2019t why this problem coming. Do I need to uses PIAPPLUSER in RFC destination??it is mandatory?? Because PIAPPLUSER maintained as a user name for Integration server in exchange Profile.
Regards,
Raj

Similar Messages

ABAP Inbound Proxy issue

Hi All,
I have a file to ABAP Inbound proxy scenario for creating vendor in SAP.
When I execute from SPROXY test tab, vendor is created in SAP.
But when i test end to end i.e by feeding the file adapter with the vendor file i don't see the vendor creating in SAP.
The message is successful in PI moni and in ABAP moni. Cant see any errors
Appreciate your inputs in this solving this please
Keerthi

>
Keerthika R wrote:
> The message is successful in PI moni and in ABAP moni. Cant see any errors
Hello Keerthi,
I was facing the same issue. I found that we can use SXMB_MONI and SMQ2 in the SAP side as well (Backend ABAP System where the Server Proxy is created). If you are able to see the messages in SXMB_MONI of the ERP system then your proxy is working fine however, have problems in ERP System. Follow through the error message it will be easy for you to perform error analysis.
You can ignore if you have already done it!
Thanks & Regards,
Anand Patil

ABAP Server Proxy Issue

Guys,
For a scenario i am using ABAP Server Proxy.
I have successfully generated the proxy object but when i want to put some logic in server proxy by double clicking on execute_synchronous, i am getting nothing and when i am trying to use the toggle button to bring the proxy in editable mode i am getting the message that " you can't edit proxy objects ".
What is the solution....
Regards,

As sheetal said "Have you activated the proxy object properly ".
no i didn't ...
I went to SE24 and selected the class with my interface and activated it..
Process should be : Under Proxy Objects choose your interface and test .
It will show you the class needed to be activated..Finally i activated the class..
and get the ball rolling..
Thanx to Sheetal.
Regards,

ABAP Client Proxy Issue..

Hi Folks,
I am trying to push the data from R3 to RDBMS ...using proxies..
I am able to push single line item but when i am not able to push multiple line item.
<b>I want to know how to handle table type inside a stucture..? sample code will help me in this regard..
Any suggestions..?</b>
Regards

Hi Santosh,
To send multiple items from proxy..
Did you create the fields inside a structure in your data type.
I mean like this..
Records
   field1
   field2
   field3
Now suppose your Message Type name is MT_TEST.
Then in your abap code you can access records like this..
OUTPUT-MT_TEST-Records[].
Best options is create your proxy and then see in debugging mode. You will figure out yourself.
Regards,
Sumit

ABAP Client Proxy from ECC 6.0 to XI message irregular recieving

Hi Gurus
Any one has come across issue whereby the ECC 6 system trigger ABAP Client proxy to SAP PI 7.0. The first time the PI is able to recieve it in the SXI_MONITOR. But subsequent trigger from the ECC 6.0 system the SAP ABAP program to trigger the Client Proxy, the PI seem to lost connectivity and did not recieve any message. This is pretty strange and hopefully someone in SDN and enlighten me.
Thanks
Regards
On behalf of malcolm

Hi Santosh
I went to SMQR and register the queue, but it still did not reflect the locked queue when i trigger the ECC 6 to SAP PI 7.0. The green flag - schedule still appear in the SXMB_MONI queue. But i am quite puzzle as why the ABAP client proxy after sending message the first time and second time, the third time it stuck? And also it is not practical to everytime go to the SMQ1 or SMQ2 to unlock the queue. I don't think it a good solution for solving my problem, it is just a temporary solution.

ABAP Outbound Proxy: some messages stuck in CRM system

Hi all,
we've a strange issue with a ABAP Outbound proxy we've generated in our CRM 5.0 system (asynchronous interface).
Sometimes messages stuck in the CRM system. They are in status 'Scheduled' (green flag) in SXMB_MONI in the CRM system. When I have a look at the corresponding queue, there's no message within. Status in SMQ1 and SMQ2 is fine, too. All queues are registered. When I reprocess such a message manually in SXMB_MONI in CRM with the restart button, they're sent fine to XI.
Please note: it's NOT a general issue with that outbound proxy. In most cases the messages are sent immediately, just in some cases the messages stuck and I don't know why.
Is it possible to restart such messages automatically? I just know the report RSXMB_RESTART_MESSAGES, but that one just restarts messages in Error status. But the ones we have aren't in error status so they cannot be selected with that report.
Any idea where could be the problem / we should check?
BR
Holger

On which SP r u working correctly. May be an SP upgrade could help.
Regards,
Prateek

How does ABAP client proxy determine the sender business system

When we use ABAP client proxy to send a message in XI-SOAP format to the integration engine, how does the client proxy determine what is the sender business system, i.e. how does it know what value it should insert in the sender service field in the SOAP envelop.
For example, at first, the business system X8A_105 corresponds to the technical system X8A_105, so when the client proxy sends out a message, the sender service is X8A_105. Then I delete the business system X8A_105 in the SLD, and create a new business system that is associated with the technical system X8A_105.when the client proxy sends out a message, the sender_service is still X8A_105, why?

Hi Annie,
Execute the following function module in your business system and see what name it returns..
LCR_GET_OWN_BUSINESS_SYSTEM.
You can always debug the code inside the above FM to find out how it gets the business system name...
I think the issue should be related to cache. I would also suggest you to logoff from your business system and then login again.
Regards,
Sumit
Message was edited by:
Sumit Khetawat

ABAP Client Proxy to SOAP

Hi all,
I am working on ABAP client proxy to SOAP Asynchronous scenario. when iam sending the data from r/3 system data sent to webservice.
but PI sending this same data 3 more to the third parth system. when i checked in runtime workbench it is showing number of retrys 3
how to resolve this issue. please explain in detail
Thanks
Anil

Anil,
That's the default setting for Async SOAP communication...this can occur if the receiver is overloaded and cannot take any more feed and sometimes time out in the middle of the hand off...this would lead to re-try in PI...so you would see 3 entries of same data...refresh or clear the data from the receiver could solve the issue...
Thanks,
Srini
Edited by: Srinivas Davuluri on Sep 9, 2010 1:51 PM

File to ABAP Server Proxy Scenario

Hi 2 all,
I am running File to Server(ABAP) Proxy scenario...
I have checked the ABAP Server Proxy at application server only and it is working fine....But when i am running the whole scenario my server proxy is not getting executed..( i.e my file is being picked up but proxy is not getting called ..:(( )
Can i expect some valuable inputs regarding this issue..?
Regards,

to debug the problem....
first check SXMB_MONI of R3 system... where proxy has been created.
1 .check whether your proxy has been called ... it will be evident you get any message in moni for you interface or namespace..
2. check you proxy message has not got stucked in queue... sometimes message get stucked in queue and hence proxy are not called.. release the messaeg using smq2.
ELSE
1 .go to SXMB_MONI...of XI..
2. select 'Call Adapter' in right hand of monitor.
3. check the 'trace' under Call Adapter.
4. if you go at end of trace or somewhat near to end.. there should trace like...this ...
Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">Addressing mode: destination</Trace>
<Trace level="3" type="T">Destination = D67CLNT103_HTTP</Trace>
<Trace level="3" type="T">Attributes of destination: D67CLNT103_HTTP</Trace>
<Trace level="3" type="T">Type = H</Trace>
<Trace level="3" type="T">Pipeline = ENTRY</Trace>
<Trace level="3" type="T">Action = EXECUTE</Trace>
<Trace level="3" type="T">Host = XXXXXXX</Trace>
<Trace level="3" type="T">Port = XXXX7</Trace>
<Trace level="3" type="T">Client = 103</Trace>
<Trace level="3" type="T">User = XIAPPLUSER</Trace>
<Trace level="3" type="T">Language = E</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">SSL not active</Trace>
<Trace level="1" type="T">----
</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">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>
check whether connection establishment between XI and R3 is successful or not...
if you are getting same message as above ,,that means ur RFC is working fine...
problem is on r3 side.. for this go to r3 and check moni...

HOW TO RUN ABAP SERVER PROXY IN BACKGROUND?

Hi All,
I have a ABAP Server Proxy running in WAS 6.20. This Server Proxy runs as a foreground Process when the scenario is executed. if we run a scenario with huge load or run scenarios with continuous load, due to the fact that the server proxy runs as a foreground process, the system slows down and has some performance issues. How to handle this issue.Is there a way to run the Server Proxy as a background Job. Please do help me out.
Regards,
Sundararamaprasad.

hi,
here's an idea: encapsulate your proxy call inside an object which can be ran in background.... like an IDoc !
Steps:
create a zidoc in ECC and use it from PI to ECC to send data (instead of your direct abap proxy call).
Afer that, in z_function_module which is used to intregate your zidoc, call your abap proxy.
in WE20 (partner profile), the process mode of your idoc should be of course "Triggered by background program", and then use a job on program RBDAPP01 (with a variant limited to your zidoc) to process your idocs.
Note:
1. the only interest to do that compare to create a real IDoc interface is just (in my mind) to call a common proxy or to want to reuse an existing proxy without too more effort.
2. of course your current proxy call should be asynchronous.
I never tested it, so it's without warranty !
Regards.
Mickael

ABAP Client proxy message not reaching AAE

Hi Experts,
I am facing a strange issue in one of my proxy interfaces. ABAP client Proxy is used to post message to AAE in SAP PI 7.3. The messages are being generated and pushed out of ECC successfully. I can see them in the SXMB_MONI t-code with checkered flag. These messages are reaching the Integartion Engine instaed of the Adapter Engine.
I have configured the following:
1. Sender / Receiver ID in SXMSIF:
2. Configured the corresponding Runtime parameter in SXMB_ADM
I have few other such ABAp client proxy i/f's which work fine and their message are being sent to the Adapter engine. Howveere, only this one interface is posing a problem. What can be the issue?
Please advice.
Thanks in advance.
Elizabeth.

Hi Elizabeth,
It will be great if you could please let me know all the user profile configured in userID of Logon&Security tab of SM59 for connecting ECC system to post the message via AAE.
I have used
SAP_XI_APPL_SERV_USER
SAP_XI_DEVELOPER_J2EE and
SAP_XI_IS_SERV_USER
profiles in my UserID for Basic authentication.
Currently I am doing the same scenario what you have done with integrated configuration.The message is getting failed in ECC with 403 Forbidden error.
Please help me.
Thanks
Ray...

About ABAP Client proxy

Hi Experts,
Through ABAP client proxy I am sending data to PI system, when i execute the calling program then it executes fine, but data is not going to PI system.
I couldn't find any message sent from R/3 in the SXMB_MONI (R/3 system).
R/3 to PI connection is fine.
Regards
Ramesh

I couldn't find any message sent from R/3 in the SXMB_MONI (R/3 system). -
> hope u r not checking in the R3 system for message !!!
Few of our shadow resources, they had similar kind of issue...they configured sender as business service....
so when they run the report program... it was not displayed in MONI..... the reason is agreements as sender business service.... as it cant find the proper receiver, and the proxy comes with Business system details...message wont be processed and cant see in MONI...
so just have look...have u configured like this?

Problem with Consuming ABAP Server Proxy WSDL in InfoPath

Tried to design a InfoPath (MS Office 2003) form from a WSDL file of a web service generated from an ABAP Server Proxy in a NW2004s SP10 system. InfoPath rejected this WSDL with error InfoPath cannot use the selected Web service method for receiving data because the method does not provide valid XML data. Tried other WSDL files from other web services from ABAP Proxy with InfoPath, all got rejected.
Validated the WSDL file with XMLSPY, no error. Tried to import the WSDL into XI 3.0, no error. Also tried the WSDL in .NET C#, also worked fine. It seemed only InfoPath does not like this WSDL from ABAP Proxy.
Created a similar web service in XI 3.0 and InfoPath had no problem with its WSDL. Then I compared the two WSDL files. There are differences. After try and error on changing the differences, I have nailed down to the XML tag that caused the problem. Please see the extracted WSDL line attached at the end. In the XI 3.0 generated WSDL the wsdl:message and the wsdl:part have the same name. In the ABAP Proxy generated WSDL the wsdl:part has the name Parameters which is different from the wsdl:message. After I copied the wsdl:message name to the wsdl:part name, InfoPath accepted the WSDL file without any problem.
I know the fix but I like to find out the root cause. Is this a known issue? Did we miss some configuration setting thats causing this issue? Any help will be much appreciated.
WSDL from NW2004s SP10 ABAP Proxy
<wsdl:message name="RegionR3GetList_Req_MT">
    <wsdl:part name="Parameters" element="tns:RegionR3GetList_Req_MT"/>
</wsdl:message>
<wsdl:message name="RegionR3GetList_Resp_MT">
    <wsdl:part name=" Parameters" element="tns:RegionR3GetList_Resp_MT"/>
</wsdl:message>
WSDL from XI 3.0 Interface
<wsdl:message name="RegionR3GetList_Req_MT">
    <wsdl:part name="RegionR3GetList_Req_MT" element="tns:RegionR3GetList_Req_MT"/>
</wsdl:message>
<wsdl:message name="RegionR3GetList_Resp_MT">
    <wsdl:part name="RegionR3GetList_Resp_MT" element="tns:RegionR3GetList_Resp_MT"/>
</wsdl:message>

Anne Tarnoruder has pointed out to me that her SDN article "Consuming SAP Enterprise Services in a Microsoft Office InfoPath Form" has described the the cause and workaround of this issue on page 9. I am extracting it below and mark this thread as answered. Thanks to Anne but not sure how I can award point to her.
Currently SAP supports only the Document style of WSDL, and not the Microsoft-specific RPC style, which causes a problem when consuming SAP services in the Microsoft environment. In this example, you need to apply a workaround that involves a minor correction of locally-stored WSDL files:
a. In the Project Explorer toolbar, click the Show all files icon and expand the Web reference folder.
b. For each Web reference in the project, perform the following steps:
c. Open the WSDL file, replace all instances of <wsdl:part name="parameters" with <wsdl:part name="parameter" (remove the s in parameters) and save the file.
d. Right-click the Reference.map file and choose Run Custom Tool to invoke a utility that generates code for XML Web services. This recreates the local proxy.

ABAP Consumer Proxy error after upgraded from 7.0 SP14 to 7.01 SP3

The ABAP consumer proxy was created in ECC6 with Netweaver 7.0 SP14. After the system was upgraded to Netweaver 7.01 SP3 the proxy call started to get error back.
The first error message from the service provider said "SoapException: Server did not recognize the value of HTTP Header SOAPAction". This error was resolved by manually putting the correct action in the SOAManager configuration.
Ran the same test again and then the service provider complained about the To field in the SOAP Header. The error message said "SoapHeaderException: SOAP header To was not understood".
Below is the To field in the Requesting XML message from the 7.0 SP14 system that worked fine:
<n3:To soap-env:mustUnderstand="1" xmlns:n3="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope">
http://localhost:50081/AddSix.asmx
</n3:To>
Below is the To field in the Requesting XML message from the 7.01 SP3 system that did not work:
<wsa:To soap-env:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
http://localhost:50081/AddSix.asmx
</wsa:To>
It looks like the issue is with the xmlns:soap-env element that has different values in these two systems. Searched in SDN but could not find any related information. Please help if anyone has experienced similar issue or knows how to fix it.
Thanks,
Jiannan

Got solution from SAP through an OSS message. Below is SAP's solution:
Either the Message ID protocol should be switched off on the SAP
consumer side or turn on this protocol support on the .NET provider.
To switch off the Message ID protocol:
1. start the soa manager
2. find the consumer proxy
3. find the corresponding logical port
4. jump to the 'Messaging' tab
5. choose the 'Suppress ID Transfer' from the dropdown list of the Message ID Protocol field
Besides this setting I also have to specify the operation in the Operation specific tab of the logical port configuration.

Internal table in ABAP Server Proxy

Hi Experts,
I have developed a JDBC to ABAP Proxy scenario.
I have a problem. In my ABAP server proxy I have to import the values into an internal table and pass them to a BAPI for GR creation.
I get an error like. OCCURS 0 is not allowed in OO concept.
Can anyone give me examples on declaring internal table in an ABAP Proxy(OO Concept).
Thanks
AK

Hi
Check this out.
http://help.sap.com/saphelp_nw70/helpdata/EN/fc/eb3660358411d1829f0000e829fbfe/frameset.htm
Cheers

ABAP Clinet Proxy issue

Similar Messages

Maybe you are looking for