Hello experts.

We moved to Product system and I am trying to configure Fiori MyTimesheet application in it. The problem is that service for this app is missing. According to guides after RFC Connection (which was successful as I can access ERP system through NetWeaver) and System Alias configuration with transaction /IWFND/maint_service I should be able to add SRA001_timesheet_srv service. But it is missing in list of suggested service. Here is image

Also I can't find it in ' transaction SICF-> sap-> opu-> odata-> sap '.

At the same time I successfully added Launchpad, Pagebuileder and Transport services. May be application's service should be added in some other way?

Waiting for your advices.

Best Regards.

P.S. The main issue for me is that previous develop and quality system were configured not by me. I done everything by guide step by step but the result is negative...

Dear all

i have SAP ECC 6

and

i want to install Fiori UX, the prerequisites steps says you must have "SAP Netweaver Gateway 2.0", so can i know if i have it or not?

thanks,

Working on first gateway project and being asked to expand the parent child entities linked with Navigation Property with a single expansion or RFC call requires quite a bit of self learning. However, when explored the internet, I could not find blogs/links which explained in detail how to use Expansion Method of the Gateway to expand both Parent and Child Entity in a single RFC call, rather than making call first to parent entity and then to the child using $EXPAND parameter in the Odata Service Link.

This scenario is more appropriate for Gateway Hub scenario where in GW(GW_CORE, I_BEP and IW_FND) and ECC are separate systems. An RFC call is made from GW to ECC each time data is requested from UI. Therefore, if the user needs to fetch the Parent Child data using $EXPAND, the gateway framework will first call the entity set for the Parent(SOHeaderSet) and then the entity set for Children(SOItemSet). This results in 2 RFC call to fetch the required data.

In this blog, we will learn how we can reduce 2 RFC calls to a single RFC call and expand both the Parent and Child Entities in a single Odata Service Call.

In order to implement this, we will re define 'GET_EXPANDED_ENTITYSET' Method of the Data Provider Class.

In this example, we will use 2 entities Sales Order Header(SOHeader) and Sales Order Item(SOItem). Both are linked to each other with a navigation property SOHeaderToItem.

Redefine GET_EXPANDED_ENTITYSET as explained in the attached snapshot.

The catch here is that, we have to tell the GW framework that we have expanded both the Header and Item entities in a single entity set call and no need to call the child entity set to fetch the the Sales Order Items. We can do this using parameter ET_EXPANDED_TECH_CLAUSES of GET_EXPANDED_ENTITYSET. Append the Navigation Property Name(SOHEADERTOITEM) in this exporting parameter, which will tell the gate way framework that the child entity has already been expanded and there is no need to call the child entity set.

An important point to not here is that the structure of the output entity set should have a field with Name same as Navigation Property Name(SOHEADERTOITEM). This field has to be a Table Type to support Header and Item relationship structure. Check structure below.

When you will call the Odata Service from the Client with $EXPAND, only the Header Entity Set will be called and no call is made to the Item Entity Set.

https://<Host Server:Port>/sap/opu/odata/sap/ZEXPAND_PARENT_CHILD_SRV/SOHeaderSet?$expand=SOHeaderToItem

In normal expansion scenario with $EXPAND, the gateway framework would first call SOHeaderSet and then the corresponding SOItemSet.

Thanks!!!!

Dears,

Try to resolve the issue to connect to the backend GW system, and searched a whole day here in SCN, try all means which suggested, but still could not get it conneted.

Here it's my enviornment:

- Eclipse Luna version with GWPA plug-in installed (actually, I also have Juno version with GWPA, but still failed to connect).

- JDK 1.8.025 together with JAVA_HONE and PATH maintained

- GW system is on NW7.40 SP07 with SAP_GWFND SP08 installed (all NW GW is activated fo sure, and all needed Odata service works perfectly)

Following is the error and my reserch in details:

- Firstly, I try to call the Odata server that I want to use, and it looks good in IE

- Sencondly, open eclipse to set up the proxy with every case that I could image for Bypassing the proxy

- Then goto Odata Development in Preference and try to add a connections there

You see, netowork connection error

Then I simply switch to Service Catalog option which works find in GW client

Error again!

- Searched some hints in SCN, so I make sure that port 55080 is open

See, it's opened.

- Also make sure that the host file is maintained with the system info and restart the system

But no matter what I tried there, just could not get it connected.

And ironically, I got the SAPWebIDE local version installed, and I could get my system connected without any issues.

So, anyone who could help me here? Do do appreciate that!

BTW, here it is the trace log for the issues.

!ENTRY com.sap.gw.oc.eclipse.preferences.ui.validator 4 0 2014-11-12 06:21:34.376

!MESSAGE Network connection error

!STACK 0

com.sap.nw.gateway.odata.client.exceptions.RestClientException

at com.sap.nw.gateway.odata.client.connectivity.impl.RestClientBase.execute(RestClientBase.java:58)

at com.sap.gw.oc.eclipse.preferences.ui.validator.ConfigurationValidator.testConnection(ConfigurationValidator.java:259)

at com.sap.gw.oc.eclipse.preferences.ui.validator.ConfigurationValidator.validateConfiguration(ConfigurationValidator.java:93)

at com.sap.gw.oc.eclipse.preferences.ui.validator.ConfigurationValidator.validateCreatedObject(ConfigurationValidator.java:41)

at com.sap.gw.oc.eclipse.preferences.ui.validator.ConfigurationValidator.validateCreatedObject(ConfigurationValidator.java:1)

at com.sap.gw.oc.eclipse.preferences.ui.AbstractGatewayConfigurationDialog.getDialogStatus(AbstractGatewayConfigurationDialog.java:721)

at com.sap.gw.oc.eclipse.preferences.ui.AbstractGatewayConfigurationDialog$26.run(AbstractGatewayConfigurationDialog.java:752)

