AS_API_INFOSTRUC_SELECT SAP Function module

AS_API_INFOSTRUC_SELECT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name AS_API_INFOSTRUC_SELECT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: AS_API
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM AS_API_INFOSTRUC_SELECT - AS API INFOSTRUC SELECT

CALL FUNCTION 'AS_API_INFOSTRUC_SELECT' "
* EXPORTING
*   i_popup = 'X'               " c
*   i_object =                  " arch_obj-object  Archiving Object
*   i_fieldcat =                " aind_fcat
*   i_obligatory_fields =       " table
  IMPORTING
    e_infostruc =               " aind_desc
    e_all_fields =              " table
    e_cancelled =               " c
  EXCEPTIONS
    NO_INFOSTRUC_FOUND = 1      "               No suitable info structure found
    .  "  AS_API_INFOSTRUC_SELECT

ABAP code example for Function Module AS_API_INFOSTRUC_SELECT

The ABAP code below is a full code listing to execute function module AS_API_INFOSTRUC_SELECT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_infostruc  
 
 TYPE AIND_DESC
,
ld_e_all_fields  
 
 TYPE TABLE
,
ld_e_cancelled  
 
 TYPE C
.


DATA(ld_i_popup) = 'Check type of data required'.
 

SELECT single OBJECT 
  FROM ARCH_OBJ 
  INTO @DATA(ld_i_object).


DATA(ld_i_fieldcat) = 'Check type of data required'.

DATA(ld_i_obligatory_fields) = 'Check type of data required'.
.

CALL FUNCTION 'AS_API_INFOSTRUC_SELECT'
* EXPORTING
*   i_popup =                    ld_i_popup
*   i_object =                   ld_i_object
*   i_fieldcat =                 ld_i_fieldcat
*   i_obligatory_fields =        ld_i_obligatory_fields
  IMPORTING
    e_infostruc =                ld_e_infostruc
    e_all_fields =               ld_e_all_fields
    e_cancelled =                ld_e_cancelled
  EXCEPTIONS
    NO_INFOSTRUC_FOUND =         1
    .  "  AS_API_INFOSTRUC_SELECT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_infostruc
 
 TYPE AIND_DESC ,
ld_i_popup
 
 TYPE C ,
ld_e_all_fields
 
 TYPE TABLE ,
ld_i_object
 
 TYPE ARCH_OBJ-OBJECT ,
ld_e_cancelled
 
 TYPE C ,
ld_i_fieldcat
 
 TYPE AIND_FCAT ,
ld_i_obligatory_fields
 
 TYPE TABLE .


ld_i_popup = 'Check type of data required'.

SELECT single OBJECT 
  FROM ARCH_OBJ 
  INTO ld_i_object.

ld_i_fieldcat = 'Check type of data required'.
ld_i_obligatory_fields = 'Check type of data required'.