Sending MATMAS05 IDOC via XML-HTTP Interface (without XI)

Dear all,
I have to send the MATMAS05 IDOC via XML-SOAP-HTTP Interface to a subsystem. Sending works (the sub-system receives the SOAP-Request with the MATMAS05 as Body). So far so good. Now the SAP System is waiting for an answer (synchronous communication). How should this answer look like?
We receive the Error EA390 "Problem with SOAP Class" - execute_processing: entry result table
Can anybody give me a hint how the response should look like.
Many thanks and best regards
Roman

Hello Sven,
we find a solution. As far as I remember, there is a flag to send without waiting for answer (or technical better to not rely on SOAP standard).
Look in WE21 and the XML_HTTP Port you use. Uncheck the "SOAP Protocol" flag. Then it should work.
HTH and Best regards
Roman

Similar Messages

RFC to send an idoc PEXR2002 using HTTP connection to an external server

Hi,
Iam working on RFC to send an idoc PEXR2002 using HTTP connection to an external server. first time iam working on this particular scenario on http connections. please clarify on this and explai me in detail about this.
Points will be rewarded **
Thanks & Regards,
Ravi

HI Jagruthi,
Have you loaded the metadata into the XI system by using IDX2?
If it is done then try to delete once and do once again.
And also delete the IDoc from IR and reimport the IDoc and activate it once again.
Regards
Goli Sridhar

XML/HTTP interface for AccessManager 7.1

