Legacy Data transfer Initial step?

Hi guys,
What is the first step that we need to do before transferring the assets from legacy data to SAP?
Is it setting up of the Chart of accounts? How do we do this.
what are the steps.
thanks
srik.

You have first to set up asset accounting. There is only a link with Chart of accounts when you set-up the g/l accounts for the asset postings.
For the conversion follow the steps in the IMG TC SPRO
Financial Accounting / Asset Accounting / Asset Data Transfer.
In the most cases an LSMW is create to do the asset upload with TC AS91. Manual the balance values are uploaded with TC OASV.
When you seach on this forum with AS91 and OASV you will found all information for different situation how to do the asset upload

Similar Messages

Asset Legacy data transfer reconciliation with GL

We have recently merged a deactivated company code with our operating company and transferred all Finance processes, open items,master data etc.
We transferred assets using Legacy Data Transfer AB91 (we did not use intercompany asset transfer ABT1N).
We then transferred the Trial Balance.
The asset balances reconcile against the GL accounts for the transferred assets when executing S_ALR_87011964 and FS10N.
However there is a difference in ABST2 which is the same difference as the migrated assets.
I would expect there to be no difference between FI and AA for legacy data transfer
I have also run ABST for all affected GL accounts and there is no difference when executing this report.
Note that the company code migration occurred in January 2008, there is no effect on 2007 year end data.

Hi
You have to take over the GL balance using OASV t.code
regards
Sibichan

Legacy data transfer for new depreciation area for already existing assets

Hi all,
I am doing legacy data transfer for New deprecaition area for already existing assets through AS92.
I like to give Ordinay depreciation posted amount for the current FY for these assets in AS92, but i find this field is not editable inAS92.
Please guide me to upload the Posted deprecaiton amount (for current FY) for these assets. I have assets both which are acquired in Last FY year and also this FY year.
Regards,
Srinivas

HI,
I have to migrate Posted dpereciation for new depreciation for nearly 3000 assets, In transaction 147, where i need give Acquituion value aslo, please note these are not new assets, these are prior year assets wiht opeing balances. If we use 147 system will take it is current acquition.
Please note my transter date is 28.02.2010, I have already run AFAB for this company cdoe Feb 2010 for other depreciation areas.
Now i am trying to update Opening APC Cost and Opening Accumulated deprecation for these assets and also posted depreciation for this FY.
Where in AS92, i am able to update Opeing APC Cost and Opeing Acc Dep succsfully for new dep area for already existingassets, bu Posted deprecation field is not editable.
Please guide me how to update posted deprecation for new deprecaition area in AS92 or some other way for already existing assets.
REgards,
Srinivas

Net Book Value calculation Issue Manual Legacy Data Transfer

Dear All
I want to Upload balance of old fixed Asset in newly configure System that are managed manually in previous year, I want to Post Their previous Current Written Down Value and Current Accumulated Depreciation when i go via IMG Create Legacy Data Transfer and enter,
Take Over Value of assets I entered for example
Accusation Value 100,000
Accumulated ordinary depreciation (Old depreciation in Previous Years) RS.10,000
Net book Value Rs.110,000
and system Calculate the Depreciation on 110,000 as WDV 10% that is 11,000
My requirement is that it will Calculate it as 100000-10000
Depreciation should be calculated at a 90000 @ 10% WDV that is 9000
Please suggest me, how i can do.
or other path or T.code where i can do.
i am new please explain in detail.
Regard
Khalid mahmood

Dear Atif and AP
Issue is not with Depreciation key it is working well according to my requirement but the issue is that base value that the system use is wrong.
i want that the system calculate depreciation at Cumulative Acquisition value (Purchase /capitalize/ cost price) less Accumulated Depreciation
is equals to Written Down Value.
I want that system use WDV as a base in each year after deducting year depreciation or (Acqusition cost - Accumulated depreciation).
I post a new asset and assign depreciation key it working well as required.
But i going to post Old asset for example Rs.100000 in year 2006. its Accumulated depreciation is suppose Rs.30000 in Year end 2011.
i want to post that asset in year 2012 as 100000-30000 and WDV IS Rs.70000 ;
i want that it will use 70000 as a base in the coming year to calculate depreciation.
My response is 100000+30000 and use 130000 as base to calculate the ordinary depreciation for the next year.
Now Please read the first thread again and guide me according to my scenario.
or tell me how i post the old asset value and their depreciation.
Regard
Khalid Mahmood

