KKPI_SESSION_COSTING_CREATE SAP Function module

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

Associated Function Group: KKPI
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM KKPI_SESSION_COSTING_CREATE - KKPI SESSION COSTING CREATE

CALL FUNCTION 'KKPI_SESSION_COSTING_CREATE' "
  EXPORTING
*   client = SY-MANDT           " apqi-mandant
*   user = SY-UNAME             " apqi-userid
*   group = 'BATCHMAP'          " apqi-groupid
*   keep = SPACE                " apqi-qerase
*   holddate = SY-DATUM         " apqi-startdate
    it_transfer_data =          " kkpi_transfer_data
  EXCEPTIONS
    CALL_TRANSACTION_ERROR = 1  "
    NO_TRANSFER_DATA = 2        "
    WRONG_MODE_PARAMETER = 3    "
    .  "  KKPI_SESSION_COSTING_CREATE

ABAP code example for Function Module KKPI_SESSION_COSTING_CREATE

The ABAP code below is a full code listing to execute function module KKPI_SESSION_COSTING_CREATE 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).

 

SELECT single MANDANT 
  FROM APQI 
  INTO @DATA(ld_client).

 

SELECT single USERID 
  FROM APQI 
  INTO @DATA(ld_user).

 

SELECT single GROUPID 
  FROM APQI 
  INTO @DATA(ld_group).

 

SELECT single QERASE 
  FROM APQI 
  INTO @DATA(ld_keep).

 

SELECT single STARTDATE 
  FROM APQI 
  INTO @DATA(ld_holddate).


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

CALL FUNCTION 'KKPI_SESSION_COSTING_CREATE'
  EXPORTING
*   client =                     ld_client
*   user =                       ld_user
*   group =                      ld_group
*   keep =                       ld_keep
*   holddate =                   ld_holddate
    it_transfer_data =           ld_it_transfer_data
  EXCEPTIONS
    CALL_TRANSACTION_ERROR =     1
    NO_TRANSFER_DATA =           2
    WRONG_MODE_PARAMETER =       3
    .  "  KKPI_SESSION_COSTING_CREATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
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_client
 
 TYPE APQI-MANDANT ,
ld_user
 
 TYPE APQI-USERID ,
ld_group
 
 TYPE APQI-GROUPID ,
ld_keep
 
 TYPE APQI-QERASE ,
ld_holddate
 
 TYPE APQI-STARTDATE ,
ld_it_transfer_data
 
 TYPE KKPI_TRANSFER_DATA .



SELECT single MANDANT 
  FROM APQI 
  INTO ld_client.


SELECT single USERID 
  FROM APQI 
  INTO ld_user.


SELECT single GROUPID 
  FROM APQI 
  INTO ld_group.


SELECT single QERASE 
  FROM APQI 
  INTO ld_keep.


SELECT single STARTDATE 
  FROM APQI 
  INTO ld_holddate.

ld_it_transfer_data = 'Check type of data required'.