SAP Tables for Plant, Country, Project and Business Partner
The table to check a plant in SAP is T001W. Country is T005 (names in T005T), project is PROJ for the definition and PRPS for WBS elements, and business partner is BUT000. This reference lists those and the tables you join next, with key fields and a tip for each.
| Object | Table | What it stores | Key / link fields | How to use it |
|---|---|---|---|---|
Plant | T001W | Plants and branches (the plant master) | WERKS | Start here to check a plant. NAME1 is the name, BWKEY the valuation area, LAND1 and REGIO the location. |
Plant | T001K | Valuation area, links plant to company code | BWKEY, BUKRS | Join T001W-BWKEY to T001K-BWKEY to find the company code of a plant. |
Plant | T001L | Storage locations per plant | WERKS, LGORT | List all storage locations of a plant with WERKS. |
Plant | T001 | Company codes | BUKRS | BUTXT is the name, WAERS the company code currency, LAND1 the country. |
Plant | T024W | Purchasing organization assigned to plant | WERKS, EKORG | Shows which purchasing organizations can buy for a plant. |
Plant | T024E | Purchasing organizations | EKORG | EKOTX holds the description. |
Plant | T024 | Purchasing groups | EKGRP | Buyer groups, not linked to a plant. |
Plant | TVKWZ | Allowed plants per sales organization and distribution channel | VKORG, VTWEG, WERKS | Check which plants can deliver for a sales area. |
Plant | TVSWZ | Shipping points allowed per plant | VSTEL, WERKS | Join to TVST for shipping point names. |
Country | T005 | Countries (country master) | LAND1 | LAND1 is the 2 character code, WAERS the country currency, SPRAS the default language. |
Country | T005T | Country names and nationality texts | SPRAS, LAND1 | LANDX has the country name. Filter SPRAS = 'E' for English. |
Country | T005S | Regions (states, provinces) per country | LAND1, BLAND | Region codes used in addresses and tax determination. |
Country | T005U | Region names | SPRAS, LAND1, BLAND | BEZEI is the region name text. |
Country | ADRC | Central address data (plants, partners, customers, vendors) | ADDRNUMBER, DATE_FROM, NATION | COUNTRY, REGION, CITY1 and POST_CODE1 hold the actual address. Plant address number is T001W-ADRNR. |
Country | TCURC | Currency codes | WAERS | Pair with TCURR for exchange rates. |
Country | T002 | Language keys | SPRAS | Internal one character language key to ISO mapping. |
Country | T006 | Units of measure | MSEHI | Internal unit codes, texts in T006A. |
Project | PROJ | Project definition | PSPNR (internal), PSPID | PSPID is the external project ID users see. OBJNR links to status tables. |
Project | PRPS | WBS elements | PSPNR (internal), POSID | POSID is the external WBS number. PSPHI points to the project in PROJ-PSPNR. |
Project | PRHI | WBS hierarchy | POSNR, PSPHI | UP, DOWN, LEFT and RIGHT hold the tree structure of WBS elements. |
Project | JEST | Individual object status (system and user statuses) | OBJNR, STAT | Use PROJ-OBJNR or PRPS-OBJNR. Active status has INACT blank. Texts in TJ02T. |
Project | TJ02T | System status texts | ISTAT, SPRAS | TXT04 is the short code (REL, CLSD), TXT30 the description. |
Project | AFVC | Network activities, linked to WBS | AUFPL, APLZL | PROJN holds the WBS element internal number for the activity. |
Project | AUFK | Order master, includes networks | AUFNR | Networks have AUTYP = '20'. PSPEL on the order links to the WBS. |
Project | MSPR | Project stock | MATNR, WERKS, LGORT, CHARG, SOBKZ, PSPNR | Stock assigned to a WBS element (special stock Q). |
Project | EKKN | Purchase order account assignment | EBELN, EBELP, ZEKKN | PS_PSP_PNR links a PO item to a WBS element. |
Project | COEP | CO line items (actual and plan costs by object) | KOKRS, BELNR, BUZEI | OBJNR of the WBS gives costs. In S/4HANA the same postings are also in ACDOCA. |
Partner | BUT000 | Business partner general data | PARTNER | NAME_ORG1 for organizations, NAME_LAST and NAME_FIRST for persons. TYPE: 1 person, 2 organization, 3 group. |
Partner | BUT100 | Business partner roles | PARTNER, RLTYP | Customer role FLCU00 or FLCU01, vendor role FLVN00 or FLVN01. |
Partner | BUT020 | Partner to address link | PARTNER, ADDRNUMBER | Join ADDRNUMBER to ADRC for the address. |
Partner | BUT0ID | Partner identification numbers | PARTNER, TYPE, IDNUMBER | Tax numbers and other IDs stored per type. |
Partner | BUT050 | Business partner relationships | RELNR, PARTNER1, PARTNER2, RELTYP | Contact person to company links. |
Partner | CVI_CUST_LINK | Link between business partner and customer | PARTNER_GUID, CUSTOMER | Map BUT000-PARTNER_GUID to KNA1-KUNNR. |
Partner | CVI_VEND_LINK | Link between business partner and vendor | PARTNER_GUID, VENDOR | Map BUT000-PARTNER_GUID to LFA1-LIFNR. |
Partner | KNA1 | Customer master, general data | KUNNR | NAME1, LAND1, ORT01. Sales data in KNVV, company code data in KNB1. |
Partner | LFA1 | Vendor master, general data | LIFNR | Purchasing data in LFM1 (by EKORG), company code data in LFB1. |
Partner | KNVV | Customer master, sales area data | KUNNR, VKORG, VTWEG, SPART | Payment terms, shipping conditions and pricing data per sales area. |
Partner | LFM1 | Vendor master, purchasing organization data | LIFNR, EKORG | Order currency, payment terms and incoterms per purchasing organization. |
Partner | KNVP | Customer master partner functions | KUNNR, VKORG, VTWEG, SPART, PARVW, PARZA | Sold-to, ship-to, bill-to, payer assignments. |
Partner | VBPA | Sales document partners | VBELN, POSNR, PARVW | Partners as copied into a sales order. KUNNR holds the customer. |
Partner | EKPA | Purchasing document partner functions | EBELN, EKORG, PARVW, PARZA | Partners on a purchase order, such as ordering address or invoicing party. |
Partner | TPAR | Partner function definitions | PARVW | Texts in TPART. Explains codes like AG, WE, RE, RG. |
Table names are standard SAP names; field lists show the fields most useful for lookups, not every column. Always check the table in SE11 on your release, and remember that S/4HANA uses business partner as the lead object for customers and vendors.
Ask SAP in plain language
Optional: see how a private AI layer can answer table and master data questions from your own SAP system, on-prem if you need it.
Optional. The tool and every export work without this. No spam.
How to look up a plant, country, project or partner
Filter the table above by object, or search for the table name, then open it in SE16N or SE11 in your system. For a plant, enter WERKS in T001W and read NAME1, BWKEY, LAND1 and ADRNR. To find which company code owns it, join BWKEY to T001K. For a country, read T005 with LAND1 and the texts from T005T where SPRAS is your logon language. For a project, enter the external project number in PROJ-PSPID, take PSPNR, and read the WBS elements in PRPS where PSPHI equals that PSPNR.
- Plant: T001W, then T001K for company code
- Country: T005 with T005T for texts
- Project: PROJ, then PRPS through PSPHI
- Partner: BUT000, with roles in BUT100
Internal versus external numbers
The most common mistake in project queries is using the external number where the internal one is stored. PROJ and PRPS both have PSPNR, a numeric internal key that is not what users see. Users type PSPID or POSID, and tables such as AFVC, MSPR and EKKN store the internal PSPNR. Convert with the PRPS or PROJ table, or in ABAP with the conversion exits. In SE16N this is why a WBS number filter often returns nothing until you pass the internal value or use the table with conversion exit applied.
Business partner versus customer and vendor tables
In ECC, customers and vendors lived in KNA1 and LFA1 only. In S/4HANA the business partner is the lead object, so BUT000 holds the master record and customer and vendor numbers are linked through CVI_CUST_LINK and CVI_VEND_LINK. In most S/4HANA systems the partner number and the customer number are the same value, but that is a setting you should confirm rather than assume. Roles in BUT100 tell you whether the partner can be used as a customer, a vendor, or both.
Common mistakes
Mixing up table scope is the usual source of wrong reports. T001W is client dependent and has only plant data; storage locations are in T001L, not on the plant. Country names are language dependent, so a join to T005T without a SPRAS filter doubles rows. Status of a project is never in PROJ itself; it is in JEST through OBJNR. Check the results against a known plant or project before using any query in a report.
Frequently Asked Questions
What is the table to check a plant in SAP?
T001W holds the plant master with the key WERKS. Use SE16N or SE11 to display it. The plant name is NAME1, the valuation area BWKEY and the address number ADRNR. For the company code, join BWKEY to table T001K.
Which SAP table has country data?
T005 is the country master with key LAND1. Country names are in T005T by language, regions in T005S and T005U, and currency codes in TCURC. Addresses store the country code in ADRC-COUNTRY.
What are the main SAP project tables?
PROJ holds the project definition and PRPS the WBS elements. PRHI stores the hierarchy, JEST the status, and AFVC links network activities to a WBS. Costs sit in COEP, and in S/4HANA also in ACDOCA. Remember PSPNR is the internal key.
Which table stores business partner data in SAP?
BUT000 holds general business partner data keyed by PARTNER. Roles are in BUT100, addresses link through BUT020 to ADRC, and the customer and vendor links are in CVI_CUST_LINK and CVI_VEND_LINK. KNA1 and LFA1 still hold the customer and vendor records.
If you spend time looking up tables for every question from the business, we can put a private AI layer over your SAP system so people can ask in plain language and see the query it ran. It can run on-prem.
Related Tools
SAP MM Tables and Key Fields Reference
Searchable list of the core SAP MM tables with their primary key fields and what each stores, including S/4HANA changes.
SAPSAP PP Database Tables Reference
A lookup of the main SAP PP database tables, what each holds and the key fields to join on.
SAPSAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)
Lookup of the main SAP SD tables with their key fields and what changed in S/4HANA. Search, then export to Excel or PDF.
SAPSAP FICO Database Tables Reference
A lookup of the standard finance and controlling tables used in reports, extracts and SE16N queries, with module and what each stores.
More SAP tools
See all- SAP ABAP Stock Below Safety Stock Report Generator
- SAP MM Fit-Gap Analysis Template with Examples
- SAP MM Standard Reports and Report T-Codes
- SAP Movement Types Reference
- SAP Purchasing Document Types Reference
- SAP MIGO Goods Receipt Checklist
- SAP GR/IR Clearing Worksheet
- SAP Release Strategy Design Template
- SAP Source List Upload Template
Keep exploring
Free tools
- SAP B1 Business Partner Master Data Request FormA fill-in request form for creating or changing a customer or vendor in SAP Business One, with the fields finance needs and an approval block.
- SAP S/4HANA Production Order Tables and Join SQL GeneratorGet the production order tables for S/4HANA and generate the join SQL for order headers, operations and components.
- SAP PP Database Tables ReferenceA lookup of the main SAP PP database tables, what each holds and the key fields to join on.
ERP fixes and how-tos
- SAP S/4HANA API Guide: Business Hub, OData, Public Cloud and Business PartnerA guide to SAP S/4HANA APIs: the Business Accelerator Hub, A2X OData, the Business Partner API, public cloud communication arrangements, PI/PO and Digital Manufacturing.
- SAP Business One tables list: the core tables and how the names workA practical list of core SAP Business One tables (OITM, OCRD, ORDR, OPOR, OWOR, OINM) with prefix conventions and safe query advice for reports.
- ERP AI: when to hire a partner versus build it in-houseA decision framework for CIOs on whether to hire an ERP AI implementation partner or build an internal AI capability, with staffing, cost, and timeline tradeoffs.
Runs with your ERP
- Solver BI360 and SAP Business One: reporting, budgeting and data warehousingHow Solver BI360 delivers reporting, budgeting, dashboards and a data warehouse for SAP Business One, what to check before buying, and where private AI helps.
- ECOSIRE Time and Attendance and SAP Business One: clock events to job costingHow ECOSIRE's time and attendance integration turns clock terminal events into hours, overtime and absence in SAP Business One, with setup, pitfalls and AI.
- Prometheus Planning & Scheduling with SAP Plant MaintenanceHow Prometheus Planning and Scheduling works with SAP Plant Maintenance work orders on S/4HANA and ECC: data flows, setup, pitfalls and a private AI layer.
Guides
- Selecting an AI Implementation Partner: Evaluation CriteriaSelecting an AI implementation partner: a weighted evaluation scorecard, reference-check questions, and why a pilot-first contract beats a big-bang one.
- ERP Implementation Project Plan TemplateDownload a proven ERP implementation project plan template with phase gates, milestones, and resource allocation. Reduce project risk with structured planning.
AI on your ERP
- How to Choose an ERP AI Implementation PartnerA CIO checklist for picking an ERP AI implementation partner: the architecture questions to ask, red flags, pricing models, and what to demand in the SOW.
- SAP AI Consulting for On-Prem and Private DeploymentsWhat to demand from an SAP AI consulting partner when data must stay on-prem or private: OData/BAPI mechanics, Joule vs. private LLM, and buyer questions.