Http communication with non-sap system

Hi ,
We have a requirement to send OM related data to a non-sap system using HTTP post in XML format and receive the response from that external system. We are on ECC 6.0 and we cannot use XI at this time.
What would be the correct approach to do this? I read that we could use ICM for HTTP communication am I on the right track?
Thanks

Hi ,
We have similar type of requirement, if you have the solution then let me know .
Thanks in adv
Vishnu

Similar Messages

Non-XI HTTP Communication with non-sap system

Hi ,
We have a requirement to send OM related data to a non-sap system using HTTP post in XML format and receive the response from that external system. We are on ECC 6.0 and we cannot use XI at this time.
What would be the correct approach to do this? I read that we could use ICM for HTTP communication am I on the right track?
Thanks

What setup do we need for this ?
We are on ECC 6.0. I am trying to run the program, I am getting http_communication_failure = 1 in the receive function.
I am not sure if I am missing any authorizations/setup.
Thanks for your help.
VV

How to integrate the portal system with non-sap system

Hi Gurus,
How to integrate Portal system with non-SAP system?
I know few ways .......Using Usermapping UIDPW method.
Using Appintegrator .....and using Business repository objects in JCA?
Is there anyother way to integrate if so please give me the names and steps for integrating it?
Thanks in Advance,
Dharani

Hi Dharani,
You can get information from the following links:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/d08b00d73001b4e10000000a11466f/frameset.htm
https://www.sdn.sap.com/irj/sdn/thread?threadID=744043
SAP CONNECTORS:- Basically Connectors are like middlewares , that we use to connect to the backend system including Non SAP systems also. Will try to explain it to u with some examples of SAP Connectors:-
a) SAP Business Connectors:-
A middleware application based on the B2B integration server from webMethods.
The SAP Business Connector enables both bi-directional synchronous communication and asynchronous communication between SAP applications and SAP and non-SAP applications.
The SAP Business Connector makes all SAP functions that are available via BAPIs or IDocs accessible to business partners over the Internet as an XML-based service.
The SAP Business Connector uses the Internet as a communication platform and XML or HTML as the data format. It integrates non-SAP products by using an open, non-proprietary technology.
b) SAP Java Connector:-
SAP Java Connector (SAP JCo) is a middleware component that enables the development of SAP-compatible components and applications in Java. SAP JCo supports communication with the SAP Server in both directions: inbound calls (Java calls ABAP) and outbound calls (ABAP calls Java).
SAP JCo can be implemented with Desktop applications and with Web server applications.
SAP JCo is used as an integrated component in the following applications:
1) SAP Business Connector, for communication with external Java applications
2) SAP Web Application Server, for connecting the integrated J2EE server with the ABAP environment.
SAP JCo can also be implemented as a standalone component, for example to establish communication with the SAP system for individual online (web) applications.
To Know more go through,
SAP Java Connectors
II) ALE Concept:-
ALE is not restricted to communication between SAP systems, it can also be used for connecting SAP Systems to non-SAP systems.
By using IDocs as universal information containers, ALE can reduce the number of different application interfaces to one single interface that can either send IDocs from an SAP system or receive IDocs in an SAP system.
SAP certified Translator Programs can convert IDoc structures into customer-defined structures.
Alternatively, the RFC interface for sending and receiving IDocs can be used in non-SAP systems.
In both cases you need the RFC Library of the RFC Software Development Kit (RFC-SDK).
This link gives a great insight into landscape for Connectivity to Non-SAP systems:-
SAP to Non-SAP systems
III) Communication Between SAP Systems and External (Non-SAP) Systems using RFC:-
When you use RFC for communication with an external (non-SAP) system, you can also implement the SAP Java Connector or the SAP .Net Connector for the conversion of data. However, there are no specific security requirements for these components, since they only perform internal system conversion functions.
The additional security recommendations for communication with external systems in this section make particular reference to cases where an external system is used as a server (SAP calls the external system). If you use an external system as a client (the external system calls SAP), the appropriate SAP-specific security mechanisms are implemented on the SAP side.
This link explains in detail all the security considerations you need to take for connecting to an External Non SAP system like, User administration, Network Security etc.
Communication Between SAP Systems and External (Non-SAP) Systems using RFC
Hope this helps,
Regards,
Rudradev Devulapalli
Reward the points if helpful

IDoc adapter with Non SAP systems

SAP XI 3.0 help says:
You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures
What does this mean?
-Naveen.

Hi Naveen,
Let me give a use-case in one of our projects ....we have 2 middlewares in our landscape...webmethods and XI...and in one particular instance there was a need to send an FI IDoc from webmethods to XI and forward it to R/3....
In this case, the webmethods was treated like any other sap system for receiving IDoc into XI(with settings in IDX1)...
Hope this might clarify a little bit...
Thanks,
Renjith

