Reevaluation indicator in Vendor master

Hi MM Gurus,
Can anybody let me know about
Re-Evaluation Allowed indicator in Purchasing View of Vendor Master.
Pls revert back with example for better understanding
Points would be rewarded.
Regards,
Girish.C.M.

Hi
If you select this indicator for a vendor you can revaluate services or deliveries which are already setteled for this vendor.
Use below link to get more clarification.
http://help.sap.com/saphelp_47x200/helpdata/en/b1/b5ecdaa6d111d2b4a3006094192bbb/content.htm

Similar Messages

Use of LFA1-STKZU "Liable for VAT" indicator in Vendor Master

Dear Friends,
Could anyone please explain to me what the functionality is for the LFA1-STKZU "Liable for VAT" field in the Vendor master?
I have no idea about what the difference is between having this flag set or not.
Please, anyone?
Thanks and Regards
Anil

Dear,
A checkbox in the customer and vendor master records that determines whether or not a customer or vendor is liable for value-added tax (VAT). This field is used in Venezuela
It has a integration with Sales Ledger and Purchase Ledger
In Venezuela, you are required to submit this report to the authorities each month, in accordance
with the Law on Wholesale and Luxury Items Tax
To access the report, from the SAP Easy Access screen, choose Accounting> Financial
Accounting> General Ledger>Reporting>Tax Reports>Venezuela>Sales Ledger/Purchase Ledger.
It does not have any implication for Business Process in India.
Regards,
Chintan Joshi.

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

Upload program for vendor master

Hi Friends,
Could you please help me in this.
actually i have a program like this:
i have to download the data from an excel sheet and reformat it and output into a text file so that the data can be uploaded into vendor master using standard progarm
"RFBIKR00".
i have written the program like this:
but in the middle when formatting the data...i'm facing the problem....
plz help me in solving that...
thnx very very much...........
the program i wrote is like this:

tables: lfa1,
 lfb1,
 lfm1,
 lfbk,
 bnka,
 bgr00,
 blf00,
 blfa1,
 blfb1,
 blfbk,
 blfm1,
 blfb5,
 blfbw,
 blfei,
 blfza,
 blflr,
 blfm2,
 bwyt3,
 bwyt1,
 blfat.
*--- Internal table for spread sheet.
data: t_filedata like alsmex_tabline occurs 0 with header line.
*--- Internal table for Vendor Master Data in Spread Sheet.
data: begin of t_sheet occurs 0,
 name1 like lfa1-name1, "vendor name1
 name2 like lfa1-name2, "vendor name2
 altkn like lfb1-altkn, "previous master record number
 bukrs like lfb1-bukrs, "company code
 ekorg like lfm1-ekorg, "purchase organization
 ktokk like lfa1-ktokk, "account group
 stras like lfa1-stras, "street
 street4 like lfa1-name4, "street4
 pfach like lfa1-pfach, "po box
 ort01 like lfa1-ort01, "city
 regio like lfa1-regio, "region
 pstlz like lfa1-pstlz, "postal code
 land1 like lfa1-land1, "country
 telf1 like lfa1-telf1, "first telephone number
 telfx like lfa1-telfx, "first fax number
 stcd1 like lfa1-stcd1, "fed tax ID#
 brsch like lfa1-brsch, "commodity code
 akont like lfb1-akont, "reconciliation account
 mindk like lfb1-mindk, "monitory indicator
 zwels like lfb1-zwels, "payment method
 reprf like lfb1-reprf, "check double invoice
 banka like bnka-banka, "bank name
 stret like bnka-stras, "house number and street
 city like bnka-ort01, "city
 provz like bnka-provz, "bank state
 banks like lfbk-banks, "bank country
 swift like bnka-swift, "swift code
 bankl like lfbk-bankl, "aba#
 bankn like lfbk-bankn, "bank account no
 zterm like lfb1-zterm, "payment terms
 terms like lfm1-zterm, "terms of payment key
 end of t_sheet.
