Supported OData Version in SAP Gateway

Hello Experts!
I need to figure out about the supported OData Versions for SAP Gateway? I couldn't find anything at SAP Help or SCN. Is there a chance to get the supported version at our current system installation (any transaction or customizing step??)
Thanks in advance!

Rupp,
As I see, Gateway is supposed to comply with OData V2 and they are gradually adding V3 features.
There is a reference here in first few lines of Andre's blog. How to consume an OData service using OData Services Consumption and Integration (OSCI).
If you are concerned about features supported, your best bet would be note 1574568.

Similar Messages

What is the latest prod. supported MaxDB Version w. SAP Content Server 6.40

What is the most actual supportet MaxDB Version when using with SAP Contentserver 6.40?
In PAM Page 5 (of the Powerpoint) the official Version should be 7.5.
In "install and Upgrade" NW 7.0 there is the "NW 7.0 Presentation - MaxDB Release 7.6.03" available for Download and the "MaxDB RDBMS 7.7.06 Build 10 - Windows Server on x64 64bit "
Does that mean, that the 7.7 Version is official supported for Production?
Searched the Notest but found no answer for that.
Ulrich
... half an hour later ...
just found MAXDB 7.7 Installation which suggest the 7.7 is the latest official supported.
could that be the answer?
Ulrich
Edited by: Ulrich Neumann on Feb 2, 2010 12:39 PM

Hello Ulrich,
Please refer at SAP link http://service.sap.com/pam for full platform availability information of the new version. SAP Content Server is shipped with NetWeaver 2004s SR1.
< service.sap.com/pam -> SAP NetWeaver 04 -> Database Platforms -> Content Server
   Select in MAXDB section u201CWINDOWS SERVER...   u201C >
< according PAM :
MAXDB 7.6 64-BIT is released on WINDOWS SERVER 2003/X64 64BIT for
SAP CONTENT SERVER 6.40 >
As you know the SAP installation guide for Content server is available at::
service.sap.com/installations -> SAP Components
->SAP Content Server -> Release 6.40 and higher
< Installation - Standalone Engines >
For additional information and documentation please go at SAP link:
http://service.sap.com/ContentServer
-> FAQs SAP Content Server
Thank you and best regards, Natalia Khlopina

Until when give SAP support for version 7.30?

Hello,
Until when give SAP support for version 7.30?
How is the update from SAP GUI 7.30 to 7.40 handle?

Hello Herr Jürs,
As per the attached note http://service.sap.com/sap/support/notes/147519
support ends in July
SAP GUI for Windows Support Deadlines
7.30: Full support up to July 15th, 2015. On July 15th, 2015 the used development environment Microsoft Visual Studio 2010 will transit to Microsoft's "Extended Maintenance" mode. This means that Microsoft will not create any corrections for components which belong to this development environment anymore (unless the issue is security relevant). Therefore no extension of full support for SAP GUI for Windows 7.30 beyond this date is possible.
Regards,
Jude

What versions of Call Manager support the new VG3XX Voice Gateways?

What versions of Call Manager support the new VG3XX Voice Gateways?

http://www.cisco.com/c/en/us/td/docs/routers/access/vg350/software/configuration/guide/vg350_scg/scgapp_platforms_ORIG.html#64565

PEXR2002 supported from which version of SAP

Hi,
Please let me know that Idoc PEXR2002 is supported from which version of SAP. Is it supported by 4.7. If not than what is a corresponding Idoc in 4.7.
Regards,
Milan Thaker

Hi,
I am not sure of actual version, but referring to help in SAP we can conclude the it existed as of Release 4.0b, of course with not the full functionality as of today.
Please refer to link below:-
http://help.sap.com/saphelp_40b/helpdata/en/72/c199d3546a11d182cc0000e829fbfe/frameset.htm
The last sentence of the help can lead to more information...
The R/3 Consolidation system EC-CS is available as of Release 3.0 on a project basis only. A standard delivery of the application will be possible with a later release.
Rgds.

Connection to SAP gateway failed

I got the following error when i am connecting to BEX( through rrmx & direct from Business explorer) from offshore. onsite people are able to connect BEX.
as we do not have basis consultant we only need to resolve it.
please let me know what all the process I have to do. is there anything i need to contact network perople at client place. is there any settingss i need to do at sm59 tcode.
<b>please find following error message</b>
Error Group
RFC_ERROR_COMMUNICATION
Message
Connect to SAP gateway failed
Connect_PM GWHOST=10.235.245.95, GWSERV=sapgw05, ASHOST=10.235.245.95, SYSNR=05
LOCATION    CPIC (TCP/IP) on local host
ERROR       partner not reached (host 10.120.130.85, service 3305)
TIME        Mon Nov 06 21:53:32 2006
RELEASE     640
COMPONENT   NI (network interface)
VERSION     37
RC          -10
MODULE      nixxi_r.cpp
LINE        8602
DETAIL      NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     2
Thanks
Lakshmi

