01 — Notebook Information & Scope

Architectural Thesis

Enterprise Resource Planning (ERP) is fundamentally a business process transformation system enabled by software, not merely a software package. Its purpose is to enforce disciplined master data management, transactional integrity, and cross-functional synchronization across an enterprise.

Domain: Operations & Supply Chain Systems
Subject: Enterprise Resource Planning
Pedagogical Lead: Prof. Rahul Altekar
Core Reference Model: 3-Tier Distributed Architecture & The Five Pillars of Enterprise Alignment

02 — Learning Map

[Siloed Legacy Systems] ──> [Integration Need] ──> [3-Tier Client-Server]
                                                         │
                                                         ▼
[Value Matrix Prioritization] <── [The Five Pillars] <── [Relational RDBMS Engine]

03 — Core Concepts: What is ERP?

Enterprise Resource Planning (ERP) is a software-driven business management system that integrates all core transactional processes of an enterprise into a unified relational database architecture.

The Problem of Siloed Legacy Applications

Prior to modern ERP systems, commercial enterprises operated isolated departmental databases:

Sales & Marketing maintained isolated customer records in stand-alone CRM or custom billing tools.
Manufacturing & Operations planned shop-floor work orders on standalone MRP-I software.
Procurement & Warehousing tracked purchase orders in local inventory ledgers.
Finance & Accounting manually re-keyed invoices and ledger entries at month-end.

This departmental fragmentation produced structural liabilities:

Data Duplication & Redundancy: The same customer, product, or supplier was represented multiple times across incompatible formats.
Batch Latency: Cross-departmental synchronization occurred in weekly or monthly batch runs, leaving executive leadership blind to real-time inventory and cash obligations.
Lack of Single Source of Truth (SSOT): Discrepancies between physical inventory and book records generated frequent stockouts and operational friction.

📌

ERP Core Definition

An ERP system replaces departmental batch handoffs with a shared, synchronous relational database where a transaction executed anywhere in the enterprise instantly updates all associated ledgers, inventories, and accounting entries.

04 — The 3-Tier Client-Server Architecture

Modern ERP platforms (such as SAP S/4HANA and Oracle Cloud Applications) execute upon a distributed three-tier architecture:

Presentation Layer (Tier 1 — Client UI): The user interface (desktop GUI, web browser, or mobile interface) responsible for input capture and output display. It executes zero business logic and zero direct database queries.
Application Layer (Tier 2 — Business Logic Engine): A scalable cluster of application servers executing program rules, transactional authorizations, pricing logic, MRP explosions, and workflow state machines.
Database Layer (Tier 3 — Relational/In-Memory RDBMS): The central repository storing all transactional tables, document records, and master data. It guarantees ACID properties (Atomicity, Consistency, Isolation, Durability).

OLTP vs. OLAP Database Processing Dynamics

COMPARISON

Architectural Dimension	OLTP (ERP Core)	OLAP (Data Warehouse / BI)
Primary Objective	Execute high-volume, real-time business transactions	Perform historical aggregations and multidimensional analysis
Data Structure	Highly normalized relational schema (3NF) to prevent anomalies	Denormalized star or snowflake schemas optimized for read scans
Query Latency	Milliseconds per single transaction insert/update	Seconds to minutes for large aggregation scans
Update Frequency	Continuous, synchronous transactional commits	Periodic asynchronous ETL batch loads

05 — Strategic Frameworks: The Five Pillars of ERP

Prof. Rahul Altekar emphasizes five foundational pillars necessary for ERP operational viability:

Integrated Business Processes: Eliminating organizational silos so that sales, manufacturing, logistics, and finance operate as one continuous workflow.
Single Source of Truth (SSOT): Centralized data repository preventing conflicting definitions of inventory, cost, or customer balances.
Real-Time Visibility: Instant visibility of order statuses, WIP queue lengths, cash positions, and material availability across the supply network.
Standardized Best Practices: Aligning operating procedures with globally tested process templates (e.g. SAP reference workflows) rather than custom departmental quirks.
Organizational Discipline & Master Data Governance: Rigorous enforcement of input validation, role-based authorizations, and structured master data governance.

06 — Strategic Prioritization: Value Matrix Analysis

When evaluating ERP functionality and process automation, executive sponsors utilize the Value Matrix:

High Value / Low Risk (Quadrant I — Immediate Quick Wins): Core financial ledgers, inventory visibility, standardized purchase order workflows. High return with minimal disruption.
High Value / High Risk (Quadrant II — Strategic Transformational Projects): Advanced planning and scheduling (APS), multi-plant S&OP synchronization, shop-floor automation. Requires major change management.
Low Value / Low Risk (Quadrant III — Operational Hybrids): Standard office workflows, basic expense tracking. Safe but marginal return.
Low Value / High Risk (Quadrant IV — The Danger Zone / Traps): Deep custom code modifications to accommodate non-standard departmental legacy procedures. Avoid at all costs.

⚠️

Common ERP Implementation Mistake

Customizing standard ERP software to fit broken legacy business processes is the #1 cause of ERP budget overruns and operational failures. Organizations must adapt their processes to standard ERP software, not customize the software to legacy bad habits.

07 — Active Recall & Study Flashcards

🗂 Flashcard • ArchitectureClick to Flip

What are the three tiers in modern ERP client-server computing?

Reveal Definition / Answer ↓

1. Presentation Layer (User Interface / Browser), 2. Application Layer (Business Logic Engine), 3. Database Layer (Normalized ACID RDBMS / In-Memory Store).

🗂 Flashcard • GovernanceClick to Flip

Why is master data discipline considered the foundation of ERP success?

Reveal Definition / Answer ↓

Because transactional workflows inherit parameters directly from master data. An error in a material master (e.g., wrong lead time or unit of measure) cascades through every future MRP calculation, purchase order, and inventory valuation.

08 — Interactive Conceptual Check

Conceptual Check / QuizActive Recall

Which of the following processes belongs strictly to the Application Layer in a 3-tier ERP architecture?

09 — Verified Examination Questions & Model Solutions

Q1.[Strategic Theory](10 Marks)

ERP Business Applications Core Question Bank

Explain the evolution from siloed functional applications to Enterprise Resource Planning. What business liabilities did siloed applications create?

▸Reveal Model Solution & Answer Blueprint

1. Executive Summary: Pre-ERP enterprise systems were functionally isolated, resulting in data redundancy, asynchronous batch latency, and cross-departmental conflict.

2. Core Structural Liabilities:

Information Asymmetry: Sales promised delivery dates based on manual spreadsheets without visibility into shop floor WIP or component shortages.
Inventory Inaccuracies: Month-end reconciliations routinely revealed unrecorded material consumption, driving safety stock inflation.
High Transactional Cost: Every inter-departmental transaction required manual paper slips or duplicate re-entry into secondary ledgers.

3. The ERP Solution: Implementing a common relational schema with real-time transactional posting provides immediate end-to-end auditability and eliminates duplicate data entry.