SAP FLBP_CALLBACK_BUPA_ARCH4 Function Module for Delete after Archiving
FLBP_CALLBACK_BUPA_ARCH4 is a standard flbp callback bupa arch4 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete after Archiving 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 flbp callback bupa arch4 FM, simply by entering the name FLBP_CALLBACK_BUPA_ARCH4 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVBP_CALLBACK_BUPA
Program Name: SAPLFVBP_CALLBACK_BUPA
Main Program: SAPLFVBP_CALLBACK_BUPA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FLBP_CALLBACK_BUPA_ARCH4 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 'FLBP_CALLBACK_BUPA_ARCH4'"Delete after Archiving.
TABLES
IT_DELETE = "BDT Archiving: Data Already Archived - Free for Deletion
* ET_RETURN = "Business Partner: Complex Return Structure for Messages
EXCEPTIONS
FATAL_ERROR = 1
TABLES Parameters details for FLBP_CALLBACK_BUPA_ARCH4
IT_DELETE - BDT Archiving: Data Already Archived - Free for Deletion
Data type: BUSSARCYESOptional: No
Call by Reference: Yes
ET_RETURN - Business Partner: Complex Return Structure for Messages
Data type: BUS_RETURNOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FATAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FLBP_CALLBACK_BUPA_ARCH4 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: | ||||
| lt_it_delete | TYPE STANDARD TABLE OF BUSSARCYES, " | |||
| lv_fatal_error | TYPE BUSSARCYES, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BUS_RETURN. " |
|   CALL FUNCTION 'FLBP_CALLBACK_BUPA_ARCH4' "Delete after Archiving |
| TABLES | ||
| IT_DELETE | = lt_it_delete | |
| ET_RETURN | = lt_et_return | |
| EXCEPTIONS | ||
| FATAL_ERROR = 1 | ||
| . " FLBP_CALLBACK_BUPA_ARCH4 | ||
ABAP code using 7.40 inline data declarations to call FM FLBP_CALLBACK_BUPA_ARCH4
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