I 've noticed that uploading file sin folders does not update the modified date and time of the folder. This is solved by just running a occ files:scan --all from the konsole.
But i would like that to happen daily. Do i have an option for that?
I am currently subscribed to the following. I am thinking of moving out from Copilot Pro+ and either upgrade my GPT plan or Claude. Aiming towards upgrading Claude.
Claude Pro
GPT Plus
Copilot Pro+
Google AI Pro
My coding use includes C#, Javascript (Vue), SQL, Python, SAP ABAP mainly.
I need to be able to work with Excel Files in the areas of FinOps , General ERP data analysis (Financials, Production Data, Production Costing e.t.c).
I was thinking of dropping Copilot Pro + and trying OpenCode Go + Upgrading Claude sub.
Wondering also if i could stop Gemini as the only thing i am using there is NotebookLM but i am starting to feel that it is getting left behind.
Appreciate any views that you guys can drop...
From the original Linkedin post:
---
Every SAP project has a middleware conversation. It usually happens around week three. Somebody draws a box labelled PI/PO, somebody else asks how much it costs, and the room goes quiet.
That conversation just got a lot more interesting.
THE MIDDLEWARE PROBLEM
PI/PO - SAP Process Integration and Process Orchestration - has been the connective tissue in SAP landscapes for a long time. It sits between SAP core and everything else, translating, routing, and managing message flows. For non-SAP readers: it's expensive, it requires specialist skills to build and maintain, and when it breaks, it takes everything around it down with it.
Teams have lived with it because there wasn't a credible alternative inside the SAP ecosystem.
That's changing.
WHAT ACTUALLY HAPPENED AT SAPPHIRE
At SAP Sapphire 2026, SAP announced a strategic investment in n8n - the open-source workflow automation platform. The investment doubled n8n's valuation to $5.2 billion.
More importantly, n8n is being embedded natively into Joule Studio, SAP's agent-building environment within the SAP Business AI Platform. This isn't a third-party integration. It's a multi-year commercial partnership with deep product alignment.
Both companies are German. That's not coincidence — it's a signal about how SAP thinks about long-term partnerships.
WHAT SAP ACTUALLY BOUGHT
Here's the part people are underplaying.
SAP didn't buy a tool. SAP bought a community.
n8n has 1.7 million monthly active builders. Over 1,000 integrations. A thriving ecosystem of workflows, templates, and integrations built by people who were never going to be SAP customers.
SAP has always struggled to grow a broad builder community. Its developer ecosystem is deep but narrow - mostly SAP specialists. n8n brings in a completely different profile: technical generalists, citizen developers, and integration engineers who live in the modern automation layer.
SAP didn't have to grow that community from scratch. They acquired it.
That's the real move.
I've been building automations with n8n outside SAP for a while - connecting tools, automating workflows, saving hours across projects that have nothing to do with ERP. The community is doing genuinely impressive things. What I'm most excited about is what becomes possible once official SAP nodes ship. The same builder energy, now pointed directly at SAP data and processes.
WHAT JOULE STUDIO + N8N LOOKS LIKE IN PRACTICE
For practitioners on the ground, here's what this starts to look like.
Joule Studio gives you a visual canvas for building SAP AI agents. Add n8n into that environment and you've got visual workflow orchestration alongside those agents. No code required for many scenarios. No PI/PO middleware for integrations that previously would have needed it.
SAP-specific nodes are in development for SAP software systems, expected to reach general availability in Q3 2026. These will let practitioners build integration logic directly in the visual canvas, connecting SAP systems to external services without the traditional integration stack.
Critically, the workflows run within SAP's managed cloud environment. This isn't shadow IT. It isn't a workaround someone's spinning up on their laptop. It's governed automation, inside SAP's compliance and audit framework.
When these nodes ship, PI/PO stops being the default answer for a lot of common integration scenarios. That's a significant shift in how SAP implementations get designed.
THE MCP ANGLE
Here's where I want to share how I'm currently thinking about this - and I'll be clear this is my read, not SAP's positioning.
n8n inside Joule Studio has the potential to function as a visual MCP (Model Context Protocol) orchestration layer.
For context: MCP is the emerging standard for connecting AI models to tools, data sources, and external services. It's the protocol layer that lets agents do useful work rather than just generate text.
What I'm seeing is that Joule Studio, with n8n as its workflow engine, could let practitioners chain SAP AI Core, external LLMs, and MCP servers together inside a visual canvas - all running within SAP's governed cloud environment.
That's not a small thing. Right now, building MCP pipelines requires either developer skills or bespoke tooling. A visual, governed MCP orchestration environment inside SAP's ecosystem would bring that capability to a much broader audience.
SAP hasn't framed it this way explicitly - but I've been building toward it from a different direction. Using Claude Code with an n8n MCP server, I've been orchestrating workflow builds through conversation: describe the logic, Claude Code wires up the nodes. Same concept, different entry point. What Joule Studio does is bring that pattern into a governed enterprise environment - which is the version practitioners actually need.
WHAT THIS MEANS FOR CITIZEN DEVELOPERS AND ANALYSTS
Data analysts and operational teams have always had a complicated relationship with SAP data. They need it. Getting it usually requires either a specialist, a ticketing queue, or a data extract that's already three days old by the time it arrives.
The access story is starting to change.
If Joule Studio + n8n delivers on its direction, analysts with moderate technical comfort - people who can work in Power Automate or similar tools today - will have a path to build SAP-connected workflows without going through IT for every integration request.
That's not a threat to IT. It's a release valve. It moves the low-complexity work off the specialist queue and lets the specialists focus on the integrations that actually need them.
HONEST LIMITS
This is early. Worth saying clearly.
The SAP-specific nodes for n8n are still in development. They're on the roadmap, not in the product today. Joule Studio itself is still maturing - it's a compelling environment but it's not finished.
Enterprise governance remains SAP's responsibility to get right, and that takes time. The promise of governed citizen automation is real, but the guardrails need to be solid before most enterprise teams will trust it at scale.
Practitioners should be watching this closely, not waiting passively - but also not redesigning their integration architecture based on a Sapphire announcement.
The signal is strong. The product needs time to catch up.
CLOSE
I've been in enough middleware conversations to know how durable the PI/PO default is. It persists not because it's always the best option, but because it's the known one. Everyone at the table understands the risks, the costs, and the trade-offs.
What SAP is building with Joule Studio and n8n is a credible challenger to that default - not for every scenario, but for enough of them that the conversation in week three should start changing.
I'm genuinely curious how other practitioners are thinking about this. Whether you're designing integrations, advising on architecture, or sitting in those week-three rooms - I'd love to hear where your thinking is landing.
---
