Legacy Consumer Number

Hi Everyone,
A very basic CRM question. How do you often maintain the legacy consumer number of your BPs when doing data migration? What is the best practice here?
Thanks,
Dave

Hi Dave,
Completing information provided in the last post, the table that you have this information is BUT0ID. When you do the initial load this table is automatically filled.
Best regards,
Caíque Escaler

Similar Messages

Legacy Serial Number MIA - SOL?

I've been a PageMaker user since 1.0a (uh, that'd be 1987). Subsequent versions of PM came with a "lite" version of PhotoShop. PMx had PS2.0 LE. PM6 had PS 3.04 LE. PM6.5 had PS 5.0 LE. They were all I needed since I also had Corel Paint and Draw through the years.
I'm semi-retired now and mentally locked in to PageMaker after all these years. So, no, I don't need InDesign. What I do need is to replace my existing PS 5.0 LE because every time it fires up, it shuts down my sound card. And then I miss all the little jingles that keep my head from falling over on my desk asleep.
So, my obvious solution is to go back to PS3.04 LE on my PM6 disk. But of all the thirty or so serial numbers for all my software, that's the one that's missing. The box or sleeve after 17 years, yeah, forget that.
Any ideas on how to hack a legacy serial number?
I've got the s/numbers from PS 5.0 and PS 2.0 and my PM6, 6.5, and 7. And all my manuals and original disks. But after all these years, and almost a decade and a half of being out of warranty, I no longer have any receipts proving ownership. The only thing I have is a statement transferring ownership of the software to me by the chairman of the company I retired from. (They weren't re-hiring an ad man. Guess I broke the mold!) I was the only user through all the years and it was worthless to them after I was gone. Plus, they needed to make me happy.
Going through Adobe channels is going to get me nowhere because the software is too old and I can't produce a BestBuy receipt anyhow. I'm sure the programmers built in a secret install password ("CorelBites" or maybe "BytesDoItOneAtATime" or something).
This probably has no answer, but I thought I'd try.
If I were writing software, I'd certainly have built in a supersecret universal serial number.
Thanks.

Oh, not forward at all. Like my thinking, probably!!
Short answer:
Why spend the 100 bucks I don't need to? It's not a lot, but maybe a 100 means more to me than you.
Long answer:
1. I enjoy the challenge of making old software continue to be productive.
2. I don't use 20% of the features of my decade-old versions of PS, Word, Excel, PM, whatever. Why buy newer versions with even more great features I don't need?
3. I was, and am, a creative guy. There's always 2-3 ways to do things on computers. I don't need a super new single macro key set to do all kinds of things thus easing my (semi-retirement) workload.
4. I've already got the software and I've still got the hundred bucks.
5. The "cascade effect." Every time you do an upgrade that you don't absolutely have to, you open yourself up to a whole plethora of potential incompatibilities, archive file conversions, forced updates, OS updates, driver mis-matches.
6. I've got CorelPaint, a professional version and use that for some things, particularly anything CMYK. But for most things, a lite edition of PS is quicker for me.
I've been computing for thirty years, and on PCs for 25. I will upgrade given a very strong case for doing so. But last time I spent over a hundred bucks on an upgrade, it was for Office 2007 a couple of years ago. Waste of money. Only thing I got out of it was peer version compatibility with a client. After two weeks with the new interface, I degraded back to 97. I already had ten years invested in being able to work fast and efficiently in 97. Didn't need to go learnin' no new geography to continue productivity.
I do graphic design and copywriting and have even created Windows fonts that people are still licensing. I already have everything I need to continue doing that. I don't need to send files to a smart phone and archive in the cloud and check in with Facebook in the shower.
A lot of this new stuff out there is to just keep getting people to send in their hundred buckses!
Re-reading myself here, I think I may paraphrase as, "Me thinks me doth protest too much!"
= Tom

LEGACY DOCUMENT NUMBER FIELD

Hi:
Does anyone know of any existing field at GL line item or document header level specifically for legacy document number? Please do not suggest assignment, text or reference field. I'm looking for a field specifically named "Legacy Document" or similar.
Thanks and Regards
Hisham

Hi
I dont think SAP has provided any such field specifically for Legacy Document.
You have to go with the options that you have mentioned or there are some other extra fileds like Reference specification 1/2 or Reference specification 3.
Good Luck
Hari

Consumer number for a JMS queue continues to grow

          I am using WLS 7.0 SP2. I have a JMS Queue and number of consumers continues to
          grow.
          Is there any way to stop it from growing? If not, should I be concerned about
          the memory usage by those consumers?
          Thanks.
          Rick


          Tom,
          You are right on JMS resources. We found that developer didn't close JMS session
          and conneciton which caused the memory leak. Now it has being running more than
          10 hours without crashing.
          Thanks.
          Rick
          Tom Barnes <[email protected]> wrote:
          >
          >Rick Chang wrote:
          >> I am using WLS 7.0 SP2. I have a JMS Queue and number of consumers
          >continues to
          >> grow.
          >>
          >> Is there any way to stop it from growing?
          >
          >No.
          >
          >> If not, should I be concerned about
          >> the memory usage by those consumers?
          >
          >Before jumping to conclusions though, make sure
          >that you are looking at the right statistic, there
          >are three for consumer count:
          > current -- active consumer count
          > high -- highest active consumer count
          > total -- total consumers ever created
          > (ever increasing by definition)
          >
          >If you are looking at "current"
          >the statistics point to a likely memory/resource leak.
          >Perhaps some part of your application is failing to close
          >its JMS resources when it is finished with them.
          >
          >>
          >> Thanks.
          >>
          >> Rick
          >