at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

Thanks!!!

Hello,

I am following the steps of the SAP NW GTW 2.0 SP06 configuration guide, and am a bit stuck on the section Configuring the Task Gateway Service. In step 3, we are instructed to choose the option Single Service Configuration. However, I don't see this option. I do see option Web Service Configuration and when I choose it, I am able to continue with the rest of the steps of the documentation.

Am I missing an option here or does the documentation just need to be updated where Single Service Configuration should read Web Service Configuration?

Thanks!

Jeffrey

General

1) What is SAP Gateway?

SAP Gateway lets you empower users with secure, personalized solutions that leverage and extend your existing SAP infrastructure, all with security, robustness, agility, and efficiency. SAP Gateway lets you meet the changing needs of your business at the speed of business by enabling People agility, System agility and Process agility.

Getting Started with SAP Gateway

2) What does SAP Gateway deliver?

With SAP Gateway, you can:

• Increase workforce productivity
• Help ensure enterprise readiness
• Reduce IT complexity and total cost of ownership
• Create custom apps quickly and easily
• Consume SAP Data on any Platform, any User Experience

Getting Started with SAP Gateway

3) What is the value customers should expect from SAP Gateway?

SAP Gateway liberates your SAP data to quickly and easily create apps that help your workforce be more productive, your partners are more connected with your business and your business be more connected with your customers.

Getting Started with SAP Gateway

4) What are the technical benefits of using SAP Gateway?

SAP Gateway utilizes your existing SAP infrastructure investment providing different deployment options. It offers strong, built-in security, automated governance, comprehensive monitoring and secured connectivity.

It provides easier, faster data consumption from SAP Business suite, SAP HANA and other SAP business applications on any device, anywhere, at any time.

SAP Gateway provides standard tools for service provisioning which allow generation of services which can be consumed easily on any device and on difference experience. Consumption of service from SAP Gateway need no or minimum SAP experience.

5) What is SAP Gateway roadmap?

The solution is a natural fit for businesses looking to enable or extend efforts in the following areas:

• Provisioning and API management, so developers can simplify consumption of SAP data by easily creating apps that are secure, scalable, and compliant
• An innovative engagement framework for a better user experience with modern UIs, the ability to consume SAP data anywhere, easier access to backend technologies, and enterprise readiness
• Cloud and Big Data opportunities with SAP HANA and easier integration for developers using standards like  ABAP language and ODATA protocol

SAP Gateway lets you fully embrace these with rapid development that focuses on value, simplicity, and a reliance on standards so you can leverage existing skills.

6) How is SAP Gateway placed in SAP portfolio?

SAP Gateway is a set of components which utilizes the existing SAP NetWeaver infrastructure. SAP Gateway can connect to SAP Business Suite, SAP HANA and SAP Business Information Warehouse backend. It is a platform that exposes all the back end data as OData to be consumed by outside world of SAP.

Getting Started with SAP Gateway

7) What is the adoption rate of SAP Gateway?

As of 2013, there are 8000 adoption instances of SAP Gateway.

8) Any there any business use cases?

Yes, American airlines and University of Mississippi are two customer success stories who have greatly benefited from SAP Gateway to improve their processes.

SAP Gateway - YouTube

9) What social medial channels does SAP Gateway offer?

• LinkedIn:https://www.linkedin.com/groups/SAP-Gateway-4554629
• YouTube: SAP Gateway - YouTube
• Facebook: SAP Database &amp;amp; Technology | Facebook

10) Where can I learn more on SAP Gateway?

We have great resources to get you started with SAP Gateway for e.g. SCN, Social media channels, SAP Gateway curriculum.

SAP Gateway - YouTube

SAP Gateway

11) Where can I find training to get started with SAP Gateway?

The following blog guides you through the GW100 course available on SAP training web site

SAP NetWeaver Gateway Course Available - GW100 - Building OData Services

There is also a self-Pace learning available for SAP Gateway. SAP NetWeaver Gateway Self-Paced Learning - Technologies - SCN Wiki

12) What are the new features in SP8?

Some of the features are mass activation of services, parallelization of batch queries integration with unit test framework, etc.

SAP NetWeaver Gateway SP8 is out

13) What is the typical enterprise landscape?  Is a reverse proxy used in the DMZ?

In majority of cases, typically reverse proxies are used. There is specific technical documentation on Service Marketplace for customers and partners, and on SCN.

14) How is SAP Gateway different from Web Services?

Generally Web Services are SOAP based, where SAP Gateway is REST-based.  SAP Gateway focuses on consumption scenarios and SOAP is more process-to-process, and machine to machine usage.

OData

1) What is OData? How is it used by SAP Gateway?

OData is a Web protocol for accessing structured data following the REST architecture principles. It builds on the AtomPub and JSON standards to allow easy consumption of data by a wide range of devices and client technologies. OData is called the “ODBC for Web” and provides Create, Retrieve, Update and Delete (CRUD) via HTTP protocol. SAP Gateway enables SAP functionality through OData protocol making it simple to access by developers without SAP development knowledge. http://www.odata.org/

http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?_SCLASS=XDP_STRUCT&_SLOIO=0BC6E235A30244CF9C178FEF218D2D67&TMP_…

2) What is REST?

REST is an architectural framework and methodology which is based on addressability, statelessness, connectedness and uniform interface. OData is an implementation of REST

NetWeaver Gateway- Introduction to REST

3) How can SAP Gateway help translate SOAP service into OData?

SAP Gateway provides a way to translate existing SOAP service into OData for usage in user centric scenarios.

SAP NetWeaver Gateway - SOAP and OData Services

4) When will OData version 4 be supported by SAP Gateway?

OData version 4 is planned to be supported SAP Gateway.

