Skip to content

Source: RFC

Nuno Godinho edited this page May 20, 2019 · 1 revision

The RFC source type is somewhat special because it doesn't only determine the provenience of the data. It also determines its format: XML.

Using the RFC source type one SAP system can fetch constants from a different remote SAP system, as long as there is an RFC Connection string properly customized and abaK is also installed there and has the requested constants centrally customized in its ZABAK table.

This source type needs two parameters:

  • ID of the remote system's ZABAK constants registry;
  • RFC Destination of the remote system.

As explained above, it must always be used together with format XML.

How to use it

1. Defined in the local system's ZABAK:

ID NAME FORMAT_TYPE CONTENT_TYPE CONTENT
REMOTE1 Remote system constants XML DB REMOTE_ID REMOTE_RFCDEST

To instantiate it just do this:

DATA: o_abak TYPE REF TO zif_abak.
o_abak = zcl_abak_factory=>get_zbak_instance( 'REMOTE1' ).

Consider caching it in Shared Memory

If it is often used, this is one of those cases in which it may make sense to set the ZABAK-USE_SHM flag to X so that the remote contents are stored in Shared Memory and don't have to be constantly fetched from the remote system.

2. Explicitly

This way you won't need to register it in the local system although it will always have to be registered in the remote system's ZABAK:

DATA: o_abak TYPE REF TO zif_abak.
o_abao = zcl_abak_factory=>get_instance(
           i_format_type = 'XML'
           i_source_type = 'RFC'
           i_content     = 'REMOTE_ID REMOTE_RFCDEST' ).

abaK will automatically fetch the constants from the remote system.

Clone this wiki locally