SAP Purchasing Info Record Mass Upload Worksheet (ME11)
A purchasing info record stores the relationship between one vendor and one material: price, delivery time, tolerances and order unit. Migrating or refreshing hundreds of them is a common SAP MM task. This worksheet gives you a clean layout and instant value checks before you load.
| Vendor (LIFNR) | Material (MATNR) | Purch. org (EKORG) | Plant (WERKS) | Info record category (ESOKZ) | Net price (NETPR) | Price unit (PEINH) | Order price unit (BPRME) | Planned delivery time (days) | Expected annual quantity | Price per single unit | Expected annual value | Price valid to | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
$0 | $25,200 | ||||||||||||
$19 | $44,400 | ||||||||||||
$7 | $34,000 | ||||||||||||
$2 | $25,800 | ||||||||||||
$8 | $37,920 |
Info records live in tables EINA (general vendor material data) and EINE (purchasing organization data). Condition prices are stored through condition records. Check which fields your migration cockpit object, LSMW recording or BAPI expects. This sheet prepares and sanity checks the data and does not post anything to SAP.
Price data cleanup
Share an anonymised extract of your price data and we will flag unit errors and duplicates. Optional.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Replace the sample rows with your records: one row per vendor, material, organization and plant combination. Pick the info record category, then enter net price, price unit and order price unit. The sheet computes price per single unit and expected annual value, which makes outliers visible, for example a price entered per 1 that should be per 100. Export to Excel and use it as the upload source for the migration cockpit, a recording or a custom program.
Key fields and how SAP uses them
EINA holds data valid across organizations, such as vendor material number and order unit. EINE holds purchasing organization and plant data: net price, price unit (PEINH), planned delivery time (APLFZ), standard order quantity and tolerances. The price itself is held as a condition record, so a load must create the condition together with the record. The info record category decides whether the record is used for standard, subcontracting, pipeline or consignment procurement.
- Standard (0): normal purchase from the vendor
- Subcontracting (1): the vendor assembles with components you supply
- Pipeline (2): material is withdrawn from a pipeline and invoiced periodically
- Consignment (3): vendor owned stock at your site
Worked example
A fastener has a net price of 42 per price unit of 100 pieces. The sheet shows a price per single unit of 0.42 and with 60,000 pieces a year an expected annual value of 25,200. If a colleague typed 42 with a price unit of 1 by mistake, the sheet would show 2.52 million, a clear sign of an error you can catch before the upload. Use the average value summary to spot rows far above the typical.
Common mistakes
Price unit errors are the most expensive, followed by wrong order price unit conversions. Others include loading a record for a vendor not extended to the purchasing organization, mixing plant specific and organization level records for the same vendor and material, and ignoring validity dates on conditions so that old prices stay active. Always reconcile the loaded records with a SELECT on EINA and EINE or a report such as ME1M after the load.
Frequently Asked Questions
What are the main tables for info records in SAP?
EINA stores general data of the info record: vendor, material and order unit. EINE stores purchasing organization and plant specific data such as net price, planned delivery time and tolerances. Conditions for the price are stored in the condition tables, accessed through the record.
How can I mass upload info records in SAP?
Typical routes are the S/4HANA migration cockpit with a purchasing info record object, LSMW with a ME11 recording, or a program that calls standard BAPIs. Prepare the data in Excel, test on a few records, then load. Reconcile with ME1M afterwards.
What is the price unit in an info record?
It is the quantity that the net price refers to. A net price of 42 with a price unit of 100 means 42 per 100 pieces, or 0.42 each. The order price unit defines the unit of measure of that quantity and may differ from the base unit of the material.
Do I need an info record to create a purchase order?
No. A PO can be created without one, but then price and delivery time must be typed by the buyer. With an info record the system proposes them, and MRP can use it for source determination. Info records also feed price history and vendor evaluations.
If you are consolidating prices from several ERPs or spreadsheets into SAP info records, we can help validate the source data and map it to the right fields before the load.
Related Tools
SAP Source List Upload Template
Generate a tab separated source list upload file with the EORD fields for material, plant, vendor, validity and MRP usage.
SAPSAP Purchasing Document Types Reference
Searchable list of SAP purchasing document categories, standard document types, item categories and account assignment categories.
SAPSAP GR/IR Clearing Worksheet
Editable worksheet that computes the GR/IR balance per purchase order line from receipts and invoices, with ageing for month end clearing.
SAPSAP MRP Type Reference
Searchable list of SAP MRP types, lot sizing procedures, procurement types and special procurement keys used in the material master MRP views.
More SAP tools
See all- SAP Movement Types Reference
- SAP MIGO Goods Receipt Checklist
- SAP Release Strategy Design Template
- SAP Physical Inventory Count Sheet Template
- SAP Purchase Requisition Approval Form Template
- SAP Material Master Creation Request Form Template
- SAP Vendor Evaluation Scorecard Worksheet
- SAP Goods Receipt Discrepancy Report Template
- SAP Subcontracting Component Tracking Worksheet