Implementation of outbound data transfer

As far as I understood it outbound web services are not available in SOD.
However, in one of oracle's white papers it says:
"For instance, information about recently closed opportunities can be retrieved
through the Siebel Web Services On Demand interface and be inserted into
an order entry system that has been fitted with a Web Services front end"
How can this be realized?
Thanks Claus

There's a QueryPage function in each of the data web services. You can use it to retrieve data.

Similar Messages

Outbound Data Transfer pricing confusion

I have a customer who may want to move their website/SQL database to Azure, so I am doing some price analysis to make sure I am presenting the options correctly. As such, I need clarification on Outbound Data Transfer pricing. I have an MSDN Premium subscription
and I am using my monthly credits with that subscription to analyze how billing works.
I am comparing the pricing page (http://azure.microsoft.com/en-us/pricing/details/data-transfers/) to what I am actually seeing on my bill, and more specifically, in the billing
CSV that I downloaded to analyze. According to the pricing page, Inbound Data Transfers are FREE, which is what I am seeing in my bill. For Outbound Data Transfers, it shows that the first 5 GB of data transfers should also be free. However, when I download
my billing CSV, I see that I am getting charged for my outbound transfers even though the total so far this month is only 0.25GB (all Zone 1.) While I understand that the price for this is negligible, I want to make sure I am understanding the pricing pages
properly so that I can advise my client properly.
Why am I seeing charges for my Outbound Data Transfers when the first 5 GB/month are supposed to be free?
Thank you,
Cindy Kee, CNC Consulting

I guess it pays to read the fine print! :)
So since my client will be a regular paying customer, they will get the first 5GB free. That's good news.
Thank you,
Cindy
Cindy Kee, CNC Consulting

Data transfer cost

If I exec a sql command outside azure on another server like
sqlcmd -S sld51cxbyz.database.windows.net -U bleetmaa@sld51cxbyz -P Kj73Bh71D -d MigrationFromAX -Q "exec dbo.runAzureDbJobs"
runAzureDbJobs is a bunch of procs who is merging two tables located inside azure.
What will the data transfer cost? Does the procs executet inside azure or will the data transfer between the external server and azure?
bleetmaa

Hi,
If you Work role and your sql database in the same region, you are not charged.
see this:
Is data transfer between Azure services located within the same region charged?
No. For example, an Azure SQL database in the same region will not have any additional data transfer costs.
If they are in different regions, you could be charged .
Is data transfer between Azure services located in two regions charged?
Yes. Outbound data transfer is charged at the normal rate and inbound data transfer is free.
See the pricing Page:
http://azure.microsoft.com/en-us/pricing/details/data-transfers/
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Data transfer b/w SAP to Java using IDOC and Interface SAP Jco

Dear Experts,
The challenging requirement we are having is, we need to create the interface for data transfer between SAP system and the Java system. The data will be transferred from SAP to java and similarly once some processing done in Java again the details needs to be transferred from Java to SAP.
For this data transferred we are planning to use IDOC process and for interface "SAP Java connector (Version 3.0.5)" we are planning to use. As per our understanding, from Java side one program needs to be written to connect with SAP as "Registered program". This registered program will appear in SAP GATEWAY automatically and using tRFC, TCP/IP connection both SAP and Java system will be connected.
In this case we are having some doubts.
1. The data from SAP is going to be transfered from one Custom transaction (Z tcode). Once "Outbound IDOC" will get triggered and will carry the details. Now the doubt is, whether the data / details will get transfered to JAVA system automatically or we need to perform any other steps from SAP ABAP coding...(like converting in to flat file, XML file and etc) ??
2. We are planning to install "SAP Jco" in Java server. Is this correct...??
3. Other than SAP Jco any other softwares needs to be installed or not..??
4. Since we are going to trigger the "outbound IDOC" from custom transaction, we are planning to develope one program in SE37. Other than this any other program we need to develop or not..??
5. Any sample Java program for the SAP Jco version 3.0.5 to create the "Registered program" with SAP..? (e.g. SAP Listener program).?
If anybody has detailed steps or explanation please share it with us.
Thanks in advance
Warm Regards,
VEL

