Send/receive IDOCs to SOLMAN system using AS2 protocol!

Hi All,
I want to send/receive IDOC file to/from web based SOLMAN system. Currently I'm using FTP server to send/receive IDOC file.
As of now the current process is to send the IDOCs from ECC to FTP server and from FTP to third party and vice-versa. But due to some constraints, I'm bound to use web based SOLMAN system. Please, can you let me know how to send/receive IDOC files to SOLMAN. Is there standrad FM/method to connect to SOLMAN from ECC as in case of FTP we have FM 'FTP_CONNECT'. Heard that same functionality in case of SOLMAN can be achieved through AS2 protocol.
Kindly help.
Thanks.
Regards,
Mukesh

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

Similar Messages

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

Receiving idocs from multiple systems

I got to receive two different idocs from two differnt systems and both are to be mapped to one target structre. Is this scenario is possible without using BPM ? If so coupld you plz advise the design ? Is there any literature which talks abt this scenario ?
thanks
kumar

Hi Kumar,
Your scenarios look like n:1,like more than one sender .
You can implement your scenarios using BPM very easily.
Uisng BPM you can colect IDOCS from SAP system you can send.
Please search in sdn blogs you wil find it,
if you are unable to find let me know i will give u the links.
Regards,
Raj

What all configurations to do in SAP R/3 to send an iDOC to XI system

I want to send an idoc from an SAP R/3 ECC5.0 to an XI system Netweaver 04's.
Pls let me know the STEPS I HAVE TO DO IN MY r/3 SYSTEM .
I have created the RFC destination in R/3 and XI system but still the idoc is not going into XI system.
It would be a great help if i can get step bu step guide for the configurations i have to do in R/3 .

Hi,
First check the status , with we02
Also see the below links
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI. Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
Regards
Chilla

Modify control record and send out to external (TAMA) system using ALE

Hi All,
I have a scenario to send idoc from ECC 5.0 to 3.1R/3 and then to TAMA system (external system-through TRFC)
In the inbound process code of 3.1R/3, I have to write a custom FM to modify the control record and point to TAMA system and then send it out to TAMA system.
Has anybody got idea about this and what function module need to use for modifying the control record and send it out. Any help is really appreciated
Thanks
Ricky

Hi Ricky,
To access IDoc data and modify it in your custom FM, you could investigate the following FM's:
EDI_DOCUMENT_OPEN_FOR_PROCESS
EDI_SEGMENTS_GET_ALL
They should allow you to access the EDIDD, EDIDC tables.
The IDoc related functions are contained in the function group EDI1, it may be helpful to start from there.

Problems while sending/receiving IDOCs

Hi,
I am trying to store IDOC data to MS access database. I created a scenario and able to activate that successfully, but after sending IDOC from SAP, in SXMB_MONI I can see status as "Message Processed succesfully" flag, and acknowledgement status as "Still awaiting acknowledgement" and data is not stored in database. Anybody having any idea about this problem.
Another problem what I am facing is, when sending an XML file from a file server to SAP(through XI), I am getting status as " Scheduled for outbound processing". Receiver determination, Interface determination, Sender & receiver agreements all are present and correct. Any help?

Hi,
Check what chris has said....Also in SXMB_MONI check the status of the message on the outbound side(by scrolling to the right)...This will say whether it has been transferred to the Adapter Engine....
For the second problem, pls check whether all your queues are registered. All queues can be registed from transaction SXMB_ADM...then doublwe click on "Manage Queues"...and choose the register queues and execute...
Thanks,
Renjith

Connection with external System using AS2/SFTP adapter.

Hi All,
I need to use SFTP/AS2 to connect to an external Server which is not in our landscape.
Can anybody could help whether i need to create a party on the Sender side as sender system is an external Server.
I have gone through many docs but i am not clear when to use party and when not..?
Regards,
Rahul

Hi Rahul
Whether to use a party or not is both an architectural question as well as a development question.
Architecturally, if an external server is not in your landscape and belongs to a different company/entity, your scenario would be a B2B process. You can refer to the below link for more details about B2B, but I've included a short snippet below too.
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/c7a475da5e31ebe10000000a42189b/content.htm
Using a communication party, you address a company that is involved in a B2B process.
The (technical) name of the communication party (for example Bosch) is the identifier for the company within an Integration Directory. To be able to identify the company during any external communication using a globally unique ID, you specify alternative identifiers for a communication party. For external communication, the name of the communication party that is known internally is mapped to the ID. A particular identifier is specified in the communication channel (see below).
In terms of development, not all adapters (FTP, SFTP, SOAP, etc) require the use of a party object when you develop a B2B integration scenario. There are companies which have implemented all B2B scenarios using those adapters in an A2A style (using just Business Systems.)
As Harish has mentioned, if you use the Seeburger AS2 adapter, you will need the party object (AS2ID is configured there), but if you use the SFTP adapter, it is optional.
For your case, I'd recommend going with Party to clear distinguish that it is a B2B process.
Rgds
Eng Swee

Identifying idoc in SAP system using message id in XI system

