Filling VBPA kunnr lifnr pernr parnr

Hello,
I am trying to understand how the following field in VBPA are filled and determined. The fields are:
kunnr
lifnr
pernr
parnr
I understand that it depends on the partner function (parvw) value.
But I am not sure if there is a place in config that determines which field in VBPA should be filled according to the parvw.
I have seen the IMG CONFIG partner determination in SD.
For partner function SP(sold-to), the partner type is KU. This seems to be stored in VBPA-kunnr, while the other fields are empty. In other cases, partner function AP, is stored in VBPA-PARNR.
QUESTION:
How does SAP determine which field(above 4 fields) to place the value into? Is there another configuration that I can take a look at?
Regards,
Anna-Liza
Moderator message : Not directly related to ABAP development, post the question in relevant functional forum. Thread locked
Edited by: Vinod Kumar on Jan 4, 2012 10:39 PM

Hello,
Thank youf for the reply.
However, from transaction XD02, partner function tab, there can be many partner functions. The question is for the partner functions defined (SP - sold to party, bp - bill to party, ve - sales employees) -- when the partner function is used in a sales order and table VBPA is updated, which field is the partner number placed into VBPA? is the partner number stored in vbpa-kunnr or vbpa-lifnr, or vbpa-pernr, or vbpa-parnr? I think the parther function (SP, BP, VE) has something to do with the determination of which field to move the partner number value into. But I am not aware of where this would be defined.
Regards,
Anna-Liza

Similar Messages

IF condition to execute ABAP code; VBAK-VSBED; VBPA-KUNNR; XVBPA/YVBPA

Hi All!
I need some help. I have to change the MV45AFZZ, the FORM USEREXIT_MOVE_FIELD_TO_VBAK. The user exit should write the VBAK-VSBED (shipping condition) from the KNVV-VSBED for the VBPA-KUNNR, PARVW=WE (the ship-to-party partner). The user exit should also permit the modification of VBAK-VSBED directly from VA01 or VA02 (even if the ship-to-party remain the same).
I write down the ABAP code but I need to write a condition in order to execute the modification of VBAK-VSBED:
1. in VA01, for the first time;
2. in VA01 and VA02 if I change the ship-to-party partner.
Now, if I want to change VBAK-VSBED without modifying the ship-to-party, I can not. The user exit overwrite the VBAK-VSBED for the ship-to-party.
The code is:
READ TABLE xvbpa WITH KEY parvw = 'WE' .
IF SY-SUBRC = 0.
SELECT SINGLE * FROM knvv WHERE kunnr EQ xvbpa-kunnr and
 vkorg EQ xvbak-vkorg and
 vtweg EQ xvbak-vtweg and
 spart EQ xvbak-spart .
vbak-vsbed = knvv-vsbed.
ENDIF.
Any help will be appreciate.
Florina C.

Hi,
try this example:
*Table YVBPA should always be filled, when executing VA02, but if it is not, you
*can simple select the Sales Partner from VBPA(in va02 scenario it would be in *DB aldready)
if sy-tcode = 'VA01'.
READ TABLE xvbpa WITH KEY parvw = 'WE' .
IF SY-SUBRC = 0.
 SELECT SINGLE * FROM knvv
 WHERE kunnr EQ xvbpa-kunnr and
 vkorg EQ xvbak-vkorg and
 vtweg EQ xvbak-vtweg and
 spart EQ xvbak-spart .
 vbak-vsbed = knvv-vsbed.
ENDIF.
else if tcode = 'VA02'.
if YVBPA[] is initial.
 select single * from vbpa
 where vbeln = vbak-vbeln and parvw = 'WE'.
 if sy-subrc = 0.
 partner_before_change = vbpa-kunnr.
 endif.
else.
 READ TABLE yvbpa WITH KEY parvw = 'WE' .
 if sy-subrc = 0.
 partner_before_change = yvbpa-kunnr.
 endif.
endif.
READ TABLE xvbpa WITH KEY parvw = 'WE' .
IF SY-SUBRC = 0 and
 xvbpa-kunnr <> partner_before_change.
 SELECT SINGLE * FROM knvv
 WHERE kunnr EQ xvbpa-kunnr and
 vkorg EQ xvbak-vkorg and
 vtweg EQ xvbak-vtweg and
 spart EQ xvbak-spart .
 vbak-vsbed = knvv-vsbed.
 endif.