Hi All,
For the above mentioned issue, we implemented JCo software in JAVA system and created the JAVA program including SAP logon credential details like Client, User name, password and Language details.
When this JAVA program was compiled successfully then, that non SAP system will appear in SAP gateway Tcode.
Once non SAP system started appearing in SAP gateway that means, both SAP & Non SAP are connected automatically.
Regards,
Velmurugan P

ALE data transfer in E-recruiting

hi All,
We are Implementing E-recruitment in HCM.
            I have following 2 requirements
Case 1). Distribute data of infotypes 0000,0001,0002,0006,0022,0023,,0024,1000 and 1001 into ER(E-recruiting) from my HCM (ECC) system. This i have achieved using message type HRMD_A and setting up ALE as per standard guidelines.
Case 2) i have to transfer Candidate data which gets created in E-recruitment server back into HCM(ECC) server(reverse of case 1) and stored them in infotypes 0000,0001,0002,0006,0022,0023 and 0024. How this can be achieved ??
is there any standard way i mean IMG configuration or ALE setup to transfer this data back into HCM (ESS) server?? or any BAdis or BAPIss??
    kindly suggest me some solution if anyone of you have encountered the same situation in past. The final solution i m thinking is of creating custom basic IDOC type, message type and custom programs for inbound and outbound processing but before doing this i just wan to have a confirmation that there is no standard way of doing this...
Thanks in advance..

Hi.
     There is a standard activity in e-Recruiting "Data Transfer for New Employee" which transfer the Candidate data from e-Recruiting to HCM system in temprary table T752F. when you hire this candidate from PA48 all transfer data will get stored in respective Infotype of SAP HCM system..
Thanks,
Madhu

Data transfer between SAP & Java and Vice versa using IDOC Process

Dear Experts,
        We are working on one of the good requirement related to data transfer between SAP and Java software. Client requirement is, they want to transfer the data in both the ways (from SAP --> Java and Vice versa also).
In detail is, after sales order creation using one custom program loading plan details will be calculated. Once loading dates are confirmed then, user will release the sales document to transfer the data from SAP to Java using "Outbound IDOC processing". Similarly in that JAVA software some shipment details will be performed, once completed from JAVA software again details needs to be pumped back to SAP as "Inbound IDOC Processing".
For this fields are already identified from external software SAP and we are looking for the same to perform the steps in SAP.
At this stage, I need your expert opinion / feedback how to go about at this stage.
Meaning,
                 1. What are the customizing steps needs to be done in SAP..?
                 2. How to trigger the :Outbound IDOC process" once the documents are "Released" from custom transaction
                 3. How to create the link between SAP and JAVA to transfer the data between these 2 software
                 4. How to trigger the "Inbound IDOC Process" from JAVA software to SAP and how to store the data in SAP
Experts, please give your feedback in terms of reply or by sending the step by step process to fulfill this client requirement.
Thanks for your cooperation.
Regards,
Ramesh

Maybe too many open questions in the same document.
Maybe you should repost a more specific question in a technical forum.
This looks like a small project where you already know what you want, maybe you should contract a technical specialist so he proceeds to the implementation!

HR Master Data Transfer to MRS

Hi Experts,
we have recently implemented MRS scheduling for PM orders and we ran three jobs to transfer work center data, capacities and personnel assignment from ECC6 HR (release 604/0020) into MRSS (release 700/0004) . The reports are /MRSS/SGE_PN_MNT , /MRSS/CAG_CG_PLANNING_NODE_MNT and /MRSS/HCM_RPTWFMIF. The data transfer took several days to run manually.
Now our customer wants to run nightly updates to MRS on any work centers/ Personnel records which have changed. Issues are:
u2022 /MRSS/CAG_CG_PLANNING_NODE_MNT short dumps if you execute in background
u2022 if PM users have work orders open when we execute the jobs, the useru2019s transaction can short dump (this can happen even if they are from a plant which is not related to the data being transferred)
How have other MRS users overcome these issues of regular HR master data updates?
Thanks in advance
Sarah

