Enterprise Systems and the SCM Application Landscape

Introduction

Supply chain management (SCM) depends on coordinated decisions across suppliers, factories, warehouses, transportation networks, channels, and customers. Each participant generates data and performs activities that influence the performance of the entire network. Enterprise software provides the digital infrastructure for coordinating these activities, but the application landscape is not a single system. It is an ecosystem of specialized platforms with different purposes, data structures, decision horizons, and users.

A common managerial error is to treat all SCM applications as interchangeable. An enterprise resource planning system may record a purchase order, but it is not necessarily the best tool for optimizing a transport plan. A warehouse management system may direct picking and replenishment, but it does not replace a manufacturing execution system or a customer order management platform. Effective digital supply chains therefore require architectural clarity: managers must understand what each application does, which system owns particular data, how applications exchange information, and where analytical or artificial-intelligence capabilities should be placed.

This chapter distinguishes the major classes of SCM software: enterprise resource planning (ERP), advanced planning and scheduling (APS), warehouse management systems (WMS), transportation management systems (TMS), order management systems (OMS), manufacturing execution systems (MES), supplier relationship management (SRM), procurement platforms, product lifecycle management (PLM), and control-tower platforms. It also introduces four useful roles in an enterprise architecture: systems of record, systems of planning, systems of engagement, and systems of intelligence.

Learning Objectives

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

1. Explain the purpose and boundaries of major SCM application categories.
2. Distinguish transactional execution from planning, engagement, and intelligence capabilities.
3. Identify systems of record and evaluate ownership of supply-chain master data.
4. Describe how ERP, APS, WMS, TMS, OMS, MES, SRM, procurement, PLM, and control-tower platforms interact.
5. Analyze integration, governance, implementation, and organizational risks.
6. Recommend an application architecture for a supply-chain problem and justify the recommendation.

1. From Functional Applications to Enterprise Architecture

Early business systems were commonly organized around functions such as finance, purchasing, inventory, production, and sales. Functional systems improved local efficiency but often created fragmented information. A purchasing department might maintain supplier data independently from accounts payable; a warehouse might use a separate inventory file from the sales department; and manufacturing might schedule production without visibility of transportation constraints.

Enterprise systems emerged to connect these functions through shared databases, common processes, and standardized controls. The central idea is not merely automation. It is the creation of a consistent transaction record across organizational boundaries. For example, a sales order can trigger availability checking, a production requirement, a warehouse allocation, a shipment, an invoice, and a financial posting.

Modern SCM architectures are usually layered rather than monolithic. A typical architecture includes:

• Transactional core: records orders, receipts, inventory movements, invoices, and financial postings.
• Planning layer: evaluates demand, capacity, inventory, materials, and network alternatives.
• Execution layer: directs physical work in factories, warehouses, and transportation operations.
• Engagement layer: connects employees, suppliers, carriers, customers, and partners.
• Intelligence layer: monitors performance, detects exceptions, predicts outcomes, and supports decisions.

These layers overlap in commercial products. An ERP vendor may offer planning, procurement, and analytics modules, while a specialist vendor may offer a deeper WMS, TMS, or APS. The practical question is therefore not simply “Which software category is best?” but “Which application should perform which capability, and how will the capabilities be governed as one system?”

2. Systems of Record, Planning, Engagement, and Intelligence

Systems of record

A system of record is the authoritative application for a defined class of business transactions or master data. Authority is specific rather than universal. An ERP may be the system of record for financial postings and legal inventory valuation, while a WMS is the operational system of record for bin-level locations and task confirmations. A PLM system may own engineering revisions, even though the ERP stores the production item number.

A system of record should provide identifiable ownership, controlled updates, auditability, time stamps, and reconciliation procedures. Replicating data into a data warehouse does not transfer ownership. Similarly, a dashboard is not a system of record merely because executives use it.

Systems of planning

Systems of planning transform data into feasible or desirable future actions. Planning applications work with forecasts, constraints, policies, scenarios, and optimization or simulation methods. Their outputs may include a production plan, purchase recommendations, deployment quantities, transport plans, or labor schedules.

