Questions on Asset Data Transfer

Hi Friends,
Currently we are in process to remap the company codesu2026
We have two company codes 1) ALFA 2) BETA
Business Decision : ALFA is going to move company code BETA
System comparability :
1)     Chart of Accounts is same
2)     Chart of Depreciation is different ALFA
I need clarification on these areas
ALFA running asset accounting and depreciation has performed till P9/2011
When moving the data from ALFA to BETA I need assistance
1)     I am going to upload data till 30th-sept-2011 here I took capitalization date as 31/12/2010
I will take asset acquisition value + Accumulated Dep till 31/12/2010 and start depreciation will set as 1st-october-2011 u2026. Here
How can I post current year 9 months depreciation ?? where can I post ? I am unable to run depreciation for those 9 months because I set start depreciation as 1st-october-2011..
Guide me how to post current year depreciation u2026.
2)     In above scenariou2019s how I need to update Asset Life
Ex : Asset   A
       Actual acquisition date : 01/01/2009u2026u2026 life 3 years each month depreciation is 100 Asset value is 3600u2026.
By the time upload into new company
Asset Acqi Value :   3600 Dt : 01/01/2009
Cumulative Dep :   2400    Dt : 31/12/2010
Depreciation for 9 months: 900
new asset master in new company how I need update Asset useful life and periods ??? and how can I post Current period depreciation ?
Highly appreciate your help and guidance
Thanks

Dear TKP.FICO
Select unplanned depreciation in AFAB
Regards
shankar

Similar Messages

Partial Asset data transfer at company code level

Hi all,
We are planning to go live on december 1st, 2007. My client wants to hold a portion of fixed assets relating on one company code and want to convert them after couple of months.
I think I will go with the current conversions and leave the division for which they want to hold, and to keep the company code in test mode. Planning to use the same conversion program designed for that particular division after go-live.
And the GL balances for that particular division will be in non-recon account to ensure that there will not be any inconsistency between GL-FI
Before second load after making correct entries, to convert the non recon account to recon and
Please advice me, about this situation any impacts.
Thanks
Krishna

Never mind. We managed somehow to figure it out ourselves.

AS91 - Legacy assets data - Ord depr posted fieds only displayed.

In As91 I have tried to create one legacy asset, in the takeover screen, ordinary depreciation posted field (depreciation amounts for Jan to April 09) is not open for all the depreciation areas.
How can I change this custo?
In AS92, if I want to change the data, I have this message: u201CAsset values are only displayed for depreciation.u201D
How can I change the 2009 amounts for depreciation ?
Asset data transfer date i have given as 01.05.2009. It is Go Live date
Asset data ordinary dep 2009 period 04.
Can any one help me on this?
Thanks

When you are doing the transaction AS91 it update the values in the table ANLC and when you create asset transactions it update there values to. When a depreciation run is done for this fiscal year it change values in ANLC to.
When some one change the values then in AS92 there is no FI posting and no way to found back what the reason is for the difference between FI and CO.
The depreciation calculation is based on a fiscal year! When the take over value is wrong for this year depreciation then SAP correct it in the first depreciation run.
The last years a did a lot of uploads from other systems in existing companies with assets but used an other way to do the uploads then with AS91
Created an asset with AS01 (option post capitalization on)
Posted the values with the transaction abso with a copy from transaction type 147 (made some little changes in it for reporting reason in the asset history list). In the asset I filled in old asset number, this number was used in the upload to found the SAP asset number for the abso posting.
With the transaction type 147 you can fill in the values by depreciation area (acquisition value, depreciation last years, depreciation this year).
With this option it create direct posting in FI and when a value is wrong you can reverse the posting and post it again.
For the uploads I used LSMW
This option is not the standard way how SAP advise you to do the Legacy assets data upload

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

Table data transfer

Hi,
One basic question on table data transfer. We have a client dependant custom z table. When we transport the table's data also to quality and production, will the client field get automatically updated with the correct client number to which we are transporting it to or will it remain the same? E.g if we are transporting from Dev client 100 to quality client 200, will all the data record's client field be updated as 200 instead of 100? If not, please let me know how it should be done.
Thanks
Swetha.