PFAL transaction is used when we want to transfer an object without a change pointer. For sending deltas you should be using RBDMIDOC (TRAN - BD21) and provide the message type . This program will send the delta.
But neither of the programs PFAL or BD21 will help in filtering the future dated record. This filtering should happen in an user exit for outbound IDoc. The user exit need to be coded to exclude a change pointer from processing if the key in CP contains a future dated record and that may get processed. This may get complex as you would like to send part of the changed record and not the other part of changed record. For example if you create a new IT0002 with future date, you would still want the current record which was delimited one day prior to future dated record.
It would be nice to have the target system handle this instead of handling it within SAP.
Regards
Ravikumar

IDOC data transfer SAP to Java using SAP JCo

Dear Experts,
The challenging requirement we are having is, we need to create the interface for data transfer between SAP system and the Java system. The data will be transferred from SAP to java and similarly once some processing done in Java again the details needs to be transferred from Java to SAP.
For this data transferred we are planning to use IDOC process and for interface "SAP Java connector" we are planning to use. In this case we are having some doubts.
1. The data from SAP is going to be transfered from one Custom transaction (Z tcode). Once "Outbound IDOC" will get triggered and will carry the details. Now the doubt is, whether the data / details will get transfered to JAVA system automatically or we need to perform any other steps from SAP ABAP coding...(like converting in to flat file, XML file and etc) ??
2. We are planning to install "SAP Jco" in Java server. Is this correct...??
3. Other than SAP Jco any other softwares needs to be installed or not..??
4. Since we are going to trigger the "outbound IDOC" from custom transaction, we are planning to develope one program in SE37. Other than this any other program we need to develop or not..??
If anybody has detailed steps or explanation please share it with us.
Warm Regards,
VEL

Hi All,
For the above mentioned issue, we implemented JCo software in JAVA system and created the JAVA program including SAP logon credential details like Client, User name, password and Language details.
When this JAVA program was compiled successfully then, that non SAP system will appear in SAP gateway Tcode.
Once non SAP system started appearing in SAP gateway that means, both SAP & Non SAP are connected automatically.
Regards,
Velmurugan P

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.

Rp-pppoe connected but no data transfer