*--- Internal table for Vendor Master data in Text File.
data: begin of t_file occurs 0,
 s_session type bgr00,
 s_header type blf00,
 s_blfa1 type blfa1,
 s_blfb1 type blfb1,
 s_blfbk type blfbk,
 s_blfm1 type blfm1,
 s_blfbk type blfbk,
 s_blfb5 type blfb5,
 s_blfza type blfza,
 s_blfm1 type blfm1,
 s_blfat type blfat,
 s_bwyt1 type bwyt1,
 s_bwyt3 type bwyt3,
 s_blfm2 type blfm2,
 s_blfei type blfei1,
 s_blfbw type blfbw,
 s_blflr type blflr,
 end of t_file.
 SELECTION SCREEN *****
*---Selection Parameters.
selection-screen begin of block b1 with frame title title1.
parameters: p_xlfile like rlgrap-filename.
parameters: p_txfile type rlgrap-filename.
selection-screen end of block b1.
 INITIALIZATION *****
initialization.
*---Initialize text fields for selection-screen.
title1 = 'Selection Parameters'.
 AT SELECTION-SCREEN *****
at selection-screen.
at selection-screen on p_xlfile.
 perform check_file using p_xlfile.
at selection-screen on value-request for p_xlfile.
 perform select_file using p_xlfile.
 START-OF-SELECTION *****
start-of-selection.
 clear t_sheet.
 refresh t_sheet.
*---Upload Spreadsheet.
 perform read_file using p_xlfile.
*---Process data into formatted internal table.
 perform format_data.
 append t_file.
 clear t_file.
 endloop.
*---Download data to Text file.
 perform download_data.
 TOP-OF-PAGE *****
top-of-page.
 perform top_of_page.
 S-U-B-R-O-U-T-I-N-E-S *****
 Form TOP_OF_PAGE
 Calling the Standard Report Header
form top_of_page.
 perform header using 'CREATE FILE FOR'
 'VENDOR MASTER UPLOAD'
 132.
 skip 2.
endform. "TOP_OF_PAGE
 Form check_file **
 Checking the File entered **
data: p_filename type string.
form check_file using p_filename.
*---The entered File must be Excel spreadsheet.
data: l_length type i,
 l_ext(4) type c.
l_length = strlen( p_xlfile ).
subtract 4 from l_length.
l_ext = p_xlfile+l_length(4).
translate l_ext to upper case.
if l_ext <> '.XLS'.
 message e009 with 'Only Excel spreadsheets are supported'.
endif.
*---Check if File exits and not empty.
data: l_return(10) type c.
CALL FUNCTION 'WS_QUERY'
 EXPORTING
 FILENAME = p_filename
 QUERY = 'FL'
 IMPORTING
 RETURN = l_return
 EXCEPTIONS
 INV_QUERY = 1
 NO_BATCH = 2
 FRONTEND_ERROR = 3
 OTHERS = 4
IF l_return = space or l_return = '0'.
 message e530(pj) with p_filename.
ENDIF.
endform. "CHECK_FILE
 Form select_file **
form select_file using p_filename like rlgrap-filename.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 PROGRAM_NAME = SYST-REPID
 DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = ' '
 STATIC = 'X'
 MASK = ',MS Excel (.xls),.xls.'
 CHANGING
 FILE_NAME = p_filename
 EXCEPTIONS
 MASK_TOO_LONG = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE e838(29) with p_filename.
ENDIF.
endform. "SELECT_FILE
 Form read_file **
form read_file using p_filename like rlgrap-filename.
*---Display status message for User.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
 EXPORTING
 TEXT = 'Uploading Spreadsheet'
*---Upload spreadsheet.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = p_filename
 I_BEGIN_COL = 1
 I_BEGIN_ROW = 1
 I_END_COL = 256
 I_END_ROW = 65536
 TABLES
 INTERN = t_filedata
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3
IF t_filedata[] is initial.
message i009 with 'NO DATA FOUND IN FILE' p_filename.
stop.
ENDIF.
sort t_filedata by row col.
endform. "READ_FILE
 Form format_data **
