Extraction program for EH&S (EH&S to XI scenario)

[Former Member]

Dear Experts,

I would like to know whether there exists an extraction program to extract substance data from EH&S(ECC) and send it to XI. If yes then what is it? The EH&S team here doesn't know of any kind. They have only used Change pointers to extract data from one client to the another.

Please help.

Thanks,

Merrilly

[Former Member]

HI

Proxy is a better option for extracting data from ECC to XI. As it allow you to build even business logic to extract data as per requirement. Performace wise also it is better than IDOCs

Regards

Gauarv Bhargava

[Former Member]

Hi,

Problem: I would like to know whether there exists an extraction program to extract substance data from EH&S(ECC) and send it to XI. If yes then what is it?

Solution: For the same you can use outbound proxy. First you need to configure and activate the proxy in R/3.

First of all something about Proxy:

1. Proxies can be a server proxy (Inbount Proxy) or client proxy (Outbound Proxy). In our scenarios we require proxies to send or upload the data from/into SAP system.

2. One more thing proxies can be used if your WAS ≥ 6.2.

3. Use Tcode SPROXY into R/3 system for proxy use.

4. To send the data from R/3 system we use OUTBOUND PROXY. In Outbound proxy you will simply write an abap code to fetch the data from R/3 tables and then send it to XI. Below is the sample code to send the data from R/3 to XI.

REPORT zblog_abap_proxy.

DATA prxy TYPE REF TO zblogco_proxy_interface_ob.

*

CREATE OBJECT prxy.

DATA it TYPE zblogemp_profile_msg.

TRY.

it-emp_profile_msg-emp_name = 'Sarvesh'.

it-emp_profile_msg-empno = '01212'.

it-emp_profile_msg-DEPARTMENT_NAME = 'NetWeaver'.

CALL METHOD prxy->execute_asynchronous

EXPORTING

output = it.

commit work.

CATCH cx_ai_system_fault .

DATA fault TYPE REF TO cx_ai_system_fault .

CREATE OBJECT fault.

WRITE 😕 fault->errortext.

ENDTRY.

Receiver adapter configurations should be done in the integration directory and the necessary sender/receiver binding should be appropriately configured. We need not do any sender adapter configurations as we are using proxies.

5. To receive data into R/3 system we use INBOUND PROXY. In this case data is picked up by XI and send it to R/3 system via XI adapter into proxy class. Inside the inbound proxy we careate an internal table to take the data from XI and then simply by using the ABAP code we update the data inot R/3 table. BAPI can also be used inside the proxy to update the data into r/3.

I hope this will give some idea about proxy.

Now, use below mentioned steps one by one:

Step1: How to Activate Proxy.

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

Step2: How to create proxy.

http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm

Examples:

OutBound Proxy (Client Proxy)

/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies

Outbound Proxy (Client Proxy)

/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy

ABAP Server Proxies (Inbound Proxy)

/people/siva.maranani/blog/2005/04/03/abap-server-proxies

Regards,

Sarvesh

[Former Member]

Hi Sarvesh,

Thank you for your Information. Are proxies the only way to do this. I think the team here is using IDOCs to send the data. Specifically SUBMAS02. In that case is there another extraction method?

Thanks and regards,

Merrilly

[Former Member]

Well, IDocs are the best option to be used if you have. In similar way you can alos use RFCs, but in case if you have to go for custom design of IDocs & RFC then proxy will be better option rather than creating the custom IDocs & RFCs.