Creation of backend vendor master from SUS

Hi
We are on SRM4.0 and ECC5.0 with SUS3.0 and having following scenario.
Suppliers gets registered in registration system in SRM.
Purchaser will do screening and select the supplier.
Requirement
Want to create Vendor master in backend system(ECC5.0) for the above selected supplier from SRM system itself without login to ECC system(that means no manual creation of vendor master in ECC).
Is this scenario possible?
Did anyone come across such requirement?
Please share your experience on how to achive this.
Thanks in advance
Jagdish

Hi,
You can create a custom WF for vednor replication using BUS1006.We have done the same thing at our place.
BR,
Disha.
(Please open a new thread so that points can be rewarded)
Pls reward points for useful answers.

Similar Messages

How to transfer vendor master from MM to SUS?

Hi friends
How to transfer vendor master from MM to SUS
Are the following steps correct
1.create vendor master in MM
2.use tcode BD14 in MM and enter partner system as SUS ( to send vendor master)
3.use BD15 in SRM to accept the master data from MM.
Please let me know if i am wrong
Thanks
Vinny

Hi Vinny,
Please follow below steps for transferring vendor master from MM to SUS.
!) Create a vendor master in MM and assign class type ALV under enviornment-Classification tab.
2)Go to BD14 and enter following fileds
Vendor number
Class
Message type
Target System...
Before doing BD14 hope you have done all the partner profile configuraion as well as model view creation and mapping has been established between MM to XI to SUS.
Before repliating vendor, please note that vendor root org unit has been created in SUS system.
After executing BD14 then check in your mm system WE05 whether idoc has been generated and sent to XI system.
If sent to XI system successfully then please check in SXMB_MONI t-code in XI what is status then finally check in SUS.....
If useful points please...
Thanks
Ravi

Vendor replication from SUS to ECC 6 backend in SRM 7.01

Dear Gurus,
1. Vendor registration in ROS: Vendor's are registered in ROS and stay there as preapproved vendors. They can be replicated to SRM system through OPI calls. How these suppliers are replicated to backend MM system?
2. I get to know that from SRM 7 enhpk 1 facilitates transfer of vendor data from SRM SUS to SAP ERP. A business partner monitor cockpit is available in SUS/ROS. Do we need to upgrade our ECC system to ECC 6.0 enhpk 5 or ECC 6.0 enhpk 4 will do to avail these functionality?
Any input on these will be highly appreciated.
Thanks and regards,
Ranjan

Hi Ranjan,
As of now without Ehp1, vendors are replicated to backend MM systems using a PI scenario "Supply_base_management".
And you are right, from Ehp1 vendor replication will be handled as you mentioned and ECC Ehp4 will support that.
Nikhil

Problem about replicate the vendor master from R/3 to SRM5.0

