IDoc u2013 HTTP Using SAP BC

Hi Experts,
I want to create the following scenario using SAP Business Connector.
SAP system sends an IDoc asynchronously to SAP BC. The SAP BC converts the IDoc into a standard IDoc XML document. After the conversion the SAP BC sends the XML document synchronously to an external URL of a business partner via HTTP.
Can anyone provide me with a document consisting of all the steps involved for the above configuration, right from SAP system to BC system.
Thanks & Regards,
Amit

hi,
so you're doing rosseta
>>can you please let me know from where can i get this file????
the lastest version of best practices cd can be downloaded from:
service.sap.com/swdc
then path:
Installations and Upgrades" SAP Best Practices" SAP BP FOR HIGH TECH" HIGH TECH - V1.600
but it's for 1.600 version and you're file should be for V1.471
so maybe you need to ask SAP where to download it if V1.600 DVD will not work
but try the link
Regards,
Michal Krawczyk

Similar Messages

IDOC-- XI-- HTTP (non-sap) 403 Forbidden

Hi guys,
When I execute my scenario IDOC>XI>HTTP (non-sap) URL address Asynchr. The receiver receives the message correctly
but in my XI monitoring the message stands in error mode.
At first sight this is not a big problem because the receiver receives the message correctly
but it would be nice if the message would stand in processed succesfully.
The error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3>Service Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 403 reason Forbidden explanation Service Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please don't redirect me to an old topic because I have read all topics and none of them could help me. :s
TIA
Message was edited by: Peter Delve

Hi,
this is the describtion of W3ORG:
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
May contact web admin.
Regards
Matt

IDoc to HTTP using BPM

Hi,
My Requirement is IDoc(Async)HTTP(sync)-IDoc(Async) using BPM
and there is a condition if i will not get response from HTTP then i need to send error message to ECC(IDoc).
could you please provide me details steps in IR and ID.
Thanks
Girii

HI,
please go through below blog instead of file you are using IDoc and instead of rfc you are using HTTP,
http://wiki.sdn.sap.com/wiki/display/XI/FILETORFCTOFILEwithBPM
regards,
ganesh.

IDOC Outbound processing using SAP BC

Hello Experts,
I am trying to develop a simple IDOC outbound processing scenario using SAP BC. In this an IDOC from SAP ECC server will be sent to an external webserver via SAP BC, for this i have done all the setup i.e Establishing connection between SAP BC & SAP ECC, ALE settings, creating a new Routing rule, but when i try to run this scenario, i am getting the following error 'IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE' , is there any way to import the IDOC metadata, just like how we do in SAP XI using IDX2. Please Help...
Thanks & Regards,
Amit Naik

Hi Michal,
Following is the error which i am getting :-
2009-03-12 21:56:59 IST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.
     at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)
     at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)
     at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)
     at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
     at com.sap.conn.idoc.jco.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:88)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:141)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2621)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2298)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2130)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2012)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1903)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:258)
     at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:320)
     at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:219)
     at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
     at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
Thanks & Regards,
Amit

IDoc to HTTP: Using acknowledgments

Hi friends.
I know the HTTP Adapter does not support acknowledgments.
But we had a scenario in which we send an IDoc from SAP and transformed it in a HTTP Call.
We get back to the SAP system a aleaud Ack IDoc from PI. It reports that the communication between SAP and PI works.
The ack was not for the sucessfully or unsucessfully HTTP call.
Now we updated our PI 7.0 system from service level 12 to 20.
Since the update there comes no ALEAUD IDoc back.
Any replies to that problem?
Thanks!!!
Stefan

HI,
please go through below blog instead of file you are using IDoc and instead of rfc you are using HTTP,
http://wiki.sdn.sap.com/wiki/display/XI/FILETORFCTOFILEwithBPM
regards,
ganesh.

IDoc structure mismatch between SAP R/3 and PI

Hi,
There is an interface in PI which receives IDoc from SAP R/3 system. I have been facing an issue of IDoc structure mismatch (in terms of data present in it) between SAP R/3 and when PI receives the IDoc.
To be more precise,
In SAP R/3 system, the value ABC is present in the field DOCNUM in the IDoc.
But when the PI receives the same IDoc from SAP R/3 (as seen in Integration Engine), the value ABC is present in a different field and the DOCNUM field is empty.
<DOCNUM></DOCNUM>
<ARCKEY>ABC</ARCKEY>
The first step towards resolution was to delete and reimport the IDoc metadata from SAP R/3 in PI system using IDX2, which did not help in this case.
Could anyone please help in resolving the field mismatch between the IDoc triggered from SAP R/3 and the IDoc received by PI.
Regards,
Prajeet

