SAP JV_MCC_CHECK Function Module for Multiple company code selection - checks









JV_MCC_CHECK is a standard jv mcc check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Multiple company code selection - checks processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for jv mcc check FM, simply by entering the name JV_MCC_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: GJU1
Program Name: SAPLGJU1
Main Program: SAPLGJU1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function JV_MCC_CHECK pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'JV_MCC_CHECK'"Multiple company code selection - checks
  EXPORTING
   I_TEST =  "Test or update
   I_PROCESS_CODE =  "Process code
*  I_T_BUKRS =  "JVA Company code range

 IMPORTING
   E_MCC_USED =  "Four-digit number
   E_T_MCC =  "Table of company codes
   E_NOAUTH =  "No authorisation

CHANGING
*  C_T_VENTURE =  "JVA Venture Range
*  C_T_PARTNER =  "JVA Partner Range
*  C_T_EGROUP =  "JVA Equity Group Range
*  C_T_JOA =  "JVA JOA Range

EXCEPTIONS
   NO_SELECTION = 1    INCONSISTENT_SELECTION = 2
.



IMPORTING Parameters details for JV_MCC_CHECK

I_TEST - Test or update

Data type: CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

I_PROCESS_CODE - Process code

Data type: CHAR10
Optional: No
Call by Reference: Yes

I_T_BUKRS - JVA Company code range

Data type: T8J_TBUKRS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for JV_MCC_CHECK

E_MCC_USED - Four-digit number

Data type: NUM4
Optional: No
Call by Reference: Yes

E_T_MCC - Table of company codes

Data type: JV_T_MCC
Optional: No
Call by Reference: Yes

E_NOAUTH - No authorisation

Data type: N
Optional: No
Call by Reference: Yes

CHANGING Parameters details for JV_MCC_CHECK

C_T_VENTURE - JVA Venture Range

Data type: T8J_TVENTURE
Optional: Yes
Call by Reference: Yes

C_T_PARTNER - JVA Partner Range

Data type: T8J_TPARTNER
Optional: Yes
Call by Reference: Yes

C_T_EGROUP - JVA Equity Group Range

Data type: T8J_TEGROUP
Optional: Yes
Call by Reference: Yes

C_T_JOA - JVA JOA Range

Data type: T8J_TJOA
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_SELECTION - No company code selected

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_SELECTION - Extra selctions with one company code only

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for JV_MCC_CHECK Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_i_test  TYPE CHAR1, "   
lv_e_mcc_used  TYPE NUM4, "   
lv_c_t_venture  TYPE T8J_TVENTURE, "   
lv_no_selection  TYPE T8J_TVENTURE, "   
lv_e_t_mcc  TYPE JV_T_MCC, "   
lv_c_t_partner  TYPE T8J_TPARTNER, "   
lv_i_process_code  TYPE CHAR10, "   
lv_inconsistent_selection  TYPE CHAR10, "   
lv_e_noauth  TYPE N, "   
lv_i_t_bukrs  TYPE T8J_TBUKRS, "   
lv_c_t_egroup  TYPE T8J_TEGROUP, "   
lv_c_t_joa  TYPE T8J_TJOA. "   

  CALL FUNCTION 'JV_MCC_CHECK'  "Multiple company code selection - checks
    EXPORTING
         I_TEST = lv_i_test
         I_PROCESS_CODE = lv_i_process_code
         I_T_BUKRS = lv_i_t_bukrs
    IMPORTING
         E_MCC_USED = lv_e_mcc_used
         E_T_MCC = lv_e_t_mcc
         E_NOAUTH = lv_e_noauth
    CHANGING
         C_T_VENTURE = lv_c_t_venture
         C_T_PARTNER = lv_c_t_partner
         C_T_EGROUP = lv_c_t_egroup
         C_T_JOA = lv_c_t_joa
    EXCEPTIONS
        NO_SELECTION = 1
        INCONSISTENT_SELECTION = 2
. " JV_MCC_CHECK




ABAP code using 7.40 inline data declarations to call FM JV_MCC_CHECK

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!