on ‎2023 Apr 20 12:53 PM
Hello,
We are trying to implement some of the dataflows of an older BW system into BW Bridge.
One of the first things we are trying to implement is a routine in a transformation that reads the hierarchy table of an InfoObject to derive an attribute based on the position of the leaf in the hierarchy.
Unfortunately, use of tables, data elements, function modules is extremely restricted on BW bridge (and as I understand other cloud products). Only objects 'released' by SAP can be used in code and views, but this list is really short.
Surely, there must be a way around this?
In our case, not only are there thousands of lines of code that are unusable, I don't even see a way around it if the hierarchy table can't be read.
Request clarification before answering.
Hello Jorg,
We are planning to expose the hierarchy H table as released objects with the initial release of 2305 or with hotfix collection 4 of 2305, see SAP BTP ABAP Environment – Maintenance Windows and Major Upgrade Windows in 2023.
Note that you have to activate the InfoObject after the upgrade to expose the hierarchy H tables as released objects.
Regards,
Dominik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jorg,
Migrating own ABAP code to SAP BW bridge is a semi-automatic task that may require manual changes to the code. The set of released function modules and classes is not necessarily carved in stone. We validate requests to release additional function modules or classes on a case by case basis.
May I ask what is the use case to read hierarchy tables?
Regards,
Dominik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, this is not necessary. You can call your own custom developed function modules and classes without releasing them.
My previous comment was about function modules, classes, interfaces, data types, database tables, etc. provided by SAP which may - or may not - be released. See the API State tab in the Properties view of the artifact in question.
Thanks for reply, Dominik.
Now, I'm confused a bit because of following situation: On BW Bridge side, I've recreated my Z* FM, which is being used in Start routine of my transformation. While performing the Shell conversion for this transformation, I've got the error message:
"Error in generated class: The use of FUNC Z_*** is not permitted". The system I'm migrating from is BW4HANA 2021.
Maybe, you've got any suggestions how to resolve it?
Hello Dominik,
Thanks for your reply. We are dealing with an old BW system with not a lot of data flows and it was decided to "copy-paste" only what was needed and an RFC between BW and BW bridge is not set up. Would using the remote conversion release the objects that are used in the old ABAP code?
The use case for the hierarchy is as follows. Based on a profit center hierarchy, we need to determine a value for an attribute based on a node higher up in the hierarchy. Not all parents and leaves are on the same level, unfortunately. The orginal code - over 10 years old - makes use of recursion to solve this.
I could rewrite the code, but because we are not able to read the hierarchy and RS* tables or use the function modules (we aren't even allowed to type fields with SAP data types), I don't see how I can.
I could try to do it in the Datasphere, but I'm not sure it is possible being limited to SQL.
Kind regards,
Jorg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jorg,
Using remote conversion would not change the release state of ABAP classes or function modules.
We are currently discussing whether hierarchy data can be made available to your ABAP code and if so how. Keep you updated.
Regards,
Dominik
| User | Count |
|---|---|
| 11 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.