Can anybody send me SD and MM flow

Former Member · ‎11-27-2007

Hi friends,

Can anybody forward me details steps of SD and MM flow

Former Member · ‎11-27-2007

SALES & DISTRIBUTION MODULE RELATED TABLES:

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)

MATERIAL MANAGEMENT MODULE:

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)

Regards,

Satish

Former Member · ‎11-27-2007

SALES & DISTRIBUTION MODULE RELATED TABLES:

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)

MATERIAL MANAGEMENT MODULE:

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)

Former Member · ‎11-27-2007

Hi,

1. MM Flow.

> goto T.C MM01.

> give material Number - some no.

give MAterial sector - Mechanical

give Material Type - Raw Material.

then goto ORg Levels on top.

then goto plant - 1000 n storage location - 0001

then select views.

in that select basic data 1, basic data 2, purchasing, general plant data storage / main..., Accounting 1 n then enter.

> Then give the materiual descripition

basic unit of measure KG

Mat group - 001.

click on purchasing n give mat no u have created n plant - 1000 n basic unit of measure KG n enter enter n enter.

then goto valuation class - 3000, P.C - S n moving price -100.

save then the mat no gets created.

> now go to TC XK01 ie, vendor master

give vendor - 126

comp code - 1000.

pur org - 1000.

Acc grp - 0001

enter

give title name - company.

search itenm 1/2 - M

then Rec ACc - 31000.

Cash Mang Grp - A1.

enter n enter.

order currency - INR

in control data click on GR- based info verf n click on ACK Req.

save n enter.

> goto TC ME 11 ie, purchasing info record.

Vendor - 126.

Mat no - the one u have created.

Pur org - 1000

plant - 1000

info rec-

select standard enter n enter.

in Period delay time give -10 n In conditions Net price - 100.enter In control Pur grp - 100.

enter n enter n enter for three times.

> goto ME01 source list.

Mat no - mat no u have created.

Plant - 1000.

enter fix the line.

give vlaid from , vend to , vendor as 126 p org as 1000, enter n save.

> TC code RFQ for request for quotation.

TC ME41.

RFQ type - AN

Lang Key -EN

RFQ date - any date.

QUAT Deadline - any date RFQ-

give purc org grp - 000

presss enter

coll no - RFQ1.

enter then give MAt no RFQ qnt as 100 ,O as KG del dat n netr.

goto header click on Vendor Add

vendor - 567

Title - company

enter.

the goto tc ME47

quotation.

give net price 100 enter.

then goto ME49.

give quotation no tht u have created coll rfq as RFQ1 vendor as 567 mat no u have created. n execute, back n back.

> goto tC ME51N for purc requisition.

click on header n give text as.

item as 10,SR as sur3, quant 100, del date, mat grp, plant n pur as 000

enter n save.

we will get purch req no...

now go to ME21N pur order.

click on Purchase/req no. click on value ur purh req no will be displayed there select it...

then goto Org data tab strip.

pur org - 1000.

Pur grp - 000

com code - 1000

enter

vendor - the one u have given...

enter n enter check n save.

then tc MIGO for goods receipt.

give pur order no u have created...

gotot quantity tabstrip n press enter give qty in unit of enrty as 80

goto pur org tabstrip n give del comp as set automatic.

click on item ok.

then continue n then post n continue.

then two documents will get created mat doc n acc doc.

then > MIRO invoice.

give vendor no - comp code invo date pur ord no.then select it n copy.

enter.

then we will get acc no n write it in the acc block.

the >MB1A ie goods issues.

mov type - 201

plant - 1000

stor loc - 0001

enter

cost cent - 1000

vendor - u have created

then give sc qty enter.

mat n acc doc r generated.

>MMBE stock overview.

give mat no - u have created.

plant - 1000

sto loc - 0001 n enter...

the MM get created...

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)

|

AR

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

see this link

http://www.sap-basis-abap.com/sd/sap-sd-processing-flow.htm

Former Member · ‎11-27-2007

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 F2

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

plzzzzzzzzzzz reward if usefulll

dont forget to rewarddddddd

Former Member · ‎11-27-2007

Hi Fnd,

This is kiran kumar.G.I have send some information.plz go through that.The below information is very much helpful for u ok.

if u r satisfy with my answer plz give me REWARD POINTS.

HAVE A NICE DAY.

SD FLOW:( Basic Terminology before we go to SD Flow)

Flow of SD in brief:

1) Quotation -> Vendor sends the quotation based on Purchase

Requisition sent by Customer

2) Purchase order -> this is raised by the customer once the

quotation is accepted.

3) Sales Order -> if Quotation is accepted then Vendor shall raise a

sales order for the raised purchase order

