SAP Source List Table Guide: EORD Fields, Keys, and Purchasing Checks

August 31, 2026 admin

A single incorrect date in the SAP EORD table can stop a million-dollar production line cold. While many beginners view the Source List as just another administrative screen, it actually functions as the gatekeeper for every automated purchase order in the system. If the data here is wrong, the supply chain breaks, and the business loses money because a vendor was blocked or a contract expired without anyone noticing.

The EORD table stores the rules for where a company buys its materials. It tells SAP which suppliers are allowed, which ones are forbidden, and which one is the “favorite” for a specific warehouse. Think of it like a digital whitelist that prevents buyers from making expensive mistakes by ordering from the wrong person at the highest price.

The reader will find that mastering these fields is not about memorizing technical codes. It is about understanding the logic that prevents procurement delays and keeps stock moving across international borders. This guide explains how specific fields control the flow of goods and why an auditor will look at this table first when things go wrong.

Pro tip: Always check the “Fixed Source” indicator in EORD before running automated replenishment (MRP), or the system might ignore your preferred vendor entirely.

The following sections break down the essential table keys and purchasing checks. They cover everything from validity dates that act like expiration stickers to the plant-specific rules that ensure a factory in France doesn’t accidentally order parts from a supplier meant only for a warehouse in Dubai. By the end, a user will know exactly which fields to audit to keep a global supply chain running smoothly.

Why EORD Is More Than Just a Table

The SAP EORD table functions as the central nervous system for procurement, dictating exactly which vendors are permitted to supply specific materials to a business. It is not merely a static list of names; it is a dynamic control mechanism that links materials to vendors and purchasing organizations. This connection ensures that every time a buyer creates a document, the system already knows the “who, where, and when” of the transaction.

When a procurement professional triggers a purchase requisition, the EORD table steps in to automate vendor selection. This automation removes the guesswork from the process, allowing the system to pick the right source based on pre-defined corporate strategies. Without this logic, every single order would require manual intervention, increasing the risk of human error and inconsistent pricing.

Driving Efficiency Through Automation

Automation in SAP is only as good as the underlying data. The EORD table acts as a gatekeeper for automated purchase orders, ensuring that procurement follows the rules set by the management team. By maintaining these records accurately, a company can avoid the chaos of buying from unapproved suppliers or using outdated pricing agreements.

The system relies on this table to bridge the gap between high-level material data-often found in the MARC table in SAP-and the actual execution of a buy. While other tables might define how a material is stored, EORD defines how it is acquired. It is the difference between having a part in a warehouse and knowing exactly which partner to call when the shelf is empty.

The Risks of Neglecting Source Data

Ignoring the setup of the EORD table creates hidden risks that often surface at the worst possible moment. A missing or incorrect entry can lead to a complete halt in automated processing. If the system cannot find a valid source, it stops the requisition, forcing a manual review that wastes time and resources.

Strategic Compliance: It ensures buyers use preferred vendors that have negotiated volume discounts.
Audit Readiness: It provides a clear trail of which vendors were authorized for specific periods.
Operational Continuity: It prevents orders from being sent to vendors who are no longer in business or are under performance review.
Data Integrity: It works alongside the material group table in SAP to maintain a clean procurement hierarchy.

The strategic importance of EORD is most visible in global deployments. In these environments, consistent procurement across different regions depends on centralized sourcing rules. A single oversight in this table can lead to millions in lost savings because the system defaulted to a more expensive, non-contracted vendor. Mastering the specific fields within this table is the only way to prevent these costly disruptions.

Four primary database fields in the EORD table dictate whether a purchase order succeeds or fails at the point of entry. These technical keys-Material, Plant, Source List Record, and Item-serve as the unique identifiers that prevent the system from confusing one procurement rule with another. While the Material and Plant fields link the record to the Material Master table in SAP, the real control lies in how the user configures the vendor and purchasing organization assignments.

The Foundational Linkage Fields

The Material and Plant fields are the non-negotiable anchors of every entry. In my experience with global rollouts, a common error involves assuming a source list for a material in one plant automatically applies to another. It does not; SAP treats each plant as an independent entity, meaning a vendor approved for a site in Strasbourg might be entirely restricted for a facility in Dubai.

The Vendor (LIFNR) and Purchasing Organization (EKORG) fields complete the logic. The Purchasing Organization field is particularly sensitive because it defines the legal and commercial framework of the buy. If the vendor is not extended to the specific purchasing organization listed in the EORD entry, the system will trigger a hard error during the requisition process, stalling the entire procurement run.

Control Flags: Fixed and Blocked Sources

