Vendor master configuration in IDES?

hii experts
In IDES, how i can configure the vendor master ??
So many its asking while creating vendor master in XK01..
What are all the configuration has to be done befor creating vendor master in XK01 for My company code in IDES
Thanks

>
MM group wrote:
> Hii
>
> What u said , the same i have configured .
>
> What about the reconciliation account ..etc ??
>
> Thanks
Recon account is a group of G/L accounts which is created by FI consultant. We just assign the recon account to the vendor master or usually FI maintains the company code side of vendor master.
Recon Account
use FS00/FS02
- create a GL account
- Go to Control Data Tab
- Choose appropriate Recon. account for acct type (Customer/Vendor)
- save it.
Reconcilliation A/c is just a G/L. You can prepare a G/L by using T.code FS00.
In Type/description tabe : select B/S A/c
In control data tab : select the reconcilliation A/c for account type i.e. whether it is customer or vendor or asset etc.
In other tabs : select as per your requirements and then save the entries.
In this way you can create a new reconcilliation A/c
Edited by: Afshad Irani on Jun 29, 2010 9:54 AM

Similar Messages

Vendor Master or F-58 field

Good Day,
We are doing download program which involves F-58 to bank as a process of automatic payment. In this file that will be sent to bank to process payment, the bank requires SAP to capture a field which will indicate "Agent Charge" . Agent Charge is similar to bank charge.
Agent Charge field will have to just show three (3) scenarios where
1- Beneficiary - Vendor will bear the cost
2- Company - The company will bear the cost
3- Shared between Company and Beneficiary.
We just need a field that can cater or indicate the above scenario in SAP (either Vendor master or F-58 ). User should be able to select during the F-58 or in Vendor level .
I have search in Vendor Master but no idea which field that i can configure. And all text fields in F-58 are in use.
Appreciate your kind advice.

Dear,
This can be done with some program modification to F-58, ask your ABAPer to do a customized program for your requirement.

Contact Person on Vendor Master

Hi Experts,
I turned contact person as required on Vendor Master configuration. However, it still doesn't show up on Vendor Master create/change/display. Would you pls let me know what else I need to do to make this happen?
On the general data section, it only has Address, Control and payment transaction. How do I add the contact person?
Thanks a lot!!!

Sorry dear dnt knw abt Multiple sales person but for check ing the Single name follow this path :
While entering Thru XK03 input the Purchasing Org and give a tick for purchasing data and check the same thru
GOTO > Purchsing Org Data > Purchsing Org
Revert

Need config table which stores data for Vendor Master changes

Hi Gurus,
I need to have the name of the config tables which store the details of the Vendor Master configuration changes based on account group information.
For Example,
For a given Account Group(ZM09), the VAT Registration field in the control data tab of the transaction XK02 is suppressed. and for other Account Groups the VAT Registration field is appearing in the Control data tab of the XK02 transaction.
So I need to determine at run time for which vendor account group the VAT Reg field is suppressed and for which it is appearing.
Hence I require the name of the Config table in SAP which stores this information.

Hi,
Use this transaction S_ALR_87010039 (Program RFKABL00)
You can select all levels of changes (i.e. General, Company Code, purchasing org)or individual levels only.
If you want the tables then CDHDR & CDPOS will provide all the details.
Regards
Hiren K.Chitalia

Tax Configuration in Vendor Master

HI
What are all the steps to be followed in order to establish tax criteria in Vendor master i.e the fields that want to be inputted for Tax configuration .
Any one please explain me in detail
Thanks & Regards,
senthil.

when i maintain it is throwing error message :
Entry USER does not exist in USR02 - check your entry
Message no. 00058
Diagnosis
Input values must be defined in Table USR02. The value or values 'USER ' are not specified in this table.
Procedure
Check whether the input is correct and correct if necessary.
Procedure for System Administration
If this is not an incorrect entry, check the system settings and change them if necessary.
If there is a connection to the Customizing system, you can maintain the system settings by choosing Customizing in the Performance Assistant or Maintain Entries (F5) when displaying the help in a modal dialog box.
please help me to solve this issue
Thanks & Regards,
senthil.

Detect potential duplicate vendor master records

