SAP EDOSVN_BGR_TRIGGER Function Module for eDocument Slovenia: Process triggering in background

Search SAP Function Modules

EDOSVN_BGR_TRIGGER is a standard edosvn bgr trigger SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for eDocument Slovenia: Process triggering in background processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for edosvn bgr trigger FM, simply by entering the name EDOSVN_BGR_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

Function Group: EDO_SVN_FGR
Program Name: SAPLEDO_SVN_FGR
Main Program: SAPLEDO_SVN_FGR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EDOSVN_BGR_TRIGGER pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'EDOSVN_BGR_TRIGGER'"eDocument Slovenia: Process triggering in background
  EXPORTING
   IV_SOURCE_TYPE =  "eDocument Source Type
   IV_SOURCE_KEY =  "eDocument Source Key

.

IMPORTING Parameters details for EDOSVN_BGR_TRIGGER

IV_SOURCE_TYPE - eDocument Source Type

Data type: EDOC_SOURCE_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_SOURCE_KEY - eDocument Source Key

Data type: EDOC_SOURCE_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EDOSVN_BGR_TRIGGER Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM EDOSVN_BGR_TRIGGER

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects