Practice Test GeeksERP - Management Practice Test
← All ERP Flashcard Decks

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 Integration flashcards as text

  1. A company migrating from a legacy ERP to SAP S/4HANA must map old general ledger account codes to new ones. What is this process called?

    Answer: Field mapping / data mapping

    Field mapping (data mapping) defines the transformation rules that translate source fields to target fields during ERP data migration or integration.

  2. What is the main purpose of a 'canonical data model' in ERP integration architecture?

    Answer: Provide a common, neutral data format that all connected systems transform to and from

    A canonical data model creates a neutral format so each system only needs one transformation (to/from canonical) instead of N×N direct mappings.

  3. Which ERP integration scenario is most likely to use an SFTP-based batch file transfer?

    Answer: Nightly payroll file exchange with a bank or payroll bureau

    Banks and payroll bureaus commonly use scheduled SFTP file drops because they process transactions in batch overnight rather than in real time.

  4. When two ERP systems need to share master data (e.g., vendor records), what governance discipline ensures consistency across platforms?

    Answer: Master data management (MDM)

    Master data management (MDM) establishes policies, processes, and tools to keep shared reference data synchronized and accurate across all systems.

  5. In an ERP integration, a 'dead letter queue' is used to handle what situation?

    Answer: Hold messages that could not be processed successfully after maximum retries

    A dead letter queue captures failed messages so they can be inspected and reprocessed without being lost, preventing silent data gaps.

  6. An ERP integration team notices that customer records updated in the CRM are overwriting newer changes made directly in the ERP. What integration design principle was violated?

    Answer: System of record (authoritative source) definition

    Each data entity must have exactly one designated system of record; allowing both systems to write back the same field without conflict resolution causes overwrites.

  7. What does API versioning (e.g., /api/v1/ vs. /api/v2/) protect against in long-running ERP integrations?

    Answer: Breaking changes that would disrupt existing integrations when the API is updated

    API versioning lets the ERP team evolve the interface without immediately breaking all existing consumers, who can migrate to the new version on their own schedule.