SAP XI - ABAP Proxy Communication Client Proxy

ABAP Proxy Proxy Communication (Client (Client Proxy)

SAP XI Scenario Scenari o ABAP Proxy Proxy Communication (Client (Client Proxy) Brought to you by

For more tips, tutorials, Interview questions, certification questions, please visit SAPTechnical.com

ABAP Proxy Proxy Communication (Client (Client Proxy) By Neeraja Surapaneni, YASH Technologies This document is focused to give a better understanding understanding on ABAP client proxies. From WAS 6.20 onwards, proxy generation feature enables application systems to communicate with XI using proxies. Proxy objects implement message interfaces from Integration Repository. Proxy generation converts non-language-specific interface descriptions in WSDL into executable interfaces in the application system. Proxies separate Business Application logic from the integration logic of the Exchange infrastructure i nfrastructure.. There are 2 types of proxies av ailable. 1.

Java Proxies 2. ABAP Proxies. 1. Java Proxies: Proxies : - Java proxies are used when JAVA applications needs to send or receive messages with other applications. JAVA proxies are generated from the WSDL description of the interface in the Integration Repository, and the result is a .jar file containing generated java classes corresponding to the integration objects. 2. ABAP Proxies: Proxies : - ABAP proxies are used when ABAP applications needs to send or receive messages. ABAP proxies are generated on the Application server with transaction SPROXY, based on the WSDL representation of the message interface. The type of the message interface determines what type of proxy is generated. The counterparts to outbound message interface in application systems are client proxies , these are called to send a message to inbound interface. And the counterparts of inbound message interface in application systems are server server proxies. proxies . Advantages of ABAP Proxies. 1.

Proxy communication always by passes the Adapter Engine and will directly interact with the application system system and Integration engine. So it will give us better performance. 2. Proxies communicate with the XI server by means of native SOAP calls over HTTP. 3. Easy to handle messages with ABAP programming. 4. Proxy is good for large volumes of data. we can catch and persist the errors ( both system & application fault ) which was generated by Proxy setting The rest of the document gives you pre-requisites and steps that are necessary for generating and executing ABAP client proxies. Pre-requisites 1.

The business systems should be based on SAP Web AS 6.20 and SAP Web AS 6.20 kernel patch level above 1253 2. You have installed the XI Add-On in each of these business systems as described in the Installation Guide SAP Ex change Infrastructure Infrastructure 3.0 3. The business systems and your central Integration Server are maintained in the System Landscape Directory (SLD).


ABAP Proxy Proxy Communication (Client (Client Proxy) Steps req uired for for developing developing ABAP ABAP Pr oxies oxies •

• • •

• • • • •

Establish the connection between WAS and Integration Builder, this allows the application system to retrieve WSDL description of the interface as the basis of proxy generation. Create a source data type and a target data type. Create Message types for the source and target data types. Create Message Interfaces includes Inbound Message interface and Outbound Message interface. Create message mapping between the source and target message types. Create Interface mapping. m apping. Create ABAP proxies using the transaction SPROXY in the application system. Create Collaboration agreements agreements and Collaboration Collaboration profiles profil es in Integration directory. Write a program in the application system for creating c reating the client proxy request.

Scenar Scenar io demonstr demonstr ating ABAP Client Pr oxies. oxies.

Take a business scenario where in business (Source System) sends an Employee details to their Payroll system for calculating the monthly salaries of their employees. But here the source business is running on SAP R/3 and corresponding Payroll system is not on SAP, hence the interpretation of data/communication is different. Because source system sends employee information through proxy communication and the target Payroll system is not aware of these proxy call, so in order to provide a communication between these two we need some interface mechanism which accepts proxy request and converts it into the format understandab understandable le by the target payroll system and v ice versa. v ersa.

Obj ects needed to be developed developed in IR

For this scenario we need to create the corresponding Data types, Message types and Message interfaces for source and target messages. Once the source Message interface is created we can generate the interface in source R/3 system using SPROXY transaction.







In this demo scenario, there is slight variance in source and target messages. From the source we will get First name and last name where as target will accommodate only one full name and also source will send the annual salary whereas target will have the field Monthly salary. Hence required mapping should be done.



Save it.


ABAP Proxy Proxy Communication (Client (Client Proxy) Now activate all the objects that are developed in IR. Before starting the configurations in the Integration directory, let us complete the creation of client proxies in source R/3 system. Cr eating ABAP Pr oxies oxies in Application system system

Go to SPROXY transaction in R/3 system. Here we can see all the Integration Repository objects. Select the outbound interface for which we want to create the proxy. Right click on the interface and select create option.

ABAP proxy will generate generate the following f ollowing objects. objects.



We can observe the Structures resembling outbound data types, message types get created in the system. As the source structure can send multiple records of Employee, observe that a Table type of ZTDT_EMPDET_OB_EMPLOYEE_TAB getting created. This can be transferred to FTP.


ABAP Proxy Proxy Communication (Client (Client Proxy) Activate the generated generated proxy. For creating ABAP client proxy request we need to call the execute_asynchronous method of this class. This method will take the input as of type ZTMT_EMPDET_OB. ZTMT_EMPDET_OB . To fill the employee details we need to create the structure of type ZTDT_EMPDET_OB_EMPLOYEE and table of type ZTDT_EMPDET_OB_EMPLOYEE_TAB . After filling fi lling the internal table finally we need to move this to ZTMT_EMPDET_OB- MT_EMPDET_OB-EMPLOYEE Obj ects that n eed to be developed developed in ID

First we need to create communication channels for sender and receiver. Here it is not required to create sender communication channel as we are using proxies in the sender side for communication. comm unication. We need to create Receiver communication channel channel to place the file with employee details in the FTP server.


ABAP Proxy Proxy Communication (Client (Client Proxy) The next step in the Integration directory is we need to create Sender agreement, receiver agreement, interface determination and Receiver determination. But in our scenario it is not required to create sender agreement.



Testing the Scenar io.

In order to test the scenario we need to develop an ABAP Report to trigger a client proxy. The following report is executed in the SE38 Editor for triggering an ABAP Proxy. *&--------------------------------------------------------------------* *& Report Z_SEND_EMP_DETAILS *& *&--------------------------------------------------------------------* *& Published at SAPTechnical.com *& *&--------------------------------------------------------------------* REPORT Z_SEND_EMP_DETAILS. TABLES: PA0001. DATA: PRXY TYPE REF TO ZTCO_MI_EMPDET_OB, FS_EMPLOYEE TYPE ZTDT_EMPDET_OB_EMPLOYEE, T_EMPLOYEE TYPE ZTDT_EMPDET_OB_EMPLOYEE_TAB, FS_EMPLOYEE_MT TYPE ZTMT_EMPDET_OB. DATA: BEGIN OF I_PA0000 OCCURS 0, PERNR LIKE PA0000-PERNR, MASSN LIKE PA0000-MASSN, END OF I_PA0000, BEGIN OF I_PA0001 OCCURS 0, PERNR LIKE PA0000-PERNR, WERKS LIKE PA0001-WERKS, " Personnel Area PERSG LIKE PA0001-PERSG, " Employee Group PERSK LIKE PA0001-PERSK, " Employee Subgroup BTRTL LIKE PA0001-BTRTL, " Personnel Subarea


ABAP Proxy Proxy Communication (Client (Client Proxy) ABKRS LIKE PA0001-ABKRS, KOSTL LIKE PA0001-KOSTL, ORGEH LIKE PA0001-ORGEH, PLANS LIKE PA0001-PLANS, END OF I_PA0001, BEGIN OF I_PA0002 OCCURS 0, PERNR LIKE PA0000-PERNR, NACHN LIKE PA0002-NACHN, VORNA LIKE PA0002-VORNA, GESCH LIKE PA0002-GESCH, GBDAT LIKE PA0002-GBDAT, END OF I_PA0002, BEGIN OF I_PA0007 OCCURS 0, PERNR LIKE PA0000-PERNR, SCHKZ LIKE PA0007-SCHKZ, ARBST LIKE PA0007-ARBST, END OF I_PA0007, BEGIN OF I_PA0008 OCCURS 0, PERNR LIKE PA0000-PERNR, TRFAR LIKE PA0008-TRFAR, TRFGB LIKE PA0008-TRFGB, TRFGR LIKE PA0008-TRFGR, TRFST LIKE PA0008-TRFST, STVOR LIKE PA0008-STVOR, WAERS LIKE PA0008-WAERS, ANSAL LIKE PA0008-ANSAL, LGA01 LIKE PA0008-LGA01, BET01 LIKE PA0008-BET01, ANZ01 LIKE PA0008-ANZ01, LGA02 LIKE PA0008-LGA02, BET02 LIKE PA0008-BET02, ANZ02 LIKE PA0008-ANZ02, LGA03 LIKE PA0008-LGA03, BET03 LIKE PA0008-BET03, ANZ03 LIKE PA0008-ANZ03, END OF I_PA0008, BEGIN OF I_PA0009 OCCURS 0, PERNR LIKE PA0000-PERNR, ZLSCH LIKE PA0009-ZLSCH, BANKS LIKE PA0009-BANKS, BANKL LIKE PA0009-BANKL, BANKN LIKE PA0009-BANKN, BKONT LIKE PA0009-BKONT, END OF I_PA0009. TRY. CREATE OBJECT PRXY. ENDTRY. SELECT-OPTIONS: S_PERNR FOR PA0001-PERNR. START-OF-SELECTION. SELECT PERNR MASSN FROM PA0000 INTO TABLE I_PA0000 WHERE PERNR IN S_PERNR AND ENDDA GE SY-DATUM AND BEGDA LE SY-DATUM

" " " "

Payroll Area Cost Center Organizational Unit Position

" " " "

Last Name First Name Gender Key Date of Birth

" Work Schedule Rule " Daily Working Hours

" " " " " " " " " " " " " " " "

Pay scale type Pay Scale Area Pay Scale Group Pay Scale Level Date of Next Increase Currency Key Annual salary Wage Type Wage Type Amount for Payments Number Wage Type Wage Type Amount for Payments Number Wage Type Wage Type Amount for Payments Number

" " " " "

Payment Method Bank country key Bank Keys Bank account number Bank Control Key

" Personnel number


ABAP Proxy Proxy Communication (Client (Client Proxy) AND STAT2 EQ '3'. SELECT PERNR WERKS PERSG PERSK BTRTL ABKRS KOSTL ORGEH PLANS FROM PA0001 INTO TABLE I_PA0001 WHERE PERNR IN S_PERNR AND ENDDA GE SY-DATUM AND BEGDA LE SY-DATUM. SELECT PERNR NACHN VORNA GESCH GBDAT FROM PA0002 INTO TABLE I_PA0002 WHERE PERNR IN S_PERNR AND ENDDA GE SY-DATUM AND BEGDA LE SY-DATUM. SELECT PERNR SCHKZ ARBST FROM PA0007 INTO TABLE I_PA0007 WHERE PERNR IN S_PERNR AND ENDDA GE SY-DATUM AND BEGDA LE SY-DATUM. SELECT PERNR TRFAR TRFGB TRFGR TRFST STVOR WAERS ANSAL LGA01 BET01 ANZ01 LGA02 BET02 ANZ02 LGA03 BET03 ANZ03 FROM PA0008 INTO TABLE I_PA0008 WHERE PERNR IN S_PERNR AND ENDDA GE SY-DATUM AND BEGDA LE SY-DATUM. SELECT PERNR ZLSCH

" " " " " " " " "

Personnel number Personnel Area Employee Group Employee Subgroup Personnel Subarea Payroll Area Cost Center Organizational Unit Position

" " " " "

Personnel number Last Name First Name Gender Key Date of Birth

" Personnel number " Work Schedule Rule " Daily Working Hours

" " " " " " " " " " " " " " " " "

Personnel number Pay scale type Pay Scale Area Pay Scale Group Pay Scale Level Date of Next Increase Currency Key Annual salary Wage Type Wage Type Amount for Payments Number Wage Type Wage Type Amount for Payments Number Wage Type Wage Type Amount for Payments Number

" Personnel number " Payment Method


ABAP Proxy Proxy Communication (Client (Client Proxy) BANKS " Bank country key BANKL " Bank Keys BANKN " Bank account number BKONT " Bank Control Key FROM PA0009 INTO TABLE I_PA0009 WHERE PERNR IN S_PERNR AND ENDDA GE SY-DATUM AND BEGDA LE SY-DATUM. SORT: I_PA0000 BY PERNR, I_PA0001 BY PERNR, I_PA0002 BY PERNR, I_PA0007 BY PERNR, I_PA0008 BY PERNR. REFRESH T_EMPLOYEE. LOOP AT I_PA0000. CLEAR FS_EMPLOYEE. FS_EMPLOYEE-PERSONNEL_NUMBER = I_PA0000-PERNR. FS_EMPLOYEE-ACTION_TYPE = I_PA0000-MASSN. READ TABLE I_PA0001 WITH KEY PERNR = I_PA0000-PERNR BINARY IF SY-SUBRC EQ 0. FS_EMPLOYEE-EMP_GROUP = I_PA0001-PERSG. FS_EMPLOYEE-EMP_SUBGROUP = I_PA0001-PERSK. FS_EMPLOYEE-PERSONNEL_SUBAREA = I_PA0001-BTRTL. FS_EMPLOYEE-PAYROLL_AREA = I_PA0001-ABKRS. FS_EMPLOYEE-COST_CENTER = I_PA0001-KOSTL. FS_EMPLOYEE-ORGANIZATIONAL_UNIT = I_PA0001-ORGEH. FS_EMPLOYEE-POSITION = I_PA0001-PLANS. ENDIF. READ TABLE I_PA0002 WITH KEY PERNR = I_PA0000-PERNR BINARY IF SY-SUBRC EQ 0. FS_EMPLOYEE-LASTNAME = I_PA0002-NACHN. FS_EMPLOYEE-FIRST_NAME = I_PA0002-VORNA. FS_EMPLOYEE-GENDER = I_PA0002-GESCH. FS_EMPLOYEE-DOB = I_PA0002-GBDAT. ENDIF. READ TABLE I_PA0007 WITH KEY PERNR = I_PA0000-PERNR BINARY IF SY-SUBRC EQ 0. FS_EMPLOYEE-WORK_SCHEDULE_RULE = I_PA0007-SCHKZ. FS_EMPLOYEE-DAILY_WORKING_HOURS = I_PA0007-ARBST. ENDIF. READ TABLE I_PA0008 WITH KEY PERNR = I_PA0000-PERNR BINARY IF SY-SUBRC EQ 0. FS_EMPLOYEE-PAY_SCALE_TYPE = I_PA0008-TRFAR. FS_EMPLOYEE-PAY_SCALE_AREA = I_PA0008-TRFGB. FS_EMPLOYEE-PAY_SCALE_GROUP = I_PA0008-TRFGR. FS_EMPLOYEE-PAY_SCALE_LEVEL = I_PA0008-TRFST. FS_EMPLOYEE-INCREASE_DATE = I_PA0008-STVOR. FS_EMPLOYEE-CURRENCY = I_PA0008-WAERS. FS_EMPLOYEE-ANNUAL_SALARY = I_PA0008-ANSAL. FS_EMPLOYEE-WAGE_TYPE1 = I_PA0008-LGA01. FS_EMPLOYEE-AMOUNT1 = I_PA0008-BET01. FS_EMPLOYEE-NUMBER1 = I_PA0008-ANZ01. FS_EMPLOYEE-WAGE_TYPE2 = I_PA0008-LGA02. FS_EMPLOYEE-AMOUNT2 = I_PA0008-BET02. FS_EMPLOYEE-NUMBER2 = I_PA0008-ANZ02. FS_EMPLOYEE-WAGE_TYPE3 = I_PA0008-LGA03.

SEARCH.

SEARCH.

SEARCH.

SEARCH.


ABAP Proxy Proxy Communication (Client (Client Proxy) FS_EMPLOYEE-AMOUNT3 = I_PA0008-BET03. FS_EMPLOYEE-NUMBER3 = I_PA0008-ANZ03. ENDIF. READ TABLE I_PA0009 WITH KEY PERNR = I_PA0000-PERNR BINARY SEARCH. IF SY-SUBRC EQ 0. FS_EMPLOYEE-PAYMENT_METHOD = I_PA0009-ZLSCH. FS_EMPLOYEE-BANK_COUNTRY = I_PA0009-BANKS. FS_EMPLOYEE-BANK_KEYS = I_PA0009-BANKL. FS_EMPLOYEE-BANK_ACCOUNT_NUMBER = I_PA0009-BANKN. FS_EMPLOYEE-BANK_CONTROL_KEY = I_PA0009-BKONT. ENDIF. APPEND FS_EMPLOYEE TO T_EMPLOYEE. ENDLOOP. TRY. FS_EMPLOYEE_MT-MT_EMPDET_OB-EMPLOYEE = T_EMPLOYEE. CALL METHOD PRXY->EXECUTE_ASYNCHRONOUS EXPORTING OUTPUT = FS_EMPLOYEE_MT. COMMIT WORK . CATCH CX_AI_SYSTEM_FAULT . DATA FAULT TYPE REF TO CX_AI_SYSTEM_FAULT . CREATE OBJECT FAULT. WRITE :/ FAULT->ERRORTEXT. ENDTRY. When this report is executed, we can see the file in the FTP server with the employee details. - - 00001002 52 1 DT D2 0000002100 50000563 50000083 Ulrike Zaucker 2 19600905 FLEX 7.50 40 02 AT 00000000 EUR 0 MA90 4601.63 0.00


ABAP Proxy Proxy Communication (Client (Client Proxy) 0.00 0.00 0.00 0.00 U DE 23984899 253571587

Please visit SAPTechnical.com for more scenarios on XI: • • • • • • • • • • • •

XSLT Mapping IDOC-to-IDOC Scenario File-to-File Scenario with SLD and Monitoring Status Publishing Interface Interface as Web Service (Web Service to RFC Scenario) Monitoring of XML Message Queues in the R/3 system ABAP Proxy communication Scenario (Server Proxy) RFC-to-Web Service Scenario IDoc-to-File Scenario How-to-do Alert Configuration in XI Time Bound File Processing - File to IDoc Scenario Collect Multiple IDOCs to File Fi le using BPM Useful information regarding SAP XI


SAP XI - ABAP Proxy Communication Client Proxy

Recommend Documents