OCS_SAVE_QUEUE SAP Function module

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

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

Pattern for FM OCS_SAVE_QUEUE - OCS SAVE QUEUE

CALL FUNCTION 'OCS_SAVE_QUEUE' "
* EXPORTING
*   iv_ocs_tool =               " sy-tcode      ABAP Program, Current Transaction Code
*   iv_scenario =               " pat01-scenario
*   iv_extern_call =            " c
  IMPORTING
    ev_final_scenario =         " pat01-scenario
  TABLES
    tt_patq =                   " pat_q
  EXCEPTIONS
    QUEUE_LOCKED = 1            "
    PAT01_NOT_EMPTY = 2         "
    INTERNAL_ERROR = 3          "
    .  "  OCS_SAVE_QUEUE

ABAP code example for Function Module OCS_SAVE_QUEUE

The ABAP code below is a full code listing to execute function module OCS_SAVE_QUEUE 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_ev_final_scenario  
 
 TYPE PAT01-SCENARIO
,
it_tt_patq  
 
 TYPE STANDARD TABLE OF PAT_Q,"TABLES PARAM
wa_tt_patq
 
 LIKE LINE OF it_tt_patq
.


DATA(ld_iv_ocs_tool) = 'some text here'.
 

SELECT single SCENARIO 
  FROM PAT01 
  INTO @DATA(ld_iv_scenario).


DATA(ld_iv_extern_call) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_tt_patq to it_tt_patq.
.

CALL FUNCTION 'OCS_SAVE_QUEUE'
* EXPORTING
*   iv_ocs_tool =                ld_iv_ocs_tool
*   iv_scenario =                ld_iv_scenario
*   iv_extern_call =             ld_iv_extern_call
  IMPORTING
    ev_final_scenario =          ld_ev_final_scenario
  TABLES
    tt_patq =                    it_tt_patq
  EXCEPTIONS
    QUEUE_LOCKED =               1
    PAT01_NOT_EMPTY =            2
    INTERNAL_ERROR =             3
    .  "  OCS_SAVE_QUEUE

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_ev_final_scenario
 
 TYPE PAT01-SCENARIO ,
ld_iv_ocs_tool
 
 TYPE SY-TCODE ,
it_tt_patq
 
 TYPE STANDARD TABLE OF PAT_Q ,
wa_tt_patq
 
 LIKE LINE OF it_tt_patq,
ld_iv_scenario
 
 TYPE PAT01-SCENARIO ,
ld_iv_extern_call
 
 TYPE C .


ld_iv_ocs_tool = 'some text here'. 

"populate fields of struture and append to itab
append wa_tt_patq to it_tt_patq.

SELECT single SCENARIO 
  FROM PAT01 
  INTO ld_iv_scenario.

ld_iv_extern_call = 'some text here'.