Regarding Street3 and Street 4 in Vendor Master

hi all,
I am trying to upload Vendor Master data through LSMW.
But When i am doing recording i am not getting the fields Street3 , Street4 and Street 5. I tried in Direct Input Method also. I am not getting that fields.
Please suggest any standard Program for uploading Vendor Master data and also Plz suggest any other method for uploading vendor master data for getting these fields also.
Regards
Rami Reddy

Hi Manesh
We are having trouble inputting any of the address fields. I have recorded and check the "use Central Address Management" field, but the Batch is not reading the data. Is there something else we have to do?
Thanks
Queenie

Similar Messages

Obligatory fields "iban" and "swift" in vendor master data creation

Hi,
I need a way to get obligatory iban and swift in vendor master data.
I need to check if iban and swift have been filled during creation or modification of a vendor (transactions XK01, MK01, FK01,XK02, MK02, FK02 ).
In user-exit ZXF05U01(function EXIT_SAPMF02K_001) I can't check iban and swift fields.
Do you know another way to solve my issue?
Thanks in advance. Stefano.

Hi Stefano,
swift codes are data from financial institute (and not vendor data). So try exit (CMOD) SAPLBANK (but I dont no if it will work!).
As i remember (at time iban where introduced), there was an exit to check consistency (mean "rules") to propose/create iban from account no of vendor. But i cant remember the name of this exit, so you may search in sap notes for this exit.
Best regards,
Christian

Bapi For creation and change for Vendor Master and Customer Master

I am looking for BAPI to create and change Vendor Master and Customer Master which will not take me to standard SAP transaction but will work in the background
Explanation: BAPI to delete material (BAPI_MATERIAL_DELETE) take you to standard SAP screen of T-Code MM06 but BAPI to create material (BAPI_MATERIAL_SAVEDATA) creates material in the background i.e. does not take you to standard SAP screen of T-Code MM01
So in my case (i.e. to create and change Vendor Master and Customer Master ) I want BAPI which would work like BAPI to create material (BAPI_MATERIAL_SAVEDATA)

For general information,to find BAPIs associated with any business object :
Transaction : BAPI - choose alphabetical tab - Find customer - (right side choose - tools - create bapi list and search ) , you will get all the BAPIs associated with this particular business object
Mathews

Vendor Master and Customer Master for FI AP/AR

hi FICO Gurus,
I am Sapna here and I have questions regarding the Mandatory fields for Vendor Master and Customer Master which would be mandatory for Running FI AP and AR. I am basically a MM Consultant but I have been asked to perform this role of Master Data at my current client.
I am quite familiar with the fact that these feilds are based on the needs of the bussiness and can be configured in IMG as required/optional or suppressed or diaplsy only.
What I am looking is
1. Are there any fileds list which is Mandatory for running FI AP/AR in global financial implemntation.
2. Also from FI Perspective what is Good to have/Recommended fields in Vendor Master and Cusotmer Master for Global Finacial implemtation.
Your help is greatly appreciated. Please point me in right direction...

OK all implementations are different so the client should have some imput here.
However you need to make sure certain address details are mandatory such as name, post code street and city.
You may always want an e mail address or phone number.
All AR & AP customer/ Vendors will need a recon account, so it is important there is one set up, but you also need to make sure in change mode this cannot be changed.
For Vendors you will require some kind of bank details and payment method.
For Customers if Dunning is being used you may need the Dunning Procedure and Accounting Clerk.
Also for a Customer there is the Sales Org view, and it is best to contact the SD consultant to see which fields are required here. The tax code, payment terms are normally mandatory.
For the Purchasing Org, I guess you would know about this...
Hope this helps.
Award points if useful.

Vendor Master Extraction from Legacy