endif.
Best Regards,

. bapi to create customer

Hi All,
I am having problem finding a right bapi for create a customer.
I am using "bapi_customer_createfromdata1" to create a customer. Problem is i couldn't find a structure to pass sales org. data as well as partner functions.
Please help me. Feel free to ask me questions.
Thanks,
Diwakar.

Hi,
The way is using multiple BAPI's.
bapi "bapi_customer_createfromdata1" is used to create customer with reference customer number and then send the information to bapi "sd_customer_maintain_all" for changing the the values.
Still having problem passing parameters.
When i am sending partner information(knvp) to "sd_customer_maintain_all", it is giving abap dump assertion_failed.
I tried to debug the program but i couldn't find the error.
values i passed to bapi sd_customer_maintain_all
internal table of type fknvp.
MANDT sy-mandt
KUNNR st_knvp-kunnr
VKORG st_knvp-vkorg
VTWEG st_knvp-vtweg
SPART st_knvp-spart
PARVW st_knvp-parvw
PARZA
KUNN2 st_knvp-sp_kunnr
LIFNR
PERNR
PARNR
KNREF
DEFPA
Appended line by line to the table.
Reward points if found helpful....
Cheers,
Venkoji Babu.

Customer Create BAPI

Hi All,
I am trying to create a customer by calling a BAPI. I am unable to find the right one. I wanted to create customer with all levels of data(General, Company and Sales Org including partner functions). I have used below BAPI's.
BAPI_CUSTOMER_CREATEFROMDATA - Only taking general data
BAPI_CUSTOMER_CREATEFROMDATA1 - Importing general information and copying sales org data from reference customer.
SD_CUSTOMER_MAINTAIN_ALL - it is not importing KNVP(partner function data)
Please help me.
ABAPer.
Thanks in advance,

Hi All,
      I found a way to solution.The way is using multiple BAPI's.
BAPI "BAPI_CUSTOMER_CREATEFROMDATA1" is used for creating for customer with reference customer number and then send the information to BAPI "SD_CUSTOMER_MAINTAIN_ALL" for changing the the values.
Still having problem passing parameters.
When i am sending partner information(KNVP) to "SD_CUSTOMER_MAINTAIN_ALL", it is giving ABAP dump ASSERTION_FAILED.
I tried to debug the program but i couldn't find the error.
values i passed to BAPI SD_CUSTOMER_MAINTAIN_ALL
internal table of type FKNVP.
MANDT     sy-mandt
KUNNR     st_knvp-kunnr
VKORG    st_knvp-vkorg
VTWEG    st_knvp-vtweg
SPART     st_knvp-spart
PARVW   st_knvp-parvw
PARZA
KUNN2    st_knvp-sp_kunnr
LIFNR
PERNR
PARNR
KNREF
DEFPA
Appending line by line to the table.
Please help. Is there anything i am missing.
Thanks,
ABAPer.
Edited by: ABAPer on Dec 16, 2007 8:43 PM

SO via inbound EDI. partner problem LIFNR - PARTN

Hi,
Working on PO -> SO interface. Question on populating VOE4 (EDPAR).
in the inbound IDOC I have this segment:
E1EDKA1:
PARVW: AG
PARTN: external customer number (in my case it is purchasing organisation)
LIFNR: 'blank'
In forums it is told that segment LIFNR should be populated by external customer number.
What is the difference between PARVW and LIFNR? Does VOE4 look at PARTN for substitution?
in my case seems that it ignores PARTN at all..
Thanks,
Artashes

