topic Re: query in Application Development and Automation Discussions

query

Former Member — Tue, 13 Nov 2007 05:52:00 GMT

what is the flow of sd and mm

Re: query

former_member189629 — Tue, 13 Nov 2007 05:54:48 GMT

Hi Mudassir,

Link Between SAP SD, MM & FI

1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD :-

1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped

directly to your customer).

1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.

2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc. *-- Shahee

The link between SD and MM :-

1. When you create sales order in SD, all the details of the items are copied from Material master of MM.

2. MRP and availibility check related data is also taken from MM although you control this data in SD also.

3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.

4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.

There are many such links between SD and MM.

Now the link between SD and FI :-

1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.

Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.

2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI

3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM

SD Integration points with other modules

SD module is highly integrated with the other modules in SAP.

Sales Order –

Integration Points Module

•Availability Check - MM

•Credit Check - FI

•Costing - CO/ MM

•Tax Determination - FI

•Transfer of Requirements - PP/ MM

Delivery & Goods Issue –

Integration Points Module

•Availability Check - MM

•Credit Check - FI

•Reduces stock - MM

•Reduces Inventory $ - FI/ CO

•Requirement Eliminated - PP/ MM

Billing -

Integration Points Module

•Debit A/R - FI/ CO

•Credit Revenue - FI/ CO

•Updates G/ L - FI/ CO

(Tax, discounts, surcharges, etc.)

•Milestone Billing - PS

Return Delivery & Credit Memo -

Integration Points Module

•Increases Inventory - MM

•Updates G/ L - FI

•Credit Memo - FI

•Adjustment to A/R - FI

•Reduces Revenue - FI

Tips by: Subha

SD Transaction Code Flow:

Inquiry / Document type IN

Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP

Quotation / QT

Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP

Purchase Order PO

Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.

Sales Order OR

Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP

Delivery LF

Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS

Billing MN

Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP

To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no.

To create vendor tcode is

xk01(create), xk02(change) , xk03(display)

Tables are lfa1.

To create custmer tcode is xd01, xd02, xd03.

Table is kna1.

After creating sales order using this no we can create delivery note tcode is vl01.

Reward if helpful,

Karthik

Re: query

Former Member — Tue, 13 Nov 2007 05:55:53 GMT

SD FLOW

SD Flow Cycle and T Codes:

INQUIRY ( VA11)

QUOTATION (VA21)

PURCHASE ORDER (ME21)

ORDER CONFIRMATION (VA01)

PICKING LIST – (VL36)

PACKING LIST - (VL02, VL01)

SHIPPING – (VT01)

INVOICE – (VF21, VF01)

Explantion with relavent tables:

Enquiry - Customer enquires about the Products services that were sold by a company - VA11

Quotation - Company Gives a Quotation for the products and Services to a Customer

Sales Order - Customer gives a Purchase order to the company agaionst which a Sales order will be raised to Customer in SAP.

VBAK: Sales Document(Header Data) (VBELN)

VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)

Enquiry, Quotation, Sales Order are differentiated based on Doc.

Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,

for Quotation 'B' & for Order it is 'C'.)

Delivery(Picking, Packing, Post Goods Issue and Shipment)->

Company sends the material after picking it from Godown and Packing it in a Handling Unit(box) and Issues the goods

LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)

LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)

(LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)

Billing - Also company bills to the customer for those deliveries

And in FI against this billing Accounting doc is created.

VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)

VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)

(VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)

Apart from these tables there are lot of other tables which starts with

‘V’, but we use the following tables frequently.

Links for sd:

http://www.sapgenie.com/abap/tables_sd.htm

Please check this SD online documents.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCSD/CAARCSD.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_SD.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSD/BCBMTWFMSD.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOLISPLN/LOLISPLN.pdf

Also please check this SD links as well.

http://help.sap.com/saphelp_47x200/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm

http://www.sap-basis-abap.com/sapsd.htm

http://www.sap-img.com/sap-sd.htm

