ERP Module Landscape & Integration Flashcards
7 cards from real ERP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 ERP Module Landscape & Integration flashcards as text
Which integration pattern uses a central hub to translate messages between ERP modules rather than direct point-to-point connections?
Answer: Enterprise Service Bus (ESB)
An Enterprise Service Bus (ESB) acts as a central middleware layer that routes and transforms messages between ERP modules, eliminating the complexity of point-to-point integrations.
In an ERP system, the Master Data Management (MDM) module's primary role is to:
Answer: Maintain a single authoritative version of core business data
MDM ensures that a single, consistent, and accurate version of master data—such as customer, supplier, and product records—is maintained across all ERP modules.
Which ERP module typically owns the Chart of Accounts (COA) configuration that other modules post transactions to?
Answer: General Ledger (GL)
The General Ledger module owns the Chart of Accounts, and all other ERP modules (AP, AR, payroll, inventory) post their financial transactions into the GL.
A 'tight coupling' integration between ERP modules means:
Answer: Modules share the same physical database tables
Tight coupling means modules share underlying database tables or direct function calls, making them highly interdependent and harder to update independently.
Which ERP sub-module handles the process of matching purchase orders, goods receipts, and vendor invoices before payment?
Answer: Three-way match in Accounts Payable (AP)
The three-way match in Accounts Payable compares the purchase order, goods receipt, and vendor invoice to ensure accuracy before authorizing payment.
In ERP integration, an 'API-first' approach means:
Answer: ERP modules expose well-defined APIs as the primary integration mechanism
An API-first approach means ERP modules expose RESTful or SOAP APIs as the standard integration interface, enabling real-time, scalable, and loosely coupled connections.
Which ERP module integration scenario describes the Procure-to-Pay (P2P) process?
Answer: Purchase Requisition → Purchase Order → Goods Receipt → Accounts Payable → General Ledger
The Procure-to-Pay process flows from Purchase Requisition through Purchase Order, Goods Receipt, Accounts Payable invoice verification, and final posting to the General Ledger.