form format_data.
data: l_index type i.
field-symbols: <fs1>.
*---Display status message for user.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
 EXPORTING
 TEXT = ' Processing Data...'
loop at t_filedata.
 l_index = t_filedata-col.
 assign component l_index of structure t_sheet to <fs1>.
 <fs1> = t_filedata-value.
 at end of row.
 append t_sheet.
 clear t_sheet.
 endat.
endloop.
 refresh t_filedata.
 free t_filedata.
endform. "FORMAT_DATA
 Form download_data.
form download_data.
OPEN DATASET p_txfile for OUTPUT.
LOOP at t_file.
 TRANSFER t_file to p_txfile.
ENDLOOP.
CLOSE DATASET p_txfile.
IF SY-SUBRC = 0.
WRITE: / 'Excel to Textfile for Vendor Master Upload: ', P_TXFILE.
ENDIF.
endform. "DOWNLOAD_DATA

Hi!
You don't need to program the 'translation' from a file into input data for RFBIKR00 yourself. SAP has done this, so that you can do this (nearly) without programming. If you need some special conversion rules, then you can add some coding, but most is possible without.
Have a look at transaction LSMW. It's not so complicated it looks at the first time. Just look at <a href="http://help.sap.com/saphelp_erp2004/helpdata/en/ad/2d54a41d7011d2b42e006094b944c8/frameset.htm">help</a> for the way to use LSMW.
Regards,
Christian
P.S.: sorry for lost your efforts, but you should switch to LSMW

Header Text copy to PO from vendor master

Dear all,
I am trying to pull data storeed in vendor master to PO for header text so that we don't need to repeat to each PO for the vendor.
I tried to link this in "Texts for Purchase Orders" in SPRO ,But not able to link it
B'coz it's not allowing me to add the object of vendor master
so pl guide me how i link vendor master text to PO
Regards,
Vimlesh

Hi,
In customizing ->material management -> purchasing -> purchase order -> texts for purchase orders -> define copying rules for header texts, choose "header text" and click on text linkages. Here you can enter for source object "vendor master", and for source text choose vendor master header text.
And in the FIX INDICATOR for text you have to maintain blank. then it will copy text
This will copy text from vendor master to PO header text.
Please check this and revert back if you need further details
thanks,
santosh

PR to PO Vendor Master Setting

If i need using ME59N to convert PR to PO one of the requirement is set the auto PO in Vendor purchasing view.
I have an question is how about
I don;t set the auto PO in the Vendor Purchasing View but set under Vendor Purchasing view DC veiw auto ordering
Is it ok ?
Because I want the Auto PO function can down to Purchasing View -> DC level, but it's seems not work

OSS Note 335079 - ME59/ME59N: "Automatic purchase order" ind. in vendor master
explains a missing functionality
If a purchase requisition (PReq) is automatically converted to a purchase order using transaction ME59 or ME59N, the "Automatic purchase order" indicator must be set in the vendor master record of the source of supply. In this case, note that it is not sufficient to maintain this indicator under the alternative vendor data (plant level or vendor subrange (VSR) level). In the program, only the indicator for the general vendor data is checked even though the field is also available under the alternative vendor data.
Reason and Prerequisites
A function is missing.
Solution
There are none.

Vendor Master change pointers problem

Hi ,
We have a custom program that will read change pointers for Vendor master .
we use these change pointers to trigger our custom idoc . But we need to select only change pointers of vendors whose changes are confirmed in transaction FK08 or Fk09
Please let me know how we can check the changpointers for particular vendor is confirmed or not
Regards,
Ramesh

