SAP ISM_GET_IDCODE_AREA Function Module for Determine ID Code Area and Number Range for ID Code

Search SAP Function Modules

ISM_GET_IDCODE_AREA is a standard ism get idcode area SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine ID Code Area and Number Range for ID Code 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 ism get idcode area FM, simply by entering the name ISM_GET_IDCODE_AREA into the relevant SAP transaction such as SE37 or SE38.

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

Function ISM_GET_IDCODE_AREA 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 'ISM_GET_IDCODE_AREA'"Determine ID Code Area and Number Range for ID Code
  EXPORTING
   PVI_IDCODE =  "Identification Code
   PVI_IDCODETYPE =  "Type of identification code

 IMPORTING
   PVE_ISMIDCODEAREA =  "Identification Code Area
   PVE_ISMIDCDNUMAREA =  "Key for ID Code Number Range
   PVE_ISMIDCDNUMBER =  "Identification Code Number

EXCEPTIONS
   WRONG_CALL = 1    AREA_NOT_FOUND = 2    NUMAREA_NOT_FOUND = 3    WRONG_FORMAT = 4 

.

IMPORTING Parameters details for ISM_GET_IDCODE_AREA

PVI_IDCODE - Identification Code

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

PVI_IDCODETYPE - Type of identification code

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

EXPORTING Parameters details for ISM_GET_IDCODE_AREA

PVE_ISMIDCODEAREA - Identification Code Area

Data type: JPTIDCODE-ISMIDCODEAREA
Optional: No
Call by Reference: Yes

PVE_ISMIDCDNUMAREA - Key for ID Code Number Range

Data type: TJPIDCNUMAR-ISMIDCDNUMAREA
Optional: No
Call by Reference: Yes

PVE_ISMIDCDNUMBER - Identification Code Number

Data type: JPTIDCODE-ISMIDCODENUMBER
Optional: No
Call by Reference: Yes

EXCEPTIONS details

WRONG_CALL -

Data type:
Optional: No
Call by Reference: Yes

AREA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NUMAREA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

WRONG_FORMAT - Incorrect Format

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_GET_IDCODE_AREA 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.

ABAP code using 7.40 inline data declarations to call FM ISM_GET_IDCODE_AREA

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