SAP Endorsed App: Why it should matter to Redwood customers

Article

A lot of companies have gotten comfortable with the way their job scheduling has always worked. It ran in the background, executed batch jobs and didn’t cause a lot of noise — so why change it? 

The problem is, “just working” isn’t the same as being ready for what’s coming next, especially if you care about SAP’s evolution and the massive role AI is playing. In a world where digital transformation now means becoming an intelligent enterprise built on real-time data, you can’t afford not to make use of the “best of the best” solutions.

Luckily, SAP gives us an easy way to determine which compatible solutions the company most strongly stands behind: SAP Endorsed App Premium certification.

SAP Endorsed App: More than just a badge

SAP Endorsed Apps aren’t ordinary partner solutions. This invitation-only program highlights solutions that help you with strategic business challenges not directly addressed by core SAP functionality. 

SAP Endorsed App status is the highest level of certification SAP offers, and it isn’t handed out lightly. It signals to customers that the solution has been extensively tested and validated to meet SAP’s highest standards for performance, security and integration.

Being an Endorsed App means a solution has been rigorously evaluated and passed SAP’s most demanding Premium certification standards. Every angle is tested to ensure the solution truly stands up to real-world enterprise demands, even in the most complex hybrid environments. Only solutions that are widely used by SAP customers, future-aligned and proven to deliver outstanding customer value earn this highest level of SAP trust.

SAP Endorsed App for workload automation

Taking advantage of SAP’s next-generation capabilities is particularly important when it comes to workload automation, the backbone of your mission-critical processes. SAP CEO Christian Klein envisions a world in which ERP, automation, data and AI all work together in one cohesive ecosystem. Your processes should run end to end, intelligently orchestrated rather than stitched together. If your automation layer isn’t deeply integrated and future-ready, it becomes an anchor dragging you down. And if your workload automation partner isn’t deeply aligned with SAP, you’re going to hit bottlenecks sooner than you think.

That’s why RunMyJobs by Redwood becoming a Premium certified SAP Endorsed App matters so much. You know your automation will be not just compatible but optimal, now and into the future.

Certified vs. optimal integration

Many job scheduling solutions are certified to connect to SAP systems, even RISE with SAP. And that’s good, but it’s only the first step. Basic certification means a scheduler has been tested to connect and perform standard tasks, but it doesn’t tell you how it integrates, what extra infrastructure you need or whether it supports a clean core without workarounds and fragile custom code.

It’s kind of like giving your teenager a learner’s permit. Sure, they’re legally allowed to drive, but would you hand them the keys and say, “Go ahead, take your friends to the basketball game tonight … and use the freeway”? Probably not. You know that true readiness involves more than basic certification. It’s about trust, experience and minimizing risk — for the driver and everyone else on the road.

RunMyJobs is the experienced, fully licensed driver: the only workload automation solution that is an SAP Endorsed App, Premium certified. Thus, it’s optimized to run in complex SAP landscapes, including RISE with SAP, Business Technology Platform (BTP) and Business Data Cloud (BDC). 

It’s not about whether your automation connects to SAP. It’s whether it truly unlocks SAP’s full value, without compromise.

True future-proofing: Not just a fancy marketing slogan

We all see “future-proof” plastered across marketing materials. But real future-proofing isn’t a tagline. It means what’s being offered is designed to evolve, not just function today.

With SAP Endorsed App status, RunMyJobs is verified to keep pace with SAP’s roadmap. There is a regular cadence for SAP and Redwood Software to collaborate and align product roadmaps. What you get from this: reduced risk, faster time-to-value and confidence that your automation engine won’t become the bottleneck when it’s time to embed AI into your core business processes. So when we talk about RunMyJobs being “future-proof,” we’re not throwing around empty words. 

Don’t run your business on a learner’s permit. You need a solution that’s been trained, tested and trusted to navigate the entire journey confidently, even if the road ahead is uncertain.

Watch the video below to learn more about what RunMyJobs’ SAP Endorsed App status means for your business.

See more about RunMyJobs in the SAP Store.

Manual to magic: Agile automation for closing journal entries, account reconciliations and more

Article

In conversations with finance teams navigating automation, a familiar pattern often emerges. Leaders know their accounting operations need to evolve, but the path forward isn’t always clear. The sheer scope of a transformation can be paralyzing.

You can get out of this state of shock and start making strides when you realize you don’t need to overhaul your entire accounting function overnight.

I recommend a more pragmatic approach: Begin with a narrow focus, apply agile methods and build momentum through small, structured wins. Agile, originally a software development methodology, works exceptionally well in finance when adapted thoughtfully. Applied to accounting, it can give you a structured way to modernize processes without sacrificing efficient daily operations.