Hello Experts,
I have executed a couple of XML's that wil be read by XI and passed into my crm system. In XI using the transaction SXMB_MONI i am able to see the executed XML files . Is there any way i can track the exact idoc no for a particular XML that was processed?
Regards,
Vignesh

Hi,
In the Processed XML message double click on the IDoc(under Technical outbound channel column) near the status u will find the IDoc number that are created for that xml message..
Regards
San
Remember to set the thread to solved when you have received a solution there is a Way.

Send / Receive Idoc(XML) in SAP ECC 5.0

Hi Experts,
We are using SAP standard idocs to exchanges master data and Sales data between SAP and non SAP system. currently all the idocs are generated and posted as flat file structure.
There is possiblity to use idoc(XML) and HTTP service instead of standard process without XI?
All info related with this is welcome. is it possible? how?
all suggestion n helpful ans will be rewards with points.
regards: gaurave.

Hi Gaurave,
I have comae accross this type of issue once and hope the below link will give you an idea.
http://msdn2.microsoft.com/en-us/library/cc185479.aspx
thanks,
KIRAN

Send ACC_GL_POSTING01 idocs to another system?

Hi all,
i need to send G/L account postings transaction F-02 from one R/3 ro another as soon as the documents is posted or manually distribute through a program.
suppose a FI document is posted in source R/3 in company code '180' and Business Area '7000' then the same document needs to be posted in target R/3 in company code '1870'.
can ACC_GL_POSTING01 iDOC type be used for this?
so what ALE settings needs to be maintained and how to use customer exits at target end to calculate new company code based on source company coade and business area.
valuable inputs needed.
thanks,
Subba

Hi subba Krishna,
Can u please tell me how did u slove this issue. I am also facing the same kind of problem.
Ur help in regard to this is highly appreciated.
Thanks and Regards,
Prasanna.R

What is best way to connect a non-sap sys sending xml idocs to SAP system

Hi Can some one please guide as to what will be the best approach in connecting a NON SAP system to a SAP system.
The non sap system should not be connected to access real time data,it does not support RFC,it can send data in IDOC xml format and i think in teaxt files also.Also I dont think there is any EDI subsystem in place.
There has to be a periodic upload of material data from SAP /stock status/
then there will be incoming data into SAP for sales order/purchase order etc
What would be the best way to connect the two systems,IDOCs with partial EDI looks the best way ,but I am confused as to how will the XML IDOC be converted to normal IDOC and viceversa,how to handle the event triggering mechanism.
If someone has experience in such a scenario ,please help.
There is a option to update the database of the application through SQL also...

Hi,
Check this link.
Web Services from Function Module
it might help u.
Thanks.

During SAP outages,XI unable to send the IDoc to SAP System.

Hi
We have an interface in XI which posts IDoc to SAP .
In the inbound side XI polls the database and executes a query.
But during SAP outages ( Planned/unplanned) though XI executes SQL and process the messages successfully the message fails in the outbound side as SAP is not available.( Column 'c' will be marked with red flag)
Is there any way we can queue up the messages till SAP is available and post the IDocs.
Presently we have to either resend the message from the source system or using
Run time workbench and payload post the IDoc manually.
I guess there could be some settings in the J2EE stack if done can help with.
My environment is XI 3.0 SP14.
Please suggest a feasible solutions.
Thanks in advance,
KP

Hi,
if the quality of service is EO then your idoc is stuck in sm58 and you can force the idoc to be delivered once SAP will come back available.
You can schedule the report RSARFCEX that does exactly this task.
Normally this job is scheduled to run every 5 minutes.
This should solve your problem.
Btw, I suggest you to additionally have a look at this blog <a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically">XI : How to Re-Process failed XI Messages Automatically</a>.
Best Regards,
Sergio

Sender receiving endless mail delivery system notifications

For the past 25 hours (or so) a friend has been receiving REPEATED messages from Mail Delivery System saying:
"This is an automatically generated Delivery Status Notification. Delivery to the following recipeints is still under way after 25.6 hour(s.): [email protected] Will keep trying and contact you if the message can't be delivered permanently."
How can I/she stop these? She eventually resent the message and all is well, but that original notification regarding the original message is still out there and driving her crazy. DOZENS of these things are being sent by Mail.

How can I/she stop these?
You can't. Eventually they'll time out and stop. Meanwhile you can create a Mail rule to delete the notices automatically.

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

Send IDoc from External System to SAP system

Hi Folks,
I have a requirement to send IDocs from an external system to the SAp system. Basically the external system is a subsystem which is able to send & receive idocs. The external system is currently able to send idocs to SAP system through the ALE layer but now we have to replace it by PI. Now the external system has to send teh IDocs to the SAP ECC system through the SAP PI 7.0.
Kindly let me knowq how I can achieve it.
Regards,
Santosh

Hi Satish,
You can achieve this requirement
1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel to send IDoc.
or
2)Use proxy program ,implement the same ALE logic in PI.
or
3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
Regards,
raj

Send/receive IDOCs to SOLMAN system using AS2 protocol!

Similar Messages

Maybe you are looking for