Ashish Sampat

I am currently in one of the worlds largest ECC to S/4HANA Migration. This question was asked by one of the Business Stakeholders: what is pilot notes, modified notes, cloned notes, any idea...? Thought of sharing this answer: In order to explain this we need to start with SAP Notes: 1. SAP NOTES: is a bug fix for a problem that SAP has identified. It has to be applied on the SAP ECC or S/4 environment, then tested if the fix has worked. Each time a customer detects a bug, we open an OSS message. If many customers face the same bug SAP then releases a SAP note to be applied in the system that should fix that problem. when the next customer approaches SP then simply ask them to check the specific SAP Note and see it that resolves their problem. One can search for SAP notes on service.sap.com 2. PILOT Notes: Are custom notes developed for large customers for very unique fixes. These are paid bug fixes and do not appear in the SAP Notes repositories as they are custom for a particular customer. Think of them as custom fixes. If we had a pilot note developed in ECC we can request that it be upgraded for our target S/4 3. MODIFIED Notes: Are notes that have been enhanced, modified for the customer. Think of them as Notes+. Something like an append to a BW extractor, or an ABAP program. We can take a standard SAP Note and modify it to our specific, and our unique needs 4. CLONED Objects: is a customer specific version of a standard SAP object that has been copied and modified to meet customer specific business needs. A clone is a SAP Standard object, copied and modified by a customer to meet their needs. By copying, and changing the original object remains the same. A cloned object can be an ABAP Object (CLAS), Function Module (FUNC), a program or a Report Source Code 5. CORE CODE Modification: SAP has areas where customers can modify and other areas that belong to a SAP base core code area. There are special rules on how to alter / modify objects in the Core Code area. In a SAP Migration, and upgrade SAP will not check core code areas and simply override any changes there. Technically it is recommended not to change core code. For example: in French <> English translation the word for a 'plate' is called an 'assiette' in French. Depending on context this could be the food on the plate and/or the English word dinner plate itself. This is part of core code in the French core code page. We had a US Steel rolling manufacturer in Chicago, that had plants in Canada. Instead of using the allowed page for custom translation they went and changed the core code object to translate to 'acier' or a steel sheet. In our 'Mock run -01' when we moved them from SAP ECC 4.7 to S/4 HANA all their translation sheets were overwritten. These had all to be manually reconfigured in the translation allowed space in SAP, prior to migration. This Basic Translation work was 1 of 3,200 translation changes the customer had made all of which had to be manually corrected.

329

21 Comments

"Clean core" has become a big SAP talking point in the U.S. One side of the argument is that customisation overload can over-engineer a process where sometimes simplicity scales. Keeping your core clean and extending via SAP BTP makes upgrades faster, integrations smoother, and innovation easier. SAP professionals who understand the balance between standardisation and flexibility will be the ones in demand for years to come. Less clutter, more clarity.

60

32 Comments

Many SAP EWM consultants secure roles but lack exposure to full-cycle, real-time implementations, often working only in limited functional areas. Drawing from real project experience and multiple live implementations, we have designed a comprehensive 60-hour program covering end-to-end EWM configuration across all major processes. If you’re seeking complete implementation exposure to accelerate your EWM career, this program is built for you.

12

Unpopular opinion: Your SAP BW migration budget is already wasted. If your plan is to: ❌ Lift and shift existing structures ❌ Recreate current processes 1:1 ❌ "Fix quality issues later" ❌ Focus on data movement over business logic …you're planning to fail. Organizations winning their migrations focus on one thing: Turning business logic into data products. Not just moving data. Transforming intelligence. See the playbook that works → https://lnkd.in/dnekfQBP

11

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

Here are some practical top tips for SAP managers looking to hire a strong SAP Test Lead: 1. Clarify the Testing Scope Early Define whether the role is focused on manual, automation, performance, or integration testing. For SAP, specify modules (e.g., FI/CO, SD, MM, HCM) and environments (ECC, S/4HANA, SuccessFactors). 2. Look Beyond “SAP Knowledge” A good SAP Test Lead doesn’t just know SAP screens—they understand business processes, integration points, and risks. Prioritize candidates who can translate business requirements into robust test strategies. 3. Demand Strong Stakeholder Management Test Leads often act as the bridge between functional consultants, business users, and offshore teams. Look for evidence of influencing skills, clear reporting, and escalation management. 4. Validate Test Tools Experience Common SAP test tools: SAP Solution Manager, Tricentis Tosca, HP ALM, Worksoft Certify. Ask how they’ve embedded tools into delivery, not just if they’ve “used” them. 5. Assess Leadership Over Hands-On Skills The best Test Leads don’t just execute—they design, plan, manage defect triage, and mentor testers. Check for examples of setting up governance and driving testing phases (unit, SIT, UAT, regression, cutover). 6. Check Track Record in Large-Scale SAP Programmes Experience in multi-wave, multi-country rollouts is gold—complexity teaches resilience. Probe how they managed test cycles under time and budget pressures. 7. Prioritize Risk-Based Thinking SAP testing can’t cover everything. A strong Test Lead knows how to focus on critical processes, data conversions, and integrations. Ask: “How do you decide where to focus testing when time is limited?” 8. Cultural Fit with Delivery Model If you use agile, waterfall, or hybrid, ensure the candidate has operated in that model. For offshore/onshore, check if they have led distributed teams. 9. Use Scenario-Based Interviews Give a real testing challenge (e.g., cutover weekend with failed test scripts) and see how they’d handle it. This reveals calmness under pressure and structured problem-solving. 10. Don’t Overlook Soft Skills Communication, resilience, and pragmatism are often what separate an average Test Lead from a great one. 🏆 Phone OJB Resourcing - +44 7852909535 to discuss the right SAP Test Manager for your team.

