SAP Function Modules

comments icon Comments

J_3K_GET_PAYMBASE SAP Function module - Return contract string







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

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


Pattern for FM J_3K_GET_PAYMBASE - J 3K GET PAYMBASE 





CALL FUNCTION 'J_3K_GET_PAYMBASE' "Return contract string
  EXPORTING
    i_tree_type =               " dmee_treetype  DMEE: tree type
    i_tree_id =                 " dmee_treeid   DMEE: unique description for a DMEE format tree
    i_item =                    "
    i_param =                   "
    i_uparam =                  "
    i_extension =               " dmee_exit_interface  DMEE: Extended Interface for Exit Module
  IMPORTING
    o_value =                   "
    c_value =                   "
    n_value =                   "
    p_value =                   "
  TABLES
    i_tab =                     "
    .  "  J_3K_GET_PAYMBASE

ABAP code example for Function Module J_3K_GET_PAYMBASE





The ABAP code below is a full code listing to execute function module J_3K_GET_PAYMBASE 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_o_value    TYPE STRING
,
ld_c_value    TYPE STRING
,
ld_n_value    TYPE STRING
,
ld_p_value    TYPE STRING
,
it_i_tab    TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_i_tab  LIKE LINE OF it_i_tab
.




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

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

DATA(ld_i_item) = 'some text here'.

DATA(ld_i_param) = 'some text here'.

DATA(ld_i_uparam) = 'some text here'.

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

"populate fields of struture and append to itab
append wa_i_tab to it_i_tab.
.

CALL FUNCTION 'J_3K_GET_PAYMBASE'
  EXPORTING
    i_tree_type =                ld_i_tree_type
    i_tree_id =                  ld_i_tree_id
    i_item =                     ld_i_item
    i_param =                    ld_i_param
    i_uparam =                   ld_i_uparam
    i_extension =                ld_i_extension
  IMPORTING
    o_value =                    ld_o_value
    c_value =                    ld_c_value
    n_value =                    ld_n_value
    p_value =                    ld_p_value
  TABLES
    i_tab =                      it_i_tab
    .  "  J_3K_GET_PAYMBASE

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_o_value  TYPE STRING ,
ld_i_tree_type  TYPE DMEE_TREETYPE ,
it_i_tab  TYPE STANDARD TABLE OF STRING ,
wa_i_tab  LIKE LINE OF it_i_tab,
ld_c_value  TYPE STRING ,
ld_i_tree_id  TYPE DMEE_TREEID ,
ld_n_value  TYPE STRING ,
ld_i_item  TYPE STRING ,
ld_p_value  TYPE STRING ,
ld_i_param  TYPE STRING ,
ld_i_uparam  TYPE STRING ,
ld_i_extension  TYPE DMEE_EXIT_INTERFACE .




ld_i_tree_type = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_i_tab to it_i_tab.
ld_i_tree_id = 'Check type of data required'.
ld_i_item = 'some text here'.
ld_i_param = 'some text here'.
ld_i_uparam = 'some text here'.
ld_i_extension = '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 J_3K_GET_PAYMBASE or its description.


   
 

J_3K_GET_PAYMBASE - Return contract string
J_3K_GET_PAVAL - Get ID number(paval) of Payer
J_3K_GET_INIT - Get identification
J_3K_GET_IDENT - Get identification
J_3K_GET_COUNTER - Get daily counter
J_3K_GET_CONTRACT - Return contract string