on 01-31-2018 5:53 AM
Hi Experts,
I need a requirement to move Table functions from development system to quality system.
I create a Table function using SAP Develoment Perspective. And I wan to move it from the Dev to quality system.
I'm trying that Delivery units but I get all the view and objects except Table functions.
any suggestions please..?
Thanks Florian. you are absolutely right about the authorization in QA system and above and that concludes not using the import/export mechanism for transporting the table (catalog) to another system.
said that, pls shed some light on what other ways the transporting of tables can be achieved.
Regards,
Hari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Florian,
Would you please tell us how we can move tables (Created using SQL), virtual tables? We have change mangement system which only capture objects which are created in Repository packages(Like Flow graphs) and Views can captured in Delivery unit. so What is the perfect way to trasnport schema based objects from one system to other system in SAP HANA Cloud.
Looking forward to connect with your response
Thank You
Sunil Sharma
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kabilasaran,
In order to transport table function , you should use Catalog object, not delivery unit..
Step1:First log on to your development server -> File->Export ->SAP HANA-> Catalog Objects->Next-> Type the table function name to transport -> Then save it in your local system or in the server.
Step 2: Log on to your Quality server-> File-> Import->SAP HANA -> Catalog Object -> Search the table function to import ->finish
That's it.
Regards,
Shawon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, but your answer/recommendation is only valid in case you have some kind of sandbox systems for some kind of tests. But it is not valid for a professional landscape setup with a valid transport/deployment strategy. Arguments against your recommendation are that catalog objects should not be used if necessary, because then you loose all lifecycle management comfort. Another point is that many developers do not have (and should not have) rights on an QA system to change coding artifacts (so a developer can crash/hinder the execution of tests for instance).
In the XS Classic world, as used here, the delivery via delivery units or changes is the way to go. For XSA, which does not use anymore the HANA repository, but a Git based repository, the story is another one.
Regards,
Florian
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.