When you get it right, the transformation can feel like magic — not because it’s effortless but because of how dramatically it simplifies the work.

Step 1: Define your project and assemble your team

Agile begins with a clear purpose. What part of your accounting cycle is ripe for change? It might be:

• Reducing manual effort in preparing recurring journal entries
• Standardizing reconciliations for high-risk balance sheet accounts
• Improving visibility and control over intercompany eliminations

Once you’ve selected your initial focus, identify a small, cross-functional team. That might include one or two accountants who manage the process today, a member of your IT or automation team and a team lead or controller to serve as the product owner.

Your goal is to scope out a project small enough to deliver real progress in a few weeks, rather than trying to automate everything.

Step 2: Choose your sprint cadence

Agile teams work in time-boxed cycles called sprints. In software, sprints typically last two weeks. This same rough sprint cadence also works well for finance. In my experience, two staggered sprints per month allow you to maintain momentum without interfering with the month-end or quarterly close cycle.

The key is to make the sprint regular and predictable. Every two weeks, your team should:

• Review what was completed
• Set clear, achievable goals for the next sprint
• Prioritize the next set of tasks
• Assign ownership based on capacity

This rhythm helps you maintain forward progress even amid daily demands and the ebbs and flows of a typical fiscal year.

Step 3: Start with process selection and discovery

Your first sprint should focus on understanding the process you want to improve. Let’s say you choose to automate a journal entry for prepaid expenses. This first step isn’t writing scripts. You need to understand how the process works today (pain points included), what systems and data are involved, what artifacts exist and what volume and complexity you’re dealing with. 

Say you’re working on a recurring entry to allocate depreciation. You need to uncover: how the entry is generated today, what triggers it and when in the accounting period, which accounts it impacts, what documentation and validations exist and who reviews or adjusts it before it’s posted to the general ledger. You might also need to gather artifacts like Excel templates, email approval flows or ERP screenshots. These are your starting points for making sure your automation reflects a real workflow rather than an ideal one.

Don’t underestimate the importance of the discovery phase in making sure your automation efforts are grounded in reality.

Step 4: Break down tasks and build your backlog

Once you’ve scoped your process and gathered what you need, it’s time to translate your findings into tasks. Some examples:

• Map the current workflow in a flowchart and make sure you cover any places where the process could fail or have to start over
• Identify fields and logic needed for journal entry automation, so you know the required data and calculations
• Review automation platform capabilities (e.g., templates or connectors)
• Write acceptance criteria for a successful automation — this is how you’ll prove your new automation is working
• Prepare test data or validate entry logic, and be sure to include several examples of the different kinds of data you might see to cover the most probable cases 

Tasks that can’t be finished in this sprint go into your backlog. You can reprioritize that backlog after each sprint based on what you’ve learned or what’s most urgent.

Some tasks may expose gaps in how the process works today, and that’s a good thing. Agile sprints are built for learning, not perfection.

Step 5: Communicate, adjust and demo progress

A key agile principle is transparency. Short, regular check-ins — say, 15 minutes twice a week — keep everyone aligned and aware of blockers. No need for slides or long updates. A quick “What’s done, what’s next and what’s in the way?” is usually enough. 

At the end of the sprint, reconvene for a demo. Even if you didn’t automate the entire process, showing a prototype or workflow map can energize your team and stakeholders. Use what you learn to shape the next sprint.

Where to start? Go for high pain, low complexity

If you’re not sure where to begin, I often recommend focusing on account reconciliations. They’re a consistent source of friction and effort, especially for temporary account balances or frequently adjusted liabilities. But many can be standardized or automated with relatively little effort.

For example, bank reconciliations follow a predictable pattern. Accrual accounts only need simple threshold logic. And intercompany receivables/payables might just require timing alignment.

Journal entries are another good candidate, particularly if they’re recurring and related to depreciation, allocations or amortizations. Their fixed logic and regular intervals make them perfect for early wins.

The record-to-report (R2R) cycle contains many interconnected subprocesses that are ideal for incremental automation. Applying agile to this domain brings visibility and momentum to your transformation efforts while minimizing risk and burnout.

Agile is how finance gets things done

Finance doesn’t often borrow from the world of software development, but it should. The pressure is real today to modernize, optimize and transform while still closing the books on time — no small feat.  Agile gives your accounting team a way to improve processes iteratively, without waiting for perfect conditions or massive budgets. They get a repeatable structure and still have space for experimentation. Once they see how agile can turn a painful process into a streamlined one, you’ll have the buy-in you need to scale your automation strategy across your finance organization.