5) How is OData integrated to SAP Lumira?

As part of SAP Lumira SP11, there is integration with Gateway to the back end systems. Gateway is the key connector.

6) Are there any tutorials on customer REST channels and offline capabilities of OData?

SAP Community Network (SCN) is the best source to review blogs and how-to guides.  Additionally, there are videos on YouTube.

SAP Gateway

7) Is OData from SAP HANA different from OData from SAP Gateway? Are there other products from SAP with OData?

Yes, HANA has its own OData capabilities.  There are some other products, like SuccessFactors have their own REST-based, OData.  Ariba’s roadmap includes having OData capabilities as well. The OData in HANA or other solutions is the same as OData from GW.  The only difference is the tools and service provisioning.  This should be checked with each of the respective product teams.

8) Where can I find example models of OData? Are there videos to demonstrate how OData models, implementation services and UI code are created?

YouTube channels have introduction videos and additional videos to talk about Provisioning and Consumption.

SAP NetWeaver Gateway Tutorial: Provisioning a NetWeaver Gateway service based on screen scraping - YouTube

SAP NetWeaver Gateway Tutorial: Create iPhone app using SAP Gateway Consumption Tool - YouTube

Developer

1) As a developer, where can I find tutorials/documents that can help me in building various apps using SAP Gateway?

This SAP Gateway curriculum gives you a complete list of tutorials and documents to help you get started with SAP Gateway

SAP NetWeaver Gateway Self-Paced Learning - Technologies - SCN Wiki

2) Where can I get SAP Gateway hands-on system?

The following document will guide you through the hand-on system for SAP Gateway

Developer & Trial Editions: SAP NetWeaver Application Server ABAP and SAP Business Warehouse powered by SAP HANA

3) What kind of application can we develop on SAP Gateway?

Any platform which can consume HTTP protocol can create an application on SAP Gateway. There are plug-in from SAP Gateway available as part of Gateway productivity accelerator toolkits for Android, HTML5, iOS, PHP let you develop applications in these environments.

SAP NetWeaver Gateway Developer Tools

You can also find more plug-in for OData on http://www.odata.org/libraries/

4) What are the deployment options?

The deployment options have been explained in the following blog

SAP Gateway deployment options in a nutshell

5) What are the different development approaches?

The development approaches can be either using service generators or hard coded in the back end system. This SAP Help Documentation explains these two approaches:

Development Approaches - SAP NetWeaver Gateway - SAP Library

6) How is security handled by SAP Gateway?

This SAP Insider article describes the options available for authentication and single sign on

SAPinsider: Take Advantage of Cross-Platform, Cross-Device Access While Keeping Your Data Secure with SAP NetWeaver Gateway

7) What are best practices from performance point of view for SAP Gateway?

This document provides a list of do’s and don’ts for developers with focus on performance aspects

http://aiokeh.wdf.sap.corp:50000/SAPIKS2/navTreeOpen.sap?_SCLASS=XDP_STRUCT&_SLOIO=0BC6E235A30244CF9C178FEF218D2D67&TMP_…

8) How to connect SAP Business Suite to SAP HANA Cloud Platform using SAP Gateway as a service trial edition?

The following demo scenario shows how to bring data from SAP Business Suite into HANA Cloud via SAP Gateway as a service and everything is based on the free trial version for you to try it out. Please note:  GWaaS is currently only part of the HANA Cloud

How to connect the SAP Business Suite to the SAP HANA Cloud Platform using Gateway as a Service Trial Edition

Partner

1) Can I get an overview of SAP Gateway Ecosystem and available partners?

Since its general availability in October 2011, SAP Gateway has enjoyed significant adoption in the market by both customers and partners. As of April 2013, about 90 partner solutions have been certified and published on SAP Partner Information Center, SAP EcoHub and SAP Store. SAP Gateway’s partner portfolio includes ISVs, SIs and VARs of various sizes.

2) Where can I find list of solutions built by partners?

List of all the partner built solutions can be found on the below link

Adoption of SAP NetWeaver Gateway in the Partner Ecosystem - Part 1

3) How can I find solution briefs written by partners?

In this blog, you can find solution briefs written by 5 of our partners on their solutions and their recent experiences.

Adoption of SAP NetWeaver Gateway in the Partner Ecosystem - Part 2

Related Products

1)How does SAP Gateway relate to SAP Gateway productivity accelerator for Microsoft and Duet Enterprise?

Duet Enterprise and SAP Gateway for Microsoft are solutions built on SAP Gateway and you can find more details about these solutions here

SAP Microsoft Interoperability

2) What other SAP Products use SAP Gateway?

You can find list of all products which are built on top of SAP Gateway in this blog.

Getting Started with SAP Gateway see the last section

Hello All,

I am needing some assistance in knowing how to handle an HTTP OPTIONS request. I have a front end JavaScript developer that is performing an AJAX request to my gateway URL expecting JSON in return. I can execute my gateway URL with the ?format=json parameter, and it renders correctly in the browser. In speaking with my JS developer, his call to my URL is failing because SAP is not handling the OPTIONS request. Specifically, I need set the header information on the OPTIONS request to allow for CORS processing.

Evidently, an AJAX request makes an OPTIONS request before the specified request (GET, POST, etc…). Therefore, I need to set the header data on the Options request. Any help would be appreciated.

I have created a service in SEGW and have added the following code to the method USR01SET_GET_ENTITYSET. I need to find the method that handles the OPTIONS request.

