SAP Function Modules

EXIT_SAPMM07M_010 SAP Function module - Propose Batch / Transfer Batch







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

Associated Function Group: XMBC
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM EXIT_SAPMM07M_010 - EXIT SAPMM07M 010





CALL FUNCTION 'EXIT_SAPMM07M_010' "Propose Batch / Transfer Batch
  EXPORTING
    i_mseg =                    " mseg          Document Segment: Material
    i_vm07m =                   " vm07m         Fields: Update Control of Module Pool SAPMM07M
    i_dm07m =                   " dm07m         Dialog Control Fields for Module Pool SAPMM07M
    i_mkpf =                    " mkpf          Header: Material Document
    i_transfer =                " dm07m-kzuml   Stock Transfer/Transfer Posting
  IMPORTING
    e_charg =                   " mcha-charg    Batch Number
    .  "  EXIT_SAPMM07M_010

ABAP code example for Function Module EXIT_SAPMM07M_010





The ABAP code below is a full code listing to execute function module EXIT_SAPMM07M_010 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_charg  TYPE MCHA-CHARG .

DATA(ld_i_mseg) = 'Check type of data required'.
DATA(ld_i_vm07m) = 'Check type of data required'.
DATA(ld_i_dm07m) = 'Check type of data required'.
DATA(ld_i_mkpf) = 'Check type of data required'.

DATA(ld_i_transfer) = some text here . CALL FUNCTION 'EXIT_SAPMM07M_010' EXPORTING i_mseg = ld_i_mseg i_vm07m = ld_i_vm07m i_dm07m = ld_i_dm07m i_mkpf = ld_i_mkpf i_transfer = ld_i_transfer IMPORTING e_charg = ld_e_charg . " EXIT_SAPMM07M_010
IF SY-SUBRC EQ 0. "All OK 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_charg  TYPE MCHA-CHARG ,
ld_i_mseg  TYPE MSEG ,
ld_i_vm07m  TYPE VM07M ,
ld_i_dm07m  TYPE DM07M ,
ld_i_mkpf  TYPE MKPF ,
ld_i_transfer  TYPE DM07M-KZUML .

ld_i_mseg = 'Check type of data required'.
ld_i_vm07m = 'Check type of data required'.
ld_i_dm07m = 'Check type of data required'.
ld_i_mkpf = 'Check type of data required'.

ld_i_transfer = some text here

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name EXIT_SAPMM07M_010 or its description.