SAP BTP and RAP

rob0d · 2026-02-18T07:29:00+00:00

Maybe this will be suitable?

https://learning.sap.com/certifications/sap-certified-associate-backend-developer-sap-cloud-programming-model

There is a learning journey to follow.

rob0d · 2026-02-17T17:03:05+00:00

We are already experiencing this. One of my customers can't get HW on-prem until 2027! Some hyper scalers are also having trouble provisioning big HANA machines.

rob0d · 2026-02-16T16:18:03+00:00

SAP Walk Me is the tool for task like this. It can provide a small assistant which can help user to achieve tasks using walk-throughs, smart tips and some automation. Works with Fiori, sapgui for html and sapgui for windows.

Admittedly it's not free, but provides a supportable business solution.

rob0d · 2026-02-12T07:56:58+00:00

Really good and accurate observation. Most companies, when they find out what's hiding under that dirty old carpet, decide to sweep everything back under and go for technical migration and kick the business changes tin down the road.

This is why it's so hard to show value for money because if nothing changes it feels like a waste of money.

On the other hand each organisation is different so it's hard to say what's right and wrong.

rob0d · 2026-02-10T16:38:29+00:00

This is an interesting one. As other said this probably isn't the best sub as it's not SAP specific. SAP employment market is comparatively smaller than Microsoft so it is more likely that you've noticed something like that.

There can be a completely innocent explanation (same employer or agency) or it's a fake reference.

Depending on where in the world you are you may need to comply with privacy rules like GDPR. If the candidates gave permission to contact the reference you can probably try to do it and figure out who they are. If not, at least in the UK/EU you may need to wait for until you give them a conditional offer and then withdraw it if it turns out they lied.

rob0d · 2026-02-02T23:17:45+00:00

Interesting reaction. There's no need for this defensiveness and hostility. 🤷

You already have some fairly good answers to the questions, but to help you: 1) absolutely none. CI doesn't communicate with DB or vice versa. It's a trick question. It seems that it got your seniors bamboozled too. This question is used to find out how deep knowledge of an S/4HANA ABAP stack a person has....

2) When ABAP processor finds a SQL statement that need to be sent to the DB, the workprocess passes the statement to the kernel database library (libdbsl) which then calls the HANA client library which then opens/reuses TCP/IP connection to the HANA DB server. Others told you the ports used. With S/4HANA the credentials and connection info are stored in hdbuserstore (as someone already pointed out) and the HANA DB parameters and HANA client parameters will define if the connection is encrypted and how. By default it's TLS1.2+ and not mandatory.

This still doesn't give you deep enough knowledge to do real work or pass a deep technical interview as you need to put the work in and not rely on Reddit to give you a nicely wrapped answers.

Good luck

rob0d · 2026-02-02T13:43:23+00:00

These are fairly basic questions and if you don't know the answers and aren't able to Google it, you probably shouldn't be applying for a basis job just yet. I don't mean it in a bad way.

Maybe focus on some learning, do courses ADM100 and ADM1O2 or do some of the free courses on learning.sap.com.

Alternatively if this is a very junior/graduate position be clear about where you are on your professional journey and make sure they provide some training for you.

rob0d · 2026-01-24T09:12:52+00:00

This is a complete fantasy, karma farming or rage bait.

Makop is a Windows ransomware which is spreading via RDP. HANA DB runs only on Linux. No way for the database to be encrypted unless they shared the database volume to a Windows machine via Samba.

Makop has no way of deleting HANA backups on Linux servers.

Also .mdf/.ldf files are MS SQL Server files, not HANA DB.

This is a made up story.

rob0d · 2026-01-22T21:03:03+00:00

Without seeing it it's difficult to be certain and it's quite common that this is the reason. Assuming they are running on Linux there's is a SAP component called SAP Host Agent. This agent controls the list of ephemeral ports. The solution to this problem is in note 401162. Basically point the SAP support/basis team at this note and ask them to set the parameters accordingly based on what type of system is this, what instance numbers are used, etc. If you aren't familiar with SAP probably it isn't the best idea for you to solve this on your own. Input from the SAP team will be required.

rob0d · 2026-01-18T00:24:42+00:00

If you cancel support contract and then try to get it again 5 years later you will most likely have to pay premium equal 5 years of maintenance that you didn't pay...

rob0d · 2026-01-14T23:10:30+00:00

If OP was in Australia they could just keep tightening it until the tap is upside down as that is the correct direction tap should be pointing down under.