Beyond the basic identifiers, two specific indicators-Fixed Source (KZFIX) and Blocked Source (BLOCKED)-act as the manual overrides for automation. The Fixed Source flag tells the system to prioritize one specific vendor over all others when multiple valid contracts exist. This is the primary tool for enforcing volume commitments with preferred partners.

Fixed Source (KZFIX): When checked, this vendor becomes the “first choice” for automated sourcing suggestions.
Blocked Source (BLOCKED): This acts as an immediate kill-switch, preventing any buyer from placing an order with the vendor for that specific material, regardless of contract status.
Validity Start/End: These date fields define the lifespan of the record, ensuring that old pricing or expired agreements don’t leak into new orders.

Pro Tip: Use the Blocked Source flag instead of deleting EORD rows; this preserves the audit trail of why a vendor was disqualified while instantly stopping unauthorized spending.

In high-velocity environments like SAP Retail, these fields are the only thing standing between a clean supply chain and a data nightmare. If the validity dates are off by even twenty-four hours, the system might default to a non-contracted vendor, leading to price variances that erode profit margins. This sensitivity to timing makes the management of start and end dates a high-stakes task for any data steward.

Ensuring Supply Chain Continuity Through Accurate Timing

A buyer at a global fashion retailer attempts to convert a purchase requisition for a seasonal jacket, only to be met with a “No Source Found” error. The material is active, the vendor is ready, but the system remains paralyzed because the validity period on the record expired at midnight. These validity dates act as a hard stop for SAP procurement logic; if the current date sits even one second outside the defined range, the automation breaks entirely.

Managing these dates requires more than just setting them to the distant future. Overlapping periods for the same material and plant create ambiguity in source determination, forcing the system to guess or fail when it needs to decide which vendor takes priority. When people create and manage SAP Retail articles, they often forget that the source list must evolve alongside the product lifecycle.

Avoiding the Fixed Source Trap

The Fixed Source (KZFIX) indicator is a powerful tool that tells SAP to ignore all other options and stick to one specific partner. While this provides stability for strategic partnerships, using it as a “set and forget” toggle often leads to single-source dependency. If a buyer marks a vendor as fixed but that vendor suddenly faces a strike or a raw material shortage, the system will continue trying to route orders there until a human intervenes.

Align Dates with Contracts – Synchronize the start and end dates in the EORD table with your legal purchasing agreements. This prevents the system from ordering at old prices or under expired terms.
Audit Overlapping Windows – Run regular reports to find materials with multiple active records for the same period. Ambiguous dates cause the system to ignore your preferred logic and can lead to random vendor selection.
Use Fixed Sources Sparingly – Reserve the KZFIX flag for high-volume, predictable items where you have a guaranteed capacity agreement. For everything else, let the system evaluate the best source based on current data.
Monitor Expiring Records – Set up alerts or SAP Retail queries to identify records expiring in the next thirty days. Proactive updates prevent the “No Source Found” errors that halt warehouse intake.

Misusing these controls doesn’t just create a minor IT ticket; it stops the flow of goods. I once saw a beauty care giant lose a week of production because a single “Fixed Source” indicator was left on a vendor that had gone bankrupt months prior. The system refused to look at the three other perfectly valid backups because it was told that only one mattered. This type of rigid configuration is exactly what later sections on Blocked Sources and compliance auditing aim to solve by introducing more nuanced layers of control.

Securing Supply Chains with Blocked Sources and Localized Rules

Relying on a single global procurement strategy often ignores the reality that what works for a warehouse in France might fail for a distribution center in South Africa. SAP allows for this granularity by treating each plant as a distinct entity within the EORD table. This means a procurement lead can authorize a specific vendor for one location while strictly forbidding them at another, ensuring that regional constraints or logistics costs do not compromise the broader supply chain.

The Strategic Use of the Blocked Source Flag

The Blocked Source (BLOCKED) indicator functions as a digital restraining order within the system. When this flag is active, SAP prevents any purchase orders or requisitions from being generated for that specific material and vendor combination at the designated plant. It is a hard stop that overrides other sourcing logic, effectively “blacklisting” the supplier for a set period.

In my experience as a consultant, this field is the primary tool for managing vendor non-compliance. If a supplier fails a series of quality inspections or breaches a contract, the BLOCKED flag ensures no buyer accidentally places a new order. It is far more effective than deleting the record entirely, as it maintains a historical trail of why the vendor was excluded and prevents them from being automatically re-selected by the system’s sourcing logic.

Managing Plant-Specific Sourcing Logic

Global organizations frequently encounter scenarios where a material is available from a multinational vendor, yet local regulations or transport costs make a regional supplier more attractive. By utilizing plant-specific entries, a company can tailor its localized vendor strategies. This allows Plant A to prioritize a nearby supplier to reduce lead times, while Plant B uses a different partner better suited to its specific storage capabilities.