http://www.sapgenie.com/abap/tables_sd.htm

http://searchsap.techtarget.com/featuredTopic/0,290042,sid21_gci961718,00.html

http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html

All help ebooks are in PDF format here

http://www.easymarketplace.de/online-pdfs.php

MM Cycle:

Purchase Requisition-> Staff in an orgn places Pur requisition for want of some goods/products - ME51

Request for Quotation(RFQ)-> The Purchase dept in the orgn calls/requests for the quotation for the products against which PR was raised. - ME41

Vendor Evaluation->After receving the RFQ's, after comparison a Vendor is finalised based on the terms and conditions.

Purchase Order(PO)-> Pur order was issued to that vendor asking him to supply the goods/products -ME21N

Goods Receipt Note(GRN)->Vendor supplies the material/Products to the orgn-

MB01

Goods Issue (GI) -> People receives their respective itesm for which they have placed the Requisitions

Invoice Verification-> ALong with the Material Vendor submits a Invoice for which the Company Pays the amount - .MIRO

Data to FI -> data will be posted to FI as per the vendor invoices

you better go through all these links u will get all the info what ever u need

for mm

http://www.sapgenie.com/abap/tables_mm.htm

http://www.sap-img.com/sap-download/sap-tables.zip

http://www.allsaplinks.com/material_management.html

http://www.training-classes.com/course_hierarchy/courses/2614_SAP_R_3_MM_Invoice_Verification_-_Rel_4_x.php

http://www.sapfriends.com/sapstuff.html

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSMAT/PSMAT.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCMM/CAARCMM.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOMDMM/LOMDMM.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMMM/BCBMTWFMMM.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMIVMVAL/MMIVMVAL.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMWMLVS/MMWMLVS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMISVE/MMISVE.pdf

Regards

Anji

Re: query

Former Member — Tue, 13 Nov 2007 05:56:43 GMT

MM Process flow:

The typical procurement cycle for a service or material consists of the following phases:

1. Determination of Requirements

Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.

2. Source Determination

The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.

3. Vendor Selection and Comparison of Quotations

The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.

4. Purchase Order Processing

The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.

5. Purchase Order Follow-Up

The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.

6. Goods Receiving and Inventory Management

Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.

7. Invoice Verification

The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.

Common Tables used by SAP MM:

Below are few important 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

Transaction Codes:

RFQ to Vendor - ME41

Raising Quotation - ME47

Comparison of Price - ME49

Creation of PO - ME21N

Goods Receipt - MIGO

Invoice (Bill PAssing) - MIRO

Goods Issue - MB1A

Physical Inventory - MI01( Create doc)

MI04 (Enter Count)

MI07 (Post)

Also please check this links.

http://www.sapgenie.com/sapfunc/mm.htm

http://www.sap-basis-abap.com/sapmm.htm

SD Process Flow:

The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customer’s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents – the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge – creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.

Transaction Codes:

Inquiry - VA11/VA12/VA13

Quotation - VA21/VA22/VA23

Sales Order - VA01/VA02/VA03

Delivery - VL01N/VL02N/VL03N

Billing/Invoicing - VF01/VF02/VF03

Also please check this links.

http://www.sapgenie.com/sapfunc/sd.htm

http://www.sap-basis-abap.com/sapsd.htm

http://www.sapgenie.com/abap/tables_sd.htm

Re: query

Former Member — Tue, 13 Nov 2007 06:02:53 GMT

HI,

<b>SALES & DISTRIBUTION MODULE RELATED TABLES:</b>

Cycle:

Enquiry?Quotation?Sales Order?Delivery(Picking, Packing, Post Goods

Issue and Shipment)?Billing? Data to FI

TABLES and Important Fields:

VBAK: Sales Document(Header Data) (VBELN)

VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)

Enquiry, Quotation, Sales Order are differentiated based on Doc.

Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,

for Quotation 'B' & for Order it is 'C'.)

LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)

LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)

(LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)

VTTK: Shipment Table (Header Data)(TKNUM)

