Vendor Master Ship to / Bill to

Dear Friends,
Is it possible to have multiple Ship to Addresses for One single vendor.
The vendors are service providers to whom Installation material needs to be despatched ( One vendor would be operating from Various states). No invoices are to be raised for the material despatched.
Please advice
Regards
Mukesh

Hi,
Locations are stored in HZ_LOCATIONS. I suggest you going through the Metalink Note 220383.1 (TCA FAQ) and also on Metalink -> Knowledge Browser -> Financials -> Trading Community Architecture to gain more clarity on HZ objects (These objects belong to TCA - Trading Community Architecture).
Rgds,
Rakesh.

Similar Messages

Vendor Master Ship to Address

Dear Friends,
Is it possible to have multiple Ship to Addresses for One single vendor.
The vendors are service providers to whom Installation material needs to be despatched ( One vendor would be operating from Various states). No invoices are to be raised for the material despatched.
Please advice
Regards
Mukesh

Dear Mukesh,
There is no possibility to have multiple vendors entry in Partner functions. In PO, also single vendor is allowed.
If you leave blank at Partner functions at PO level, You have a chance to give multiple vendors as Partner functions for that particular PO at the time of J1IEX transaction (Excise invoice capturing time by using SHIP FROM option)
Thanks & Regards,
VB

One vendor master with different recon posting while accounting of the bill

I have one vendor master, where we can able to give only one recon. account. But the vendor supplies various materials like rm, pm and capital material. I want to change the recon account while accounting the invoice.

Hi,
Changing the Recon. while doing the transaction is not possible and not advisable as later on Recon a/c wise reports(FBL3N) won't tally with(FBL1N).
Better to create different Vendor codes for different Recon. a/c.
Regards
Swapna

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

Is it possible to maintain the multiple address in the Vendor Master (XK01)

SCENARIO:
Vendor ( Ex.VEN) Address maintained in the SAP Vendor Master is the Corporate Address (M).
But I want to maintain delivery address as Address (X) and Remit Address as Address (Y) and
Billing address (Address on Invoice/Bill) as Address (Z).
Is it possible to maintain as mentioned in SAP Vendor Master (XK01)?
Please suggest, How can we go head and release the PO in the above scenario?
Regards,
SB

This can be easily acheived by Partner Functions
1.VN Vendor
2.SP Sold to party
3.SH Ship to Party
4.IP Invoicing Party
5.Delivery address
Please refer below link from help.sap.com
Partner Roles in Purchasing
http://help.sap.com/saphelp_470/helpdata/en/a1/7b373944f7a97ce10000000a114084/content.htm
regards,
Lalita

Vendor Master File - Back order allowed

My client is using ECC 6.0 Retail
We would like to automatically allow or not, back order from certan vendors.
We are using also TM and WM. The Inbound Deliveries are created automatically at night and POs are manually closed by the buyers. If there is a partial receipt by default another I.Del. will be created at night for the remaining quantity. When POs are reviewed after the fact, the inbound deliveries will be deleted, POs be flagged as completed and the case will be closed. However we know that for this particular vendor, he will never shipped backorders. Is there a flag we can use in the Vendor Master File to identify these vendors (no backorder) and prevent the creation of additional Inbound Deliveries?
Thanks
Gaetan

I would agree however in this case this is more vendor specific than article specific. The same article might be sourced from two different vendors having two different approaches (with or without backorder deliveries).
GD

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.

Creating Vendor Master Records from HR Master Records

Dear Experts,
I have been using t-code PRAA to create vendor master records from HR master records. The client would like to have one vendor number for a group of employees (in this case external contractors all working for the same company). The system won't allow me to link several PERNR to one LIFNR (i.e. error message).
Is it, however, possible to do this?
Thank you.
Edited by: Philip on Jan 14, 2011 9:58 PM

Hi ,
PRAA has one to one relation ship , means it created 1 vendor for 1 employee .
If you are using PERNR then you cant use one vendor to may PERNR .
Either create them as individual vendor or else have a manual control system in place where in you will have to create a dummy PERNR and then allocate all the cost to this invidual vendor , if you are paying the check to only 1 contractor for say 100 contract employees you can use this .
else it is a better mechanism and control to have 1 is to 1 in case of employee to vedor .
Regards ,
Dewaang T.

Purchase organisation Field in Vendor master data

