4. Enterprise Systems and Logistics Integration

Introduction and Context

Logistics performance depends not only on physical movement but also on the quality, timing, and coordination of information. A shipment may be physically available, yet operationally invisible if its status is not recorded. A purchase order may be correctly issued, yet create disruption if the supplier, warehouse, transport provider, and finance department interpret its data differently. Enterprise systems address this problem by connecting transactions, processes, people, and decisions across organizational functions and, increasingly, across organizational boundaries.

Enterprise integration is the coordinated linking of systems such as enterprise resource planning (ERP), supply chain management (SCM), order management, procurement, customer relationship management (CRM), warehouse management, transportation management, and financial applications. Integration allows information entered in one process to become available to authorized users and systems elsewhere without repeated manual entry. In logistics, this can improve visibility, reduce errors, accelerate decisions, and align commercial, operational, and financial activity.

Integration, however, is not simply a technical exercise. It involves process design, data governance, organizational authority, cybersecurity, contractual relationships, and managerial choices about standardization and flexibility. A poorly designed integration may transmit inaccurate information faster, automate unsuitable processes, or expose sensitive data. The objective is therefore not maximum connectivity, but useful, controlled, and strategically aligned connectivity.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the role of ERP, SCM, order management, procurement, CRM, and financial systems in logistics.

2. Distinguish systems integration from simple data exchange.

3. Compare EDI, APIs, middleware, and event-driven architecture.

4. Explain how information flows across organizational and supply-chain boundaries.

5. Evaluate integration choices in relation to visibility, cost, speed, risk, and governance.

6. Apply integration principles to logistics problems and managerial decisions.

7. Identify implementation risks, ethical concerns, and emerging developments.

The Enterprise System Landscape in Logistics

An enterprise system is an organized combination of applications, databases, processes, infrastructure, and controls used to support business operations. Its value lies in connecting activities rather than merely automating isolated tasks.

Enterprise Resource Planning

ERP is the transactional backbone of many organizations. It integrates functions such as sales, purchasing, inventory, production, human resources, asset management, and finance through shared master data and coordinated workflows. In logistics, an ERP may create a sales order, generate a demand signal, reserve inventory, initiate replenishment, record goods receipt, issue an invoice, and post the resulting financial entries.

The principal strength of ERP is transactional integrity. A material receipt can update inventory, create an accounts-payable liability, and support supplier performance measurement. However, ERP systems are not always optimized for every logistics activity. Warehouse execution, route optimization, real-time tracking, and complex order orchestration may require specialist applications integrated with the ERP.

Supply Chain Management Systems

SCM systems extend the enterprise view beyond internal transactions. They support demand planning, supply planning, forecasting, inventory positioning, supplier collaboration, transportation planning, and supply-chain performance analysis. Whereas ERP commonly records what has occurred, SCM applications often help determine what should occur and when.

The distinction is not absolute. Modern platforms increasingly combine ERP and SCM capabilities. The important managerial issue is the quality of coordination between planning and execution. A sophisticated forecast is of limited value if procurement cannot act on it, warehouse capacity is ignored, or transport constraints are absent from the planning model.

Order Management Systems

An order management system (OMS) coordinates customer orders from capture through fulfillment, delivery, returns, and settlement. It may receive orders from websites, marketplaces, sales representatives, stores, or electronic channels. The OMS determines availability, allocates inventory, selects a fulfillment location, manages backorders, and communicates status to customers.

In omnichannel logistics, the OMS is particularly important because inventory may be distributed across stores, warehouses, suppliers, and third-party logistics providers. The system must apply rules concerning promised delivery dates, service levels, transportation cost, inventory ownership, and customer priority. Integration with warehouse, transport, CRM, and finance systems prevents the customer promise from becoming detached from operational reality.

Procurement and Supplier Systems

Procurement systems manage requisitions, sourcing, purchase orders, approvals, supplier information, contracts, receipts, and invoice matching. They support the source-to-pay process, beginning with the identification of a requirement and ending with payment.

Integration enables a purchase order to be compared with the supplier’s acknowledgment, advance shipment notice, receipt record, and invoice. Three-way matching—purchase order, goods receipt, and invoice—is a common control. It reduces overpayment and helps identify quantity, price, or delivery discrepancies. Supplier portals and supplier relationship management tools may also provide shared forecasts, capacity information, quality records, and compliance documentation.