I think what you need is the following.
On the EDIDC record, field SNDPRN, you need to have the Sold To customer number mapped. You'll also need to have the SoldTo setup in WE20 with a partner profile.
You can send in an Order to SAP with a Logical System in the above field but you then have to have the PARTN fields filled in with the correct Sold To Ship To. Which you typically would not have.
On the KA1 segments, you'll need two KA1 segments, one for the Sold To and the Other for the Ship To. Since you already would know the Sold To since you put it in the EDIDC record, just fill it in the PARTN field, unless your partner wants their store number back. Personally I would set it up this way with the external store number.
So you'll want a KA1 record with the AG qualifier for the Sold To and the LIFNR field filled in with the partners external number for the Sold To. This could be the Duns number or N1/04 code.
On the second KA1 for the ship to, set the qualifier to WE for Ship To and then fill in the LIFNR with the external store number.
You'll now need entries in VOE4 for each KA1. Customer would be the same as the Customer in the EDIDC record, field SNDPRN. external function is either SP or SH. External Number is the external number, either the DUNS number for the Sold To (Most likely) or the N1/04 code for the ship to. Int No is the Internal customer number for the Sold To and Ship To.
Sold To 55555
Customer Sender ID/Dunning # 123456789
External Ship To Store # 321
WE20 setup for Sold To 55555
VOE4 setup for 55555    SP    SOLD TO   123456789 55555
VOE4 setup for 55555    SH    SHIP TO     321              55555
I think what SAP Messed up on is the fact that we should not have an external cross reference or hard coding mechanism to populat the SNDPRN with a customer number for inbound transactions in order for the EDPAR table to work correctly. You can have a logical system at the EDIDC level but would need to populate the correct Sold To and Ship To on the KA1 segments. When using the LIFNR fields, SAP Uses the SNDPRN, External Partner Number and Partner Function on the KA1 record to determine the Internal Customer Number.
If anyone else has an opinion please let me know.   I would love a way to be able to cross reference the Dunning Number for a partner to a Sold To within SAP and allow for the LIFNR fields to be used for the Ship To's.

KUNNR in IDOC COND_A

High,
I have some problems with sending conditions to the other systems. I have to send the condition which is relevant for only one customer. I have tabel with SO/DC/Customer (KUNNR) only. When I send the condition out via VK11 --> conrition info --> send condition, outgoing IDOC is created, but KUNNR field is not filled. KUNNR field is in IDOC documentation (WE60) and should be filled. What I have to do, to get customer number to the standard KUNNR field.
Thanks,
BR, Matija

Hi,
I checked in the customizing ant I have this in my table
Field name Data element Domain name
KUNAG KUNAG KUNNR
As I can understand you, there is something wrong with that?
BR, Matija

VBPA and VBAK query using OPEN CURSOR... anyway to skip buffer?

Hi all,
I have a query which VBPA inner join VBAK. In this query, I am using VBPA-KUNNR and VBPA-PARVW to query out data. I know VBPA holds a lot of data and querying in this way will be very heavy.
So I use OPEN CURSOR to query the SELECT .. INNER JOIN for these two tables...
It's fast for partners with few sales document.
But, i noticed the query will do a buffer before it process the query...
So my question is, is there a way to by-pass the buffer so it can immediately query?
Thanks,
William Wilstroth

Hi Sandeep,
I did put the BYPASSIUNG BUFFER syntax in the query. The result is still the same...
I wonder if it's just querying by VBPA-KUNNR and VBPA-PARVW is causing it? On the other hand, I think it's not because I am using VBPA-PARVW key field...
Hmmm... I wonder why in the first time query, it will go to buffer and it takes out some time...
Thanks,
William Wilstroth

Vbpa-parvw and kna1-name2

Hi Folks,
Can anyone here please provide me the select statement for picking parvw from vbpa and name2 from kna1?
Points will be rewarded.
K.Kiran

Create an IT with those fields....
SELECT PARW NAME2
INTO TABLE T_TABLE
FROM ( VBPA INNER JOIN KNA1
ON VBPA~KUNNR EQ KNA1~KUNNR )
Greetings,
Blag.

Fields KUNNR vs KNDNR!

Hi all,
What the difference between two fields KUNNR and KNDNR?
Which one should i use to be a characteristic in CO-PA?
Thanks,
HuyenTT

Hi,
KNDNR is a fixed field in COPA i.e it is delivered by SAP and in case of SD documents it is automatically filled with KUNNR from SD i.e. the sold-to-party. So there is no need for you to create another char called KUNNR.
I have seen some customers who have both KUNNR and KNDNR because they do not want the system defined logic i.e. through derivation (tcode KEDR) they overwrite KNDNR with another value of their choice. In that case it makes sense to also have another char KUNNR since then you want to capture customer and sold-to-party seperately.
regards
Waman