This localized control is essential for those who want to learn SAP Retail or manage complex FMCG environments. It prevents a “one size fits all” approach that often leads to shipping inefficiencies. Without these plant-level distinctions, the system would struggle to handle the nuances of regional procurement, potentially forcing a plant to buy from a vendor that cannot legally or physically service that territory.

Key Considerations for Local vs. Global Sourcing

Quality Control: Use the blocked flag immediately upon receiving a failed quality audit report to stop incoming shipments.
Contractual Boundaries: Ensure that plant-specific records reflect the legal geographical limits of your supplier agreements.
Redundancy Planning: Maintain secondary, non-fixed sources for each plant to avoid total shutdowns if a primary local vendor fails.
Data Integrity: Periodically verify that a block at one plant should not also be applied to other plants using the same vendor.

While these localized settings provide immense control, they also create a massive amount of data that must be managed. When hundreds of plants have unique rules for thousands of materials, the risk of “dirty data” or outdated blocks increases exponentially. Maintaining this level of detail requires more than just initial configuration; it demands a systematic approach to verifying that every entry still aligns with current corporate purchasing policies and legal requirements.

Auditing EORD for Purchasing Compliance

Clean data is the only barrier between a smooth supply chain and a total warehouse standstill. After setting up complex procurement rules, the reader must realize that these records are not “set and forget” assets. Without regular oversight, the database quickly fills with digital debris that triggers unexpected order failures.

Auditing the source list ensures that every entry still aligns with current business goals. I have seen massive retail operations grind to a halt because an old record was left active, forcing the system to pick a supplier that no longer existed. Regular data integrity checks prevent these ghost entries from sabotaging your automation.

Essential Audit Checkpoints

A thorough audit focuses on identifying records that contradict current reality. Users should look for entries where the business logic has shifted but the system remains stuck in the past. This process is vital for maintaining purchasing efficiency and avoiding compliance risks during external audits.

Expired Records: Identify lines where the timeframe has lapsed, leaving the material without a valid procurement path.
Hidden Fixed Sources: Locate materials where a single vendor is still marked as the primary choice despite new contracts being signed.
Block Consistency: Ensure that vendors restricted in the global vendor master are also correctly restricted within specific plant lists.
Duplicate Logic: Search for multiple active entries for the same material that might cause the system to pick the wrong partner.

Tools for Data Rectification

While manual spot checks work for small batches, global implementations require a more aggressive approach. My experience in SAP MM and MDG (Master Data Governance) shows that custom SAP queries are often the most effective way to pull large datasets for review. By extracting the table data into a spreadsheet, you can quickly highlight anomalies that the standard interface hides.

Audit Focus	Detection Method	Required Action
Outdated Vendors	Cross-reference with Vendor Master	Delete or update record
Logic Conflicts	Search for multiple “Fixed” indicators	Uncheck secondary sources
Compliance Gaps	Filter by “Blocked” status	Align with procurement policy

Effective auditing transforms the source list from a static table into a dynamic tool for compliance. Identifying and rectifying these common errors before they hit the production environment saves hours of troubleshooting. Managing these records requires constant vigilance to ensure the system reflects the actual physical supply chain accurately.

Mastering the Source List to Protect the Supply Chain

The SAP Source List (EORD) acts as the primary gatekeeper for every purchase order created in the system. When a user manages this table correctly, the business avoids the chaos of ordering from the wrong vendor or using expired contracts. If the data in EORD is wrong, the supply chain breaks, leading to delayed shipments and wasted capital.

Critical Takeaways for System Stability

Validity dates are non-negotiable. A single day of overlap or a gap in the EORD table can stop a buyer from placing a critical order during a peak season.
The “Fixed Source” indicator prevents human error. This field ensures that the system automatically picks the preferred vendor, removing the risk of a junior buyer choosing a more expensive or unverified supplier.
Blocked sources provide instant compliance. Marking a vendor as blocked in the EORD table is the fastest way to stop all procurement activities for a specific material at a specific plant without deleting entire master data records.
Plant-level control is mandatory. Because EORD is plant-specific, a vendor might be perfect for a warehouse in France but completely invalid for a site in South Africa due to logistics or legal constraints.

Immediate Actions for Reliable Purchasing

The reader should run transaction SE16N for table EORD today to check for entries with past expiration dates. Identifying these dead records is the first step in cleaning up a messy procurement system. They should also verify that every “Fixed” source aligns with the current legal contracts held by the purchasing department.

Regular audits of the EORD table turn a reactive supply chain into a proactive one. High-performing companies do not wait for an error message at checkout to fix their data. They treat the source list as a living document that requires constant precision to keep the business moving.

Mastering EORD fields is the difference between a system that works and one that costs millions in manual fixes.