SAP BAPI_REQUEST_GETDETAIL Function Module for BAPI: Read Request









BAPI_REQUEST_GETDETAIL is a standard bapi request getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI: Read Request 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 request getdetail FM, simply by entering the name BAPI_REQUEST_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: FKK_REQUEST_BOR
Program Name: SAPLFKK_REQUEST_BOR
Main Program: SAPLFKK_REQUEST_BOR
Appliation area:
Release date: 02-Dec-2003
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_REQUEST_GETDETAIL 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_REQUEST_GETDETAIL'"BAPI: Read Request
  EXPORTING
   REQUESTNUMBER =  "Request Number
*  READARCHIVE = ' ' "Also Read Data from Archive

 IMPORTING
   REQUESTHEADOUT =  "BAPI Export: Request Header Data

TABLES
*  REQUESTITEMOUT =  "BAPI Export: Request Items
*  REQUESTLOCKS =  "BAPI: Processing Locks in Request Items
*  REQUESTDUEDATAOUT =  "BAPI Export: Due Dates of Request
*  REQUESTDOCUMENT =  "BAPI Export: Documents Created from Request
*  EXTENSIONOUT =  "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
   RETURN =  "Return Parameters
.



IMPORTING Parameters details for BAPI_REQUEST_GETDETAIL

REQUESTNUMBER - Request Number

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

READARCHIVE - Also Read Data from Archive

Data type: BAPIREQUEST_ADMIN-READ_ARCHIVE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_REQUEST_GETDETAIL

REQUESTHEADOUT - BAPI Export: Request Header Data

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

TABLES Parameters details for BAPI_REQUEST_GETDETAIL

REQUESTITEMOUT - BAPI Export: Request Items

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

REQUESTLOCKS - BAPI: Processing Locks in Request Items

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

REQUESTDUEDATAOUT - BAPI Export: Due Dates of Request

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

REQUESTDOCUMENT - BAPI Export: Documents Created from Request

Data type: BAPIREQUEST_DOCUMENT
Optional: Yes
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: No
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_REQUEST_GETDETAIL 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_requestnumber  TYPE BAPIREQUEST_KEY-REQUESTNUMBER, "   
lv_requestheadout  TYPE BAPIREQUEST_HEAD_OUT, "   
lt_requestitemout  TYPE STANDARD TABLE OF BAPIREQUEST_ITEM_OUT, "   
lv_readarchive  TYPE BAPIREQUEST_ADMIN-READ_ARCHIVE, "   SPACE
lt_requestlocks  TYPE STANDARD TABLE OF BAPIREQUEST_LOCKS, "   
lt_requestduedataout  TYPE STANDARD TABLE OF BAPIREQUEST_DUE_OUT, "   
lt_requestdocument  TYPE STANDARD TABLE OF BAPIREQUEST_DOCUMENT, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_REQUEST_GETDETAIL'  "BAPI: Read Request
    EXPORTING
         REQUESTNUMBER = lv_requestnumber
         READARCHIVE = lv_readarchive
    IMPORTING
         REQUESTHEADOUT = lv_requestheadout
    TABLES
         REQUESTITEMOUT = lt_requestitemout
         REQUESTLOCKS = lt_requestlocks
         REQUESTDUEDATAOUT = lt_requestduedataout
         REQUESTDOCUMENT = lt_requestdocument
         EXTENSIONOUT = lt_extensionout
         RETURN = lt_return
. " BAPI_REQUEST_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM BAPI_REQUEST_GETDETAIL

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.

"SELECT single REQUESTNUMBER FROM BAPIREQUEST_KEY INTO @DATA(ld_requestnumber).
 
 
 
"SELECT single READ_ARCHIVE FROM BAPIREQUEST_ADMIN INTO @DATA(ld_readarchive).
DATA(ld_readarchive) = ' '.
 
 
 
 
 
 


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!