Legacy data transfer - open items customer/vendor

Hi together,
We want to transfer legacy data to SAP. With our open item postings (customer/vendor) we want to use the relevant tax code, but we don´t want to actually post the tax amount. (The tax will be transferred in sum)
How does that work?
Thanks for any help.

Hi Murali,
I´ve checked that by entering a manual posing via fb01.
The problem is that within the posting I can´t set the tax code for the transfer account (GL-account) since field
MWSKZ must be empty. I´ve already deactivated message no. FF753 but that does not influence the system behavior.
Else I get error message FF707.
Does SAP behave differently in case of LSMW?
Rgds
Murali. N

Asset depreciation calculation for prevous year when legacy data transfere

Hello,
Asset Legacy Data transfer has made as on 31.12.2006. so, for the first period asset depreciation calculation has done wrongly i.e. on the first period of 2007. but it was not noticed at that point of time, now after 2 years, the cumulative difference is coming out very big.
for 1st period, in Asset Value Tab of AS03, for period 01 , 2007 when i am checking right now it shows for dep. Area 01 right now that Amt to be post (14.48) instead of that in the next line for Dep. area 20 and in the next line it shows, Amt. to be posted ( -0.28). hence, for next period only differnce amount is posted in G/L side instead of actual it should be posted as 14.76.
so, now because of this error, my G/L and AA sides are not matching up.
eventhough i post manual reversal entry via FB01, when i will run ABST2 there will be problem.
if i run manual unplanned depreciation, then will my problem of not matching of Asset side and GL side will be solved. ?
also, please provide suggestion from your end in order to solve this issue.
Thanking you for your help.
Jigs.

We cannot post any depreciation to previous fiscal year 2008 as no planned depreciation is envisaged for the previous year 2008. The transfer date for Legacy asset data transfer is maintained as 12/31/2008 and takeover values are uploaded accordingly. Hence, 2009 is a first year for Asset Accounting of the company code.
However, Depreciation posting program checks for previous period log while executing for the current period. The logs are stored in u201CTABAu201D table. For new company code there will not be any entries in TABA table.
Due to missing functionality, System is checking for previous year depreciation posting logs even though the current fiscal year is first year for planned depreciation and giving error message AA 687.
As per SAP Note 144441 this error can be rectified with the help of correction program ZACORR_TABA_ENTRY_CREATE.
Steps to Rectify the Error:
1. Copy correction program from SAP Note 144441 into SAP System.
2. Execute the program with transaction code SA38
3. Check the values in test mode
4. If the table is updated with documennt number , remove the test mode tick and execute again
5. Execute the deprecation
Edited by: Ramesh Reddy Nalamada on Jul 25, 2009 1:17 AM

Creating legacy data with AS91 problem

Hi all,
We found an old laptop and we just want to trace it. It wonu2019t have a value. So I am trying to create legacy data with AS91 transaction code, after the input Asset Class and Company Code, following error code appears on the screen:
Closed fiscal year does not agree with legacy data transfer date
     Message no. AC199
    Diagnosis
     The closed fiscal year 2010 does not agree with transfer date 21.12.2008
     If you wish to carry out a transfer within the fiscal year, the date of the legacy data transfer has to be in the year following the closed fiscal year.
     Example: Transfer date July 1, 1993; closed fiscal year 1992 In any other cases the transfer date has to be the last day of the last closed fiscal year.
     Example: Transfer date December 31, 1993; closed fiscal year
     Procedure
     Correct your entry.
I know that I can change the FI-AA Date of Legacy Data Transfer but I donu2019t want to change it because I donu2019t know where will be affected if I change the date. Is there any other solution for this?
Thanks for all.