It will get automatically updated with the Target Client number.
You can check in the Customization tables. Like T001 (company Codes) has the MANDT. We create the Company codes in the customization and than transport to Quality or Producation. Those requests contains the tables entries and they will get saved with the appropriate client in the other systems.
Regards,
Naimesh Patel

FTP data transfer

Hi!
I have some questions regarding FTP data transfer and programing message fields in SAP
1) How can I program the message fields in SAP?
How much effort do I invest on this issue?
2) We are about to replace our FTP-transfer in SAP-system from manuall to automatic (from location/city A --> to location/city B).
The current approach is/was to start batch-input manually.
How can we do this issue? Is there some ABAP-knowledge necessary or is that typical SAP-Basis (administrative) task?
Thank you very much
regards
Axel

Hi!
Are you saying that you want to upload text file using ftp, and run batch input automatically from executing ABAP program?
I would like to find the automatic way for FTP-data transfer frorm location 1 to location 2. My current solution based on manual execution of Batch-input, that transfers/pushes the data from location 1 to the location 2.
Thank you for your recommendation/information.
regards

HR data transfer across server

Hi HR expert,
I have question on HR data transfer from 1 server to other with different clients,
let me know is it possible in SAP to transfer HR data of organizational management i.e. i am mainly consigned about data of HRP1000,HRP1001,PA0002 & PA0105 tables?
let me know if there is any methods to populate HR data.
regards,
John.

PL check the following BAPIs..
BAPI_HRMASTER_SAVE_REPL_MULT   BAPI for Replicating HR Master Data, HR Organizational Data
BAPI_ORGMASTER_REPLICATE       HR-CA: Replication of HR Objects
BAPI_ORGMASTER_SAVE_ORIG_MULT Save Replications of HR Organizational Objects as Originals
BAPI_ORGMASTER_SAVE_REPL_MULT BAPI for Replication of HR Organizational Data
~Suresh

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

Question: New Hard Drive and Data Transfer Kit Device

Yep, I go another HDD this time for my lil Compaq Persario 700 series notebook OS Win XP. I bought a DriveWire Univeral Adapter & Data Transfer Kit. I want to know if there would be any issue transferring my iTunes Library to my new HDD? I do have some music apart of my iTunes Library that's DRM protected. Should still deactivate my account during the transfer . . . that is, if it's possible. Thank you for any assistance your can give me. Itunes 10 by the way.

From what you posted, you should be able to set the itunes media folder location to the exHD and then run the ituens consolidate library command.
That will put your itunes library content onto the exHD.
Here's Apple's article on that
http://support.apple.com/kb/ht1364
Pay attention to this note from it
+Note: If you move your library to an external drive, you'll need to power up and connect the drive before starting iTunes. If you don't, iTunes will prompt you to either locate the library or to create a new library (which will result in an empty library). No matter what, it's always a good idea to have a backup of the media you have in iTunes.+
That means you MUST have the exHD connected BEFORe starting itunes. WHat it doesn't mention is, it always needs to have the same drive letter. WIndows can change USB port drive letter without telling you it's doing it. Best practice, is to assign a permanent drive letter such as m: for Media. You can assign drive letters using windows disk manager.
There's no need to deactivate any account during this procedure - why do you think you should?

Data transfer with some errors on registers. (Novice question)

Hi experts.
First of all i wat to say that i'm realtively novice in BW.
I have an ods object. I have a transformation>Data Transfer Processes>Infopackage to load data to it.
I execute this with a process chain.
well the roblem is that some registers I get are erroeous. That's ok, i just want lo load the OK regs, but when this happens the sistem does't load any.
I want to load only the good registers and be reported about the errors too.
Can someone please give me some advice about this?? I think thje secret is in the error handling customizing on the DTP, and maybe create a error DTP and something in the infopackage.
Any tip to me please?
Thank you!!!

Hi,
you need to maintain some parameters in the update tab of the dtp.
a) set the error handling to update valid records, reporting possible (request green)
b) enhance the no. of error records to the size of the data packet.
c) create a error dtp
Now all records without error will be updated, the request will be green and so available for reporting. The records with errors will go to the error stack and can be edited there. The records of the error stack will be updated thru a error dtp.
regards
Siggi

Simple Question - Data Transfer Object