VTTP: Shipment Table (Item Data)( TKNUM,TPNUM,VBELN)

(VTTP-VBELN = LIKP-VBELN)

VTFA: Shipping Document Flow(TKNUM,VBELV,VBELN)

VTPA: Shipping Partners data(VBELN,PARVW,KUNNR,PERNR)

VTTS: Stages in Shipment(TKNUM,TSNUM,TSTYP)

VTSP: Transport Stage/Shipment Item Allocation(TKNUM,TSNUM,TPNUM)

VEKP: Handling Unit: Header(Packing)(VENUM,VSTEL)

VEPO: Handling Unit: Item (Packing)(VENUM,VEPOS,VBELN)

VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)

VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)

(VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)

Apart from these tables there are lot of other tables which starts with

‘V’, but we use the following tables frequently.

VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)

VBTYP= ‘C’(Sales Order) VBTYP=’J’(Delivery) VBTYP=’M’(Invoice)

VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)

VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)

VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)

VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)

VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)

VEDA: Contract Data(VBELN,VPOSN)

VEDAPO: Contract Data(VBELN,VPOSN)

KONA: Rebate Agreements (KNUMA,VKORG,VTWEG,SPART)

VBRL: SD Document: Invoice List(VBELN,POSNR,VBELN_VF,NETWR,KUNAG)

VKDFS: SD Index: Billing Indicator(FKTYP,VBELN,FKART,VKORG)

VBSK: Collective Processing for a Sales Document Header(SAMMG,SMART)

VBSS: Collective Processing: Sales Documents(SAMMG,VBELN,SORTF)

VRKPA: Sales Index: Bills by Partner Functions(VBELN,BELNR,KUNDE,PARVW)

VRPMA: SD Index: Billing Items per Material(MATNR,VBELN,BELNR,KUNNR)

TVLKT: Delivery Type: Texts(LFART,VTEXT)

KNA1: Customer Master-General(KUNNR,NAME1,LAND1)

KNB1: Customer Master(Company Code)(KUNNR,BUKRS,PERNR)

KNC1: Customer Master Data (Transaction Figures)(KUNNR,BUKRS,GJAHR)

KNVK: Customer Master Contact Partner(PARNR,KUNNR,NAME1)

KNVV: Customer Master sales data(KUNNR,VKORG,VTWEG,KDGRP)

KNBK: Customer Bank Details(KUNNR,BANKS,BANKL,BANKN)

KNVH: Customer Hierarchy (HITYP,KUNNR,VKORG,VTWEG,SPART)

KNVP: Customer Master Partner Functions(KUNNR,PARVW,KUNN2)

KNVS: Customer Shipment data(KUNNR,VSTEL,TRANS)

KNVI: Customer Tax data(KUNNR,ALAND,TATYP)

LFA1: Vendor Master-General (LIFNR,NAME1,ORT01)

LFB1: Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)

LFC1: Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)

MARA: Material Master-General (MATNR,MTART,MATKL)

MARC: Material Master-Plant data(MATNR,WERKS,EKGRP)

MARD: Material Master- St.Location Data(MATNR,WERKS,LGORT,LABST)

EBEW: Sales Order Stock Valuation(MATNR,VBELN,BWKEY,BWTAR)

TVKO: Sales Organizations(VKORG)

TVTW: Distribution Channel(VTWEG)

TSPA: Divisions(SPART)

TVKOV: Distribution Channels for S.Orgn(VKORG,VTWEG)

TVKOS: Divisions for S.Orgn(VKORG,SPART)

TVTA: Sales Areas(VKORG,VTWEG,SPART)

TVBUR: Sales Offices(VKBUR,ADRNR)

TVKBT: Sales Office Texts(VKBUR,SPRAS,BEZEI)

TVKBZ: Sales Office Assign.to Sales Area(VKORG,VTWEG,VKBUR)

TVKGR: Sales Group(VKGRP)