Hi,
Some fields can be made optional for input.
First: check in customizing (transaction OAOA) which screen layout rule is assigned to the required asset class.
Second: go in customizing to Asset Accounting / Master Data / Screen Layout / Define Screen Layout for Asset Master Data. Select the screen layout you found in the 1st step.
Double-click Logical field groups.
Select 2 Posting information.
Double-click Field group rules.
Set the required field on optional (or required - whichever suits you best). Select Main number and/or Sub number for these fields.
The field Acquisition date will only be filled with a date from an actual posting you'll make on the asset. Since you won't have any values on the asset, this field will remain empty. It is not possible to define this field as optional or required in the screen layout settings.
Kind regards,
Andre

Incorrect posting in asset accounting after legacy asset transfer

I have an issue in Asset accounting.
The depreciation key used is LINA (with a base method 0009 and Dec. bal. method 001 straight line depreciation)
My question is:
An asset was acquired 02/01/2005. It has an expected useful life of 1/11.
Under AS93.
I see the asset ***. acquisition value 205,695.00
Accu.ord. deprec - 78,784.06
The asset was transferred to SAP at 03/31/2007.
Now In aw01n I see the following:
Legacy data transfer Per 3 Ord. deprec 10,143.87
Posted Per 4 13,364.13
Posted 5 5877.00
Posted 6. 5877
Till 8th month posted 5877.
The posted values are wrong. Since it was transferred to SAP it has a useful life
of 1 year. At this rate it will go for 3 years.
What can I do to rectify this error?
Why is it posting 5877?
Thanks,

Hi Roma,
The useful life has to be the Total Useful life of the asset.
Since your useful life is less than the expired usefull life the system is calculating depr. for after the end of useful life, which for base method 0009 is curbing.
<i>Curb
With depreciation beyond the planned useful life, the depreciation percentage rate can be derived, not only from the planned useful life, but also from the actual useful life. This method produces a declining-balance effect instead of a straight-line effect (curb).
Use Base Method 0007, this does not curb.
Kind regards
An asset that originally had a useful life of 10 years is depreciated in year 11 by 1/11 = 9.09 %, in year 12 by 8.33 % and in year n with 100/n %.
When you use below-zero depreciation with a curb, the system determines the percentage rate, after the end of planned life, to the exact period and not to the year.</i>

Asset Tables for legacy data takeover

Dear Friends
We've to take assets data from one client to another and hence would be using Legacy assets.
Could you please let me know from which tables / reports i should extract the data related to master & transaction data from the legacy system which is also on SAP.
ANLA - master data and to take those assets which are not deactivated
ANLB
ANLC - asset accumulated APC & dep. And current yr dep
ANLZ - dep terms data
ANEP - asset transaction data for current year acquisitions
I dont have the system in from of me and i hope the above tables are correct.
1. Please let me know if other tables are required?
2. Should the dep area data be posted with remaining useful life & expired life in legacy asset?
Regards
Kapil

Hello Kapil,
I invite you to carefully review the attached SAP notes which should
provide you with the necessart answer:
68802   Legacy data trnsfr: diff.fields n.ready f.input
550176 FAQ note legacy data transfer asset master records
373894 Collective note: introdctn to prblm solutn in FI-AA
Further I also attach the following 6 notes that provide further
informative details regarding legacy transfer, and also some specific
only for legacy transfer during the year:
729164 AS91/AS92: Incorrect ready for input status for prop. values
29706   AS91/92/94: Dep. area fields not ready for input
4206    Net book value input at old data transfer
50607   Depreciation during old assets data takeover
26240   Reconciliation of posted depreciat. after takeover
For further information, please review the information for asset data
transfer in the R/3 Library:
FI-AA - Assets -> Legacy Data Transfer -> Special Considerations for
Asset Data Transfer -> Time of Transfer...
thanks and regards
Ray

Please send detail steps for uploading legacy data

Hi friends,
please send detail steps for uploading legacy data
Thanking u in advance,
Diwa.

