SAP BAPI_JBD_GETR_GET_DET_MULT Function Module for Generic Transaction: Get Detail Multiple









BAPI_JBD_GETR_GET_DET_MULT is a standard bapi jbd getr get det mult SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generic Transaction: Get Detail Multiple 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 bapi jbd getr get det mult FM, simply by entering the name BAPI_JBD_GETR_GET_DET_MULT into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_JBD_GETR_GET_DET_MULT 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 'BAPI_JBD_GETR_GET_DET_MULT'"Generic Transaction: Get Detail Multiple
  EXPORTING
*  PROCESSEXTENSION =  "Flag

TABLES
   TRANSACTION_KEYS =  "External Key of Generic Transaction
*  EXTENSIONOUT =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
*  RETURN =  "Return Parameters
*  HEADER =  "Generic Transaction: Header Data
*  HEADER_EXTENSION =  "Generic Transaction: Extended Header Structure
*  HIERARCY =  "Generic Transaction: Hierarchy
*  ELEMENTARY_TRANSACTION =  "Generic Transaction: Elementary Transactions
*  OPTION =  "Generic Transaction: Option Part
*  CASHFLOW =  "Generic Transaction: Flow Data
*  FORMULA =  "Generic Transaction: Formula
*  EXTENSIONIN =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
.



IMPORTING Parameters details for BAPI_JBD_GETR_GET_DET_MULT

PROCESSEXTENSION - Flag

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

TABLES Parameters details for BAPI_JBD_GETR_GET_DET_MULT

TRANSACTION_KEYS - External Key of Generic Transaction

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

EXTENSIONOUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

RETURN - Return Parameters

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

HEADER - Generic Transaction: Header Data

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

HEADER_EXTENSION - Generic Transaction: Extended Header Structure

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

HIERARCY - Generic Transaction: Hierarchy

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

ELEMENTARY_TRANSACTION - Generic Transaction: Elementary Transactions

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

OPTION - Generic Transaction: Option Part

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

CASHFLOW - Generic Transaction: Flow Data

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

FORMULA - Generic Transaction: Formula

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

EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

Copy and paste ABAP code example for BAPI_JBD_GETR_GET_DET_MULT 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_processextension  TYPE BAPIFLAG, "   
lt_transaction_keys  TYPE STANDARD TABLE OF BAPI_JBD_STR_GT_KEY, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_header  TYPE STANDARD TABLE OF BAPI_JBD_STR_GT_KO, "   
lt_header_extension  TYPE STANDARD TABLE OF BAPI_JBD_STR_GT_ABEST, "   
lt_hierarcy  TYPE STANDARD TABLE OF BAPI_JBD_STR_GT_HIER, "   
lt_elementary_transaction  TYPE STANDARD TABLE OF BAPI_JBD_STR_GT_KOET, "   
lt_option  TYPE STANDARD TABLE OF BAPI_JBD_STR_GT_OPTI, "   
lt_cashflow  TYPE STANDARD TABLE OF BAPI_JBD_STR_GT_BEWEG, "   
lt_formula  TYPE STANDARD TABLE OF BAPI_JBD_STR_GT_FML, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX. "   

  CALL FUNCTION 'BAPI_JBD_GETR_GET_DET_MULT'  "Generic Transaction: Get Detail Multiple
    EXPORTING
         PROCESSEXTENSION = lv_processextension
    TABLES
         TRANSACTION_KEYS = lt_transaction_keys
         EXTENSIONOUT = lt_extensionout
         RETURN = lt_return
         HEADER = lt_header
         HEADER_EXTENSION = lt_header_extension
         HIERARCY = lt_hierarcy
         ELEMENTARY_TRANSACTION = lt_elementary_transaction
         OPTION = lt_option
         CASHFLOW = lt_cashflow
         FORMULA = lt_formula
         EXTENSIONIN = lt_extensionin
. " BAPI_JBD_GETR_GET_DET_MULT




ABAP code using 7.40 inline data declarations to call FM BAPI_JBD_GETR_GET_DET_MULT

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!