You won’t need a wand, just the right structure, people and mindset. Those create the real magic.

Bridging R&D and clinical operations with frictionless SAP data pipelines

Article

A cross-functional team of researchers has spent months developing a next-generation machine learning (ML) model designed to predict how a new compound behaves across multiple biological targets. It’s the kind of computational power that can accelerate drug discovery by weeks or months and bring life-saving therapies to market faster.

Despite an optimized IT infrastructure and cloud environment, the simulation doesn’t start because the latest compound batch data hasn’t been validated in SAP. The experiment metadata is still siloed in spreadsheets, and the model can’t ingest incomplete or inconsistent values. In other words, the fluid connection required between systems isn’t there.

As you may well know if you work in this industry, this isn’t a hypothetical delay. Data readiness can’t be treated as a side task, although it too often is. In which case, it doesn’t matter how advanced an AI model you have. With regulatory pressures high, the cost of a subtle misalignment is steep.

Because this applies whether you’re simulating compounds, ensuring patient records are anonymized and audit-ready or forecasting inventory, critical processes break down when data stays disconnected. Leading healthcare and pharmaceutical organizations are attempting to solve this common problem by rethinking how data moves from SAP to ML platforms to analytics and back.

Life science’s parallel pipelines: Innovation and execution

In life sciences organizations like yours, innovation happens on two fronts. On one side, your R&D teams use AI and massive datasets to accelerate discovery. ML models in AWS SageMaker or Schrödinger Suite predict promising compound structures, while simulation platforms test toxicity and efficacy before running a single experiment.

On the other side, your clinical and supply chain teams ensure those discoveries reach patients safely and cost-effectively while following all compliance regulations. They manage everything from patient enrollment to cold chain logistics to regulatory filing, with each process powered by SAP supply chain and life sciences solutions and custom platforms.

These processes live in very different domains, but they share a common dependency: structured, timely, accurate data. And in too many organizations, that data still moves manually or asynchronously between systems.

Where the cracks appear 

When SAP data isn’t orchestrated, critical handoffs break down and molecular data must be manually pulled from SAP R&D Management to feed AI pipelines. Trial operations build forecasts on outdated enrollment data. Lab results live in one system and regulatory documentation in another, with no feedback loop. Business users wait on IT to reconcile siloed datasets and generate reports.

Drug discovery is increasingly computational, but that doesn’t mean the work is fully automated. Whether you’re managing experiments or kits, the pain is the same: unreliable flow, lost time and elevated risk. Without intelligent orchestration, pipelines either fall apart or deliver fragmented, stale information. This directly undermines the performance of AI models and introduces bias or neglects to provide key correlations. Essentially, you end up making decisions with outdated datasets — or worse, hallucinations. Predictive models built to accelerate discovery or optimize trial logistics can quickly fall out of compliance with data lineage and validation requirements.

Meanwhile, if you cling to these fragmented or manually stitched data pipelines, you face another growing disadvantage: You can’t match the speed of your competitors. Those who are investing in intelligent, adaptive data orchestration are moving faster while proving the trustworthiness of their AI-driven insights.

High-fidelity orchestration is the foundation of competitive agility and relevance in your industry.

Research, meet orchestration

Orchestration is what makes AI scale in R&D. Your SAP environment becomes the launchpad for faster, smarter research, enabling you to:

• Continuously extract experimental and batch data from SAP R&D Management and SAP Analytics Cloud 
• Send compound specs to AWS SageMaker or Schrödinger Suite for modeling
• Coordinate modeling jobs and return results to Databricks for consolidation
• Push insight summaries about ranked candiddates back into SAP
• Trigger alerts for research leads of successful outcomes or red flags and send validated results to SAP Datasphere

Clinical delivery, intelligently aligned

On the delivery side, timing is everything. Clinical trial operations depend on up-to-date patient enrollment data, trial protocols and inventory levels across distributed trial sites. If systems aren’t aligned, sites risk running out of supplies or holding expired stock.

With proper orchestration:

• Enrollment data from SAP Intelligent Clinical Supply Management flows into forecasting tools
• ML models in Azure ML or Databricks predict site-specific demand
• Stock levels in SAP Integrated Business Planning (IBP) or S/4HANA Materials Management (MM) are cross-checked automatically
• If risk is flagged, replenishment is triggered and stakeholders are notified
• Trial performance metrics update automatically in SAP Analytics Cloud
• All data is centralized in SAP Business Data Cloud (BDC) for regulatory compliance and real-time insight