data: ls_header type ihttpnvp.

   ls_header-name = 'Access-Control-Allow-Origin'.

   ls_header-value = '*'.

   /iwbep/if_mgw_conv_srv_runtime~set_header( ls_header ).

   ls_header-name = 'Access-Control-Allow-Credentials' .

   ls_header-value = 'true' .

   /iwbep/if_mgw_conv_srv_runtime~set_header( ls_header ).

   ls_header-name = 'Access-Control-Allow-Headers' .

   ls_header-value = 'Content-Type, Authorization' .

   /iwbep/if_mgw_conv_srv_runtime~set_header( ls_header ).

   ls_header-name = 'Access-Control-Allow-Methods' .

   ls_header-value = 'POST, GET, OPTIONS, PUT, DELETE, HEAD' .

   /iwbep/if_mgw_conv_srv_runtime~set_header( ls_header ).

Thanks in advance!

Allen

Hello everybody,

I'm currently having an issue with uploading files via SAP Netweaver Gateway.

What I'm trying to do is to capture a video and sending it to SAP Gateway. I'm coding in JAVA and I'm using the odata4j-Framework for consuming and producing OData. My current tries involved to encode the video to a base64-String and sending the string to the gateway... The encoding of the video works quite fine but the prolbem is that the string is really veeeeeeeeery huge ... Everytime when I'm trying to make the request I receive a "OutOfMemoryException".

Is there actually a way with which I'm able to send a video file with odata4j to the SAP Netweaver Gateway??? I'm really looking forward to your help!!!

Greetings

Stefan

Hi Experts, We are upgrading our system to SAP NetWeaver 7.4 and as part of this we are relapsing UWL with Unified Inbox. In UWL we have created few custom columns and we would like to have same custom columns in Unified Inbox also. Can somebody direct me how we can create custom column in Unified Inbox. Thank you, Kishore

Hi all,

When we invoke invoke Create to post data against NW GW, the response includes the listing of the whole entity created - it seems that Read statement is invoked automatically and its response content is provided as a response body for the Create command. Is it possible to customize the Response body? So that it would for example only return HTTP Status '200'? To save downstream bandwidth?

Thanks a lot.

Pavel

Introduction

With SAP NW Gateway SP08, there is an option to create OData service by importing search help. Please refer https://help.sap.com/saphelp_gateway20sp08/helpdata/en/29/4e9c1b65f3499cbec6365f59dfa3c8/content.htm

You will find some of the details at https://help.sap.com/saphelp_gateway20sp08/helpdata/en/77/ec405224753607e10000000a441470/content.htm

In this document, I will demonstrate creation of OData service based on search help BRF_SH_CUSTOMID (Search Help for Flight Customers).

Steps

1) Create project ZSEARCH_HELP. Right click on Data Model and Select Import-->Search Help. Provide Entity type name FlightCustomer and provide Search help (from F4 ) as BRF_SH_CUSTOMID and click Next button.

2) Select parameters from RESULT_LIST which you want to include in search help and click Next. Here, I will select all parameters as shown below.

3) Mark fields which you want to be key properties. Here I will select property ID as key property. Click Finish.

Note that Create Default Entity Set is marked by default and hence we need not to create Entity set as wizard will create it.

As result of this step, entity type and entity set will get created as displayed below,

4) Now we will do service implementation for Query and Read operation. first let's do it for Query operation. Expand Service Implementation folder and right click on GetEntitySet(Query) operation and select Map to Data Source. Select Data Source Attributes as displayed below.

Press Propose Mapping button which will enable system to select mapping automatically.

5) Now let's map GetEntity (Read) operation. Right click and select Map to Data Source. Select Data Source Attributes as mentioned above. Click on propose Mapping but as this is read operation, we need to provide input key to read it.Click on Insert Row button and add input key property. here I will select ID. then drag the ID parameter from right screen to Data Source Parameter. This will provide input key as ID.

Now Check project consistency and if everything is okay then click on Generate Runtime Objects. This will generate runtime artifacts. Finally do the service maintenance which involves service registration. Click on Maintain which will open window for Gateway Client.

Service Testing

Let's test Query operation with request URI /sap/opu/odata/sap/ZSEARCH_HELP_SRV/FlightCustomerSet

It will display the search help result as below. you can use $count, $top etc query parameters.

Now let's test Read Operation with URI /sap/opu/odata/sap/ZSEARCH_HELP_SRV/FlightCustomerSet('00000017'). Output will be as below,

Closing Remarks

With the import wizard, it is very simple to create OData service based on elementary search help. please keep in mind below constraints. Reference https://help.sap.com/saphelp_gateway20sp08/helpdata/en/77/ec405224753607e10000000a441470/content.htm

The following are the constraints:

• Only elementary search helps are supported. Collective search helps are not supported.
• Search helps that call UI in their exit function are not supported, as this cannot be validated by the Service Builder.
• At runtime, a query operation that is based on a search help data source can retrieve a maximum of 9,999entries.

Also note that

Only the search helps in the local SAP system can be used as a data source.

Please feel free to put your comments and suggestions.

Happy learning and Coding!

Thanks for SDN, it helped me a lot to finish this document. I just want to make it available in a single document.

Introduction -

Here, we will focus on how we can build SAPUI5 mobile application consuming GW Service builder from the Eclipse.

Prerequisites -

We need to follow the steps as mentioned below

1. 1. Download and install Java SE6
2. 2. Download and install Eclipse IDE for Java EE developers from Eclipse (download based on your system type either 64-bit or 32-bit)
3. 3. Download UI Development Toolkit For HTML5
4. 4. Install the SAP NetWeaver Gateway Productivity Accelerator (GWPA) features.
5. 5.You should have Eclipse IDE with SAP UI development toolkit for HTML5 and access to SAP NetWeaver Gateway system.

Steps:

• First finish the installation of Eclipse.

• From the Eclipse menu choose Help->Install New Software

                        Add the URL in Work with: https://tools.hana.ondemand.com/junoand click on Add, give any name and click OK. (see the below screenshot)

• Select the feature(s) you want to install and follow the steps of installation wizard.(see the below screen shot)