Customer Relationship Management

CRM systems maintain information about customers, interactions, service cases, opportunities, and preferences. Their logistics relevance is sometimes underestimated. Customer service staff need accurate information about order status, inventory availability, delivery exceptions, returns, and claims. Integration with OMS, warehouse, transport, and finance systems allows service personnel to respond using operational facts rather than estimates.

CRM also supports segmentation and service differentiation. For example, a high-value customer may have a contractual requirement for priority delivery or proactive disruption notification. Such policies must be translated into executable logistics rules and not remain merely as customer-service intentions.

Financial and Management Systems

Financial systems record revenue, costs, payables, receivables, tax, assets, and profitability. Logistics events have financial consequences: purchasing creates obligations, inventory movements affect valuation, transportation generates costs, and delivery may trigger revenue recognition or customer billing.

Integration allows logistics managers to evaluate total cost rather than only operational measures. A low-cost transport option may produce more damages, delays, or customer concessions. Linking logistics activity with finance makes these trade-offs visible. Management information systems and business intelligence tools then aggregate transactions into measures such as cost per order, inventory carrying cost, supplier variance, fulfillment profitability, and working-capital utilization.

From Functional Silos to an Integrated Process View

Traditional organizations often develop functional silos. Sales promises delivery dates, procurement negotiates prices, warehousing manages space, transport arranges movement, and finance controls expenditure. Each function may optimize its own indicators while weakening overall performance. Enterprise integration encourages an end-to-end process perspective.

A useful example is the order-to-cash process. The customer order begins in a commercial channel, passes through credit validation and inventory allocation, is fulfilled by warehouse and transport operations, and ends with invoicing and payment. The process crosses several systems and departments. Integration creates a shared transaction identity and enables the organization to trace the order across its lifecycle.

Similarly, procure-to-pay links demand identification, requisition, sourcing, purchase order, supplier fulfillment, receipt, invoice verification, and payment. Plan-to-deliver connects forecasting and supply planning with production, inventory, warehouse, and transport execution. These process perspectives reveal that an integration project should begin with business outcomes and process dependencies, not with a list of software interfaces.

Important Concepts and Terminology

Several concepts are central to integration design.

Master data refers to relatively stable entities such as products, customers, suppliers, locations, units of measure, payment terms, and carriers. Transactional data records business events such as orders, receipts, shipments, invoices, and payments. Reference data provides controlled classifications, such as country codes, status values, currencies, and transport modes.

A system of record is the authoritative source for a particular data domain. A single source of truth is a consistent, trusted view of information, although it does not necessarily mean that only one physical database exists. Data quality concerns accuracy, completeness, consistency, timeliness, validity, and uniqueness. Interoperability is the ability of systems to exchange and use information meaningfully. Latency is the time between an event occurring and its availability for use.

An interface is a defined mechanism through which systems exchange information. Synchronous communication requires an immediate response, whereas asynchronous communication allows the sender and receiver to operate independently. An event is a significant change of state, such as “shipment dispatched” or “inventory received.” An event bus distributes events to interested applications. Orchestration uses a coordinating component to direct a process; choreography allows services to react independently to events according to defined rules.

Integration Architectures and Methods

No single method is universally superior. The suitable choice depends on transaction volume, partner capability, data sensitivity, required speed, process complexity, and investment horizon.

Electronic Data Interchange

Electronic data interchange (EDI) is the structured, computer-to-computer exchange of standardized business documents. Common documents include purchase orders, order acknowledgments, advance shipment notices, invoices, and shipment status messages. EDI reduces manual re-keying and provides predictable document formats, making it valuable in high-volume, repetitive business relationships.

EDI traditionally uses value-added networks or managed connectivity, although Internet-based approaches are now common. Its advantages include established standards, auditability, and suitability for formal business documents. Its limitations include implementation cost, rigid formats, slower change cycles, and dependence on agreed standards and partner onboarding. EDI usually communicates business documents rather than every operational event, so it may need to coexist with APIs or real-time tracking services.

Application Programming Interfaces

An API is a defined set of rules through which one application requests data or functionality from another. A logistics platform may use an API to obtain a carrier quotation, create a shipment, check inventory, or retrieve a delivery status. APIs can support near-real-time interaction and more granular services than traditional document exchange.

