“The end-to-end FI process in SAP starts with defining the organisational structure — Company Code, Fiscal Year Variant, and Chart of Accounts. From there, we configure the G/L accounts, set up the Accounts Payable and Accounts Receivable sub-ledgers, and define document types and posting keys. In a live scenario, when a vendor invoice arrives, the AP process flows from invoice entry → document posting → payment run via F110 → bank reconciliation. Every posting generates a document with a unique document number tracked in the FI module. Integration with MM happens at the point of goods receipt and invoice verification through the MM-FI interface.”

“A Company Code is the smallest organisational unit for which a complete set of accounts can be drawn up — it represents a legal entity. A Business Area is used to produce financial statements for internal reporting across company codes — it’s not legally required but useful for segment reporting. A Profit Centre is a management accounting concept in CO that tracks revenue and costs for internal profitability analysis — it doesn’t produce legal financial statements but drives management decision-making. In S/4HANA, Profit Centre Accounting has become the primary tool for segment reporting, making Business Areas less commonly used in new implementations.”

“Asset depreciation in SAP FI-AA is configured through Depreciation Areas and Depreciation Keys. The Depreciation Area determines which values are posted — for example, Area 01 is typically book depreciation posted to G/L. The Depreciation Key defines the calculation method — straight-line, declining balance, or units of production. Configuration involves: setting up the Chart of Depreciation → defining Depreciation Areas → assigning the Chart of Depreciation to the Company Code → creating Asset Classes → configuring Depreciation Keys. The periodic depreciation run (AFAB) then posts depreciation automatically based on the asset master data and configured keys.”

“The P2P cycle in SAP MM flows as: Purchase Requisition (ME51N) — internal request for materials → RFQ/Quotation (ME41/ME47) — request for vendor quotes if required → Purchase Order (ME21N) — formal order to vendor → Goods Receipt (MIGO) — recording receipt of materials, which posts a GR/GI document and updates inventory → Invoice Verification (MIRO) — 3-way match between PO, GR, and vendor invoice → Payment (F110) — automatic payment run in FI. The GR posting in MM triggers a corresponding entry in FI, which is the MM-FI integration point. In S/4HANA, this process runs on a simplified data model with real-time inventory valuation.”

“The 3-way match in SAP MM is the validation during invoice verification (MIRO) that compares three documents: the Purchase Order (what was ordered and at what price), the Goods Receipt (what was actually delivered), and the Vendor Invoice (what the vendor is charging). SAP automatically checks for price and quantity variances between these three. If the invoice price exceeds the PO price by more than a tolerance limit, the system blocks the invoice for payment until a buyer resolves the discrepancy. This controls financial risk and prevents over-payment — a key control in any procurement process.”

“The O2C process in SAP SD flows as: Sales Inquiry / Quotation (VA11/VA21) — optional pre-sales steps → Sales Order (VA01) — customer order with pricing, delivery date, and item confirmation → Delivery (VL01N) — picking, packing, and goods issue which reduces inventory and posts in MM → Billing (VF01) — billing document created, revenue recognised in FI → Payment — customer payment received and cleared in AR. The SD-FI integration happens at billing — the billing document triggers an accounting document in FI. The SD-MM integration happens at goods issue — stock is reduced and COGS is posted.”

“A condition type in SAP SD pricing defines the type of price element applied to a sales document. Examples: PR00 — basic price, K007 — customer discount, K005 — material discount, MWST — output tax, KF00 — freight. Condition types are combined in a Pricing Procedure, which defines the sequence and calculation logic. For example, the final customer price = PR00 (base price) – K007 (customer discount) – K005 (material discount) + MWST (tax) + KF00 (freight). Configuration involves defining condition types, maintaining condition records (pricing master data), and assigning the pricing procedure to the sales area.”

“These are three different SAP enhancement tools: A BAPI (Business Application Programming Interface) is a standardised, stable method that allows external systems or custom programs to interact with SAP business objects — used for system integrations. A BAdI (Business Add-In) is an object-oriented enhancement spot — SAP delivers a defined interface and you implement custom logic inside it. Multiple active implementations are possible. A User Exit is an older function-based enhancement — SAP provides empty subroutines (FORM routines) which you fill with custom code. User Exits can only have one active implementation. In modern S/4HANA development, BAdIs are the preferred approach. User Exits are legacy technology but still commonly found in existing systems.”