Finding Accounts/Customers/Vendors based on Legacy Account Number

Hi Guru's,
Is there an easy way to get the SAP Account number based on account number provided from the legacy system?
Appreciate your help.
Regards,
Ved

Hello Vedratna,
It is much easier to find the SAP account number based on account number provided by leagacy data but for this in the background you need to know the data structuring rule which was followed during the data transfer from legacy to SAP system.
The data to be transferred to the SAP system is prepared in a sequential file. A file may only contain data that can be processed with the same transfer program. This means that a file may not contain data for different master records, for example, customers and vendors, since there are separate transfer programs for these records. The program creates batch input sessions from this file.
For every file, there are three types of structures:
Session header record
This structure contains data that applies to a session that is to be created. Here you enter information such as a batch input session name, the client key, and a user name. By entering a lock date, you can set a latest date for the session to be processed by.
Header data
These structures contain data that applies to one transaction only. Here you specify the data that you must enter on the initial screen when manually selecting the transaction. Among other items, this includes the transaction code and key fields, for example, Account group, Company code key, Account number, Purchasing organization, or Division.
Subsequent data
These structures contain data from the master records. This includes, for example, the address data for your customers/vendors, the company code data, or the sales area data.
The different structures are indicated by record types. For subsequent data, you have to specify the structure name in addition to the record type.
Hope I had been able to help you. Please assign points.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The other way could be to take a dump of customer master(general data) KNA1 in one excel file and also take the dump of legacy data. then use the Vlook up in excel. But for this to happen there must be some link between the two sets of the data like in search term u could have used the legacy number of customers or their leagcy name or any link.
Hope I had been able to help you. Please assign points.
Rgds
Manish

Legacy Serial Number for Upgrade

I am reinstalling Acrobat XI, which was purchased as an upgrade from a previous Adobe product. The reinstall is asking for the Serial Number from the previous product; but I no longer have that Serial Number. What do I do now?

This is the forum for the free Reader. You'll probably want to continue in the Acrobat forum.
That being said, did you register the product or do you have receipts? If not to both answers, you may be out of luck.

Legacy number in the material master

Dear SAP Guru,
Good day.
We are currently in production support today and we want to understand how a legacy number differs from a material number. As we can see in the material master (Classification View) there is an indicated legacy number there with a corresponding value. Could you further elaborate on how and what is the usage of a legacy number?
Thanks in advance for your help.
Kind regards,
JMT

Jasmin,
Basically some clients would be interested to track the SAP material number with referance to the Legacy material number, this data would be uploaded during the Cut-over and data conversion to SAP.
I would suggest you look at the Functional/Tehnical specification document for the conversion program which was used for uploading the material master data into SAP, that would give you the business reason and the field mapping details.
Regards,
Prasobh

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

PO Creation with external PO number

Hi All,
We have SRM and some other legacy system. We will receive the PO information from the legacy system with the Legacy PO number. Now we have to create a PO with external number only.
So for PO creation we are using the BAPI BAPI_POEC_CREATE. this is working fine if you dont pass any external PO number.
But If you pass external PO number I am facing some problem. BAPI_POEC_CREATE is giving the informaiton that PO with XXXXXXX number is created, but when we call BAPI_TRANSACTION_COMMIT it is throing some error like.
Buffer table not up to date
Message no. BBP_PD001
Diagnosis
In LOOP OBJ_RELATIONS_UPDATE (function group SAPLBBP_PDH_OR) an inconsistent status was discovered.
Procedure
Start the transaction again. If the error occurs again, create an OSS message.
To analyze the error, you can set a breakpoint in the function module 'BBP_PD_ABORT' and look at the call-up hierarchy in debugging mode.
Is this the number range problem? please tell me what is missing.
Thanks & Regards,
Raghu

Raghavender,
I think that maybe the external number is not the problem.
Sometimes the explicit <b>COMMIT</b> causes this error cuz some processes or BADI's are accessing the table at memory level, so if you use this explicit bapi_transaction_commit maybe it will raise that error...
Have your tried to remove that function call?
Please acknowledge if it worked...
Regards,
Gerardo.

Asset Report with old Asset Number in the Second description text field

I have a requirement for a report in the Asset accounting.
User wants a report where in he can see the asset details with the legacy asset number which is entered in the second description field in the Asset Master. I executed the available reports and could not find one like that. Please help me out.

You have the option to ad this field to the reporting stucture.
Wy you have ased this field and not the fields in the tab origin for old asset number?
For extra fields in the asset see the Wiki
http://wiki.sdn.sap.com/wiki/display/ERPFI/IncludeownfieldsinFI-AAstandardALV
for all the wiki's from asset accounting go to the link:
http://wiki.sdn.sap.com/wiki/display/ERPFI/Asset+Accounting