Just as a follow up on this. I think that within the setup of the classification system you need to configure the tracking of changes. If you take a look at table TCLA you'll notice that there is a field which indicates if change document are turned on. I belive that this then relates back to the "virtual" change document objects that I refered to in my previous post.
It looks like during update tasks that fucntion CLVF_VB_INSERT_CLASSIFICATION and that this checks the TCLA table and then writes the change documents as part of the updates.
The description of this field in TCLA is:
Change Documents for Classification
Indicator: for this class type, a change document is generated for all changes to classification data.
For technical reasons, this indicator can only be set if the class type is defined for classifying different object types.
looks like there is some more research needed but this should hoepfully get you on the right track.
~Ian
Edited by: Ian Maxwell on Sep 29, 2008 1:37 PM

Field Mobile phone (ADR2-R3_USER) vendor master changed from Blank to 1

Hi
Where I can find Mobile phone (ADR2-R3_USER) in Vendor master.
We have updated Purchasing block to vendor master via LSMW and after that if i am going to see the changes in vendor master (XK03)
Found that the field Mobile phone (ADR2-R3_USER) changed from BLANK to ONE
Field Mobile phone (ADR2-R3_USER)
from
to 1
Not sure what happened.
Can any one throw some ides on this?
Regards
Jai

Hello,
F1 on the field ADR2-R3_USER gave the below information. Check if this is useful.
Indicator: Telephone is a Mobile Telephone
This field specifies whether the telephone number is a mobile telephone number.
Input values
' ' : The telephone number is a fixed-line telephone
'1' : The telephone number is the standard fixed-line telephone
'2' : The telephone nubmer is a mobile telephone
'3' : The telephone number is the standard mobile telephone
Dependencies
Either the standard fixed-line telephone number or the standard mobile telephone number is also the standard telephone number (FLGDEFAULT = 'X').
In older data sets, this field may have also have the value ' ' for the standard fixed-line telephone. In this case, however, FLGDEFAULT is always 'X'.
Effects on Customizing
In Customizing, you can specify whether the SMS-compatible indicator is to be proposed for new mobile telephone numbers created in dialog by choosing General Settings -> Set countries -> Define Mobile Telephone Attributes for each country.
Cheers
Balaji

Minority Indicators on Vendor Master

Hello Experts,
I have a couple of queries around the Minority vendors in the USA.
The current business scenario has vendors who are a part of various minority groups.
(a) Do we have an option within SAP (Standard) to make multiple minority groups
(b) Capture the certification dates for each of those groups
I was looking to check if SAP provides this as a standard functionality, or would it be a good option to create a custom table with the required combination for the business.
what are the standard SAP reports used for Minortiy vendor reporting.
Thanks in Advance.
Cheers
Shankar

Hi Shankar,
We have that same issue. Not sure if it is best practice, but we ended up using the Minority Indicator field (LFB1-MINDK) to store a Minority Code and these are our selection options we configured to handle if a vendor applies to more than one:
M = Minority
MS = Minority/SBE
MW = Minority/Women
MWS - Minority/Women/SBE
S = Small Business
W=Women-Owned
WS = Women/SBE
Certification Date is CERDT
These fields are on the vendor master screen: Accounting Information.
We have not found any standard SAP reports, we've had to write our own ABAP reports to pull in from table LFB1 to view vendor spend, etc.
Cindy

Vendor Master - Export License - MEK3

All,
We have 3 raw material vendors for which we have an export licence. Is there a way to record these in the vendor master ? This would have to affect the conditions leading to the determination of the tax key.
We tried the info records, but these are overruled by the conditions in MEK3.
- We have no material tax indicator MM03/OMKK
- Plant indicator is set OMKM
- Plant indicator is assigned OMKN
- Account Assignment indicator is set OMKL
- Assignment of Tax indicator to Account Assignment Cat. is done OMKO
MEK3 Taxes: Plant, Account Assignment Origin and Region leads to wrong tax key as there is no distinction between local suppliers and local supplier with export license.
Thanks,
Mariëtte.

