Soap - Xi - Bapi (different)

I am having a problem with my scenario -- in which some parameters are passed to xi through webservice reuest, and BAPI have to called ,given some input parameter( that XI recieved from webservice),BAPI now the returned result ,these value r sent back to webservice as responce
can any can give me some input ,what configuration have to be done in IR & ID ?

Hi,
Go thro the following links:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
SOAP to RFC sync scenario
SOAP to RFC(Syn) what are the settings i need to do
I think all the details are provided in the above links.
Regards,
P.Venkat

Similar Messages

Soap - Xi - Bapi (different)(not able to see output)

hello
Firstly thank to Tuhin & Venkataramanan
In reference to my early question dated Posted: Dec 15, 2006 7:59 AM
/people/community.user/blog/2006/10/24/exposing-bapi-as-web-services-through-sap-xi
-- web service request to XI ,than XI call a BAPI ,and the output of BAPI is sent back to web service responce.-- I am using Altova XML Spy to send a web service request ,& getting responce.I had done all configuration in IR, ID.
As i send a request,through Altova XML spy ,and getting a responce to. but in responce
the BAPI Output Data is absent ,only element tags shows zero,
ex-- <customer salary> 0 </customer salary>
it should have some value i.e. like 2300 ,which BAPI is giving
Every thing is working In Itegration monitering-> adapter (RFC) status green
the massage is---
BAPI name is -- BAPI_AR_ACC_GETPERIODBALANCES
Text
BAPI_Cchannel Receiver channel 'BAPI_Cchannel' for party '', service 'account2service' (internal name 'RfcClient[BAPI_Cchannel]')
Client data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=800, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=guest, jco.client.sysnr=00, jco.client.ashost=192.168.100.21}
Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=800, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=guest, jco.client.sysnr=00, jco.client.ashost=192.168.100.21}
Current pool size: 0, max pool size : 1
RFC_HISTORY
- OK: 2006-12-20 10:06:09 IST: Message processed for interface BAPI_AR_ACC_GETPERIODBALANCES
- OK: 2006-12-19 22:37:20 IST: Message processed for interface BAPI_AR_ACC_GETPERIODBALANCES
In SXMB_MONI staus flag is processed succesfully
there in payload ,the out put is there but with the same empty tag ,which i am getting in
as responce in Altova xml spy, as described earlier
there is no mapping exception
I am not able to locate the error
Might be some different mapping required for BAPI Responce to WEBservice responce or else.
Thanks & Regards
Ashutosh

Hi,
Try to execute that BAPI in R3 first.
If u r passing input from XI to BAPI in R3 some number input fields should be preceeded by zeros(means from ur soap request message).
eg if ur vendor no is 169 then u should preceed it with 7 zeroz as vendor no. ia a 10 digit no.
eg 0000000169.
In ur bapi if u r passing any no. then preceed it with required zeros(it is required if u r passing data from XI but not in case of R3 BAPI execution).
Then test ur response message in ur response mapping.
Thanks.
And then check

Best Design : for a SOAP -XI - BAPI ( Multiple )

Hi all,
Need your suggestion on best design to implement a SOAP -XI - BAPI ( Multiple calls ) scenario.
NON SAP Application will make a SOAP service call to XI. This service need to call 2 BAPI's ( 1st call to get some reqd params for second BAPI call ). Also secon call need a commit.
Whats the best design :
1. ABAP server proxy
2. BPM ( to handle multiple calls )
Thanks and cheers,
Anisha.

>>>>>( 1st call to get some reqd params for second BAPI call ). Also secon call need a commit.
1. ABAP server proxy
Here u can have explicit coding and have better control over the process interms u will call the first bapi and the result of it will be passed to exporting parameter of the second bapi as required.
2. BPM ( to handle multiple calls )
performance hinders as pointed out.

How bapi different from session and call transaction?

how bapi different from session and call transaction?
thanks in advance.

