MANCONTRACT_TRANSFER2BUFFER SAP Function module

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

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

Pattern for FM MANCONTRACT_TRANSFER2BUFFER - MANCONTRACT TRANSFER2BUFFER

CALL FUNCTION 'MANCONTRACT_TRANSFER2BUFFER' "
* EXPORTING
*   iv_reset_buffer = 'X'       " xfeld
*   iv_max_buffer_size = 100    " i
*   iv_search_buffer = SPACE    " xfeld
*   is_vivw01 =                 " vivw01
* TABLES
*   it_vivw01 =                 " vivw01
  EXCEPTIONS
    TWO_IMPORT_PARAMETERS = 1   "
    BUFFER_INCONSISTENCY = 2    "
    INDEX_INCONSISTENCY = 3     "
    RECORD_ALREADY_EXISTS = 4   "
    OTHER_ERROR_INDEX_PUSH = 5  "
    .  "  MANCONTRACT_TRANSFER2BUFFER

ABAP code example for Function Module MANCONTRACT_TRANSFER2BUFFER

The ABAP code below is a full code listing to execute function module MANCONTRACT_TRANSFER2BUFFER 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_it_vivw01  
 
 TYPE STANDARD TABLE OF VIVW01,"TABLES PARAM
wa_it_vivw01
 
 LIKE LINE OF it_it_vivw01
.


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

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

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

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

"populate fields of struture and append to itab
append wa_it_vivw01 to it_it_vivw01.
.

CALL FUNCTION 'MANCONTRACT_TRANSFER2BUFFER'
* EXPORTING
*   iv_reset_buffer =            ld_iv_reset_buffer
*   iv_max_buffer_size =         ld_iv_max_buffer_size
*   iv_search_buffer =           ld_iv_search_buffer
*   is_vivw01 =                  ld_is_vivw01
* TABLES
*   it_vivw01 =                  it_it_vivw01
  EXCEPTIONS
    TWO_IMPORT_PARAMETERS =      1
    BUFFER_INCONSISTENCY =       2
    INDEX_INCONSISTENCY =        3
    RECORD_ALREADY_EXISTS =      4
    OTHER_ERROR_INDEX_PUSH =     5
    .  "  MANCONTRACT_TRANSFER2BUFFER

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
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "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_iv_reset_buffer
 
 TYPE XFELD ,
it_it_vivw01
 
 TYPE STANDARD TABLE OF VIVW01 ,
wa_it_vivw01
 
 LIKE LINE OF it_it_vivw01,
ld_iv_max_buffer_size
 
 TYPE I ,
ld_iv_search_buffer
 
 TYPE XFELD ,
ld_is_vivw01
 
 TYPE VIVW01 .


ld_iv_reset_buffer = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_it_vivw01 to it_it_vivw01.
ld_iv_max_buffer_size = 'Check type of data required'.
ld_iv_search_buffer = 'Check type of data required'.
ld_is_vivw01 = 'Check type of data required'.