Hi guys,
We have 2 different legacy systems here (4.5b and 4.6c) and I am trying to extract the vendor master from both of them and integrate them into the new mysap2004.
What is the best way to extract the vendor master along with the address , punchasing doc, bank details, partner functions,etc ? Any sample program for vendor master extraction is most welcome. Here is my extract layout.
ADDRESS
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
SZA1_D0100     Title (TITLE_MEDI)     CHAR/30          Not used
ADDR1_DATA     Name (NAME1)     CHAR/40          Bring values over as is.
ADDR1_DATA     Name (NAME 2)     CHAR/40          Bring values over as is.
ADDR1_DATA     Name (NAME 3)     CHAR/40          Bring values over as is.
ADDR1_DATA     Name (NAME 4)     CHAR/40          Bring values over as is.
ADDR1_DATA     Search Term 1 (SORT1)     CHAR/20          Convert to HPC methodology.
O-First 8 char. of vendor name
R- First 8 char. of vendor name
B- First 8 char. of vendor name
ADDR1_DATA     Search Term 2 (SORT2)     CHAR/20          Bring values over as is.
ADDR1_DATA     Street/House Number
(Street)     CHAR/60          Bring values over as is.
ADDR1_DATA     House Number
(HOUSE_NUM1)     CHAR/10          Bring values over as is.
ADDR1_DATA     Building (number or code)
(BUILDING)     CHAR/20          Bring values over as is.
ADDR1_DATA     Room or apartment number
(ROOMNUMBER)     CHAR/10          Bring values over as is.
ADDR1_DATA     Floor in building
(FLOOR)     CHAR/10          Bring values over as is.
ADDR1_DATA     c/o name
(NAME_CO)     CHAR/40          Bring values over as is.
ADDR1_DATA     Street 2
(STR_SUPPL1)     CHAR/40          Bring values over as is.
ADDR1_DATA     Street 3
(STR_SUPPL2)     CHAR/40          Bring values over as is.
ADDR1_DATA     Street 4
(STR_SUPPL3)     CHAR/40          Bring values over as is.
ADDR1_DATA     Street 5
(LOCATION)     CHAR/40          Bring values over as is.
ADDR1_DATA     City
(CITY1)     CHAR/40          Bring values over as is.
ADDR1_DATA     District
(CITY2)     CHAR/40          Bring values over as is.
ADDR1_DATA     City (different from postal city)
HOME_CITY     CHAR/40          Bring values over as is.
ADDR1_DATA     City postal code
(POST_CODE1)     CHAR/10          Zip Code. Bring values over as is.
ADDR1_DATA     Country
(COUNTRY)     CHAR/3          Bring values over as is.
ADDR1_DATA     Region (State, Province, County)
(REGION)     CHAR/3          E.g., NJ New Jersey, CO Colorado, etc.   Bring values over as is.
ADDR1_DATA     Time Zone
(TIME_ZONE)     CHAR/6          Bring values over as is.
ADDR1_DATA     Transportation Zone
(TRANSPZONE)     CHAR/10          Bring values over as is.
ADDR1_DATA     Regional Structure Group
(REGIOGROUP)     CHAR/8          Bring values over as is.
ADDR1_DATA     P. O. Box
(PO_BOX)     CHAR/10          Bring values over as is.
ADDR1_DATA     P.O. Box Postal Code
(POST_CODE2)     CHAR/10          Bring values over as is.
ADDR1_DATA     Language Key
(LANGU)     LANG/1          Bring values over as is.
SZA1_D0100     Telephone
(TEL_NUMBER)     CHAR/30          Bring values over as is.
SZA1_D0100     Telephone Number Extension
(TEL_EXTENS)     CHAR/10          Bring values over as is.
SZA1_D0100     Fax
(FAX_NUMBER)     CHAR/30          Bring values over as is.
SZA1_D0100     Fax Extension Number
(FAX_EXTENS)     CHAR/10          Bring values over as is.
SZA1_D0100     E-mail
(SMTP_ADDR)     CHAR/240          Bring values over as is.
ADDR1_DATA     Standard Communication Type
(DEFLT_COMM)     CHAR/3          Bring values over as is.
ADDR1_DATA     Data Line
(EXTENSION1)     CHAR/40          Not used.   Do not bring over field values.
Note: This field will be available to populate with other data during the conversion.
ADDR1_DATA     Telebox
(EXTENSION2     CHAR/40          Not used.   Do not bring over field values.
Note: This field will be available to populate with other data during the conversion.
ADDR1_DATA     Comments
(REMARK)     CHAR/50          Bring values over as is.
CONTROL
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
LFA1     Customer
(KUNNR)     CHAR/10          Bring values over as is.
LFA1     Authorization
(BEGRU)     CHAR/4          It is to be determined if this field will be used in the future.   If yes, bring values over as is from HPC and populate with vendor account group code for Foods.
LFA1     Trading Partner
(VBUND)     CHAR/6          Bring values over as is.
LFA1     Group Key
(KONZS)     CHAR/10          Not used
LFA1     Tax Code 1
(STCD1)     CHAR/16          Bring values over as is.
LFA1     Tax Code 2
(STCD2)     CHAR/11          Bring values over as is.
LFA1     Fiscal Address
(FISKN)     CHAR/10          Bring values over as is.
LFA1     Jurisdiction Code
(TXJCD)     CHAR/15          Bring values over as is.
LFA1     VAT Registration No.
(STCEG)     CHAR/20          Bring values over as is.
LFA1     Tax Office
(FISKU)     CHAR/10          Bring values over as is.
LFA1     Tax Number
(STENR)     CHAR/18          Bring values over as is.
LFA1     Industry
(BRSCH)     CHAR/4          Bring values over as is.
LFA1     Train Station
(BAHNS)     CHAR/25          Not used.
LFA1     Transportation Zone
(LZONE)     CHAR/10          Bring values over as is.
LFA1     Actual QM Sys.
(QSSYS)     CHAR/4          Bring values over as is.
LFA1     QM System To
(QSSYSDAT)     DATS/8          Bring values over as is.
LFA1     DAK
(J_1FDAK)     CHAR/8          Bring values over as is.
PAYMENT TRANSACTIONS
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
LFBK     Bank Country Key
(BANKS)     CHAR/3          Bring values over as is.
LFBK     Bank Key
(BANKL)     CHAR/15          Bring values over as is.
LFBK     Bank Account
(BANKN)     CHAR/18          Bring values over as is.
BNKA     Bank Name
(BANKA)     CHAR/60          Foods - Bring values over as is.
HPC Populate with Bank Account Number
LFA1     Alternative Payee
(LNRZA)     CHAR/10          Bring values over as is.
LFA1     Individual Spec.
(XZEMP)     CHAR/1          Bring values over as is.
LFA1     Spec. Per. Reference
(XLFZA)     CHAR/1          Bring values over as is.
ACCOUNTING INFORMATION ACCOUNTING
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
LFB1     Recon. Account
(AKONT)     CHAR/10          Bring values over as is.
LFB1     Sort Key
(ZUAWA)     CHAR/3          Bring values over as is.
LFB1     Head Office
(LNRZE)     CHAR/10          Bring values over as is.
LFB1     Authorization
(BEGRU)     CHAR/4          Bring values over as is.
LFB1     Cash Mgmnt Group
(FDGRV)     CHAR/10          Bring values over as is.
LFB1     Release Group
(FRGRP)     CHAR/4          Bring values over as is.
LFB1     Minority Indicator
(MINDK)     CHAR/3          Bring values over as is.
LFB1     Certification Date
(CERDT)
     DATS/8          Bring values over as is.
LFB1     Interest Indicator
(VZSKZ)     CHAR/2          Bring values over as is.
LFB1     Last Key Date
(ZINDT)     DATS/8          Bring values over as is.
LFB1     Interest Cycle
(ZINRT)     NUMC/2          Bring values over as is.
LFB1     Last Interest Run
(DATLZ)     DATS/8          Bring values over as is.
LFB1     Withholding Tax Code
(QSSKZ)     CHAR /2          Bring values over as is.
LFB1     Withholding Tax Country
(QLAND)     CHAR /3          Bring values over as is.
LFB1     Recipient Type
(QSREC)     CHAR /2          Bring values over as is.
LFB1     Exemption Number
(QSZNR)     CHAR /10          Bring values over as is.
LFB1     Valid Until
(QSZDT)     DATS/8          Bring values over as is.
LFB1     Exemption Authority
(QSBGR)     CHAR /1          Bring values over as is.
LFB1     Previous Account No.
(ALTKN)     CHAR /10          Do not bring over existing values. Will populate during vendor conversion when legacy vendor number is replaced by a new vendor number.
LFB1     Personnel Number
(PERNR)     NUMC/8          Bring values over as is.
PAYMENT TRANSACTIONS ACCOUNTING
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
LFB1     Payment Terms
(ZTERM)     CHAR/4          Refer to data mapping spreadsheet later in this spec.
LFB1     Tolerance Group
(TOGRU)     CHAR/4          Bring values over as is.
LFB1     Credit Memo Terms
(GUZTE)     CHAR/4          Bring values over as is.
LFB1     Chk. Double Inv.
(REPRF)     CHAR/1          Bring values over as is.
LFB1     Chk. Cashing Time
(KULTG)     DEC/3          Bring values over as is.
LFB1     Payment Methods
(ZWELS)     CHAR/10          Refer to data mapping spreadsheet later in this spec.
LFB1     Alternate Payee
(LNRZB)     CHAR/10          Bring values over as is.
LFB1     Individual Payment
(XPORE)     CHAR/1          Bring values over as is.
LFB1     Bill of Exchange Limit
(WEBTR)     CURR/13
Decimal/2     9999999999999.99     Bring values over as is.
LFB1     Payment Advance By EDI
(XEDIP)     CHAR/1          Bring values over as is.
LFB1     Payment Block
(ZAHLS)     CHAR/1          Bring values over as is.
LFB1     House Bank
(HBKID)     CHAR/5          Not used.   Do not bring forward existing values.
LFB1     Grouping Key
(ZGRUP)     CHAR/2          Bring values over as is.
LFB1     Payment Method Supplement
(UZAWE)     CHAR/2          Bring values over as is.
LFB1     Alternate Payee Indicator
(XLFZB)     CHAR/1          Bring values over as is.
LFB1     Tolerance Group
(TOGRR)     CHAR/4          Bring values over as is.
CORRESPONDENCE ACCOUNTING
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
LFB5     Dunning Procedure
(MAHNA)     CHAR/4          Bring values over as is.
LFB5     Dunning Recipient
(LFRMA)     CHAR/10          Bring values over as is.
LFB5     Last Dunned
(MADAT)     DATS/8          Bring values over as is.
LFB5     Dunning Clerk
(BUSAB)     CHAR/2          Bring values over as is.
LFB5     Dunning Block
(MANSP)     CHAR/1          Bring values over as is.
LFB5     Legal Dunning Proceedings
(GMVDT)     DATS/8          Bring values over as is.
LFB5     Dunning Level
(MAHNS)     NUMC/1          Bring values over as is.
LFB1     Grouping Key
(MGRUP)     CHAR/2          Bring values over as is.
LFB1     Local Processing
(XDEZV)     CHAR/1          Bring values over as is.
LFB1     Acct. Clerk
(BUSAB)     CHAR/2          Bring values over as is.
LFB1     Account with Vendor
(EIKTO)     CHAR/12          Bring values over as is.
LFB1     Clerk at Vendor
(ZSABE)     CHAR/15          Bring values over as is.
LFB1     Acct. Clk. Tel. No.
(TLFNS)     CHAR/30          Bring values over as is.
LFB1     Clerks Fax
(TLFXS)     CHAR/31          Bring values over as is.
LFB1     Clerks Internet
(INTAD)     CHAR/130          Bring values over as is.
LFB1     Account Memo
(KVERM)     CHAR/30          Bring values over as is.
PURCHASING DATA
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
LFM1     Order Currency
(WAERS)     CUKY/5          Bring values over as is.
LFM1     Terms of Payment
(ZTERM)     CHAR/4          Refer to data mapping spreadsheet later in this spec.
LFM1     Incoterms (Part 1)
(INCO1)     CHAR/3          Refer to data mapping spreadsheet later in this spec.
LFM1     Incoterms (Part 2)
(INCO2)
     CHAR/28          Bring values over as is.
LFM1     Minimum Order Value
(MINBW)     CURR/13
Decimal/2     9999999999999.99     Bring values over as is.
LFM1     Schema group, vendor
(KALSK)     CHAR/2          Bring values over as is.
LFM1     Pricing Date Cat.
(MEPRF)     CHAR/1          Bring values over as is.
LFM1     Order Optim. Rest
(BOPNR)     CHAR/4          Bring values over as is.
LFM1     Salesperson
(VERKF)     CHAR/30          Bring values over as is.
LFM1     Telephone
(TELF1)     CHAR/16          Bring values over as is.
LFM1     Acc. With Vendor
(EIKTO)     CHAR/12          Bring values over as is.
LFM1     GR. Based Inv. Verif.
(WEBRE)     CHAR/1          Bring values over as is.
LFM1     Auto.Eval. GR Setmt. Del.
(XERSY)     CHAR/1          Bring values over as is.
LFM1     Auto.Eval. GR Setmt. Ret.
(XERSR)     CHAR/1          Bring values over as is.
LFM1     Acknowledgement Reqd.
(KZABS)     CHAR/1          Bring values over as is.
LFM1     Automatic Purchase Order
(KZAUT)     CHAR/1          Bring values over as is.
LFM1     Subsequent Settlement
(BOLRE)     CHAR/1          Bring values over as is.
LFM1     Subseq. Sett. Index
(BOIND)     CHAR/1          Bring values over as is.
LFM1     B. Vol.Comp./Ag. Nec.
(UMSAE)     CHAR/1          Bring values over as is.
LFM1     Doc. Index Active
(BLIND)     CHAR/1          Bring values over as is.
LFM1     Returns Vendor
(KZRET)     CHAR/1          Bring values over as is.
LFM1     Srv.-Based Inv. Ver.
(LEBRE)     CHAR/1          Bring values over as is.
LFM1     ABC Indicator
(LFABC)     CHAR/1          Bring values over as is.
LFM1     Mode Of Transport-Border
(EXPVZ)     CHAR/1          Bring values over as is.
LFM1     Office of Entry
(ZOLLA)     CHAR/6          Bring values over as is.
LFM1     Sort Criterion
(SKRIT)     CHAR/1          Bring values over as is.
LFM1     PROACT Control Prof.
(PAPRF)     CHAR/4          Bring values over as is.
LFM1     Revaluation Allowed
(XNBWY)     CHAR/1          Bring values over as is.
LFM1     Grant Discount In Kind
(NRGEW)     CHAR/1          Bring values over as is.
LFM1     Relevant for Price Determination
(PRFRE)     CHAR/1          Bring values over as is.
LFM1     Relevant for Agency Business
(AGREL)     CHAR/1          Bring values over as is.
LFM1     Shipping Conditions
(VSBED)     CHAR/2          Bring values over as is.
LFM1     Purchasing Group
(EKGRP)     CHAR/3          Bring values over as is.
LFM1     Planned Delivery Time
(PLIFZ)     DEC/3          Bring values over as is.
LFM1     Confirmation Control
(BSTAE)     CHAR/4          Bring values over as is.
LFM1     Unit of Measure Group
(MEGRU)     CHAR/4          Bring values over as is.
LFM1     Rounding Profile
(RDPRF)     CHAR/4          Bring values over as is.
LFM1     Price Marking Agreed
(LIPRE)     CHAR/2          Bring values over as is.
LFM1     Rack jobbing service agreed
(LISER)     CHAR/1          Bring values over as is.
LFM1     Order entry by vendor
(LIBES)     CHAR/1          Bring values over as is.
LFM1     Serv. Level
(VENSL)     DEC/4
Decimal/1          Bring values over as is.
PARTNER FUNCTIONS
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
WYT3     Partner Function
(PARVW)     CHAR/2          Bring values over as is.
WRF02K     Number (Partner)
(GPARN)     CHAR/10          Map to new partner number in vendor correlation table.
ALTERNATE DATA
(Purchasing Data)
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
LFM2     Order Currency
(WAERS)     CUKY/5          Bring values over as is.
LFM2     Terms of Payment
(ZTERM)     CHAR/4          Refer to data mapping spreadsheet later in this spec.
LFM2     Incoterms (Part 1)
(INCO1)     CHAR/3          Refer to data mapping spreadsheet later in this spec.
LFM2     Incoterms (Part 2)
(INCO2)
     CHAR/28          Bring values over as is.
LFM2     Minimum Order Value
(MINBW)     CURR/13
Decimal/2          Bring values over as is.
LFM2     Schema group, vendor
(KALSK)     CHAR/2          Bring values over as is.
LFM2     Pricing Date Cat.
(MEPRF)     CHAR/1          Bring values over as is.
LFM2     Order Optim. Rest
(BOPNR)     CHAR/4          Bring values over as is.
LFM2     Salesperson
(VERKF)     CHAR/30          Bring values over as is.
LFM2     Telephone
(TELF1)     CHAR/16          Bring values over as is.
LFM2     Acc. With Vendor
(EIKTO)     CHAR/12          Bring values over as is.
LFM2     GR. Based Inv. Verif.
(WEBRE)     CHAR/1          Bring values over as is.
LFM2     Auto.Eval. GR Setmt. Del.
(XERSY)     CHAR/1          Bring values over as is.
LFM2     Auto.Eval. GR Setmt. Ret.
(XERSR)     CHAR/1          Bring values over as is.
LFM2     Acknowledgement Reqd.
(KZABS)     CHAR/1          Bring values over as is.
LFM2     Automatic Purchase Order
(KZAUT)     CHAR/1          Bring values over as is.
LFM2     Subsequent Settlement
(BOLRE)     CHAR/1          Bring values over as is.
LFM2     Subseq. Sett. Index
(BOIND)     CHAR/1          Bring values over as is.
LFM2     B. Vol.Comp./Ag. Nec.
(UMSAE)     CHAR/1          Bring values over as is.
LFM2     Doc. Index Active
(BLIND)     CHAR/1          Bring values over as is.
LFM2     Returns Vendor
(KZRET)     CHAR/1          Bring values over as is.
LFM2     Srv.-Based Inv. Ver.
(LEBRE)     CHAR/1          Bring values over as is.
LFM2     ABC Indicator
(LFABC)     CHAR/1          Bring values over as is.
LFM2     Mode Of Transport-Border
(EXPVZ)     CHAR/1          Bring values over as is.
LFM2     Office of Entry
(ZOLLA)     CHAR/6          Bring values over as is.
LFM2     Sort Criterion
(SKRIT)     CHAR/1          Bring values over as is.
LFM2     PROACT Control Prof.
(PAPRF)     CHAR/4          Bring values over as is.
LFM2     Revaluation Allowed
(XNBWY)     CHAR/1          Bring values over as is.
LFM2     Grant Discount In Kind
(NRGEW)     CHAR/1          Bring values over as is.
LFM2     Relevant for Price Determination
(PRFRE)     CHAR/1          Bring values over as is.
LFM2     Relevant for Agency Business
(AGREL)     CHAR/1          Bring values over as is.
LFM2     Shipping Conditions
(VSBED)     CHAR/2          Bring values over as is.
LFM2     Purchasing Group
(EKGRP)     CHAR/3          Bring values over as is.
LFM2     Planned Delivery Time
(PLIFZ)     DEC/3          Bring values over as is.
LFM2     Confirmation Control
(BSTAE)     CHAR/4          Bring values over as is.
LFM2     Unit of Measure Group
(MEGRU)     CHAR/4          Bring values over as is.
LFM2     Rounding Profile
(RDPRF)     CHAR/4          Bring values over as is.
LFM2     Price Marking Agreed
(LIPRE)     CHAR/2          Bring values over as is.
LFM2     Rack jobbing service agreed
(LISER)     CHAR/1          Bring values over as is.
LFM2     Order entry by vendor
(LIBES)     CHAR/1          Bring values over as is.
LFM2     Serv. Level
(VENSL)     DEC/4
Decimal/1          Bring values over as is.
ALTERNATE DATA
(Partner Functions)
Source File /Table Name     Field Name     Field Type / Length     Format     Rule / Logic
WYT3     Partner Function
(PARVW)     CHAR/2          Bring values over as is.
WRF02K     Number (Partner)
(GPARN)     CHAR/10          Map to new partner number in vendor correlation table.

Hi Shareen,
Have you looked Master Data Distribution (ALE) for Vendor since your legacy system are SAP?
Please check t/code BD14 (Send Vendor Master Data) and BD15 (Get Vendor Master Data).
Hope this will give you an idea.
Regards,
Ferry Lianto

Partner Function in Vendor Master With Internal Number Range

Hello Friends,
I am creating vendor master record with internal no range.I wanted following clarifications.
1.In partner function screen, I want to have same vendor no which i am creating to be assigned automatically to VN.OA PI and GS funtions at the time of its master creation.This is not happening in my case
2.Partner function like VN,OA,PI and GS does not appear automatically whereas i have to select it manually.
Regards
Vivek

Hi,
During defining the partner Schema, please follow the process:
a.Create partner Schema
b.After creation of partner Schema, select your partner Schema and click u201Cpartner roles in schemau201D and you will have next screen
Now for Partner function like VN,OA,PI and GS as you required and select the check box of mandatory
and save.
Now try creating Vendor and you will have Partner function like VN,OA,PI and GS in vendor master.
Note: The following configuration steps for Vendor master are:
1. Create Vendor Account Group.OBD3
2. Maintain Number Ranges from Vendor account Group:XKN1,
3.Assignment of Number ranges to Account Group,OBAS
4.Partner Function: SPRO->MM->Purcahsing->Partner Determination-> partner roles->Permissible partner role sper account group
5.Partner Schema:
SPRO->MM->Purcahsing->Partner Determination->Partner setting in Vendor master record-> Define partner Schema
6.Assgin partner schema to accont Group
SPRO->MM->Purcahsing->Partner Determination->Partner setting in Vendor master record-> Assgin partner schema to account Group
Regards,
Biju K

Customer Master / Vendor master Creation

Hi Folks,
I have a requirement that the whenever Customer / vendor is created or changed, then there needs to be a mail sent for the same.
We are currently using the user exit : EXIT_SAPMF02D_001 for customer creation and user xit : EXIT_SAPMF02K_001 for vendor.
The issue :
When the new Cust / Vend is created, the user exit is called. The issue is that the "Customer number" / "Vendor number " is blank as the number is generated by the system after the user exit is over. So the mail sent is having Blank Ven / Cust number which is not desired.
IF anyone knows any other User exit / Badi that can be used for this purpose. Or if there is a business object for the Customer abd vendor master, whose event is raised by the SAP transaction when Cust / vendor is created with the customer number passed to the event, then kindly let me know. I can then create a workflow for the same.
P.S: There is no issue when the customer is changed as the customer number comes in the above exit.
Thanks and Regards,
Anuj.

Hi,
I think you can use Business transaction events for this.
BTE 1320 and 1321 for Customer Master
BTE 1420 and 1421 for Vendor Master
And FYI,
http://help.sap.com/saphelp_46c/helpdata/en/63/ed2c7dd435d1118b3f0060b03ca329/frameset.htm
Hope this helps..
Sri

How to check which currency is assigned to Bank in Vendor Master

Hi,
Good Morning to All.
We have a requirement. We like to know the details for currencies in Bank accounts maintained in Vendor Master.
For ex.
For XYZ vendor we have assigned ABC bank for country GB along with the IBAN,SWIFT, A/C No, etc....now how can we be sure while making payment to vendor that the bank account maintained in vendor master is relevant to currency USD and not to GBP or any other curreny.
As we are planing to make automation payment to vendors, we are not able to find any currency linked to Bank account in vendor master.
We have more that 10K vendors and its impossible to check with all of them regarding the currency and update the vendor master.
Do we have any way to find out the link between the Vendors Bank Account & Currency the bank account tagged too.
Thanks in advance for your assistance.
Do revert.
Rex

Hi Rex,
The Currency in which the Vendor has maintained the Bank account is an information that you will get only from the vendor.. and then you can update in the vendor master.. From SAP system you will not get this info anywhere..
In FBZP.. we maintain Our Bank Accounts and not the Vendor Bank Accounts.. For Vendors, we only maintain the Bank key in our system in T-Code Fi01 and his Bank details in the vendor Master.
When you update the Partner Bank Type in vendor master with Currency in which the Vendor has maintained his bank account with the Bank, you can write the logic in BTE to pick up logically in APP.
Hope it clarifies..
Regards,
SAPFICO

Validate Terms of Payment in MIRO against vendor master

Dear All,
I have a requirement to Validate Terms of payment in MIRO with Vendor master data. I am using INVOICE_UPDATE BADI to check if Terms of payment in MIRO is same as Vendor master table LFB1, However I also need to check days which is not in LFB1,
How do I validate MIRO -> ZTERM and Days with Vendor master is there any function module ? I checked T052 table but ZTERM is not the only primary key and suggestions please ?
Regards,
soyunee
Edited by: soyunee on Jun 23, 2010 11:43 AM

Hi,
See the the SAP documentation of Daylimit.
For terms of payment which depend on whether or not the baseline date is
after or before the 15th of the month, you can define a two-part payment
term under the same terms of payment key. The terms of payment key is
expanded by the day limit entered here. Thus there are two entries in
which different terms can be specified.
In your case,
if rbkp-bldat is between 1st and 5th of the month, extract
data related to t052-ztagg = '05'.
If rbkp-bldat is between 6th and 20th of the month, extract
data related to t052-ztagg = '20'.
if rbkp-bldat is between 21st and end of month, extract
data related to t052-ztagg = '31'
Regards
Vinod

Vendor Master transactions from external application

Hi..
I have to Create(XK01), Change(XK02), Block(XK05) and Delete(XK06) Vendor Master from an external application.
This application is able to interact with SAP using RFC/BAPI and IDOC, but I only found BDC as a way to achieve this. How does this work? Can I 'wrap' a BDC into a BAPI and remote-enabled this BAPI to my application?
All help welcome (and examples too
Cheers,
Adzy

Hi Andreas,
Thank you for your reply.
BAPI_VENDOR_CREATE seems to be used in a dialog; the response was:
"RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user"
I going back digging a bit more...
Thank you and regards,
Adzy

Vendor master data changes

Hi all,
Please help me with some useful information regarding the history of master data creationa and changes. I need to create a query for creation and changes of vendor master data. Data for creation of the vendor master data are saved in LFA1 but for changes I cannot find table.
Thank you,
Desimira

Hi,
You can use the standard report for Vendor master data changes, S_ALR_87012089 - Display Changes to Vendors.
Regards,
SAPFICO

Updating SWIFT Code in Vendor Master with IDoc

Hello,
I am facing the following problem.
We are using IDoc CREMAS04 to update vendor master data. Now we also would like to use the SWIFT code. I have seen that there is a SWIFT field in the IDoc in segment E1LFBKM in the CREMAS04 IDoc. However the SWIFT field in vendor master data is still empty after transferring the IDoc.
Any idea why the value in the SWIFT field of CREMAS04 IDoc is not transferred to the vendor master data? Are there any other approaches I could follow?
Thank you so much for your help!

Hi Florian,
Not sure if this will answer your question but the swift code is part of the bank master and not the vendor master.
You can check via de Bank data button in de vendor master or via FI03 for the specific bank country and bank key fi the Swift code is in there.
If not or you already checked the above this answer will be no help and i think you really have to debug/analyze to see what goes wrong.
Regards,
Mike

Access Vendor Master

Dear all,
In our project we need to create, modify and read vendor master data in SAP ECC 5.0. Can anybody help to give the following information or a reference to relevant documentation?
1. The tables which contain the vendor master.
2. The BOR object representing vendor.
3. The BAPI and function module to access the data.
4. Vendor-related workflow
Many Thanks + Best Regards
Jerome

Dear Jerome,
Tables:
LFA1 Vendor Master (General Section)
LFAS Vendor master (VAT registration numbers general section)
LFAT Vendor master record (tax groupings)
LFB1 Vendor Master (Company Code)
LFB5 Vendor master (dunning data)
LFBK Vendor Master (Bank Details)
LFBW Vendor master record (withholding tax types) X
LFC1 Vendor master (transaction figures)
LFC3 Vendor master (special G/L transaction figures)
LFEI Vendor Master: Preference for Import and Export
LFLR Vendor Master Record: Supply Regions
LFM1 Vendor master record purchasing organization data
LFM2 Vendor Master Record: Purchasing Data
LFMC Vendor master (short texts for condition types)
BOR Objects:
BUS3008 Vendor account
LFA1 Vendor
LFB1 Company code vendor
LFM1 Purchasing organization vendor
MDMLFA1 Vendor (MDM)
BAPI:
BAPI_VENDOR_GETDETAIL - Vendor Detail Information
BAPI_CREDITOR_GETDETAIL - Vendor Details
Vendor-related workflow:
Refer to the above business objects.
Regards,
Naveen.

Infotype to link Personnel Number with Vendor Master Record

Hi All,
pls help me what infotype to link Personnel Number with Vendor Master Record in AP module.
Customer require when Create Employee then system automatic gernerate Vendor Master.
pls help us.
Thanks

Hi,
PRAA works absolutely fine. I have external number range for vendors.
There is an option so that you can create HR accounts in vendor accounts
Path:Accounting> Financial accounting>Travel
management>Personal-Related Master Data> Create Vendors (tr.code PRAA)
Look at this description:
From the HR master data, this program creates a batch input session for
maintaining person-specific vendor master records.
The report can process vendor master records as follows:
o Initial set up (create/add missing company code segment)
o Uupdate (change completely according to vendor and HR reference)
o Change (only according to HR master data, for example, name
Block
The following infotypes from HR master data are taken into account for
the key date specified:
o Actions (Infotype 0000)
o Organizational Assignment (Infotype 0001)
o Personal Data (Infotype 0002)
o Permanent Residence (Infotype 0006 Subtype 1)
o Bank Details (Infotype 0009 Subtype 0 or 2)
All other required data is taken from a reference vendor that you can
specify as a parameter when you start the program. Note that for the
reference vendor, reference data must exist for all company codes that
are applicable according to HR master data. Since program RPRAPA00 cannot
assign vendor master record numbers externally when creating
vendor master records, you must be sure that the reference vendor is
assigned to an account group that requires internal number assignment.
If no house bank is specified in the reference vendor, this is
determined via feature TRVHB (Implementation guide for 'Travel Expenses'
-> Transfer to Data Medium Exchange -> Set up Feature for Determining
House Bank according to the employee's organizational situation.
The link between the HR employee's master record and the corresponding
vendor master record is set up by entering the personnel number in the
company code segment of the vendor master record.
General program flow
Program RPRAPA00 creates a sequential work file in the specified
directory. Ensure that you use a global directory that can be accessed
by all application servers; a directory is automatically proposed. The
work file is later transformed into a batch input session by the
subsequent program RFBIKR00, which is started automatically.
In test run mode this program delivers information messages which
document the creation of a batch input session. Since each information
message must be confirmed manually, the test run should only be
performed for a small number of personnel numbers.
In productive run mode, however, the program RFBIKR00 is automatically
started as a job; the information mentioned above is stored in the job
log in this case.
Initial setup of vendor master records
Corresponding vendor master records are created from the infotypes
listed above and the non-HR-specific information from the reference
vendor. During the process, the personnel number is stored in the
company code segment of the vendor master record. Persons who already
have a vendor master record with corresponding personnel number are
rejected in this run.
If a vendor master record already exists for a personnel number, but
without a company code segment for the company code in which the
employee exists at the key date entered, the program adds the required
company code segment to the vendor master record. You must however
activate the checkbox "Create new company code segment for existing
vendor master records".
The HR master data used is the info type record valid on the key date
entered.
Update of vendor master records
The corresponding vendor master records are updated from the infotypes
listed above and the non-HR-specific information from the reference
vendor. Persons who already have a vendor master record with
corresponding personnel number are rejected in this run. The system uses
HR master data from the infotype records valid for the key date.
Change vendor master records according to HR master data
All HR-specific data is changed in the vendor master records for
personnel numbers that have changes since the date recorded under '...
with last change since'. The system uses HR master data again from the
infotype records valid for the key date specified.
Block vendor master records
All vendor master records which correspond with the selected personnel
numbers are blocked for posting.
User exits
For the following situations, two empty routines are supplied in the
includes RPRAPAEX and RPRAPAEX&H5F001 which you can adapt to your
requirements.
o The employee's last name is entered in the sort field in the vendor
master record. If you do not want this to happen, you can program
the situation you want in the user exit routine
'set&H5Fmc&H5Ffield&H5Fby&H5Fuser'.
o If the address editing in the vendor master record does not suit
your requirements, it can also be changed. For this purpose you have
the user exit routine 'set&H5Faddress&H5Fby&H5Fuser'.
o If you want to assign numbers to the vendor master records to be
created via external number assignment (for example, vendor master
record number &H3D personnel number), you can adjust the user exit
routing 'SET&H5FVENDOR&H5FNO&H5FBY&H5FUSER' (in include RPRAPAEX&H5F00). Note
that
the account group of the reference vendor must also have external
number assignment.
Note that in each case a thorough knowledge of the programming
language
ABAP/4 is necessary.
Set up vendor master records in a separate system
The distribution of personnel master data from a HR system to an FI
system is a prerequisite for creating, changing, and blocking vendor
master records.
In the section Master Data Distribution (link to separate HR unit) of
the ALE IMG, an explanation is given regarding the way in which the
FI
System is supplied with the relevant employee data from the HR System
In the FI System, report RPRAPA00 described here can be used to
create,
change, and block vendor master records.
Other wise try with VPE1 t.code.
Regards
Devi

Vendor Master BADI

First time working on Badi ...I need to enhance the vendor master screen ( xk01 ) with some fields . I m following this link to implement the badi vendor_add_data_bcs...
http://help.sap.com/saphelp_nw04/helpdata/en/9d/12233a0edd7978e10000000a11402f/frameset.htm
but I m stuck on the 4th step under 'Defining Screen Enhancements' :
how to create the Subscreen area for this standard program of vendor master ....through se51 ...if i try it says that standard object ( SAPMF02..) cant be changed ...then how to create the subscreen and link it to the program ???
Message was edited by: SAP BEE

Hi Stacie!
You need to implement both BADIs. Have a look at documentation of BADIs in SE18 (on general and method level) to get some more hints (ensure that you have prepared modification-free enhancement of vendor master in customizing...).
Methods SET_DATA, GET_DATA of VENDOR_ADD_DATA_CS and customizing of vendor master->Transfer Customer Master Data Fields is needed for field filling (/reading).
New definitions of BADIs would be a modification - then you can modify source code directly.
So all changes should be possible without modifications.
Regards,
Christian

Regarding Street3 and Street 4 in Vendor Master

Similar Messages

Maybe you are looking for