Disable adopting vendor master 's salesperson in RFQ

Dear Sir/Madam,
Now SAP has the function to adopt the sales person's telehpone field in vendor master purchasing data into RFQ document.
Any config to disable the adopt function? That is, I don't want the telephone automatically update when I change the vendor during RFQ creation.
Please kindly advise, thanks load.
Best Regards,
Gary

Hi,
Data in vendor master flow to RFQ and if you want to disable sales person's telephone field, then go for transaction variants by simplify requirement by Hiding that field.
Refer an example-how to hide a field with transaction variants
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a070bfbb-d34a-2d10-b092-ecbe0b0d4a4c?QuickLink=index&…
Regards,
Biju K

Similar Messages

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

PO texts from vendor master

Hi,
when I create a PO using a vendor, after filling field Purchasing Org., Purch. Group and Company code, system copies a text but I don't know from where.
In PO down the header texts I can read "Text adopted from Vendor Master (Purch.org.-spec.test text )", I cannot find it in vendor master....
Could You help me ?
Regards

Hi,
In MK03 please open your vendor go to purchasing data and click on extras on the menu bar, and select text, here you will find purchase order texts, hope this is what you were looking for.
Also check the PIR.
Regards
Shailesh
Edited by: Shailesh Rajan on Jun 28, 2011 3:07 PM

Header Text PO from Vendor master automatically

Dear Friends
This is regarding automatically adoption of header text in PO from vendor master. I am following these steps
- Maintained customizing as MM>purchasing > PO>texts for PO >define copying rules for header texts .
in this , select the text type ( this is the PO header text ) and click on text linkage and maintain source obj as vendor master and maintain the fixing as blank ( ie text automatically adopt in the target obj)
-Then I wrote text (needed in FR lanugage) to respective vendor in purchasing view
Now When I create a PO, system does not propose any thing under header text
Did I miss anything.
Please respond
Regards
SG

Hi,
1. First I assume the configuration settings are correct
MM- Purchasing -- PO --Texts for PO --Define Copying rules for header text
Here the target text type (in this case the PO text type ) i.e. sequence no. is assigned to the correct source object and text (in this case the vendor text type)
2.If you logon to the system using the language option. i.e. logon id, password and language you get the SAP screens in that language. Now if you try to maintain vendor text in FR and create a PO, the FR Text would get copied to the PO. Now if you go back to the EN logon you ll still find the vendor text in FR. So it is definitely linked to the logon language.
There should be another way for this too.
This is an observation and may help you resolve your issue.

Additional Field in Vendor Master for PF Number and ESI Number

Hi Experts,
I have to maintain ESI Number and PF Number in Vendor Master, but no such field is available in vendor master or J1ID. Kindly suggest me the fields which I can use. We have to capture the ESI and PF Number of the vendor in case He is a subcontractor to us.
Regards
GR

Hi
You can looks for customer fields (ABAP developed fields). You have standard development available in SAP. See the below config path. It will help you and your abaper
spro>logistics General->bussiness partner->vendors->control--->adoption of customer's own master data fields.
With the help of help text available there you and your abaper can develop it with flow logic easily with minimum effort.
Hope it helps you
Regards
Antony

Payment Terms should come from vendor master data

When we create a new contract (ME31K) Z0NQ for the vendor XYZ by default the payment terms that the contract retrieve is 1131, but in master data (XK03) for vendor XYZ I have payment terms 1011 defined.
I already checked it in Purchase organization and CCode level.
Please advise. Thanks!

It should come from vendor master only butmake sure that you are creating cintract based onthe RFQ or some use exit is avtive for that.

Vendor master change confirmation (Fk08)

Dear Experts,
I have an requirement that i want change vendor master details that details should be confirmed by other user in FK08 but in FK08 t.code i am getting only confirmation status (central) as "to be confirmed" and then i am able to confim that change.
Here my problem confirm status (company code) is disabled and confirm button is also disabled.
I want here this button should be enabled and i should cofirm the change here.
For this do i need to change the vendor who is created at company code level or any other solution.
Please help.
Thanks.
Bhaskar