• After selecting SAP NetWeaver GWPA (Toolkit for HTML5), UI Development Toolkit for HTML5 click 2 times ‘Next’ and then ‘Finish’ as shown below. It will take some time and in between it will give some warning messages, click ‘OK’. At last you need to restart the eclipse for changes to take effect.  After that you will get some error messages, as of now avoid it.

You should also need to install SAP NetWeaver Gateway plug-in for Eclipse which can be downloaded at

New_Gateway_plug-in_for_ Eclipse

  In the above URL ‘Click here for download’ as shown below. Accept the license agreement, after that it will ask for SDN User credentials, once that is done, the download starts automatically.

Procedure –

Steps involved for creating SAPUI5 mobile application consuming Gateway Services with the help of Gateway plugin for eclipse.

Step 1:

         Select Project from the path shown in the below screenshot.

      In Eclipse Open Menu->File->New->Other

Step 2:

          Select Starter Application Project as displayed in below screen shot

Step 3:

         Give Project name and select HTML5

Step 4:

         Select List/Details Application (SAPUI5)

      Step 5:

In this step, we need to select Gateway service either from remote location or from file system. We will choose Remote location and connect to SAP Gateway system.

    Step 6:

If the connection to gateway system is already established, click on catalog and follow from STEP 10. Otherwise, if it is for the first time, click on manage connections.

   Step 7:

       In the below screen, click on add, you will see pop-up screen asking for a User Credentials.

Step 8:

As displayed below, connect to the gateway system and provide the user details. Here I provided user credentials of  system and Do not check the HTTPS.

• Provide Server Host  - Mandatory
• Provide Server Port   - Mandatory
• Provide Client           - Mandatory
• Username                - Mandatory
• Password                 - Mandatory
• Select checkbox Save Password and click OK.

    Step 9:

       If the connection established successfully, you can see the below screen, and click on ‘Add’.

Step 10:

Now, you will be able to see the list of all projects available in your SAP system and you can search for services.

Step 11:

After selecting the Service Builder, you will be get the below screen.

      Step 12:

       If you followed exactly the same steps as mine, you will be facing this error “There are no addressable collections in the service”

Troubleshooting:

It is not possible to complete the wizard without solving the above problem. So after some time, I found out that when creating your entity set in Gateway Service builder, you should flag the "Addressable" checkbox. But, when I did this and tried to re-generate my service, I faced the exact same issue, the system kept telling me that everything was correctly generated, but nothing was changed at all.

So, first we need to delete the generated classes of the Service Builder and we need to make the necessary changes and regenerate the classes.

As of now, I don’t have required authorizations to perform the delete action, so I am again recreating the service from the scratch.

Old Entity Set screen shot from Gateway Service builder.

New Entity Set screen shot from Gateway Service Builder

Once done save it and generate the classes, from the step 10, you need to select the newly created Gateway Service Builder.

Step 13:

Now, we solved the problem. Here we need to create the list view and details view and add the necessary fields which are to be displayed.

Provide the name for View title and Click on symbol and add the fields, which need to be displayed in the list screen.

Again, click on the symbol to create a new view in the left side of the screen. 

Provide View title and add the fields that are to be displayed in the details View and click on finish.

Now, Our SAPUI5 mobile application is ready for testing.

Step 14:

• Now, you can see the newly created project in the Project explorer.
• Right click on the project, Run as->Web App Preview

However I couldn't test it: while choosing "Run as >> Web App Preview" in the context menu, only a blank page was displayed.

How to Fix the Issue:

To fix this, we need to follow few steps, it is bit complicated, after doing lot of research, we got to do this. Please follow accordingly

• Go to the folder where we initially downloaded the UI Development Toolkit For HTML5
• Extract the folder and inside that, again extract “sapui5-static”.
• Go to sapui5-static->resources, drag and drop resources folder into the Eclipse inside the “WebContent “folder. (But the problem   here is the resources folder is quite heavy i.e., 91MB and my machine did not support it and Eclipse keeps on crashing).
• So, Instead I can send you light weight “resources” folder which is around 4MB along with this document which makes our life easier.
• After coping the light weight “resources” folder to the “WebContent” folder in Eclipse,

Click on index.html under WebContent folder.

In the index.html, edit the code as shown in the below screen shots.

So, I changed it to src=”./resources/sap-ui-core.js” and save it.

After saving it, run your project. It will ask your username and password, once that is done you can see the output in index.html as below.

Copy the URL and paste it in Internet Explorer, provide user credentials and you are done.

Click on the Address type in the list view and you can see the details view.

Conclusion:

Do the same and follow the same steps as we did here and you can see the output. Let me know if you have any concerns.

Your suggestions and inputs are always welcome

Hi Guys!

I am tried install to Add-on IW_BEP on SAP ERP 6.0 Ehp6 and I have this error on Saint: Error message: OCS Package SAPK-200AGINIWBEP, tp step "A", return code 0008

I verified the STMS request and is showing the error:

Table /IWBEP/D_MGW_SUB could not be activated

(E- index 010 e 1 to table /IWBEP/D_MGW_SUB have identical fields)

Table /IWBEP/I_MGW_SRH could not be activated 

(E- index /IWBEP/I_MGW_SRH-SVC (field NAMESPACE does not exist in table) )        

When I tried run the SAINT in phase import_proper I have this error:

Error during executing the tp command 'tp IMPORT all ECP ...'

tp return code: '0008' , tp message: 'A tool used by tp produced errors' , tp output:

This is tp version 380.13.51 (release 721, unicode enabled)

ERROR: stopping on error 8 during DD ACTIVATION

stopping on error 8 during DD ACTIVATION

tp returncode summary:

TOOLS: Highest return code of single steps was: 8

WARNS: Highest tp internal warning was: 0118

standard output from tp and from tools called by tp:

