Vendor Specific EAN Assignments - Cockpit

SAP plant (WERKS in T001W) represents an organizational unit where materials are stored, produced, or processed. In IS Retail, plants typically correspond to distribution centers or central warehouses. WERKS in MLEA indicates which specific plant location this vendor-specific EAN applies to, enabling precise receiving and inventory tracking at the plant level.

VEND_EAN_CAT is a retail-specific classification that indicates the role or priority of a vendor-specific EAN. Common categories include 'P1' (primary inbound barcode used for receiving), 'S1' (secondary barcode for stock checks), and 'PR' (promotional barcode). This field allows retailers to track multiple EAN assignments per vendor-article-plant combination and identify which EAN is preferred for which process (receiving, POS, stock count).

SAP client is a self-contained logical area with separate master data, configuration, and transaction data. In a migration context, MANDT identifies which client instance the MLEA record belongs to and is typically set to the target migration client for all rows.

ERDAT is a system-maintained audit timestamp indicating when the vendor-specific EAN assignment was first created. It is automatically set by SAP at record insertion and is not typically updated on subsequent changes. Used for audit trails, reporting, and compliance purposes.

ERNAM is a system-maintained audit field that records the user ID or service account responsible for creating the MLEA record. Used for audit trails, change tracking, and compliance. If ERDAT is populated, ERNAM should also be populated to indicate who created the record.