Vendor Master Validity

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

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

Similar Messages

Vendor Master - Validity date table

Hi ,
   Do we have table for maintaining the validity
   period of the Vendors.if so , help me out.
   or how the validity period is taken for the
   vendors.
Thanks.

This thread give you very good idea !!
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-acct/substitution-or-validation-on-vendor-master-data-518622#
Thanks
SK

Validation for vendor master data creation

Dear All,
Can anybody suggest how to apply validation while creation of vendor master data. As this can not be done through GGB1 as it is ment for document level validation. Please suggest any user exit or badi or validation path for this.
Thanks & Regards

hi,
the enhancement for vendor master is SAPMF02K, you can easily add your own check, pls. check in tcode SMOD!
hope this helps
ec
>
Srinivasa Maruvada wrote:
> Hi
>
> Check TCode for validation OB28, for substitution OBBH
> and also OKC9 which may helps you.
> Cheers
> Srinivas
your post is rubbish, substitutions and validations are in use in document posting, not for master data creation. Even the OP told this, when he asked his question...

Can validation check can be set for vendor master record .

Hi Experts ,
User wants to remove two existing payment methods,instead of removing i think to set validation for the vendor master record .
can validation can be set for vendor master record ?
PLease suggest me with advice.
Thanks
Pardha

Hi,
To my knowledge, validation can be set up for accounting document.
Though a work around, create a validation such that
Make the user enter the Payment method to be mandatorily entered by the user.
Also, restrict the unwanted payments as well in the same validation.
In case of APP also, the payment method in the document will take precedence.
Regards,
Sridevi

How to reference vendor master data in Document Validation?

Hi,
We would like to display a warning message as follows during AP invoices posting if the following details have been defined in the vendor master data.
a.        u201CAlternate payee has been definedu201D
b.        u201CPermitted payee has been definedu201D
c.        u201CPartner bank has been definedu201D
May i know the best method to do this? If i use document validation, how can i reference these details sitting in the Vendor master data?

Hi,
You can use custom validation program (Z*) by copying standard validation (RGGBR000) program.
Modify the validation program to check table vendor master data.
After that, you need to assign this custom validation program to GBLR application area in GCX2.
Thanks

FK01: Vendor Master Record Validation Table is not maintained

Hi Experts,
Appreciate your help on this matter: I have created a new Vendor Account Group and tried to used it. However, upon saving I encountered problem: error message Vendor Master Record Validation Table is not maintained. Do I missed some configuration?
Thank you very much!

Hi,
STEP 3 : In Financial accounting > A/R A/P > Business Transactions > Outgoing payments > Manual Outgoing payments >
Define Tolerance (Vendors)
STEP 4 : Create a GL A/c Creditors in FS00 as a balance sheet a/c and in control tab give reconciliation type as Vendors
and Field Status Group G067. Assign this account in company code data in FK02.
Regards,
Sadashivan

Vendor Master Number validation

Hi,
I want to create vendor master as 123456789A i.e first 9 digits is number and the last is the alphabet, this can be achieved with number range as 000000000A to199999999Z, but my problem is, even if I do not maintain the last unit as alphabet the system is allowing me to proceed i.e with all the 10 digits as numbers.
My requirement is, if the last digit is not an alphabet then the system should give me a error, kindly let me know how this can achieved.
Thanks
Suresh

Hi,
You can implement user-exit for validation of vendor master data: SAPMF02K.
Regards,
Eli

What credit limit is valid - the one set at Vendor master , PO or invoice ?

Dear Friends,
I want your suggestions, if weather there is any standard guidelines on which credit limit is followed if I maintain different values at Vendor master, purchase order and at Invoice level
Looking forward for your thoughts ?

There is no credit limit for vendors, as we buy goods from vendor and not sell it to them
There are release strategies in MM. Please clarify your setup.
Regards,
Gaurav

Automatic validation of Bank routing no# in teh Vendor master

We are on ECC 6.0 and are live on Accounts payable in USA. Is it possible to validate the bank routing numbers automatically in Vendor master? Or any other automated solution through Bolt-On products..
Thanks in advance for your response.
Raj Una

