SAP NEWS-71-RFC



Get Example source ABAP code based on a different SAP table
  



Remote Function Call in ABAP Release 7.0, EhP2
ITOC

ABAP_MODIFICATION_NN Background RFC

With the new Background RFC (bgRFC) Remote Function Calls can be carried out safely in a transaction and in the call sequence. The calling application and the called application are connected asynchronously. bgRFC replaces the functions previously provided by tRFC and qRFC (but not qRFC <(>no-Send<)>).



Latest notes:

This modification was also added to ABAP_RELEASE 7.0 in SP14.
ABAP_HINT_END

ABAP_MODIFICATION_NN Local Data Queue

The Local Data Queue (LDQ) is a persistence layer into which data can be placed. This data can only be read in the order that it is recorded in. This involves separation of data recording from data retrieval by the receiver like in an inbox. Since the access order is defined according to the First-In First-Out (<(>FIFO<)>) principle, queues are used as the organizational element for the individual receivers. The LDQ replaces the functions previously provided by the <(>qRFC No-Send<)> scenario.

ABAP_MODIFICATION_NN SAP RFC SDK

The new SAP RFC SDK replaces the classic RFC SDK. It supports a revised API that can be used like the SAP Java Connector.

ABAP_MODIFICATION_NN RFC Connectivity in SAP Java Enterprise Edition (Java <(>EE<)>)

For the SAP Java Enterprise Edition (Java <(>EE<)>), the SAP Java Resource Adapter (SAP JRA) for SAP JCo is provided. It provides connections to resources in accordance with <(>JCA 1.5 SAP JCo<)>.

ABAP_MODIFICATION_NN basXML as New RFC Protocol

The basXML format is supported as the new standard RFC protocol and replaces the previous formats.

ABAP_MODIFICATION_NN Identification of Trusted Systems

In transaction SMT1 for editing RFC trust relationships, the installation number is now also used when creating trusted systems by entering the system ID (name of the AS ABAP). This applies to all trusted systems from ABAP releases 7.02, EhP2 and 7.2 (including 7.1).
When creating a trusted relationship from ABAP_RELEASE 7.0, EhP2, the trusting system checks the installation number of the calling system, if it is specified in transaction SMT1. For trust relationships of this kind, the relevant authorizations need to be modified so that field RFC_INFO in authorization object S_RFCACL contains the installation number of the calling system.