Hey gurus,
I like the option in JBuilder to automatically create Data Transfer Objects and an Assembler for it. But what? I used to make the assembler a Session Bean, and JBuilder makes it a normal Java class with static methods. I know JBuilder always ships with the best solutions, but...
what is the advantage of the static class here? And in my case, i have the session beans and the entity beans deployed on a different server, would that make a difference for the advantage?
greets,
Nick.

Hey gurus,
I like the option in JBuilder to automatically create
Data Transfer Objects and an Assembler for it. But
what? I used to make the assembler a Session Bean,
and JBuilder makes it a normal Java class with static
methods. I know JBuilder always ships with the best
solutions, but...
well....... not always
:-)

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.

Data Transfer

I'm developing an application for a customer who requires data to be transferred between what they have termed a Level 3 Database Server and a Level 2 Database Server. Prior to the start of a production run they require that the data entered in a table on Level 3 is transferred to an identical table on Level 2. I have accomplished this using a database link defined on Level 2. I then developed PL/SQL Cursor to read out the data from the Level 3 table and insert into the corresponding Level 2 table. This action must be initiated by an operator it cannot be automatic. Although this is a non business critical application I'm not happy with this solution because how does the Level 2 system know the data is ready for transfer and that the data is current and how does the Level 3 system know the data transferred without error? I'd like to include some kind of transfer structure and I can think of is adding a table on the Level 3 server which defines a command word for the data transfer function. When the data is ready to be transferred Level 3 sets this word to 1. Level 2 is now able to initiate the transfer and when it's done so and run a basic table comparison. If the comparison is successful it resets it to 0 or, if it fails to -1. I have two questions I'd be grateful if someone would consider.
1. Am I reinventing the wheel? Does Oracle9i come with an inbuilt feature which makes what I'm trying to do easy?
2. How to compare two tables for differences.
Thanks in advance, my job would be a lot harder without you guys.

Hi - you might want to consider the following.
Try to load the data onto a staging area.
In the staging area the tables might have extra fields.
Use sqlldr to load with option for error logging.
You've to have the total records for each table from the orginal target and compare with the total loaded on the destination (staging).
For comparing the tables - yes - you need to compare each and every field.
Select ....
FROM table_a a, table_b b
WHERE ...
Or use TOAD for Oracle - if there's not too many records. (Manually check...)
They all can be automated, provided all the checks (your requirements) are flagged OK (or NOT OK== 'do not proceed').
Use a Control Table with fields as follows -
SL_NO, TABLE_NAME_PROCESS, TOTAL_ORG_COUNT, TOTAL_LOAD_COUNT, TABLE_COMPARE_SUCCESS
1 PROD_CUSTOMERS 100000 100000 Y
The values in the above table (except SL_NO, table_name_process) are got programtically.
So you basically update the values, and before each step you check if they are ok...
So if you have now loaded the table and updated the load_count, before you try to compare check if the load is completed sucessfully, else no use proceeding...like wise after table value compare...
Cheers.
Lovell.

Error 33172 occurred at Read & Write data transfer between two or more PF2010 controller

Hi,i need to do data transfer between two or more FP2010 controller.e.g. FP2010(A) & FP2010(B).
FP2010(A) need to transfer the measurement (from its I/O module) to FP2010(B) to do the data analysis.These data transfer should be synchronous btw two controller to prevent data lost.
From the vi used in the attachment,i encountered some problems at:
(1) Error 33172 occurred while publishing the data.Can i create and publish data under different item name?
(2) How to synchronies the read & write btw contorller?
All controller are communicating with each other directly without the need of a host computer to link them together
Is there any other method to do fast data transfer betwe
en controller?

Hi YongNei,
You were succesful in omiting enough information to make it very difficult to answer!
Please post your example.
Please tell us what version of LV-RT you are using.
Please define what you concider "fast data transfer".
Have you concidered mapping the FP tags of FP2010(A) to FP2010(B) and vise versa?
WHat exactly has to be syncronized?
If you have something that is close to working, share that.
Well, that as far as I can go with the info you have provided. Depending on the details, what you are asking could be anything from trivial to impossible with the currently available technology. I just can't say.
It would probably be a good idea to start over with a fresh question (sorry) because not many people are going to know what a a "
PF2010" is and I can not guarentee that I will be able to get back to you personally until next week-end.
Trying to help you get an answer,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Questions on Asset Data Transfer

Similar Messages

Maybe you are looking for