Hi Lakshmi ,
As rightly mentioned by Ganesh, this is supposed to be handlled by Basis+hardware support team.
What you can do as temporary solution, use RSRT for Query Monitor.
And use query display as BEx/HTML, this way you can atleast see the result of query.
Hope it helps.

Connect from SAP gateway to RFC server failed - Java StandAlone app X SAP RAC System

Dears,
I'm developing a Java application (RFC SERVER) with JCo3 and I need to connect to SAP RAC system.
I have configured the TCP/IP connection via transaction SM59, but when I try to start my server I face the error below (dev_jco_rfc.trc):
==========================================================================================
**** Error file opened at 20140714 112024 Brasilia Time Rel 3.0.10 (2013-08-08) [720.440]
Error: >Mon Jul 14 11:20:24,636<    RfcException: [null]
    message: Connect from SAP gateway to RFC server failed
Connection parameters: TYPE=A DEST=VSPAGUE ASHOST=cpe1601 SYSNR=01 SAPROUTER=/H/155.56.49.28 PCS=1
LOCATION    SAP-Gateway on host ld7624.dmzwdf.sap.corp / sapgw01
ERROR       hostname 'cpe1601' unknown
TIME        Mon Jul 14 16:20:25 2014
RELEASE     740
COMPONENT   NI (network interface)
VERSION     40
RC          -2
MODULE      /bas/740_REL/src/base/ni/nixxhl.cpp
LINE        193
DETAIL      NiHLGetNodeAddr: hostname cached as unknown
COUNTER     3
    Return code: RFC_FAILURE(1)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
==========================================================================================
This problem happens when my app executes the line:
JCoServer myServer = JCoServerFactory.getServer(myServerName);
My system properties:
jco.client.lang=EN
jco.destination.peak_limit=10
jco.client.client=800
jco.client.passwd=********
jco.client.user=********
jco.client.sysnr=01
jco.destination.pool_capacity=3
jco.client.ashost=/H/155.56.49.28/H/cpe1601
jco.server.connection_count=3
jco.server.gwhost=/H/155.56.49.28/H/cpe1601
jco.server.progid=VSPAGUE
jco.server.gwserv=sapgw01
jco.server.repository_destination=VSPAGUE
Using SAP Logon i can connect to server cpe1601 system E16 without problems.
Please, I really need some help, because my knowledge on SAP platform is minimum.

Hi Markus,
Changing ASHOST=ld7624.dmzwdf.sap.corp as you have suggested, I got the error message: Connect to SAP gateway failed ...
As you could see, the host I'm connecting is from SAP RAC Service.
Here in our company we have only SAP Logon and my RFC Application, and I can connect to SAP remote system via SAP Logon with this settings:
System Connection Parameters
Description: SAP ECC 6.0
Application Server: cpe1601
Instance Number: 01
System ID: E16
SAProuter String: /H/155.56.49.28/H/
Below the connection information I received from SAP RAC SUPPORT for testing purposes:
    E16 System:
    SID: E16
    Client: 800
    System Number: 01
    Server: cpe1601
    Component Version: SAP ERP Central Component 6.0 Enhancement Pack 6 Suite on HANA
    User: ********
   Password: ********
   SAProuter String:
   If you don't plan to use SAPRouter at your end,
   /H/155.56.49.28/H/

Pessimistic Locking mechanism in SAP Gateway.

Hi All,
           I am new to SAP Gateway. I know there are two types of locking mechanism ( optimistic and pessimistic) . Optimistic we do by etag and if-match.
Is there any idea of how to do by pessimistic approach.
For example we are reading a contract and then updating it. So, in get_entity we have to put the lock while reading and we have to unlock while updating. But how does it works. Whether the lock automatically get released after the get_entity method.
Kindly guide me in proceeding further.

Hi Sundar,
Here is my opinion :
          Gateway is Completely Stateless till the current version which is SP8. So Pessimistic Locking would not be available out of the box by Gateway. You need to implement your custom logic to achieve this behaviour. However simulating a Pessimistic Lock in a complete stateless architecture will lead to many complexities which often might lead to inconsistency in the Application. As mentioned by Krishna, you can store lock information in some table in backend , but it might get messy very easily. I would not recommend to do so. However if you are really keen to do Pessimistic Locking kind of mechanism, what about the following approach -----
