SAP JBD_VTMD_ARCH_RT_GET Function Module for Lesebaustein für Residenzzeit

Search SAP Function Modules

JBD_VTMD_ARCH_RT_GET is a standard jbd vtmd arch rt get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lesebaustein für Residenzzeit 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 jbd vtmd arch rt get FM, simply by entering the name JBD_VTMD_ARCH_RT_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: JBD_VTMD_ARCH_RT
Program Name: SAPLJBD_VTMD_ARCH_RT
Main Program: SAPLJBD_VTMD_ARCH_RT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JBD_VTMD_ARCH_RT_GET 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 'JBD_VTMD_ARCH_RT_GET'"Lesebaustein für Residenzzeit
  EXPORTING
*  I_TAB_VTMD_OBJNR =  "Interne Tabelle mit der komponente OBJNR

 IMPORTING
   E_FLG_GLOBAL_RESI_USED =  "Flag: für mindestens ein Objekt wurde die globale Residenzzeit verwendet
   E_FLG_OBJ_CUST_NOT_FOUND =  "Flag: Archivierungsobjekt-spezifisches Customizing nicht vorhanden

CHANGING
   C_TAB_ARCHIVE =  "Tabellentyp zum Lesen/Prüfen Residenzzeit Objekt VTMD_ARCH
*  C_STR_GLOBAL_CUST =  "Globale Steuerung Archivierung: Einstellungen

EXCEPTIONS
   GLOBAL_CUSTOMIZING_NOT_FOUND = 1 

.

IMPORTING Parameters details for JBD_VTMD_ARCH_RT_GET

I_TAB_VTMD_OBJNR - Interne Tabelle mit der komponente OBJNR

Data type: JBD_TAB_OBJNR
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for JBD_VTMD_ARCH_RT_GET

E_FLG_GLOBAL_RESI_USED - Flag: für mindestens ein Objekt wurde die globale Residenzzeit verwendet

Data type: XFELD
Optional: No
Call by Reference: Yes

E_FLG_OBJ_CUST_NOT_FOUND - Flag: Archivierungsobjekt-spezifisches Customizing nicht vorhanden

Data type: XFELD
Optional: No
Call by Reference: Yes

CHANGING Parameters details for JBD_VTMD_ARCH_RT_GET

C_TAB_ARCHIVE - Tabellentyp zum Lesen/Prüfen Residenzzeit Objekt VTMD_ARCH

Data type: JBD_TAB_JBDVTMD_RT
Optional: No
Call by Reference: Yes

C_STR_GLOBAL_CUST - Globale Steuerung Archivierung: Einstellungen

Data type: AFX_STR_GLOBAL_CUST
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

GLOBAL_CUSTOMIZING_NOT_FOUND - Globales Customizing nicht gefunden

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

Copy and paste ABAP code example for JBD_VTMD_ARCH_RT_GET 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 JBD_VTMD_ARCH_RT_GET

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