Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

ABAPCALL_FUNCTION_BACKGROUND_UNIT - CALL FUNCTION BACKGROUND UNIT

ABAPCALL_FUNCTION_BACKGROUND_UNIT - CALL FUNCTION BACKGROUND UNIT

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

CALL FUNCTION IN BACKGROUND UNIT

Short Reference



CALL FUNCTION func IN BACKGROUND UNIT oref
parameter_list.

Effect

Background Remote Function Call (bgRFC) of a remote-enabled function module specified in func using the RFC interface. Here, oref is an object reference variable that must point to an object whose class implements the interface IF_BGRFC_UNIT.

The object contains all the information required for the Remote Function Call, including the destination, whether to execute a transactional or queued call and, if required, the quantity of queues. If the same object is used for multiple calls, all called function modules are executed in one unit. Conversely, multiple objects of this type can be used in parallel in one internal session, which enables parallel processing.

Parallel processing is executed if queues or destinations in the used objects have different names. If, in consecutive calls, different objects are used for which the same queues and destinations are specified, they are executed in the same queue one after the other.

Note

Background RFC (bgRFC) is the enhanced successor technology of transactional RFC (tRFC) and makes this technology obsolete. It is strongly recommended to use bgRFC instead of tRFC.

More Information

For more information about bgRFC, see the documentation RFC in SAP Help Portal.

Notes

  • Before the introduction of bgRFC, the parallel processing of multiple function modules was only possible using the addition AS SEPARATE UNIT of the statement CALL FUNCTION IN BACKGROUND TASK. This same functionality is provided by the parallel use of multiple objects, which means this addition is no longer necessary.
  • If, within the same SAP LUW, bgRFC units and updates are executed, the bgRFC units are dependent on the update. Only after the update has been processed can the associated bgRFC processed. When an incorrect update record is deleted, the bgRFC units linked to it are also deleted. The bgRFC can be decoupled from the update using the interface method IF_BGRFC_UNIT~SEPARATE_FROM_UPDATE_TASK of the bgRFC object.
  • bgRFCs registered in a dialog module that were not started there using COMMIT WORK are not executed by the COMMIT WORK of the caller either.

Exceptions

Catchable Exceptions

CX_BGRFC_INVALID_UNIT

  • Cause: oref points to an invalid object.






ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 4660 Date: 20221203 Time: 170334     sap01-206 ( 79 ms )