HI U CAN USE LSMW TO UPLOAD LEGACY DATA
LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods for processing the legacy data.
The LSMW comprises the following main steps:
Read data (legacy data in spreadsheet tables and/or sequential files).
Convert data (from the source into the target format).
Import data (to the database used by the R/3 application.
But, before these steps, you need to perform following steps :
Define source structure : structure of data in the source file.
Define target structure : structure of SAP that receives data.
Field mapping: Mapping between the source and target structure with conversions, if any.
Specify file: location of the source file
Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time?
How is the decision made which method should be followed? What is the procedure followed for this analysis?
All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
SO Bottom line is make choice of these methods based of real time requirements.
These methods are chosen completely based on situation you are in. Direct input method is not available for all scenario, else, they are the simplest ones. In batch input method ,you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
Try to go through the some material on these four methods, and implement them. You will then have a fair idea about when to use which.
LSMW Steps For Data Migration
How to develop a lsmw for data migration for va01 or xk01 transaction?
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)
Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode : LSMW.
2. Enter Project name, sub project name and object name.
    Execute.
3. Maintain object attributes.
    Execute
    select Batch Input recording
    goto->Recording overview
    create
    recording name.
    enter transaction code.
    start recording
    do recording as per ur choice.
    save + back.
    enter recording name in lsmw screen.
    save + back
Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
    Here you have to enter the name of internal table.
    display change
    create
    save + back
3. MAINTAIN SOURCE FIELDS.
    display change
    select structure
    source_fields->copy fields.
    a dialogue window will come .
    select -> from data file
    apply source fields
    enter No. of fields
    length of fields
    attach file
    save + back
4. MAINTAIN STRUCTURE RELATIONS
    display change
    save + back
5. MAINTAN FIELD MAPPING & CONVERSION RULE
    display change
    click on source field, select exact field from structue and enter
    repeat these steps for all fields.
    save+back
6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
    execute
    save + back
7. SPECIFY FILES.
    display change
    click on legacy data
    attah flat file
    give description
    select tabulatore
    enter
    save + back
8. ASSIGN FILE
    execute
    display change
    save + back
9. IMPORT DATA.
    execute
    display change
    save + back
10. DISPLAY IMPORTED DATA
      enter ok, it willl show records only.
      back
11. CONVERT DATA
      execute
      display change
      save + back
12. DISPLAY CONVERTED DATA
      execute
      display change
      save + back
13. CREATE BATCH INPUT SESSION
      tick keep batch input folder
      F8
      back
14. RUN BATCH INPUT SESSION.
      sm35 will come
      Object name will be shown here
      select object & process

Data transfer legacy

dear all
Can eny one tell me about data transfer legacy?
How are modules interagted and what are means of data transfer for intra module.
Thanks in advance.

Hi,
You would use LSMW to upload master data and either BDC/BAPI for uploading transaction data.
Visit the following link:
Re: sap general
Where you would find more information about BDC and LSMW.
For information regarding LSMW steps visit the following link:
/people/hema.rao/blog/2006/09/14/lsmw--step-by-step
http://help.sap.com/bp_blv1500/BL_US/html/dataconv_lsmw.htm
The SAP System consists of a number of components that are completely integrated with one another. This integration allows the various departments and units of an enterprise to share and maintain the same information.
Purchasing is a component of Materials Management (MM). The Materials Management (MM) module is fully integrated with the other modules of the SAP System. It supports all the phases of materials management: materials planning and control, purchasing, goods receiving, inventory management, and invoice verification.
The tasks of the MM Purchasing component are as follows:
    External procurement of materials and services
    Determination of possible sources of supply for a requirement identified by the materials planning and control system or arising directly within a user department
    Monitoring of deliveries from and payments to vendors
Good communication between all participants in the procurement process is necessary for Purchasing to function smoothly.
<b>Integration</b>
Purchasing communicates with other modules in the SAP System to ensure a constant flow of information. For example, it works side by side with the following modules:
    Controlling (CO)