RESTful APIs commonly use web protocols and lightweight formats such as JSON, while other approaches may use XML or specialized protocols. Effective API design requires authentication, authorization, version management, rate controls, validation, error handling, monitoring, and clear ownership. An API is not automatically a good integration: an unstable interface, unclear data definitions, or excessive dependence on a single provider can create significant operational risk.

Middleware and Integration Platforms

Middleware is software that connects applications and manages communication, transformation, routing, monitoring, and security. Enterprise service buses historically provided centralized routing and transformation. Contemporary integration-platform-as-a-service solutions may combine API management, workflow integration, data mapping, message queues, and monitoring in cloud environments.

Middleware is valuable when applications use different data structures or communication methods. For example, it can transform a warehouse status code into the format required by an ERP and route exceptions to a control tower. However, excessive point-to-point interfaces create a fragile network in which every application depends directly on many others. A governed integration layer can reduce this complexity, though it introduces its own architecture, skills, and cost requirements.

Event-Driven Architecture

In an event-driven architecture, systems publish events when meaningful changes occur, and other systems subscribe to events relevant to their functions. A “goods received” event may update inventory, trigger quality inspection, release an invoice for matching, and inform the supplier portal. The producing system does not need to know every consumer.

This architecture can improve responsiveness, scalability, and decoupling. It is especially useful for shipment tracking, inventory alerts, exception management, and IoT-enabled logistics. It also creates challenges. Events must be uniquely identified, ordered where necessary, retained for an appropriate period, and processed safely if delivered more than once. Organizations need observability, replay capability, failure recovery, and clear event ownership. Eventual consistency may be acceptable for a status dashboard but unsuitable for a legally controlled financial posting.

Choosing Among Integration Approaches

A practical decision should consider:

• the required response time and tolerance for delay;
• document standardization and partner readiness;
• transaction volume and expected growth;
• data sensitivity and regulatory obligations;
• process complexity and exception frequency;
• implementation and operating cost;
• resilience, monitoring, and recovery requirements; and
• the organization’s internal capabilities.

Many mature logistics environments use a hybrid architecture: EDI for formal trading documents, APIs for interactive services, middleware for transformation and governance, and events for operational changes and alerts.

Cross-Organizational Information Sharing

Logistics networks often include manufacturers, suppliers, brokers, carriers, ports, warehouses, retailers, platforms, regulators, and customers. Information sharing can reduce uncertainty, but it also redistributes power and risk. Participants may hesitate to share forecasts, inventory, costs, or capacity because they fear commercial disadvantage or misuse.

Effective sharing requires agreement on data ownership, permitted use, quality responsibilities, timing, security, retention, and liability. A shared data model is useful only when participants interpret fields consistently. For example, “available inventory” may mean physically present stock, unrestricted stock, stock after safety reservations, or stock available for a particular customer. Ambiguity at this level can cause more harm than a lack of data.

Governance mechanisms include data-sharing agreements, service-level agreements, access controls, data classification, audit trails, dispute procedures, and common performance definitions. Trust is strengthened when participants can see who changed data, when it changed, and how it was used. The principle of minimum necessary access should apply: partners should receive the information required for an agreed process, not unrestricted visibility into the enterprise.

A Framework for Designing Integration

A disciplined integration program can follow six connected stages.

First, define the business outcome. Examples include reducing order-cycle time, improving inventory accuracy, increasing invoice-match rates, or providing reliable delivery promises. Second, map the end-to-end process and identify decisions, handoffs, data requirements, and exceptions. Third, establish data ownership and quality rules before building interfaces. Fourth, select an architecture and integration method based on business and technical requirements. Fifth, implement in controlled increments, beginning with high-value and manageable use cases. Sixth, monitor outcomes and revise processes as operating conditions change.

Architecture should be accompanied by an integration governance board or equivalent authority. Governance should control interface standards, naming conventions, versioning, security patterns, testing, incident management, and retirement of obsolete connections. Key performance indicators may include interface availability, message failure rate, data completeness, processing latency, duplicate transactions, manual interventions, and business outcomes such as delivery reliability or working-capital improvement.

Testing must include more than a successful data transfer. Functional testing verifies business rules; volume testing assesses performance; security testing examines unauthorized access; resilience testing evaluates failure and recovery; and end-to-end testing confirms that the complete process produces the intended operational and financial result. Partner testing is essential where external organizations are involved.

Practical Applications in Logistics