Planning systems are often decoupled from transactional systems because planning requires alternative scenarios and may need to evaluate plans that have not yet been executed. Once a decision is approved, relevant results are released to execution systems, where actual events are recorded.

Systems of engagement

Systems of engagement facilitate interaction among people and organizations. Supplier portals, customer order portals, carrier tendering networks, procurement marketplaces, and collaboration workspaces are examples. They may initiate transactions, but their primary value is communication, participation, workflow, and visibility.

Engagement systems create governance questions. A supplier may update a confirmation in a portal, but the enterprise must determine whether the portal, ERP, or procurement system is authoritative. Clear ownership prevents conflicting dates, quantities, and statuses.

Systems of intelligence

Systems of intelligence aggregate data, apply analytics, and support interpretation or action. Business-intelligence platforms, control towers, data platforms, machine-learning services, and optimization engines may belong to this category. Intelligence systems are not automatically accurate: their results depend on data quality, model assumptions, event latency, and appropriate human oversight.

A useful distinction is between descriptive intelligence, which explains what happened; diagnostic intelligence, which investigates why it happened; predictive intelligence, which estimates what may happen; and prescriptive intelligence, which recommends what should be done.

3. Enterprise Resource Planning

ERP is the transactional backbone of many organizations. Core ERP capabilities commonly include general ledger, accounts payable and receivable, purchasing, sales orders, inventory, bills of material, production orders, costing, and human-resource processes. ERP integrates commercial, operational, and financial transactions so that the organization can operate from a common process model.

In SCM, ERP commonly performs the following functions:

• creation and maintenance of item, location, supplier, and customer records;
• purchase orders, sales orders, transfer orders, and production orders;
• inventory balances at a defined level of detail;
• material requirements planning in basic or moderate forms;
• financial valuation, invoicing, and compliance reporting;
• transaction history and audit trails.

ERP is strong at controlled transactions and cross-functional integration. It is not always the strongest environment for highly granular warehouse tasks, complex multi-echelon optimization, real-time carrier execution, or detailed machine control. Organizations therefore extend ERP with specialist applications while preserving integration and data governance.

An important distinction is between available inventory and physically observed inventory. ERP may show the book balance, while WMS records detailed movements and locations. Reconciliation is required because timing differences, damaged stock, unrecorded movements, and counting errors can create discrepancies.

4. Advanced Planning and Scheduling

APS platforms support medium- and short-term planning under constraints. They may address demand planning, supply planning, inventory positioning, production scheduling, distribution planning, and sales and operations planning or integrated business planning.

Traditional planning may use deterministic rules, such as reorder points, lot-sizing policies, or material requirements planning. APS extends these approaches through finite-capacity scheduling, constraint propagation, scenario analysis, optimization, and multi-echelon modeling.

A planning model can be represented conceptually as:

Here, x represents decisions such as production quantities, shipment quantities, or inventory allocations; f(x) is the objective function, such as cost or lateness; g(x) ≤ 0 represents inequality constraints such as capacity limits; and h(x) = 0 represents equality constraints such as material balance. The formulation is only useful when data, assumptions, and objective priorities are credible. A mathematically optimal plan based on inaccurate lead times may be operationally poor.

APS differs from ERP primarily in purpose and time orientation. ERP records what has been ordered, produced, received, and paid for. APS explores what should be done next, often across multiple possible futures. The plan must subsequently be released to ERP, MES, WMS, or TMS for execution.

5. Warehouse Management Systems

A WMS controls and coordinates warehouse operations at a level of detail below the general inventory ledger. Core capabilities include receiving, put-away, location management, replenishment, picking, packing, cycle counting, wave or batch planning, labor assignment, and shipping confirmation.

WMS logic may use rules based on product dimensions, storage compatibility, turnover, expiration date, lot, serial number, or customer priority. In highly automated facilities, the WMS exchanges messages with material-handling equipment, warehouse-control systems, conveyors, sorters, autonomous mobile robots, and scanners.