1. In the OData service, let us have an extra Entity called LOCK which has properties such as USER, RESOURCE_ID(such as contract ID),DATE,TIME. USER and RESOURCE_ID is the key in this entity. This data is stored in a table in database.
2. When a particular USER opens the CONTRACT screen in EDIT mode, the UI fires a POST(Create) call for Entity LOCK with the USER and RESOURCE_ID(contract ID in this case). In the backend database table if no entry exists with that USER ID and RESOURCE_ID, then a new entry is created and the USER is allowed to EDIT the contract. If an entry already exist in table then it means some other user is already in Edit mode , and the current user is refused to access the resource in edit mode.
3. When the USER saves the CONTRACT you need to fire a DELETE request for that Particular LOCK entity. Thus is resource is dequeued.
However this is like a vanilla flow. Handling can be complicated if user closes the browser, disconnects the network connection, opens parallel session etc etc.
          Rather a clean approach would be an Optimistic lock. Fiori Applications are using this mechanism to handle concurrency control. You may refer to my reply on Locking mechanism in SAP Gateway. for a little more information on Optimistic Locking.
I agree that even though Optimistic locking works pretty well in REST based applications as it allows operations to be free from overhead of long transaction , there can be situations as mentioned below, where an Optimistic lock might not be preferred -
1. Where the chances of concurrency collision is very high (Example: Online Reservation of Tickets)
2. If modifying the resource by the user requires a lot of typing (However JS libraries such as Garlic.js, sisyphus.js or HTML5 Local storage can help us here )
Now it is upto you to decide upon the approach ..

Versioning on SAP PI

Hello PI gurus
I have been asked to look at versioning on PI. Specifically how we maintain multiple versions of an interface for our various Landscape rollouts and ensure that both versions can be used. I have researched the options, run a few tests and my conclusions are below but I am looking for a second opinion and would appreciate your feedback
Options
1) Create a new SWCV.
According to SAPs documentation a software component version is a shipment unit for design objects in the ES Repository. You use a SWCV to group together objects that are shipped or installed together.SAP uses this approach for the majority of their standard content. You cannot copy objects between different releases of a SWCV. You have to use the Transfer Design Objects Function (ESR Menu under tools). It is a neat tool that will transfer objects only if the source objects are more recent or the target objects do not exist. You can preview the changes and it will tell you what will be updated (source version is more recent), what cannot be transferred (the target version is more recent) or what does not need to be transferred (the versions are the same).
This is appropriate for deploying different versions of a particular software package but does not allow us to actually use both versions. The majority of the ID objects refer to the interface/namespace and not the SWCV. If you try and add two identical interfaces from separate SWCV to the same Communications Component you get an error.
2) Create a new namespace with a version number
SAP has used this approach for the NFE updates and it works.
3) Ensure that the interface is backwards compatible.
Backwards compatibility is not always easy to achieve. The functional requirements we are given evolve over time and it may be the case that what seems to be a simple change that may not have any impact may will change significantly.
4) Add a version number to the object names
Not the most elegant approach but it would work.
5) Stand up a separate PI landscape.
Not my preferred approach as it introduces additional costs, maintenance, monitoring and development. It seems to overkill.
Summary
Using different SWCV allows new releases to be created and deployed but you can only have a single release active at any moment in time. Using Namespaces allows multiple releases to be deployed. If you look at the SWCV for NFE, SAP SLL-NFE you can see they have taken this approach. I have hecked the SAP support sites and cannot find anything on versioning.
My preferred option is number 2. Using a different namespace works but will require the calling system to update their configuration to support this.

Dimitri,
My other concern is that there is no relationship between the versions. For example assume we have version 1 and 2 of an interface and both need to be in production for several weeks. Then, for example, the end users identify a bug that can be found in both versions. We then have to apply that fix to both versions independently. What that means is while we have both versions available we would then have dual maintenance.
I've look at versioning with SWCV and SAP have a great tool for copying code between the releases. However, from what I can see you can only configure one version in place at any one time.
Is this really the only solution.
Regards
Rob

Earliest version of SAP R/3 compatible with XI

Hi,
Can anyone tell me where I can find out the earliest version of R/3 that is compatible with XI ?
I am trying to connect an R/3 3.1i system and facing a lot of issues.
Kind regards
Colin.

