✒️ABAP Los módulos de funciones RFC
ABAP Los módulos de funciones RFC
RFC – Remote Function Call
A Remote Function Call (RFC) involves invoking a function that exists in a system different from the one running the calling program. The primary goal of RFC is to access other environments to retrieve data. Communication between different systems in the SAP environment includes connections between SAP systems as well as between SAP and non-SAP systems. When declaring an RFC function, it's essential to include the "DESTINATION" clause, utilized in RFC function module declarations to specify an RFC destination.
Example of when to use an RFC function module:
Reading a customer data record from the DTR(Design Time Repository) system by an existing ABAP program in the DCR environment requires creating an RFC function module in the DTR environment that returns customer records.
* Function created in DTR env
FUNCTION ZGET_CUSTOMERS.
"Read the customer record.
ENDFUNCTION.
In the DCR environment, call the RFC function module:
* Calling the function in the other System
CALL FUNCTION 'ZGET_CUSTOMERS'
DESTINATION V_DCR
EXPORTING KUNNR = V_CLIENT
TABLES CUSTOMER = TI_CUSTOMERS
EXCEPTIONS NO_RECORD_FOUND = 01.
In case of an error during RFC execution, error messages are returned by the remote system and stored in the variables SY-MSGID, SY-MSGTY, SY-MSGNO, SY-MSGV1 (V2) (V3) (V4).
Creating an RFC Function Module
Creating an RFC function module follows the same process as regular function modules.
- Access transaction SE37.
- Fill in the parameters required for creating a function module, but select the "Remote-enabled module" option in the Attributes tab.
- Parameters in an RFC function module cannot be passed by reference; they must be passed by value. Enable the "Transport values" checkbox for each parameter in the IMPORT, EXPORT, and CHANGING tabs.
RFC-enabled functions can be used as regular function modules in two ways:
- Using the declaration CALL FUNCTION DESTINATION 'NONE'
- Using the declaration of a normal function module without adding the DESTINATION clause.
Types of RFC Function Modules
There are three types:
- Synchronous: Both systems must be available at the time of the function call (synchronous communication).
- Transactional: Systems don't need to be available at the time of the function call. To create them, use the suffix "IN BACKGROUND TASK" in the declaration. Note: The system logs the remote call request in the SAP standard tables ARFCSSTATE and ARFCSDATA with all parameter values. To view this log, use transaction SM58. The RFC execution triggers the COMMIT WORK statement.
- Asynchronous: The calling program invokes the RFC function and immediately finishes its processing. To create them, use the suffix "STARTING NEW TASK" in the declaration.
E.g
DATA: ti_account TYPE STANDARD TABLE OF zsuaccountw_ov,
ti_det_xblnr TYPE STANDARD TABLE OF zsudetxblnr,
v_vkont LIKE fkkvkp-vkont,
v_destino(9) TYPE c,
v_taskname(9) TYPE c.
*---------------------------------------------------------------------*
START-OF-SELECTION.
*---------------------------------------------------------------------*
CLEAR v_destino.
* Select the destination - Depends on the client
IF sy-sysid(3) EQ 'LD0'. " DEV
v_destino = 'BD3ARG110'.
ELSEIF sy-sysid(3) EQ 'LK0'. " QA
v_destino = 'BK3ARG311'.
ELSEIF sy-sysid(3) EQ 'LP0'. " Prod
v_destino = 'BP3ARG311'.
ENDIF.
* Synchronous RFC example
CALL FUNCTION 'Z_OV_RFC_ESTADO_DEUDA'
DESTINATION v_destino
EXPORTING
i_vkont = v_vkont
i_fecha_int = sy-datum
TABLES
t_account = ti_account
t_det_xblnr = ti_det_xblnr.
* RFC being used as regular function modules
CALL FUNCTION 'Z_OV_RFC_ESTADO_DEUDA'
DESTINATION 'NONE'
EXPORTING
i_vkont = v_vkont
i_fecha_int = sy-datum
TABLES
t_account = ti_account
t_det_xblnr = ti_det_xblnr.
* Transactional RFC example
CALL FUNCTION 'Z_OV_RFC_ESTADO_DEUDA' IN BACKGROUND TASK
DESTINATION v_destino
EXPORTING
i_vkont = v_vkont
i_fecha_int = sy-datum
TABLES
t_account = ti_account
t_det_xblnr = ti_det_xblnr.
* Asynchronous RFC example
CALL FUNCTION 'Z_OV_RFC_ESTADO_DEUDA' STARTING NEW TASK v_taskname
DESTINATION v_destino
EXPORTING
i_vkont = v_vkont
i_fecha_int = sy-datum
TABLES
t_account = ti_account
t_det_xblnr = ti_det_xblnr.
Sobre el autor
Publicación académica de Jaime Eduardo Gomez Arango, en su ámbito de estudios para la Carrera Consultor ABAP.
SAP Master
Jaime Eduardo Gomez Arango
Profesión: Ingeniero de Sistemas y Computación - España - Legajo: SW34C
✒️Autor de: 99 Publicaciones Académicas
🎓Cursando Actualmente: Consultor ABAP Nivel Avanzado
🎓Egresado del módulo:
Disponibilidad Laboral: FullTime
Presentación:
Ingeniero de sistemas y computación con 8 años de experiencia el desarrollo frontend & backend (react/node) y en cloud (aws), actualmente desarrollando habilidades en sap btp, ui5, abap y fiori.
Certificación Académica de Jaime Gomez
