Vendor Master replication from EBP and MM to SUS
Hi !
We would be replicating Vendors from R/3 as well as from EBP to SUS. I believe that there is certain configuration to check duplication of Vendors and also to assign a single business partner ID even if a Vendor is replicated both from EBP as well as from MM. Can anyone thro some light on this & the procedure...
Thanks
Hi,
For the Vedor Maste replication from EBP and MM to SUS,
U need to maintain the proper RFC conncection between R/3, EBP SUS and XI as a middleware.
U can transfer the Vendor by using the T.Code - BBPGETVD.
U can transfer vendor to SUS using
transaction BD14 with message type Z_CREMAS_SUSMM as
SAP suggested.
Your error due to incorrect mapping in Integration
Directory of XI.Kindly check the Interface
determination for message type Z_CREMAS_SUSMM.
Please award the points for the help.
BR,
Vijay Mittal
Similar Messages
-
Vendor Master Replication from MM to SUS
Does any one have experience on Vendor Master Replication from R/3-MM to SUS (scenario without EBP).
Is this replication made via XI?
Which are the configuration steps for this scenario?
Thanks
antonioHi antonio,
I hope now you r now transfering vendor to SUS using
transaction BD14 with message type Z_CREMAS_SUSMM as
SAP suggested.
Your error due to incorrect mapping in Integration
Directory of XI.Kindly check the Interface
determination for message type Z_CREMAS_SUSMM.
If possible send more details for error .Is this at
SUS End ?
Regards
Sachin S M -
Vendor Master REplication from CRM
Hi friends,
I am maintaining Employees from CRM to R/3 and these EMployees exists as Vendors in ECC (Purchasing). So whenever I replicate a document it is giving me error with these Partner functions CSR, Field Sales
The possible reason could be I have no option to map the Vendor Accountgroups to CRM Classification through PIDE(ECC)
Question is
How do you I maintain vedor master mapping to CRM partner functions,
I have already mapped the CRM Partner functions to R/3 Account groups, but i am assuming that I need to maintain the classification in PIDE to replicate.
So please help any suggestions will be greatly rewarded
thanks
RajHi Subramaniyan,
Thanks for the Reply. But this is supposed to happen real time.
Here is the detailed explanation again. I am maintaining the Partners CSR, Field Sales (Internal Employees) in Vendor master and they are coming into CRM as Employees with Mapping Data Transfer. When the same replicates to ECC through a Quote or Order... The problem is these Employees CSR, Field Sales from CRM to ECC are not linked to any of the ECC Classifcations becasue we dont have any option to do so.
Now when i replicate becasue the classifcation is not mentioned, it is popping back to me and giving me as error on just these 2 Employee functions.
To resolve this issue, I have to maintain some kind of mapping structure using a classification Consumer, Competitor, Customer, or Prospect. In a different way, I have to assign the vendor account group to a classification. which is not possible through PIDE, coz PIDE only allows you to map customers not vendors.
My question is how do i handle the incoming vendor partners from CRM into R/3.
thanks a lot -
Vendor Master Replication from 2 Backend System
Hi Experts,
I am facing a problem in replicating the vendor masters from two Different Logical ECC systems.
The vendor master at 1st Backend system
Vendor Master: 0011000196
Company Code: C001
Pur.Organization: P001
The vendor Master at 2nd Backend system
Vendor Master: 0011000196
Company Code: 1000
Pur.Organization: 1000
In BBPGETVD, the vendor from 1st backend system is replicated successfully and available in VENMAP table. Again, I entered the same vendor code and change the 2nd Backend destination in BBPGETVD and clicked on start transfer , In SLG1 i could find the error as below
"Error: The Vendor Number Exists as a Partner Number Vendor: 0011000196”.
In VENMAP table for the above vendor there is only one entry for the 1st logical system alone.
Kindly suggest.
Thanks& Regards,
Ramprakash NIf it is the same vendor - it must have the same address in both backends.
After that you should be able to start BBPGETVD with following checkbox activated.
Then VENMAP should be extended automatically.
Regards
Konstantin -
*Journal Entries while uploading the vendor master data from legacy system*
hi SAP Folks,
can any one of you tell me the journal entries while uploading the vendor master data from legacy system to SAP system.
Eg: legacy system is having 10000 vendors list, 1 reconciliation account and $ 1000000. while uploading all these data from legacy system to SAP what are the journal entries we get.
thanks in advance.
Edited by: ravindranath manikonda on Nov 24, 2008 1:12 PMHi
you will be having only one entry logically
i.e. Opening Bal. clrng A/c Dr.
To Vendor A/c Cr.
regards -
Error while replicating vendor master data from R3 to SRM
Hi,
I am trying to replicate Vendor master data from the R3 system to SRM system(7.0) for the first time and am facing the following error :
Organizational unit 50000004 does not exist; check entries
Message no. BBP_BUPA034
I have gone through the other posts with similar issues but haven't been able to find a solution.
Any ideas?
Thank you.hi sahlini
did you create a vendor organisation structure via PPOCV_BBP ? SINCE YOU REFER THIS NUMBER 50000004 WHAT IS THIS?
BR
\MUTHU -
Upload vendor master data from legacy system to internal table tcode xk01
through batch input program how to upload vendor master data from legacy system to internal table and then to SAP R/3 database(transaction XK01) by using recording method.
By learning the basics of BDC recording and the use of GUI_UPLOAD
-
Modify vendor number when replicating vendor master data from ECC to SRM
Hi,
Is there a way to modify vendor number(manually input vendor number e.g. from a file) when replicating vendor master data from ECC to SRM using the vendor master data user exit (SAPMF02K)?
Does anyone have documentation on the user exit, how do I use it??
Thanks and Regards'
DavidHi David,
Please go through the link below:
[Enhancement SAPMF02K Vendor Master Data - question about LIFNR;
Regards
Anirban -
Function Module to send Vendor Master Data from SRM to ECC
Hi Guys
I heard there is a function module in SRM which can send Vendor Master Data from SRM to ECC please confirm for me if there is such a function Module and what is it called. ThanksHi,
Vendor Master data is replicated to SRM from ECC. Standard Transactions (BBPGETVD,..) will be used to replicate the data from ECC.
Vendor Master will exists in ECC, so there is no point in sending the same back from SRM to ECC. If the requirement is the other way around, we can use the transaction BBPGETVD in SRM system.
Hope this helps.
Regards,
Hemanth -
Error importing vendor master data from ERP
Hi experts,
currently we are trying to import vendor master data from ERP to SAP Sourcing 9.
We exported the data in an XML file by using the transaction BBP_ES_MAST_DOWNLOAD.
We already imported all the dependencies like vendor account group, purchase org, regions etc. successfully.
However, every time we are trying to import the vendor data we receive the same result:
Data Import:
Trace.txt:
Do you have any hints why this happens?
Thanks in advance and best regards,
JohannesHello Johannes,
This looks to come from a custom script in your system.
Go to Setup > Script Definition and check all scripts defined on class "Supplier" (starting with those on context: Import Lifecycle Event).
Search for a script that starts with "throw doc.createApplicationException(test..."
Regards,
Bogdan -
Creating Vendor Master Records from HR Master Records
Dear Experts,
I have been using t-code PRAA to create vendor master records from HR master records. The client would like to have one vendor number for a group of employees (in this case external contractors all working for the same company). The system won't allow me to link several PERNR to one LIFNR (i.e. error message).
Is it, however, possible to do this?
Thank you.
Edited by: Philip on Jan 14, 2011 9:58 PMHi ,
PRAA has one to one relation ship , means it created 1 vendor for 1 employee .
If you are using PERNR then you cant use one vendor to may PERNR .
Either create them as individual vendor or else have a manual control system in place where in you will have to create a dummy PERNR and then allocate all the cost to this invidual vendor , if you are paying the check to only 1 contractor for say 100 contract employees you can use this .
else it is a better mechanism and control to have 1 is to 1 in case of employee to vedor .
Regards ,
Dewaang T. -
Replication of vendor master ac from employee in HR
Hi Experts,
My client looking to create vendor master account in accounts payable when hire the employee in HR, or if employee bank details infotype change should also replicate in vendor master account, Could any one let me know is standard practice in SAP or need to do development. Let me knowthe path to customize.
Note: client having HR and FI in two different clients.
Surya.Hi,
There is dedicated SAP report for that.
You should start transaction PRAA and investigate different options and figure out what is needed for you.
Cheers! -
Hi,
We are implementing SRM 5.0 connecting to R/3 backend. Our client will be using Master Data Management (MDM) component to manage the vendor master data. My questions are:
1. If we are using MDM for vendor master management, do we still need to perform the replication of R/3 vendors to SRM?
2. Assuming the answer to question '1' is yes, how so we replicate the vendor master data to MDM? should the replication be done from R/3 to MDM or from SRM to MDM?
3. How can the changes to the vendor master data in MDM be reflected in SRM and R/3 backend?
Thanks.
Regards,
Irene W.Hello Irene,
AFAIK, there is no process between MDM and SRM for vendors.
MDM could extract SRM vendors (as business partners) and R/3 vendors and match them for Consolidation scenario, but for Distribution scenario, MDM uses IDOCs to create/change vendors in R/3.
So:
1- Yes: the flow will be MDM --> R/3 --> SRM
2- Do you plan some changes on SRM vendors ?
-- if no, let R/3 --> MDM flow. R/3 remains the master.
-- if yes, parts of SRM vendor updates can be transfered to R/3, so the R/3 --> MDM flow applies. SRM --> MDM flow might not be supported (it was not in MDM 2.0 and MDM 3.0).
3- Via MDM -(IDOC)-> R/3 -(BBP_VENDOR_SYNC)-> SRM. This is the MDM scenario where you maintain vendors centrally.
Rgds
Christophe
PS: please reward points for helpfull answers -
Vendor Master Replication-getting error message
Dear SRM Gurus,
Currently I am using SRM 5.0 and ECC 6.0. I am trying to replicate the vendors from ECC system using BBPGETVD for initial download.
I am getting the error message "*_All backend descriptions are already assinged in the system".*_
I checked in SLG1 tcode even i couldn't find any log entry.
I created root orgnisational unit using ppocv_bbp and same object id i am using for replication.
I am not sure but i believe i have maintained all the necssary settings.
Can you please give me the solution.
Thanks for your help
Ravi NagandlaHi Muthu,
I maintained below settings for number ranges in both the systems.
In ECC:
Spro->Logistics general->Busines partner->vendors->define number range for vendor master records
No From number To number Current Ext
01 0001000001 0001999999 1004422
In SRM:
SPRO-> supplier relationship management->srm server->cross application components->number ranges- Define Number Ranges for Vendor List
No From number To number Current Ext
01 0001000001 0001999999 1004422
Should I check u2018EXTu201D checkbox in any of the system.
Please check above settings and please guide me.
Thanks
Ravi -
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
Maybe you are looking for
-
Can I clone a brand new Lion HD, and later use it as upgrade path?
Six weeks ago, I ordered a refurb 2011 iMac from the Apple online store. This was obviously well after the introduction of Lion, but I was hoping the refurb might still come with Snow Leopard, which I still need for several reasons. I confirmed with
-
DVD set to wrong region and crashes when I try to change it
I'm in Region 2. I only watch Region 2 DVDs, I only want to watch Region 2 DVDs. At Christmas, my DVD player was working fine with Region 2 DVDs. Today I tried to load another Region 2 DVD (for the first time since I updated the OS for the App Store,
-
Sun One App Server 8.1,Sun One Message Q3.6,administered objects in LDAP
Hi, Has anyone tried hosting an MDB on Sun One App Server 8.1 listening to a queue on Sun One Message Queue 3.6 through administered objects in directory server...? It looks quite straight forward but somehow it doesn't seems to work. Any idea if Sun
-
Alternating row colors inside netui-data:repeater?
Is there an easy way to make the row colors alternate inside the netui-data:repeater? I am looking for somthing similar to what happens with the netui-data:grid tag. A code sample maybe? Thanks, John
-
I'm a new admin running Server 2008R2 on Cisco hardware. A user created a subfolder and wanted special permissions for that folder. I accessed the Server Desktop, went to "computer" to look for that folder and noticed that I can't locate it. There ar