Skip to Content
Technical Articles
Author's profile photo Prabuddha Raj

Hdbsynonymconfig and cross container access in Hana Cloud

The blog has been written as an extension of hdbsynonym usage in sap hana cloud as compared to sap hana XSA 2.0 environment. Implementation of the synonym config files and hdbsynonym differs slightly in sap hana cloud environment.

For cross container access, if it is a hdi container in a different space or any schema within the same database where data is being replicated from an on premise S4hana system/oracleDB/any data source. The following steps needs to be implemented:

  • Each cross container service binded to your sap mta application should be bounded to one schema. For ex: if you are getting data from big query and s4hana onprem, you should create 2 separate UPS services and adding the schema name in each service:

{

“driver”: “com.sap.db.jdbc.Driver”,

“endpoint”: “https://api.cf.eu20.hana.ondemand.com”,

“host”: “<hostid of the hana cloud instance>”,

“password”: “<>”,

“port”: “443”,

“tags”: [

“hana”

],

“schema”:  “<schemaname>”

“user”: “GRANTOR_SERVICE” (the user in the database with access to the particular schema)

}

  • After you have added the schema name in the ups service, the hdbsynonym and hdbsynonymconfig file should follow the below format

Hdbsynonym file:

{

“SYN_PT_VBAK”: {}

}

Hdbsynonymconfig file:

{

“SYN_PT_VBAK”: {

“target”: {

“object”: “PT_S4_VBAK”,

“schema.configure”: “ServiceName_1/schema”

}

}

ServiceName_1 is the logical service name in your mta yaml file.In hana XSA “*.configure” worked as a property but in sap hana cloud it doesn’t compile.
For more details on creating hdbsynonym and hdbsynonymconfig follow the below documentation:

https://help.sap.com/viewer/4505d0bdaf4948449b7f7379d24d0f0d/2.0.02/en-US/aad1653a9b95422089fec53f48c2899e.html

Assigned tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Jun Wu
      Jun Wu

      what's the difference from xsa?

      my Hdbsynonymconfig in xsa seems to use same format like your example.

      Author's profile photo Prabuddha Raj
      Prabuddha Raj
      Blog Post Author

      Hi jun,

      the example that i have provided works both in sap hana cloud and in XSA but the below syntax
      doesnt work in sap hana cloud :

      “SYN_PT_VBAK”: {

      “target”: {

      “object”: “PT_S4_VBAK”,

      “*.configure”: “ServiceName_1”

      }
      i read some examples with the above syntax in sap archives for sap hana XSA development

      Author's profile photo Jun Wu
      Jun Wu

      I just checked in xsa, you cannot build the db module if you use “*.configure”