Hello,
Please understand conception of confirm.
The confirmation is called dual control. When you changed the sensitive fields, if any changes made to those sensitive will be asked for confirmation. Not all other fields. When the sensitive fields are being changes, the vendor master will be invialidated, unless these changes are being confirmed by the other user.
You have configure the sensitive fields.
IMG==> Finaicial Accounting ==> Accounts Receivables and Payables ==> Vendor Accounts ==> Master Data ==> Configure sensitive fields
Normally, payment terms and payment methods are considered to be the sensitive fields. Select these two fields as sensitive fields. Then if you make any changes to these fields would invalidate the vendor master and only the other User is able to confirm, subject to his authorization. Until that time, the user is not valid for any transactions.
Regards,
Ravi

Vendor Master Data change (VENDOR_ADD_DATA)

Hi experts,
I implemented the badi's VENDOR_ADD_DATA_CS and VENDOR_ADD_DATA to create the subscreen
in XK01 but
i created the Z table for storing the data based on vendor and company code
i placed table control on the screen, because for single vendor i need to create more records thats why i created the ztable
now i am not getting how to store these details in my ztable for vendor
please tell me the sequence of methods to implement in the badi.
Thans&regards,
srinivas

Hi Srinivas,
These are the steps to implement BADI for XK01
Goto Transaction SPRO---->select SAP reference IMG button on tool bar
select 'logistics general' node-->select 'business partner' node>'vendors' node>control
--->'Adoption of customers own master data fields'
read the documentation of 'Prepare modification free enhancement of vendor master record'
Besides Execute button.
There are four node read all the documentation
Hope solves your problem
Regards
Krishna

How to use copy default values for material from vendor master in Account Group

Dear all:
In define AccountGroup for vendor ,there is a field named DURAS which means default values,who can tell me how to use it?
Any informations are appreciated!

Hi Katherine,
I have tried using default value as B in the customizing
If i maintain default values in the vendor master record, it will automatically adopt in the purchase info record.
Here i tried using sales person & telephone no field in vendor master record & it automatically adopts to purchase info record.
Region sales person and telephone no i have maintained in vendor master record, it automatically fetches to info record for the particular account group. I am not sure if there is any relation between vendor master and material master record.
Regards
Subbu.

Vendor Master - Urgent

Hi All
We have requirement to "Place a message to prompt the user when creating the vendor master to check to see if the vendor is 1099-reportable"
Thanks in advance
raj

Hi Sridevi,
In Fiscal year 2006, they posted posted some invoices without withholding tax code and cleared the same. Later the W/t code assigned in vendor master. Then they adopt some patchup to display 1099 report correct.
Now, our client needs to have control whenever they create vendors, the system should popup a message that he is subject to 1099 reportable or not. So that they will not forget to assign w/t code in vendor master
Thanks for reply
raj

Confirmation Control Key Value in vendor master overwritten by Info Record?

Dear all
In the standard 3rd party processing, we will use S/O to trigger PR and we then convert PR to PO. And when PO is converted, Confirmation Control Key (CCK) Z01 maintained in Vendor master purchasing view will be adopted for all the items in the PO, and in the purchase infor Record for the combination of material & this vendor, we do not maintain any CCK value there.
However recently, the system behaves in such a way that the CCK value does not automatically show up in PO item anymore. And I have been thinking can it be the fact that the blank value of CCK in info record will overwrite the Z01 value in the CCK of vendor master? But if so, why all the past PO I have checked does not have CCK value maintained in info record but the CCK was able to appear automatically?
An interesting fact is that if I create the PO manually by enter Vendor with CCK value Z01, Org Data, account assignment S and Item category S (both for 3rd party processing), and then the material and hit ENTER, the CCK value Z01 will appear in PO Item level under tab: Confirmation.
However, once I enter the PLANT value in PO Overview, seem like the Empty value of CCK in info record will overwrite the existing Z01 value.
Please advise if it is how the info record CCK work to overwrite? Also, how do I get back to the stage where the info record CCK will not overwrite as I do not want to spend time to update all the info record CCK to have Z01.
Thanks

