Abesh Bhattacharjee

Payload logging and alerting at API Policy level within SAP API Management has been challenge. Checkout #Incture's #APIPolicyPulse. Why #APIPolicyPulse? 1. Solving the "Policy Blind Spot" - When a policy fails (like a Spike Arrest, JSON Threat Protection, or JavaScript policy), the default error flow often loses the original context of the request. By capturing payload details at the policy level, we move from "knowing there was an error" to "knowing exactly what data caused it." This significantly reduces Mean Time to Repair. 2. Eliminating Third-Party Dependency Standard SAP documentation often suggests sending logs to external services like Splunk, Loggly etc using the Message Logging policy. Many enterprise customers have strict data residency or budget constraints that make third-party loggers a hurdle. Keeping everything within the SAP Integration Suite (APIM + Cloud Integration) is the key. 3. Integrated Traceability and Alerting Mechanism On failure of API Policy, alert will be sent over a mail to the relevant teams. Additionally, the request payload will be logged in SAP Cloud Integration along with custom headers to enhance monitoring and traceability, allowing developers to use the Message Monitoring dashboard of #SAPIntegrationSuite to search for failed APIM transactions. Linking the "Application Name", "Endpoint", "Failed Policy Name" etc across both layers provides the "single pane of glass" visibility that many teams struggle to build manually. Kudos to Sumandeep Kaur and Vishal Singh Manhas for putting this together. Connect with us to know more. Sumandeep Kaur Vishal Singh Manhas Vinduja N Seema Rani, PMP Nitin Choudhary, PMP Gayatri Lakkundi Srikanth C S Jaspreet Kaur #Incture #SAPCommunity #EnterpriseIntegration #TechInnovation #JoyofSolvingProblems #APIM #Teamwork

83

1 Comment

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

🚀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

🚨 Security Alert for SAP GUI Users 🚨 If your organization uses SAP GUI for Windows or Java, there is a critical security issue you need to be aware of and fix as soon as possible. 🔍 What’s the issue? Researchers have discovered that both SAP GUI for Windows and SAP GUI for Java store user input history (such as usernames, national IDs, and account numbers) in an insecure way: • SAP GUI for Windows uses weak XOR encryption with a static key • SAP GUI for Java stores the data without any encryption at all Although passwords are not affected, attackers who gain access to a user's system could easily extract sensitive information. This can be used for social engineering, phishing, or unauthorized access. 🛠️ What should you do? 1. Apply SAP-recommended updates For Windows: Upgrade to SAP GUI 8.00 Patch Level 9 or higher For Java: Upgrade to SAP GUI 7.80 Patch Level 9 or 8.10 2. Disable the input history feature to stop further data collection 3. Delete previously stored input history to remove existing risks 📌 Even after applying the patches, researchers warn that fallback encryption could still leave data exposed. Disabling the input history and clearing any saved data is strongly recommended. Please share this with your SAP Basis and InfoSec teams so they can act immediately. For step-by-step guidance and technical details, refer to the sources in the first comment. #SAP #SAPGUI #CyberSecurity #SAPSecurity #PatchManagement #InfoSec

42

2 Comments

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

Automation in SAP: IDoc, API, OData, REST, and JSON Executive Summary Modern enterprises demand seamless system integration to achieve automation and efficiency. SAP provides multiple integration options: IDoc, API, OData, REST, and JSON. This paper highlights their roles, differences, and best-fit applications in business processes like Procure-to-Pay (P2P) and Order-to-Cash (O2C). Key Technologies IDoc: Standard SAP format for asynchronous, bulk data exchange. Reliable but rigid and slow for real-time. JSON: Lightweight, human-readable format for APIs. Flexible, ideal for cloud/web. API: Rules for real-time system interaction. Fast but requires governance. REST: API style using HTTP (GET, POST, PUT, DELETE). Simple, scalable. OData: SAP’s REST-based protocol with query and metadata, powering Fiori apps. Applications in Business Processes Procure-to-Pay PO Distribution: IDoc (ORDERS05) to supplier. Confirmation: JSON payload via REST API updates SAP. Goods Receipt: Fiori app via OData. Payment: Bank API validates in real time; confirmation may return via IDoc. Order-to-Cash Order Capture: JSON API from e-commerce. Shipment: IDoc (DESADV) to logistics partner. Invoice: IDoc (INVOIC02). Payment: Real-time bank API + reconciliation IDoc. Comparative Overview Tech Best Use Strength Limit IDoc Bulk/EDI Reliable Rigid, async JSON Cloud/web Flexible Needs middleware API Real-time Fast Complex to manage REST Web/mobile Lightweight Stateless OData Fiori/UI Query-enabled SAP-centric Conclusion IDocs remain essential for SAP ↔ SAP and bulk processes, while APIs, REST, OData, and JSON power real-time and cloud integrations. A hybrid approach enables automation, error reduction, and agility—balancing stability with innovation

2

#productionhead #SAPPP #productionplanning #factoryhead #SAPAI #SAP #PronixInc AI is rapidly reshaping SAP Production Planning (PP) by enabling predictive, autonomous, and data-driven decision-making across manufacturing operations. Here are the key AI applications integrated or emerging within SAP PP and related components (like IBP, MII, and BTP): 1. Predictive Demand and Production Planning AI models analyse historical production data, sales trends, and market variables to forecast demand with greater accuracy. Example: SAP Integrated Business Planning (IBP) uses machine learning to predict demand fluctuations and automatically adjust production schedules, minimizing overproduction or stockouts. 2. Automated Production Scheduling and Sequencing AI optimizes the production sequence by evaluating factors like machine capacity, changeover time, and workforce availability. Example: SAP’s AI-powered scheduling assistant can reschedule jobs automatically when disruptions occur, maintaining throughput without manual intervention. 3. Predictive Maintenance & Equipment Reliability Through integration with SAP Digital Manufacturing or SAP Predictive Asset Insights, AI analyses sensor data (IoT) from machines to predict breakdowns before they occur. Impact: Reduces unplanned downtime and improves Overall Equipment Effectiveness (OEE). 4. Quality Inspection and Defect Prediction AI-driven vision systems integrated with SAP PP detect defects early in the production line. Use Case: AI models flag quality deviations using image recognition or sensor data, allowing proactive corrective action within SAP QM (Quality Management). 5. Intelligent Material Requirements Planning (MRP) AI enhances MRP by continuously learning from production patterns, lead times, and supplier reliability. Use Case: AI agents in SAP S/4HANA can dynamically recommend reorder quantities or alternate suppliers based on real-time constraints like raw material shortages. 6. Energy and Resource Optimization AI analyses production energy consumption to identify patterns and recommend efficiency improvements. Example: Integration with SAP Environment, Health, and Safety (EHS) enables AI to recommend energy-efficient scheduling or machine utilization strategies. 7. Intelligent Exception Handling Using SAP Joule or conversational AI agents, planners receive real-time insights on delays, material shortages, or capacity bottlenecks — with recommended corrective actions. 8. Generative AI for Planning Insights GenAI tools like SAP Joule assist planners by summarizing complex data, generating alternative production scenarios, and drafting communication with suppliers or internal teams. 9. Supplier and Logistics Synchronization AI synchronizes production schedules with supplier availability and logistics data for end-to-end visibility and faster response to disruptions.

13