hi,
i installed arch on 27th . Post installation i setup internet connection using rp-pppoe, which was a straight forward setup. I also got connected to net and downloaded data upon a system upgrade. Except this one instance, thereafter last two days if connected i am getting no data transfer after a connection is established.
Upon ping of 8.8.8.8 i am getting this error of destination net unreachable & if you ping google.com i get the error unknown host.
when i checked the pppoe status i get this message:
link is up and running on interface ppp0 and no packet errors both RX and TX.
The system upgrade did not happen on 27th due to the TZselec tconflicting files error.
It is a fresh system.
i am pasting below the lines from the messages.log of 27th when i got the data transfer happened for the first time and next of 29th with the same system but nothing happening except i am connected.
27th:
Jun 27 12:46:03 localhost kernel: [ 117.794497] r8169 0000:02:00.0: eth0: link up
Jun 27 12:46:06 localhost kernel: [ 120.763326] eth0: no IPv6 routers present
Jun 27 12:58:01 localhost kernel: [ 835.641169] PPP generic driver version 2.4.2
Jun 27 12:58:01 localhost pppd[888]: pppd 2.4.5 started by root, uid 0
Jun 27 12:58:01 localhost pppd[888]: Using interface ppp0
Jun 27 12:58:01 localhost pppd[888]: Connect: ppp0 <--> /dev/pts/0
Jun 27 12:58:02 localhost pppoe[889]: PADS: Service-Name: ''
Jun 27 12:58:02 localhost pppoe[889]: PPP session is 14295 (0x37d7)
Jun 27 12:58:02 localhost pppd[888]: CHAP authentication succeeded: CHAP authentication success, unit 7436
Jun 27 12:58:02 localhost pppd[888]: CHAP authentication succeeded
Jun 27 12:58:02 localhost kernel: [ 837.068606] PPP BSD Compression module registered
Jun 27 12:58:03 localhost pppd[888]: Cannot determine ethernet address for proxy ARP
Jun 27 12:58:03 localhost pppd[888]: local IP address 117.204.173.123
Jun 27 12:58:03 localhost pppd[888]: remote IP address 117.204.160.1
Jun 27 12:58:03 localhost pppd[888]: primary DNS address 218.248.255.212
Jun 27 12:58:03 localhost pppd[888]: secondary DNS address 218.248.241.2
Jun 27 13:01:01 localhost /USR/SBIN/CROND[934]: (root) CMD (run-parts /etc/cron.hourly)
Jun 27 13:01:01 localhost anacron[938]: Anacron started on 2012-06-27
Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.daily' in 28 min.
Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.weekly' in 48 min.
Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.monthly' in 68 min.
Jun 27 13:01:01 localhost anacron[938]: Jobs will be executed sequentially
Jun 27 13:04:10 localhost -- MARK --
Jun 27 13:16:48 localhost pppoe-stop: Killing pppd
Jun 27 13:16:48 localhost pppd[888]: Terminating on signal 15
Jun 27 13:16:48 localhost pppd[888]: Connect time 18.8 minutes.
Jun 27 13:16:48 localhost pppd[888]: Sent 411268 bytes, received 16885685 bytes.
29th :
Jun 29 17:54:13 localhost kernel: [ 5.019108] r8169 0000:02:00.0: eth0: link down
Jun 29 17:54:14 localhost dhcpcd[675]: eth0: carrier acquired
Jun 29 17:54:14 localhost kernel: [ 6.632983] r8169 0000:02:00.0: eth0: link up
Jun 29 17:54:14 localhost dhcpcd[675]: eth0: broadcasting for a lease
Jun 29 17:54:15 localhost dhcpcd[675]: eth0: offered 192.168.1.2 from 192.168.1.1
Jun 29 17:54:15 localhost dhcpcd[675]: eth0: acknowledged 192.168.1.2 from 192.168.1.1
Jun 29 17:54:15 localhost dhcpcd[675]: eth0: checking for 192.168.1.2
Jun 29 17:54:21 localhost dhcpcd[675]: eth0: leased 192.168.1.2 for 10080 seconds
Jun 29 17:54:21 localhost dhcpcd[675]: forked to background, child pid 702
Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) STARTUP (1.4.8)
Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) INFO (running with inotify support)
Jun 29 17:54:47 localhost kernel: [ 39.424170] NET: Registered protocol family 10
Jun 29 17:54:47 localhost kernel: [ 39.441086] NET: Registered protocol family 4
Jun 29 17:54:47 localhost kernel: [ 39.458946] NET: Registered protocol family 5
Jun 29 17:54:47 localhost kernel: [ 39.480053] PPP generic driver version 2.4.2
Jun 29 17:54:47 localhost pppd[811]: pppd 2.4.5 started by root, uid 0
Jun 29 17:54:47 localhost pppd[811]: Using interface ppp0
Jun 29 17:54:47 localhost pppd[811]: Connect: ppp0 <--> /dev/pts/0
Jun 29 17:54:48 localhost pppoe[812]: PADS: Service-Name: ''
Jun 29 17:54:48 localhost pppoe[812]: PPP session is 2021 (0x7e5)
Jun 29 17:54:48 localhost pppd[811]: CHAP authentication succeeded: CHAP authentication success, unit 4257
Jun 29 17:54:48 localhost pppd[811]: CHAP authentication succeeded
Jun 29 17:54:48 localhost kernel: [ 40.866233] PPP BSD Compression module registered
Jun 29 17:54:48 localhost pppd[811]: not replacing existing default route via 192.168.1.1
Jun 29 17:54:48 localhost pppd[811]: Cannot determine ethernet address for proxy ARP
Jun 29 17:54:48 localhost pppd[811]: local IP address 117.204.161.173
Jun 29 17:54:48 localhost pppd[811]: remote IP address 117.204.160.1
Jun 29 17:54:48 localhost pppd[811]: primary DNS address 218.248.255.212
Jun 29 17:54:48 localhost pppd[811]: secondary DNS address 218.248.241.2
Jun 29 17:54:57 localhost kernel: [ 49.523342] eth0: no IPv6 routers present
Jun 29 18:01:01 localhost /USR/SBIN/CROND[876]: (root) CMD (run-parts /etc/cron.hourly)
Jun 29 18:01:01 localhost anacron[881]: Anacron started on 2012-06-29
Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.daily' in 29 min.
Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.weekly' in 49 min.
Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.monthly' in 69 min.
Jun 29 18:01:01 localhost anacron[881]: Jobs will be executed sequentially
Jun 29 18:04:04 localhost pppoe-stop: Killing pppd
Jun 29 18:04:04 localhost pppd[811]: Terminating on signal 15
Jun 29 18:04:04 localhost pppd[811]: Connect time 9.3 minutes.
Jun 29 18:04:04 localhost pppd[811]: Sent 0 bytes, received 926 bytes.
Now in both the cases i got connected but as i said before except twice on 27th i am not able to have data transfer of any type either through ping or pacman upgrade.
Upon the same time i cross checked on my other systems, ubuntu and windows and i had no problems with the same, to confirm any issue with my isp. As of now i am typing one of those systems only.
I have googled a lot, read the other options of pppd,etc, but upon similar queries by other users found no viable solution to this problem.
My hostname is also proper in the config files. I also once used static ip for a change to see if things go working
but nothing is sucessful so far.
The only viable solution i read so far upon google search where there was a success was a fresh installation of arch by an user and he got the same working. But definitely i wont go with that. As i said above i got connected twice on the day of the installation and post that also i am now getting connected but with no data transfer.
Pls suggest what to do to get the connection working.
regards

