4.5B server - Vendor Master

I have this same question posted in the SD forum but I think this would be a better place to ask this question (my apologies for the double post).
I am working in a 4.5B environment and coming across this situation.  So far I have tried using OMSG and made carrier details optional and mandatory but these fields do not show up when trying to create a new vendor.  I have tried doing this in 6.0 and it works fine.  My question from my original post is below...
I am trying to get fields DLGRP (ServAgntProcGrp ) and SCACD (SCAC) on my vendor master so I can assign carriers their proper group and SCAC code but can't figure it out. pts rewarded for any help.
thank you!

Hey
There is no as such difference in different versions in this regard.
Although field selection is not dependent on account group but also other parameters like purchase organization, transaction used etc.
Pl verify if this is the case.
Thx
Dilip sadh

Similar Messages

  • Vendor master Creation in Development Server and Production Server - ASAP

    < MODERATOR:  Message locked.  Please read the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] before posting next time. >
    Hello everyone,
    I just want to know that how to transfer the vendor accounts or vendor master data from dev client to Prod client?
    Vendor accounts are already in the dev client, created mannually, any one please guide me how  to transfer these vendor accounts in the prod server, without the USE OF LSMW.
    Please Reply ASAP
    Thanks
    M

    Hi
    Your understanding is correct.
    Development -
    > Quality
    Move TRs from Development to Quality till the time it is working as expected by business / comitted to business....
    Development -
    > Production
    Once the results in Quality (post UAT) are satisfactory, move the TRs from development to Production....
    Good Luck !!!!
    Kumarpal Jain.

  • 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

  • Error while Importing Vendor Master records

    I get the following error when importing vendor Master records into the MDM repositorry
    Cannot import qualifiers because the qualified lookup field is not mapped.
    I noticed that the file I'm importing contains 1000 vendors. However the qualified lookup table "PHONE" for the vendors contain only 388 records.
    After I imported the records I found that there was only 389 records in the repository.
    I'm using standard map provided by SAP.
    I ran the import again but this time I unmapped all fields for the qualified update.
    Now the Import Manager uploaded the remaining 613 records.
    I would like to know whether how I can load 1000 records in one load rather than having to go through the file twice.
    This is important since I want to use the import manager server for my loads.
    Thanks
    manoj

    Hi Manoj,
    Try the following options.
    1. In the Import Manager, Select Configuration->Options
    set <b>"Merge qualified links using matching qualifiers value to Off"</b>
    2. In the Map Fields/Values tab in Import manager, select the qualified field in which you are trying to import, right clik on the field->select Set Qualified Update -> Update -> Select All available qualifiers into Matching qualifiers->
    New Links- Create
    Existing Links -> Update (All Mapped Qualifiers).
    Hope this should solve your problem.
    Thanks and Regards
    Subbu.

  • User Exit/ BADI during creation of vendor master

    Dear Friends,
    During creation of vendormaster if the with holding tax is maintained then PAN no. field should be made mandatory.
    So far I know this can't done through standard field selection of vendor master. So this is to be done through BADI/User exit. Please provide me the same where in run time I can get PAN no field. It comes from the excise table.
    Regards

    First try for any Customization is available.
    If not we can achieve with enhancement point.
    Try to find out an implicit enhancement point on PAI event of the screen there validate for the "PAN No"
    if the "PAN No" is blank raise an error message & EXIT from the PAI.
    It would serve your purpose.
    Regards.
    Abhijit

  • Creation of Vendor Master Data

    Hi,
    In my company they are currently using this process to create Vendor Master Data: The Vendor Master Data is created in the Production Server and refreshed to Development Server and to Quality Server, using ALE.
    Is this the right process? If not can you let me know the steps to create Vendor Master Data.
    regards,
    raj

    Hi Raj,
    ALE and IDoc is the best way to transfer master data between SAP system. They have excellent error handling and reprocessing capabilities (Recommended by SAP).
    In order to automate the vendor master data transfer, you need to do the following steps.
    1. Create Logical System (if not available) for PROD, QA and DEV system.
    2. Create RFC Destination (SM59) from PROD to QA and DEV system.
    3. Create Distribution Model from PROD to QA/DEV (BD64) for message type CREMAS (Vendor Master).  
    4. Create Partner Profile (WE20) for message type CREMAS in PROD, QA and DEV system.
    5. Execute transaction code BD14 (Send Vendor) from PROD to QA and DEV system.
    6. To monitor the IDoc, you can use transaction code WE02.
    If you are not familiar with ALE/IDoc setup, please work with technical folk.
    Hope this will help and give an idea.
    Regards,
    Ferry Lianto

  • Data upload Vendor Master Chinese character from Excel does not upload

    Hi Gurus,
    We are trying to upload Vendor Master from Excel sheet.
    The Chinese characters in excel sheet is not getting uploaded.
    After upload, we see in SAP as ????? for these Chinese character.
    Could any one inform what setting I may need to change?
    Thanks and Best Regards,
    Mohan

    Hi Bala,
    Goto he Initial screen of SAP and click the ALT+F12    costomizating of local setup.the choose the options-->choose the I18N Tab in that POP up and check the Activate the multi byte support.
    press Apply and OK.
    close the  SAP Log on and Re-loag on.if u r not closing the Logon screen the changes wiil not effect.
    or
    click on the log on SAP and choose the server  name -->right click ->Properties>chose the log on language as chanies .-->Apply and Logon.
    Now u can eassily Upload to the Excel in checnies language.
    Thanks & REgards,
    Nelson.

  • Payment term in PO to be picked from Payt trans a/c of Vendor Master

    Hi ,
    In standard scenario Payment Term in Purchase Order is automatically picked up from Purchasing data of Vendor Master.
    Our requirement is Payment Term in Purchase Order should get picked up from Payment Transaction view of vendor master rather than from Purchasing data of Vendor Master.
    Is there any user exit or customization to achieve this.
    Please help.
    Regds,
    Ritesh

    there are payment terms at comapny code level AND purchasing org level, because you may get vendors for which you dont need purchasing views, such as customs or restaurants, where you never place a purchase order at. And other vendors like goods suppliers may never need company code views because you will never pay them.
    So each view serves its own purpose.
    It is not possible to just ignore maintenance at one level and get the payment term for an other organisation.
    Especially as you can have several purchasing organisations within one company (if you purchasing wants to differentiate purchases of direct material from MRO purchasing) or you have one purchasing org for several company codes.
    And not always is the payment term equal then.
    If you are certain that the company code payment term is always equal to purchasing org payment term, then copy it over with mass maintenance and everything is fine.

  • Automatic Payment Run - Alternate Bank Account in Vendor Master

    Dear Forum,
    We have a situation where the users want the alternate bank accounts to be maintained in the Vendor Masters and also to select this alternate bank account while doing the automatic payment run thru F110. While we can maintain more than one bank account in the Vendor Master, but how to select the alternate one during payment run. Your help would be highly appreciated.
    Regards

    Hi...
    As per your issue while runing APP in F110 once complete parameters
    And go to Edit praposal and double click vendor and double click on line items than it will displays the one more screen there select Reallocate button there you can enter your respective bank details.
    Otherwise there is a Business Transaction Event 1810. You can see the code, looks like you  need to replicate the vendor bank details with link to a company code.
    Note:
    Assign Multiple Bank Accounts in the Vendor Master
    Your SAP system provides the functionality to store and use
    information from multiple vendor bank accounts in the Payment
    transactions screen of the vendor master general data via
    transaction FK03 (Figure 1). Figure 1 reflects the bank type
    determination logic I used in the vendor master, using the
    three-digit International Organization for Standardization (ISO)
    currency code as the Bank type.
    Figure 1 Bank details vendor master
    You can use the BnkT (bank type) field in the vendor master to
    enter text differentiators for identifying the vendoru2019s bank
    accounts. If you leave the bank type field blank against a bank
    account in the vendor master, then it serves as the default bank
    if the bank type information is missing in the vendor invoice.
    You may want to leave this field blank if the vendor has only
    one bank account and you want the system to select that bank
    account for all payments.
    If the bank type is blank for multiple bank accounts, then the
    system looks for the first bank account with the blank bank type
    in the vendor master to use as the default. You are not required
    to define the text values u2014 in my example, INR, SGD, and USD u2014
    elsewhere in your SAP system. The field allows any value up to a
    length of four characters. Iu2019ll demonstrate the use of bank type
    with vendor invoice later on.
    The system performs a check at the time of invoice creation on
    the bank type value used in the vendor invoice against the bank
    type values used in the vendor master. If you have not defined
    the bank type value in the vendor master prior to using it in
    the vendor invoice, the system shows an error message. The
    system performs the check to ensure that you are using a bank
    type value in the vendor invoice against which it can find a
    bank account in the vendor master. Otherwise, the system cannot
    determine a bank account for making payments to the vendor.
    Prerequisites for Vendor Bank Selection
    You need to take care of a few configuration prerequisites before
    you can use vendor bank selection in the automated payment
    functionality.
    1. Check the Bank details check box in the payment method as
    defined at the country level in transaction FBZP. This ensures
    the selection of the bank details from the vendor master at the
    time of the automatic payment run. If you donu2019t do this, the
    system does not copy the bank details into the payment IDoc that
    it creates as a result of the automated payment run (transaction
    F110).
    2. Make the Bank Business Partners field optional in the field
    status group attached to the vendoru2019s reconciliation G/L account
    by selecting the button under Opt. Entry for this field. This
    field maps to the Part.bank type (partner bank type) field in
    the vendor invoice. If the Bank Business Partners field is not
    optional and is in a suppressed state, then you cannot input the
    partner bank type field in the vendor invoice.
    I hope it will helps you....
    Regards
    vamsi

  • Terms of payment in vendor master

    Can we have different terms of payment in vendor master? if yes what is the use of it?

    you can have payment terms at company code level and payment terms at purchasing org level.
    Company code level payment terms come into the game if finance posts invoices for which you do not have any purchase order.
    In a purchase order the payment terms from purchasing org view are taken.
    2fields are needed because vendors like a restaurant may not need purchasing views, you never create a purchase order. But finance may have to pay a bill.
    And the other way around, you may have vendors with purchasing view, that do not need company code data, as they serve only purchasing needs as order address or goods supplier, but the invoice is posted to the main vendor.

  • How to accept changes in Vendor master record as an accounting clerk?

    I made some changes in vendor master records and they are yet to be confirmed by accounting clerk!! so , how can I do that in my development system?

    Hi,
    I guess you posted your query in wrong forum.
    This forum is related to tool Test Data Migration Server (TDMS) which is used to transfer reduced set of data from a production system to a test or quality system.
    In case you are using TDMS and having any issue, please give more details of the problem.
    Regards,
    Rupam

  • PO created by means of Workflow  with out Vendor master updates

    Hi  Friends,
       I  have my scenario like this. I am working with Production server. When ever a request is created, it has to be sent for Vendor master data updates. then only a PO has to be created. The problem is the PO is created and the workflow is completed with out vendor master updates. When i check through SWI6  the step is just skipped. In the graphical view the steps vendor master update i.e tru  descion and other wait step types are disappeared. but in the original workflow the steps are present. can any one pls help me in solving this?
    Thanks,
    Archana.

    Hi  Arghadip,
      Thanks for the reply. The process is like this :
       when once request is created , it will fetch the email id of the approver from LDAP
       Then 2 approval steps are there. first approval is not mandatory. second is mandatory and its having terminatting event.
      After this Amendment descion will be there. on rejection of this descion it has to go and update vendor master. Until the amendments the process is going on. after  this  vendor master update will be there . it includes wait steps to  finish the update. then PO has to be created. but  from vendor descion to wait event the steps are disappeared when i checked  in SWI6 for that user. pls help me.

  • How to replicate R/3 Vendor Master changes to SRM

    Hi Gurus,
    We have scheduled the job "BBP_VENDOR_GET_DATA_JOB " on daily basis, the job is running and updating the new vendor master from R/3 to EBP. But it is not updating the R/3 vendor master changes (E.g. Blocking the Vendor in R/3) are not getting update to R/3.
    Please any one can suggest which job we need to schedule for this one. Also I found to report for this one " BBP_VENDOR_UPDATE_DATA_JOB" and BBP_VENDORS _SYNC", but I am not sure which one needs to setup. Also please suggest me any config needs to be do for this one.
    Your help will greatly appreciated.
    Thanks & regards,
    Sada

    Hi Sada,
    AS per  OSS Note 602651 , for SRM 2.0 and SRM 3.0 [ EBP 3.0 and EBP 3.5] SAP provided the  report  BBP_VENDOR_GET_DATA_JOB and BBP_VENDOR_UPDATE_DATA_JOB which could be scheduled in background for vendor replication and synchronization in SRM. These reports are equivalent to TCODE BBPGETVD and BBPUPDVD.
    Thereafter from SRM 4.0 onwards SAP strategy has been to do one time replication through BBPGETVD and provided different way of synchronizing the replicated vendor. That is based on change object concept, for that it has provided an SPRO Node for Customization.
    SPRO->IMG->SAP Supplier Relationship Management -> SRM server -> Technical Basic setting -> Settings for Supplier Synchronization
    The Customization setting is required before we schedule the synchronization job. The Synchronization job runs the report BBP_VENDOR_SYNC.
    Cheers
    Iftekhar Alam

  • Question about using 1 SETID for Vendor Master

    Hello everyone,
    I work for a large healthcare system and we are currently in the PeopleSoft training classes and are about to move into the design phase. We are a multi hospital system and are moving everyone to PeopleSoft for our ERP system. My questions is for Supply Chain purposes and hope that someone can help clarify. It is our goal to use 1 vendor master SETID for our entire hospital system. Please see my question below.
    The customer account # for a vendor is currently at the set id. The customer account # is specific to an entity as it identifies where the vendor should ship. How can we have one vendor master (setid) and still allow the correct customer account # to default on the PO (the buyer needs this when calling in an order)?

    On each of these 'dumb terminals' I assume you are looking to access the complete Mac desktop from the central Mac?
    Unfortunately, this can't be done.
    In the past, the setup you describe first was used on mainframes where each end node was a dumb terminal. But it was just text.
    Next came X11 which does mostly what you are asking about, but each end node is basically a full computer in itself. You can remotely log into a central server and get a complete desktop session. This would take using a central computer that is running full X-Windows and then you'd need a PC running Linux, or running Windows and a X-Terminal package like Exceed or a Mac with X11 installed (not sure if you can make the Mac X11 do a full-blown desktop X session.) Note that as the central server, you'd need a computer running an OS with full-blown X-Windows (Linux, Solaris, HP-UX, etc.) -- OS X is UNIX but it doesn't run full X-Windows as its window manager.
    Finally, there is what are called 'thin clients' ... a good example is Sun Microsystems' SunRay... it's enough hardware on the client side to provide display, keyboard and mouse. They boot off a central Sun Solaris server and work just like X-Windows clients. The difference here is that the SunRay unit can't work on its own; it has no disk, and has to boot from the SunRay server.
    And of course there's Windows Terminal Services, which lets you do the same thing with Windows. I think that takes Windows Server edition software on the central computer, and then a regular PC as a client.
    Sounds like your only option is to use Mac minis as you suggest. But then there's no need for a central computer to share, obviously.

  • Vendor Master Validity

    Hi All,
    We have a scenario where in a vendor has a validity period. The vendor is allotted a temporary vendor code for some period. One can do procurement from that vendor only in the stipulated period. How we can give validity period to a vendor master.
    Based on his evaluation he will be given another ( permenant) vendor code. Now can we link the old vendor code with the new one so that we can get consolidated report for all the transaction done with him.
    Also we can buy only restricted items( probably material group) from a vendor.How this restriction can be built?
    How we can map this.

    hi
    use MK14 (planed changes for vendor) , here you can enter vendor and date from which you want to change ...
    try this hope will serve ur requerments
    regards
    ravikant

Maybe you are looking for