SAP ARCHIV_CUSTOMIZE_BARCODE Function Module for









ARCHIV_CUSTOMIZE_BARCODE is a standard archiv customize barcode 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 archiv customize barcode FM, simply by entering the name ARCHIV_CUSTOMIZE_BARCODE into the relevant SAP transaction such as SE37 or SE38.

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



Function ARCHIV_CUSTOMIZE_BARCODE 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 'ARCHIV_CUSTOMIZE_BARCODE'"
  EXPORTING
*  DOCUMENT = ' ' "
   OBJECT =  "
*  USERNAME = SY-UNAME "
*  NO_CHECK = ' ' "

 IMPORTING
   BARCODETYPE =  "
   X_CHECK =  "
   X_ACTIV =  "
   X_NO_CANCEL =  "
   X_DUPLICATE =  "
   RETURN =  "
   S_TOACM =  "
   X_WORKFLOW =  "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLOPTE_001 Business Document Service: Customer Exit Bar Code

IMPORTING Parameters details for ARCHIV_CUSTOMIZE_BARCODE

DOCUMENT -

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

OBJECT -

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

USERNAME -

Data type: TOACM-USERNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_CHECK -

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

EXPORTING Parameters details for ARCHIV_CUSTOMIZE_BARCODE

BARCODETYPE -

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

X_CHECK -

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

X_ACTIV -

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

X_NO_CANCEL -

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

X_DUPLICATE -

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

RETURN -

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

S_TOACM -

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

X_WORKFLOW -

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

Copy and paste ABAP code example for ARCHIV_CUSTOMIZE_BARCODE 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_document  TYPE TOAOM-AR_OBJECT, "   SPACE
lv_barcodetype  TYPE TOACM-BARCODE_TY, "   
lv_object  TYPE TOAOM-SAP_OBJECT, "   
lv_x_check  TYPE TOACM-OPTICAL_AR, "   
lv_x_activ  TYPE TOACM-BARCODE_IN, "   
lv_username  TYPE TOACM-USERNAME, "   SY-UNAME
lv_no_check  TYPE TOAOM-AR_STATUS, "   SPACE
lv_x_no_cancel  TYPE TOACM-NO_CANCEL, "   
lv_x_duplicate  TYPE TOACM-DUPLICATE, "   
lv_return  TYPE SAPB-RETURN, "   
lv_s_toacm  TYPE TOACM, "   
lv_x_workflow  TYPE TOACM-WORKFLOW. "   

  CALL FUNCTION 'ARCHIV_CUSTOMIZE_BARCODE'  "
    EXPORTING
         DOCUMENT = lv_document
         OBJECT = lv_object
         USERNAME = lv_username
         NO_CHECK = lv_no_check
    IMPORTING
         BARCODETYPE = lv_barcodetype
         X_CHECK = lv_x_check
         X_ACTIV = lv_x_activ
         X_NO_CANCEL = lv_x_no_cancel
         X_DUPLICATE = lv_x_duplicate
         RETURN = lv_return
         S_TOACM = lv_s_toacm
         X_WORKFLOW = lv_x_workflow
. " ARCHIV_CUSTOMIZE_BARCODE




ABAP code using 7.40 inline data declarations to call FM ARCHIV_CUSTOMIZE_BARCODE

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 AR_OBJECT FROM TOAOM INTO @DATA(ld_document).
DATA(ld_document) = ' '.
 
"SELECT single BARCODE_TY FROM TOACM INTO @DATA(ld_barcodetype).
 
"SELECT single SAP_OBJECT FROM TOAOM INTO @DATA(ld_object).
 
"SELECT single OPTICAL_AR FROM TOACM INTO @DATA(ld_x_check).
 
"SELECT single BARCODE_IN FROM TOACM INTO @DATA(ld_x_activ).
 
"SELECT single USERNAME FROM TOACM INTO @DATA(ld_username).
DATA(ld_username) = SY-UNAME.
 
"SELECT single AR_STATUS FROM TOAOM INTO @DATA(ld_no_check).
DATA(ld_no_check) = ' '.
 
"SELECT single NO_CANCEL FROM TOACM INTO @DATA(ld_x_no_cancel).
 
"SELECT single DUPLICATE FROM TOACM INTO @DATA(ld_x_duplicate).
 
"SELECT single RETURN FROM SAPB INTO @DATA(ld_return).
 
 
"SELECT single WORKFLOW FROM TOACM INTO @DATA(ld_x_workflow).
 


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!