Vendor Master Transports

Hi All,
     I have created a Vendor with all address details in Dev system. When i transport the same to Testing environment I could no see the vendor from FK02 where i am getting the error as 'Address does not exists XXXXX'.
   I transported the vendor using manual transports with following objects.
R3TR   TABU  LFA1
Once this is transported to Test environement i could not see this vendor but when i check in LFA1 all the vendor details were updated at database level.
  I could find somehow that this might problem with ADRNR field from LFA1, but i am not sure how to go about this.
  Can you also please let me know how we maintain the Vendor master data between the systems?
Please help me in this regard...
Thanks
Suresh

hi,
you can not transport master data like vendor with transport system.
please use reports
1) rfbikr10 for sending in your dev-system
2) rfbikr20 for receiving in your test-system
pls reward point if answers are useful
thank you
Andreas
Message was edited by: Andreas Mann

Similar Messages

  • Transporting Vendor Master Records

    Is there any information, or process flow, that shows how to transport vendor master records from a cleansing client to production?

    Master data is not transported but created in the respective clients by either LSMW, BAPI programs, IDOC, BDC programs etc.
    If you're the MM person then you can discuss with your technical person on the method to be adopted. Once that is done you prepare the template & the data, provide the same to your technical person to do the upload alternatively you can do the same yourself.
    If you wish to know more about it, then I would strongly suggest that you use the search feature in MM forums or maybe even google to get an idea.

  • 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     Clerk’s Fax
    (TLFXS)     CHAR/31          Bring values over as is.
    LFB1     Clerk’s 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

  • Currency field in Vendor master

    Hi,
    There are vendors in the production client. But the vendors are without any purchasing view as it was uploaded for Fnance purpose. Now i have done the settings for purchasing view & transported to production. But the currency field is not coming for the vendors. What setting needs to be done to make that field active.
    Thanks
    John

    Hi
    Screen layout for the vendor master is controlled by the Vendor account group.
    Please see the screen layout for vendor account groups in the following menu
    SPRO-> Financial accounting -> Account receivable and Account payable -> Master data -> Preparation for creating Vendor master data -> Define account groups with screen layout
    Selct the vendor account group and go to details, where you select the Purchasing data and agian select Purchasing data , You can fine Purchase order currency field.Please make field as optional or Required entry as per your requirement.
    Regards
    Ramakrishna

  • Vendor Master bank Details Query

    Hi Gurus..
    i have developed a program from extracting vendor master and vendor A/P transaction.. in vendor master i have to get bank info like bank key and bank account number with respect to vendor number(lifnr).
    i have found the field name
    <b>bnka-BANKL    ---          Bank Key
    bsec-BANKN   ---          Bank account number  ...</b>Now the problem is i fighting hard to relate these fields with respect LIFNR..
    I'm Looking forward to here solutions from you all..
    thanks in Anticipation
    seriesnous is critical.. its has to be transported 2'marrow..
    full points will be rewarded for usefull solutions..
    chears,
    Chandru.S

    hi Chandru,
    you have to go to table LFBK, there you'll find all banks for all vendors. Pls. have a look at the table and come back if yuo have more questions. Pls. note that one vendor can have more bank accounts (but I am sure you have seen that in FK03).
    hope this helps
    ec

  • Control data in VENDOR MASTER..?

    hi gurus
    Can can anybody explain me about the how many views are there in vendor master like (material master-28 views).
    In Control data , what is the use of   --- GR based IV..?
    Please explain me clearly
    Thanks in advance
    sap-mm

    Hi,
    We can do MIRO(Invoice before GR) by deselecting the GR based IV block.
    We normally use it in case of Import process where we have to clear planned delivery cost(Customs duty,transportation charges) & then do the GR.
    But in domestic procurement, if we do IV without GR, we will not be able to get proper PO history.
    Hope this will solve your query.
    Reward if useful.
    Regards,
    Piyush

  • LSMW - Vendor Master DATA - IBAN management

    Dear SAP guru's,
    I'm trying to integrate the IBAN in vendor master data with my LSMW (batch recording techno).
    unfortunately, I do not have the IBAN information in structure BLFBK
    BLFBK Vendor Master Record Bank Data (Batch Input Structure)
    DO you know how we can integrate an IBAN by LSMW? Batch recording seems to be too risky..
    And I do not have the BBAN info, I only receive the IBAN...
    Thanks for your comments,
    Karim

    Hello,
    With batch, it is not possible to have IBAN details updated in Vendor master data. This should be done manually, when the IBAN
    number is entered system will do the validation checks as per the legal requirements using the specific Function modules for each country.
    Nevertheless, there is batch input program RFBIKR00 which is used for processing the following data:
    - Creating and changing vendor master data
    - Creating bank master data
    Please, note that the program RFBIKR00 cannot import master data which contains the usual account number and the IBAN at the same time. There has to be either an IBAN or an account number in the imported file.
    There are 2 scenarios how to get all the data imported, depending from
    the source system:
    1. If the source is also an SAP system, you can import the account numbers using the RFBIKR00 and then transport the IBANs separately using the ALE distribution (RFIBAN_ALE).
    2. If the source is a non SAP System, then file contains always two entries for a payment instruction. In the first one the account number will be imported, in the second one the IBAN. The functionality "IBAN without account number" is prerequisited and has to be active in the target system. In this scenario 2 payment instructions would be created in the vendor master(LFBK), one with the account number, another one with the IBAN.
    I hope this helps to resolve the problem.
    Thanks and regards,
    Suresh Jayanthi.

  • Customer & Vendor not transported via Plant tCodes WB01/2 or WB07/8

    Hello,
    We have change control enabled in our Dev, instance/clients SAP 4.7 IS-Retail , Basis 6.2
    Looking for help in understanding the necessary steps to transport the Plant Vendor and Customer records.
    The transport includes Plant records, but in the destination client the Customer and Vendor records that
    are automatically created via WB01/02 are not being included in the transports?
    Would appreciate any advice on how we transport the Vendor and Customer records that automatically
    get created via WB01/2 in the source client to the destination client.
    If we try to use XD01, XK01 the system enforces the Customer/Vendor records can only be maintained
    via the WB## transaction codes for IS-Retail.
    Have tried using WB07/08 and included in a transport, but still the Customer & Vendor master records
    are not being included in the transport.
    Any ideas?
    Regards, Ron.

    WB02 can not be used if the Customer and Vendor are not created implicitly via WB01, this
    is why the transport methodology is failing, See below. We were able to use WB01 on an existing
    Plant that had been transported, to maintain/create the Customer and Vendor relationship,
    but this produced inconsistent CO relationships that caused ME59 to fail.
    Note, you can not use XD01/XK01 for Customer/Vendor maintenance as it would pertain
    to Plant Customer Vendor relationships, this must be done via WB## t-codes.
    What we have found is that exporting and importing plants includes the Customer & Vendor
    coupled to the Plant. However the export and import WBTE,WBTI capability is not working
    properly as is similar to the transport capability.
    So, we have reverted to manually creating the Plant in each Instance Dev "IMG Gold Client",
    Test, Pro to complete this requirement. This has proven to work, but transports and or
    export/import have proven to not work as expected. Probably specific issue with SAP
    IS-Retail.

  • "Plant" in vendor master

    Hi All,
    I have created a new vendor account grp ZXYS for internal vendor i.e. our own plants which need to be created as vendors for the stock transport order process. For this I copied standard vendor account grp 0001 to create ZXYS.
    But now when I try to create a new vendor I do not see the field "plant" in the vendor master purchaing data --> Additinal purchasing data view.
    I can see that when I craete the vendor with vendor account grp LIEF.
    So should I copy LIEF to create ZINV or is there any other way of adding that field to ZXYS?
    BR,
    V S

    Check field selection settings for the account group ZXYS. May be Plant field is supressed.
    Transcation: OMSG
    Select account group ZXYS and click on the details button.
    Click on the Purchasing Data option, which is on the Field status block.
    Click on the Add. Purchasing Data option, which is on the Select group block.
    Check where plant field is supressed or not. If supressed, select Opention entry radio button and save.
    Then try to create vendors with ur account group ZXYS.

  • What are the important views or field in vendors master record

    All,
    We are converting two different companies into our SAP.  We are at blue printing stage.  I was assigned to gather vendor master data requirements in SAP.  I sent them all the fields that we are currently using in SAP.  I sent them a template of General, Company code data and purchasing views.  The legacy team is coming to meet with our it team one to one to discuss the importance of the fields.  Now my team manager asked us to submit a presentation about all the questions we should be asking the legacy team as well as the important information we should be discussing from SAP point of view.  Can someone guide me here please.  It's important.  
    Thanks,

    Hi The task is pretty simple. You would need to create a mapping from the legacy data to SAP data. You would go through every field of the legacy data and identify which field it will map to. there is nothing like important field. Ideally you would get all the fields. Identify the recon account that the vendors should go to.
    Hope this helps
    Points will be appreciated.
    Regards,
    Zaid Azam

  • Error in ALE Service While Creation of Vendor Master

    hi,
    I am using a scenario where a third party system is sending vendor master data to a R/3 system The file is picked up by the file adapter(sender) and mapped to IDOC format, using Idoc adapter (receiver). A Vendor is then created by posting the CREMAS03 IDOC into the R/3 system.
    Everything goes fine till the Idoc comes into the R/3 system. There in BD87(Idoc Status Monitor), getting the "Error in ALE Service" error. When expanded further the specific error is that of "Cross-system company code xxxx does not exist". What is generally the cause of this error and how would I resolve it?
    For those of you who have attended TBIT 40, this scenario is Example 1 - Creation of Vendor Master Data.
    Any help would be appreciated?
    regards,
    SK

    one more thing
    if you want to be sure that you're using the right data
    try to set your system to send the vendor data out
    first - send it from BD14
    and then you'll know which fields do you need
    if you do that take a look at segment E1LFB1M
    and check for BURKS
    Regards,
    michal

  • Creation of Business partner by using the vendor master

    Dear all ,
    I have a requirement as follows. I  Have already vendor master created  in MM .Now the requirement is  while creating Business partner I have to use this vendor as the business partner .
    Can experts suggest the possibility of this .
    Regards.
    Arjun.

    Hello Arjun,
    Yes, this feature also works in 4.7. What has happened is that in ECC 6.0 the BP functinality has been totally redefined with a lot of automations. As such, if properly configured then in ECC 6.0 there is no practical use of the FLBPD/FLBPC Tcodes. However, in 4.7, both these traqnsactions should be working fine. The SAP ntes that I have mentioned are however only for ECC 6.0.
    Kind regards,
    Suvarghya Dutta
    Edited by: Suvarghya Dutta on Nov 27, 2008 4:02 PM

  • Added new fields in vendor master in xk01 but data is not getting saved

    Hi experts,
    To add new fields in vendor master i have followed the following steps :
    1.) Appended a structure ZRTGS in LFA1 table with required fields and activated
    2.) Added new button in xk01( vendor master ) using spro -> logistics-general -> business partner -> vendors ->
    control ->adoption of customer's owaster data fields -> prepare modification free-enhancement of vendor master record
    Created a screen group ZR and defined label tab pages with function code ZRTGS and saved entries
    3.) Created a implementation for BADIs VENDOR_ADD_DATA and VENDOR_ADD_DATA_CS.
    4.) Created a program with my own subscreen for the required fields
    The button is getting displayed in XK01, XK02 and XK03 respectively. Whenever the button is clicked the subscreen with
    the fields is also displayed. But whenever i try to save the data in either XK01 or XK02 it is not getting saved in to the
    database table LFA1.
    Request your help in this regard.
    Thanks in Advance.

    Hi,
    You may need to check this include .
    EXIT_SAPMM06E_008  -->Import Data from Customer Subscreen for Purchasing Document
    Thanks,
    vamshi

  • Vendor master file report.

    Dear All,
    I always use S_ALR_87012089 display changes to vendors to check vendor master data if they are created or updated in accordance with proper approvals (not a workflow in SAP).
    Recently, I see other tcode S_ALR_87012090, but do not know what is its use.
    Can you please let me know detail about S_ALR_87012090.
    Thanks
    Ndhoan

    Hello,
    The program S_ALR_87012090 displays changes to the sensitive fields (such as Bank Account, Bank control key etc. configured defined by us). The reviewer can confirm or refuse the changes interactively from the list produced by this report.
    Thanks,
    Venu

  • Vendor master details report

    Dear all,
    We need to download all the vendor master data account groupwise from SAP. Is there any standard report available in SAP?? Like we have MM60 for material master data download.
    Regards,
    Santosh

    Dear Santosh,
    Please finf the path
    Logistic > Mat Management> Purchasing > Master data > Vendor > List display > MKVZ  Purchasing list.
    You will get the list as per your requirement.
    Reward if useful,
    Vivek Maitra

Maybe you are looking for