SAP ARCHIVE_GET_CUSTOMIZING_DATA Function Module for Read Customizing Data of an Archiving Object









ARCHIVE_GET_CUSTOMIZING_DATA is a standard archive get customizing data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Customizing Data of an Archiving Object 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 archive get customizing data FM, simply by entering the name ARCHIVE_GET_CUSTOMIZING_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: ARCH
Program Name: SAPLARCH
Main Program: SAPLARCH
Appliation area: S
Release date: 10-Nov-1994
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ARCHIVE_GET_CUSTOMIZING_DATA 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 'ARCHIVE_GET_CUSTOMIZING_DATA'"Read Customizing Data of an Archiving Object
EXPORTING
OBJECT = "Archiving Object

IMPORTING
COMMIT_COUNT_FOR_DELETE_PRG = "Number of Objects for a Commit Work
MAINTAIN_INDEX = "Indicator: Data Object Index Created

EXCEPTIONS
OBJECT_NOT_FOUND = 1
.



IMPORTING Parameters details for ARCHIVE_GET_CUSTOMIZING_DATA

OBJECT - Archiving Object

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

EXPORTING Parameters details for ARCHIVE_GET_CUSTOMIZING_DATA

COMMIT_COUNT_FOR_DELETE_PRG - Number of Objects for a Commit Work

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

MAINTAIN_INDEX - Indicator: Data Object Index Created

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

EXCEPTIONS details

OBJECT_NOT_FOUND - Object Unknown

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

Copy and paste ABAP code example for ARCHIVE_GET_CUSTOMIZING_DATA 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_object  TYPE ARCH_OBJ-OBJECT, "   
lv_object_not_found  TYPE ARCH_OBJ, "   
lv_commit_count_for_delete_prg  TYPE ARCH_USR-ARCH_COMIT, "   
lv_maintain_index  TYPE ARCH_USR-ARCH_INDEX. "   

  CALL FUNCTION 'ARCHIVE_GET_CUSTOMIZING_DATA'  "Read Customizing Data of an Archiving Object
    EXPORTING
         OBJECT = lv_object
    IMPORTING
         COMMIT_COUNT_FOR_DELETE_PRG = lv_commit_count_for_delete_prg
         MAINTAIN_INDEX = lv_maintain_index
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
. " ARCHIVE_GET_CUSTOMIZING_DATA




ABAP code using 7.40 inline data declarations to call FM ARCHIVE_GET_CUSTOMIZING_DATA

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 OBJECT FROM ARCH_OBJ INTO @DATA(ld_object).
 
 
"SELECT single ARCH_COMIT FROM ARCH_USR INTO @DATA(ld_commit_count_for_delete_prg).
 
"SELECT single ARCH_INDEX FROM ARCH_USR INTO @DATA(ld_maintain_index).
 


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!