on 09-13-2007 3:56 AM
The integration points b/w SD module and ABAP?
(also specify the underlying databse table names and fields with detail)
Dear Mathew Parera,
Well ABAP is integrated with all the modules.
A small search on SDN SD forum will help you to answer your query.
I will suggest you to visit http://sap-img.com/sap-sd.htm. It will give you the overview of SAP SD module.
Moreover there is a separate section of FAQs with answers which will help you in great deal.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mathew,
ABAP Plays a vitol role in all SAP Modules.
Because once you save the data it will goes and stores in respective tables in which it contians respetive Fields.
In addition to above, Please find the Important Tables Pertaining to SD Module.
SD TABLES:
Important Tables for SAP SD
Sales and Distribution:
Customers : Table Description
KNA1 General Data
KNB1 Customer Master Co. Code Data (payment method, reconciliation acct)
KNB4 Customer Payment History
KNB5 Customer Master Dunning info
KNBK Customer Master Bank Data
KNKA Customer Master Credit Mgmt.
KNKK Customer Master Credit Control Area Data (credit limits)
KNVV Sales Area Data (terms, order probability)
KNVI Customer Master Tax Indicator
KNVP Partner Function key
KNVD Output type
KNVS Customer Master Ship Data
KLPA Customer/Vendor Link
Material Master:
MARA Material master
MAKT Material text
MARC Material per plant / stock
MVKE Material master, sales data
MARD Storage location / stock
MSKA Sales order stock
MSPR Project stock
MARM Units of measure
MEAN International article number
PGMI Planning material
PROP Forecast parameters
MAPR Link MARC <=> PROP
MBEW Material valuation
MVER Material consumption
MLGN Material / Warehouse number
MLGT Material / Storage type
MPRP Forecast profiles
MDTB MRP table
MDKP Header data for MRP document
MLAN Tax data material master
MTQSS Material master view: QM
Sales Documents
VBAKUK VBAK + VBUK
VBUK Header Status and Administrative Data
VBAK Sales Document - Header Data
VBKD Sales Document - Business Data
VBUP Item Status
VBAP Sales Document - Item Data
VBPA Partners
VBFA Document Flow
VBEP Sales Document Schedule Line
VBBE Sales Requirements: Individual Records
VBKA Sales activities
VBFA Sales Document Flow
Logical databases: AAV, AKV, ARV, VFV
Sales requirements
VBBE Sales Requirements: Individual Records
VBBS Sales Requirement Totals Record
SD Delivery Documents:
LIPS Delivery Document item data, includes referencing PO
LIKP Delivery Document Header data
Shipping:
VTTK Shipment header
VTTP Shipment item
VTTS Stage in transport
VTSP Stage in transport per shipment item
VTPA Shipment partners
VEKP Handling Unit - Header Table
VEPO Packing: Handling Unit Item (Contents)
VTFA Flow shipping documents
Billing Document:
VBRK Billing Document Header
VBRP Billing Document Item
SD Shipping Unit VEKP Shipping Unit Item (Content)
VEPO Shipping Unit Header.
Pricing:
KONAIND Index: Groups of Conditions/Header Record Conditions
KOND Conditions (Data)
KOND3 Conditions: Campaign Determination - Data Part
KONDD Material Substitution - Data Division
KONDDP Conditions: Additional Materials for Material Determination
KONDH Conditions: Batch Strategy - Data Division
KONDI Conditions: Data part for certificates
KONDIND General Document Index for Conditions
KONDN Conditions: Free goods - Data section
KONDNS Conditions: Free goods determination - scales
KONDP Conditions: Packing Object Data Section
KONDR Conditions: Derivation strategy - data part
KONDRPR Conditions: Derivation strategy - recipient item data
KONDRPS Conditions: Derivation strategy - sender item data
KONDV Conditions: Data part for certificates
KONH Conditions (Header)
KONM Conditions (1-Dimensional Quantity Scale)
KONP Conditions (Item)
KONV Conditions (Transaction Data)
KONW Conditions (1-Dimensional Value Scale)
KOTN900 LSI Free Goods Condition Table
KONV Conditions for Transaction Data
KONP Conditions for Items
LIKP Delivery Header Data
LIPS Delivery: Item data
VBAK Sales Document: Header Data
VBAP Sales Document: Item Data
VBBE Sales Requirements: Individual Records
VBEH Schedule line history
VBEP Sales Document: Schedule Line Data
VBFA Sales Document Flow
VBLB Sales document: Release order data
VBLK SD Document: Delivery Note Header
VBPA Sales Document: Partner
VBRK Billing: Header Data
VBRP Billing: Item Data
VBUK Sales Document: Header Status and Administrative Data
VBUP Sales Document: Item Status
VEKP Handling Unit - Header Table
VEPO Packing: Handling Unit Item (Contents)
VEPVG Delivery Due Index
Bill of Material:
MAST Material to BOM Link
EQST Equipment to BOM Link
STAS BOMs header
STKO BOM header
STPN BOM follow-Up control
STPO BOM item
STPU BOM sub-item
STST Standard BOM link
STVB Bills of material - Serialization of posting
STZU Permanent BOM data
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
as per ur query, abap is integrated with all the modules available in sap..
the grt advantage of abap integrating with sd is that, say for instance u are working on an erp product (XXX) say a web based, which covers up all the sales and distribution activities right from the sales order to billing,.. now this product has the such features that it can be integrated with sap system in the areas of SD.
to be clear on this lets say for instance A is the customer who is using SAP system fro his business process, now this customer is looking up for this product (XXX) which gives him the option of online purahase order by the customer itself.. so now this customer wants to take up this product(xxx)'s ordering system but the rest of the ordering process ie, delivery, billing etc is to be done in sap system only. in such cases the advantage of abap integration is very useful, by using some standard abap programs, say Bapi's , RFMs, the product(xxx) is intergeated with sap. here what happens is that as soon as the order is placed in product(xxx) the fields are mapped into sap system with the help of some bapis, or rfms and the values are inserted exactly into the tables where sap order details are stored.. say for eg:beow are the sales order tables..
VBAK Header
VBAP Item
VBEP Schedule Lines
VBPA Partner Details
VBUK Header Status
VBUP Item Status
after posting the order into the sap system the the document number is returned to the product(xxx) same with help of bapi, rfms.. later on the delivery and billing process is done as usual in the sap system.. this is just an example, in this same way the abap can be integrated with all the modules with respect to the busienss requirements and clients requirements..
below are some of the important tabels
SD DeliveryDocumet LIPS Delivery Document item data, includes referencing PO
LIKP Delivery Document Header data
Billing Document VBRK Billing Document Header
VBRP Billing Document Item
SD Shipping Unit VEKP Shipping Unit Item (Content)
VEPO Shipping Unit Header
refer to the link below..can get the list of tables and the integration flow
http://www.erpgenie.com/sap/abap/tables.htm
Reward if USeful
Thanx & regards.
Naren..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
SAP ABAP related tables with respect to SD are as follows
Refer the sdn thread for more details
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.
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
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
Message was edited by:
SHESAGIRI.G
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
ABAP is integrated with every module as this is the technical module.
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 F2
Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
Sail
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.