topic Re: Flow between SAP tables in Application Development and Automation Discussions

Flow between SAP tables

Former Member — Thu, 02 Aug 2007 05:54:33 GMT

Dear Friends;

I just wanna know the flow between SAP Sales And Distribution Tables.

Please help me out.

Regards;

Parag

Re: Flow between SAP tables

Former Member — Thu, 02 Aug 2007 05:57:11 GMT

Hi,

SD FLOW

SD Flow Cycle:

INQUIRY ( VA11)

QUOTATION (VA21)

PURCHASE ORDER (ME21)

ORDER CONFIRMATION (VA01)

PICKING LIST – (VL36)

PACKING LIST - (VL02, VL01)

SHIPPING – (VT01)

INVOICE – (VF21, VF01)

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.

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)

Regards

Re: Flow between SAP tables

Former Member — Thu, 02 Aug 2007 05:58:18 GMT

Hi Parag,

Check below link

http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm

Regards,

Atish

Re: Flow between SAP tables

Former Member — Thu, 02 Aug 2007 05:58:42 GMT

Hi,

Here are the links which explains you the links

http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm

http://www.sap-basis-abap.com/mm/sap-mm-tables-link.htm

All tables: http://www.erpgenie.com/abap/tables.htm

Regards

Sudheer

Re: Flow between SAP tables

Former Member — Thu, 02 Aug 2007 05:58:48 GMT

Hi,

check this link..

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

reward if it helps..

regards,

Omkar.

Re: Flow between SAP tables

Former Member — Thu, 02 Aug 2007 06:05:38 GMT

Hi,

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.

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

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.

Regards,

Bhaskar

Re: Flow between SAP tables

Former Member — Thu, 02 Aug 2007 06:11:03 GMT

Hi Parag,

VBAK --> VBAP - Sales order

LIKP --> LIPS - Delivery

VTTK --> VTTP - Shipment

VBRK --> VBRP - Billing

VBUK --> VBUP - Status

VBFA - Document flow tables linking Sales order, delivery, shipment and invoice

Regards

Arun

Re: Flow between SAP tables

Former Member — Thu, 02 Aug 2007 06:23:33 GMT

SD FLOW OVERVIEW:

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 Order Management Transactions

SALES ORDER PROCESSING

Creating Sales Order - VA01

Maintaining a Sales Order - VA02

Displaying a Sales Order - VA03

Releasing an Order or Delivery from Credit Hold: Non-Flooring - VKM1

Display List of RMAs by Customer - VA05

Confirm RMA Goods Receipt - VL02

Generate list of open return orders for deletion - VA05

Display Customer returns eligibility - MCSI

Removing a Billing Block (Approving Credit/Debit Requests) - V.23

PRICING MASTER DATA

Create Pricing - VK11

Creating a Sales Deal - VB21

Maintaining a Sales Deal - VB22

Displaying a Sales Deal - VB23

Maintaining Prices - VK12

Displaying Prices - VK13

MATERIAL MASTER DATA

Creating Material Substitution Master Data - VB11

Maintaining/Deleting Material Substitution Master Data - VB12

Displaying Material Substitution Master Data - VB13

Creating a Bundled Master - MM01

Creating a Sales BOM - CS01

Maintaining a Sales BOM - CS02

Displaying a Sales BOM - CS03

CUSTOMER MASTER DATA

Creating Partner Records - XD01

Maintaining Customer Master Data - XD02

Displaying Customer Master Data - XD03

Deactivating a Partner - VD06

CUSTOMER CREDIT INFO

Creating/Maintaining New Customer Credit Information - FD32

Displaying Customer Credit Information - FD33

Blocking or Unblocking a Customer - VD05

SHIPPING

Creating a Delivery - VL01N

Displaying a Delivery - VL03N

Changing a Delivery - VL02N

Shipment Inquiry / Display - VT03

Adjusting Transfer Order - Confirmation Quantity - LT12

Collectively Confirm Transfer Order - LT25

Batch Shipment Confirmation - VL19

PGI Reversal Cancellation - VL09

Creating Service Provider/Carrier Master Data - XK01

Maintaining Serive Provider/Carrier Master Data - XK02

Displaying Service Provider/Carrier Master Data - XK03

Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit - MM02

IDoc Inquiry - WE02 / WE05

BILLING

Invoicing a Customer Shipment - VF01

Reprinting an Invoice - VF31

Releasing a Sales Order for Billing - V.23

Creating an Invoice by Using the Billing Due List - VF04

Checking Open Billing Documents - VF05

Create Credit/Debit Memo - FB01

A/R

Controlling Total Debit/Credit bkgs - F.03

Generate FI Account balance - F.08

Generate Month-to-date Inv. register - F.02

Process payments - FBZ1

Rqst Individual Customer Corresp. - FB12

Generate Customer Correspondence - F.61

Enter Batch totals under Control ttl - FB07

Display G/L Acct. totals - FBL3N

Reverse Posted Amounts - FB08

Customer Refunds - FBL6

Customer Refund to other than Payer - FB05

Clearing Debit/Credit on Cust. acct. - FB1D

Customer Balance in Local Currency - F.23

G/L Account Balance Report - F.08

Create Invoice - legal entity adjust - FB01

Generate Cust. Acct. statements - F.27

Generate Dunning Letters - F150

Generate Billing Due List - VF04

Generate Blocked Billing Doc list - VFX3

Inq. via Credit Release Screen - VKM1

List orders by partner - VA05

Past Due invoices by customer - FD11

Check number info by G/L account - FBL3N

Display customer Line items - FBL5N

Re: Flow between SAP tables

fmunozb — Fri, 31 Jul 2020 11:53:38 GMT

The link is broken, use the one below

Re: Flow between SAP tables

former_member8821 — Tue, 24 May 2022 09:36:36 GMT

Please find SD FLOW Below

SD Flow Cycle:

INQUIRY ( VA11)

QUOTATION (VA21)

IF STO is there then you have to with this T-Code à PURCHASE ORDER (ME21)

ORDER CONFIRMATION (VA01)

PICKING LIST – (VL36)

PACKING LIST - (VL02, VL01)

SHIPPING – (VT01)

INVOICE – (VF21, VF01)

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

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)