SAP JBD_GETR_ARCH_JBGT2_1260 Function Module for Prüfung, ob Objekte gesperrt sind









JBD_GETR_ARCH_JBGT2_1260 is a standard jbd getr arch jbgt2 1260 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prüfung, ob Objekte gesperrt sind 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 getr arch jbgt2 1260 FM, simply by entering the name JBD_GETR_ARCH_JBGT2_1260 into the relevant SAP transaction such as SE37 or SE38.

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



Function JBD_GETR_ARCH_JBGT2_1260 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_GETR_ARCH_JBGT2_1260'"Prüfung, ob Objekte gesperrt sind
CHANGING
C_TAB_STATUS_CHANGE = "
.



CHANGING Parameters details for JBD_GETR_ARCH_JBGT2_1260

C_TAB_STATUS_CHANGE -

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

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

DATA:
lv_c_tab_status_change  TYPE BANK_TAB_PP_STATUS_CHANGE. "   

  CALL FUNCTION 'JBD_GETR_ARCH_JBGT2_1260'  "Prüfung, ob Objekte gesperrt sind
    CHANGING
         C_TAB_STATUS_CHANGE = lv_c_tab_status_change
. " JBD_GETR_ARCH_JBGT2_1260




ABAP code using 7.40 inline data declarations to call FM JBD_GETR_ARCH_JBGT2_1260

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!