The WMS is often the operational authority for:

• the physical location of a stock-keeping unit;
• the status of a license plate, pallet, carton, lot, or serial number;
• task assignment and confirmation;
• detailed quantity and condition information.

The ERP may remain authoritative for financial inventory and order commitments. This division requires disciplined interfaces. A receipt should not be financially posted before the physical event is appropriately confirmed, unless the enterprise has explicitly defined an accrual or expected-receipt process.

6. Transportation Management Systems

A TMS supports the planning, execution, monitoring, and settlement of freight. Functions can include shipment consolidation, carrier selection, route and mode planning, tendering, appointment scheduling, freight rating, tracking, freight audit, and payment support.

The TMS typically receives demand from orders, deliveries, or warehouse releases. It may then create loads, assign carriers, transmit tenders, receive acceptance or rejection, and capture status events such as departure, arrival, delay, and proof of delivery.

TMS value depends strongly on accurate constraints and commercial rules. A plan that minimizes transport cost may increase transit time, handling risk, emissions, or stockout exposure. Consequently, transport decisions should be evaluated against service, cost, resilience, and sustainability objectives rather than freight cost alone.

7. Order Management Systems

An OMS coordinates the lifecycle of customer demand, especially in omnichannel and direct-to-consumer environments. It may receive orders from web stores, marketplaces, call centers, retail channels, and business-to-business interfaces. It then validates orders, determines sourcing, promises dates, manages holds, coordinates fulfillment, and supports returns or cancellations.

The OMS is especially valuable when inventory is distributed across stores, fulfillment centers, drop-ship suppliers, and third-party logistics providers. It can apply sourcing rules such as proximity, available-to-promise quantity, margin, delivery commitment, or split-shipment avoidance.

OMS, ERP, and WMS have distinct roles. The OMS manages the customer-facing order journey and sourcing decision; ERP may manage the commercial and financial transaction; WMS executes fulfillment. Poorly designed architectures can create duplicate orders, contradictory statuses, or inaccurate promises.

8. Manufacturing Execution Systems

MES connects production planning with physical manufacturing. It may manage dispatch lists, work instructions, electronic batch records, labor reporting, quality checks, genealogy, downtime, and real-time production status. MES often interfaces with supervisory control and data acquisition systems, programmable logic controllers, sensors, and production equipment.

ERP usually defines production orders, bills of material, routings, and financial consequences. MES determines and records how work is performed on the shop floor. This distinction is essential in regulated or quality-sensitive industries, where traceability may require a detailed record of materials, operators, equipment, process conditions, and inspections.

MES data can improve planning, but data integration must account for different time scales. Machine events may occur in seconds, while ERP transactions may be posted in minutes or hours. Event timestamps, sequence logic, and exception handling are therefore central design concerns.

9. Supplier Relationship Management and Procurement Platforms

SRM concerns the structured management of supplier relationships, performance, risk, collaboration, segmentation, and development. Procurement platforms support processes such as requisitioning, sourcing events, quotation comparison, contract management, catalog buying, purchase-order collaboration, and invoice matching.

The terms are related but not identical. Procurement focuses on acquiring goods and services under approved commercial processes. SRM takes a broader relationship view, including strategic suppliers, joint improvement, innovation, risk, and performance governance.

Typical procurement controls include approval limits, segregation of duties, approved supplier lists, contract compliance, and three-way matching among purchase order, receipt, and invoice. Automation can reduce processing time, but it cannot replace judgment about supplier capability, continuity risk, ethical conduct, or total cost.

Supplier portals are systems of engagement, while the procurement or ERP platform may remain the system of record for purchase orders and invoices. Integration should preserve version control for prices, delivery dates, specifications, and commitments.

10. Product Lifecycle Management

PLM manages product information from concept and design through engineering change, release, production, service, and retirement. It commonly includes computer-aided design integration, product structures, specifications, document management, requirements, configurations, and engineering change control.