TVGRT: Sales Group Texts(VKGRP,SPRAS,BEZEI)

TVBVK: Sales Group to Sales office(VKBUR,VKGRP)

TVKWZ: Plants Assign.to S.Orgn(WERKS,VKORG)

T171T: Sales District Texts(BZIRK,BZTXT,SPRAS)

TVLA: Loading Points(LSTEL)

TVST: Shipping Points (VSTEL)

TVSWZ: Shipping Point to Plant(VSTEL,WERKS)

TVPT: Item Categories (PSTYV)

TINC: Customer Incoterms(INCO1)

T077D: Customer Account Group (KTOKD)

T001W: Plants (WERKS)

T001L: Storage Locations (LGORT)

T499S: Locations(WERKS,STAND,KTEXT)

TWLAD: To get address of Storage Location and Plant(LGORT,ADRNR)

TVAK: Sales Document (Order) Types (AUART)

TVAU: Sales Documents: Order Reasons (AUGRU)

TVFK: Billing Document Types (FKART)

TVLK: Delivery Types(LFART)

TVSB: Shipping Conditions (VSBED)

TTDS: Transportation Points(TPLST)

TVKT: Account Assignment Groups (KTGRD)

KONV: Condition Types pricing)(KNUMV,KSCHL,KWETR)

ADRC: To get Addresses of Partners(ADDRNUMBER,NAME1)

VBBE: Sales Requirements: Individual records(VBELN,POSNR,MATNR)

VBBS: Sales Requirement totals Record(MATNR,WERKS,LGORT,CHARG)

VBKA: Sales Activities Data(VBELN,KTAAR)

VBPV: Sales Document Product Proposal(VTWEG,MATNR,KUNNR,CHARG)

T682: Access Sequences (KOZGF)

T682T: Access Sequence Texts (KOZGF,VTXTM)

T683: Pricing Procedures (KALSM)

T683T: Pricing Procedures Texts(KALSM,KAPPL,SPRAS,VTEXT)

T685: Pricing Condition Types (KSCHL)

T685T: Condition Type Texts(KSCHL,SPRAS,KAPPL,VTEXT)

KONH: Conditions (Header)(KNUMH,KAPPL,KSCHL)

KONP: Conditions (Item)(KNUMH,KOPOS,KAPPL,KSCHL)

KONV: Conditions (Transaction Data)(KNUMV,KSCHL,KBERT,KWERT)

KOND: Conditions (KNUMD,ZUSKO,KSCHL)

<b>MATERIAL MANAGEMENT MODULE:</b>

Cycle:

Purchase Requisition?Request for Quotation(RFQ)?(Vendor Evaluation)?Purchase Order(PO)?Goods Receipt Note(GRN)?Invoice Verification?Data to FI

TABLES and Important Fields:

LFA1--Vendor Master-General (LIFNR,NAME1,ORT01)

LFB1--Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)

LFC1--Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)

LFM1—-Pur.Orgn. Related Vendor Data (LIFNR,EKORG)

MARA--Material Master-General (MATNR,MTART,MATKL)

MARC--Material Master-Plant data(MATNR,WERKS,EKGRP)

MARD--Material Master- St.Location Data(MATNR,WERKS,LGORT,LABST)

MAKT--Material Descriptions(MATNR,MATKL,MAKTX)

MBEW--Material Valuation Data(MATNR,BWTAR)

MVKE—-Material Master: Sales related Data(MATNR,VKORG,VTWEG)

MDKP--MRP related data(Header)(DTART,MATNR,PLWRK,PLSCN)

MDTB—-MRP Table(DTNAM,DTPOS,PLANR)

MCHA--Batches (MATNR,WERKS,CHARG)

MCHB—-Batch Stocks(MATNR,WERKS,LGORT,CHARG)

EBAN-- Pur.Reqn. Data (BANFN,BNFPO,BADAT,MATNR)

EBKN-- Purchase Requisition Account Assignment(BANFN,BNFPO,VBELN)