Hi Vineeth
For a vendor master record all the important controlling parameters are controlled by the account group which you are assigning to the vendor master recored.the controls of the account group are
Number assignment:whether you can maintain an external number or internal number assignment.In your issue of internal and external vendor you can maintain different account groups for bot and thus assign different number ranges to them
Field Selection: Account group determines whether a filed in vendor master should be hidden,displayed,required entry or optional entry
Partner Roles::Account groups determine which are all the valid partner roles for a vendor ,eg: order recepient,invoicing party etc
Status of Vendor: Account group determines whether the vendor is one time vendor or regular vendor
Vendor subrange::
We can delete vendor master record using transaction OBR2
Reward if useful
Thanks and Regards
SHYAM.R

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

Sustainability in the Vendor Master

There is much discussion about [sustainability|http://www.sdn.sap.com/irj/bpx/sustainability] in the BPX community and in other sources. Much of the discussion is about initiatives SAP has taken as a company to become more "Green" or white papers about the topics of CSR and sustainability.
I've got a much more concrete question. In the vendor master (ECC6.0) what fields are available to help classify or document sustainability indicators of vendors? How would you begin to go about creating an evaluative record of practice or performance? GRI provides a [reporting framework G3|http://www.globalreporting.org/ReportingFramework/ReportingFrameworkDownloads/] and standards for reporting but, where in the vendor master can some of the indicator profiles be recorded?

Hi
Sustainability is possible in SAP (vendor master) if you implement GRC module. This module has control all over modules when it comes to Sustainability.
regards
Antony

IBAN Maintenance in Vendor Master

I would like to have a solution to validate bank account number and IBAN while maintaining both these fields in vendor master record. Business scenario is that we should be able to enter bank account number with or without IBAN. But if both bank account number and IBAN are entered in vendor master, then an error is to be displayed if bank account number does not match with IBAN.
I am in United Arab Emirates (Country code AE) but SAP country verion for AE is not applied.
Edited by: Rajan Palakkal on Nov 29, 2011 6:59 AM

Hi,
Yes, only if you set the indicator "Bank Data" under Further checks then that country-specific check of the bank details (bank
number, bank account number, bank control key) is carried out. The corresponding check routines are installed in the system and can be activated via this switch "only".
for correct generation of IBAN from bank details for UAE following information is necessary:
AE - UNITED ARAB EMIRATES - United Arab Emirates
Key for the bank directory: 1
Bank account number - Length, Checking rule: 16, 2
Bank number length - Length, Checking rule: 3, 4
The IBAN is derived from the 3-digit bank number and the account number
(which may have up to 16 digits). A 3-digit bank number and a 16-digit
account number are generated from an IBAN.
Refer note 1012293
If you want to set Bank key as 4 i..e externally, please check if the same routnie works by enabling the indicator as IBAN is derived from the 3-digit bank number and the account number and vice versa.
Hope this helps.

Dunning procedure in Vendor master

Why do we create Dunning procedure in Vendor master.. cud u pls advise..?
Txk
Umesh

3.3.3.4.1.2     Dunning Procedure
3.3.3.4.1.2.1     Defining Dunning Procedures
     Use
You enter the settings that control the dunning program by:
1.     Specifying the company codes to include in dunning.
2.     Setting up the dunning procedure you want to use (dunning interval, grace periods for the due date determination and number of dunning levels)
3.     Setting the dunning charges.
4.     Specifying the net payment due date at which a particular dunning level is reached.
5.     Specifying the dunning notice you want to send to your customers.
The following dunning procedures have been defined for dunning customers:
0001     Four-level dunning notice, every two weeks
Z030     Interest calculation after 30 days
The dunning procedure Z030 specifies that customers who do not pay within 30 days are automatically in arrears. The customers receive a dunning notice without interest amounts. From then on, interest is calculated for the open items using the interest calculation program (see also the section on the interest calculation program).
Procedure
1.     Access the activity using one of the following navigation option:
Transaction code     SPRO
IMG menu     Financial Accounting (NEW) ® Accounts Receivable/
Accounts Payable ® Business Transactions ® Dunning ® Dunning Procedure ® Define Dunning Procedures
2.     Choose New procedure.
3.     Make the following entries:
Field name     Entry
Dunn.Procedure     0001
Name     Four-level dunning notice, every two weeks
Dunning Interval in Days     014
No.of dunning levels     4
Total due items from dunning level
     3
Min.days in arrears (acct)
     6
Line item grace periods
     2
Public hol.cal.ID
     08
Interest indicator
     01
Standard transaction dunning     X
Ref.Dunning Procedure for Texts     0001
4.     Choose Dunning Levels.
5.     Maintain the following entries:
Field name     Dunning level 1     Dunning level 2     Dunning level 3     Dunning level 4
Days in arrears     2     16     30     44
Calculate interest               X     X
Always dun                    X
Print all items               X     X
Payment deadline               10     7
6.     Choose Charges, enter currency EUR and make the following entries:
Field name     Dunning level 1     Dunning level 2     Dunning level 3     Dunning level 4
Dunn.charge     5     5     10     10
7.     Choose Minimum Amounts, enter currency EUR and make the following entries:
Field name     Dunning level 1     Dunning level 2     Dunning level 3     Dunning level 4
Minimum amount     1     2     5     10
Min.amt for interest     1     5     10     10
8.     Choose Dunning Texts, enter company code BP01 and choose account type customer. Make the following entries:
Field     Dunning level 1     Dunning level 2     Dunning level 3     Dunning level 4
Form     Z_F150_DUNN_01     Z_F150_DUNN_01     Z_F150_DUNN_02     Z_F150_DUNN_02
9.     Choose Save.
10.     Choose Back and maintain the next dunning procedure.
11.     Choose New procedure.
12.     Make the following entries:
Field name     Entry
Dunn.Procedure     Z030
Name     Interest Calculation after 30 days
Dunning Interval in Days     014
No.of dunning levels     2
Public hol.cal.ID
     08
Interest indicator
     01
Standard transaction dunning     X
Ref.Dunning Procedure for Texts     Z030
13.     Choose Dunning Levels.
14.      Maintain the following entries:
Field name     Dunning level 1     Dunning level 2
Days in arrears          14
Calculate interest     X     X
Print all items     X     X
Payment deadline     7
15.      Choose Dunning Texts, enter company code BP01 and choose account type customer.
16.      Make the following entries:
Field name     Dunning level 1     Dunning level 2
Form     Z_F150_DUNN_04     Z_F150_DUNN_04
17.      Choose Save.
3.3.3.4.1.2.2     Defining Dunning Procedures
     Use
In this activity you enter the settings that control the dunning program.
     Procedure
1.     Access the activity using one of the following navigation option:
Transaction code     SPRO
IMG menu     Financial Accounting (NEW) ® Accounts Receivable/
Accounts Payable ® Business Transactions ® Dunning ® Dunning Procedure ® Define Dunning Procedures
2.     Choose the menu Environment ® Company Code Data and make the following entries:
Company Code     Dunning by Area     Separate Dunn. Notice     Ref. Comp. Code      Sort. Variant Acct     Sort. Variant Items     Dunn. Comp. code
BP01               BP01     K1     P1     BP01
3.3.3.4.1.2.3     Defining Interest Rates
     Use
In the dunning program, an interest rate of 7.68% has been defined for interest indicator 01 and the currency EUR. This interest rate is the same as the rate set for the interest calculation program and is calculated from the discount rate (2.68%) and a surcharge of 5%.
     Procedure
1.     Access the activity using one of the following navigation option:
Transaction code     SPRO
IMG menu     Financial Accounting (NEW) ® Accounts Receivable/
Accounts Payable ® Business Transactions ® Dunning ® Dunning Procedure ® Define Interest Rates
2.     Make the following entries:
Interest Indicator     Currency     Valid from     Debit Interest     Credit Interest
01          01.01.1991     7.680     7.680
01     PHP     01.01.1991     7.680     7.680
3.3.3.4.2     Printout
3.3.3.4.2.1     Defining Sender Details for Dunning Forms
     Use
In this activity, you define which standard texts are used for the header, the footer, and the sender address in the letter window for each company code.
     Procedure
1.     Access the activity using one of the following navigation option:
Transaction code     SPRO
IMG menu     Financial Accounting (NEW) ® Accounts Receivable/
Accounts Payable ® Business Transactions ® Dunning ® Printout ® Define Sender Details for Dunning Forms
2.     Make the following entries:
Dunning Area     Text ID     Header Text     Footer Text     Signature Text     Sender
     ADRS     ADRS_HEADER     ADRS_FOOTER     ADRS_SIGNATURE     ADRS_SENDER
3.3.3.4.2.2     Allowing Dunning with SAP script Forms
     Use
You have the possibility to use either SAP script forms or Smart Forms in the dunning procedure. In this transaction you have to specify which forms are used for dunning in this system.
This table is cross-client. Any changes you make in this table will take effect in all clients of your system.
     Prerequisites
You have processed the previous mentioned steps.
     Procedure
1.     Access the activity using one of the following navigation options:
Transaction code     BF31
IMG menu     Financial Accounting (NEW)  Financial Accounting Global Settings (New)  Tools  Customer Enhancements  Business Transaction Events  Settings  P/S Function Modules  u2026 of an SAP appl.
2.     On the Change View Publish & Subscribe BTE: SAP Enhancement: Overview screen, check - and if necessary change - the following entries:
Field name     Description     User action and values     Notes
Event     Event (Business Transaction Event)     00001720     this entry already exists
Country     Ctr (Country ISO Code)     Blank
Appl.     Appl. (Application Indicator for BTE)     FI-FI
Funct     Function Module     FI_PRINT_DUNNING_NOTICE     this function module needs to be entered if SAPSCRIPT forms should be used
3.     Choose Save.
If you want to use Smart Forms then you have to enter for above mentioned event 00001720 function module FI_PRINT_DUNNING_NOTICE_SMARTF. Please be aware that in installation guide and configuration guide the set up for customizing is only made for dunning with SAP script forms and not for dunning with Smart Forms.

Vendor master "fixed-line telephone" and "standard fixed-line telephone"

Hi,
Can any one pls explain what is the difference between
1) The telephone number is a fixed-line telephone and
2) The telephone number is the standard fixed-line telephone
Vendor master record
I am not able to find both the fields.
Thx
Jai

