SAP BBP_CHECK_IF_ARCHIVED Function Module for









BBP_CHECK_IF_ARCHIVED is a standard bbp check if archived SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bbp check if archived FM, simply by entering the name BBP_CHECK_IF_ARCHIVED into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_CHECK_IF_ARCHIVED 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 'BBP_CHECK_IF_ARCHIVED'"
EXPORTING
* I_GUID = "
* I_OBJECT_ID = "
* I_OBJECT_TYPE = "
.



IMPORTING Parameters details for BBP_CHECK_IF_ARCHIVED

I_GUID -

Data type: CRMD_ORDERADM_H-GUID
Optional: Yes
Call by Reference: Yes

I_OBJECT_ID -

Data type: CRMD_ORDERADM_H-OBJECT_ID
Optional: Yes
Call by Reference: Yes

I_OBJECT_TYPE -

Data type: CRMD_ORDERADM_H-OBJECT_TYPE
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BBP_CHECK_IF_ARCHIVED 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_i_guid  TYPE CRMD_ORDERADM_H-GUID, "   
lv_i_object_id  TYPE CRMD_ORDERADM_H-OBJECT_ID, "   
lv_i_object_type  TYPE CRMD_ORDERADM_H-OBJECT_TYPE. "   

  CALL FUNCTION 'BBP_CHECK_IF_ARCHIVED'  "
    EXPORTING
         I_GUID = lv_i_guid
         I_OBJECT_ID = lv_i_object_id
         I_OBJECT_TYPE = lv_i_object_type
. " BBP_CHECK_IF_ARCHIVED




ABAP code using 7.40 inline data declarations to call FM BBP_CHECK_IF_ARCHIVED

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 CRMD_ORDERADM_H INTO @DATA(ld_i_guid).
 
"SELECT single OBJECT_ID FROM CRMD_ORDERADM_H INTO @DATA(ld_i_object_id).
 
"SELECT single OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_i_object_type).
 


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!