# SAP Tables for Plant, Country, Project and Business Partner > Source: https://netray.co/tools/sap-plant-country-project-partner-tables-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Look up the SAP table behind a plant, country, project or partner, with key fields and the join you need next. ## Category sap ## Erp SAP ## Audience - SAP analyst - SAP developer - BI developer ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Object **Key:** object **Type:** text #### Table **Key:** table **Type:** text #### What it stores **Key:** desc **Type:** text #### Key / link fields **Key:** keys **Type:** text #### How to use it **Key:** tip **Type:** text **Rows:** **Object:** Plant **Table:** T001W **Desc:** Plants and branches (the plant master) **Keys:** WERKS **Tip:** Start here to check a plant. NAME1 is the name, BWKEY the valuation area, LAND1 and REGIO the location. **Object:** Plant **Table:** T001K **Desc:** Valuation area, links plant to company code **Keys:** BWKEY, BUKRS **Tip:** Join T001W-BWKEY to T001K-BWKEY to find the company code of a plant. **Object:** Plant **Table:** T001L **Desc:** Storage locations per plant **Keys:** WERKS, LGORT **Tip:** List all storage locations of a plant with WERKS. **Object:** Plant **Table:** T001 **Desc:** Company codes **Keys:** BUKRS **Tip:** BUTXT is the name, WAERS the company code currency, LAND1 the country. **Object:** Plant **Table:** T024W **Desc:** Purchasing organization assigned to plant **Keys:** WERKS, EKORG **Tip:** Shows which purchasing organizations can buy for a plant. **Object:** Plant **Table:** T024E **Desc:** Purchasing organizations **Keys:** EKORG **Tip:** EKOTX holds the description. **Object:** Plant **Table:** T024 **Desc:** Purchasing groups **Keys:** EKGRP **Tip:** Buyer groups, not linked to a plant. **Object:** Plant **Table:** TVKWZ **Desc:** Allowed plants per sales organization and distribution channel **Keys:** VKORG, VTWEG, WERKS **Tip:** Check which plants can deliver for a sales area. **Object:** Plant **Table:** TVSWZ **Desc:** Shipping points allowed per plant **Keys:** VSTEL, WERKS **Tip:** Join to TVST for shipping point names. **Object:** Country **Table:** T005 **Desc:** Countries (country master) **Keys:** LAND1 **Tip:** LAND1 is the 2 character code, WAERS the country currency, SPRAS the default language. **Object:** Country **Table:** T005T **Desc:** Country names and nationality texts **Keys:** SPRAS, LAND1 **Tip:** LANDX has the country name. Filter SPRAS = 'E' for English. **Object:** Country **Table:** T005S **Desc:** Regions (states, provinces) per country **Keys:** LAND1, BLAND **Tip:** Region codes used in addresses and tax determination. **Object:** Country **Table:** T005U **Desc:** Region names **Keys:** SPRAS, LAND1, BLAND **Tip:** BEZEI is the region name text. **Object:** Country **Table:** ADRC **Desc:** Central address data (plants, partners, customers, vendors) **Keys:** ADDRNUMBER, DATE_FROM, NATION **Tip:** COUNTRY, REGION, CITY1 and POST_CODE1 hold the actual address. Plant address number is T001W-ADRNR. **Object:** Country **Table:** TCURC **Desc:** Currency codes **Keys:** WAERS **Tip:** Pair with TCURR for exchange rates. **Object:** Country **Table:** T002 **Desc:** Language keys **Keys:** SPRAS **Tip:** Internal one character language key to ISO mapping. **Object:** Country **Table:** T006 **Desc:** Units of measure **Keys:** MSEHI **Tip:** Internal unit codes, texts in T006A. **Object:** Project **Table:** PROJ **Desc:** Project definition **Keys:** PSPNR (internal), PSPID **Tip:** PSPID is the external project ID users see. OBJNR links to status tables. **Object:** Project **Table:** PRPS **Desc:** WBS elements **Keys:** PSPNR (internal), POSID **Tip:** POSID is the external WBS number. PSPHI points to the project in PROJ-PSPNR. **Object:** Project **Table:** PRHI **Desc:** WBS hierarchy **Keys:** POSNR, PSPHI **Tip:** UP, DOWN, LEFT and RIGHT hold the tree structure of WBS elements. **Object:** Project **Table:** JEST **Desc:** Individual object status (system and user statuses) **Keys:** OBJNR, STAT **Tip:** Use PROJ-OBJNR or PRPS-OBJNR. Active status has INACT blank. Texts in TJ02T. **Object:** Project **Table:** TJ02T **Desc:** System status texts **Keys:** ISTAT, SPRAS **Tip:** TXT04 is the short code (REL, CLSD), TXT30 the description. **Object:** Project **Table:** AFVC **Desc:** Network activities, linked to WBS **Keys:** AUFPL, APLZL **Tip:** PROJN holds the WBS element internal number for the activity. **Object:** Project **Table:** AUFK **Desc:** Order master, includes networks **Keys:** AUFNR **Tip:** Networks have AUTYP = '20'. PSPEL on the order links to the WBS. **Object:** Project **Table:** MSPR **Desc:** Project stock **Keys:** MATNR, WERKS, LGORT, CHARG, SOBKZ, PSPNR **Tip:** Stock assigned to a WBS element (special stock Q). **Object:** Project **Table:** EKKN **Desc:** Purchase order account assignment **Keys:** EBELN, EBELP, ZEKKN **Tip:** PS_PSP_PNR links a PO item to a WBS element. **Object:** Project **Table:** COEP **Desc:** CO line items (actual and plan costs by object) **Keys:** KOKRS, BELNR, BUZEI **Tip:** OBJNR of the WBS gives costs. In S/4HANA the same postings are also in ACDOCA. **Object:** Partner **Table:** BUT000 **Desc:** Business partner general data **Keys:** PARTNER **Tip:** NAME_ORG1 for organizations, NAME_LAST and NAME_FIRST for persons. TYPE: 1 person, 2 organization, 3 group. **Object:** Partner **Table:** BUT100 **Desc:** Business partner roles **Keys:** PARTNER, RLTYP **Tip:** Customer role FLCU00 or FLCU01, vendor role FLVN00 or FLVN01. **Object:** Partner **Table:** BUT020 **Desc:** Partner to address link **Keys:** PARTNER, ADDRNUMBER **Tip:** Join ADDRNUMBER to ADRC for the address. **Object:** Partner **Table:** BUT0ID **Desc:** Partner identification numbers **Keys:** PARTNER, TYPE, IDNUMBER **Tip:** Tax numbers and other IDs stored per type. **Object:** Partner **Table:** BUT050 **Desc:** Business partner relationships **Keys:** RELNR, PARTNER1, PARTNER2, RELTYP **Tip:** Contact person to company links. **Object:** Partner **Table:** CVI_CUST_LINK **Desc:** Link between business partner and customer **Keys:** PARTNER_GUID, CUSTOMER **Tip:** Map BUT000-PARTNER_GUID to KNA1-KUNNR. **Object:** Partner **Table:** CVI_VEND_LINK **Desc:** Link between business partner and vendor **Keys:** PARTNER_GUID, VENDOR **Tip:** Map BUT000-PARTNER_GUID to LFA1-LIFNR. **Object:** Partner **Table:** KNA1 **Desc:** Customer master, general data **Keys:** KUNNR **Tip:** NAME1, LAND1, ORT01. Sales data in KNVV, company code data in KNB1. **Object:** Partner **Table:** LFA1 **Desc:** Vendor master, general data **Keys:** LIFNR **Tip:** Purchasing data in LFM1 (by EKORG), company code data in LFB1. **Object:** Partner **Table:** KNVV **Desc:** Customer master, sales area data **Keys:** KUNNR, VKORG, VTWEG, SPART **Tip:** Payment terms, shipping conditions and pricing data per sales area. **Object:** Partner **Table:** LFM1 **Desc:** Vendor master, purchasing organization data **Keys:** LIFNR, EKORG **Tip:** Order currency, payment terms and incoterms per purchasing organization. **Object:** Partner **Table:** KNVP **Desc:** Customer master partner functions **Keys:** KUNNR, VKORG, VTWEG, SPART, PARVW, PARZA **Tip:** Sold-to, ship-to, bill-to, payer assignments. **Object:** Partner **Table:** VBPA **Desc:** Sales document partners **Keys:** VBELN, POSNR, PARVW **Tip:** Partners as copied into a sales order. KUNNR holds the customer. **Object:** Partner **Table:** EKPA **Desc:** Purchasing document partner functions **Keys:** EBELN, EKORG, PARVW, PARZA **Tip:** Partners on a purchase order, such as ordering address or invoicing party. **Object:** Partner **Table:** TPAR **Desc:** Partner function definitions **Keys:** PARVW **Tip:** Texts in TPART. Explains codes like AG, WE, RE, RG. **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to look up a plant, country, project or partner **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is the table to check a plant in SAP? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms table to check plant in sap, sap plant table T001W, table for country in sap, sap country table T005, table sap project, sap project table PROJ PRPS, table sap partner, sap business partner table BUT000 --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json