PLM is especially important where product complexity, regulatory traceability, or frequent engineering changes creates risk. A product design may evolve through several revisions before an approved manufacturing bill of material is released to ERP and MES.

PLM and ERP must be connected without confusing engineering and manufacturing structures. PLM may own the design bill of material, while ERP owns the manufacturing or costing bill of material. Change governance must define when a revision becomes effective, which orders are affected, and how obsolete material is controlled.

11. Control Towers and Supply-Chain Intelligence

A control tower is a visibility and decision-support capability that brings together data from multiple systems and partners. It typically provides event monitoring, alerts, exception management, impact analysis, collaboration, and sometimes scenario simulation or automated recommendations.

A control tower is not simply a dashboard. A dashboard reports indicators; a control tower connects events to business context and workflows. For example, a delayed vessel may be linked to affected purchase orders, production requirements, customer orders, inventory exposure, alternative transport options, and responsible users.

Control towers face three recurring challenges. First, data may arrive at different speeds and with inconsistent identifiers. Second, an alert may be technically correct but operationally irrelevant if it lacks impact analysis. Third, recommendations may fail if users cannot execute them in the underlying ERP, TMS, WMS, or supplier network.

Artificial intelligence can support anomaly detection, estimated-time-of-arrival prediction, demand sensing, document extraction, and recommendation ranking. However, organizations should establish model monitoring, explanation standards, access controls, bias testing where relevant, and human override procedures. AI should augment accountable decision making rather than obscure responsibility.

12. How the Applications Fit Together

Consider a simplified order-to-delivery flow. The OMS receives an order and determines a fulfillment source. ERP records the commercial order and financial implications. APS may evaluate supply or replenishment requirements. WMS allocates, picks, packs, and confirms the shipment. TMS plans and monitors transport. The customer and carrier interact through engagement channels. A control tower aggregates events and highlights exceptions. If the product is manufactured, MES records production execution, while PLM provides the approved product definition.

The same physical item may therefore appear in many systems, but with different meanings. In PLM it may be an engineering revision; in ERP it may be a sellable or manufacturable item; in WMS it may be a lot-controlled stock unit; in TMS it may be part of a shipment; and in OMS it may be a customer-order line. Integration must preserve context rather than merely copy fields.

A practical architecture should specify:

1. the owner of each master-data object;
2. the owner of each transaction and status;
3. the event or message that triggers downstream action;
4. the acceptable latency and error-handling method;
5. reconciliation and audit procedures;
6. the process for changing interfaces and data definitions.

13. Integration and Data Governance

Integration may use application programming interfaces, event streaming, electronic data interchange, file exchange, middleware, or enterprise service buses. No method is universally superior. Real-time interfaces are useful when immediate action matters, while batch integration may be sufficient for periodic financial or planning updates.

Important data objects include items, locations, suppliers, customers, units of measure, calendars, bills of material, routings, inventory, orders, shipments, and status events. Governance should address naming, validation, duplicate prevention, reference data, retention, access, and stewardship.

A useful principle is “enter once, use many times,” but this does not mean that every application must store identical data. Instead, the organization should define a golden source, controlled replicas, and synchronization rules. Data quality can be considered across dimensions such as accuracy, completeness, timeliness, consistency, uniqueness, and fitness for purpose.

Security is also architectural. Role-based access, least privilege, multifactor authentication, encryption, segregation of duties, logging, and supplier-access controls reduce operational and compliance risk. Cybersecurity incidents in one connected application can interrupt the entire supply chain; resilience therefore requires recovery objectives, backup testing, alternative procedures, and incident-response exercises.

14. Implementation and Managerial Implications

Software implementation is a socio-technical change, not merely an information-technology project. Processes, incentives, authority, skills, data, and physical operations must change together. Common implementation strategies include a global template, a phased rollout, a best-of-breed landscape, or a hybrid approach.

