SAP Learnings

  Greenfield Implementation (Fresh Start)✔️ A Greenfield implementation involves starting from scratch: setting up a brand-new SAP system with redesigned processes and configuration. Existing data and customizations are not carried over automatically. Instead, only selected master and transactional data might be migrated, allowing organizations to adopt SAP best practices and eliminate legacy technical debt. Example: A manufacturing company running multiple, outdated ERP systems decides to unify its operations with SAP S/4HANA. They use the Greenfield approach to design new, standardized global processes, opting not to bring in past custom developments or obsolete data structures. Data from old systems is selectively cleansed and imported into the new landscape. Brownfield Implementation (System Conversion)✔️ A Brownfield implementation is a system conversion or upgrade. The existing SAP ERP (such as ECC) system, including configurations, data, and processes, is transitio...

SAP MM TRAINING & DOCUMANTATIONS 👇  sphoorthisapmm2025.blogspot.com

  🖥️ SAP GUI – SPRO (Configurations) – On-Premise Environment : Traditional on-premise setup Tool : SAP GUI with SPRO (SAP Project Reference Object) Capabilities : Full access to backend configurations Deep customization of SAP modules (FI, MM, SD, etc.) Direct control over system landscape and transport routes 🌐 SAP Fiori – UI – Cloud Deployment 1. Public Cloud (e.g., AWS, Azure, Google Cloud) Type : Multi-tenant SaaS model Customization : ❌ Not allowed Limitations : Only standard Fiori apps and configurations No access to backend SPRO or custom Z-developments Ideal for rapid deployment and standard business processes 2. Private Cloud (Dedicated Cloud on AWS, Azure) Type : Single-tenant managed cloud Customization : ✅ Allowed Capabilities : Access to SPRO and custom developments Flexibility similar to on-premise Managed infrastructure with SAP Basis support 🔍 Summary Table

In interviews, I often get this question: 👉 “If you are implementing calibration in SAP, what master data do you need?” Most consultants get stuck here. Because calibration is not just PM. It’s a mix of PM + QM integration. Here’s the step-by-step list you must know (and explain like in real-time): ⸻ 🔑 Master Data for Calibration 1. Equipment (IE01) • All measuring instruments must be created as Equipment. • Use Equipment Category Q for Quality Instruments. 2. Catalog (QS41) • Define parameter attributes as Catalog. • Catalog type: 1 – Characteristic Attributes. • Create Code Groups → Release them → Add Codes. 3. Selected Set (QS51) • Link Catalogs into Selected Sets. • Status must be Released. • If valuation = “Rejected,” assign a defect class. 4. Master Inspection Characteristics (MICs) (QS21) • Two types: • Quantitative → Define limits & sampling procedure. • Qualitative → No numeric value, just recording. • Control indicators must be set properly. 5. Sampling Proc...