Hi Prajeet,
it's long ago but your question has not been finally solved, so let me try to give you an answer. We are facing the same problem after patching our PI.
I think the reason for the different behaviour is related to SAP note 1233908, where SAP has changed the IDoc adapter.
https://service.sap.com/sap/support/notes/1233908
Regards,
Lars

How to use SAP XI to get Inspection Lot IDOC when Insp. lot is created

I want to create a 3rd party .NET app that gets an Inspection Lot IDOC when an inspection lot is created, gather the inspection results, then push the results back to SAP in an IDOC. How do I use SAP XI to do that? I developed an HTTP listener .NET app and configured a sender communications channel for the SAP System and a receiver connunications channel for the HTTP adapter in the XI integration scenario, but how do I configure the XI integration scenario to send my app an IDOC when an inspection lot is created, and what IDOCs do I use?
Thanks,

Hi Ed
I think you can use
IDOC TYPES : QALITY01, QALITY02
in XI you can create
IDOC to HTTP as a scenario
IDOC need to be triggered from SAP system and you can import the IDOC metadata into XI from SAP
Check this thread it will help
Re: IDOC to HTTP
Thanks
Gaurav

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

Send Idoc to AS2 System via HTTP using XI

Hi,
We need to send Invoice Idocs as XML files from SAP R/3 system to external AS2 system using XI. The communication will happen over HTTP using certificate. I tried using Plain HTTP adapter , but the message went into error 'ATTRIBUTE_CLIENT'. Why this error ?
I came across some blogs saying about Seeburger AS2 adapter , but is this the only possible way ?
Kindly guide.
Thanks.
Tushar

Yes , AS2 adapter is the solution for it.
Refer all the below threads for AS2 information and configuration which need to do for B2B integration:
SEEBURGER EDI adapter
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.

In sap 4.7 ver i want to dispatch an Idoc through http in xml format

Hi
Here i am giving the brief scenario of about my
requirements "::::
Our organization need to receive an IDoc through
HTTP into XML format then we have to send an acknowledgement back to USA (external system
located)
then we hav eto process tha tIDoc an dsend it back
to the edi 850 ...
we are not using Sap Business Connector
Plz send the suggestions as soon as possible
I really appreciated if u can give the suggestions
regarding my business scenario ..
without using any thirdparty tool in sap 4.7 version it is possible how can i do that ??
Thanks & Regards ,
bak

The exact error message I'm getting is :
ABAP XML formatting error in XML node of type "element", name: "abap"

How to Use IDOC and ALE in SAP?

Hi anybody,
I want Use Idoc and ALE in sap ABAP. What is inbound and outbout process of IDOC?
Please give me sample code for Idoc . and Sample code for ALE.
anybody Please tell me.
Thanks
Regards,
S.Muthu.
IT Dept.

hi,
Follow the link for step by step ALE/IDOC tutorials.
http://www.sapmaterial.com/idoc_sample.html
http://www.****************/Tutorials/ALE/ALEMainPage.htm
An IDoc is not a process.
The term IDoc stands for intermediate document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. An IDoc is created as a result of executing an outbound ALE or EDI process. In an inbound ALE or EDI process, an IDoc serves as input to create an application document.
IDocs are stored in the database.
In the SAP system, they are stored in database tables. Several utilities are available to display the information contained in an IDoc and present it in different ways. For details, refer to Chapter 11, "Monitoring the Interface."
Every IDoc has a unique number.
When an IDoc is generated in the system, a unique number is assigned to it. This number is unique within a client.
IDocs are independent of the sending and receiving systems. They can be used for SAP-to-SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data.
IDocs are based on EDI standards, ANSI ASC X12 and EDIFACT, but are closer to the EDIFACT standards. The size and format of data elements in an IDoc type are derived from these standards wherever applicable. For example, if a material number is represented by 20 characters in an EDIFACT message, the corresponding data element in the IDoc is also 20 characters. If there is a conflict in data size between standards, the one with greater length is adopted. This approach ensures compatibility with most standards.
IDocs are independent of the direction of data exchange. An inbound and an outbound process can use an IDoc. For example, the ORDERS01 IDoc is used by the Purchasing module to send a purchase order, and is also used by the Sales and Distribution module to accept a sales order. Using this technique avoids creating redundant IDoc types for the same information.
IDocs can be viewed in a text editor and do not contain any binary data. Data is stored in character format. When transferred to the operating system, an IDoc is stored in a file in text format and can be viewed using a regular text editor. However, the contents make sense only if you understand the structure and format of the data in that IDoc. In the Appendix, "FAQs, User Exits, and Miscellaneous Resources," you will find an example of an IDoc file.
Hope this helps, Do reward.
Edited by: Runal Singh on Mar 5, 2008 6:09 PM

Use XMLSpy as a SOAP client to POST message to PI u2013 HTTP error

