Вы находитесь на странице: 1из 5

Getting Started New sletters


Welcome, Guest



Search the Community

Products Industries Lines of Business

Services & Support Training & Education University Alliances

About SCN Partnership Events & Webinars

Downloads Developer Center Innovation

Activity Brow se Communications Actions


4 Replies Latest reply: May 26, 2011 9:24 AM by S Katta


subha chakrapani

May 26, 2011 7:00 PM

List of MM tables used in SPRO

This question is Assumed Answered. Hi 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

8680 View s

Average User Rating (0 ratings)

Manish Kumar Agarwal May 26, 2011 9:05 AM (in response to subha chakrapani) Re: List of MM tables used in SPRO Hi, The below links may help you : http://www.sap-img.com/materials/all-the-tables-in-sap-mm-purchasing.htm http://www.sap-img.com/materials/common-tables-used-by-sap-mm.htm

Like (0)

kailas ugale May 26, 2011 9:19 AM (in response to subha chakrapani) Re: List of MM tables used in SPRO Hi check this link[sap table |http://www.scribd.com/doc/454570/Total-SAP-Tables] Regards Kailas ugale

Like (0)

S Katta May 26, 2011 9:37 AM (in response to subha chakrapani) Re: List of MM tables used in SPRO Hi, 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 | Document/Movements MKPF Material document header information Material Stock Balances MARD Material stock MBEW Material stock with valuation Sales Order Stock MSKA Stock balance with associated sales order data Stock Transport EKUB Index for Stock Transport Orders for MDUB Material Reading View of Stock Transport Ord. for Release Ord. Special Stocks vendor, etc. Material Master Data| Table | Materials | | | | | | | | | | | | | | | | | | Description | | 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 | MKOL | Consignment, material provided to |

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 EKET - Vendor Confirmations - 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 T069 - Compliance with Shipping Instructions: Texts - Certificate Categories

T069Q - Control Data for Source Determination and Checkin T069T - Certificate Categories: Text Description T160 T160B T160C T160D T160E T160I T160J - SAP Transaction Control, Purchasing - SAP Transaction Control, List Displays, Purchasin - SAP Transaction Control for List Displays in CALL - Function Authorizations: Purchase Order - Function Authorizations: Purchasing: Descriptions - Control of Intrastat Reports - 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 T160X T160Y T161 T161A T161B T161E T161F T161G T161H T161I T161M T161N T161P T161R T161S T161T T161U Description for Default Values for Purchasing Ope Scope of List: Buyer's Negotiation Sheet Scope of List: Buyer's Negotiation Sheet: Descrip Purchasing Document Types Linkage of Requisition Doc. Type to Purchasing Do Default Business Transaction Type for Import Release Codes Release Point Assignment for Purchase Requisition Release Prerequisite, Purchase Requisition

- Fields for Release Procedure, Purchase Requisitio - Determination of Release Strategy - Fine-Tuned Control: Message Types - Message Determination Schemas: Assignment Check of Document Type, Document Category, Item C REORG Control, Purchasing Release Indicator, Purchase Requisition Texts for Purchasing Document Types Texts for Release Indicator Shipping-Specific Data for Stock Tfr. for Purch. Order Types for Stock Transfer Additional Checks for Outline Agreements on Reorg Field Selection, Purchasing Document Field Selection, Account Assignment Fields, Purch Description of Field Selection Reference Key Description of Field Groups from T162/T162K Groups: Field Selection Item Categories in Purchasing Document

T161V T161W T161Z T162 T162K T162T T162X T162Y T163 -

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 T163I T163K T163KS T163L T163M T163P T163S T163X T163Y T165K T165P T166A Confirmation Control Texts for Account Assignment Categories Account Assignment Categories in Purchasing Docum Assignment of Tax Indicator to Account Assignment Confirmation Control Keys Confirmation Control Keys: Description Release Creation Profile Description for Release Creation Profile

- "Zombie" T163X - Texts for Item Categories - Copying Options: Header Texts - Copying Options: Item texts - 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 T167 T167T T168 T168F Headings in Purchasing Document Printout Number Range Management for Purchasing Master Dat Transaction Description Screen Control, Purchasing 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 & System landscape in another...... Hope this will help you. Regards, Sapsrin - Release Strategies

Like (0)

S Katta May 26, 2011 9:24 AM (in response to subha chakrapani) Re: List of MM tables used in SPRO 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 ---> QUALITY > PRODUCTION 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. Regards, Sapsrin

Like (0)


Site Index Privacy

Contact Us Terms of Use

SAP Help Portal Legal Disclosure


Follow SCN