Hi All
During the creation of Vendor master ,Needs to make the Field Purchase organisation as a mandatory. I have checked the in the following configs.
Define Account Groups with Screen Layout (Vendors
Define Screen Layout per Company Code (Vendors)
Define Account Group and Field Selection (Vendor)
The option is not available. for the above requirement.
thanks & Regards
DP

In many companies the address data is maintained by different people than accounting data and purchasing org data.
I would not like that accountants to create my purchasing org data, and I am certain that my accountants dont want the buyer to create his accounting data.
if you could make this combination mandatory, then the user would have to maintain all screens at the same time, which may result in delays. as he can only start once he has all data available. SAP standard allows to create a vendor with general data and purchasing org data and purchasing can start buying. the company code data is only needed in the moment the goods arrive.
So you gain time to collect the data while you already started business.
Further, not all vendor master need to have purchasing org data. and not all vendors with purchasing org views need a company code view.
e.g. a restraunt may send you bills for lunch, but you do not place purchase orders with this restaurant. No purchasing org view needed here.
a goods supplier, that is needed for Intrastat purposes only, does not need a company code view, as you will never get invoices from the goods supplier.

Possibilities to replicate R3 vendor master to CRM

We are working with SAP ECC and at them moment we are installing CRM 4.0 Best Practices. Replication of customers from R3 to CRM is working but we face a problem with vendor master records:
In R3 we have setup sales representatives as vendor master records (account group EMPL). In R3 every sold to customer must have 1 sales rep linked as a partner function. In CRM we need to have the same situation.
Does somebody know what configuration/steps we have to follow to be able to replicate a vendor master record and a sold to-sales rep partner function be able to CRM?
Another example is forwarders (also vendor master records) that we have to link as a business partner to our ship to's.
Your help is very much appreciated!
Kind regards,
Angélique Heutinck

Have a look at OSS note 883162, there is a config guide linked and that is what we have used.

Pl tell me config and process of return PO to vendor via shipping

Hello,
My sloc is HU- Warehouse managed. I am creating a scenario of return purchase order to vendor using 161 Movement type. I have created a PO with 161 movement type. But whenever I am using MIGO with reference to return PO, OBD is created with customer. But I want OBD to be created for vendor because we are returning the delivery to vendor and not customer. I have done all the setting in vendor master of return delivery to vendor in purchasing view. Please provide me step by step process of configuration and business process of written PO to vendor via shipping.
Thanks
Milind

Hi,
Pre requisites Vendor return Via return PO and delivery.
1. You must create a customer master record for the vendor and assign the same in vendor master u2013Control view
2. In vendor master u2013purchasing view flag the Returns Vendor check box.
3. Maintain shipping point determination (OVL2)
Refer below link for config
[http://help.sap.com/bp_blv1600/BL_US/Documentation/Scenarios/V3I_BPP_EN_US.doc]
Regards,
Vikas

Vendor Master - "Returns Vendor" Field

Hello folks,
I am trying to load vendor master data. For Purchasing Data, there is a checkbox titled "Returns Vendor" (LFM1-KZRET) - indicates that a vendor return is carried out using shipping processing.
I am running into problems trying to load this field automatically. The standard load program does not work since when you tick this checkbox, a pop-up comes up asking you to specify a customer (and creates a new customer if you don't specify an existing one). However, in my case, the "customer" field in the general data view of the vendor master record will already be populated with an existing customer.... so when I tick the "returns vendor" checkbox, the pop-up will by default list the customer number and won't allow me to change it anyway.
I have also tried creating a BDC recording, but it prevents me from doing so.
I hope my explanation isn't too confusing...can anyone help me out?
Thanks,
Jayesh

Hi,
Did you guys find any resolution to this issue? I also have a similar requirement and am not finding any solution.
Thanks,
Sandeep

How to add a new field to the Quote: Shipping and Bill Tab Payment region

Hello All,
We have a requirement to add payment description column to the Payment Region of Shipping and Bill tab in Quoting User(Quote Page).
We have extended the View object HeaderPaymentsVOObj and created a custom view object, then created and ported the substitution.
In Quotes page, 'Shipping and Bills' tab Payments region, we have created a new item(Payment Description), assigned the custom View object instance and attribute to it.
We are able to enter and update the payment details before substitution, but after substitution while entering payment details we are facing the below error.
At most one payment record can exist at quote header/line level.
Help and inputs are highly appreciated.
Thanks in advance.
Regards,
Supriya.

Hi,
So you need that this new field have data in old records?
1.- If you are in BI 7.0 and the logic or data for that New field are in the same Dimension, you can use a Remodeling to fill it. I mean if you want if you want to load from a Master Data from other InfoObject in the same Dim.
2.- If condition "1" is not yours.
First add the new field, then create a Backup Cube (both cubes with the new field) and make a full update with all information in the original Cube. The new field willl be empty in both cubes.
Create an UR from BackUp_Cube to Original_Cube with all direct mapping and create a logic in the Start Routine of the UR (modiying the data_package) you can look for the data in the DSO that you often use to load.
To do that both cubes have to be Datasources ( right click on Cube-> aditional function-> and I think is "Extract Datasource")
Hope it helps. Regards, Federico

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.

What the setting required in vendor master for Intercompany or intracompany

What the setting required in vendor master for Intercompany or intracompany orders
Thanks,
Kiran

Hi,
For the inter company STO scenario
Create a vendor for the company code of receiving plant, using account group :0007 Assign this vendor to Delivering plant
in the Purchasing view>Extras>Add. Purchasing data>Plant.
Also create an internal customer for the supplying sales area and assign it to the vendor, it helps in determining the Shipping point.

Vendor Master Ship to / Bill to

Similar Messages

Maybe you are looking for