Dear,
As found...
This field indicates whether the phone number entered is a mobile phone number or standard phone.
Indicator: Telephone is a Mobile Telephone
This field specifies whether the telephone number is a mobile telephone number.
Input values
' ' : The telephone number is a fixed-line telephone
'1' : The telephone number is the standard fixed-line telephone
'2' : The telephone nubmer is a mobile telephone
'3' : The telephone number is the standard mobile telephone
Dependencies
Either the standard fixed-line telephone number or the standard mobile telephone number is also the standard telephone number .
In older data sets, this field may have also have the value ' ' for the standard fixed-line telephone.
Effects on Customizing
In Customizing, you can specify whether the SMS-compatible indicator is to be proposed for new mobile telephone numbers created in dialog by choosing General Settings -> Set countries -> Define Mobile Telephone Attributes for each country.
Preferred Telephone Type
For many SAP applications, you have to mark one telephone number as the standard telephone number. This can be either the standard fixed-line number or the standard mobile telephone number. This field indicates which of these numbers takes precedence.
Example
When you call a business partner, this field is used to determine whether the standard fixed-line telephone number or the standard mobile telephone number is used.
Use
Choose the value 'Telephone' if the standard fixed-line telephone number is to be the standard telephone number and 'Mobile Telephone' if the standard mobile telephone number is to be the standard telephone number.
Regards,
Syed Hussain.

Reevaluation indicator in Vendor master

Similar Messages

Maybe you are looking for