SAP 4.7 Interface through RFC with non-sap system

We have SAP 4.7 instance and no XI and currently we are looking at following solutions using SAP connector, need following infrormation:
1. Which standard connector can be used ?
2. How Master Data to be replicated from SAP system to non-sap system( Outbound) ?
3. How Transactional data from non-sap sytem to SAP system ( Inbound)?
We need the above input considering that we don't have XI
regards

hi ,
Can you tell me which other non-sap system you are using
either it is dot net or some other
Regards
Deepak .

Can PMI be used with non-SAP systems?

For example we have an interface that travels through several systems and servers before being fed into XI (and back).
So far as I know PMI only starts when XI picks up the message. Are there any agents, API's or any method to PMI enable other applications to send data to the central PMI collector system so we can see a complete view of the process? Or is that just wishful thinking? Thanks folks,
David

Hi David,
The solution seems to be difficult as per below link.
Please let me know if you find any solution.
http://help.sap.com/saphelp_nw04/Helpdata/EN/a8/a81b0b6473cb49bc34effad6eab13b/frameset.htm

Using ale u can send from sap to sap and sap to non sap systems

hi,
using ale u can send from sap to sap and sap to non sap systems,
then what is diff b/w ALE and EDI

Hello KALYAN KUMAR,
Application Link Enabling (ALE)
1.You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems.
2.ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
3.ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
1.You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor).
2. The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12).
3. This enables communication with non-SAP systems.
By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message
I hope u understands the difference:)

Communication between non SAP and SAP

HI,
do you have some information about communication between non SAP and ERP (WebAs) SAP System ?
I would like to receive an xml file or xml IDoc from a Java Plattform (non SAP) into our SAP ERP System as an own defined IDoc.
remember: we don´t have a converter like XI.
What about using a proxy (do you have some information/blog how to use that) ?
What about using a webservice (do you have some information/blog how to use that) ?
What about storing the xml on the application server (do you have some information/blog how to use that) ?
How to transform xml to IDoc ?
other methods ?
Thanks for your help.
Gordon

Here is a link to connecting MS SQL Server with SAP using Open Hub connection.
http://msdn.microsoft.com/en-us/library/dd299430(SQL.100).aspx
This might give you some insight into connecting with Non SAP Systems.
I have used the information from this link to export data from SAP to MS SQL Server.
Good Luck.
MP.

NON-SAP Systems in IBASE

Hello,
i have maintained ibase entries for non-sap systems as discussed in an other thread, the entry looks like this:
NSI 000000000 001
and then i put the same entry in the identification tab, but when i go to the work center and try to open a message under this system just after pressing the button to create the notification the following message shows up:
You have not selected a system
I have also maintained SMSY with non-sap system but the problem keeps on taking place.
I really would appreciate some help here, usefull answers will be rewarded.
Many thanks in advance.
Marcos

Check this
http://help.sap.com/saphelp_sm40/helpdata/en/45/37bd3d4beb6d7be10000000a114a6b/content.htm
and morever for steps with screenshot
check
http://www.sappro.com/downloads/NonSAPsystems.pdf
hope all the doubts for creating the same are solved
Regards
Prakhar
Edited by: Prakhar Saxena on Jun 30, 2010 7:27 PM

Interface module in GTS from Non-SAP system

Hi, GTS experts,
Can you give me some hint please.
Now I'm plannning to connect Non-SAP system to GTS.
Are there any interface modules or something in GTS?
At least, following objects & actions are to be transferred and maintenanced.
- business partner (customer or vendor in ERP)
- customs product (product in ERP)
- customs document & customs declaration document (document in ERP)
- release of blocked customs document
regarads,
Katsumi

Hello Katsumi,
Some further info to what has been provided above, here is how the following function groups align with data from the ECC system:
/SAPSLL/API_1006 -> Business partners
/SAPSLL/API_6800 -> Customs documents
/SAPSLL/API_6850 -> Products
For each group there usually is a function module for individual or mass update, e.g.
/SAPSLL/API_6850_SYNCH
/SAPSLL/API_6850_SYNCH_MASS
The function modules in these function groups are remotely-enabled (i.e., they are BAPIs).
It is, thus, true to say that GTS can interface with non-SAP systems. Some GTS users have done this. But you have to use some sort of connector technology to build up the proxy and call the function modules (e.g. JCo) from your non-SAP system directly.
Regards,
Randy
Edited by: Randy Strader on Dec 5, 2008 11:03 PM

HOW TO SEND THE REPORTS AND THROUGH XI TO NON -SAP SYSTEM

Hi Experts,
I want to know how to send the reports and smartform through xi to another system. All the post blogs are just explaning only about the FILE-TO-FILE, FILE-TO-IDOCS scenarios only.