Hi guys,
I have vendor in R/3 backend system.And the vendor data has been customized.We have added some customize fields to the table LFA1 which is not exist in the standard R3 system.
Now,
I want to replicate all vendor information to SRM5.0 include these customized fields.I have tried t-cd: BBPGETVD&BBPUPDVD.But it only copy the standard fields.
Then I searched the web and found some information said that at SRM side I should use eewb to make extension for vendor in SRM and create instance for the BAdI:BBP_GET_VMDATA_CF and do some coding in the method GET_DATA & UPDATE_DATA.
At the R/3 side I should create a instance for the BAdI:BBP_MAP_VMDATA_CF and do some coding in the method MAP_DATA.
So at the SRM side I used eewb and it generated some function:
ZZSER_BUPA_DTL_ADD
ZZSER_BUPA_DTL_CHANGE
ZZSER_BUPA_DTL_REMOVE
ZZSER_BUPA_GET
And I created a instance for the BAdI:BBP_GET_VMDATA_CF.
At the R/3 side I created a instance for the BAdI:BBP_MAP_VMDATA_CF.
My problem is
1.I don't how to use those functions(generated by eewb) in the method GET_DATA & UPDATE_DATA.
2.I don't know what should I do to the method MAP_DATA(R/3 side)
3.When will these instance be called?It seems that the t-cd BBPGETVD &BBPUPDVD won't find the BAdI's instance(I didn't find any code such as cl_exithandler=>get_instance in the programe BBP_VENDOR_GET_DATA which is for t-cd BBPGETVD&BBPUPDVD)
4.If there is a solution to the problem 1-3 and all has been done, then from where should the import parameter IT_LFA1(in R/3's BAdi BBP_MAP_VMDATA_CF) get its value?
Can anyone who are familiar with these BAdI help me? Thanks in advance.

Hi
Which R/3 and SRM versions are you using ?
Vendor Master Extension in SRM
Vendor Master Extension in SRM
Look for the OSS Note for more details.
Note 675800 - Business partner enhancement SRM on maintenance screen
Please See this thread for creating customer fields in BBPMAININT Transaction.
Re: Adding new fields in VEndor master data in EBP
Do let me know.
Regards
- Atul

Creating / updating vendor master from CREMAS03

Hi All,
I am getting vendor master data from external system and SAP XI will convert this into Idoc of message type CREMAS03. I would like to create/update vendor master in R/3 system from Idoc CREMAS03. Which function module / BAPI will cater to this need.
Thanks and best regards
Kalingeri

Hi
Check in WE57 using the Message type & Idoc type & direction.
IDOC_INPUT_CREDITOR & IDOC_INPUT_CREDITOR_MDM are the the two Func modules being used. You can use any one of them based on your reuirement
Thanks & Regards
Kishore

Update the Vendor master from Employee master - PRAA

Hi
I need to know the process of updating multiple vendors from multiple employee data .i.e.bank,address and pernr.
I was using PRAA transaction but it was not updating ...i think i miss some entries..especially file path...
what are the steps need to be taken care of ...what should be in the file in the file path?
please let me know
Thanks

Thanks Rob
I checked the documentation..and found my error...actually the PRAA is updating vendor with employee data only when the employee number(PERNR) is updated in Vendor master...so i updated the field PERNR in Accounting section of Vendor then i ran the transaction PRAA it worked...it created the session and i processed the session..
My question is ..is the PERNR is mandatory in Vendor master record?
and How iam going to update the multiple vendor records with multilple Employee records? since the vendor for Reference is the single filed?
Please let me know
Thanks
Govi

Vendor master from Customer master

Hi Friends
Is it possible to create a vendor master refering a customer master? If answer is yes, how it can be achieved?

Hi,
you can assign customer master to a vendor and same vendor number in customer master, so that to facilitate FI activity in clearing the open items by adjustment.
Regards,
gln

Creation of new vendor master record

When I assign Account Group, getting following error "Acc. group uses internal no. assignments, leave blank".
if leave blank; asking to enter account group. Can anyone suggest how to select external number assignment while creating a new account group?
Edited by: Kushal Pal on Jun 11, 2011 5:46 PM

Hi Atif,
I have solved the problem myself. we assign external numbers in the customization through SPRO u2013 SAP reference IMG u2013 Finance Accounting u2013 Accounts Receivable and Accounts Payable u2013 Vendor Accounts u2013 Master Data u2013 Preparation for Creating Vendor Master Data u2013 Create Number Ranges for Vendor Accounts ans selecting Ext check box as first step.
In the second step, by selecting "Assign Number Ranges to Vendor Account Groups" in the same customization.
Your suggestion was helpful but I had already worked out. XKN1 is the correct Trans. to look into assigned ranges.
Thanks.
Edited by: Kushal Pal on Jun 13, 2011 4:55 AM

Error while transferring Vendor master from R/3 to SRM

Hi,
I have done the following.
R/3 .
1. Vendor creation in Xk03 for the organisation
SRM.
1.Created a vendor group in PPOCV_BBP
Entered the following in BBPGETVD.
1. Logical system
2.Vendor
3.Purchase organisation.
4. tice mark in address comparion,
5. Organisation ID: 50000407 for the Vendor group created in PPOCV_BBP.
6. only Transfer R/3 Number
7. Executed ..
Error is I am getting the following error. while using BBPGETVD .
"None of the purchasing organisation in org Structure"
Please give your solution
Regards
G.Ganesh Kumar

Hello Ganesh,
I did not talk about tab Attributs.
In PPOSA_BBP, one of your Organizational Unit must have in its tab Functions value 'Purch. Organization' set with correspondence in R/3 values (number and logical system).
Regards.
Laurent.

Vendor master from one plant to another plant

Dear Gurus
i Have vendors in on plant 100 and now i want to transfer from 100 to 200 plant those vendors.. how can i do. xk99 is okay...
Thanks
ramki

Ram ki
see when you create a Vendor it will always be at company code level or at Purchasing Org level , you can never create a vendor at plant level so since these two have higher hierrarchy and plant comes under it , once you extend to this it will automatically extend for your plant.
The only place as per my knowledge where you use Vendor = Plant assignment is at Stock transport order for system to undertsnd that is maintained in Additional data tab.
so as i was saying you can extend this at company code or at Purch Org level
Hope this is clear
Cheers

Vendor Master can not replicate from SAP R3 to SAP SRM system.

Hi All,
We face one issue when we use bbpgetvd program to transfer Vendor master from SAP R3 to SAP SRM, after I check Analysis Application log, found the following issue:
Error: No Bank Master Data Maintained No Bank Data Transferred
Error: Name/Address for Vendor Already Exists Vendor: 0015118743 Address Number 0000054208
Error: Warning: Complete Business Partner: Vendor: 0015118743 Backend: APP002TS No Transfer of Vendor Data
But I check BP in SRM and can not find vendor 0015118743 information, so could you give me any tips or suggestions to fix this issue. Is there any table in SRM system to keep Vendor Master like SAP R3?
Thanks for your kind suggestions or help in advnance!

Hello Gavin,
>
Gavin Feng wrote:
> (...)
> 1. How to use BP to find business partner by address num 0000054208, I did not find this search condition.
> (...)
You cannot.
Business Partner are stored in BUT000 table. I don't remember if its address number is also stored in this table.
If yes, link is done directly between both.
If not, this is the person number which is stored in BUT000. So, use your address number to get its corresponding person number using ADCP table. Then, with this person number, check in BUT000 what is its corresponding Business Partner.
Finally, with its corresponding GUID, check in VENMAP table the vendor number.
>
Gavin Feng wrote:
> (...)
> 2. I used VENMAP and ADRC to check vendor 0015118743 and address num 0000054208, but there is no record in both table, so why the SRM system generate information that is "Name/Address for Vendor Already Exists".
> (...)
See my answer above concerning ADCP table.
Regards.
Laurent.

XML message failing in the SUS side for vendor replication from ERP

Dear Experts,
We have configured MM-SUS scenarios in our environment of SRM 7.01/ECC 6 ehp 5.
We are trying to replicate the Vendor master from ECC to SUS using PI ( idoc message ZCREMAS_SUS_MM)).
The message is successully processed in the PI. It is failing in the SUS side.
The exception is as below:
An error occurred when deserializing in the simple transformation program /1SAI/SASF5486DA19E3520591A1B (Length of "123 JALAN TIMUR" exceeds maximum length "10", specified with tt:maxLength Kernel ErrorId: ST_CONSTRAINT_MAXLENGTH) XML Bytepos.: 607 XML Path: ns0:SupplierPortalTradingPartner(1)TradingPartnerOrganization(2)Address(8)HouseNumber(6) An error occurred when deserializing in the simple transformation program /1SAI/SASF5486DA19E3520591A1B Length of "123 JALAN TIMUR" exceeds maximum length "10", specified with tt:maxLength</SAP:Stack>
Where I can change the settings to allow the maximum length of 10?
Any input will be highly appreciated.
Thanks and regards,
Ranjan

Hi,
Note 1510484 - SUS: Order longtext in message area displayed incorrectly
Note 1559121 - SUS: Long texts are getting broken in PCO (POR)document
Given notes are not exactly related to the problem. Let me know if notes could work for the current issue.
Regards,

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

Data upload Vendor Master Chinese character from Excel does not upload

Hi Gurus,
We are trying to upload Vendor Master from Excel sheet.
The Chinese characters in excel sheet is not getting uploaded.
After upload, we see in SAP as ????? for these Chinese character.
Could any one inform what setting I may need to change?
Thanks and Best Regards,
Mohan

Hi Bala,
Goto he Initial screen of SAP and click the ALT+F12 costomizating of local setup.the choose the options-->choose the I18N Tab in that POP up and check the Activate the multi byte support.
press Apply and OK.
close the SAP Log on and Re-loag on.if u r not closing the Logon screen the changes wiil not effect.
or
click on the log on SAP and choose the server name -->right click ->Properties>chose the log on language as chanies .-->Apply and Logon.
Now u can eassily Upload to the Excel in checnies language.
Thanks & REgards,
Nelson.

Updating Vendor Master Address from HR Master using PRAA

Hi All,
When PRAA updates the Address into the Vendor Master from Infotype 6 subtype 1, does it consider the Second Street address as well?
Some employees have 2nd address line populated in their IT0006 record and this isnt showing in their vendor account.
Regards,
Anjali.

Hi Anjali,
No, the sttandard program does not update any subtypes of infotype 0006 other than subtype 0001. However, you can adapt this to suit your needs: an empty routine is supplied in the includes RPRAPAEX and RPRAPAEX_001 which you can adapt to your requirements You must implement the user exit routine 'set_address_by_user'. An experienced ABAP programmer can do this.
Regards,
Rodrigo

Creation of backend vendor master from SUS

Similar Messages

Maybe you are looking for