GeneXus for SAP Systems FAQ

Official Content

How to use SAP HANA database on SAP Cloud Platform?

You can use a trial account in SAP Cloud Platform to create a database using SAP Hana in-memory database. More information at How to use SAP HANA database on SAP Cloud Platform

How to deploy an application to SAP Cloud Platform?

More information on How to deploy an application to SAP Cloud Platform

Can GeneXus for SAP Systems open GeneXus 15 Knowledge bases?

No, GeneXus for SAP Systems can not open them, since it has not some required components (e.g. Database Reverse Engineering Tool, multiple DBMSes like SQL Server, Oracle, etc, .NET Generator,etc. ).

Can GeneXus 15 open GeneXus for SAP Systems Knowledge Bases?

No, GeneXus 15 can not open them since GeneXus has not some required components  (e.g. Fiori Pattern).

How to get a GeneXus that has the capabilities all together?

Contact http://genexus.com/sales and ask for a specific kit for SAP Systems development.

What's the difference between the values "1.0" and "1.0 SPS 11 or higher" of the Data Store property "Database Information/SAP HANA version"?

See SAC 41124

Why doesn't work new when duplicate on HANA DB?

See SAC 41934
Use for each when none instead.

Inspecting an OData service from SAP Business One I get an error Could not parse as Edmx document?

The complete message is: HTTP 500 - java.lang.IllegalArgumentException: Could not parse as Edmx document
This is because of the version of the OData service, the supported one is V4.0 or up (you can check this in the metadata of the service (<edmx:Edmx Version="4.0" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">).
Some times, in B1 the URI of the service indicate that, i.e. http://www.xx.yy.zzz:50001/b1s/v2 (v2 refers to the version but there is no relationship between the number 2 and the version number)

Inspecting an OData service from SAP Business One I get an error Unsupported kind for attribute BankPagesDueDate: None, Edm.DateTime?

This is because the metadata has an entity with an attribute with the Edm.DateTime type, which is supported for Odata v2, but no longer supported for v4. In the OData v4 the type Edm.DateTimeOffset is used instead.This irregularity with the types and version is given because even if on the metadata is defined that follows the OData v4 protocol, sometimes for Business One, the data types are not the ones used on that version.