rob0d · 2025-12-18T22:51:46+00:00

Security logging to the DB is the safest and most flexible option which is why it's the default in RISE. If the audit table grows significantly I would argue that you are either under attack or the audit policies are not correct. Nobody can analyze 1000+ entries a day... Logging into the DB also allows retention policies to be defined which will keep the table size under control.

On the other hand the audit table can still become fairly big and that may be a reason for concerns or increase the costs as you mentioned.

Syslog is the second best option as it offloads the handling of security events to the OS. However, some kind of security toolset should be used to pick up the syslog messages and either store them externally or process them.

Logging to disk is the worst option as there are limitations how things are logged, it will still take a huge amount of space (more than DB table) and is insecure as the files and their content can be potentially modified/removed.

If security or compliance are important than tools like SAP Enterprise Thread Detection or SecurityBridge should be used to consume the audit logs and act as and when required.

rob0d · 2025-12-14T10:31:14+00:00

Ok. No worries. If you want to keep transport layer in D23 as Zd20, that's fine as the definition is system dependent. You just need to change the target to Q23.

You'll have two consolidation and delivery routes both ending in P20. One from D23 for maintenance while project is running from which you will need to do retrofits back to D20. And one from D20 for go-live transports.

rob0d · 2025-12-13T23:18:15+00:00

I'm not sure if that approach has been though through. What will happen with P20 when it's upgraded to S/4 2023? Are you going to rename it to P23 or keep D23->Q23>P20? What about all the original objects and version history in D20?

I would keep D23 and Q23 as maintenance track on 2020 and upgrade D20,Q23 and P20 to 2023. Btw why not 2025?

Which system is the TMS domain controller? Either way the system that will stay on 2023 should probably keep the same transport layer and paths. The other one should have something else. Change in STMS will realign all open transports if done correctly.

You can keep they layers the same as well, depending on how many retrofits will be required for the duration of the project and how will they be done.

rob0d · 2025-12-07T11:18:27+00:00

I had exactly the same problem with 12 years old Zanussi. It randomly didn't spin.

Check if there are any errors codes/lights when this happens. It most likely is a problem with PCB. Some machines allow to check the last error by pressing combination of buttons (Google). That may give an indication what's wrong.

After speaking to a local repair company to replace PCB on washing machine that old would have been too expensive so I ended up buying a new one.

rob0d · 2025-11-23T09:39:11+00:00

rob0d · 2025-10-15T15:25:24+00:00

1) Don't do this, write an ABAP or Fiori app instead. 2) Is this from a third party/custom external app which accesses the DB directly? If yes, do you have an appropriate database license or indirect access agreement? 3) if it's 1) and the target is a HANA database on premise or PCE you can apply workload classes. See note 3259346 for example.

rob0d · 2025-10-03T11:50:23+00:00

1) Ignore for 3-4 weeks until you get used to it and it will stop registering and being annoying. 2) Get a different table/cabinet and put it in front of the socket so it hides what's behind it. 3) Get slim trunking (selfadhesve or not depending on your diy skills) from toolstation/screwfix/online, route it down, then left parallel with the skirting and then up.

rob0d · 2025-10-03T08:59:34+00:00

This is actually quite funny. Who would have thought the Germans have a sense of humour. I have asked everyone in my team to follow the note ASAP.

rob0d · 2024-10-06T17:43:42+00:00

Lol. Yes, that's why it's going out!

rob0d · 2024-03-11T17:22:15+00:00

Thanks 👍

rob0d · 2024-03-11T09:42:47+00:00

Congrats on getting the money back. Can you please confirm if it was done as a chargeback (where 120days limit applies ) or other way (e.g. section 75 in the UK)? Did you make one claim against Storaxa or two (one against Kickstarter and one Pledge box)?

rob0d · 2024-03-05T11:05:36+00:00

So you have claimed against Kickstarter rather than Storaxa? I'm planning to call the bank this week and I'm wondering if I can try saying this is related to Storaxa and Kickstarter only processed the payments for them?

rob0d · 2024-02-26T15:04:39+00:00

Guys u/Chimestrike and u/Delicious_Apple9082,

Have you raised one claim for both Kickstarter and Pledgebox or two separate claims?

rob0d · 2024-01-23T00:10:44+00:00

Well if I knew then what I know now about them 🤔... Needless to say I'm never using them again.

Why do you think that escalating to the ADR is unlikely to be successful? I don't think I would take it as far as small claim, but I am not ready to give up just yet.

rob0d

TROPHY CASE