Integration supports a range of operational decisions. In inbound logistics, a supplier’s advance shipment notice can prepare dock capacity, create expected receipts, and support labor planning. In warehouse operations, real-time inventory updates can prevent an OMS from promising stock that has already been allocated. In transportation, an API can compare carrier rates and capacity while a tracking event can trigger customer notifications and exception workflows.

In reverse logistics, the OMS, CRM, warehouse, quality, and finance systems must coordinate return authorization, inspection, disposition, refund, replacement, and inventory status. In cold-chain operations, sensor events may be integrated with shipment records so that temperature deviations generate alerts, investigation tasks, and claims documentation. In financial control, integrated receipt and invoice data can identify unauthorized purchases, duplicate invoices, or supplier billing discrepancies.

Analytics adds another layer. A data platform can combine orders, inventory, transport events, costs, and customer outcomes. Descriptive analytics explains what happened; predictive analytics estimates likely delays or shortages; prescriptive analytics recommends actions. Artificial intelligence may assist with demand forecasting, anomaly detection, document extraction, route decisions, and customer-service responses. These applications remain dependent on reliable source data, explainable rules where decisions affect stakeholders, and human oversight for exceptional or high-impact cases.

Illustrative Case: Integrating a Multi-Channel Distributor

Background

The following fictional case concerns Northstar Distribution, a regional distributor serving industrial customers through sales representatives, a web portal, and marketplace channels. It operates two warehouses and uses several contracted carriers.

Situation and Problem

Northstar’s ERP recorded financial transactions and purchase orders, while each warehouse used a separate warehouse management system. Customer orders were entered manually from some channels. Inventory updates were transferred several times a day, and carrier status was received through spreadsheets or email. Customers frequently received confirmation for products that were unavailable or were given delivery dates that excluded warehouse capacity and carrier constraints. Finance also reported a high number of invoice exceptions.

Management initially proposed replacing all systems with a single platform. A diagnostic review showed that the principal weaknesses were inconsistent product and location codes, unclear ownership of inventory status, and the absence of an integrated order process. A complete replacement would have been expensive and disruptive.

Analysis

The project team mapped the order-to-cash process and identified four critical information gaps: available-to-promise inventory, order status, shipment status, and proof of delivery. It also found that product units of measure differed between the ERP and warehouse systems. The team defined the ERP as the financial system of record, the warehouse systems as authoritative for physical inventory movements, and the OMS as the system responsible for order orchestration and customer promises.

Approach and Solution

Northstar introduced an OMS connected to the ERP through APIs and to the warehouses through middleware. A governed product and location master was created. Warehouse receipts, picks, and dispatches generated events that updated inventory and order status. Carrier APIs supplied shipment creation and tracking information. EDI was retained for major suppliers that already used standardized purchase orders and advance shipment notices.

The implementation began with one warehouse and a limited product category. Testing included duplicate messages, delayed carrier responses, partial shipments, returns, and financial reconciliation. A control dashboard monitored failed interfaces, inventory mismatches, and orders requiring manual intervention.

Outcome

The integrated process gave customer-service staff a common order view and enabled more realistic delivery promises. Manual order entry decreased, invoice exceptions became easier to trace, and warehouse and finance teams used consistent transaction identifiers. The project did not eliminate all problems: supplier data quality and carrier outages continued to require management. Nevertheless, the staged approach produced operational benefits without forcing an immediate replacement of every application.

Learning Points

The case illustrates that integration should be designed around business processes, authoritative data, and exception handling. It also demonstrates the value of hybrid architecture and incremental implementation. A technically successful interface would not have solved Northstar’s problem without agreement on data definitions and responsibility.

Risks, Limitations, and Common Mistakes

Integration projects commonly fail when organizations automate an inefficient process without redesigning it. Other mistakes include treating master data as a technical afterthought, allowing uncontrolled point-to-point connections, ignoring external partner capability, and measuring interface completion rather than business value.

Data synchronization does not guarantee data accuracy. A wrong product code can be propagated across every connected application. Real-time integration can also create false confidence: a current status may still be incomplete, estimated, or based on an unverified event. Systems may disagree because of timing, different business rules, or failed messages. Reconciliation processes are therefore essential.

Cybersecurity risks include credential theft, insecure APIs, excessive privileges, unpatched middleware, malicious message injection, and ransomware affecting connected partners. Availability risks arise when a central integration service fails or when an external carrier API becomes unavailable. Organizations need redundancy where justified, queues for temporary outages, recovery procedures, supplier contingency plans, and tested backups.