Hello all,
I have developed a scenario in PI 7.0. The sender is SOAP channel and PI acts like a web service server. The WSDL has been generated in ID using the following URL (https://dalcxid00:8001/XISOAPAdapter/MessageServlet?channel= :BS_Ecomm_WS_FG_Order:CC_Orders_SOAP_Sender_FG). I am using XMLspy to test the web service but getting the following error.
HTTP error: could not POST file u2018/XISOAPAdapter/MessageServlet?channel= :BS_Ecomm_WS_FG_Order:CC_Orders_SOAP_Sender_FG&version=3.0&Sender.Service=BS_Ecomm_WS_FG_Order&Interface=http%3A%2F%2Ffossil.com%2Fecomm%2Fglobal%2Forders%5EMI_Order_Ecomu2019 on server u2018dalcxid00u2019 (0)
The port above is a HTTPS port. Does any body has successfully using XMLSpy to test web service in HTTPS? If not, any other good tool can be used for the testing?
Thanks in advance for your help,
Shawn Chen

Hi
a) Are u using client authentication such as logon credentials user/password? If so , input logon credentials.
If not, check https without client authentication.
b) Are u tesing your webservice within firewall boundary? if not, it might not work.
Please see the link ..
http://help.sap.com/saphelp_nw70/helpdata/EN/14/ef2940cbf2195de10000000a1550b0/frameset.htm
HTTPS Connectivity via Sender SOAP Adapter
Thanks
Baskar
Edited by: JAVAGUY on Nov 30, 2010 6:14 PM

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

Build daily Big flat file using SAP R/3 material master data

Hi all,
I must build an interface between SAP R/3 4.7 and an external application
Daily a flat file must be generated contaning Material data in full exchange mode
(volume 100 000 materials, <10 fields => ~ File of 30Mo)
No complex mapping, only format mapping (Ex : Price quantity...)
I don't know yet if I will use Idocs or BAPI to extract data. However, I'm sure I must use multiple inbound messages because of volume
After reading documentation, I consider the both following solutions to manage it :
1) A simple asynchronous interface with a file adapter in construction mode APPEND to build flat file progressively with arrival of SAP messages
=>
viable solution ?
Is there problem of concurrent access to file in such a solution ?
(idocs or bapi data will be processed ones following the others )
2) BPM Collecting and Bundling Messages - One Interface
(Unlimited Loop with Deadline trigger correspondint to time I must build flat file)
=>
Each SAP message is a small message but the outbound XML will represent a 30 Mo flat file => Is it a problem ??
Which solution do you advise ?
Is there another ?
Last question : (more general one)
In such scenario, I can't see XI-value added comparing a creation of flat file directly with R/3.
I will generate a big number of idocs, use a big part of XI memory ...
Can you give me your opinion about it ?
Thanks a lot
Best regards
Jean-Charles
Message was edited by:
Jean-Charles
Message was edited by:
Jean-Charles

Hi Jean-Charles,
>>>volume 100 000 materials, <10 fields => ~ File of 30Mo
You have a performance task...
>>>Is there problem of concurrent access to file in such a solution ?
No, the adapter framework has its own queueing, the message would be stored and executed later. If sequence is important, you can use EOIO as well.
>>>BPM Collecting and Bundling Messages - One Interface
BPM is not required in your case, you should avoid becoz of performance task. You can append at file adapter, no problem. Bundling and splitting is even possible at Integration Server without BPM.
>>>Each SAP message is a small message but the outbound XML will represent a 30 Mo flat file => Is it a problem ??
Avoid using BAD words
>>>Each SAP message is a small message but the outbound XML will represent a 30 Mo flat file => Is it a problem ??
Use the <a href="https://websmp110.sap-ag.de/quicksizing">Quick Sizer</a> for sizing the hardware.
Regards,
Udo

How to convert IDoc-XML to native Idoc-File with in SAP XI/PI

Hello,
I have a problem to Create an native IDoc-Format for an File-Receiver.
The scenario:
I get an Idoc (ZMATMAS) from a SAP System to an MATMAS-exchange-scenario. One of the non-SAP-receiver-systems needs an other native IDoc-Format as File. So I have to map the ZMATMAS to the receiver Format and write this as File. The problem is, that this file contains the data as IDoc-XML and not as native IDoc-format.
Has anybody an idea for this problem?

U need to use sender idoc adapter and file receiver adapter.
U can do file content conversion at receiver end.
Content Conversion is basically to convert a text file that contains complex structures into an XML source format and vice versa. It is present only in the File Adapter because it is one of the message protocol which will convert the structure to a desired format.
There are many blogs for File Content Conversion. Some of them are listed hereunder:-
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
You may also check the FCC documentation for Sender and Receiver:-
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm

IDoc u2013 HTTP Using SAP BC

Similar Messages

Maybe you are looking for