SAP BAPI_RECORD_EXISTENCECHECK1 Function Module for Check Whether Record Exists









BAPI_RECORD_EXISTENCECHECK1 is a standard bapi record existencecheck1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Whether Record Exists 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 record existencecheck1 FM, simply by entering the name BAPI_RECORD_EXISTENCECHECK1 into the relevant SAP transaction such as SE37 or SE38.

Function Group: SRM_BAPI_RECORD
Program Name: SAPLSRM_BAPI_RECORD
Main Program: SAPLSRM_BAPI_RECORD
Appliation area:
Release date: 15-Jul-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_RECORD_EXISTENCECHECK1 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_RECORD_EXISTENCECHECK1'"Check Whether Record Exists
EXPORTING
OBJECTID = "Internal ID of Record Instance
DOCUMENTCLASS = "Storage Location of Record Instance
* DOC_CONTEXT = "SRM Context for Document Access

IMPORTING
RETURN = "Return Parameters
.



IMPORTING Parameters details for BAPI_RECORD_EXISTENCECHECK1

OBJECTID - Internal ID of Record Instance

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

DOCUMENTCLASS - Storage Location of Record Instance

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

DOC_CONTEXT - SRM Context for Document Access

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

EXPORTING Parameters details for BAPI_RECORD_EXISTENCECHECK1

RETURN - Return Parameters

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

Copy and paste ABAP code example for BAPI_RECORD_EXISTENCECHECK1 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_return  TYPE BAPIRET2, "   
lv_objectid  TYPE BAPISRMREC-GUID, "   
lv_documentclass  TYPE BAPISRMREC-DOCCLASS, "   
lv_doc_context  TYPE BAPIDOCCONTEXT. "   

  CALL FUNCTION 'BAPI_RECORD_EXISTENCECHECK1'  "Check Whether Record Exists
    EXPORTING
         OBJECTID = lv_objectid
         DOCUMENTCLASS = lv_documentclass
         DOC_CONTEXT = lv_doc_context
    IMPORTING
         RETURN = lv_return
. " BAPI_RECORD_EXISTENCECHECK1




ABAP code using 7.40 inline data declarations to call FM BAPI_RECORD_EXISTENCECHECK1

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 GUID FROM BAPISRMREC INTO @DATA(ld_objectid).
 
"SELECT single DOCCLASS FROM BAPISRMREC INTO @DATA(ld_documentclass).
 
 


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!