Rec - data transfer

Hi
While transferrring data from recrutiment to PA, i want only those infotypes which are updated by user in recruitment to be transferred to PA(apart from the mandatory infotypes). I am using operation MOD still the IT updated in recrutiment does not pop up during data transfer.
Please help me in this regard
Regards
Minal

Thanks Nicole for your inputs.
Need to confirm some more unsderstanding
- where is master data of E rec stored? and is thr any storage period to be define for the data.
I understand that attachements are stored in DMS and we can define the storage period for the same but what ant the object data, activity record data, etc...
Ext cand is attached to CP to BP but where are these stored ECC or whr?
- Regarding integration aspect I was told that PSA will be mapped with location in E rec, Ed fields in PA will be available in E erc is it correct? I have to take requirement for each object from client eg.-functional area list, industrry etc..so do I need to consider any PA integration data which will be available in e rec and jst need to add the list...
- When job posting is viewed by external candidate does it hit ECC for details?
- How to consider Virus scan for documents attached..
Regards

Similar Messages

E Rec data transfer & Integration with PA

Hi Gurus,
As per my understanding E Rec & PA integration is diff concept and Data transfer from E Rec to PA & vise versa is separate.
We have E Rec on same instance as ECC. and Client needs to have all e rec object data available lifelong and transfer most of the data to PA from E Rec.
Can you please illustrate on Integration and data transfer concept.
Regards

Thanks Nicole for your inputs.
Need to confirm some more unsderstanding
- where is master data of E rec stored? and is thr any storage period to be define for the data.
I understand that attachements are stored in DMS and we can define the storage period for the same but what ant the object data, activity record data, etc...
Ext cand is attached to CP to BP but where are these stored ECC or whr?
- Regarding integration aspect I was told that PSA will be mapped with location in E rec, Ed fields in PA will be available in E erc is it correct? I have to take requirement for each object from client eg.-functional area list, industrry etc..so do I need to consider any PA integration data which will be available in e rec and jst need to add the list...
- When job posting is viewed by external candidate does it hit ECC for details?
- How to consider Virus scan for documents attached..
Regards

E-Rec: XI for data transfer

Hello Experts,
I am working on an implementation project where SAP E-Rec is on different box. We are on EhP5. We have XI for data transfer between both the systems (ECC and E-Rec). Now, when we use RFC to connect these systems, we use PA48 in ECC to hire candidates as employees which in turn pulls data from T752F table. Now as we are using XI, how/where does data flow?
Also, please guide in case candidate is a rehire, how and where to capture his previous perr number to validate candidate is actually an old employee? Instead of T752F, which table is populated which creates an entry in HR admin's UWL. Please help understand.
Thanks and regards,
E-Rec Beginner!

Hello,
Please have a look at the attachment of note 997181 where the HR integration process is explained.
Regards
Nicole

New Hire Data Transfer from E-Rec to ECC via PA48

Hi,
We have requirement where we need to use the basic new hire data transfer from erec to ecc using PA48.
Could someone help me by listing the step by step process that is required to configure in both EREC & ECC?
I know there is pdf document available online but that refers mostly to XI which we are not planning to use.
Please help.
Regards,
Vikram

