ECC 6.0 includes EHPs 1–8, adding new features without a full upgrade. 2. Essential Manuals & Documentation Types | Document Type | Purpose | Typical Audience | |---------------|---------|------------------| | User Manual | Step-by-step transaction execution | End users, super users | | Configuration Guide (IMG) | System setup via Implementation Guide | Functional consultants | | Process Flow Document | Cross-module business process mapping | Business analysts | | ABAP Developer Guide | Custom programs, reports, enhancements | Developers | | Security Guide | Role/authorization design | Basis/security admins | | Basis Administration Manual | System health, transports, jobs | Basis team | 3. Core Navigation & Transaction Codes (T-Codes) SAP ECC is transaction-driven. Key T-Codes every manual should include:
Transaction: ME21N – Create Purchase Order Prerequisites: Material master exists (MM01), vendor master exists (XK01) sap ecc 6.0 manual
| T-Code | Function | Module | |--------|----------|--------| | SE38 | ABAP program execution | Basis | | SE11 | Data dictionary (tables) | Basis | | SU01 | User maintenance | Security | | PFCG | Role maintenance | Security | | SM30 | Table maintenance (view) | Basis | | MM01 | Material master creation | MM | | ME21N | Purchase order creation | MM | | VA01 | Sales order creation | SD | | FB50 | General ledger posting | FI | | IW31 | Maintenance order creation | PM | Always prefix T-codes with /n in the command field to switch sessions, or /o to open a new session. 4. Structure of a Good End-User Manual Entry Each transaction in your manual should follow this template: Core Navigation & Transaction Codes (T-Codes) SAP ECC