SAP COMPUTE_KIDMOD11 Function Module for Norway: Modulus 11 check for KID number









COMPUTE_KIDMOD11 is a standard compute kidmod11 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Norway: Modulus 11 check for KID number 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 compute kidmod11 FM, simply by entering the name COMPUTE_KIDMOD11 into the relevant SAP transaction such as SE37 or SE38.

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



Function COMPUTE_KIDMOD11 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 'COMPUTE_KIDMOD11'"Norway: Modulus 11 check for KID number
EXPORTING
* I_CHECK_CORRECT = 'X' "Flag: 'X' - check if number correct

CHANGING
C_VALUE = "Number to process

EXCEPTIONS
NUMBER_TOO_LONG = 1 NUMBER_TOO_SHORT = 2 NUMBER_NOT_VALID = 3 REMAINDER_10 = 4 NUMBER_NOT_CORRECT = 5
.



IMPORTING Parameters details for COMPUTE_KIDMOD11

I_CHECK_CORRECT - Flag: 'X' - check if number correct

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

CHANGING Parameters details for COMPUTE_KIDMOD11

C_VALUE - Number to process

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

EXCEPTIONS details

NUMBER_TOO_LONG -

Data type:
Optional: No
Call by Reference: Yes

NUMBER_TOO_SHORT -

Data type:
Optional: No
Call by Reference: Yes

NUMBER_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

REMAINDER_10 -

Data type:
Optional: No
Call by Reference: Yes

NUMBER_NOT_CORRECT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COMPUTE_KIDMOD11 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_c_value  TYPE STRING, "   
lv_i_check_correct  TYPE STRING, "   'X'
lv_number_too_long  TYPE STRING, "   
lv_number_too_short  TYPE STRING, "   
lv_number_not_valid  TYPE STRING, "   
lv_remainder_10  TYPE STRING, "   
lv_number_not_correct  TYPE STRING. "   

  CALL FUNCTION 'COMPUTE_KIDMOD11'  "Norway: Modulus 11 check for KID number
    EXPORTING
         I_CHECK_CORRECT = lv_i_check_correct
    CHANGING
         C_VALUE = lv_c_value
    EXCEPTIONS
        NUMBER_TOO_LONG = 1
        NUMBER_TOO_SHORT = 2
        NUMBER_NOT_VALID = 3
        REMAINDER_10 = 4
        NUMBER_NOT_CORRECT = 5
. " COMPUTE_KIDMOD11




ABAP code using 7.40 inline data declarations to call FM COMPUTE_KIDMOD11

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_i_check_correct) = 'X'.
 
 
 
 
 
 


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!