Hi Colin,
Are you using idoc or RFC adapter for integration ?
Check this..
"The IDoc adapter enables you to process IDocs (Intermediate Documents) using the Integration Engine. IDocs from SAP systems Release 3.1x or higher are supported."
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm
Also check this thread..
Re: Support of RFC and IDOC adapters
Regards
Anand

SAP_CMINIT3 : rc=20 Connect to SAP gateway failed when connecting SAP CR

Dear SAP Gurus,
I have the follwowing issue when I try to access SAP Crystal Reports 2011 on my desktop.
I can access the SAP ERP 6.0 back-end system without problem, but when I try to connect to SAP Crystal Reports, as soon as I enter my login details, I get the following error message:
Logon Failed.
Details: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM GWHOST=192.12.353.12, GWSERV=sapgw00, SYSNR=00
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 192.12.353.12:3300' not reached
TIME Thu Oct 27 12:02:17 201
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2823
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 3
I can login to SAP Crystal Reports using other desktops, but cannot access using my own. This is the same for other people, they also cannot access using my desktop.
Thanks in advance, Marc

HI Mark,
Are you and Ramish working together?
See this post for your answer: Connection keeps failing
Don

SharePoint 2013 and SAP connectivity / SAP Gateway for Microsoft and Duet Enterprise 2.0

Hello,
we are investigating the connection possibilities of SharePoint 2013 with SAP.
The basic scenario in our cases involves the transfer of documents and/or metadata from SharePoint to SAP possibly through a Workflow in SharePoint.
From my research the most promising official (no 3d-party) interfaces that can be used are the Duet Enterprise 2.0 and the SAP Gateway for Microsoft.
From my understanding both interfaces allow only the consumption of Data from SAP to SharePoint and not vice versa. Moreover the interoperability of documents seems not be supported. Are CRUD operations from a SharePoint native lists to SAP supported?
Can someone please clarify this topics?
I have found lots of documentation concerning the interfaces but not a clear answer to this questions.
Many thanks in advance!
Ioannis

Hi Ioannis,
It seems that there is no built in method to get data from SharePoint list in SAP.
As a workaround, we can export SharePoint list to excel and then use that spread sheet as a source data in SAP.
http://scn.sap.com/thread/3467263
http://scn.sap.com/thread/3472110
As this issue is regarding to SAP, I recommend you to ask the question in the SAP:
http://scn.sap.com/welcome.
More experts will assist you, then you will get more information relation to SAP.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Sol Man 4.0 Installation Error ECJS-30196 Connect to SAP gateway failed

Hi Experts
I am trying to install Solution Manager 4.0.
While installing SolMan, everything goes fine, until step # 31 create java users (creating SAP Jsf user), then it runs into below error messages.
CJS-30196 Connect to SAP gateway failedConnect_PM TYPE=A ASHOST=solman SYSNR=23 GWHOST=solman GWSERV=sapgw23 PCS=1LOCATION    CPIC (TCP/IP) on local host with UnicodeERROR       partner 'solman:sapgw23' not reachedTIME        Mon Aug 13 17:44:59 2007RELEASE     700COMPONENT   NI (network interface)VERSION     38RC          -10MODULE      nixxi.cppLINE        2770DETAIL      NiPConnect2SYSTEM CALL connectERRNO       10061ERRNO TEXT WSAECONNREFUSED: Connection refusedCOUNTER     1
FCO-00011 The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with status ERROR .
CJS-30196 Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=solman SYSNR=23 GWHOST=solman GWSERV=sapgw23 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       timeout occured
TIME        Mon Aug 13 17:17:35 2007
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -5
MODULE      gwxx.c
LINE        480
DETAIL      timeout 60000 msecs
SYSTEM CALL NiRead
COUNTER     1
Any suggestions/ideas for this error
Regards
Rahul

Hi Experts
I am trying to install Solution Manager 4.0.
While installing SolMan, everything goes fine, until step # 31 create java users (creating SAP Jsf user), then it runs into below error messages.
CJS-30196 Connect to SAP gateway failedConnect_PM TYPE=A ASHOST=solman SYSNR=23 GWHOST=solman GWSERV=sapgw23 PCS=1LOCATION    CPIC (TCP/IP) on local host with UnicodeERROR       partner 'solman:sapgw23' not reachedTIME        Mon Aug 13 17:44:59 2007RELEASE     700COMPONENT   NI (network interface)VERSION     38RC          -10MODULE      nixxi.cppLINE        2770DETAIL      NiPConnect2SYSTEM CALL connectERRNO       10061ERRNO TEXT WSAECONNREFUSED: Connection refusedCOUNTER     1
FCO-00011 The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with status ERROR .
CJS-30196 Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=solman SYSNR=23 GWHOST=solman GWSERV=sapgw23 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       timeout occured
TIME        Mon Aug 13 17:17:35 2007
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -5
MODULE      gwxx.c
LINE        480
DETAIL      timeout 60000 msecs
SYSTEM CALL NiRead
COUNTER     1
Any suggestions/ideas for this error
Regards
Rahul

