Gejo John

💡 Why We Stopped Relying on Manual Controls — and Built Our Own in SAP Business One Every ERP system comes with controls. But not every business runs the same way. We realized early that standard SAP Business One settings alone were not enough to support a multi-branch, multi-division operating model. So instead of adding more manual checks and approvals, we designed our own SBO Controller logic — directly inside SAP. What we automated and enforced: ✅ Division-based document visibility within the same branch ✅ User-specific series control across Sales, Purchase & Finance ✅ Mandatory division, cost center & project validation ✅ Automatic series selection based on branch + division ✅ Real-time transaction blocking using SBO_SP_TransactionNotification ✅ Governance without slowing down operations The result? A controlled system where: • Users see only what they are authorized to see • Documents follow business structure by design • Errors are stopped before posting — not corrected later • Finance, operations, and IT work from the same rules ERP governance isn’t about adding more approvals. It’s about designing the system so the right action is the only possible action. 📌 Control should live inside the ERP — not in spreadsheets, emails, or after-the-fact reviews. #SAPBusinessOne #ERP #SBO #Governance #InternalControls #DigitalTransformation #Leadership

1

Sapphire 2025: Some Musings This year’s Sapphire was a more enriching and yet a little bit more tantalizing experience. Enriching because we at Mars could share minds with a lot of peers and also a vast portion of SAP vendor ecosystem. What we could learn was very much in line with our current model, methodology and set up. We in fact found ourselves at the frontier of a number of SAP integrated toolchain components especially for the size and complexity of our organization. SAP is looking to weave a future-ready (I won’t dare challenge the future by saying future proof 😜) tool chain to help their customers navigate the developing journey of intelligent enterprise transformations. Critical dev-ops tools such as Signavio, LeanIX, Cloud ALM, WalkMe along with a strong foundation of Business Technology Platform (BTP) have already proven to be a set of steps in the right direction. We have been fortunate to have access to wall-to-wall tools from SAP augmented by other vendor tools to create a clear framework for our transformation. These help bring focus on integration, automation while paving the foundation for adopting SAP Joule AI and its army of agents. More on Joule and AI later. We see a clear focus from SAP to bring together the TRUE Enterprise Architecture principles: Process (Signavio), Data (BDC and DataSphere), applications and technology (LeanIX, BTP) orchestrated by Cloud ALM. One of the biggest focus areas for SAP has been Clean Core commitment. While this is a long (and arduous) journey, we do see SAP working hard to enhance the scope of technical objects, tools, methods of development and capabilities of its applications. Effectively a Transformation mindset is by definition a Clean Core mindset. We also see a significant effort from the edge applications vendors to align with the Clean Core principles, practices and applications. Now for the tantalizing part. Surely a better coordination and collaboration between SAP and these edge vendors is needed but we see both the partners moving in the right direction. It’s just a matter of pace at which they can deliver. As many of our Keynote speakers said during Sapphire, there’s no time better time than now- so SAP, our edge systems partners and integration services provides, here’s a call for all of us to synergize our efforts to build a sustainable, clean core and future-ready SAP ecosystem!! Cheers!!

41

5 Comments

In this week's BTP Bytes, Abhilash Gampa details Cloud Transport Management. #Sapcommunity #SAPBTP #SAPFiori #SAPDevOps #SAPs4HANA #SAPapphausnetwork #sapai #sapgoldpartner #sapapphauspartner #mindsetconsultingllc

9