10

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

𝗣𝗿𝗼𝘁𝗲𝗰𝘁𝗶𝗻𝗴 𝗮𝗻𝗱 𝗠𝗮𝘅𝗶𝗺𝗶𝘇𝗶𝗻𝗴 𝗘𝗥𝗣 𝗜𝗻𝘃𝗲𝘀𝘁𝗺𝗲𝗻𝘁 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 Credit to ERP Today. "⇨The shift to ERP systems like SAP S/4HANA and Infor CloudSuite necessitates improved testing workflows due to the increasing frequency of software updates, moving from annual to monthly releases, which complicates traditional testing methods. ⇨ Original Software emphasizes a low-code/no-code approach to testing, allowing businesses to streamline their testing processes without introducing additional complexity or risk associated with traditional code-based testing solutions. ⇨Utilizing AI in testing is crucial for enhancing user-friendliness and accessibility of test scripts, enabling broader participation in the testing process and improving efficiency, while also emphasizing the need for businesses to adapt to the rapid technological changes in their software ecosystems..." https://lnkd.in/ertPUutP

3

1 Comment

It is tough boosting SAP skills to keep up with the latest SAP innovations but the consultants winning the best engagements build their competitive edge through consistent, deliberate learning. Here’s how to do it: 👇🤔 🧱 Build across layers, as well as modules A competitive profile combines SAP module certification, BTP proficiency, and also non-SAP qualifications such as hyperscaler credentials, or project management qualifications. 📅 Make learning part of your schedule Maintain consistent learning activity each year: a certification in progress, or a stay-current assessment lined up. By adding at least one credential per year, with quarterly check-ins against SAP's release cycle, this is a realistic and manageable schedule. 🔁 Maintain your certifications! SAP certifications now expire after twelve months without a stay-current assessment via SAP Learning Hub. Miss the window and you must resit the full exam. The new performance-based format rolling out now tests applied skills in live SAP environments, so keep that in mind. 🏗️ Every credential needs a project story Certification proves knowledge but hiring managers need evidence that each qualification has been exercised on an engagement: describing what you configured, what the business outcome was, what judgment the work required. That is what converts a credential into a proof of competency. 🤖 Get ahead of AI in SAP SAP Business AI and Joule are now standard in S/4HANA Cloud and BTP. Understanding how AI-assisted workflows affect configuration, data governance, and process design is becoming a baseline expectation on projects. 📋 Adjacent credentials expand the scope you are trusted with. PMP, PRINCE2, SAP Activate PM, and Agile certifications appear consistently on programmes where consultants are expected to lead workstreams or manage stakeholders. The time investment is modest relative to the access they create. 🔍 Use SAP's free resources SAP Road Map Explorer shows where each product is heading. SAP Community blogs and TechEd on-demand sessions provide current intelligence at no cost. Focus learning on your current module, then BTP, then the adjacent credential closest to your next target role. 👁️ Keep your profile visibly current Credly badges, LinkedIn certifications, SAP Community contributions, and outcome-focused project descriptions must all be relevant. Recruiters and hiring managers notice when the most recent credential is years old. 🎯 Speak your client's language Every certification on your profile should sit alongside a sentence describing the business outcome it supported. Hiring teams are reading your profile to decide whether you have solved their specific problem before. Treat your skills profile as a living document, evidenced with project outcomes and aligned to where SAP is heading, so you are fully qualified to step up to the next role. What does your current SAP learning stack look like? Share in the comments. ⬇️ #IgniteSAP #ContinuousLearning

16

7 Comments

The ERP server manages eight corporations using a single SAP B1 server. It aggregates and displays current A/P data. The web server uses wihnost.com, and SAP B1 runs on a Cloud Server. The web application is ASP 3.0, and the database is MS SQL. Click the number to the right of the amount to view detailed information.

2

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