SCMA_BUFFER_OFFICE_KEYS SAP Function module

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

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

Pattern for FM SCMA_BUFFER_OFFICE_KEYS - SCMA BUFFER OFFICE KEYS

CALL FUNCTION 'SCMA_BUFFER_OFFICE_KEYS' "
  EXPORTING
    i_doc_id =                  " bds_docid
*   i_doc_class = 'SCHEDMAN_TASK'  " sbdst_classname
    i_profile =                 " tscma-profile
    i_node_id =                 " scmatree-node_id
    i_seqnr =                   " scmaoffice-seqnr
    i_mode =                    " char1
  EXCEPTIONS
    MODE_NOT_SUPPORTED = 1      "
    .  "  SCMA_BUFFER_OFFICE_KEYS

ABAP code example for Function Module SCMA_BUFFER_OFFICE_KEYS

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

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

SELECT single PROFILE 
  FROM TSCMA 
  INTO @DATA(ld_i_profile).

 

SELECT single NODE_ID 
  FROM SCMATREE 
  INTO @DATA(ld_i_node_id).

 

SELECT single SEQNR 
  FROM SCMAOFFICE 
  INTO @DATA(ld_i_seqnr).


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

CALL FUNCTION 'SCMA_BUFFER_OFFICE_KEYS'
  EXPORTING
    i_doc_id =                   ld_i_doc_id
*   i_doc_class =                ld_i_doc_class
    i_profile =                  ld_i_profile
    i_node_id =                  ld_i_node_id
    i_seqnr =                    ld_i_seqnr
    i_mode =                     ld_i_mode
  EXCEPTIONS
    MODE_NOT_SUPPORTED =         1
    .  "  SCMA_BUFFER_OFFICE_KEYS

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_i_doc_id
 
 TYPE BDS_DOCID ,
ld_i_doc_class
 
 TYPE SBDST_CLASSNAME ,
ld_i_profile
 
 TYPE TSCMA-PROFILE ,
ld_i_node_id
 
 TYPE SCMATREE-NODE_ID ,
ld_i_seqnr
 
 TYPE SCMAOFFICE-SEQNR ,
ld_i_mode
 
 TYPE CHAR1 .


ld_i_doc_id = 'Check type of data required'.
ld_i_doc_class = 'Check type of data required'.

SELECT single PROFILE 
  FROM TSCMA 
  INTO ld_i_profile.


SELECT single NODE_ID 
  FROM SCMATREE 
  INTO ld_i_node_id.


SELECT single SEQNR 
  FROM SCMAOFFICE 
  INTO ld_i_seqnr.

ld_i_mode = 'Check type of data required'.