There are also organizational risks. Departments may resist shared data because visibility changes accountability. Employees may bypass formal systems when interfaces are slow or inconvenient. Integration can increase surveillance of workers or suppliers if event data is used without proportionality and transparency. Project governance must therefore address change management, training, role clarity, and responsible use of information.

Governance, Ethics, and Regulatory Considerations

Enterprise integration involves personal, commercial, and sometimes sensitive operational data. Customer addresses, contact details, employee information, shipment contents, pricing, and supplier performance should be collected and shared according to applicable law and contractual authority. Privacy principles include purpose limitation, data minimization, accuracy, retention control, and secure processing.

Organizations should define accountability when an automated decision causes harm. If a system allocates scarce inventory, rejects a supplier, changes a delivery promise, or flags a customer as risky, affected parties may require explanation, review, or correction. AI-supported decisions should be monitored for bias, unstable performance, and inappropriate reliance on historical patterns.

Auditability is important in logistics and finance. Organizations should preserve relevant transaction histories, approvals, changes, and evidence of delivery or receipt. Compliance requirements vary by jurisdiction and industry, so integration design should involve legal, compliance, security, and records-management specialists rather than relying solely on software teams.

Emerging Directions and Best Practices

Cloud-based platforms are making integration capabilities more accessible, but cloud adoption does not remove the need for architecture and governance. API marketplaces, event streaming, digital twins, collaborative control towers, and industry data spaces are expanding the ways supply-chain participants exchange information. IoT devices increasingly provide condition and location data, while AI tools support prediction and exception prioritization.

A digital twin may combine physical assets, transactions, and operational events to represent a logistics network for simulation and monitoring. Its usefulness depends on timely, trusted data and clearly defined decisions. Blockchain or distributed-ledger applications may assist selected traceability or provenance requirements, but they do not automatically ensure that the original data entered into the ledger was truthful.

Sound practice rests on several principles: begin with measurable business outcomes; simplify processes before integrating them; establish master-data ownership; use standards where they genuinely improve interoperability; design for exceptions and outages; protect data by default; monitor both technical and business performance; involve partners early; and retire unused interfaces. Integration should be treated as a continuing capability, not a one-time project.

Chapter Summary

Enterprise systems connect logistics transactions, processes, and decisions across internal functions and external partners. ERP provides a transactional and financial backbone, while SCM, OMS, procurement, CRM, warehouse, transport, and financial systems address complementary needs. Integration creates an end-to-end process view such as order-to-cash or procure-to-pay.

EDI is effective for standardized business documents, APIs support interactive services, middleware manages transformation and governance, and event-driven architecture enables responsive, loosely coupled processes. Most mature logistics environments combine these approaches. Successful integration depends on master-data quality, system-of-record decisions, interoperability, security, governance, testing, and partner agreements. Benefits include improved visibility, more reliable customer promises, better control, and stronger analytics, but risks include cyberattack, propagation of inaccurate data, excessive complexity, privacy violations, and organizational resistance. Emerging cloud, IoT, event-streaming, digital-twin, and AI capabilities increase opportunity while making disciplined governance more important.

Key Terms

ERP: An integrated system supporting core organizational transactions and resources.

SCM system: An application supporting planning, coordination, and execution across a supply chain.

Order management system: A system that coordinates orders from capture through fulfillment, delivery, returns, and settlement.

Procure-to-pay: The process from identifying a purchase requirement through supplier payment.

Order-to-cash: The process from customer order through fulfillment, invoicing, and payment.

Master data: Relatively stable data about products, customers, suppliers, locations, and related entities.

Transactional data: Records of business events such as orders, receipts, shipments, and invoices.

System of record: The authoritative application or source for a defined data domain.

Interoperability: The ability of systems to exchange and meaningfully use information.

EDI: Standardized computer-to-computer exchange of business documents.

API: A defined interface enabling one application to request data or services from another.

Middleware: Software that connects applications and manages routing, transformation, and communication.

Event-driven architecture: An architecture in which systems publish and respond to significant state changes.

Synchronous communication: Communication requiring an immediate response.

Asynchronous communication: Communication allowing sender and receiver to operate independently.

Orchestration: Central coordination of activities in a distributed process.