HI,
The condition type has nothing to do with the consignment settlement.The factor which influence for
consignment settlement thro MRKO is the price u have given in PIR,PB00 & the tax code which u have
entered in the PIR tax code tab.It is no way connected to the vendor master.So if the tax code is
changing for different time period ask them to change manually.
regards
murugan

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

Time-dependent Vendor Master & Handling Special Characters

Hi,
I need to extract time-dependent Vendor Master.
1. The data source for 0VENDOR does not have fields to hold the valid date range.
2. Does the Master data in R/3 for Vendors will hold the valid date range?
3. The text for 0VENDOR provides time-dependent, but how to map the valid from and valid to fields?
Handling Special Characters:
We are trying to extract data from Legacy system via DB Connect. The item text field consists of special characters. Of course in BW customization we can specify all the special characters to consider. But the special character we observed is 'square' symbol i.e. 'new line character' in Oracle. We are updating this to an ODS object. When looked at error log, observed that green light for the number of records transferred and updated, but finally when it load into ODS object and activates popping up the error message saying 'could not recognize special character'.
Please help me getting the 2 issues resolved.
Thanks in advance.
Regards,
Sudhakar.

Hi Everyone,
Thanks for inputs on Special characters issue...
Finally resolved with below piece of code in the start routine:
DATA: FLAG,
 OFF TYPE I,
 LEN TYPE I VALUE 1,
 ALLOWED_CHAR(95) VALUE
'0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ`~!@#$%^&*()-_=+ ' &
'abcdefghijklmnopqrstuvwxyz:;<>,.?/|\{}[]"'''.
CONSTANTS: C_CHAR VALUE '-'.
LOOP AT DATA_PACKAGE WHERE NOT /BIC/ZI_DESC IS INITIAL .
 DO.
 IF DATA_PACKAGE-/BIC/ZI_DESC CN ALLOWED_CHAR.
 REPLACE SECTION OFFSET SY-FDPOS LENGTH LEN OF
 DATA_PACKAGE-/BIC/ZI_DESC WITH C_CHAR.
 FLAG = SPACE.
 ELSE.
 FLAG = 'X'.
 ENDIF.
 IF FLAG = 'X'.
 EXIT.
 ENDIF.
 ENDDO.
 MODIFY DATA_PACKAGE.
ENDLOOP.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
I have seen the link sent by 'Eugene Khusainov' today. Thought putting my piece of code that may help others...
Regards,
Sudhakar.

Vendor master Archiving

Hi Experts,
 I am trying to Archive the vendor master.The process i am following is like:
1.In XK06 - Deletion flag for the vendor.
2.Then went to T-code-F58A.Then in that i maintained the Variant name as vendor_del.After that i click on maintain & give the required vendor to be Archived.
3.After that when i am trying to come out of that screen the error msg is coming as
Links stored incompletely:
Message no. FG166
Diagnosis
Customer/vendor links are to be taken into consideration when archiving or deleting customers or vendors. To do this, link data from the database is required which in this case has not yet been put together.
System Response
Neither archiving nor deletion was carried out.
Procedure
Run program SAPF047 in the background at a time when no customer/vendor changes are being made. This program puts together the link information in table KLPA so that links (for example, specification of an alternative payee or dunning recipient) can be taken into consideration during deletion or archiving. You can find more information in the documentation for SAPF047.
This is the MSG i am getting in Help
4.After that i tryed to link that table KLPA.But not able.
So pls guide me the exact process to do the same.
Thanks,
Das

Please read the documentation of the program SAPF058V :
Program SAPF058V allows you to automatically set archivable vendor master data for archiving. The same checks are carried out as with archiving.
Firstly a proposal list is issued. You can set and save the archive flag in this list.
If the program is started in the background, the archive flag is set automatically for all archivable data.
Archiving itself is only permitted for master records where the archiving flag is set. If a proposed archivable data record is to actually be archived, the archiving flag must be set.
You can restrict the quantity of master records to be checked by selecting
o Vendor numbers
o Minimum number of days in the system
o Company codes, if FI data is to be considered
o Purchasing organization, if MM data is to be considered
o System criteria (see below)
Requirements
 Program modes