A research-to-treatment automation fabric

True transformation comes when discovery and delivery are both orchestrated from end to end. Here’s what a real automation fabric looks like.

Forecasting clinical and manufacturing needs

• Export enrollment or order data from SAP S/4HANA
• Clean and enrich using SAP Datasphere
• Run predictive models via Databricks, Azure ML or SageMaker
• Feed outputs into SAP IBP for dynamic planning

Managing research and validation 

• Extract compound data from SAP R&D Management
• Coordinate modeling jobs in Schrödinger Suite
• Score and validate candidates in Databricks
• Trigger SAP updates and notify research teams automatically

Controlling inventory and site logistics

• Pull inventory positions from S/4HANA
• Reconcile with forecasted site needs from SAP IBP and ML pipelines
• Generate and dispatch replenishment orders
• Publish everything in SAP Analytics Cloud for transparency

Keeping teams informed and aligned

• Push alerts to supply, clinical or research leads based on process outcomes
• Route structured datasets to reporting dashboards and compliance archives
• Automate audit trails, approvals and next-step triggers

With every step validated, timestamped and secure thanks to RunMyJobs by Redwood, your data flows continuously, allowing you to be proactive instead of reactive.

Audit-ready AI depends on orchestrated data

The rise of AI in life sciences is helping to optimize molecule screening and clinical trial site selection and even personalize patient communications. With that power comes increasing scrutiny.

Regulators are watching closely. Health authorities in the United States, European Union and beyond are issuing new guidelines around AI in clinical decision-making, digital therapeutics and research applications. They want to know: Where did the data come from? Was it anonymized? Who validated it? And can you prove it?

If your data pipelines are fragmented, those answers may simply not exist. But orchestration changes that. When you automate your data moving from SAP modules to Azure ML or from SAP Datasphere to regulatory systems, you also create a system of record. Every dataset has a timestamp, and every transformation is traceable. This strategically enables AI innovation.

The next wave of advancement will hinge on more than modeling accuracy; you’ll need to be able to explain how your model was built or prove the integrity of the data behind it. With the right orchestration solution, you don’t have to choose between speed and control. You can stay audit-ready and future-ready.

Develop a resilient nervous system

Think of your systems like organs. Each one serves a distinct purpose, but they communicate via signals that travel through connective tissue. These signals are orchestration in action!

Want to know more about orchestrating SAP data with RunMyJobs? Read more about using the SAP Analytics Cloud connector.

Intelligent data orchestration strategies for the hybrid finance landscape

Article

Across banking, insurance and asset management, financial institutions are realizing data orchestration will define their future competitiveness.

This is apparent in recent headlines. For example, JPMorgan Chase has ambitiously invested in AI, building a team of over 2,000 AI experts and developing proprietary models to improve everything from fraud detection to investment advice. But the story underneath the surface is just as important. 

Bold bets can only be made from a solid foundation. Before any AI, analytics or digital transformation initiative can succeed, the data behind it must be clean, connected and controlled. Leading financial services firms recognize these initiatives can only deliver value when the data feeding them is complete, synchronized and auditable. 

In an environment where transactions span mainframes, SAP systems, cloud platforms and best-of-breed specialty tools, orchestrating data flows rather than just integrating endpoints becomes the competitive differentiator. Instead of adding more tools, you need to build better pipelines. Your filings, financial statements and liquidity metrics are too critical to allow stale, inconsistent and siloed data to inform them. 

The more orchestrated your data movement, the faster and safer your institution can move. Whether you manage $5 billion or $500 billion, orchestration supports financial close acceleration, real-time risk aggregation and ongoing compliance with evolving regulations.

And it’s achievable now.

The stakes are higher in finance

Whereas it would be a mere efficiency problem in some industries, data friction in financial services is a major business risk. When your systems operate in silos or on rigid schedules, you open the door to fines, missed cutoffs, extended close cycles, customer dissatisfaction and other negative outcomes.

Meanwhile, the AI and analytics platforms you’re investing in, from SAP Business Technology Platform (BTP) to Azure, Databricks and beyond, can’t deliver value if the pipelines feeding them are delayed, error-prone or unverifiable. Precision and timing are non-negotiable when you’re dealing with the precious numbers that impact the lives and livelihoods of your valued stakeholders.

From static pipelines to dynamic orchestration

Despite years of modernization efforts, many financial institutions have invested heavily in connecting systems via APIs, ETL pipelines or middleware. These integrations were a necessary step, as they enabled data movement between SAP S/4HANA, legacy mainframes, cloud data warehouses, CRMs and more. But whether data moves isn’t the question; it’s whether it moves correctly, completely and in sync with the events that drive your business.