Hi all,
Our external auditor has the following comment:
'Match codes and message control can be used to help identify duplicate vendor records. Fields such as Name, Address and Country can be set as searchable fields in order to detect potential duplicate vendor records. The message control (with identifier 144) in SAP can give a message prompt when duplicate vendors are identified.
We noted that your system had not been configured to display a warning message if the name or address, etc of a new record is identical to an existing vendor record.'
Any idea to implement this?
I searched for message 144 and found that there is a similar message in message class F2: 'Vendors found with same address; check', but I cannot find where to trigger this error message.
Please help.
Best Regards,
Chris.

Goto SPRO-Financial accounting-Accounts Receivable and Accounts Payable
-vendro account-master data- Preparations for Creating Vendor Master Data
- Change Message Control for Vendor Master Data
here you can maekk the messge 144 to Error

Vendor Master- CIN details Upload

Hello Experts
I want to upload the CIN details of the vendors. We are working on implementation of CIN, so please suggest what all things should be taken care.
We are planing to go with LSMW, recording method.
But when i tried that in ides, the pop up window for cin details was not coming in XK02 transaction. What can be the issue?
Also, is the concept of small scale industries still maintained in india?
Also there is a field 'type of vendor' in the excise duty tab in the CIn details. whats its significance?
Regards

hi,
go to
spro - logistics-general - material master - Configuring the Material Master - Maintain User Settings
here you need to put the SAP user ID. Only these people can view the CIN data at Vendor Master (XK01, 02, 03). For them, the CIN Data button will be displayed.
You can upload the data by LSMW, but you need to do the above mentioned setting in each and every client. For LSMW the screen should be identical in all clients.
You need to use the SAP ID for which you have given access of the CIN Data Tab.
I am sure this will help you. I have used it in my earlier projects.
Regards,
Anand

Idoc configuration in IDES??

hi experts ,
Can somebody explain me about , how do we do entire Idoc configuration in IDES and we can execute the same as sample in IDES
Explain me in step by step for outbound and inbound ...
Thanks
Edited by: MM group on Jul 2, 2010 10:44 AM

1 Logical System
2 Assign Logical system
3 RFC
4 Port
5 Customer distribution model
6 Partner profile
7 CDM distribution
Tcode : SALE
First 2 steps not necessary ( Basis work already done )
Two logical system created
Ls110 -Sender
Ls800 - Receiver
RFC
RFC establishment SM59
Receiving system IP address or hostname
System number, client id
Username, password
Ports
We21 define ports
TRFC ale
File Edi
CPI_C - R2 connections
In the port we need to define Port name and RFC destinations
And version
Customer Distribution Model - BD64
Sender
Receiver
Message type
Partner profile we20 , BD62
Partner may be customer, vendor, logical system
In BD62 define the partner system (LS800)
One more additional entry SYNC for synchronization
Post processing Agent - workflow
MATMAS 03 03 is the version
Collect idoc we need to trigger
Transfer idoc will be send immediately
With message control
Which program need to run for generating the idoc
With out message control
For some of the programs have inbuilt idoc generation for that case no need to mention program name
Process code
Distribute CDM
Receiving System:
Partner profile is going to control all the thing
BD64 - > edit - > model view - > distribute
BD67 Function module assigned to the process code
BD10 used to create idoc for material
Master idoc generated only buffered
One master idoc multiple communication idoc
One communication idoc generated
We02 idoc satus

IDOC Types for Purchase Orders, Vendor Master and Goods Receipt

Hello All,
Can any have idea about the IDOC Types that can be used for triggering when the actions creation/change/deletion on Purchase Orders or Vendor Master or Goods Receipt is performed?
Please let me know the names of IDOC Type, Process Codes, message type... and all the other required information...
Thanks in Advance,
Kumar.

Hello Ferry,
Thanks again for the IDOC Types. I have another question. Can we use those IDOC types for creating/changing/deletion of Purchase orders or Vendor Master or Goods Receipt happens? I mean can we configure in such a way that when ever there is a change or deletion of PO or VM or GR happens?
I have got to know about the IDOC PORDCH01 which can be used for Purchase Order. Can u suggest me which can be used for PO's?
Regards,
Phani.
Message was edited by:
Sivapuram Phani Kumar

Group Key field Match Code in Vendor Master