How Can I resolve this issue in stms request? I tried active the table by SE14 I can't ...          

Thanks!

Daniel Berto Santana

Overview

This year SAP released many product updates like SAP Fiori, SAP Mobile Platform or SAP UI5 aimed to improve the user and developer experience. All the mentioned product updates have one thing in common – they are based on the development principle of an open interface standard (OData) as the abstraction layer between the user interface and the backend.

A challenge here was on the one side to improve the support for even more user-groups or available combinations of already installed SAP software at our customers and – on the other side - still offering the advantages of a consistent developer experience and supportability for all the different scenarios.

For those who are not too familiar with all the new developments you can find here a condensed overview on all the already existing and new possibilities (in the context of OData):

• ‘SAP Gateway’ 2.0: an ABAP-based framework to enable OData/REST based connectivity for all ABAP-based SAP products like SAP ERP, SAP SCM, … SAP Gateway consists of two major blocks:
  • the backend enablement (IW_BEP) which has to be deployed on the ABAP-based backend and is the basis for content development
  • The SAP Gateway Hub which takes over the connectivity to one or many SAP backend systems and the generation of OData.
• ‘SAP Mobile Platform’ 3.0: the embedded Gateway Components (Java) are taking care of the integration of various data sources like JDBC, JPA, SAP Gateway based service definitions (IW_BEP) or SOAP. The output of the Gateway Components is OData – which is then the starting point for additional mobile specific services inside SMP like device specific push notifications.
• ‘SAP Process Orchestration’: The embedded Gateway Java can connect to SAP Gateway based service definitions (via the backend enablement – IW_BEP) and transform them into OData without the need to have an SAP Gateway Hub (based on ABAP technology) installed.
• ‘HCI OData Provisioning’: For cloud based scenarios this service is connecting to the SAP Gateway backend enablement (IW_BEP) and is making the OData available directly on the HANA Cloud Platform (trial version only).

Compared to two years ago – where only SAP Gateway (ABAP) could provide the required OData Services there are now many more options available. The only missing piece is now to identify the right technology for the required scenario…

Scenario Overview

The good message in the beginning – whatever OData Services get developed in an ABAP-based SAP backend systems (using IW_BEP) can be used directly in any scenario mentioned below. The OData Service could even be used by more than one technology at the same time. So if you develop for example in an ABAP-based System an OData Service for leave requests then you could use this via the SAP Mobile Platform in a mobile app and as well via Microsoft Outlook.

Of course first the OData Services have to be created in the ABAP-based backend systems via the Gateway Service Builder (transaction SEGW – being part of the IW_BEP Add-On). Once the services are implemented there are now various choices for the final transformation into OData.

SAP Gateway Hub

Customers having built up development and operations skills for the SAP Application Server ABAP can set-up and operate the SAP Gateway Hub which is then connecting to the various SAP Backend Systems. Also the SAP UI Add-On is typically installed on top of the SAP Gateway Hub System. Everything is based here on the same technology (the SAP NetWeaver Application Server ABAP) which makes it easy to embed SAP Gateway into already existing maintenance and operations procedures.

SAP Process Orchestration

Customers who are already using SAP Process Orchestration as a middleware solution can now activate the OData generation of ABAP-based SAP Systems directly inside PI. This has the advantages that no SAP Gateway hub system is required any more (which saves cost for hardware and operations) and also strengthens central governance.

This setup is providing roughly the same level of supported OData features as the SAP Gateway hub. But to set the expectations right – there are a few points that need to be considered with this scenario:

• One feature of SAP Gateway is not yet supported in this context – the Task Gateway. This Task Gateway is a capability to connect to various backend systems (SAP ABAP Workflow, SAP BPM and non-SAP Systems) and aggregate the workflow items coming from the various sources into one single OData Service. This one OData Service is then used by the Unified Inbox, other mobile workflow apps or in Microsoft Outlook. So if a unified workflow inbox is required still the SAP Gateway Hub (ABAP) has to be installed.
• Also there is no integration from the OData generation capability to the integration flows in PI. As a result, it is not yet possible to provision OData services from non-SAP systems e.g. via REST, JDBC or SOAP. The only source for OData exposure is currently the SAP Gateway backend enablement (IW_BEP).

SAP Mobile Platform

Organizations that want to provide online or offline mobile apps to their users often have the challenge to connect to ABAP-based SAP Systems and also to other technologies which can only be reached via e.g. SOAP, JPA or JDBC. SAP Mobile Platform 3.0 provides both the connectivity to the IW_BEP-based backend services from the SAP system but also the connectivity to non-SAP data sources.
Also here roughly the same level of OData features are supported than with the SAP Gateway Hub. And also in this scenario the Task Gateway is not supported.

SAP HANA Cloud Platform

With the increasing importance of cloud-based scenarios also the relevance of hybrid scenarios is becoming more important. At hybrid scenarios the SAP systems on premise are being used as systems of record where the relevant business data is managed in a central location. Enhancements to the backend system (like alternative user interfaces or an own application logic) could be realized via application development on the SAP HANA Cloud. Direct access to the relevant data from the backend system is required.

‘HCI OData Provisioning’ is a cloud based service to securely connect (via the SAP Cloud Connector) to the OData Service definitions located on the Gateway backend enablement (IW_BEP). As a result there is now an OData Service available in the SAP HANA Cloud Platform which is directly connected to the business logic from the SAP System on premise.

And similar to the other approaches also here more or less the same features are available
than with the SAP Gateway Hub. There is also no support for Task Gateway.

This functionality is currently only available in the trial environment of the SAP HANA Cloud Platform. Productive Usage is not supported.

Summary

All mentioned technologies have one thing in common – to best support our customers with OData support no matter which technology is being used. All the
OData-related topics like administration UIs or design time tools remain consistent (for the Java based applications). And – in addition – all the OData services which were defined in the SAP backend can be re-used across all the various technologies.

