UPSIF_CALL_READ_DESCRIPTION SAP Function module

UPSIF_CALL_READ_DESCRIPTION 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 UPSIF_CALL_READ_DESCRIPTION into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: UPSIF
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM UPSIF_CALL_READ_DESCRIPTION - UPSIF CALL READ DESCRIPTION

CALL FUNCTION 'UPSIF_CALL_READ_DESCRIPTION' "
  EXPORTING
    im_objtyp =                 " api_upsitm-objtyp  Object type
*   im_callmode = KUPS_DISTRIBUTION  " char0001
    im_direct =                 " ups_direct    ALE Distribution Packet: Distribution Direction
*   im_dlock = SPACE            " ups_dlock     Include Distribution Lock
  TABLES
    outitm =                    " out_upsitm    ALE Distribution Packet: Object Data (Input Structure)
  EXCEPTIONS
    FAILURE = 1                 "                Errors
    .  "  UPSIF_CALL_READ_DESCRIPTION

ABAP code example for Function Module UPSIF_CALL_READ_DESCRIPTION

The ABAP code below is a full code listing to execute function module UPSIF_CALL_READ_DESCRIPTION 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:
it_outitm  
 
 TYPE STANDARD TABLE OF OUT_UPSITM,"TABLES PARAM
wa_outitm
 
 LIKE LINE OF it_outitm
.



DATA(ld_im_objtyp) = some text here

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

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

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

"populate fields of struture and append to itab
append wa_outitm to it_outitm.
.

CALL FUNCTION 'UPSIF_CALL_READ_DESCRIPTION'
  EXPORTING
    im_objtyp =                  ld_im_objtyp
*   im_callmode =                ld_im_callmode
    im_direct =                  ld_im_direct
*   im_dlock =                   ld_im_dlock
  TABLES
    outitm =                     it_outitm
  EXCEPTIONS
    FAILURE =                    1
    .  "  UPSIF_CALL_READ_DESCRIPTION

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_im_objtyp
 
 TYPE API_UPSITM-OBJTYP ,
it_outitm
 
 TYPE STANDARD TABLE OF OUT_UPSITM ,
wa_outitm
 
 LIKE LINE OF it_outitm,
ld_im_callmode
 
 TYPE CHAR0001 ,
ld_im_direct
 
 TYPE UPS_DIRECT ,
ld_im_dlock
 
 TYPE UPS_DLOCK .



ld_im_objtyp = some text here 

"populate fields of struture and append to itab
append wa_outitm to it_outitm.
ld_im_callmode = 'Check type of data required'.
ld_im_direct = 'Check type of data required'.
ld_im_dlock = 'Check type of data required'.