The interface to the cost accounting system (Controlling) can be seen above all in the case of purchase orders for materials intended for direct consumption and for services, since these can be directly assigned to a cost center or a production order.
    Financial Accounting (FI)
Purchasing maintains data on the vendors that are defined in the system jointly with Financial Accounting. Information on each vendor is stored in a vendor master record, which contains both accounting and procurement information. The vendor master record represents the creditor account in financial accounting.
Through PO account assignment, Purchasing can also specify which G/L accounts are to be charged in the financial accounting system.
    Sales and Distribution (SD)
Within the framework of materials planning and control, a requirement that has arisen in the Sales area can be passed on to Purchasing. In addition, when a requisition is created, it can be directly assigned to a sales order.
http://help.sap.com/saphelp_erp2005/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Hope this will help.
Regards,
Naveen.

HR Data Transfer Toolbox - Initial Conversion

Our project is trying to use the HR Data Transfer Toolbox to initially load all employees using best practice configured action 'X'. However, we have turned on concurrent employment in our config settings. This is causing a BDC error. The BDC records SAPMP50A 2000, but the screen called when you run the BDC session is SAPMP50A 2200. Has anyone come across this issue and what is the proposed resolution.

I am looking for the same thing, from what I can tell, you need to purchase this separately, it's not free. Try the following links and let me know if you find something different.
https://websmp104.sap-ag.de/bestpractices
then click cross-industry packages and then HCM

TDMS Data transfer Step : Long runtime for table GEOLOC and GEOOBJR

Hi Forum,
The data transfer for tables GEOLOC and GEOOBJR is taking too long (almost 3 days for 1.7 million records). There are no scrambling rules applied on this tables. Rather I am using TDMS for the first time so I am not using any scrambling rules to start with.
Also there are 30 process which have gone in error. How to run those erreneous jobs again??
Any help is greatly appreciated.
Regards,
Anup

Thanks Harmeet,
I changed the write type for those activities and re-executed them and they are successfully completed.
Now the data transfer is complete but I see a difference in no of records for these two tables (Geoloc and Geoobjr).
Can you please let me know what might be the reason?
Regards,
Anup

Insert step after data transfer is complete within TDMS package

Hello,
we want to start some jobs after data transfer is complete within TDMS package. For example we want to start the function DELETE_DATA_FOR_ALL_MI_DEVICES. Is this possible or is it possible to start any ABAP report or batchjob?
Kind regards,
Karlheinz

Dear Karlheinz,
It is possible starting DMIS SP07 where you will find an option on the process tree in the work center that says 'Customize Monitor'. This option will you guide through creation of new activities, deletion of existing activities. You have to however create a Z report that pertains to the new activity and maintain some activity definitions.
Regards,
Amit Sharma

How to find the max data transfer rate(disk speed) supported by mobo?