Upon a search on the forums yesterday
i read one user query on this forums who was advised the same and he had the same problem like me and it did not got solved with either methodds.
Last his query was still open. I did not save that link.
So i did not give that method a try so far, waiting for a solution for this method without going for new developments thinking a search for a day or two might get some viable results.
i guess you are mentioning the topic of this link
https://wiki.archlinux.org/index.php/Pppd [This article explains how to set up a point-ti-point connections using pppd and the kernel PPPoE driver. ]
Further in my case the connection is happening and also getting disconnected. You can very well see the same in the log file which i pasted.
Jun 27 13:16:48 localhost pppd[888]: Connect time 18.8 minutes.
Jun 27 13:16:48 localhost pppd[888]: Sent 411268 bytes, received 16885685 bytes.
Jun 29 18:04:04 localhost pppd[811]: Connect time 9.3 minutes.
Jun 29 18:04:04 localhost pppd[811]: Sent 0 bytes, received 926 bytes.
So same thing but different results on 2 different days. So what the problem really is i dont understand. Infact what the problem is the system is also not giving out, except that a connection happens, no data transfer takes place and the connection is cut and the stats are also show. Just diving to implement some new method or a reinstall, without resolving this which looks sensible yet senseless too, simply does not appeal here. If really there is some bug or issue with that rp-pppoe package then there is some point to jump to another method.
This must be solvable some way or other.
Last edited by beopen (2012-06-29 17:30:16)

Field symbols not working in data transfer VOFM routine

Hi,
I have been trying to set a value using field symbols, however for some reasons its not working. I am using a field symbol in a data transfer routine and the value which I am trying to set is a standard field outside the VOFM routine code.
I am trying to set a field gla_subrc which is actually a changing parameter.
The actual paramter is gn_subrc of type sy-subrc and within the form the name is gla_subrc. I need to set this changing parameter gla_subrc using the data transfer routine.
Is there a specific rule that field symbols dont work for changing paramters within subroutine or is there a specific syntax.
The syntax I am using is
ASSIGN ('(SAPLV50S)gla_subrc') to <fs>.
I also used the local program name instead of main program but still that does not work. Tried using the actual parameter as well.
Can someone please help me in this.
Thanks & Regards,
Naresh.

