SAP Function Modules

comments icon Comments

JV_INTERCOMP_MAPPING_CHECK SAP Function module - Reconciliation of intercompany settings







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

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


Pattern for FM JV_INTERCOMP_MAPPING_CHECK - JV INTERCOMP MAPPING CHECK 





CALL FUNCTION 'JV_INTERCOMP_MAPPING_CHECK' "Reconciliation of  intercompany settings
  EXPORTING
    bukrs =                     " bukrs         Company Code
    date =                      " datum         Date (Cost Center and Equity groups are dependent on the date)
    cost_type = 1               " i             check cost center (1)/or internal order(2) or workbreakdown structure(3)
    type_of_call = ' '          " xfeld         Is caller RGJV_ICMAP_CHECK_ALL_TOP then = 'X'  or online check    '  '
*   mtype = 'I'                 " jv_cb_btc     Not optional for TYPE_OF_CALL =' '. Customizable messages. Default mesage type
*   cc_from =                   " kostl         Range Cost Center 'from'
*   cc_to =                     " kostl         Range Cost Center 'to'
*   intcocd =                   " jv_intcocd    Intercompany Code
*   cc_cut =                    " jv_cccut      Cutback cost center
*   order_from =                " jv_ordfrom    Order 'From' Range
*   order_to =                  " jv_ordto      Order 'To' Range
*   order_cut =                 " jv_ordcut     Cutback Order
*   wbs_from =                  " jv_projfro    Work breakdown structure element 'from'
*   wbs_to =                    " jv_projto     WBS element 'to' Range
*   wbs_cut =                   " jv_projcut    Cutback WBS
*   call_fm_count = 1           " i             How often is  FunctionModule called ? Has to start at 1. Which row  is checked
*   dispv = ' '                 " xfeld         Display also valid entries of check(for RGJV_ICMAP_CKECK_ALL)
  IMPORTING
    int_messagealv =            " jv_icmap_check  contains reconciliation results of T8JI with  T8J1*
    disp_range_co_obj =         " xfeld         For RGJV_ICMAP_CHECK_ALL to hide the column cost_object_to if no message 871
    .  "  JV_INTERCOMP_MAPPING_CHECK

ABAP code example for Function Module JV_INTERCOMP_MAPPING_CHECK





The ABAP code below is a full code listing to execute function module JV_INTERCOMP_MAPPING_CHECK 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_int_messagealv    TYPE JV_ICMAP_CHECK
,
ld_disp_range_co_obj    TYPE XFELD
.




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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

CALL FUNCTION 'JV_INTERCOMP_MAPPING_CHECK'
  EXPORTING
    bukrs =                      ld_bukrs
    date =                       ld_date
    cost_type =                  ld_cost_type
    type_of_call =               ld_type_of_call
*   mtype =                      ld_mtype
*   cc_from =                    ld_cc_from
*   cc_to =                      ld_cc_to
*   intcocd =                    ld_intcocd
*   cc_cut =                     ld_cc_cut
*   order_from =                 ld_order_from
*   order_to =                   ld_order_to
*   order_cut =                  ld_order_cut
*   wbs_from =                   ld_wbs_from
*   wbs_to =                     ld_wbs_to
*   wbs_cut =                    ld_wbs_cut
*   call_fm_count =              ld_call_fm_count
*   dispv =                      ld_dispv
  IMPORTING
    int_messagealv =             ld_int_messagealv
    disp_range_co_obj =          ld_disp_range_co_obj
    .  "  JV_INTERCOMP_MAPPING_CHECK

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_int_messagealv  TYPE JV_ICMAP_CHECK ,
ld_bukrs  TYPE BUKRS ,
ld_disp_range_co_obj  TYPE XFELD ,
ld_date  TYPE DATUM ,
ld_cost_type  TYPE I ,
ld_type_of_call  TYPE XFELD ,
ld_mtype  TYPE JV_CB_BTC ,
ld_cc_from  TYPE KOSTL ,
ld_cc_to  TYPE KOSTL ,
ld_intcocd  TYPE JV_INTCOCD ,
ld_cc_cut  TYPE JV_CCCUT ,
ld_order_from  TYPE JV_ORDFROM ,
ld_order_to  TYPE JV_ORDTO ,
ld_order_cut  TYPE JV_ORDCUT ,
ld_wbs_from  TYPE JV_PROJFRO ,
ld_wbs_to  TYPE JV_PROJTO ,
ld_wbs_cut  TYPE JV_PROJCUT ,
ld_call_fm_count  TYPE I ,
ld_dispv  TYPE XFELD .




ld_bukrs = 'Check type of data required'.
ld_date = 'Check type of data required'.
ld_cost_type = 'Check type of data required'.
ld_type_of_call = 'Check type of data required'.
ld_mtype = 'Check type of data required'.
ld_cc_from = 'Check type of data required'.
ld_cc_to = 'Check type of data required'.
ld_intcocd = 'Check type of data required'.
ld_cc_cut = 'Check type of data required'.
ld_order_from = 'Check type of data required'.
ld_order_to = 'Check type of data required'.
ld_order_cut = 'Check type of data required'.
ld_wbs_from = 'Check type of data required'.
ld_wbs_to = 'Check type of data required'.
ld_wbs_cut = 'Check type of data required'.
ld_call_fm_count = 'Check type of data required'.
ld_dispv = '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 JV_INTERCOMP_MAPPING_CHECK or its description.


   
 

JV_INTERCOMP_MAPPING_CHECK - Reconciliation of intercompany settings
JV_INSTALLED - 
JV_INSERT_T8JVBA - Insert records in t8jvba
JV_INSERT_ERROR_LOG - Write the information for reposting a document into the error log
JV_INSERT - Insert internal table into DB table
JV_INITIALISE_MESSAGE - JV Error Message Handling Initialisation