Hi,
For integration between E-Rec and ECC, check [Link|http://help.sap.com/saphelp_erp2005/helpdata/en/45/8150635e9c40c1e10000000a1553f7/frameset.htm]
This gives detailed information on synchronous and asynchronous data transfers between E-Rec and ECC.
Hope it helps!
Arpita

Errors in ALE data transfer to E-Recruiting.

Hello,
I need help with my ALE for E-Recruiting.
We are on E-Rec 604 with seperated standlone e-rec system.
We have set up ALE Data transfer for object type P from ECC QA to E-Rec QA system but unfortunately the I-Doc is always gettign posted with status 52.
Those are the messages:
Object 01 ,P ,01012021 does not exist: infotype 0105 cannot be created
Object 01 ,P ,01012021 does not exist: infotype 0009 cannot be created
Object 01 ,P ,01012021 does not exist: infotype 0006 cannot be created
Diagnosis:
You have tried to create infotype 0105 for plan version 01,object type P,object ID 01012021. However,the object does not exist.
PA objects exist if infotypes 0000, 0001, and 0003 have been created.
PB objects exist if infotypes 4000, 0001, and 0002 have been created.
PD objects exist if infotype 1000 has been created.
I followed the setting of "standalone" attachment to note 997181:
HRSYNC_P                                    CONV_HR_DATA_TO_EREC (active as of Release 604)
HRALE00INBOUND_IDOC             HRRCF00_INBD_NEWMOD (active as of Release 604)
HRALE00SPLIT_INBOUND            HR_INB_PROCESS_IDOC (inactive as of Release 604)
HRALE00INBOUND_IDOC             HRRCF00_DELETE_SPREL (inactive as of Release
604)
HRALE00SPLIT_INBOUND            HR_INB_PROCESS_IDOC (active up to Release 603)
HRALE00INBOUND_IDOC             HRRCF00_DELETE_SPREL (active up to Release 603)
So we have activated only the CONV_HR_DATA_TO_EREC and HRRCF00_INBD_NEWMOD because we are on 604.
We have distributed Infotypes 0000, 0001, 0002, 0105 (Subtypes 0001 and 0010), 0006, and 0009 and I have to distribute the P - CP relation with 1001 A209.
Somebody could help me please?.
Thanks,
Esther

Hi Esther,
Can you share you inputs how you have fixed the issue.
Currently we are following I2 A Scenario according to the link
http://help.sap.com/erp2005_ehp_05/helpdata/en/49/46037f06971ec6e10000000a42189b/frameset.htm
DO we need activate the swiches in HR System or Erec System.I believe it has to be in HR
HRALX HRAC - X
HRALX PBPHR ON
HRALX USRAC X
RECFA HRRFC
RECFA RECCE
RECFA DTCBA
BADI do i need to activate only below one's
HRSYNC_P
CONV_HR_DATA_TO_EREC (active as of Release 604)   HR system
HRALE00INBOUND_IDOC
HRRCF00_INBD_NEWMOD (active as of Release 604)   Erec System.
Correct me if im wrong.

Employee Data Transfer From Recruitment to PA

Hi All,
I have a query pertaining to employee data transfer from recruitment (PBA7) to PA.
Here the client uses recruitment module only for data maintenance and then transfer the data to PA module. Is it possible if we skip the data transfer from Rec. module to PA module.
Please advise URGENTLY.
Regards,
Garima

Garima,
If your query is resolved, request to close the thread or else feel free to touch base
Thanks and Regards
Anil

Data Transfer Erec and ECC HR

Hi all,
We are using having 2 backend systems 1 for HR other than Erec and another one for erec.
Now we have setup the ALE data transfer using Message type HRMD_ABA.
In erec we have only ERECRUIT Component deployed in backend,no EA HR or SAP HR component deployed.
MEaning no PA* tables.
Now when Transfer personnel number(HR!001-A008 with Position) to erec box,it says no pernr exist.
Howver i cannot tranfer the pernr from ECC to Erec as we dont have PA* tables in Erec.
Can you share me the object types that are transferred from ECC to EREc and EREC and ECC.
What are the components to be deployed in backend Erec box.
In Portal for requistions application which should backend(System Object) and for recruiter and recruitment admin applications which should be the backend system(System Object).
Thanks,
Nachy

Hi,
Check the link :
http://help.sap.com/saphelp_erp2005/helpdata/en/45/8150635e9c40c1e10000000a1553f7/frameset.htm
Supported infotypes for transfering data from the E-Recruiting to the HR-System are the PA infotypes 0,1,2 and 6. There are 15 fields sent to pa48 if they were filled in the E-Recruiting system, which are
- forename, initials, surname
- gender
- birth date
- correspondance language
- address (street, city, streetcode, region, country)
- hiring date
- organisation unit
- position
- personel number (for internal candidates)
So these are the infotypes which can be transfered automatically and cause no problems. If you want the "title" to be transferred additionally, you have to adjust the system behaviour accordingly.
To set up data transfer,
In E-Rec System, use Tcode - BD64 Partner Type LS - Generate partner profile for the ECC System
Use Tcode - WE20 for the Partner profiles checking
For ECC Partner Profile, Give Outbound parameters - Messahge type HRMD_ABA and SYNCH. Give Inbound parameters- Message Type HRMD_ABA
In ECC system, use BD64 for the Partner Type LS. Partner Type LS - Generate partner profile for theCreate Erec System(
Use Tcode - WE20 for the Partner profiles checking
For E-Rec Partner Profile , Give Outbound parameters - Messahge type HRMD_ABA and SYNCH. Give Inbound parameters- Message Type HRMD_ABA
After doing data transfer using RHALEINI, use transaction SM58 to check whether the data has been transferred or not.
Hope it helps!
Arpita

Candidate Data transfer from E-Recruiting System to HR system for New Hiring.

Hi All,
Hope everyone doing in good Spirit.
We are implementing E-Recruiting as Standalone for one of our client.
Can any please help me in regards with Data transfer from E-Rec System to HR System for hiring once the candidate has been successfully completed recruiting process.
You inputs are highly appreciable.
Thank you.
Sekhar.

Hello Sekhar,
there are three different scenarios for transferring the data of an external candidate to the HR core for hiring.
the easiest and most commonly used is the RFC connection. When creating an activity of category data transfer the data of the candidate is transferred from eRec to HR core. There it is stored in table T752F. Then you can run transaction PA48. There you can select the candidate and run a hiring action. This is the same action like in PA40 only the system will preset the fields with the values from eRec (similar to batch input).
Instead of using the RFC solution you can transfer the data using PI (this can be activated using a switch in T77S0). To be honest none of my customers is using this. Either they had no PI server at all or they did not use it for eRec
The third was delivered with a business function HCM_HIRE_INT_CI_1. This is based on HCM processes and forms and targeted towards customers using Talent Management Core (e.g. data for education and work experience is transferred into the TM Core infotypes 740X as contrary to the hr core standard infotypes 0022 and 0023 they are structured like the eRec ones). Of course as you can do a lot of customer enhancements to HCMP&F you can replace the behavior nearly completely. One or two of my clients discussed this solution but as far as I know none is actually using it.
The simple truth is most customers seem to not use any integration at all. The first solution is easy to activate but only covers around 13 fields. Compared to a real full blow hiring action this is not even 10% of the fields which have to be entered. So the presetting this small number of fields is not a great help especially as you have to check every information anyways. Furthermore PA48 is not very nice and lacks functions to structure the incoming records which makes it difficult to handle in large distributed organizations.
The other two options require a lot of infrastructure for small functionality. What we discussed with a client was using the new hire integration to preset a full hiring form with eRec data and then send to the candidate as offline form to gather all missing information and use this for hiring. But there were to many issues on data privacy aspects when sending a form with social security data, bank account data, etc. via email. Furthermore they required actual signatures.
Kind regards
Roman

ALE Data Transfer Issue--Needs Immediate Attention

Hello Gurus
I am hoping somebody can guide me here--
We are on E-Rec 603 with seperated standlone e-rec system.
we have set up ALE Data transfer for object type P from ECC QA to E-Rec QA system but unfortunately the I-Doc is always gettign posted with status 52 ( application document not fully posted).
The infotypes 0000,0001,0002,0006 and 0105 are being transferred. The report HRALXYSNC refuses to recognise the 'P' object transferred and says=='data not found for search condition'.
We debugged HRALXSYNC and found that IT 0003 needs to be included but we tried transferring that too--however, the ALE still fails to transfer the data.
Not sure why the data transfer is not happening--what is the best alternative?
Would really reallly appreciate some light....!!
Thanks
Tania

Hello Tania,
first of all we should have a look on your system landscape. If you have e-recruiting on an standalone server, the server installation should only include basis components (BASIS, ABA, PI, ...) and the e-recruiting component. Running e-recruiting standalone on a server with a complete ERP installation is not officially supported up to EhP3.
Could you please check that you either have the first landscape situation or if you have installed a full ERP implemented note 1147882.
Before running some ALE at all ensure that the system works well and w/o any SLG1 entries for external candidates and internal candidates created using report RCF_CREATE_USER.
Then make sure the BAdI implemtations are set accorting to note 997181:
BAdI                    Implementation
HRALE00SPLIT_INBOUND    HR_INB_PROCESS_IDOC -> activated
HRALE00INBOUND_IDOC     HRRCF00_DELETE_SPREL -> activated
HRSYNC_P                CONV_HR_DATA_TO_EREC -> deactivated (if existing)
HRALE00INBOUND_IDOC     HRRCF00_INBD_NEWMOD -> deactivated (if existing)
For the distribution model define a filter restriction the infotypes / subtypes destributed for P to:
Infotype 0000
Infotype 0001
Infotype 0002
Infotype 0006 Subtype 0001
Infotype 0105 Subtyoes 0001, 0010
If you want to include the OM in E-rec (use positions in requisition maintenance, etc.) add a filter for Infotypes 1000 and 1001 for objects P, S, O and C (you can use the subtype to restrict relations and avoid unnecessary relations in the IDoc. P->CP relation is only necessary for EhP 4 and higher.
Make sure you use the best practise step by step descripion for the intial data transfere for EhP 3 documented in note 997181 document Two_Instance_E-REC_Integr_ERP_EN.pdf page 4, add the processing for type C after each object type S step.
Hope that helps.
Kind regards
Roman

OM and PA data transfer from SAP 4.7 to ECC 6.0

Dear Experts,
hi
i am working on one project where i will need to design the data transfer from SAP 4.7 to ECC 6.0. this is not a upgrade project.
the data of PA and OM are in 4.7 which is existing system. i need to transfer entire data into ECC 6.0 so i can use that data for my E-Recruitment module ( we are doing E-rec fresh implementation.)
we will keep both the systems (4.7 and ECC 6.0). ECC 6.0 will be used for E-Rec and OM only. for PA and Payroll we will use 4.7.
can some one tell me,
1. what are the key points to keep in consideration from OM point of view ?
2. which is the best method to transfer the OM structure and data from 4.7 to ECC?
3. what are the risks?
4. which system we should make master system and which will be the slave system? why ?
your input will be much appreciated.
thanks and regards
chandra

Hi Chandra,
I was under the impression that you are planning to use PA & OM from 4.7, now I read it again.
Now its advisable to keep ECC 6 as a master system, becoz OM is the stating point of the HR processes where all Orgnization unit, job, position exists. Later the same data can flow to the slave system for PA use. As OM is the starting point, this system should be the master system.
Abou the IDoc interface.
Check the basic type HRMS_A05, whether it has all the data you need to transmit. T-Code WE30
If you need to add something you can create a Z version in WE31. I selected HRMS_A05 as it is present in both the SAP version.
Next there are series of transaction you need to process. Check with technical person who hands IDoc interafcing.
Steps are:
Assigning Message type to IDOC Type with extension. T-Code WE82
Create Logical System:
T-Code SALE-> Basic Settings-> Logical Systems-> Define Logical System
It is required to configure in the sending system as well as in the receiving system
Assign Logical System to Client:
T-Code SALE-> Basic Settings-> Logical Systems-> Assign Logical System to Client
Create RFC Destinations:
T-Code SM59, select ABAP connection of type 3.
Create Distribution Model: T-Code BD64
Generate Partner Profile: T-Code BD82
Maintain sending system partner profile: T-Code WE20
Link Message Type to Function Module T-Code WE57 in receiving system only
Hope this will help.
Let me know if you need anything else.
BR/Manas

Data transfer from E-recruitment to PA

Dear All,
we are Implementing E-recruitment. while transferinf the data from E-recruitment to Personnel administraion, I am getting the error, No data available from the partner system table T752F). We are using the same server for E-rec and PA.
While doing the data transfer activity in E-recruitment i m getting succfulll. In R/3 while going to the Tcode PA48 i m getting the error.
Please help me on this.
Thanks and Regards,
Revathi.

An integrated hiring (data transfer) scenario with SAP e-recruitment
and R/3 starts with creating a "Data Transfer for New Employees"
activity within e-recruiting for the candidate selected to be hired.
Data from e-recruitment is transferred to the target HR (via an RFC
call) and stored there in a holding table (T572F) for processing
by an appropriate action. Within the HR system, execute transaction
PA48 to access the holding table. Select the candidate you want to
process and then click the "Hire" button, and continue with the
appropriate action.
This message occurs, if you execute PA42 or PA48, in order to perform
the personnel action RA (Integration with Recruitment in Partner
Systems) and no data exists on the R/3 or external system.
You will find all the relevant information in the IMG documents
available. Please check;
- Set Up Data transfer from SAP ECC
- Set Up Data Transfer for New Employees

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.

ISSUE:regarding production version tab of MRP4 of data transfer using BD10

Hi all,
This is regarding production version tab of MRP4 of data transfer using ALE idoc (BD10).
When i transfer the data using BD10 the production version is received at receiving end through segment
but not created in MRP4 view tab.An error is coming as-
"You wanted to maintain the master record of the material AB_06.04.09(2). However, it is already being processed by the user EBGABAP and is therefore locked."
I logged in as-EBGABAP
Please help me resolve the issue.
Thanks
Edited by: sanu debu on May 6, 2009 11:08 AM
Edited by: sanu debu on May 6, 2009 11:09 AM
Edited by: sanu debu on May 6, 2009 11:11 AM

>
sanu debu wrote:
> Hi,
> I have to upload production version tab data of MRP4 view(MM01).Please suggest a function moduleor bapi for the same.
>
> Thanks.
>
> Edited by: sanu debu on May 6, 2009 3:24 PM
BAPI_MATERIAL_SAVEDATA can be used, populate the respective fields in input parameter PLANTDATA

Bottleneck in Data Transfer

We run a small network in our office consisting mainly of Intel iMacs we purchased several months ago. The server computer is a brand new Intel Mac Pro server with 4 500 gig drives raided together, two 2.66GHz dual core intel processors, all the other bells and whistles we could think of, etc. We added in two fiber-optic switches: one in the server room, one in the office. The switches connect to each other and the server with fiber optic cables, but the iMacs connect with ethernet cables.
We had the iMacs for a while but we just recently got the new server and upgraded our old 100 base switches. Afterwards we wanted to test out the data transfer speeds, as we plan to back up to the server frequently. We were dismayed to find that transfer rates capped out at 60 MegaBytes/sec according to the Activity Monitor's Network Activity tab. In fact, it would range mostly from 40-45MB/sec. None of us here have much experience with networking, but that seemed a tad too slow. My basic math tells me that a byte is 8 bits, and from that a Gigabit network should transfer data at 120 MegaBytes/sec, which is three times the speeds we were actually seeing.
We sent data both to and from the server in order to test this. Thinking it was perhaps a problem with the ethernet itself, we grabbed an external FireWire hard drive and transferred data from one of the iMacs directly to it and noticed exactly the same transfer rates. We plugged two iMacs directly into each other and transferred at the same rate, ~45MB/sec.
Well this was highly frustrating. All Macs supposedly ship with Gigabit ethernet since, what, 2002? Earlier? Why are our speeds so slow? We thought the hard drives might be slow, so we got info on the drives and googled them for their tech specs. The iMacs' Western Digital drives are capable of much much faster speeds according to everything we've read.
We started reading anything we could online that addressed this issue. Some information read the problem might be that the optical DVD-R/CD-R drive was only capable of slower transfer speeds. Since the optical drive and the hard drive are on the same bus it would slow down the hard drive's maximum transfer rate, much like having a Gigabit hub with a 10 base computer plugged into it would slow the entire network down (which is of course why we use switches instead of hubs). Is there any truth to this? If this is, in fact, the case, can we bypass this bottleneck somehow? I'm not talking about opening the computer and manually disabling the optical drive, as that's a waste of a perfectly good DVD-R/CD-R drive.
Also, if this is true, why in blue blazes is Apple flaunting Gigabit ethernet if the computer can only take advantage of 1/3 the speeds Gigabit ethernet has to offer?! I'll happily provide any more information that's relevant to the problem at hand.
Thank you
Mac OS X (10.4.8)

Here's the specs for the default Hard Drive that Apple put in here:
http://www.westerndigital.com/en/products/Products.asp?DriveID=137
From that page
Buffer To Host (Serial ATA) 300 MB/s (Max)
Buffer To Disk 748 Mbits/s (Max)
I have no idea what signaling overhead for my data transfer protocol means.
The ethernet cords are no longer than 20 feet, are all Cat5E, and are well shielded. There is little to no ElectroMagnetic interference in any area they run. The longest cable is the Fiber Optic one, which runs about... oh... 40 yards? These were all installed by professionals.
I feel it's important to stress the fact that we tested an isolated direct computer to computer transfer with a single 6 foot Cat5E Ethernet cable and still experienced the same speeds that we experienced over the network. We tested multiple computers, multiple cables, multiple files.

Issues with data transfer / connectivity

Hi,
I bought a Curve 8320 last week and activated BIS. The issue that I am facing is:
- Mails do not get delivered and connectivity to the internet is lost even though the data signal (EDGE) is available. I can see an upload arrow flashing on the right top corner
- What I have noticed is that the connectivity gets resumed when I do any of the following:
a. Switch on WiFi (immediately the data connection starts receiving and sending messages and internet connectivity is resumed). Even after switching off the WiFi, it works fine
b. Switch off the device and restart
Can someone help me? Please let me know if you need any more details.
Thanks

You can try using FExplorer and using it to delete the file C:\system\shareddata\101ff93b.ini from the phone. It should reset the Data Transfer app.
FExplorer you can find here:
http://www.gosymbian.com

Rec - data transfer

Similar Messages

Maybe you are looking for