I plan on replacing my current HDD with a new and bigger HDD.
For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
Here's dmidecode:
# dmidecode 2.11
SMBIOS 2.5 present.
80 structures occupying 2858 bytes.
Table at 0x000F0450.
Handle 0xDA00, DMI type 218, 101 bytes
OEM-specific Type
Header and Data:
DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
FF 00 00 00 00
Handle 0xDA01, DMI type 218, 35 bytes
OEM-specific Type
Header and Data:
DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 04/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: OptiPlex 755
Version: Not Specified
UUID: 44454C4C-5900-1050-8033-C4C04F434731
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0200, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0PU052
Version:
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Space-saving
Lock: Not Present
Version: Not Specified
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: 76 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 6
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Not Specified
Voltage: 0.0 V
External Clock: 1333 MHz
Max Speed: 5200 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
Handle 0x0800, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2
Handle 0x0801, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0802, DMI type 126, 9 bytes
Inactive
Handle 0x0803, DMI type 126, 9 bytes
Inactive
Handle 0x0804, DMI type 126, 9 bytes
Inactive
Handle 0x0805, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB2
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB3
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0808, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB4
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0809, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB5
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB6
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB7
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB8
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ENET
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x080E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MIC
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0810, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-IN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0811, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HP-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0812, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x090A, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT1
Type: x1 Proprietary
Current Usage: In Use
Length: Long
Characteristics:
PME signal is supported
Handle 0x0901, DMI type 126, 13 bytes
Inactive
Handle 0x0902, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0903, DMI type 126, 13 bytes
Inactive
Handle 0x0904, DMI type 126, 13 bytes
Inactive
Handle 0x0905, DMI type 126, 13 bytes
Inactive
Handle 0x0906, DMI type 126, 13 bytes
Inactive
Handle 0x0907, DMI type 126, 13 bytes
Inactive
Handle 0x0908, DMI type 126, 13 bytes
Inactive
Handle 0x0A00, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: Intel Graphics Media Accelerator 950
Handle 0x0A02, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: Intel Gigabit Ethernet Controller
Handle 0x0A03, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Controller
Handle 0x0B00, DMI type 11, 5 bytes
OEM Strings
String 1: www.dell.com
Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0F00, DMI type 15, 29 bytes
System Event Log
Area Length: 2049 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFF01000
Status: Valid, Not Full
Change Token: 0x00000018
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: System limit exceeded
Data Format 2: System management
Descriptor 3: Log area reset/cleared
Data Format 3: None
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x1100, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_1
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: AD00000000000000
Handle 0x1101, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_3
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1102, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_2
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1103, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_4
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FDFFFFFF
Range Size: 4064 MB
Physical Array Handle: 0x1000
Partition Width: 1
Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1402, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1102
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1403, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1103
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1410, DMI type 126, 19 bytes
Inactive
Handle 0x1800, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Enabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Enabled
Front Panel Reset Status: Not Implemented
Handle 0x1900, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: *-* 00:00:00
Handle 0x1B10, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00
Handle 0x1B11, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD01
Handle 0x1B12, DMI type 126, 12 bytes
Inactive
Handle 0x1B13, DMI type 126, 12 bytes
Inactive
Handle 0x1B14, DMI type 126, 12 bytes
Inactive
Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x8100, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 00 81 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x8200, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
00 00 00 00
Handle 0x8300, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
Handle 0x8800, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 00 88 5A 5A
Handle 0xD000, DMI type 208, 10 bytes
OEM-specific Type
Header and Data:
D0 0A 00 D0 01 03 FE 00 11 02
Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 78 03 07 03 04 0F 80 05
Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 F8 03 04 03 06 80 04 05
Handle 0xD201, DMI type 126, 12 bytes
Inactive
Handle 0xD400, DMI type 212, 242 bytes
OEM-specific Type
Header and Data:
D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
00 00
Handle 0xD401, DMI type 212, 172 bytes
OEM-specific Type
Header and Data:
D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
BF 00 69 01 56 BF 40 FF FF 00 00 00
Handle 0xD402, DMI type 212, 152 bytes
OEM-specific Type
Header and Data:
D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
65 FC 01 FF FF 00 00 00
Handle 0xD403, DMI type 212, 157 bytes
OEM-specific Type
Header and Data:
D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
52 BF 40 45 02 52 BF 00 FF FF 00 00 00
Handle 0xD800, DMI type 126, 9 bytes
Inactive
Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
00 00 00
Handle 0xDD01, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
00 00 00
Handle 0xDD02, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
00 00 00
Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
Handle 0x7F00, DMI type 127, 4 bytes
End Of Table
Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf says that it is 3.0Gb/s
and here's hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD800JD-75JNC0
Firmware Revision: 06.01C06
Standards:
Supported: 6 5 4
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156250000
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 76293 MBytes
device size with M = 1000*1000: 80000 MBytes (80 GB)
cache/buffer size = 8192 KBytes
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* Gen1 signaling speed (1.5Gb/s)
* Host-initiated interface power management
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct
Last edited by Inxsible (2011-03-27 04:40:49)

I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
Anyhoo, while I was in the BIOS I found two things which I had questions about :
1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
I will edit this post and let you know exactly what settings were present under the Virtualization sub-section.

Legacy Data transfer Initial step?

Similar Messages

Maybe you are looking for