A single integrated suite may reduce interface complexity and provide consistent governance, but it may offer less depth in specialized operations. Best-of-breed applications may provide superior functionality but increase integration, skills, licensing, and upgrade complexity. The appropriate choice depends on strategic differentiation, operational complexity, regulatory requirements, partner connectivity, and organizational capability.

Managers should evaluate total cost of ownership, including licenses, implementation, integration, migration, testing, training, process redesign, support, cybersecurity, upgrades, and data governance. Benefits should be tied to measurable outcomes such as order-cycle time, inventory accuracy, schedule adherence, on-time delivery, procurement compliance, warehouse productivity, or forecast-bias reduction.

Implementation risks include excessive customization, unclear process ownership, poor master data, inadequate testing of exceptions, weak user adoption, and failure to define the future operating model. A technically successful go-live can still fail if planners do not trust the forecasts, warehouse workers cannot use the interface, or suppliers are not prepared to exchange required data.

15. Illustrative Case: Northstar Home Appliances

Background

Northstar Home Appliances is a fictional regional manufacturer and omnichannel distributor. It sells refrigerators and small appliances through dealers, its website, and major marketplaces. Its ERP contains finance, purchasing, production orders, and inventory balances. A separate WMS operates the main distribution center, while transport is managed through spreadsheets and carrier email.

Problem

Customers frequently receive late delivery promises. The sales channel sees inventory that is not immediately available because stock is allocated to other orders or awaiting quality release. Production planners lack reliable information about warehouse demand, and transportation staff consolidate shipments manually. Supplier confirmations are recorded inconsistently, making material shortages difficult to detect.

Analysis

The problem is not simply a lack of software. It is a combination of unclear ownership and disconnected processes. The OMS capability is weak, so customer promises are made from incomplete inventory information. The WMS has detailed physical data, but its statuses are not consistently communicated to ERP. Procurement engagement is informal, and there is no structured exception view across orders, production, suppliers, and transport.

Approach and solution

Northstar first defines data ownership. ERP remains the financial and commercial system of record; WMS owns bin-level inventory and task execution; PLM owns engineering revisions; and a procurement platform owns supplier collaboration events while approved purchase orders remain synchronized with ERP. The company then implements an OMS to centralize order capture, sourcing, and available-to-promise logic. A TMS is introduced for load planning, tendering, and tracking. Finally, a control-tower layer aggregates order, inventory, supplier, production, and transport events.

The company does not begin with complex AI. It first improves item identifiers, location codes, inventory-status definitions, and event timestamps. It establishes exception rules for late supplier confirmation, production delay, inventory discrepancy, and transport delay. Users are trained on the new decision rights: the OMS determines customer sourcing, the WMS confirms physical execution, and the control tower prioritizes cross-functional exceptions.

Outcome

After stabilization, Northstar reduces duplicate order handling, improves the reliability of customer promises, and gives managers a common view of delayed orders and their consequences. The principal improvement comes from process and data integration rather than from a single advanced algorithm. Once reliable event data is available, Northstar can evaluate predictive arrival models and more sophisticated inventory-allocation policies.

Learning points

The case illustrates five principles. First, application categories should be assigned clear responsibilities. Second, system integration cannot compensate for undefined data ownership. Third, customer-facing promise logic must reflect physical execution constraints. Fourth, visibility is valuable only when connected to action. Fifth, advanced analytics should follow basic process and data discipline, not substitute for it.

16. Challenges, Limitations, and Contemporary Developments

Enterprise application landscapes create complexity as well as capability. Vendor acquisitions can alter product road maps. Cloud subscriptions may simplify infrastructure but introduce dependence on provider availability, release schedules, and data-location policies. Integration platforms can multiply interfaces if architecture is not governed. Organizations may also accumulate overlapping applications after mergers or local implementations.

Contemporary developments include composable architectures, API-first integration, event-driven systems, digital twins, low-code workflow tools, embedded analytics, robotics, and generative AI assistants. These developments can improve responsiveness, but their value depends on process fit and governance. A digital twin that lacks current capacity and inventory data is only a simulation with weak operational credibility. A generative AI assistant that produces an attractive but unsupported explanation can create compliance and decision risk.

