Permitted payee in Vendor master

Hi Experts,
I have created a Vendor master with a Permitted payee in the General--Payment transactions. I know this is at a general level.
The permitted payee is also defined in the same company code.
When I go into FB60 and look for "Payee" , it says that no alternate payee is defined. Both tj are "NOT" one time vendors
What else am I missing ?
Thanks in advance,
GB

Hi,
You can define alternative payee on invoice entry (A. Payee in Document) or fixed in your master record (payment transaction). Check which assigment was defined in FK02. Check also if you have A.P. in invoice details.

Similar Messages

Alternative payee in vendor Master - In House Cash

Hi,
We have In House Cash Set up for Payments..
For a particular vendor X0001, the Bank Country is DK and has an alternative Payee maintained in the vendor master which has an alternative Payee X0002 and this X0002 has Bank Country SE.
The Invoice is in currency SEK..and payment Method A
The table IHC_TAB_APM_TT is maintained with the following conditions..
1200          Bank Transfer          A                      100200
1200          Bank Transfer          A                 GBP     100200
1200          Bank Transfer          A                 SEK     100200
1200          Bank Transfer          A            DE     EUR     100100
1200          Bank Transfer          A            DK     DKK     100100
1200          Bank Transfer          A            PL     PLN     100100
1200          Bank Transfer          A            SE     SEK     100100
The problem is after execution of F110, the inbound IDOC in IHC0 is not getting generated..it is in error..
I checked in Debug mode and it is picking up transaction type 100200 instead of 100100 . Any reason why this is picking up 100200 and not 100100 transaction type. If the Vendor Bank Country(Alternative Vendor's Bank country) is SE and the transaction currency is SEK, it should pick up the last record.. rather it is picking up the third record.. Any idea why?
Thanks in Advance..
Regards,
SAPFICO

Hi,
Can you please check whether it is picking the recipient country as SE in debugging mode itself. I think it might have not picked it.
Also just for test purpose, pls remove this record 1200      Bank Transfer      A      SEK     100200 and then try running the scenario.
Regards,
Ravi

Alternate Payee AZ partner role in Vendor Master pop up in PO

Hi,
Can anybody help when multiple alternate payees are created in vendor master, when the same vendor is called in a PO, the system should pop up the multiple payees for user to select the required payee. This is coming for other partner roles OA& PI but not for AZ. Does anybody has a solution.
regards
Bala

Thanks for the reply.
AZ is not marked as unique. And we are able to enter multiple payees in permitted payees in vendor master. But when you get to PO it must propose the user for to select any one, right and that is not happening for only AZ. Let me know.
regards
bala

Vendor Master Partner Function

Vendor Master Partner Function - Alternate/Permitted payee configuration pls tell me configuration

Hi:
For Creating Vendor master, refer to SAP Best pratices
help.sap.com/bp_iasifrsv1470/BBlibrary/Documentation/I50_BPP_EN_DE.doc
For Vendor Master Partner Function
http://www.copacustomhelp.state.pa.us/infopak/nav/procurement/pr%20master%20data/file1539/index.htm
http://www.sap-img.com/materials/procedure-for-setting-partner-functions.htm
For Permitted Payee in Vendor Master, refer to
vendor permitted as payee
For Alternate Payee in Vendor Master
help.sap.com/bp_bblibrary/500/Documentation/J03_BPP_01_EN_IN.doc
Please let me know if you need more information.
Assign points if useful.
Regards
Sridhar M

Individual Spec. checkbox on Vendor Master

Hello !
On the Payment Transaction tab (in the General Data section) of the vendor master there is a checkbox 'Individual Spec.'.
I would appreciate it if someone could explain how this checkbox is used.
We would like to specify a alternate payee directly in the PO... or change the alternate payee during MIRO.
Is this checkbox for that purpose?
Where on the PO can we specify the alternate payee?
Where on MIRO can we specify the alternate payee?
Please advise.
Thanks,
Anisha.

1. In case you tick Individual specification box, while executing automatic payment, you have the option of entering the address or bank details which actually differs from the one in the Vendor Master Record.
2. You can specify alternate payee in Vendor Master Record.
3. To make payment to different vendor : Make the payment through F-53, Then go to FCH5, assign the check manually.

Standard report showing Permitted Payees linked to vendor

Hello,
Does anyone know if there is a standard SAP report that shows the permitted payees linked to a vendor without having to go to table LFZA?
For example, I have a vendor 112222 ABC company and on the payment transactions global screen, I have defined three permitted payees in field EMPFK:
5555 ABC East
6666 ABC West
7777 ABC South
I am looking for a report that shows me:
Vendor                 Permitted Payee
112222 ABC Company     5555 ABC East
                       6666 ABC West
                       7777 ABC South
Does anyone know if this exists as a standard report?
Thanks,
Linda

Linda
I am unaware of a standard report like this.
The only standard reports are the Vendor list (S_ALR_87012086), Address List (S_ALR_87012087) and Display changes to vendors (S_ALR_87012089/90).
The only way to do this is write a quickviewer/SAP Query report.

System Not Picking Permitted Payee address when the Main vendor has PO Box.

Hi,
When we are doing payments to Permitted Payee ( Vendor ) the system is printing the checks with PO Box ( Post Box no. ) number of the Main vendor .
But when we deleted the PO Box number field in Main vendor, then the system is printing the check with Permitted payee address.
When Main vendor number has PO Box field populated with a number, selected credit address ( Permitted Payee address ) will not print on check.
When there is a Permitted Payee the system has to consider that Permitted Payee address only. But system is not doing like that.
Please advice what is the problem.
( They are paying through APP run ).

Can you please tell me where it is.
Thanks for your prompt reply.

Alternative Payee set up in vendor master record for payments....

Hi all,
I am facing the problem on alternative payee set up in vendor master record.
I have done the following settings but its not working.
1) Created alternative payee vendor (XYZ) and blocked for posting.
2) Created main vendor (ABCD) and given alternative payee vendor name (XYZ) in alternative payee field payment transactions tab of(general data + company code data) main vendor.
3) Created an invoice for main vendor (ABCD) using F-43.
4) Trying to make payment to main vendor (ABCD) in f-53. So when i simulate the document system supposed to show automatically the alternative payee vendor number . But itu2019s not showing and still making payment to main vendor not alternative payee.
Please help me to solve this issue. Is there any other settings need to be done to achieve this scenario (alternative payee).
Thank you very much.