For one, Batch Data Communication (BDC) is older. Business Application Programming Interface (BAPI) came later, about 10 years ago (you can see this already from the name, which contains marketese like "business" ).
More important though, they are different technologies. With BDC you build the "batch input transaction" yourself, with an ABAP program which creates the "batch input session" ("Batch-Input-Mappe" in german). You then take that session, like an object, and "run" it on a system (most of the time, this is done on a local system by the administrators, after it has been tested for correctness).
With BAPI, a system (local or remote) exposes its interface to you through some kind of Remote Function Call (RFC). Practically, it tells you: "What do you want to do? Insert that data into Materials Management? Here is the function and the the parameters you have to use for each record". You only work with the Interface - the exposed function. How this function works does not have to interest you. You don't have sessions to "run", you fire your function calls filled with data, one after another and you're done.
BAPI can be run remotely. With BDC, you probably have to call the administrators of the remote system and send them the session you created for them to run. With BDC you go through the whole transaction in one BDC session, with BAPI you may need more than one "BAPI calls" to do this.
With BAPI you don't fill obcure field names with values, you just fill the parameters. You can use a BAPI from inside your ABAP program to let a "business object" do some clearly defined work for you, then you can continue with your code doing other things. You don't do this with BDC. With BDC you write a dedicated program that creates the "session", which is then executed separately.
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a
typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program. Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.
It can also be used for real-time interfaces and custom error handling & logging features. Whereas in Batch Input Sessions, the ABAP
program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the
BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and
invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate
fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are
not available for all application areas.
Business Add-In (BADI) are a new SAP enhancement technique based on ABAP Objects.
They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.

Can we use same SOAP ACTION in different environments?

Hi All,
I have a doubt.
Can we use same SOAP Action URL in different environments i.e suppose say Quality, Production and Pre production.And the Target URL is different in both environments.
If yest what is the impact in different environment.

Hi ,
SOAP action is nothing but operation/method in webservice .
Usually at end system end as a good practice/std they will maintain the same soap action name in all their environments,but it's always better to cross check url and soap action with end system folks before configuring in PI .
We have faced an issue in production some time back ,at target system end they upgraded their server and used new wsdl which is almost similar to existing but one of the operation they duplicated by adding few addition fields but forgot to inform PI system.Though we are using new wsdl but pointed to old soap action .Interface got failed in PROD after investigation we come to know that we are using wrong soap action
Regards
Venkat

IDOC -XI-SOAP one sender different receivers based on condition

Hi All,
I have an IDOC to SOAP scenario.
For each record based on the input flag XI has to send the any one of the request ...like either create or update or delete request. All these message types are a part of single WSDL.
How can i do it?
Thanks in Advance
Jyothsna

hi There are two ways you can do this:
1. Without BPM - Since you have to create all the target messages adn you want either the 1st and second, or the first and third: create two multi-mapping with one and two, and one and three. In the receiver determination check the condtion based on which you decide the second or the third message has to be created and route it to the correct mapping accordingly.
2. with BPM, create all the target mapping. In the BPM check the condtion in the switch and do a send accordingly.
You can do this either on Receievr Determination or on Interface Determination.
Add multiple Receievrs/ Interfaces and then add the conditons on which the target should be choosen
to use Xpath for your receiver det. ref these blogs;
a combination of logics should help you in this case ...
/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
pls reward points if solution found helpfull
regards
chandra.k

Soap body xml different on server

Hello,
I am trying to verify a soap body string using a signature in the soap header. But am getting a slightly modified version of the soap message on the server side handler.
Here is how my client side handler soap body looks:
<n1:xyz xmlns:n1="http://localhost/edm/DocMgmtParametersRetriever">
</n1:xyz>
On the server side,
<n1:xyz xmlns:n1="http://localhost/edm/DocMgmtParametersRetriever"></n1:xyz>
The differences are:
1.There is an extra space between n1:xyz and xmlns on the client side.
2.There is a line break before </n1:xyz> on the client side which is not present on the server side.
When I add following lines of code on client side, the soap body looks the same and server is able to verify the signature.
soapBody = soapBody.replaceAll(" xmlns:"," xmlns:");
soapBody = soapBody.replaceAll("\n","");
soapBody = soapBody.replaceAll("\r\n","");
soapBody = soapBody.replaceAll("\r","");
The server is on weblogic 8.1 sp3. The webservice java client is using saaj-api.jar
Any clue as to why there is a difference?
Thank you