Document number in FI module

We are implementating only FI module ( dont have any MM, SD, PP no other module) and the document range for all documents type has been defined external,
I have to upload opening balances, the problem i am facing is the external Document no (as per the legacy) Which will be entered is 20 character, the external number range is allowed only upto 10 characters,
How do I go for uploading the balances,

We had the same requirement when we implemented SAP. The first thing you have to do is realize that a ten character document number is something you cannot get around.
Why don't you let SAP generate the document number automatically and put the legacy document number in a different field?
Rob

Reprocessing a legacy flat file....Avoid multiple postings

Hello everyone,
I am processing a file from application server and posting material documents in SAP against a unique number in legacy. This is a backgroung job. The same program can be executed in foreground also.
My problem is with reprocessing the same input file or accidental processing of the same file again and again.
Option 1:
While posting the material document, i pass the legacy invoice number in MKPF-BKTXT using the same BAPI. For each processing i check the BKTXT before posting against a invoice
Option 2:
Maintain separate table for posted invoices
Option 3:
Maintain log file in application server against input file and check that before posting.
For me option 1 seems to be the best method as for the other 2 options there is a chance that document is posted and while writing the log there is some termination unless i can combine and write the log in the same logical unit of work (LUW).
Please share you opinion...
Is there any better way to handle this ?
Thanks

R V,
We use a 4th option.
We created a database with the following fields;
CHAR     15     Interface File Name, case sensitive
DATS     8     Date Assigned by Source System
TIMS     6     Time Assigned by Source System
DATS     8     Date added to this table
TIMS     60     Time added to this table
All interface files contain a header record with these 3 fields:
CHAR     15     Interface File Name, case sensitive
DATS     8     Date Assigned by Source System
TIMS     6     Time Assigned by Source System
We created a program that compares the input file header record name, date, and time, with the database table values. Duplicates send an email and stop the next program in the stream (program that creates the SAP transactions). If the input file is not a duplicate, a record is inserted into the database table and the next program is the job stream runs.
Bruce

PO conversion during cutover (retaining legacy no.)

Hello !
We are planning on manually entering all open POs into SAP at the time of cutover.
One idea that has been floated is to create a special number range that matches the legacy PO numbers... and ensure that the legacy PO number is retained in SAP for POs that are brought over. This would help with communication/receiving etc.
Does anyone see any problems we could encounter with this approach? Is this a common PO cutover strategy?
It seems like a good idea to us, but I am not sure if there is anything we need to be concerned about.
Any insights appreciated.
Thanks,
Anisha.

Hi,
I agree with the approach, i have also use similar one in a project,,
create a new doc type for legacy POs (ensuring that legacy PO no. range doesn't conflicts with normal POs), it works well as it is easy to by pass PO release strategy also..
one extra precaution is to unassign the number range to this doc type once all cutover activity is signed off to avoid accedental usage of this doc type (becuase one can use this to avoid release strategy)
reg
dheeraj

Customers License Number... Tax Registration Num (TAX_REFERENCE)

Hi there
We have legacy License number which is equal to Customer number in legacy system, we used ORIG_SYSTEM_REFERENCE field as a license number in Oracle Receivable Customer form.
What happened this field is not updateable and the some time user forget to type the number and than system generates the number automatically and we want to modify this field and the field is not updateable.
CAN I use Tax Registration Num as a License Number? What is the Risk of using this field as a license number or Is there any other field I can use?
Thanks in Advance.
ASIM

Hi!
You're welcome! Yes, I meant DFF. I agree with you, if you use a dff, it will be quite difficult searching customers. You will have to open customer form, press F11, go to the flexfield and inform the number. Much harder than just using standard customer search form.
If are not in one of the countries mentioned in AR manual, neither intend to have an operating unit based in one of that countries, I think you can use Tax Registration Num or Taxpayer Id, if you don’t have another use for them. Validation on Taxpayer Id is currently restricted to Italy, Spain and Portugal.
Alternate Name field could also be used, but searching using this field is also harder than just using standard customer search form. And, if you are not using it, you have Account Name.
I searched in AR users guide for references on "Reference" field, and according to the manual, it cannot be updated after customer is saved. I don't know if there is an API that allows updating this field.
Regards,
Ketter Ohnes

Previous Account Number customer master data

FI Gurus,
I want to be able to use field KNB1-ALTKN under company code data in master data. I want to use this field to store the old legacy customer number, but then I want ot be able to search when Ina doing customer search in FBL5N. Is there a way to do that?
Thank You for your help.

Hi Frank,
Try this way.
Go to SE36-> DDF->Extras-> selection views.
origin of view -> SAP-> Change
you can see Tables/Nodes on right hand side -> click page down.
place cursor on KNB1 and click choose.
In Table fields/Node fields
click page down until you see ALTKN field.
assign functional group 04 to the field and save.
Note: Under origin of view ->SAP, this is provided by SAP. Make sure before you do change.
Best Regards,
Mohan.

Legacy Consumer Number

Similar Messages

Maybe you are looking for