Hello,
thank you for your quick reply.
1) i taken out the payment block for alternative vendor (XYZ) and tried again the above 3rd and 4th steps but still not working system paying to main verdor (ABCD) instead alternative payee(XYZ).
2) i blocked for payment posting the main vendor(ABCD) and tested same still not working.
need helps to resolve this.
thanq.

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
<b>Links stored incompletely:</b>
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.

Permitted payee error message while posting an invoice

HI,
I already define permitted payee in the vendor master record.But when i am creating an invoice through FB60, in the payment segment we are having an option to select payee. When i am clicking F4, then it is giving me an error message stating that-
No alternative payer/payee defined
Message no. F5747
Can anybody help me out in this. Points will be awarded.
Thanks and regards,
Shree.

HI,
I already define permitted payee in the vendor master record.But when i am creating an invoice through FB60, in the payment segment we are having an option to select payee. When i am clicking F4, then it is giving me an error message stating that-
No alternative payer/payee defined
Message no. F5747
Furthur to this, when i am entering manually this number there, then it is giving me an error that
Payee 7109 is not defined for account 1023861 in company code 3000.
I am creating an invoice for company coe 4000 and the paying company code for this is 3000 while making payment throgh F110. But i see that this account exist only for the company code 4000 and not for the 3000.
Main account is 1023231 and
Permitted payee is 7109.
Can anybody help me out in this. Points will be awarded.
Thanks and regards,
Shree.

Payment is not going to the permitted payee address

Hi,
I have assigned permitted payee in the vendor master record of vendor. After that i executed payment program and i am finding that payment is going to the headoffice instead of permitted payee and also in the proposal and payment list it is not reflecting permitted payee address. Here it is only showing vendor number and its address.
Can anyboday help me on this or let me know whether i need to maintain any setting anywhere so that i can get permitted payee details in payment list.
Also is permitted payee and alternative payee both are same or is there any difference in between this two.
Regards,
Sree

Hi Jayaram,
I didn't maintained that in the alternative payee in the company code data of the vendor master. i will do that and let you know.
But when i am posting any invoice through FB60, then in the payment data option we are having payee field. So when i am clicking F4 there it is not giving me any details. Is it ok or it will not pick that values.
Reards,
Sree

Netting on Permitted payees in F110

we have situation where the vendor is linked a customer and customer is linked to vendor in customer and customer in vendor and flagged clear with customer in vendor master. Both customers and vendors have different permitted payees. When we run F110 transaction it is netting at permitted payee level but not at vendor level. They still wanted to keep the separate permitted payees and should be able to net at master level. How is this possible.

Hi,
In Vendor Master we have two segments to give alternative payee field.
1. General Data level
2. Company Code level.
Whenever we want to activate alternative payee field, we need click on alternative field push button and need to give vendor codes .Then save it.
Cristiano

Permitted Payee as a remit to address

We want to use Permitted Payee as additional remit to addresses for a vendor. We will defined a vendor A with an address, and extend it to the Company Codes where vendor invoices will be entered. If the vendor has multiple addresses that we could send payments to, we will create additional vendors as permitted payees (Vendor B, C, and D) and they will be attached to vendor A. All vendor invoices will be for Vendor A.
I want to define the permitted payees as a separate account group and only general data will be defined including the address.
My question is using the permitted payee this way, do I have to extend the vendors that will be defined as permitted payees to the Company Codes where the invoices will be created. Vendor A will be extended but I did not want to have to enter any data other than address for the permitted payee vendors.
Thank you
Cindy Collins

if you want to use the alternate payee or permitted payee functionality you have to extend the main vendors and the alternate payees to other entities as well. Generally it is advised to have a separate number range for the main vendor and the permitted or alternate payee. This way you can differentiate beteen your main vendors and alternate payees. it is also advised to block all permitted payee vendors for invoice posting so that only payemnts can be made to them.
Now to answer your question: Yes, you have to extend them to all entities to establish the relationship at master data level. Try using alternate payee so that you can assign multiple payees at master data. For example AT&T USA has nexus in all states but if you want to send the payment separately for each state you need to assign multiple Alternate payee at AT&T main vendor so that you can select one at the time of booking a vendor invoice and select the right payee at docuemnt level. If you are in country USA then all alternate payee payemets gets roll up to the main vendor and you can generate one 1099 form. Hope this helps

Permitted Payee

Hi
I want to create a vendor master with permitted payee..I am tring to find the field in Idoc for permitted payee but there is no field for permitted payee.I dont think we can do using an Idoc extension in this case.Is there any BAPI to create a vendor master with Permitted Payee field..
Can any one please help me out with this requirement..What all the options we have to create a vendor master with permitted payee.We are getting as an inbound vendor master data.
Thanks in Advance
Regards
Sri

You probably mean a Payer, if so, Use Partner func. PY in vendor master creation for PARVW, this should be available in the IDOC segment E1WYT3M

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

Permitted payee in Vendor master

Similar Messages

Maybe you are looking for