The program can be run in three different modes:
1. Only general data is set for archiving (A segments)
2. Only application-specific data is set for archiving (B segments)
3. General and application-specific data is set for archiving
Check whether data can be archived
Mode 1: The A segments selected must be set for archiving, and no dependencies to B segments may exist. For example, no company code data may exist for a vendor if the general data is to be archived.
Mode 2: The application-specific data must satisfy the relevant application criteria:
FI: Company code data is archivable if no special G/L figures or transaction figures and no open or cleared items exist. In addition, the archive flag must be set at company code level.
MM: Purchasing organization data is archivable if the archive flag is set at this level.
Mode 3: The A or B segments selected must be set for archiving. The A and B segments of a record are deleted if the archive flag is set in the A segment. The B segment only of a record is deleted if the archive flag is set in the B segment (in this case, the A segment is only copied to the archive). In addition, the application-specific data must also satisfy the criteria from mode 2.
The A segments are archived if all of the dependent B segments are archived and the vendor is not referred to anywhere else. If this is not the case, the A segments are copied into the archive.
For all modes: Vendors cannot be archived if they are referred to on a general/company code level from other vendors (for example, financial address or alternative payee). This check can be deselected however (use the field "FI link validation off") if you know that all the vendors that refer to the first vendor are to be archived in this or a following run.

Standard screen changes-addition of a field in vendor master table

Hi Champs,
My requirement is to add a field in LFB1 table.
I have added the field in the table using append structure, that was fine.
I need to add the same for input/output on the screen 215 of program SAPMF02K (for the screen of Payment transaction Accounting at company code level).
The screen enhancement available for vendor master is for adding a new sub screen. But I need my field to be input/output on screen 215 of program SAPMF02K (for the screen of Payment transaction Accounting at company code level).
The only option left with me was to make changes in the Standard SAP screen as there are no enhancements available to suffice my requirement.
After taking the access key, if suppose i make changes in the standard screen viz. given a dictionary refrence to the new field created on screen 215. My query is do i need to do any kind of coding in PBO or PAI of the screen.
A quick reply would be overwhelming.
Thanks
Regards,
Nishant

Ofcouse Nishanth, u need to code in PBO and PAI event.
PAI -> To read the User input and for doing validations or some thing as per ur requirement
Hope this helps,
Shiva kankanala

Error Message WY 030 . Vendor master creation

Hi all
The Error Messgae *WY 030 :Purchasing organization &1 assigned to company code &2, not &3*:+ Need to activate as a ERROR MESSAGE.+
During Vendor creation ,if the wrong purchase organisation is selected, system is allowing to create the vendor master.
Even though ,I have done the Setting in the following , the error message is not reflectiog
1. Message Control for Vendor Master Data
2.T.code : OBMSG
3.T.code : OBA5
Thanks & Regards
DP

strange.
in my system WY 030 message is this: Entry & in table & does not exist
what do you call a wrong purchasing organisation?
I guess you have several organisations in the system.
lets make an example:
purchasing PORG1 is assigned to company code CC1
purchasing PORG2 is assigned to company code CC2
purchasing PORG3 is assigned to company code CC3
and I guess
you want prevent a user to create a vendor master with company code CC1 and purchasing org PORG2
You just cannot do this.
All company codes are valid and all purchasing orgs are valid.
It is just to combination that would logically not make sense while creating.
but if this vendor is used in all companies, then you have 3 CC views: for CC1, CC2 and CC3,
and you have 3 purchasing views for PORG1, PORG2 and PORG3
would you still say that a vendor master with CC1 must not have PORG2 ?

Signature error while attaching document in vendor master

Hi
While attaching word docuemnt in vendor master through"Store business document" option, I am getting below error
HTTP Error: Signature verification failed :No valid signature
Could you please how can we avoid this error so that the document will get stored successfully
Regards
Subbu

Resolved.
Filename path was not correct.

Vendor Master Validity

Similar Messages

Maybe you are looking for