ERP ERP Module Landscape & Integration 2 — Questions and Answers
Question 1: Which integration pattern uses a central hub to translate messages between ERP modules rather than direct point-to-point connections?
- Enterprise Service Bus (ESB) (Correct answer)
- Peer-to-peer API mesh
- Flat-file batch transfer
- Direct database linking
Correct 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.
Question 2: In an ERP system, the Master Data Management (MDM) module's primary role is to:
- Generate financial reports automatically
- Maintain a single authoritative version of core business data (Correct answer)
- Process payroll transactions
- Schedule production work orders
Correct 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.
Question 3: Which ERP module typically owns the Chart of Accounts (COA) configuration that other modules post transactions to?
- Inventory Management
- Human Resources
- General Ledger (GL) (Correct answer)
- Customer Relationship Management
Correct 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.
Question 4: A 'tight coupling' integration between ERP modules means:
- Modules share the same physical database tables (Correct answer)
- Modules communicate only via scheduled batch files
- Modules are fully independent with no shared data
- Modules use external cloud APIs exclusively
Correct 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.
Question 5: Which ERP sub-module handles the process of matching purchase orders, goods receipts, and vendor invoices before payment?
- Accounts Receivable (AR)
- Three-way match in Accounts Payable (AP) (Correct answer)
- Order-to-Cash (O2C)
- Payroll processing
Correct 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.
Question 6: In ERP integration, an 'API-first' approach means:
- All integrations are built using direct database queries
- ERP modules expose well-defined APIs as the primary integration mechanism (Correct answer)
- Batch file transfers take priority over real-time data exchange
- Manual data entry is the default for cross-module updates
Correct 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.
Question 7: Which ERP module integration scenario describes the Procure-to-Pay (P2P) process?
- Sales Order → Shipping → Accounts Receivable → General Ledger
- Purchase Requisition → Purchase Order → Goods Receipt → Accounts Payable → General Ledger (Correct answer)
- Production Order → Work Center → Quality Control → Inventory
- Customer Inquiry → Quotation → Sales Order → Billing
Correct 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.
ERP ERP Module Landscape & Integration 2
Which integration pattern uses a central hub to translate messages between ERP modules rather than direct point-to-point connections?