Welcome to the forums.
As a tip for future posts [url https://forums.oracle.com/forums/thread.jspa?threadID=2174552#9360002]2. How do I ask a question on the forums?
That said, a basic example that pulls the contents of the body out is
declare
l_ws_rsp XMLTYPE;
l_body_rsp XMLTYPE;
begin
-- Retrieving the SOAP message
l_ws_rsp := DHL_SOAP_RESPONSE_XMLTYPE;
-- Extracting out the body
SELECT xt.body_xml
 INTO l_body_rsp
 FROM XMLTable(XMLNamespaces('http://schemas.xmlsoap.org/soap/envelope/' AS "SOAP-ENV"),
 '/SOAP-ENV:Envelope/SOAP-ENV:Body/*'
 PASSING l_ws_rsp
 COLUMNS
 body_xml XMLTYPE PATH '.') xt;
 dbms_output.put_line(l_body_rsp.getClobVal());
end;If you Google
XMLTable soap site:forums.oracle.com
you can find plenty of examples on these forums regarding how to parse a web service response.
The bigger question is, what are you going to do with the data in the response. As the example above alludes too, you can actually parse the entire WS response with one SQL statement and return the results as one or more rows. Will you be performing PL/SQL logic on the returned results or will you simply be INSERTing them into the database for something else to use?

Error for SOAP to BAPI scenario

Hi All:
When I am trying to send the message from SOAP client to XI I am getting and Error and also the message is not reaching to MONI.
Is there anything that is required in in SOAP adapter or Modules setting??
Error :
<?xml version='1.0'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>WS-Security privileged action exception</faultstring>
 <detail>
 <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
 <context>XIAdapter</context>
 <code>PrivilegedActionException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:543)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.aii.messaging.srt.BubbleException: WS-Security privileged action exception [null "null"]; nested exception caused by: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: AccessControlException in Method: verify( Message, byte[], CPALookupObject ). The Code-Permission processing failed.
 at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension.doValidate(WSSecurityExtension.java:173)
 at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension.invokeOnRequest(WSSecurityExtension.java:107)
 at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:50)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)
 ... 20 more
Caused by: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: AccessControlException in Method: verify( Message, byte[], CPALookupObject ). The Code-Permission processing failed.
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension.doValidate(WSSecurityExtension.java:157)
 ... 23 more
Caused by: com.sap.aii.af.security.impl.exception.MessageSecurityException: AccessControlException in Method: verify( Message, byte[], CPALookupObject ). The Code-Permission processing failed.
 at com.sap.aii.af.security.MessageSecurityContext.verify(MessageSecurityContext.java:347)
 at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension$VerifyMessageLevelSecurity.run(WSSecurityExtension.java:417)
 ... 25 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Thanks

Hi,
It looks like error because some security settings. Hope you have given the Adapter paarameters correctly.
You can check this SAP note:856597
Also you can try out with XMLSPy ..probably the error is because of usage of wrong port or authentication for that user.
Rgds,
Moorthy

New to SOAP - Can't log in

