SAP Function Modules

comments icon Comments

MABJIT_CREATE_JIT_FROM_KAB SAP Function module







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

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


Pattern for FM MABJIT_CREATE_JIT_FROM_KAB - MABJIT CREATE JIT FROM KAB 





CALL FUNCTION 'MABJIT_CREATE_JIT_FROM_KAB' "
  EXPORTING
    pkhd =                      " pkhd
    pvbe =                      " pvbe
    badi_call_interface_gv =    " if_ex_pk_call_interface
  IMPORTING
    show_call_et =              " pkshowcall_tt
  TABLES
    jitoad_et =                 " jitoad
  CHANGING
    rmpkb =                     " rmpkb
    pkhds =                     " pkhd_save
    cuobj_cv =                  " inob-cuobj
    dspl =                      " c
    .  "  MABJIT_CREATE_JIT_FROM_KAB

ABAP code example for Function Module MABJIT_CREATE_JIT_FROM_KAB





The ABAP code below is a full code listing to execute function module MABJIT_CREATE_JIT_FROM_KAB 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_show_call_et    TYPE PKSHOWCALL_TT
,
it_jitoad_et    TYPE STANDARD TABLE OF JITOAD,"TABLES PARAM
wa_jitoad_et  LIKE LINE OF it_jitoad_et
.




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

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

SELECT single CUOBJ 
  FROM INOB 
  INTO @DATA(ld_cuobj_cv).


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

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

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

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

"populate fields of struture and append to itab
append wa_jitoad_et to it_jitoad_et.
.

CALL FUNCTION 'MABJIT_CREATE_JIT_FROM_KAB'
  EXPORTING
    pkhd =                       ld_pkhd
    pvbe =                       ld_pvbe
    badi_call_interface_gv =     ld_badi_call_interface_gv
  IMPORTING
    show_call_et =               ld_show_call_et
  TABLES
    jitoad_et =                  it_jitoad_et
  CHANGING
    rmpkb =                      ld_rmpkb
    pkhds =                      ld_pkhds
    cuobj_cv =                   ld_cuobj_cv
    dspl =                       ld_dspl
    .  "  MABJIT_CREATE_JIT_FROM_KAB

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_rmpkb  TYPE RMPKB ,
ld_show_call_et  TYPE PKSHOWCALL_TT ,
ld_pkhd  TYPE PKHD ,
it_jitoad_et  TYPE STANDARD TABLE OF JITOAD ,
wa_jitoad_et  LIKE LINE OF it_jitoad_et,
ld_pkhds  TYPE PKHD_SAVE ,
ld_pvbe  TYPE PVBE ,
ld_cuobj_cv  TYPE INOB-CUOBJ ,
ld_badi_call_interface_gv  TYPE IF_EX_PK_CALL_INTERFACE ,
ld_dspl  TYPE C .




ld_rmpkb = 'Check type of data required'.
ld_pkhd = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_jitoad_et to it_jitoad_et.
ld_pkhds = 'Check type of data required'.
ld_pvbe = 'Check type of data required'.

SELECT single CUOBJ 
  FROM INOB 
  INTO ld_cuobj_cv.

ld_badi_call_interface_gv = 'Check type of data required'.
ld_dspl = 'Check type of data required'.

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 MABJIT_CREATE_JIT_FROM_KAB or its description.


   
 

MABJIT_CREATE_JIT_FROM_KAB - 
MABASN_WE_PRODUKTIONSABRUF - 
MABASN_UPDATE_RELATION_MAB_ASN - 
MABASN_UPDATE_AT_TORD_CONFIRM - 
MABASN_SELECT_JIT_CALL - 
MABASN_REFRESH_PABASN -