🚀First AI driven and practical, case study based certification - focused on one of the most central topic in the SAP solutions ecosystem - SAP Business Technology Platform (BTP). BTP has evolved into a holistic, end-to-end platform that connects processes, data and applications, with over 80+ services covering broad spectrum across Application development, Integration, Data & analytics, Automation and AI. It is clear that BTP continues to play a central role in the AI-driven world, serving as a platform that orchestrates and innovates business processes and solutions. I'm summarizing a few critical considerations, in my view, for customers implementing BTP: ✅ 𝗕𝗮𝘀𝗶𝗰𝘀 𝗳𝗶𝗿𝘀𝘁 - The way you structure your global account, directories and subaccounts has a considerable impact on managing entitlements, monitoring performance and usage tracking. Spend sometime thinking about the most suitable model for your scenario. ✅𝗨𝘀𝗲 𝗰𝗮𝘀𝗲 𝗱𝗿𝗶𝘃𝗲𝗻 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵 - Identify use cases that delivers a high business value. This may sound obvious, but before diving into BTP services, it is critical to invest enough time in clearly defining the problem you are trying to solve. ✅𝗟𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗦𝗔𝗣 𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀 - You will find a wealth of resources on BTP, such as the BTP guidance framework, SAP Discovery center, Business Accelerator Hub, SAP Architecture center, Trust center, and methodologies such as Integration solution advisory and the application extension methodology. These resources accelerate development while ensuring solutions are SAP best-practice-aligned and clean-core compliant. ✅𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗶𝗻𝗻𝗼𝘃𝗮𝘁𝗶𝗼𝗻 - BTP's extensive portfolio of services and tools caters to almost any scenario. It is important not to treat this as a one-time activity. Instead, create a roadmap, revisit regularly and continuously innovate to benefit from platform's capabilities. Strong governance is especially important in federated, global environments. I strongly recommend this course to anyone looking to understand the BTP platform in depth, whether you are an SAP customer or partner. I’m sure the AI-driven exam will surprise you! #SAPBTP #SAP #SAPBusiessAI https://lnkd.in/ejnRgX85

63

6 Comments

Is SAP’s Joule AI the Next Defining Moment for ERP? 🌟 We’ve seen this playbook before. The shift from SAP ECC to S/4HANA wasn’t just a technical upgrade - it was a strategic move. By introducing its own database, SAP reduced dependency on third-party technology and fundamentally reshaped the ERP landscape. Fast forward to today. Is Joule - SAP’s own AI copilot - a similar inflection point? SAP is now embedding Business AI and Joule across a broad range of its cloud applications, enabling natural-language interactions, intelligent automation, and context-aware insights directly within core business processes. What’s notable is that AI is no longer positioned as a future capability - it’s already influencing how customers evaluate and adopt SAP solutions. Recent earnings discussions and industry analysis indicate that a growing share of SAP’s cloud engagements now involve AI-driven use cases, with clear momentum around Joule and Business AI as value differentiators rather than experiments. This evolution closely mirrors SAP’s earlier transformation strategy: ➡️ Own the critical layer ➡️ Embed innovation directly into the platform ➡️ Strengthen long-term differentiation in enterprise software 💭 Questions for the community: ● Can Joule meaningfully change how users interact with SAP systems on a daily basis? ● Will SAP’s “AI built-in” approach outperform best-of-breed AI integrations over time? ● Is this the next step that helps SAP sustain its leadership in ERP? (I’ve linked the full Q4 earnings breakdown in the first comment for those who want the data! 📊) 👇 I’d love to hear your thoughts - optimistic, skeptical, or somewhere in between 👇 #SAP #Joule #BusinessAI #ERP #DigitalTransformation #EnterpriseAI #FutureOfWork

5

1 Comment