RFC logon failed with message: Failed: Connect to SAP gateway failed

I installed CI instance fine and i am stopped here with this error at the end of DB instance install. Could someone let me know what could be the reason for this. Is there any fix or workaround to continue the install.
INFO       2006-09-16 01:13:02 [iaxxrfcimp.cpp:398]
          CAbRfcImpl::setRfcConnectParam
RFC parameter ASHOST set to value hostSAP.
INFO       2006-09-16 01:13:02 [iaxxrfcimp.cpp:398]
          CAbRfcImpl::setRfcConnectParam
RFC parameter SYSNR set to value 09.
INFO       2006-09-16 01:13:02 [iaxxrfcimp.cpp:543]
          CAbRfcImpl::checkConnectInfo
RFC connection information checked successfully.
ERROR      2006-09-16 01:13:02 [iaxxrfcimp.cpp:450]
          CAbRfcImpl::openRfcConn
FRF-00007 Unable to open RFC connection.
ERROR      2006-09-16 01:13:02
          CJSlibModule::writeError_impl()
FRF-00063 RFC logon failed with message: Failed: Connect to SAP gateway failed
Connect_PM GWHOST=hostSAP, GWSERV=sapgw09, ASHOST=hostSAP, SYSNR=09
LOCATION    CPIC (TCP/IP) on local host
ERROR       partner not reached (host hostSAP, service 3309)
TIME        Sat Sep 16 01:13:02 2006
RELEASE     640
COMPONENT   NI (network interface)
VERSION     37
RC          -10
MODULE      nixxi_r_mt.cpp
LINE        8528
DETAIL      NiPConnect
SYSTEM CALL connect
ERRNO       146
ERRNO TEXT Connection refused
COUNTER     4
Thanks,
Ram

at the end of the database instance installation SAPInst is doing some RFCs to the CI.
The logfile states that the gateway on host hostSAP with the systemnumber 09 is not reachable.
Please check if you have started the central instance on this machine.
peter

Connect to SAP Gateway failed.

Hello. When I setup the databridge it errors out. When I check for processes, it shows sapmsj2e as being on port 3601 in my services file. But I can't launch a webdyn pro or access my machine with the sap gui. Any ideas?
Heres the log file snipped
352 11/16/04 1:28:12 PM [SAPEngine_Application_Thread[impl:3]_12] INFO com.sap.lcr.webui.DPBridgeServlet: Data Supplier Bridge started.
#351 11/16/04 1:28:09 PM [JCO.ServerThread-97] DEBUG com.sap.lcr.sagent.SAPProxyServer: JCO exception processed.
#350 11/16/04 1:28:09 PM [JCO.ServerThread-97] DEBUG com.sap.lcr.sagent.SAPProxyServer: On server exception: Terminated thread.
#349 11/16/04 1:28:09 PM [JCO.ServerThread-97] DEBUG com.sap.lcr.sagent.SAPProxyServer: JCO Server exception received: Server startup failed at Tue Nov 16 13:28:09 PST 2004.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
Could not start server: Connect to SAP gateway failed
Connect_PM TPNAME=SLD_NUC, GWHOST=orw-gharnish, GWSERV=sapmsJ2E
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR connection to partner broken
TIME Tue Nov 16 13:28:09 2004
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -6
MODULE ninti.c
LINE 784
DETAIL NiPRead (147.34.68.157/sapmsJ2E, hdl 1)
SYSTEM CALL recv
COUNTER 88
Thrown:
com.sap.mw.jco.JCO$Exception: Server startup failed at Tue Nov 16 13:28:09 PST 2004.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
Could not start server: Connect to SAP gateway failed
Connect_PM TPNAME=SLD_NUC, GWHOST=orw-gharnish, GWSERV=sapmsJ2E
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR connection to partner broken
TIME Tue Nov 16 13:28:09 2004
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -6
MODULE ninti.c
LINE 784
DETAIL NiPRead (147.34.68.157/sapmsJ2E, hdl 1)
SYSTEM CALL recv
COUNTER 88

Also. If I check my bridge connections it shows this:
[DOWN] JCO/RFC server threads
Is that related to the other problem?
Thanks, Graeme.

Supported OData Version in SAP Gateway

Similar Messages

Maybe you are looking for