Links:

SAP Gateway

• SAP Community Network: http://scn.sap.com/community/gateway
• YouTube:https://www.youtube.com/playlist?list=PLWV533hWWvDl9IBntNQKt5xLGhWsppiDd
• SAP Online Help: http://help.sap.com/nwgateway
• Self-paced learning: http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=318672261
• OData Curriculum: https://www.sapappsdevelopmentpartnercenter.com/en/build/mobile-platform/odata-curriculum/
• SOAP Connectivity for SAP Gateway: http://scn.sap.com/docs/DOC-49811
• UI Add-On: http://scn.sap.com/community/ui-technology/blog/2012/09/04/introducing-the-new-ui-add-on-for-sap-netweaver
• Task Gateway: http://help.sap.com/saphelp_gateway20sp09/helpdata/en/e4/3143530d9e0050e10000000a44176d/content.htm?frameset=/en/56/d0cc05b564411e841141f68294e29f/frameset.htm&current_toc=/en/57/a41787789c4eca867d9a09696fc42c/plain.htm&node_id=736&show_children=false

SAP Process Orchestration

• SAP Online Help – Exposing Back-End Data as OData Services: http://help.sap.com/saphelp_nw74/helpdata/en/91/0ba096bfe34cbcb1e7eccf0d347c63/content.htm?frameset=/en/7f/b1345a57214cc887bd3b5ac272774d/frameset.htm&current_toc=/en/b5/0a32b8ef054513a3f7ca52f4c8a7d5/plain.htm&node_id=15&show_children=false

SAP Mobile Platform

• Online Help (SP4): http://help.sap.com/saphelp_smp304svr/helpdata/en/7c/20051470061014a27cf7962ebae5f8/frameset.htm
• SAP Community Network: http://scn.sap.com/docs/DOC-49861
• Blog on Integration Gateway by Mustafa: http://scn.sap.com/community/mobile/blog/2014/09/27/whats-new-in-integration-gateway-in-sap-mobile-platform-30-sp04

SAP HANA Cloud Platform - HCI OData Provisioning

• Hands-On Blog: http://scn.sap.com/community/gateway/blog/2013/09/09/how-to-connect-the-sap-business-suite-to-the-sap-hana-cloud-using-gateway-as-a-service-trial-edition
• HCI OData Provisioning: http://scn.sap.com/docs/DOC-54050
• SAP Online Help: https://help.hana.ondemand.com/hci_odata_provisioning/frameset.htm
• Trial:http://hcp.sap.com/index.html

SAP API Management

• SAP API Management: http://scn.sap.com/community/developer-center/api-management/blog/2014/10/18/unlocking-data-harmonioulsy

Hi ,

I am planning to install SAP netweaver gateway on a separate server , is there any Licensing or cost required to perform that?

Regards,

Ahmed Sobhi

Tags edited by: Jitendra Kansal

Overview

Open Interfaces play a very important role in the area of Product Lifecycle Management. Modern designs involve IT-support in the area of mechanical design, electrical / software development, all type of simulations and much more. With regards to the wide area of integration this blog distinguishes between asynchronous server-to-server scenarios and synchronous user-centric scenarios – even if there is a certain overlap in between.

Server to Server communication is required to exchange information between two (or more) systems in an asynchronous mode. Example for this would be a Material Master which is getting copied from a non-SAP Team Data Management System over to the SAP PLM System once its status was set to ‘released’. Typically SOAP or textual formats like ASCII or XML files are used for these asynchronous scenarios.

Opening SAP PLM for synchronous user centric scenarios has different reasons:

• Beautification of the User Experience: Providing mobile or user-interfaces optimized for specific use-cases based on SAP PLM – using e.g. Microsoft Office or Microsoft SharePoint, HTML5 or native mobile user interfaces.
• Mashing-Up data from various systems: Bringing information from various systems together in one user-interface
• Integration: Allowing other systems to access an SAP System via REST-based APIs to query e.g. the status of a material from another system

