Ryan Fleischmann

Writing new integrations in ABAP *on stack* in 2025 is a lot like inviting people over to your house

Should you do it? Can you do it? Sure. Absolutely even.

But if you let too much come and go - you could have a real mess

a close up of a person 's face with flames coming out of it 's mouth . ALT: a close up of a person 's face with flames coming out of it 's mouth .

When you decide to retire that MCP server that you gave SAP_ALL

I don’t think thats lost on the US at all

The big question is whether it gets work through in a genuinely friendly and effective way

Would not be shocked if Trump admin attempts to tariff US companies use of offshore labor next

Lots of anguish about H1-B n the US

Big shakeups are undoubtedly coming to US - based SAP projects because of it

It is very common for 80-90 percent of SAP roles on US projects to be a past or present immigrants from India

Even common in US govt and defense roles where US Citizenship is reqd

Reply here or send dms if interested

It lead me to genuinely feeling what comedian Mitch Hedburg felt when he said

“man I’m tired of chasing my dreams man… I just wanna ask where they’re going and hook up with them later”

Sometime I may do a retrospective.

A set of technical and life lessons learned of SAP tech professional who strayed into the web3 domain for a season of life

And still has a postitive outlook on cryptos future in our world and the enterprise - despite also living through some of the worst of it

Big difference from my last effort to this one

This is entirely CAP based. Vs what I was earlier doing with ABAP. Node.js is naturally a way better purpose built for this kind of thing than ABAP ever will be

Since earlier this year I’ve been tinkering again with blockchain/digital asset integrations with SAP

Initial results of the MVP/Poc I have are looking good.

Even if you typically write off the web3 domain you should find it interesting - particularly if you like cryptography

You will see soon!

a picture of donkey kong with the words alright bro that 's it ALT: a picture of donkey kong with the words alright bro that 's it

Who wins in 2025

100 offshore developers

Vs

1 expert developer vibe coding in AI gorilla bananza mode

What’s an underrated non-technical green flag in SAP Basis admins?

I’ll start:
An obsession with Rube Goldberg machines

It was okay project - though stifling in ways

I moved into freelancing later in my career though

It was strangely difficult to convince this EA the standard oData services even existed

I remember after activating API_SalesOrder and API_BusinessPartner we spent a few months arguing whether or not we were even licensed to use these on S/4 HANA private cloud

EA was extremely cautious with respect to direct access to the S/4 system. Security. Performance.

+ pretty large number of PO devs/leads were placed on the project who all held a similar view that SAP PO was the best way to build REST services on S/4 HANA

Sometimes I wake up in the middle of the night from this nightmare from my past

It’s 2019 and the SAP S4 project I am on requires *every* REST API be created with SAP PI/PO

The EA banned oData services from consideration. Even the standard ones 😖😣

a man with a name tag that says kevin is standing next to a woman ALT: a man with a name tag that says kevin is standing next to a woman

All the SAP EAs who don’t know how a github PR works are positively fuming rn

Every time I have to do a formal agile training - it kinda feels I’m getting put into cult

The spirit of Miiverse will live on in Splatoon 4 I think

What if the frogs caught their fishing bait with their tongues? 🐸🪰

Randomly got some http 400 JSON serialization errors in a SAP CAP project this week

Double checked the payload and http handlers. No obvious flaws or issues

Updated all the node modules. Problem solved.

Not entirely sure why it worked - but I guess thats kudos to keeping apps up to date!

Here’s little issue I found with CAP and BTP destinations

If your destination has the property ‘HTML5.forwardAuthToken’ set to true - you are very likely to have issues using CAP’s native ‘cds.connect.to’

More cases than not - leave it off. Unless a specific oauth flow is mandatory

Hard to iterate on perfection

Foreboding in some ways,
but inviting in others ways!

Like I’m listening to the scheming of a little cartoon devil on my shoulder 👹

Hey

anybody here ever sent an RFC message to a kubernetes app on SAP BTP?

In my such case

The separate global account for prod us for public-facing B2B SaaS products

And non prod for dev/qa/pre prod

Was already the chosen setup as I got there

Prod and non prod are 2 different global accounts

Within non-prod - certain hyperscalers are designated as dev/qa/pre-prod. This means separate subaccts for dev/qa/pre-prod

Cf spaces are app-specific

Use CTMS to deploy into prod and pre-prod. Simplifies the role of a business approver.

Use gh actions to deploy to dev and qa - generating CTMS transport on successful qa test.

The problem I have with a lot of online “criticism”

Across all subject matter

I think more people actually *ENJOY* complaining about things than they care to admit

Raging against something is actually easier to do - and easier to get attention for - than practicing genuine appreciation or satisfaction for something

Different people will neglect it for their own reasons imo

CAP experts likely already understand how to do this with extra vendor tools. If you know the business function well - just tell GPT or Build Code what you need

ABAP maxis would likely get bored with it and question why bother with it