SAP REVISION_LEVEL_TABLE_EXPORT Function Module for List all change indices for object (document/material)









REVISION_LEVEL_TABLE_EXPORT is a standard revision level table export SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for List all change indices for object (document/material) 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 revision level table export FM, simply by entering the name REVISION_LEVEL_TABLE_EXPORT into the relevant SAP transaction such as SE37 or SE38.

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



Function REVISION_LEVEL_TABLE_EXPORT 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 'REVISION_LEVEL_TABLE_EXPORT'"List all change indices for object (document/material)
  EXPORTING
*  EDOKAR = ' ' "
*  EDOKNR = ' ' "
*  EDOKTL = ' ' "
*  EDOKVR = ' ' "
*  EMATNR = ' ' "Material number
*  BYPASS_BUFFER = 'X' "

TABLES
   WA =  "
.



IMPORTING Parameters details for REVISION_LEVEL_TABLE_EXPORT

EDOKAR -

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

EDOKNR -

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

EDOKTL -

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

EDOKVR -

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

EMATNR - Material number

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

BYPASS_BUFFER -

Data type: CSDATA-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for REVISION_LEVEL_TABLE_EXPORT

WA -

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

Copy and paste ABAP code example for REVISION_LEVEL_TABLE_EXPORT 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_wa  TYPE STANDARD TABLE OF CCRVL_EXP, "   
lv_edokar  TYPE DRAW-DOKAR, "   SPACE
lv_edoknr  TYPE DRAW-DOKNR, "   SPACE
lv_edoktl  TYPE DRAW-DOKTL, "   SPACE
lv_edokvr  TYPE DRAW-DOKVR, "   SPACE
lv_ematnr  TYPE MARA-MATNR, "   SPACE
lv_bypass_buffer  TYPE CSDATA-XFELD. "   'X'

  CALL FUNCTION 'REVISION_LEVEL_TABLE_EXPORT'  "List all change indices for object (document/material)
    EXPORTING
         EDOKAR = lv_edokar
         EDOKNR = lv_edoknr
         EDOKTL = lv_edoktl
         EDOKVR = lv_edokvr
         EMATNR = lv_ematnr
         BYPASS_BUFFER = lv_bypass_buffer
    TABLES
         WA = lt_wa
. " REVISION_LEVEL_TABLE_EXPORT




ABAP code using 7.40 inline data declarations to call FM REVISION_LEVEL_TABLE_EXPORT

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 DOKAR FROM DRAW INTO @DATA(ld_edokar).
DATA(ld_edokar) = ' '.
 
"SELECT single DOKNR FROM DRAW INTO @DATA(ld_edoknr).
DATA(ld_edoknr) = ' '.
 
"SELECT single DOKTL FROM DRAW INTO @DATA(ld_edoktl).
DATA(ld_edoktl) = ' '.
 
"SELECT single DOKVR FROM DRAW INTO @DATA(ld_edokvr).
DATA(ld_edokvr) = ' '.
 
"SELECT single MATNR FROM MARA INTO @DATA(ld_ematnr).
DATA(ld_ematnr) = ' '.
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_bypass_buffer).
DATA(ld_bypass_buffer) = 'X'.
 


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!