EINA—- Purchase Info.Record (General Data)(INFNR,MATNR,LIFNR)

EINE-- Purchase Info.Record (Pur.Orgn Data )(INFNR,EKORG)

ELBK-- Vendor Evaluation Header Data(LIFNR,EKORG,KLASS)

ELBM-- Vendor Evaluation: Material-Related Item(LIFNR,MATNR,EKORG,INFNR,HKRIT)

ELBP—- Main Criteria for Vendor Evaluation (LIFNR,EKORG,HKRIT)

EKKO-- Purchase Order Data (Header)(EBELN,BSTYP,BSART)

EKPO-- Purchase Order Data (Item)(EBELN,EBELP,MATNR)

RFQ and PO are differentiated by Doc Type(BSTYP)in EKKO table.

For RFQ it is ‘A’ and for PO it is ‘F’.

MKPF-- GRN Data (Header) (EBELN,BLDAT,BUDAT,XBLNR,BKTXT)

MSEG-- GRN Data (Item)(MBLNR,BWART,LIFNR,MATNR,EBELN)

Apart from this there are lot of tables which begin with 'M'& 'E', but we

use the following very often.

EQUK--Quota(header) (QUNUM,MATNR)

EQUP—-Quota(item) (QUNUM,QUPOS,LIFNR)

ESLH--Service Package Header Data (PACKNO,EBELN,VBELN)

ESLL--Lines of Service Package (PACKNO)

ESUH--Ext. Services Management: Unpl.Service Limits: Header Data(PACKNO)

ESKN--Account Assignment in Service Package(PACKNO)

EKKN--Account Assignment in Purchasing Document(EBELN,EBELP,VBELN)

EKBE--PO History Data (EBELN,EBELP,BELNR,BLDAT,MATNR,VGABE)

EKBZ--PO History with delivery Costs(EBELN,BELNR,LIFNR,XBLNR)

EKET--Schedule lines data of a PO (EBELN,EINDT,SLFDT)

EKES--Vendor Confirmations Data(EBELN,EBTYP,EINDT,XBLNR)

T001W-- Plants (WERKS)

T001L-- Storage Locations (LGORT)

T300—- Warehouse Numbers(LGNUM)

T301—- Storage Types(LGNUM,LGTYP)

T320—- Assign. Stor.Locn to WM Warehouse(WERKS,LGORT,LGNUM)

T163F--Confirmation Texts(EBTYP,EBTXT)

T156-- Movement Types(BWART)

T024-- Purchasing Groups(EKGRP,EKNAM)

T024E--Purchase Organizations(EKORG,BUKRS)

T024W--Plants Assign.to P.Orgn(WERKS,EKORG)

T161-- Purchasing Document Types(BSTYP,BSART)

T163-- Item Category’s in Purchasing Documents(PSTYP)

T149D--Valuation Types(BWTAR)

T134-- Material Types(MTART)

T179—- Material Product Hierarchies(PRODH)

T179T—-Material Product Hierarchies: Texts(PRODH,SPRAS,VTEXT)

TJ02T—-System status texts(ISTAT,SPRAS,TXT30)

STKO-- BOM(Bill of Material)(Header)( STLTY,STLNR,STLAL)

STPO—- BOM(Bill of Material)(Item)( STLTY,STLNR,STLKN,STPOZ)

STPU-- BOM Sub-Item (STLTY,STLNR,STLKN)

STPN-- BOM Follow-Up Control (STLTY,STLNR,MATNR)

STST-- Standard BOM Link (STOBJ,STLNR,STLAN,STLAL)

STZU—- Permanent BOM data( STLTY,STLNR,STLAN,ALTST)

RKPF-- Document Header: Reservation(RSNUM,BWART,ANLN1,KOSTL)

RBKP-- Document Header: Invoice Receipt(BELNR,BLART,GJAHR,BUDAT)

RSEG-- Document Item: Incoming Invoice(BELNR,BUZEI,EBELN,MATNR)

rgds,

bharat.