SAP ISP_MC_STATISTICS_C_O_LOGGING Function Module for









ISP_MC_STATISTICS_C_O_LOGGING is a standard isp mc statistics c o logging SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 isp mc statistics c o logging FM, simply by entering the name ISP_MC_STATISTICS_C_O_LOGGING into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_MC_STATISTICS_C_O_LOGGING 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 'ISP_MC_STATISTICS_C_O_LOGGING'"
EXPORTING
* CONTROL = ' ' "
ZEITP = "

TABLES
MCINF = "
XMCJKAK = "
XMCJKAP = "
XMCJKEP = "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJKMC_001 IS-M / MDIS: User Exit for Correction Order Header Data - OBSOLETE
EXIT_SAPLJKMC_002 IS-M / MDIS: User Exit for Correction Order Item Data - OBSOLETE
EXIT_SAPLJKMC_003 IS-M / MDIS: User Exit for Correction Order Schedule Lines - OBSOLETE
EXIT_SAPLJKMC_004 IS-M / MDIS: User Exit for Sales Order Header Data - OBSOLETE
EXIT_SAPLJKMC_005 IS-M / MDIS: User Exit for Sales Order Item Data - OBSOLETE
EXIT_SAPLJKMC_006 IS-M / MDIS: User Exit for Sales Order Schedule Lines - OBSOLETE
EXIT_SAPLJKMC_007 IS-M / MDIS: User Exit for Correction Order Partner/DVia. - OBSOLETE
EXIT_SAPLJKMC_100 IS-M / MDIS: User Exit for Sales Order Header Data
EXIT_SAPLJKMC_101 IS-M / MDIS: User Exit for Sales Order Item Data
EXIT_SAPLJKMC_102 IS-M / MDIS: User Exit for Sales Order Schedule Line Data
EXIT_SAPLJKMC_103 IS-M / MDIS: User Exit for Correction Order for Partner/DVia.Assgments
EXIT_SAPLJKMC_110 IS-M / MDIS: User Exit for Correction Order Header Data
EXIT_SAPLJKMC_111 IS-M / MDIS: User Exit for Correction Order Item Data
EXIT_SAPLJKMC_112 IS-M / MDIS: User Exit for Correction Order Schedule Line Data

IMPORTING Parameters details for ISP_MC_STATISTICS_C_O_LOGGING

CONTROL -

Data type: MCCONTROL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ZEITP -

Data type: TMC5-ZEITP
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ISP_MC_STATISTICS_C_O_LOGGING

MCINF -

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

XMCJKAK -

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

XMCJKAP -

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

XMCJKEP -

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

Copy and paste ABAP code example for ISP_MC_STATISTICS_C_O_LOGGING 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:
lt_mcinf  TYPE STANDARD TABLE OF MCSOINF, "   
lv_control  TYPE MCCONTROL, "   SPACE
lv_zeitp  TYPE TMC5-ZEITP, "   
lt_xmcjkak  TYPE STANDARD TABLE OF MCJKAKB, "   
lt_xmcjkap  TYPE STANDARD TABLE OF MCJKAPB, "   
lt_xmcjkep  TYPE STANDARD TABLE OF MCJKEPB. "   

  CALL FUNCTION 'ISP_MC_STATISTICS_C_O_LOGGING'  "
    EXPORTING
         CONTROL = lv_control
         ZEITP = lv_zeitp
    TABLES
         MCINF = lt_mcinf
         XMCJKAK = lt_xmcjkak
         XMCJKAP = lt_xmcjkap
         XMCJKEP = lt_xmcjkep
. " ISP_MC_STATISTICS_C_O_LOGGING




ABAP code using 7.40 inline data declarations to call FM ISP_MC_STATISTICS_C_O_LOGGING

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.

 
DATA(ld_control) = ' '.
 
"SELECT single ZEITP FROM TMC5 INTO @DATA(ld_zeitp).
 
 
 
 


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!