SAP ISP_READ_DEBITOR Function Module for IS-M/SD: Read Customer in Non-SAP FI System

Search SAP Function Modules

ISP_READ_DEBITOR is a standard isp read debitor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Read Customer in Non-SAP FI System 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 isp read debitor FM, simply by entering the name ISP_READ_DEBITOR into the relevant SAP transaction such as SE37 or SE38.

Function Group: JG21
Program Name: SAPLJG21
Main Program: SAPLJG21
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ISP_READ_DEBITOR 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_READ_DEBITOR'"IS-M/SD: Read Customer in Non-SAP FI System
  EXPORTING
   BUKRS =  "Company Code
   FKUNNR =  "Customer Number
*  IISPGP =  "

EXCEPTIONS
   BUKRS_NOT_VALID = 1    NOT_EXISTS = 2 

.

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_SAPLJG21_001 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_002 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_003 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_004 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_005 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_006 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_007 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_008 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_009 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_010 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_011 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_012 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_013 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_014 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_015 IS-M Customer Synchronization
EXIT_SAPLJG21_016 IS-M Customer Synchronization
EXIT_SAPLJG21_017 IS-M Customer Synchronization
EXIT_SAPLJG21_101 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_102 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_103 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_104 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_105 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_107 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_108 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_110 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_111 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_112 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_113 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_114 Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC

IMPORTING Parameters details for ISP_READ_DEBITOR

BUKRS - Company Code

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

FKUNNR - Customer Number

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

IISPGP -

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

EXCEPTIONS details

BUKRS_NOT_VALID -

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

NOT_EXISTS -

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

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

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