4) Delivery ->delivery to the Customer( to whom to send,what to

send,material, qty Etc)

5) Shipping -> Shipping ( Shipping details where to send , what is

the mode of transport ,)

6) Billing -> bill is sent to customer with respect to goods.

7) Payment -> payment is given by the customer to Vendor

SD FLOW:

inquery / document type is 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

material no,vendor no.

to create vendor tcode is

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

tables are lfa1.

to create customer tcode is xd01,xd02,xd03.

table is kna1.

after creating sales order using this no we can create

delivery note tcode is vl01.

Sales Org. ( based on the cost center of the sold item)

|

v

Distribution Channel

|

v

Division

|

v

Reg. Sales office

|

v

Sales Group

|

v

Sales Person

MM FLOW :

MM flow is processing between business organization and Vendor

1... Purchase Requisition --- T.code ---ME51

2...Source List -

T.code- -

ME41

3...Request for Quotaation (RFQ)---T.code- -ME21N (To Vendor)

4...Purchase Order -

T.code -

ME21(To Vendor)

5...Goods Receipt----- --T.code. ...M1GO

(Tables: MKPF, MSEG)

6...Invoice Verification- ---T.code. ..MIRO

(Tables: BKPF, BSEG)

7...Vendor Payment

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 under deliveries 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)

Former Member · ‎11-27-2007

SD FLOW

Customer is buying ...

sales order - Transaction VA01 - Tables VBAK, VBAP, VBEP, VBKD, VBPA, VBUK, VBUP.

Delivery - Transaction VL01N - Tables LIKP, LIPS, VBUK, VBUP.

Goods issue - Transaction VL02N - Tables MKPF, MSEG

Billing document - Transaction VF01 - Tables VBRK, VBRP.

Customer is returning...

Return order - Transaction VA01 - Tables VBAK, VBAP, VBEP, VBKD, VBPA, VBUK, VBUP.

Returns delivery - Transaction VL01N - Tables LIKP, LIPS, VBUK, VBUP.

Goods Receipt - Transaction VL02N - Tables MKPF, MSEG

Credit memo - Transaction VF01 - Tables VBRK, VBRP.

Customer wants some money back.

Credit memo request - Transaction VA01 - Tables VBAK, VBAP, VBEP, VBKD, VBPA, VBUK, VBUP.

Credit memo - Transaction VF01 - Tables VBRK, VBRP.

Customer was charged less money ..Meaning we want some money back from customer..

Debit memo request - Transaction VA01 - Tables VBAK, VBAP, VBEP, VBKD, VBPA, VBUK, VBUP.

Debit memo - Transaction VF01 - Tables VBRK, VBRP.

*******************************************************************

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.

Regards

vasu

Former Member · ‎11-27-2007

Hi,

Can i have ur mail id so that i can send to ur mail the doc related to sd and mm flow

Regards,

Sreenivas

Former Member · ‎11-27-2007

hi

my email id is it_suresh@hotmail.co.uk

Former Member · ‎11-27-2007

Hi Suresh,

Please follow the below steps for SD,MM and some links also:

Document Flow in Sales :

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(va11), the quotation(VA21), the sales order(va01), the delivery(VL01N),picking(VL02N), the invoice(VF01), 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.

SD FLOW:

Sales

Inquiry - A customer’s request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.

Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.

Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.

The sales area that accepts the inquiry is responsible for completing the agreement.

Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.

b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).

c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.

Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.

Sales document flow is as below.

1)VA11- It starts with an enquiry where i am enquire regarding the products a company s based on pre sales activities the company carries out like say mailers on any campaign that i have carried out that leads to an enquiry.

2) Va21- Next A quatation is placed ,Customer may have enquired about 30 products but you give quotation to only 20 items subject to their availability with you. quotation is a binding document about conformed price & delivery schedule.

3) VA01- When a quatation is placed the next step is the sales order. The same is a purchase order for the person who places the order and a sales order for the person who sells the products.

4) VL01N- Once the order is placed i create a delivery where i need to deliver the goods to the customer, here I need to see that pick qty and delivery qty is the same pick qty is that qty where i pick the goods from my warehouse.

5) Once i do the delivery the next step is Post goods Issue, which means my stock gets reduced and all my previous documents get updated. A post goods issue can be done before the goods leave to the customer or when the goods are in transit. But the same should be done.

6) VF01- The next step would be billing where after doing the post goods issue i raise and invoice to the customer which is called billing.

7) If the customer finds that there are some goods which are damaged he would return the goods back which are called returns and i would then raise a credit memo which would give him credit for the damaged goods.

SD document reference:

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

http://help.sap.com/saphelp_47x200/helpdata/en/06/57683801b5c412e10000009b38f842/frameset.htm

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

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

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

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

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