Accelerating SLT Initial Loads: Achieving 5X Faster Performance for Large SAP Tables In SAP Finance, managing large tables like ACDOCA, BSEG, BKPF, and BSEG_ADD can be challenging, especially during initial load and replication. These tables, often containing hundreds of millions of records, can become bottlenecks with default SLT settings, leading to extended load times. However, by optimizing LTRS → Performance Options, organizations can achieve up to 5X faster performance, transforming data management capabilities. Enhancing Initial Load Jobs: Default SLT settings limit the number of jobs per table, which is inadequate for large tables. Increasing the Number of Jobs in LTRS to 15–16 per large table allows multiple parallel processes to efficiently handle data chunks, significantly reducing runtime and balancing workload distribution. Optimizing Records per Access Plan: The Number of Records parameter in LTRS determines the row count each access plan manages. For tables like ACDOCA, dividing them into portions of about 1 million records each facilitates efficient distribution across multiple jobs. This approach enables SLT to generate numerous parallel access plans, maximizing resource use and ensuring swift data processing. Utilizing Parallel Data Transfer Jobs: Beyond table-level parallelism, SLT uses Data Transfer Jobs to move data from the sender queue to the target HANA system. Increasing Total Data Transfer Jobs in the LTRC Administration tab to a higher value (e.g., 60 jobs) ensures effective use of parallelism, preventing idle jobs and enhancing system performance. Reserving Jobs for Initial Load: Large initial loads can strain shared SLT resources. By reserving jobs for Initial Load (e.g., 20 jobs), large tables like ACDOCA or BSEG are prevented from monopolizing resources, allowing smaller tasks to proceed smoothly and maintaining system stability. Allocating Jobs for Calculation Phase: The Jobs for Calculation parameter determines the number of parallel jobs for access plan creation. Setting this to around 20 jobs expedites planning, allowing data transfer to start sooner and minimizing downtime. Business Impact: These adjustments can reduce load times from several hours to just a few, with replication throughput improving by over 400%. Tasks that once took nearly half a day can now be completed in under two hours, enhancing efficiency and productivity. Conclusion: While these modifications require careful planning due to increased CPU and memory usage, they can significantly expedite S/4HANA transformations. Fine-tuning LTRS → Performance Options can yield nearly 5X faster SLT replication for large tables, impacting migration timelines and project success. Bonus Tips: All of the above performance options changes can be implemented online, becoming effective from the next batch work process assignment of the same load transfer jobs. #RISE#EmbeddedSLT#PerformanceOptimization#SAP Learner Community #SAP Community

17

3 Comments

RAP (RESTful ABAP Programming Model) is the modern approach to build SAP Fiori apps and Web APIs in ABAP. It provides a structured way to create business objects (BOs) using: LCDS Views for data modelling 1. Behaviour Definitions for business logic/actions ↳ Service Definitions/Bindings for exposing the app to UI or API It is tightly integrated with SAP BTP and Fiori UX paradigms. 2. What are SAP Adobe Forms? Adobe Forms (aka Interactive Forms by Adobe) are powerful tools for generating printable documents (like invoices, certificates, payslips) from SAP. They support: -> 4PDF output (print or digital) -> Formatted layouts using Adobe LiveCycle Designer -> Interactive fields, barcodes, signatures, etc. 3. Why Use Adobe Forms with RAP? While RAP is mostly about modern Uls and APIs, many business cases still require printable outputs - like: HR module-->Employee Certificate Payslip Sales ---->Invoice/ Quotation PDF Education App->Student Report / Certificate Procurement->Purchase Order Document So, even in RAP-based apps, you often need PDF generation as part of user actions. 4. How Do They Integrate? "RAP handles the business logic and UI, while Adobe Forms handles the document generation." The integration happens through an action (like a button in UI) that calls Adobe Form in the background. Here's the flow of events conceptually: 1. User triggers an action in the RAP-based UI (like Generate Invoice). 2. RAP behaviour implementation (server-side logic) is triggered. 3. In the implementation: SAP internally starts an Adobe form print job It calls a function module tied to the form Data is passed to the form LA PDF is generated (returned as binary) 4. The PDF can then be: Displayed to the user (download or open in browser) Sent via email

165

3 Comments

When comparing MDG deployments to SAP offerings, understanding their interconnection is crucial. Here's a simplified breakdown correlating SAP MDG deployment choices with SAP's primary offerings: - The Co-Deployed/Hub option is recommended for comprehensive CR & validation flows. - Opt for the Cloud Edition on BTP if you need BP-only SaaS governance. - Choose Federated MDI to efficiently synchronize data across SAP and non-SAP systems without central governance. #SAPMDG #RISEwithSAP #GROWwithSAP #SAPBTP #MasterDataGovernance #OneDomainModel #MDI #SAPArchitecture #sapbytesbydivya

43