Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Consuming Cloud Web Services (SFDC) from ABAP

Former Member

‎2010 Apr 19 5:36 PM

0 Likes
589

We are implementing a project where we integrate with SalesForce.Com (SFDC).

We received the Salesforce.com Enterprise WSDL API and created an ABAP proxy based on it.

http://www.salesforce.com/us/developer/docs/api/index.htm

However we have 2 issues with the WSDL:

1) The WSDL uses Complex Types with Extensions. Apparently SAP doesn't support this. We think we can get around this by manually updating the WSDL to only use the types that we are currently interested in.

2) The process to use one of the methods in the service (query, etc.) you first have to log into SFDC using the logon service. This returns a session ID and a session URL. Both of these fields need to be used on subsequent method calls from the API. Passing the session ID in the header is not an issue, however, the URL on subsequent calls needs to be dynamically changed based on the logon result. I am not aware of a way to dynamically change the end point that is configured in LPCONFIG or SOAMANAGER at runtime.

Does anyone know how to work around these issues?

If SAP doesn't currently support this, as cloud computing becomes more prevalent SAP is going to have to support both of these options in the future.

Thanks,

Jeff

We are implementing a project where we integrate with SalesForce.Com (SFDC).

We received the Salesforce.com Enterprise WSDL API and created an ABAP proxy based on it.

http://www.salesforce.com/us/developer/docs/api/index.htm

However we have 2 issues with the WSDL:

1) The WSDL uses Complex Types with Extensions. Apparently SAP doesn't support this. We think we can get around this by manually updating the WSDL to only use the types that we are currently interested in.

2) The process to use one of the methods in the service (query, etc.) you first have to log into SFDC using the logon service. This returns a session ID and a session URL. Both of these fields need to be used on subsequent method calls from the API. Passing the session ID in the header is not an issue, however, the URL on subsequent calls needs to be dynamically changed based on the logon result. I am not aware of a way to dynamically change the end point that is configured in LPCONFIG or SOAMANAGER at runtime.

Does anyone know how to work around these issues?

If SAP doesn't currently support this, as cloud computing becomes more prevalent SAP is going to have to support both of these options in the future.

Thanks,

Jeff

Reply
1 REPLY 1
Read only

amiya_shrivastava3
Explorer

‎2013 May 08 5:31 AM

0 Likes
406
  1. For the first issue, we've chosen to use the "partner wsdl" and not "enterprise wsdl".
  2. The second part of the second issue seems to be not possible so far. We are researching on it.

An update on the second bullet. We talked to SAP in this regards and they responded back that it's not possible using SAP Webservice framework.

I guess either we should use PI or we should build a custom program to create http message from scratch.