Environmental and social considerations are increasingly embedded in SCM applications. Systems may calculate transport emissions, support supplier due diligence, trace materials, and document labor or environmental certifications. Such functionality must be supported by reliable measurement boundaries and auditable evidence. Sustainability claims should not be inferred from incomplete data.

Ethically, supply-chain systems affect workers, suppliers, customers, and communities. Automated labor monitoring can become intrusive; supplier-risk scores can penalize smaller firms because of missing data; dynamic allocation can disadvantage certain customers; and opaque algorithms can make accountability difficult. Responsible governance requires proportional data collection, transparency, appeal mechanisms, privacy protection, and clear human responsibility.

Best-Practice Checklist

A graduate SCM professional should ask the following questions when assessing an application landscape:

• What business decision or transaction is the application intended to support?
• Which system is authoritative for each relevant data object?
• Is the capability primarily record keeping, planning, execution, engagement, or intelligence?
• What is the required data latency and acceptable failure behavior?
• How are exceptions escalated and resolved?
• Can the process be performed across organizational and partner boundaries?
• Are security, privacy, audit, and regulatory requirements addressed?
• Are users trained and accountable for the new process?
• Can benefits be measured through operational and financial outcomes?
• Does the architecture remain adaptable as products, channels, and partners change?

Chapter Summary

SCM software is an interconnected landscape rather than a single application. ERP usually provides the transactional and financial backbone. APS supports constrained planning and scenario analysis. WMS directs warehouse execution; TMS manages freight planning and movement; OMS coordinates customer orders and fulfillment sourcing; MES connects production planning with shop-floor execution; SRM and procurement platforms manage supplier relationships and purchasing processes; PLM controls product definitions and engineering change; and control towers combine visibility, exception management, and intelligence across systems.

The distinction between systems of record, planning, engagement, and intelligence clarifies both architecture and accountability. Successful integration requires explicit data ownership, reliable master data, appropriate event or batch interfaces, reconciliation, security, and user adoption. Advanced analytics and AI can improve prediction and decision support, but they cannot replace sound processes, trustworthy data, or accountable management. The central managerial task is to design a coherent operating model in which specialized applications work together to improve service, cost, resilience, compliance, and sustainability.

Key Terms

Advanced planning and scheduling (APS): Software that plans supply-chain activities under constraints such as capacity, materials, time, and demand.

Control tower: A cross-functional visibility and decision-support capability that monitors events, analyzes impact, and coordinates exceptions.

Enterprise resource planning (ERP): An integrated transactional system supporting enterprise processes such as finance, purchasing, inventory, sales, and production.

System of record: The authoritative application for a specified transaction or master-data object.

System of planning: An application that evaluates future actions, scenarios, constraints, and trade-offs.

System of engagement: A platform that supports interaction, collaboration, workflow, and participation by users or partners.

System of intelligence: A platform or capability that provides analytics, prediction, optimization, or decision recommendations.

Warehouse management system (WMS): Software that directs detailed warehouse inventory and operational tasks.

Transportation management system (TMS): Software for freight planning, tendering, tracking, rating, and settlement support.

Order management system (OMS): Software that coordinates order capture, sourcing, promising, fulfillment, and returns.

Manufacturing execution system (MES): Software that manages and records production-floor execution and traceability.

Supplier relationship management (SRM): The structured management of supplier performance, risk, collaboration, and development.

Procurement platform: Software supporting sourcing, requisitioning, purchasing, contracts, catalogs, and invoice-related controls.

Product lifecycle management (PLM): Software governing product information, revisions, engineering changes, and lifecycle processes.

Master data: Relatively stable data objects, such as items, locations, suppliers, customers, and units of measure.

Event-driven integration: An integration approach in which a business event triggers messages or actions in connected systems.

Available-to-promise: The quantity or delivery commitment that can be offered after considering supply, demand, allocations, and timing.

