EINA table — Purchasing Info Record General Data

One row in EINA represents a single vendor-material combination at the purchasing info record level, independent of purchasing organization. It is created the moment an info record is maintained for a vendor and a material, either manually or automatically from a purchase order line that has no existing info record. EINA carries the data that does not vary by purchasing organization: which vendor supplies which material, the vendor's own material number, the material group, the order unit, and administrative fields like creation date and deletion flag. It does not carry price, so a row existing in EINA only proves that the vendor-material relationship exists somewhere in the system, not that it is priced or usable in a specific purchasing organization or plant.

MANDT is always the first restriction in any custom read. EINA has one row per vendor-material combination system-wide, so it is not a huge table compared to EKPO or MSEG, but selecting on MATNR alone across a large vendor base still returns more rows than expected if the material is sourced from many suppliers. Restrict on LIFNR and MATNR together when checking a specific relationship. Do not filter on plant or purchasing organization here, that data does not exist in EINA and any attempt to join on it will silently return nothing or force an unintended cross join with EINE.

Symptom: a purchase order line will not adopt a price and the buyer says 'there should be an info record for this vendor and material'. Select EINA where LIFNR equals the vendor and MATNR equals the material. If no row returns, no info record exists at all and the fix is creating one, not chasing pricing conditions. If a row returns, take its INFNR and check EINE for that INFNR restricted to the purchasing organization on the PO. A missing EINE row for that org, with EINA present, is the actual cause.

EINA remains a physical table in S/4HANA and continues to be maintained by the standard info record transactions. It has not been absorbed into a merged table the way some MM tables have. Reporting and app layers increasingly read purchasing info record data through CDS views rather than direct table access, but the underlying persistence and field layout of EINA are unchanged from the classic model.

Purchasing master data is owned by procurement, specifically the buyer or purchasing group responsible for the vendor-material relationship. When a price or org-availability question comes up, the first stop is the buyer maintaining the info record, not the vendor master or pricing team, since the org-specific piece sits in EINE and is a purchasing decision.

EINE is the direct counterpart holding org-specific price and condition data, maintained by the same info record transactions. LFA1 supplies the vendor master, MARA the material master. EORD, the source list, frequently points back to an EINA-EINE pair as the preferred source of supply. EKPO carries INFNR when a purchase order line was created with reference to an info record.