SAP SCMS_AO_TABLE_GET_BYTES Function Module for CMS: Make AO API Document Available in Bytes









SCMS_AO_TABLE_GET_BYTES is a standard scms ao table get bytes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CMS: Make AO API Document Available in Bytes 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 scms ao table get bytes FM, simply by entering the name SCMS_AO_TABLE_GET_BYTES into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCMS_AO_API
Program Name: SAPLSCMS_AO_API
Main Program: SAPLSCMS_AO_API
Appliation area: S
Release date: 25-Aug-2003
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SCMS_AO_TABLE_GET_BYTES 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 'SCMS_AO_TABLE_GET_BYTES'"CMS: Make AO API Document Available in Bytes
EXPORTING
* MANDT = SY-MANDT "R/3 system (client number from logon)
ARC_ID = "
DOC_ID = "
OFFSET = "
LENGTH = "
* COMP_ID = 'data' "

IMPORTING
LENGTH = "

TABLES
DATA = "

EXCEPTIONS
ERROR_HTTP = 1 ERROR_ARCHIV = 2 ERROR_KERNEL = 3 ERROR_CONFIG = 4
.



IMPORTING Parameters details for SCMS_AO_TABLE_GET_BYTES

MANDT - R/3 system (client number from logon)

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

ARC_ID -

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

DOC_ID -

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

OFFSET -

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

LENGTH -

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

COMP_ID -

Data type: C
Default: 'data'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SCMS_AO_TABLE_GET_BYTES

LENGTH -

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

TABLES Parameters details for SCMS_AO_TABLE_GET_BYTES

DATA -

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

EXCEPTIONS details

ERROR_HTTP -

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

ERROR_ARCHIV -

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

ERROR_KERNEL -

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

ERROR_CONFIG -

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

Copy and paste ABAP code example for SCMS_AO_TABLE_GET_BYTES 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_data  TYPE STANDARD TABLE OF TBL1024, "   
lv_mandt  TYPE SY-MANDT, "   SY-MANDT
lv_length  TYPE I, "   
lv_error_http  TYPE I, "   
lv_arc_id  TYPE C, "   
lv_error_archiv  TYPE C, "   
lv_doc_id  TYPE C, "   
lv_error_kernel  TYPE C, "   
lv_offset  TYPE NUMERIC, "   
lv_error_config  TYPE NUMERIC, "   
lv_length  TYPE I, "   
lv_comp_id  TYPE C. "   'data'

  CALL FUNCTION 'SCMS_AO_TABLE_GET_BYTES'  "CMS: Make AO API Document Available in Bytes
    EXPORTING
         MANDT = lv_mandt
         ARC_ID = lv_arc_id
         DOC_ID = lv_doc_id
         OFFSET = lv_offset
         LENGTH = lv_length
         COMP_ID = lv_comp_id
    IMPORTING
         LENGTH = lv_length
    TABLES
         DATA = lt_data
    EXCEPTIONS
        ERROR_HTTP = 1
        ERROR_ARCHIV = 2
        ERROR_KERNEL = 3
        ERROR_CONFIG = 4
. " SCMS_AO_TABLE_GET_BYTES




ABAP code using 7.40 inline data declarations to call FM SCMS_AO_TABLE_GET_BYTES

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 MANDT FROM SY INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
 
 
 
 
 
 
 
 
 
DATA(ld_comp_id) = 'data'.
 


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!