Wht r the standard tables for vendor customer and sales order report/

Hi wht r the standard tables for vendor and customer reports and is how in normal we cannot use them for vendor reporting and etc ?

Hi
Customer is related to Sales Module
So for a customer we fetch the reports of Sales orders , Deliveries and Billing doc's
CUstomer and Vendor related tables with important fields:
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)
Sales related Tables for a customer
VBAK: Sales Document(Header Data) (VBELN, KUNNR)
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)
Vendor related MM tables
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)
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.
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)
Reward points if useful
Regards
Anji

Let me know

What are the imp. tables frequently we use in ABAP prog. from MM and SD modules.
If possible plz give me the fields details also.

Hi
see the imp tables with fields in SD and MM modules
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 Categorys 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)
Reward points for useful Answers
Regards
Anji

How to use BAPI_BUSINESS_PARTNER_CHANGE

All,
I'm trying to use BAPI_BUSINESS_PARTNER_CHANGE for changing VBPA record.
Can someone please highlight what values need to go in partnercategory, partnertype and partnergroup. Is business partner KUNNR or LIFNR from VBPA.
I'm thinking from the tables side, I need PARTNERADDR and PARTNERADDRX, right?
This is what I have in VBPA
MANDT 060
VBELN 3257239
POSNR 0
PARVW CR
KUNNR
LIFNR EHO
PERNR 0
PARNR 0
ADRNR 9000701135
ABLAD
LAND1 US
ADRDA E
CALL FUNCTION 'BAPI_BUSINESS_PARTNER_CHANGE'
EXPORTING
 BUSINESSPARTNER =
 PARTNERCATEGORY =
 PARTNERTYPE =
 PARTNERGROUP =
PARTNEREXTNO =
PARTNERGENATTRBT =
PARTNERGENATTRBTX =
PARTNERGENATTRBTADM =
PARTNERGENATTRBTADMX =
TABLES
PARTNERADDR =
PARTNERADDRX =
PARTNERADDRUSE =
PARTNERADDRUSEX =
PARTNERBANKATTR =
PARTNERBANKATTRX =
PARTNERCCATTR =
PARTNERCCATTRX =
 RETURN =
Thank you.

Hello everyone,
I'm wondering if you have found the reason of th error messages:
E VP 200 No customer master record exists for customer EHO
E V4 219 Sales document 0003257239 was not changed
I'm trying to connect through ICWinclient (CRM) the VA01 R/3 Sales Order using Action Box:
*Object Type: BUS2032
*Method: CREATEWITHDIA
And trying to pass the BP number using the BAPIPARTNR Estructure. As Eswar Rao Boddeti said, I used the PARTN_ROLE like AG and the PARTN_NUMBER for Customer Number but I'm getting the error:
E VP 200 No customer master record exists for customer 2
E V4 219 Sales document was not changed
I also checked: "As per the error mesg in your post, i guess you are trying to change details for customer EHO, can you check if the customer exists for the sales area in your sales order via transaction XD03. Alternatively you can also check in tables KNA1,KNV*." and the record exists.
Any help anyone???
Thanks and regards,
Luis

List of Important Tables in ABAP

Hi,
Can anyone send me a List of Important Tables in ABAP.
Thanks & Regards,
Sai

Customer related tables with Important fields
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)
Vendor related
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)
Material Related
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)
Plant related
T001W-- Plants (WERKS)
T001L-- Storage Locations (LGORT)
Sales related
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)
regards,
srinivas
*reward for useful answers*

Can anybody tell me about SD Functionality and the main tables used in SD

Hi,
Can anybody tell me about SD Functionality and the main tables used in SD.
Thanks,
bsv.

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)
|
AR
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.
other tables and imp fields
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)
for sd go through the links
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
Reward points if useful
Regards
Anji

Mm flow and SD flow

Hi,
Cna any body explain what is mm flow and sd flow

HI,

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 Categorys 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.

Filling VBPA kunnr lifnr pernr parnr

Similar Messages

Maybe you are looking for