This blog covers the synchronous user-centric scenarios that are covered with SAP Gateway. Asynchronous scenarios are covered with other technologies like SAP Process Orchestration (http://scn.sap.com/community/process-orchestration) or the cloud based HANA Cloud Integration (http://scn.sap.com/community/hana-in-memory/blog/2013/10/22/hana-cloud-integration-getting-started).

SAP Gateway

Via SAP Gateway it is possible to add RESTful APIs in the open format of OData to the existing SAP Business Suite / SAP PLM with little effort. Various ways to create the OData Services are supported by SAP Gateway:

• Code-free generation of the OData Services based on existing Remote Function Calls (RFCs) done via mapping in the Gateway Service Builder (Transaction SEGW)
• Manual development by re-definition of methods provided by SAP Gateway super-classes for the required methods like query, read, update or delete.
• Code-free generation of the OData Service based on existing object-oriented implementation of the business object like e.g. Material Master or Engineering Change Record. In the SAP PLM context the business objects were developed by SAP using the SPI-framework (http://wiki.scn.sap.com/wiki/display/SPI/Home;jsessionid=24F422E24DF42AAD8D7037821D1B940F)

Required components, Service Packs and Notes

When looking at e.g. the implementation of the Material Master we have to differentiate two things. One topic is the functionality of the generic
framework that was used in order to implement the service – the SPI framework. In addition the second part is also important – the way how the Material Master got implemented in the SPI Framework.

SAP Gateway is already supporting the SPI framework since the Service Pack 4 of SAP Gateway. All features of the SPI framework were supported (query, read, update, delete …). Unfortunately the implementation of many SAP PLM objects did not support Query and Update methods of the SPI framework. Reason was that these objects were developed optimized for the Floorplan Manager and WebDynpro ABAP. So Enterprise Search and state-full communication were available in the WebDynpro-based user interfaces which meant that there was no need to implement this two features in the underlying SPI service.

As OData is becoming more and more popular now the ability to query was added to the implementation of many SAP PLM objects via Service Packs and / or notes. This makes the development of OData-based applications much more easy – no need to manually program the search. The possibility of updating the SAP PLM objects is not available.

These enhancements will add the possibility to query via OData services to the following SAP PLM objects:

• Material Master (PLM_MAT)
• Document Info Record – SAP DMS (PLM_DIR)
• Engineering Change Record (PLM_ECR)
• Engineering Change Number (PLM_ECN)

So overall with the installation of the right Service Packs for your components you will save a lot of manual effort. Once all the required enhancements are in the system you are ready to go and you can start generating OData services.

Generating an OData Service for the Material Master

SAP Gateway Service Builder

This blog from Ashish is already describing the process of creating an OData Service based on an SPI Object very nicely: http://scn.sap.com/community/gateway/blog/2012/11/27/how-to-create-sap-netweaver-gateway-service-for-spi . So this blog will not go to all details, but will highlight the generation process especially for the Material Master from SAP PLM via the transaction SAP NetWeaver Gateway Service Builder (Transaction SEGW).

First a new project has to be created. A click to the context menu of the Data Model is then allowing redefining an SPI Service. For accessing the Material Master, the technical name of the Material Master (PLM_MAT) has to be selected from the SAP PLM System. This SAP PLM system could be the same system as the SAP Gateway system, it also could be another system communicating to the stand-alone SAP Gateway system via Remote Function Calls (RFCs).

The Material Master is a very central element of SAP ERP and SAP PLM. So there are a lot of attributes to support all the various aspects of central master data. Typically in a mobile scenario not all of the many 100eds of attributes are required. A reduction of the transferred data from the backend to the client
will also reduce the required bandwidth and will improve with this of course performance.

Let us assume that in this small example only the following five attributes will be required in the new user interface:

• Material Number (Key)
• Description
• Base Unit
• Volume
• Industry Sector

These attributes can easily be selected in the wizard that appears in the BASIC_DATA Entity Type. Unfortunately the generated names will be very technical. So a manual change to a more readable notation is required. This can be done in the Service Builder by the Redefinition of Attributes.

Once this manual activity is done the service can be generated.

Activating

Directly from the SAP Gateway Service Builder transaction the Service can now also be published from the backend to the central Gateway Server. Once this is done we are already ready for the last step – the testing of the service.

Testing of the service and examples

For a simple ‘smoke test’ we can use a query that will return two random Material Masters in a JSON format. The perfect transaction for this would be the ‘SAP NetWeaver Gateway Client’ transaction (/IWFND/GW_CLIENT). Here we can enter this query string:

http://server_name:port/sap/opu/odata/sap/Z_MAT_MASTER_SRV/BASIC_DATACollection?$top=2&$format=json

And as a result we receive the details from the backend system in JSON format:

As a next step you will see a list of more realistic examples for queries that are already supported out-of-the box without manual coding. Filtering for a special Material Number could be done in two ways, via a $filter statement or directly as a key (the Material Number is the key field of this service):

• http://name:port/sap/opu/odata/sap/Z_MAT_MASTER_SRV/BASIC_DATACollection?$filter=MaterialNumber eq ‘P-100’
• http://name:port/sap/opu/odata/sap/Z_MAT_MASTER_SRV/BASIC_DATACollection('P-100')

Filtering is also supported for other attributes like the material description:

http://name:port/sap/opu/odata/sap/Z_MAT_MASTER_SRV/BASIC_DATACollection?$filter=MatShortTxt eq ‘Pump’ is now returning a list of all Materials that have the short text ‘Pump’ assigned. Only a more complex queries could result into a full table scan – so please make sure to test the created service upfront. Example for a query that is taking very long would be:

http://name:port/sap/opu/odata/sap/Z_MAT_MASTER_SRV/BASIC_DATACollection?$filter=substringof (‘Pump’, MatShortTxt) eq true

One of the advantages when using SAP Gateway is the very convenient way to log and trace errors or to get an information about the performance behavior via the Gateway Tracing Tools (Transaction /IWFND/TRACES).

Performance Traces, Payload Traces or Error Logs provide a variety of additional information helping to optimize the implementation or identify errors.

Summary

In this blog I wanted to explain how easy it now is to get an OData Service generated with the enhancements provided with the latest Service Packs of SAP PLM. The master data managed by SAP PLM is very often a required piece of information for follow-on processes. The opening up of SAP PLM is now helping to bring the data easily in other environments.

Appendix

The table below provides an overview which SP has to be added as a minimum to add the query possibility to the system. The enhancements are also available as notes – please note that some notes require additional manual steps for the implementation. This list also is the maximum number of notes – depending on your SP-level there could be much less notes requires. The SP5 of IW_SPI is part of SAP Gateway SP9.

Detailed list of Notes:

1728963 Support Package queries are missing.

1913499 Access to the data of a node by means of association

1953183 Failure of SPI Service Generation  

1992454 SPI OData Services with Query Options like $top and $skip Do Not Work in HUB scenario

1992501 $filter and $top is Returning Only Keys in the Query Response for SPI

1996130 Duplicate Records while calling Material SPI Query

2007909 Downport of START_ROW parameter

2010845 Disabling NAVI Parameter in SPI

1891137 SPI: $select Based Optimization for Query/Read

Hi All,

I am trying to fetch the value of X-CSRF-Token using the REST client. Any how it always coming blank.. and showing Response Headers has been hidden.

GET is returning required application and executing the service.

"Response headers Headers panel has been hidden"

Please advice how we can get token value or un-hide the panel to get value.

Thanks

Rajesh