Finite-capacity planning: Planning that recognizes explicit limits on machines, labor, facilities, or other resources.

Data governance: Policies, roles, controls, and processes that ensure data quality, ownership, security, and appropriate use.

Review Questions

Short Answer Questions

1. What is the primary purpose of an ERP system in an SCM architecture?
2. How does a WMS differ from an ERP inventory module?
3. Define a system of record and give one SCM example.
4. What is the principal role of a control tower?
5. Why must PLM and ERP be integrated during engineering change processes?

Long Answer Questions

1. Compare ERP, APS, WMS, and TMS in terms of purpose, time horizon, users, and typical outputs.
2. Explain the differences among systems of record, planning, engagement, and intelligence, using an order-to-delivery process.
3. Discuss the benefits and risks of a best-of-breed SCM application architecture.
4. Explain why master-data governance is essential when multiple applications exchange supply-chain information.
5. Evaluate the role of AI in control-tower platforms and identify safeguards required for responsible use.

Analytical / Application Questions

1. A retailer has accurate financial inventory in ERP but frequent warehouse-location errors and late customer promises. Which applications and integration changes would you recommend, and why?
2. A manufacturer experiences material shortages despite having an APS system. Develop a diagnostic framework covering master data, supplier collaboration, planning assumptions, and execution feedback.
3. Design a high-level application architecture for an omnichannel company selling through stores, marketplaces, and its own website. Identify the likely system of record, planning, engagement, and intelligence capabilities for each major process.

Multiple Choice Questions with Answers

Question 1

Which application is most commonly the transactional and financial backbone of an enterprise supply chain?

A. Enterprise resource planning system

B. Transportation management system

C. Control-tower platform

D. Manufacturing execution system

Correct Answer: A. Enterprise resource planning system

Question 2

Which system normally directs detailed warehouse tasks such as put-away, picking, replenishment, and cycle counting?

A. APS

B. WMS

C. PLM

D. OMS

Correct Answer: B. WMS

Question 3

What is the defining characteristic of a system of record?

A. It produces the most attractive dashboard

B. It is the authoritative source for a specified transaction or data object

C. It always performs optimization

D. It is accessible only to senior executives

Correct Answer: B. It is the authoritative source for a specified transaction or data object

Question 4

Which application is primarily concerned with freight planning, carrier tendering, tracking, and freight settlement support?

A. TMS

B. SRM

C. MES

D. PLM

Correct Answer: A. TMS

Question 5

What is the principal purpose of an APS platform?

A. To record financial invoices only

B. To direct barcode scanning in a warehouse

C. To evaluate future supply-chain actions under constraints

D. To manage engineering drawings only

Correct Answer: C. To evaluate future supply-chain actions under constraints

Question 6

Which system coordinates customer order capture, fulfillment sourcing, promising, and returns in an omnichannel environment?

A. OMS

B. MES

C. WMS

D. SRM

Correct Answer: A. OMS

Question 7

Which application most directly connects production planning with shop-floor execution and traceability?

A. TMS

B. MES

C. OMS

D. Procurement platform

Correct Answer: B. MES

Question 8

Which statement best distinguishes SRM from procurement?

A. SRM focuses only on invoice printing

B. Procurement is unrelated to suppliers

C. SRM includes broader supplier performance, risk, collaboration, and development

D. SRM replaces all manufacturing systems

Correct Answer: C. SRM includes broader supplier performance, risk, collaboration, and development

Question 9

What is a central function of PLM?

A. Managing product definitions, revisions, and engineering changes

B. Routing delivery trucks in real time

C. Allocating warehouse picking tasks

D. Posting general-ledger entries only

Correct Answer: A. Managing product definitions, revisions, and engineering changes

Question 10

Why is a control tower more than a conventional dashboard?

A. It eliminates the need for transactional systems

B. It connects events to impact analysis, exceptions, collaboration, and possible action

C. It stores only historical financial data

D. It is used exclusively by suppliers

Correct Answer: B. It connects events to impact analysis, exceptions, collaboration, and possible action