Skip to Content

List of MM tables used in SPRO


I would like to know various MM tables used in SPRO configuration. Any document on SAP System Landscape overview tool will be very helpful.

Note : Please search forum or google it, before posting.

Edited by: Jeyakanthan A on May 26, 2011 10:26 PM

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 26, 2011 at 07:05 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 26, 2011 at 07:19 AM


    check this link[sap table |]


    Kailas ugale

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 26, 2011 at 07:21 AM


    Below are the tables of SAP MM in Configuration: Common Tables used in Materials Management Modules:

    EINA Purchasing Info Record- General Data

    EINE Purchasing Info Record- Purchasing Organization Data

    MAKT Material Descriptions

    MARA General Material Data

    MARC Plant Data for Material

    MARD Storage Location Data for Material

    MAST Material to BOM Link

    MBEW Material Valuation

    MKPF Header- Material Document

    MSEG Document Segment- Material

    MVER Material Consumption

    MVKE Sales Data for materials

    RKPF Document Header- Reservation

    T023 Mat. groups

    T024 Purchasing Groups

    T156 Movement Type

    T157H Help Texts for Movement Types

    MOFF Lists what views have not been created

    A501 Plant/Material

    EBAN Purchase Requisition

    EBKN Purchase Requisition Account Assignment

    EKAB Release Documentation

    EKBE History per Purchasing Document

    EKET Scheduling Agreement Schedule Lines

    EKKN Account Assignment in Purchasing Document

    EKKO Purchasing Document Header

    EKPO Purchasing Document Item

    IKPF Header- Physical Inventory Document

    ISEG Physical Inventory Document Items

    LFA1 Vendor Master (General section)

    LFB1 Vendor Master (Company Code)

    NRIV Number range intervals

    RESB Reservation/dependent requirements

    T161T Texts for Purchasing Document Types

    Following are the list of Important MM tables. Please check if its useful.

    Inventory Management:

    Material MSEG Material document / transaction details |



    Material document header information

    Material Stock Balances


    Material stock


    Material stock with valuation

    Sales Order Stock


    Stock balance with associated sales

    order data

    Stock Transport


    Index for Stock Transport Orders for



    Reading View of Stock Transport Ord. for

    Release Ord.

    Special Stocks | MKOL | Consignment, material provided to |

    vendor, etc.

    Material Master Data| Table | Description |

    | Materials | MARA | General Data, material type, group,

    | | | configurable & batch ind.

    | | MAKT | Short Texts, descriptions

    | | MARM | Conversion Factors

    | | MVKE | Sales Org, distribution channel

    | | MLAN | Sales data, tax indicator, tax

    | | MARC | classification

    | | MBEW | Plant Planning Data

    | | MLGN | Valuation Data

    | | MLGT | Warehouse Management Inventory Data

    | | MVER | Warehouse Management Storage Type

    | | MAPR | Data

    | | MARD | Consumption Data

    | | MCHA | Pointer for Forecast Data

    | | MCHB | Storage location data with stock

    | | | balances

    | | | Batches

    | | | Batch Stocks

    Please find all tables in MM-PUR (Purchasing) :

    EBAN - Purchase Requisition

    EBKN - Purchase Requisition Account Assignment

    EBUB - Index for Stock Transport Requisitions for Materi

    EINA - Purchasing Info Record: General Data

    EINE - Purchasing Info Record: Purchasing Organization D

    EIPA - Order Price History: Info Record

    EKAB - Release Documentation

    EKAN - Vendor Address: Purchasing Document

    EKBE - History per Purchasing Document

    EKBEH - Removed PO History Records

    EKBZ - History per Purchasing Document: Delivery Costs

    EKBZH - History per Purchasing Document: Delivery Costs

    EKEH - Scheduling Agreement Release Documentation

    EKEK - Header Data for Scheduling Agreement Releases

    EKES - Vendor Confirmations

    EKET - Scheduling Agreement Schedule Lines

    EKETH - Scheduling Agreement Schedules: History Tables

    EKKI - Purchasing Condition Index

    EKKN - Account Assignment in Purchasing Document

    EKKO - Purchasing Document Header

    EKPA - Partner Roles in Purchasing

    EKPB - "Material Provided" Item in Purchasing Document

    EKPO - Purchasing Document Item

    EKPV - Shipping-Specific Data on Stock Tfr. for Purch. D

    EKRS - ERS Procedure: Goods (Merchandise) Movements to b

    EKUB - Index for Stock Transport Orders for Material

    EORD - Purchasing Source List

    EQUK - Quota File: Header

    EQUP - Quota File: Item

    T024 - Purchasing Groups

    T024E - Purchasing Organizations

    T024W - Valid Purchasing Organizations for Plant

    T024Z - Purchasing Organizations

    T027A - Shipping Instructions, Purchasing

    T027B - Texts: Shipping Instructions

    T027C - Codes for Compliance with Shipping Instructions

    T027D - Compliance with Shipping Instructions: Texts

    T069 - Certificate Categories

    T069Q - Control Data for Source Determination and Checkin

    T069T - Certificate Categories: Text Description

    T160 - SAP Transaction Control, Purchasing

    T160B - SAP Transaction Control, List Displays, Purchasin

    T160C - SAP Transaction Control for List Displays in CALL

    T160D - Function Authorizations: Purchase Order

    T160E - Function Authorizations: Purchasing: Descriptions

    T160I - Control of Intrastat Reports

    T160J - Text Table for Intrastat Reports

    T160L - Scope of Purchasing Lists

    T160M - Message Control: Purchasing (System Messages)

    T160O - Description of Scope of List

    T160P - Entities Table Routines

    T160Q - Scope of List: Buyer's Negotiation Sheet: Routine

    T160R - Routines for Buyer's Negotiation Sheet

    T160S - Selection Parameters for Purchasing Lists

    T160T - Description of Selection Parameters

    T160V - Default Values for Purchasing

    T160W - Description for Default Values for Purchasing Ope

    T160X - Scope of List: Buyer's Negotiation Sheet

    T160Y - Scope of List: Buyer's Negotiation Sheet: Descrip

    T161 - Purchasing Document Types

    T161A - Linkage of Requisition Doc. Type to Purchasing Do

    T161B - Default Business Transaction Type for Import

    T161E - Release Codes

    T161F - Release Point Assignment for Purchase Requisition

    T161G - Release Prerequisite, Purchase Requisition

    T161H - Fields for Release Procedure, Purchase Requisitio

    T161I - Determination of Release Strategy

    T161M - Fine-Tuned Control: Message Types

    T161N - Message Determination Schemas: Assignment

    T161P - Check of Document Type, Document Category, Item C

    T161R - REORG Control, Purchasing

    T161S - Release Indicator, Purchase Requisition

    T161T - Texts for Purchasing Document Types

    T161U - Texts for Release Indicator

    T161V - Shipping-Specific Data for Stock Tfr. for Purch.

    T161W - Order Types for Stock Transfer

    T161Z - Additional Checks for Outline Agreements on Reorg

    T162 - Field Selection, Purchasing Document

    T162K - Field Selection, Account Assignment Fields, Purch

    T162T - Description of Field Selection Reference Key

    T162X - Description of Field Groups from T162/T162K

    T162Y - Groups: Field Selection

    T163 - Item Categories in Purchasing Document

    T163A - Check Item Category/Account Assignment Category

    T163B - Purchase Order History Categories

    T163C - Texts for Purchase Order History Categories

    T163D - Assignment Internal/External Confirmation Categor

    T163E - Confirmation Categories

    T163F - Confirmation Categories: Descriptions

    T163G - Confirmation Control

    T163I - Texts for Account Assignment Categories

    T163K - Account Assignment Categories in Purchasing Docum

    T163KS - Assignment of Tax Indicator to Account Assignment

    T163L - Confirmation Control Keys

    T163M - Confirmation Control Keys: Description

    T163P - Release Creation Profile

    T163S - Description for Release Creation Profile

    T163X - "Zombie" T163X

    T163Y - Texts for Item Categories

    T165K - Copying Options: Header Texts

    T165P - Copying Options: Item texts

    T166A - Supplement Text in Purchasing Document Printouts

    T166C - Print-Relevant Purchasing Document Changes

    T166K - Header Texts in Purchasing Document Printouts

    T166P - Item Texts in Purchasing Document Printouts

    T166T - Change Texts in Purchasing Document Printouts

    T166U - Headings in Purchasing Document Printout

    T167 - Number Range Management for Purchasing Master Dat

    T167T - Transaction Description

    T168 - Screen Control, Purchasing

    T168F - Function Codes, Purchasing

    T168T - Screen Titles

    T16FB - Release Indicators: Purchasing Document

    T16FC - Release Codes

    T16FD - Description of Release Codes

    T16FE - Descriptions of Release Indicators: Purchasing Do

    T16FG - Release Groups

    T16FH - Descriptions of Release Groups

    T16FK - Release Statuses

    T16FS - Release Strategies


    System landscape in another......

    Hope this will help you.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 26, 2011 at 07:23 AM

    System Landscape:

    Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD.

    - DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.

    - QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training.

    - PROD may have something like a 200 Production.

    These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.

    Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).

    You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.

    But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.

    The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.

    In summary:

    Landscape : is the arrangement for the servers

    IDES : is purely for education purpose and is NOT INCLUDED in the landscape.



    DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.

    QUALITY : is where the core team members and other members test the customization.

    PRODUCTION : is where the live data of the company is recorded.

    A request will flow from Dev->Qual->Prod and not backwards.

    1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process.

    2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.

    3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production.

    These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.

    Presentaion Server- Where SAP GUI have.

    Application Server - Where SAP Installed.

    Database Server - Where Database installed.

    What is the meaning of "R" in R/3 systems?

    R/3 stands for realtime three tier architecture. This is the kind of architrecture SAP R/3 system has.

    R/3 means three layers are installed in Different system/server and they are connected with each other.

    1) Presentation

    2) Application

    3) Database

    Why do we call client 000 as golden client?

    Golden client contains all the configuration data and master data so some extent. All the configuration settings are done in golden clients and then moved to other clients. Hence this client acts as a master record for all transaction settings, hence the name "Golden Client"

    Hope this helps you.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.