Choreography: Decentralized coordination in which services react to shared events.

Data governance: Policies and responsibilities governing data quality, access, use, and accountability.

Integration latency: The delay between an operational event and its availability in another system.

Three-way matching: Comparison of a purchase order, goods receipt, and supplier invoice.

Review Questions

Short Answer Questions

1. What role does ERP play in logistics integration?

2. Distinguish master data from transactional data and give one logistics example of each.

3. What is the purpose of an advance shipment notice?

4. Define an API and identify one logistics use for it.

5. Why is a system of record important in an integrated environment?

Long Answer Questions

1. Explain how ERP, SCM, OMS, procurement, CRM, and financial systems contribute to an integrated logistics process.

2. Compare EDI, APIs, middleware, and event-driven architecture in terms of purpose, strengths, and limitations.

3. Discuss the organizational and technical requirements for effective cross-organizational information sharing.

4. Explain how data governance and cybersecurity influence enterprise integration decisions.

5. Evaluate the claim that replacing all existing systems with one platform is the best solution to integration problems.

Analytical / Application Questions

1. A retailer’s website promises inventory that is physically present but already allocated to other orders. Diagnose the integration and data-governance causes and propose a solution.

2. A manufacturer wants real-time temperature alerts from contracted carriers but must continue receiving formal invoices through established channels. Recommend an integration architecture and justify it.

3. An integrated system repeatedly generates duplicate invoices after a network outage. Analyze the likely technical and process causes and design controls to prevent recurrence.

22. Multiple Choice Questions with Answers

Question 1

Which system is primarily responsible for coordinating a customer order from capture through fulfillment, delivery, and returns?

A. Order management system

B. General ledger

C. Human resource system

D. Supplier quality database

Correct Answer: A. Order management system

Question 2

A company wants to compare a purchase order, goods receipt, and supplier invoice before payment. Which control is being applied?

A. Demand sensing

B. Three-way matching

C. Event choreography

D. Customer segmentation

Correct Answer: B. Three-way matching

Question 3

Which integration method is most associated with standardized computer-to-computer exchange of formal business documents?

A. EDI

B. Computer vision

C. Manual spreadsheet entry

D. Digital twin simulation

Correct Answer: A. EDI

Question 4

A carrier exposes a service allowing a logistics platform to request a quotation and create a shipment immediately. Which technology most directly supports this interaction?

A. API

B. Master-data catalogue

C. Batch financial close

D. Paper-based workflow

Correct Answer: A. API

Question 5

In an event-driven architecture, what would most likely trigger inventory and customer-status updates?

A. A published event such as “shipment dispatched”

B. An annual financial audit

C. A manually printed catalogue

D. A staff holiday schedule

Correct Answer: A. A published event such as “shipment dispatched”

Question 6

Why is identifying a system of record important in enterprise integration?

A. It eliminates the need for cybersecurity controls

B. It establishes an authoritative source for a data domain

C. It guarantees that all data is correct

D. It prevents any system from using copied data

Correct Answer: B. It establishes an authoritative source for a data domain

Question 7

A logistics firm connects every application directly to every other application, creating many fragile dependencies. Which architectural problem does this illustrate?

A. Excessive point-to-point integration

B. Insufficient customer segmentation

C. Overuse of three-way matching

D. Lack of physical inventory

Correct Answer: A. Excessive point-to-point integration

Question 8

Which situation is most suitable for asynchronous communication?

A. A system must continue processing shipment events even when a consumer is temporarily unavailable

B. A user must receive an immediate credit approval before placing an order

C. A cashier must confirm a payment before issuing a receipt

D. A warehouse operator must receive an instant authorization response

Correct Answer: A. A system must continue processing shipment events even when a consumer is temporarily unavailable

Question 9

Northstar Distribution finds that its ERP and warehouse system use different units of measure for the same product. What should be addressed first?

A. Master-data governance and standardization

B. Increasing the number of carrier contracts

C. Removing all audit trails

D. Disabling inventory events

Correct Answer: A. Master-data governance and standardization

Question 10

Which principle best reflects responsible cross-organizational information sharing?

A. Give every partner unrestricted access to all internal data

B. Share the minimum necessary information under defined governance rules

C. Avoid documenting data ownership

D. Treat data quality as solely the receiver’s responsibility

Correct Answer: B. Share the minimum necessary information under defined governance rules