Hi,
XI is the middleware that to be used to transfer the data between various systems and even you could design the Business Processes with it.
In R/3 the smartforms, are generally converted to PDF and then have to send it across to Non SAP systems. Similarly you can convert the smartforms to pdf format and keep it on application server. XI will pick up that pdf and will send it to Non SAP system either as mail or as an attachments.
ABAP reports are normally used to re-present the data. If you need to transfer this data across the Non SAP systems then you have the IDOCs to be generated, RFC or ABAP Proxy to integrate this data with Non SAP system.
XI is not restricted only upto file to file or file to IDOC scenarios. It have enormous capabilities to involve various Business Processes as well integrate various SAP or Non SAP systems.
If need anymore specific details, please let us know.
Thanks
Swarup

RFC Adapter to connect to Non SAP System

Hi,
I have a scenario to connect to a non SAP system using RFC adapter. I am not used to the same. I need to know whether this is possible and what are the steps to be done.
Thanks and regards
Siji

Hi,
These links should help.
Non-SAP application connecting to PI via Sender RFC Adapter
Error by setup RFC Interface with non SAP system
SAP PI to Third Party system through RFC Connectivity ??
Regards,
Jannus Botha

Ale master data scenario integration with non sap syetem i.e seebeyound

hi
we have a business process scenario integrating with non sap system (i.e seebeyound)
action code      itemnumber    plant code
a(add)          material1     plant 2
d(delete)       material 3    plant 6
etc
we have upto one million materials assigned to 300 plants
we have to send all the above data to non-sap system (see beyound)
should we go for a custom idoc and setup the rfc configuration for the two sytems.
or can you please help how to go for this scaneriao

this is not one time.it is on daily basis.
please look at this scenario.what i need is how should i go for ale/idoc scenario for this one
Business case for Heiler Part/Plant Interface:
A key function of the Heiler PBC tool is to provide users a choice
between a "Global Catalog View" (e.g. all parts in the catalog) or a
"Local Catalog View" (e.g. the subset of parts in the catalog that have
a Material Master established for the user's plant in SAP). The "Local
Catalog View" is the default condition and encourages users to procure
parts that are on contract for their plant and potentially already
stocked as an inventory item at their plant. Parts that are not in a
user's "Local Catalog View" can only be procured as a spot buy purchase
order, requiring processing by a buyer.
The new Part/Plant interface is required in order for the Heiler PBC
tool to provide this "Local Catalog View" function. The Heiler
Part/Plant table will document what plants in SAP have a Material Master
record established for each part. SAP will maintain the Heiler
Part/Plant table using this interface. When a user performs a part
search in the Heiler PBC tool, the Part/Plant table determines if a part
is included in the user's "Local Catalog View".

HTTP Receiver Adapter - Post HTTPS to non-sap system

I plan on doing an https post to a non-sap system using the http rec adapter. Will I need to make some config changes to enable ssl communication on the XI system? Will I need the certificate of the target system?
Thanks,
Mark

Hi Mark,
You will need Certificate to enable SSL communication.
And once you install your certifictaes on the systems according to the above blog then there are few changes which needs to done on XI side.
On XI Server - Go to SM59 and Create HTTP destination to the system with SSL enabled in that destination.Select active option for SSL.
In confguration - Go to HTTP rec channel and select HTTP destination and here give the one which u have created in last step.

External requirement from non SAP system created in SRM 7.0 Extended Classi

Hello SRM Gurus:
Has anyone created an external requirement using XI ExternalRequirement_Create_In (http://sap.com/xi/EBP). We are getting a E001 "No company code could be determined for backend for product##". I traced the error to FM 'BAPI_SCEC_CREATE' in class "CL_BBPX_EXTERNAL_REQUIREMENT". What I found is that it check the attributes for BUK and updates a table with the backend EEC system. Then it checks if any of the entries match our external non SAP system in our external requirement and since it is a non SAP system none do. Then it sets a return error code.
I configured our non SAP system in the SLD and in SPRO under "Define System Landscape" as a non SAP system.
We are running external classic scenario. We just want to created a shopping cart from an external non SAP system. Source the shopping cart in SRM and create the PO in SRM/ECC. We are not using a product master but creating "describe requirement" in our external system. Our product categories are replicated from ECC and the same codes used in our external non SAP planning system.
If I change the external planning system to the ECC backend system, the external requirement is created in SRM but when I source it and convert it to a PO, it returns a backend error that the external requirement number does not exist in ECC. Therefore it appears all of our data from our external system is correct with the exception of how to deternine the backend company code
According to SAP this should be possible using XI.
Has anyone been successful doing this or can you please advise any OSS notes or documentation explaining how to do this. Please advise if you need additikonal info.
Thanks in advance.
Bert

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

Http communication with non-sap system

Similar Messages

Maybe you are looking for