I need to stop outbound delivery creation against STO using vl10b transaction. The only way to stop creation is using data transfer delivery VOFM routine.
If i give an error message MESSAGE E001, this will give a hard error which is not acceptable. To avoid this, i use a perform message statment with message id and certain parameters which can displayed in a log.
However to make sure this message is displayed in log, I am clearing a work area having specific data needed for delivery creation.
Because of this clear, my error message gets captured in log but along with this another fake message is displayed in log which caused by the clear message.
The user gets confused as he now sees 2 messages, 1 which is correct and other 1 which is fake and that confuses him.
Data transfer routine is not the best place to give messages in log but we have very few options. The only way the system can give 1 message is if i set gla_subrc to 1. This is a variable which will help the system understand that the delivery should not be created as there is something wrong because the value is 1. Hence it will stop the creation and instead display whatever message i had passed to the log.
I need to somehow set this variable to 1 based on lot of analysis that has been done in the past.
Please let me know if there is any way by which we can fix this.
Thanks & Regards,
Naresh.

Data Transfer Betw 8i's 0040, ODBC, or OLE DB Drivers & XML

I have researched that Oracle has 3 database drivers for
accessing Windows NT data - they are Oracle 8i's: 0040, ODBC
Driver, and OLE DB drivers. Do these drivers allow data
transfer between XML and Oracle 8i?
null

Donnell Brockenbrough (guest) wrote:
: I have researched that Oracle has 3 database drivers for
: accessing Windows NT data - they are Oracle 8i's: 0040, ODBC
: Driver, and OLE DB drivers. Do these drivers allow data
: transfer between XML and Oracle 8i?
Here are the details I have:
1. XML Support in OO4O:
The next major release of OO4O will allow query result sets to
be rendered as XML documents. Query result sets can also be
accessed, and data can be inserted or updated via a COM/DCOM
implementation of DOM interfaces. XML support in OO4O will cover
both Relational as well as Object-Relational data bases. OO4O
will also include a COM/DCOM implementation of the Oracle XML
Parser.
2. XML support in ODBC or OLE DB
Since the ODBC or OLE DB specifications are comntrolled by
Micosoft, they will be the vender to contact regarding XML
support for these interfaces.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

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

Data Transfer Workbench can copy sales & purchase modules's data?

Hi,
Just wondering that,any way to copy the Sales & Purchase Modules's data from existing company to new company? Copy Express can't do it. But how about Data Transfer Workbench can copy?
Thanks
Regards,
Danny
Edited by: Danny Gan on Mar 18, 2008 5:21 AM

Danny,
How many field from the ORDR or RDR1 have to exported depends on the business logic implemented and what was being used. No one can really provide a standard set of 5 or 10 fields as you know the clients business better than anyone in the Forum.
If the Client used User fields then data from the user fields should also be exported.
The base fields from ORDR would be CardCode, DocDate, DocDueDate, Transpcode (shipping code), SlpCode, GroupNum (Payment terms code), etc.
Similarly on RDR1, ItemCode, Quantity, Price and any additional row level information that may pertain to their business
Suda

Data transfer position for candidate

Hi Experts,
We are implementing ECC 6, E Recruiting. When we do data transfer activity for a candidate then we want to pull the position on which data transfer activity was done for candidate in a Z Report.
Can any one tell me in which info type position is stored for a candidate at which data transfer activity is done or it is not stored at all any where in data base.
Regards
Puneet

data is always stored anywhere, how would the system know what to show otherwise?
http://www.nicx.co.uk/attachments/File/Data%20Model%20&%20Infotypes.pdf

Implementation of outbound data transfer

Similar Messages

Maybe you are looking for