CATT_IDOC_STATUS_CHECK SAP Function module

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

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

Pattern for FM CATT_IDOC_STATUS_CHECK - CATT IDOC STATUS CHECK

CALL FUNCTION 'CATT_IDOC_STATUS_CHECK' "
  EXPORTING
    pi_starttime =              " sy-uzeit
    pi_finishtime =             " sy-uzeit
    pi_direction =              " edidc-direct
    pi_parnum =                 " edpp1-parnum  Partner Number
    pi_partyp =                 " edpp1-partyp  Partner Type
    pi_parfunc =                " edidc-rcvpfc  Partner func.
    pi_mestyp =                 " edimsg-mestyp  Logical message type
  EXCEPTIONS
    IDOCS_NOT_FOUND = 1         "
    WRONG_STATUS = 2            "
    .  "  CATT_IDOC_STATUS_CHECK

ABAP code example for Function Module CATT_IDOC_STATUS_CHECK

The ABAP code below is a full code listing to execute function module CATT_IDOC_STATUS_CHECK 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_pi_starttime) = 'Check type of data required'.

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

SELECT single DIRECT 
  FROM EDIDC 
  INTO @DATA(ld_pi_direction).

 

SELECT single PARNUM 
  FROM EDPP1 
  INTO @DATA(ld_pi_parnum).

 

SELECT single PARTYP 
  FROM EDPP1 
  INTO @DATA(ld_pi_partyp).

 

SELECT single RCVPFC 
  FROM EDIDC 
  INTO @DATA(ld_pi_parfunc).

 

SELECT single MESTYP 
  FROM EDIMSG 
  INTO @DATA(ld_pi_mestyp).

.

CALL FUNCTION 'CATT_IDOC_STATUS_CHECK'
  EXPORTING
    pi_starttime =               ld_pi_starttime
    pi_finishtime =              ld_pi_finishtime
    pi_direction =               ld_pi_direction
    pi_parnum =                  ld_pi_parnum
    pi_partyp =                  ld_pi_partyp
    pi_parfunc =                 ld_pi_parfunc
    pi_mestyp =                  ld_pi_mestyp
  EXCEPTIONS
    IDOCS_NOT_FOUND =            1
    WRONG_STATUS =               2
    .  "  CATT_IDOC_STATUS_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_pi_starttime
 
 TYPE SY-UZEIT ,
ld_pi_finishtime
 
 TYPE SY-UZEIT ,
ld_pi_direction
 
 TYPE EDIDC-DIRECT ,
ld_pi_parnum
 
 TYPE EDPP1-PARNUM ,
ld_pi_partyp
 
 TYPE EDPP1-PARTYP ,
ld_pi_parfunc
 
 TYPE EDIDC-RCVPFC ,
ld_pi_mestyp
 
 TYPE EDIMSG-MESTYP .


ld_pi_starttime = 'Check type of data required'.
ld_pi_finishtime = 'Check type of data required'.

SELECT single DIRECT 
  FROM EDIDC 
  INTO ld_pi_direction.


SELECT single PARNUM 
  FROM EDPP1 
  INTO ld_pi_parnum.


SELECT single PARTYP 
  FROM EDPP1 
  INTO ld_pi_partyp.


SELECT single RCVPFC 
  FROM EDIDC 
  INTO ld_pi_parfunc.


SELECT single MESTYP 
  FROM EDIMSG 
  INTO ld_pi_mestyp.