CACS_OUTBOUND_PRC_1600 SAP Function module

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

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

Pattern for FM CACS_OUTBOUND_PRC_1600 - CACS OUTBOUND PRC 1600

CALL FUNCTION 'CACS_OUTBOUND_PRC_1600' "
* EXPORTING
*   i_appl =                    " cacsappl
*   i_ctrtbu_id =               " cacs_ctrtbu_id
*   i_ctrtbu_bdate =            " cacs_ctrtbu-ctrtbu_bdate
*   i_ctrtbu_edate =            " cacs_ctrtbu-ctrtbu_edate
  IMPORTING
    e_occ_begin =               " dats
    e_occ_end =                 " dats
  EXCEPTIONS
    NO_DESTINATION = 1          "
    NO_COMPONENT_ACTIVE = 2     "
    ERROR_MULTIPLE_SELECTION = 3  "
    .  "  CACS_OUTBOUND_PRC_1600

ABAP code example for Function Module CACS_OUTBOUND_PRC_1600

The ABAP code below is a full code listing to execute function module CACS_OUTBOUND_PRC_1600 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_occ_begin  
 
 TYPE DATS
,
ld_e_occ_end  
 
 TYPE DATS
.


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

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

SELECT single CTRTBU_BDATE 
  FROM CACS_CTRTBU 
  INTO @DATA(ld_i_ctrtbu_bdate).

 

SELECT single CTRTBU_EDATE 
  FROM CACS_CTRTBU 
  INTO @DATA(ld_i_ctrtbu_edate).

.

CALL FUNCTION 'CACS_OUTBOUND_PRC_1600'
* EXPORTING
*   i_appl =                     ld_i_appl
*   i_ctrtbu_id =                ld_i_ctrtbu_id
*   i_ctrtbu_bdate =             ld_i_ctrtbu_bdate
*   i_ctrtbu_edate =             ld_i_ctrtbu_edate
  IMPORTING
    e_occ_begin =                ld_e_occ_begin
    e_occ_end =                  ld_e_occ_end
  EXCEPTIONS
    NO_DESTINATION =             1
    NO_COMPONENT_ACTIVE =        2
    ERROR_MULTIPLE_SELECTION =    3
    .  "  CACS_OUTBOUND_PRC_1600

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
ELSEIF SY-SUBRC EQ 3. "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_occ_begin
 
 TYPE DATS ,
ld_i_appl
 
 TYPE CACSAPPL ,
ld_e_occ_end
 
 TYPE DATS ,
ld_i_ctrtbu_id
 
 TYPE CACS_CTRTBU_ID ,
ld_i_ctrtbu_bdate
 
 TYPE CACS_CTRTBU-CTRTBU_BDATE ,
ld_i_ctrtbu_edate
 
 TYPE CACS_CTRTBU-CTRTBU_EDATE .


ld_i_appl = 'Check type of data required'.
ld_i_ctrtbu_id = 'Check type of data required'.

SELECT single CTRTBU_BDATE 
  FROM CACS_CTRTBU 
  INTO ld_i_ctrtbu_bdate.


SELECT single CTRTBU_EDATE 
  FROM CACS_CTRTBU 
  INTO ld_i_ctrtbu_edate.