Without considering this connectivity and complexity, you’ll lack event-driven control, data validation checkpoints, dependency management and real-time recovery, among other key capabilities. An intelligent orchestration layer addresses these gaps, especially if, like most financial operations, yours operates across a hybrid mix:

• SAP S/4HANA or SAP Central Finance
• Legacy mainframes for core banking or policy systems
• Cloud data warehouses and analytics platforms
• CRMs like Salesforce 
• Risk engines, actuarial systems, customer applications and partner ecosystems

It’s important to have a living nervous system connecting it all. A foundation that can monitor, react and adapt automatically across SAP and non-SAP systems will help you meet ballooning expectations brought about by AI, evolving regulations and more industry-specific factors.

True data pipeline enablement requires the ability to:

• Trigger workloads across SAP, cloud and legacy systems based on real events instead of static schedules
• Validate and sequence data automatically — delaying or rerouting jobs until quality gates are cleared
• Coordinate ML model execution tied directly to upstream data pipelines, whether scoring loans, recalculating provisions or updating liquidity forecasts
• Automatically log, track and retry processes to maintain auditability and meet SLA commitments
• Push structured, enriched datasets to SAP Analytics Cloud, Microsoft Power BI and other downstream consumers

Orchestration makes this possible. It doesn’t replace your SAP platforms, APIs, data lakes or CRM systems. It connects and governs the financial data flowing between them, automatically and intelligently. And AI and compliance-readiness depend on this very orchestration.

Building an efficient automation fabric around everyday financial processes

Your organization lives and dies by its ability to respond to change, and it all begins with having every dataset, account and rate positioned correctly from the outset. An automation fabric is the layer that connects and synchronizes your tools, data sources and processes across your IT environment, no matter how complex it is.

Setting your entire organization up for resilience begins with the first transaction of the day. Here’s what orchestrated start-of-day financial operations can look like with a secure, advanced workload automation platform as your control layer.

Ledger updates and overnight postings

• Finalize overnight processes — interest accruals, FX revaluations, journal entries — using SAP Financial Accounting (FI) and SAP Treasury and Risk Management (TRM)
• Validate completion of all wrap-up jobs
• Check dependencies and prevent downstream jobs if failures are detected

Balance reconciliation

• Trigger FF_5 to import bank statements
• Run matching logic and update general ledger balances
• Launch ML cash application processes in SAP Cash Application (Cash App)
• Automatically alert stakeholders about missing files and manage escalation workflows

Opening balances and cash positioning

• Refresh One Exposure hub with new data
• Load memo records and run liquidity forecasts in SAP Cash Management
• Pull FX rates, payment maturities and treasury forecasts from SAP TRM

Data loading for exchange rates and market data

• Import daily FX rates and market indices into SAP tables
• Validate values against prior-day data
• Alert treasury and risk teams of major discrepancies that could impact valuations or cash forecasts

Risk checks and exposure updates

• Run FX valuation jobs
• Generate treasury dashboards in SAP Analytics Cloud (SAC)
• Monitor for trading limit exceptions and notify teams automatically

System readiness and transaction processing enablement

• Execute standing instructions and direct debits in SAP Banking Services
• Generate payment proposals (e.g., F110, APM)
• Route for approvals via SAP Bank Communication Management (BCM) and transmit to banks
• Monitor acknowledgments and update One Exposure with outgoing flows

Every step is timestamped, validated and fully auditable, so you’re ready to operate at full speed from the first minute of the business day. Your firm can create resilient, auditable pipelines, reduce risk, enable AI and advanced analytics and scale cross-system processes without adding complexity or risk.

RunMyJobs ensures readiness across SAP FI, TRM, BCM and external systems while automatically triggering ETL pipelines once jobs complete and feeding analytics platforms like Databricks, SAC, Tableau or Power BI.

Harnessing the orchestrated advantage for hybrid environments

Financial institutions have long recognized the importance of data. However, the sheer volume, velocity and variety of financial data are exploding. Fueled by real-time event streams, the proliferation of APIs and embedded finance, plus an increasing reliance on AI-driven insights, the data landscape is becoming exponentially more complex.

The future demands a fundamentally different approach to managing this ever-growing tide. Intelligent automation and orchestration are essential for building a resilient foundation capable of handling the dynamic and interconnected nature of tomorrow’s financial operations. 

To navigate an expanding hybrid data landscape effectively, you must build a robust orchestration layer that ensures data integrity, auditability and observability across all systems.

Read more about how to get your data out of the modern-day maze.