Dear Manohar Raju Kanchanapally
I do not understand why this OSS note SAP Note 909885 - ME21N: Confirmation control key not
from vendor mentions the following:
Symptom:
When you create a purchase order using Transaction ME21N, the confirmation control key from the vendor master is not used, although it is maintained.
Cause and Prerequisites:
The symptom occurs if no confirmation control key was maintained in the existing purchasing info record.
Solution:
Implement the attached correction instructions as a modification.
It is totally contrary with the General Rule that the most specific will always prevails, meaning if I do not maintain CCK value in the Info Record, it will overwrite the CCK value I maintain vendor master when I create PO using same vendor, material, purchaisng org and plant!
Please help!
Edited by: Daimos on Sep 17, 2009 1:22 PM
Edited by: Daimos on Sep 17, 2009 1:22 PM

ERS Output email/fax to different ID (CONSNUMBER) in vendor master

Hi Guru,
I am just wondering if there is a way to change the ERS output to different email/fax ID than the default one in vendor master.
As a default in SAP, the Purchasing documents ie. PO, RFQ and ERS outputs will be sent to default emial/fax (of course when we set it up to send via fax = 2 or email = 5). The problem here is that SAP will pick up default email/fax in vendor master, however, our business would like to have an ability to send ERS outputs to different email/fax ID (CONSNUMBER). Currently it is only sent to FLGDEFAULT address.
If we change the default, it will change all other documents as well. We only want to differentiate ERS output and leave other docs (PO, RFQ) to use default setting.
Is there any enhancement spot or exit that can help achieve this?
Please advise.
Cheers
BJ

Hi All,
Found where to put our codes in to cater for this requirement ==>LMRMNF01 - Form Routines for SAPLMRMN - Logistics IV: Message Control. It works wonder. Hope that will help others.
Thanks.

Custom field in Vendor Master - track field changes

Hi Experts,
I have a requirement to enhance vendor master (XK01) by adding custom fields. I did this, but now the customer needs to track changes made to this field. He expects to see the changes made to this custom field using menu path 'Environment -> Field Changes' from vendor master transactions (XK01, XK02, XK03). I have enabled the track changes in the data element, so that field changes can be tracked in CDPOS, but that is not enough. Please help to find solution. Thanks.
Regards
Arun

Hi Brad,
I added the new fields to vendor master using the SPRO option:
'Prepare Modification-Free enhancement of Vendor Master Record' in the following path:
Logistics-General -> Business Partner -> Vendors -> Control -> Adoption of customer's own master data fields. This created a button on vendor master, and my field is in a pop up box which is generated on click of this button.
This field is stored in LFM2 table.
I have enabled the change flag in the data element of the custom field, and it is showning the field changes in CDPOS table.
But the problem I face is how I can avoid going to the CDPOS table and instead use the menu option :
'Environment -> Field Changes'
Regards
Arun

Vendor master marked for deletion

Hi Gurus,
I have the following issues related to vendor master deletion.
1. I can able to create PR, release the PR for the vendor after marked for deletion and also blocked in XK05.
2. It allows to maintain RFQ for the vendor marked for deletion and also blocked in XK05.
3. It allows to release PO for the vendor marked for deletion and it blocks only after blocking in XK05
4. It allows to post GR and IR for the vendor marked for deletion and also in blocked in XK05.
Appreciated your help on this.
Thanks and regards
Durai

the deletion indicator is a preparation for archiving.
However, archiving will check whether the vendor is still in use and must be kept.
A deletion indicator will with standard customizing not restrict the usage. The user get a warning message and this should him make start thinking.
1. I can able to create PR, release the PR for the vendor after marked for deletion and also blocked in XK05.
Do you have a purchasing organisation. in the requisition? XK05 restricts the order creation, I do not know about any restriction in requistion creation or release.
2. It allows to maintain RFQ for the vendor marked for deletion and also blocked in XK05.
This should not be possible if the purchasing block is set according to OSS note 67341
3. It allows to release PO for the vendor marked for deletion and it blocks only after blocking in XK05
Thats correct, If the vendor was not blocked at PO creation, then system has to allow the follow on activities, explained in OSS note 129836
4. It allows to post GR and IR for the vendor marked for deletion and also in blocked in XK05.
same as for Q3, explained in OSS note 129836

Disable adopting vendor master 's salesperson in RFQ

Similar Messages

Maybe you are looking for