Hello,
I'm using the XML/HTTP interface of Access Manager 7.1
(such as: http://server_name.domain_name:port/service_deploy_uri/authservice)
and it works fine, not only the interface for authservice
but policyservice and sessionservice. This is good.
(For some reason I can't use Java/C API, nor the policy agent)
Problem is, I couldn't find any description about the XML/HTTP interface for policyservice and sessionservice in the Access Manager 7.1 documents.
(for authservice, I found at
http://docs.sun.com/app/docs/doc/819-4675/adufv?a=view
and
http://docs.sun.com/source/817-7644/appB_sessionlifecycle.html
though the latter one is the document for older version of Access Manager)
Is there any documents for XML/HTTP interface of Access Manager 7.1?
or, officially we should not use this interface?
Windsor

Thanx again. We will continue to use Access Manager 7.1 for a certain period of time so we can't use REST interfaces nor Identity Services.
If we can use these XML/HTTP interface in AM7.1, we will be very happy. Otherwise we have to build a proxy server (talk to Access Manager by C API and talk to clients by XML/HTTP way) but technically it seems completely wasteful because you can talk to Access Manager by XML/HTTP directly.
Is it possible to get any (paid) support
about these XML/HTTP interfaces from Sun Microsystems?
(we don't need any "version-up" support, but just only AM7.1 support for these interfaces)

Problem while sending idoc over xml http

Hello all,
We have developed a scenario to send the idocs from SAP to Java(Tomcat) web server. Its was working fine. But SOMETIMES the idoc status will be set to 03(Data passede to port OK) on the SAP side, but no data(no xml string) received in the web server. is this depends on the size of the idoc? or due to some JVM settings of webserver??Could someone suggest us a way to identify the problem.
Thanks in advance
Regards,
Vishu.

Asit Purbey,
i have send 2 idocs with different number of segments. idoc with 2 segments is successfully received in the webserver, but the idoc with 100 segments didnt received in the webserver. Then i processed RBDMOIND but both the idocs remain in status 03.. Please help me to figure out the problem......
Regards,
Vishu.

Retrigger failed IDOC with XML HTTP port

Hi Friends,
Can anyone suggest me how to retrigger failed IDOCS in we05 with XML HTTP port, any other than we19 to retrigger? I have already gone through all the links in sdn, nothing seems to work, have tried program RSMIPROACT also.
Thanks & Regards
Ridhima

Hello,
Please check the below SAP Note:
857321 - Resending HTTP IDocs automatically in status 02
-Rahul

How can we send Error Idocs via mail

Hi,
I have read read through forums and understood that it can be achieved either through workflow or through report using table edidd & edids.
If workflow option is used , does the mail trigger for every error idoc ? How can we send daily error report to user say by EOD containing all error idocs using all possible options.
Regards,
Rachel

Rachel,
I dont think so any direct Report will be available just to get Error IDOCs details. Although you can create a simple report to read the tables. An example is in below link.
http://wiki.scn.sap.com/wiki/display/Snippets/Custom+report+for+IDOC+Monitoring
Also, you can create a Query of EDIDC and EDIDS tables to obatin relevant information.
Thanks,
Ravi

HTTP 500 Error while using XML HTTP Port for idoc

Hi,
I am trying to send CRM idocs via XML Http instead of usual t-rfc.
After standard idoc - pi configs i get the below error.
transferring the IDoc by HTTP, the return code with the message '500Error during parsing of SOAP header' has occurred.
In BD87 I get the below error.
The target address was: http://yyyyyy.XXX.local:800X/sap/xi/engine?type=entry
I get the http 500 error as:-
Check whether the IDoc can be sent again.
It is unfortunately not possible to determine automatically whether the IDoc has in fact arrived in the target system and the error occurred afterwards
Any idea on how to trouble shoot or resolve this.
Regards,
Anirban

Hi Anirban,
Follow the below links for troubleshooting.
Troubleshooting File-to-IDOC Scenario in XI.
The specified item was not found.
Regards,
Leela

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

Problems with sending IDOC via RFC from Unicode to NonUnic

Hello
I have following problem, sending an IDOC via RFC from Unicode to Non Unicode System. IDoc is not sent with error: codepage of receiver system cant determined. receiver destination was: Message no. B1999
I have tried different options in sm59, but it didnt help.
Any ideas? The recipient system is rather old, version 4.0

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

PO via XML in R/3 or ECC 6.0

Dear Friends,
Did anyone establish the functionality of sending Purchase Orders via XML in R/3 or ECC 6.0 (there is no SRM existing). I knew that in SRM there is a default functionality existing, but want to know how can the same approach be achieved from R/3 Enterprise version or ECC 6.0.
Kindly advise me with your inputs on how can this be achieved.
Appreciate your valuable inputs.
Kind Regards,
KP

Hi,
Please Go thru this Link--> Hope this will be helpful to you
http://help.sap.com/saphelp_srm30/helpdata/en/23/00dd3aeedb7445e10000000a114084/content.htm

Automatically process IDoc to XML File port

Hi everybody,
I want to send two different IDocs via "XML File" port using change pointers and the distribution modell (one SAP standard, one custom).
I maintained the distribution model and created outbound parameters in partner profile (WE20). Both are set to "Transfer IDoc Immed.".
1.
Now I change some master data and the change pointers are created. I run RBDMIDOC for both message types and both IDocs are created. But unfortunately they stuck at staus "30 - Idoc ready for dispatch" (yellow). I need to run RSEOUT00 to create the XML files.
Is it possible to avoid a job that runs this report? I want the IDocs to be processed automatically right after creation.
The really strange thing about this is, that it used to work for the standard IDoc (BOMMAT). But I might have changed some settings to get my custom IDoc work too and now both stuck at status 30?! This is what bothers me most...
2.
When the XML files are created (at the moment after running RSEOUT00) the status in WE05 is "03 - Data passed to port OK" (yellow).
Why is this light still yellow? Everything is fine, the file was created, it should be green. Is there anything I can do?
Thanks and best regards,
Oliver

Hi,
thanks for your suggestions.
Unfortunately this did not solve my problems.
1)
OUTMOD for both messages was 2 (which should be ok). Changing it to 1 did not have any affect.
At least BOMMAT works again (both with OUTMOD 1 and 2). But my custom IDoc still does not get processed automatically.
2)
Running report RBDMOIND did not change the status of my IDocs. Please keep in mind that it is no tRFC port, but XML File port.
Best regards,
Oliver

Reg: Port - XML HTTP

Hi All
Our Client is sending data from SAP to Non SAP Through IDOC Using XML HTTP port .
IDoc is a custom idoc.
Out bound idoc is generating and posting to Non sap system .. no issues...But idoc is generating with 30 Status even though
in Partner profile we marked as Trigger idoc immedeatley. Client can use RSEOUT00 to post idoc by scheduling the Job.
Question is that....using XML HTTP port if an idoc is posted can we Trigger idoc immedeatley ???
Thanks
Ram

Hi Anirban,
Follow the below links for troubleshooting.
Troubleshooting File-to-IDOC Scenario in XI.
The specified item was not found.
Regards,
Leela

Issue with the configuration of http xml port for sending the idoc

Hello,
      I am planning to send multiple idocs in a single file using http xml port.
Presently I am trying to send a single idoc, but am having the issue.
I am trying to create a RFC for HTTP XML port of type H i.e. HTTP Connection to ABAP System
In the how to guide for - How Tou2026 Send Multiple IDocs Within One XI Message
( https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b )
the following parameters are defined for the path prefix -
RFC destination of type H (HTTP Connection to R/3 System).
Specify the path prefix as follows:
/sap/xi/adapter_plain/
?namespace=< your namespace>
&interface=<IDoc_Type>
&service=<Sender System>
&qos=EO (or EOIO).
I am trying to use the following prefix -
/sap/xi/adapter_plain/
?namespace=urn:sap-com:document:sap:idoc:messages ( this is the standard namespace of SAP for all the idocs)
&interface=DEBMAS05 (Idoc type )
&service=SNDLS100 ( ECC system name )
&qos=EOIO
On testing the RFC connection, I am getting the error of page not found.
Can anyone please give me pointers for the issue.
Regards,
Mayank

Thanks Barry!!!
Now I am getting a different message.
In RFC...it is giving me the following message ->
Status HTTP Response     204
Status Text     Body is empty
In case of Idoc, the status is till 02...
the error description for the idoc is --
"When transferring the IDoc by HTTP, the return code with the message '500<SAP:Error><SAP:Category>XIServer</SAP:Category><S' has occurred.
The target address was: http://emgeccsnd1:8001/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interf
Check whether the IDoc can be sent again.
It is unfortunately not possible to determine automatically whether the IDoc has in fact arrived in the target system and the error occurred afterwards"
I am still not able to resolve the issue.
Regards,
Mayank

IDOC to XML using HTTP

Hi Friends,
Is there any possibilities to Convert IDOCs as XML using HTTP Adapter in SAP PI?
Because in my Scenario i need to send Idocs from ECC to Red Prariie using SAP PI.
Also is it there any possibilities using FTPS?
Please help me.
Thanks.

Hi PIstarter,
Sure this is possible. Just treat the IDoc like any other Service Interface that you use in the HTTP Receiver Adapter. You can even use the no-mapping approach if no additional processing is required by PI.
Hope this helps,
Greg

IDOC to XML and send it to SAP SCM SNC(Supplier network colloboration)

I am currently working in a project which I need to send the PO IDOC to PI (which is working fine) and convert it to xml and send it to SNC system which is SAP SCM system. I am not sure if this is going to be an IDOC or xml , I wasn't given more information as all of us are new to this SNC environment. Any help would highly appreciated.
Thanks,
Menaga

Following are the interface mappings in use for the Purchase Order scenario from ERP to SNC
1. create purchase order -> display PO (ERP to SNC)
OrdersOrders05_ReplenishmentOrderNotification_01
2. Create or change PO -> Display updated PO (ERP to SNC)
OrdchgOrders05_ReplenishmentOrderNotification_01
3. Confirm PO or change in web UI (SNC to ERP)
ReplenishmentOrderConfirmation_OrdrspOrders05_01
4. Create or Change Purchase Order -> Receive and Display Purchase Order (ERP to SNC)
OrdntfOrdint01_ReplenishmentOrderNotification_01
Just configure the Integration scenario "MaintainPurchase_Order_Processing" from http://sap.com/xi/SNC/Global namespace present in SNC 5.1 SWC
in your ID.
In SNC Scenarios Idocs will be sent and received from ERP and ABAP Proxies (Client/ Server) used at SNC side. You do not have to code for the ABAP Proxies as the proxies will already be inmplemented in your SNC system.
So 1. configure your SNC system for ABAP Proxy configuration
2. Configure the Integration scenario "MaintainPurchase_Order_Processing" in ID
3. Configure your ERP system for IDoc send/ receive
You are done.

Sending MATMAS05 IDOC via XML-HTTP Interface (without XI)

Similar Messages

Maybe you are looking for