I'm attempting to talk to one of our development post offices using soapui 3.6.1. On sending a soap login request, I'm getting back a 400 error. On the PO screen, I see
Code:
11:44:51 048 SOAP Action Return Code = ea01
The http trace from soapui shows:
Code:
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "POST /soap HTTP/1.1[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Accept-Encoding: gzip,deflate[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "SOAPAction: "loginRequest"[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "User-Agent: Jakarta Commons-HttpClient/3.1[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Host: 131.156.57.152:7182[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Content-Length: 789[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://schemas.novell.com/2005/01/GroupWise/types" xmlns:met="http://schemas.novell.com/2005/01/GroupWise/methods">[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <soapenv:Header>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <typ:gwTrace>true</typ:gwTrace>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </soapenv:Header>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <soapenv:Body>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:loginRequest>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:auth type="types:PlainText">[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <typ:username>Bob</typ:username>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <typ:password>Test</typ:password>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </met:auth>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:version>1.02</met:version>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " [\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:application>BEEP</met:application>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " [\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:userid>true<met:userid>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " [\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:system>true</met:system>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </met:loginRequest>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </soapenv:Body>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "</soapenv:Envelope>"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "HTTP/1.1 301 Moved Permanently[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "HTTP/1.1 301 Moved Permanently[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Location: http://131.156.57.152:7151/soap[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "POST /soap HTTP/1.1[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Accept-Encoding: gzip,deflate[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "SOAPAction: "loginRequest"[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "User-Agent: Jakarta Commons-HttpClient/3.1[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Content-Length: 789[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Host: 131.156.57.152:7151[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://schemas.novell.com/2005/01/GroupWise/types" xmlns:met="http://schemas.novell.com/2005/01/GroupWise/methods">[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <soapenv:Header>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <typ:gwTrace>true</typ:gwTrace>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </soapenv:Header>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <soapenv:Body>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:loginRequest>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:auth type="types:PlainText">[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <typ:username>Bob</typ:username>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <typ:password>Test</typ:password>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </met:auth>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:version>1.02</met:version>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " [\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:application>BEEP</met:application>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " [\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:userid>true<met:userid>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " [\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:system>true</met:system>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </met:loginRequest>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </soapenv:Body>[\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "</soapenv:Envelope>"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "HTTP/1.1 400 [\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "HTTP/1.1 400 [\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Date: Mon, 04 Apr 2011 11:44:51 GMT[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Server: NetWare GroupWise POA 8.0.2[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Content-Type: text/html[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Pragma: no-cache[\r][\n]"
Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "[\r][\n]"
The PO is GW802 (not sure what HP version) on NetWare 6.5 Sp8. The only doc I've been able to find on ea01 is in the errorCodes document:
Code:
define en WERR_NCSP_BAD_PARAMETER "Bad parameter passed to a NCSP function"
//NGD
//NGD EA01
//NGD Description: Bad parameter (Class 3).
//NGD Conditions: Bad parameter was passed to function.
//NGD Solutions: Contact Customer Support and report the conditions
//NGD under which the error was encountered.
which is interesting, but not especially informative. There are a few references to ea01 in the forumst, mostly by Mike, saying it's a soap error.
I'm hoping that this is something simple that I'm missing. I'll gladly admit to being new at GW SOAP connections, but I think the request I submitted follows the samples in the docs and should return something other than an internal error.

Is SOAP enabled on the POA?
What is the configured SOAP port on the POA?
Is SSL required for SOAP?
Port 7191 is the default port for SOAP.
I see two ports tried: 7182 and 7151.
The SOAP port is different than the HTTP port
on the POA.
Preston
>>> On Monday, April 04, 2011 at 11:06 AM,
dgersic<[email protected]>
wrote:
> I'm attempting to talk to one of our development post offices using
> soapui 3.6.1. On sending a soap login request, I'm getting back a 400
> error. On the PO screen, I see
>
>
> Code:
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ ‑‑‑
>
> 11:44:51 048 SOAP Action Return Code = ea01
>
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ ‑‑‑
>
>
> The http trace from soapui shows:
>
>
> Code:
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ ‑‑‑
>
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "POST /soap HTTP/1.1[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Accept‑Encoding:
gzip,deflate[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Content‑Type:
> text/xml;charset=UTF‑8[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "SOAPAction:
"loginRequest"[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "User‑Agent: Jakarta
> Commons‑HttpClient/3.1[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Host:
131.156.57.152:7182[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Content‑Length: 789[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "<soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:typ="http://schemas.novell.com/2005/01/GroupWise/types"
> xmlns:met="http://schemas.novell.com/2005/01/GroupWise/methods">[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <soapenv:Header>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <typ:gwTrace>true</typ:gwTrace>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </soapenv:Header>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <soapenv:Body>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:loginRequest>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:auth
> type="types:PlainText">[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <typ:username>Bob</typ:username>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <typ:password>Test</typ:password>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </met:auth>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <met:version>1.02</met:version>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
<!‑‑Optional:‑‑>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <met:application>BEEP</met:application>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
<!‑‑Optional:‑‑>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <met:userid>true<met:userid>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
<!‑‑Optional:‑‑>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <met:system>true</met:system>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </met:loginRequest>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </soapenv:Body>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "</soapenv:Envelope>"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "HTTP/1.1 301 Moved
> Permanently[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "HTTP/1.1 301 Moved
> Permanently[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Location:
> http://131.156.57.152:7151/soap[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "POST /soap HTTP/1.1[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Accept‑Encoding:
gzip,deflate[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Content‑Type:
> text/xml;charset=UTF‑8[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "SOAPAction:
"loginRequest"[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "User‑Agent: Jakarta
> Commons‑HttpClient/3.1[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Content‑Length: 789[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "Host:
131.156.57.152:7151[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "<soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:typ="http://schemas.novell.com/2005/01/GroupWise/types"
> xmlns:met="http://schemas.novell.com/2005/01/GroupWise/methods">[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <soapenv:Header>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <typ:gwTrace>true</typ:gwTrace>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </soapenv:Header>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <soapenv:Body>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:loginRequest>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " <met:auth
> type="types:PlainText">[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <typ:username>Bob</typ:username>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <typ:password>Test</typ:password>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </met:auth>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <met:version>1.02</met:version>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
<!‑‑Optional:‑‑>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <met:application>BEEP</met:application>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
<!‑‑Optional:‑‑>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <met:userid>true<met:userid>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
<!‑‑Optional:‑‑>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "
> <met:system>true</met:system>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </met:loginRequest>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> " </soapenv:Body>[\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:>> "</soapenv:Envelope>"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "HTTP/1.1 400 [\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "HTTP/1.1 400 [\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Date: Mon, 04 Apr 2011 11:44:51
> GMT[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Server: NetWare GroupWise POA
> 8.0.2[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Content‑Type:
text/html[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "Pragma: no‑cache[\r][\n]"
> Mon Apr 04 11:44:52 CDT 2011:DEBUG:<< "[\r][\n]"
>
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ ‑‑‑
>
>
> The PO is GW802 (not sure what HP version) on NetWare 6.5 Sp8. The only
> doc I've been able to find on ea01 is in the errorCodes document:
>
>
> Code:
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ ‑‑‑
>
> define en WERR_NCSP_BAD_PARAMETER "Bad parameter passed to a NCSP
function"
> //NGD
> //NGD EA01
> //NGD Description: Bad parameter (Class 3).
> //NGD Conditions: Bad parameter was passed to function.
> //NGD Solutions: Contact Customer Support and report the
> conditions
> //NGD under which the error was encountered.
>
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ ‑‑‑
>
>
> which is interesting, but not especially informative. There are a few
> references to ea01 in the forumst, mostly by Mike, saying it's a soap
> error.
>
> I'm hoping that this is something simple that I'm missing. I'll gladly
> admit to being new at GW SOAP connections, but I think the request I
> submitted follows the samples in the docs and should return something
> other than an internal error.

Default XI parameters in 7.1, soap sender.

Hi,
I have a quick question about Default XI Parameters in Soap sender adapter in PI 7.1.
Why are they not present in PI 7.1( sender interface and sender NS )?
which are mandatory parameters in 7.0.
I was guessing that , this ways we can create a generic soap sender CC.
Does anyone have a exact answer as why it was removed?
Regards,
Venkat..

> Even in PI 7.0 we will add interface name and CC to the URL.
> 1. Do you mean that we are supposed to have NS too along with above entries?
Yes, you should add interface and namespace as it is mentioned in SAP Note 856597
> 2. What do you mean by aligning behavior of SOAP adapter with other adapters?
Other adapters (File, JMS) get interface and namespace from a sender agreement connected to a sender channel. The behaviour of the SOAP adapter was different before.
I was told by development that migrated channels from 7.0 work without any change. If this is not the case, open an OSS ticket for this.
For new channels you have to call the SOAP adapter always with interface name and namespace. The online help is not correct.
Regards
Stefan

Is it possible to create own soap envolpe and body ?

Hi,
I developed a web service and deployed it on Web Logic server and Glassfish server.
But its soap envelope and soap body is different.
Glassfish Request :
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
 <S:Header/>
 <S:Body>
 <ns2:getFunctionXML xmlns:ns2="http://webservices.onwardinfosys.com/">
 <functionName>inotification_pkg_ver4.notifications_count</functionName>
 <parameters>IOS_USER</parameters>
 <appUserName>string</appUserName>
 <appUserPass>string</appUserPass>
 <deviceCode>string</deviceCode>
 </ns2:getFunctionXML>
 </S:Body>
</S:Envelope>
Weblogic Request :
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
 <env:Body>
 <getFunctionXML xmlns="http://webservices.onwardinfosys.com/">
 
 <functionName xmlns="">INOTIFICATION_PKG_VER4.NOTIFICATIONS_COUNT</functionName>
 
 <parameters xmlns="">IOS_USER</parameters>
 
 <appUserName xmlns="">string</appUserName>
 
 <appUserPass xmlns="">string</appUserPass>
 
 <deviceCode xmlns="">string</deviceCode>
 </getFunctionXML>
</env:Body>
</env:Envelope>Is it possible to have only one soap envelope and body even if I am deploying web service to different servers ?
Regards,
Ajay Sharma

Ajay Sharma wrote:
Is it possible to have only one soap envelope and body even if I am deploying web service to different servers ?Sure, it is just XML and XML is just text; you are free to just generate your own stuff in stead of using the webservices stack provided by your appserver. But you don't want to do that because what you have is just fine.

IDOC to SOAP Scenario

Hi All
Scenario is IDOC to SOAP.
As there is SOAP as a receiver side I asked to client to provide me WSDL file so that I can import into my PI. But Client sent me a BAPI structure instead of WSDL file.
So I want to ask is this posible to implement receiver SOAP using BAPI.
Regards
Dheeraj Kumar

Hi,
>>>Receiver side is portal so how come I can use RFC adapter?
portal has nothing to do with bapis - it's a display later for documents from the backend system (if we're talking about SAP)
so instead of doing a SOAP call you can use RFC adapter to connect directly to the "BAPI" engine - which is ERP
if you want to use SOAP - you need a WSDL - but the WSDL can be generated from BAPI too (keep that in mind)
Regards,
Michal Krawczyk

Error while mapping the BAPI exception to the Fault Messge

Hi
I have a scenario SOAP to BAPI ...
when i try test the scenarion from Altova XML SPY for BAPI exception ... i am getting the following error....
When i tried to map the BAPI exception to the Fault Message its giving me the error...
com.sap.aii.af.ra.ms.api.DeliveryException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Unexpected length of element <sap:Error><sap:ApplicationFaultMessageNamespace> =

Hi,
Fault messages can be used for inbound proxies....for BAPI also it can be used i am also not sure....How are you tracking that the data is getting posted into the SAP table with the help of BAPI?
Thanks
Arijit

How to implement Exception Handling for soap to RFC sync interface...

Dear Experts,
we have an interface like soap to Rfc sync, already develepment is done and moved to production. but we are getting some quatitity is greater than item then it is throwing an error below. i want to handle that exception in XI level.
please guide i am not found any document for this type of interface.
Please suggest what can i do for this. Please share me the screen shot for this.
Error Log:
<?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>Application</SAP:Category>
<SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="urn:sap-com:document:sap:rfc:functions">Z_DEPOT_DISPATCH.Exception</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
<rfc:Z_DEPOT_DISPATCH.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><Name>RFC_ERROR_SYSTEM_FAILURE</Name><Text>Delivery quantity is greater than target quantity 10.000 MT</Text><Message><ID>VL</ID><Number>363</Number></Message><Attributes><V1>10.000</V1><V2>MT</V2></Attributes></rfc:Z_DEPOT_DISPATCH.Exception>
Regards,
Kiran Polani

Dear All,
This is clearly soap to rfc interface and we are using currently PI 7.0. This is a validation of BAPI, BAPI is not accepting the field of "Quantity is some value". The quatity is greater than the amount BAPI is throwing an error like "APPLICATION_ERROR". Is it possbile to validate in XI Level.
Soap --> XI--> BAPI(Request)
BAPI--> XI-->Soap(Response)( in this step what ever message return by bapi those error message not getting 3 rd party application).
here by catching that error and i should throw to 3rd party application.
is it possible to handle this or not.?
If it is possible in Fault Mapping/Fault message type please give me the steps or document for me.
I am new for fault mapping?
Please help me on this.
Regards,
Kiran Polani

Web service SOAP response issue

Hi,*
We are upgrading system from ECC 5.0 to ECC 6.0. All of our webservices were created in new system with SOAManager configuration.
When the consumer systsem is trying to consume one of the webservice the XML response is different when compared with the one tested from ECC 5.0.
ECC 6.0 is returning different XML for the same web service. The consuming system "Cold Fusion' is expecting the SOAP XML in different place.
When we tested the same webservice in WS navigator it did gave the response. Also the issue is with this webservice only.
We have re created the webservice again and tested from cold fusion and the same response.
The issue is with only this webservice.
Regards,
Prashanth.

Christoph,
Firstly LiveCycle Designer 8.2 is still not supported to develop forms as per my knowledge. The latest version compatible for SAP Interactive Forms is ALD 8.0.
There is a difference between Acrobat based forms and LiveCycle forms and based on your coding it looks to me that you are trying to create a LiveCycle based form with coding of Acrobat which is not supported in LiveCycle Desginer, which is why you may be getting the error.
I hope that does not confuse you, so may check this [link|http://www.acrobatusers.com/articles/2006/08/designer_or_forms/index.php] for some clear information on what point I was trying to make.
Chintan

Soap - Xi - Bapi (different)

Similar Messages

Maybe you are looking for