My client have a unique requirement to group the vendors. We are using the Group key field in the vendor master for this purpose, We want to create a match code which can link the vendor number to the group key field. Anyone have any idea on how this can be developed or configured.
When I looked at the help on this field Following is the help mentioned. but I am not sure how the match code for the group key would work or how to configure this. I appreciate any inputs on this issue.
Group key
     If the customer or the vendor belongs to a group, you can enter a group
     key here. The group key is freely assignable.
     If you create a matchcode using this group key, group evaluations are
     possible.

I know it has to be done by ABAP group but I got confused with the help on this field.. ABAP group says it is going to be a core code change since there is no user exit available for that field.

Account groups for Partner Roles in Vendor Master

1. Can we use same account group to create the vendor master for the different partner roles? for the partner roles like goods supplier, invoicing party, order party, etc do all these need to have different account groups , example one account group for goods supplier, one account group for invoicing party, etc , etc.
2. why we need the configuration for partner role in purchasing documents besides partner role settings for vendor account group. what is the logic behind to have partner role dependent settings for purchasing documents.
If we do not maintain for partner role settings for purchasing documents what effects it will cause?

> 1. We can have 1 account group represent all partner role or separate account group for each role.
1.If we use the same account group, the field selection control for fields will be applicable to partner roles also. If we have made vendor schema as mandatory in vendor master than we have to assign to partner vendor also. Example ordering address will not require company code data only purchase data, it will not require also pricing procedure as mandatory as no price determination will be required for ordering address.
I think we have to use combination of account group -same account group and different account group will defining vendors for partner function.
Do we require to assign vendor schema group to following vendors roles- goods suppliers, invoicing party and payee.
If we do not assign vendor schema group will these partner role determine price from the VN partner role. For example VN (vendor) has vendor schema group assigned, no vendor schema group assigned to invoicing party, then while doing MIRO the invoicing party will be defaulted. Do the price determined for VN role will be populated for invoicing party in MIRO?
> 2. we need partner role in purchasing doc because we can copy partner role from vendor master to purchasing document
It means we need to assign similar roles in schema for vendor account group and purchasing documents. If you see the schema in config for partner determination in IDES system, different roles exists in vendor schema and purchasing document schema.
This is creating confusion for me to understand.
Please clarify
2. we need partner role in purchasing doc because we can copy partner role from vendor master to purchasing document

Creation of Business partner by using the vendor master

Dear all ,
I have a requirement as follows. I Have already vendor master created in MM .Now the requirement is while creating Business partner I have to use this vendor as the business partner .
Can experts suggest the possibility of this .
Regards.
Arjun.

Hello Arjun,
Yes, this feature also works in 4.7. What has happened is that in ECC 6.0 the BP functinality has been totally redefined with a lot of automations. As such, if properly configured then in ECC 6.0 there is no practical use of the FLBPD/FLBPC Tcodes. However, in 4.7, both these traqnsactions should be working fine. The SAP ntes that I have mentioned are however only for ECC 6.0.
Kind regards,
Suvarghya Dutta
Edited by: Suvarghya Dutta on Nov 27, 2008 4:02 PM

Vendor master file report.

Dear All,
I always use S_ALR_87012089 display changes to vendors to check vendor master data if they are created or updated in accordance with proper approvals (not a workflow in SAP).
Recently, I see other tcode S_ALR_87012090, but do not know what is its use.
Can you please let me know detail about S_ALR_87012090.
Thanks
Ndhoan

Hello,
The program S_ALR_87012090 displays changes to the sensitive fields (such as Bank Account, Bank control key etc. configured defined by us). The reviewer can confirm or refuse the changes interactively from the list produced by this report.
Thanks,
Venu

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

Payment terms in vendor Master

Hi,
In XK01- create vendor master, There are two payment terms--> payment transaction field and other in purchasing organisation data.
Is there a configuration which will default the payment terms in purchasing org screen based on the inputs in the company code screen
Regards,
Srijith

No there is no such customizing.,
Not every vendor with purchasing org data needs company code data. Not every vendor with company code data needs purchasing data.
The payment terms at company code level are used if you post non-PO related invoices with FI transactions.
the payment term of purchasing org data is used if the process is PO related.

Vendor master configuration in IDES?

Similar Messages

Maybe you are looking for