SAP ISP_UPDATE_KREDITOR Function Module for IS-M/SD: Change Vendor from IS-M/SD to Another ERP System
ISP_UPDATE_KREDITOR is a standard isp update kreditor 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: Change Vendor from IS-M/SD to Another ERP 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 update kreditor FM, simply by entering the name ISP_UPDATE_KREDITOR 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_UPDATE_KREDITOR 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_UPDATE_KREDITOR'"IS-M/SD: Change Vendor from IS-M/SD to Another ERP System.
EXPORTING
IISPKA = "
IISPKB = "
IISPGP = "
IRJGFADDR1 = "IS-M: Transfer Structure for Address Data for CAM
IMPORTING
MESSAGE = "
FLIFNR = "
RETCODE = "
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_UPDATE_KREDITOR
IISPKA -
Data type: RJGF04Optional: No
Call by Reference: No ( called with pass by value option)
IISPKB -
Data type: RJGF05Optional: No
Call by Reference: No ( called with pass by value option)
IISPGP -
Data type: RJGF01Optional: No
Call by Reference: No ( called with pass by value option)
IRJGFADDR1 - IS-M: Transfer Structure for Address Data for CAM
Data type: RJGFADDR1Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_UPDATE_KREDITOR
MESSAGE -
Data type: RJMSG_R2Optional: No
Call by Reference: No ( called with pass by value option)
FLIFNR -
Data type: RJGF01-FLIFNROptional: No
Call by Reference: No ( called with pass by value option)
RETCODE -
Data type: RJLG21-R2_SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_UPDATE_KREDITOR 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_iispka | TYPE RJGF04, " | |||
| lv_message | TYPE RJMSG_R2, " | |||
| lv_flifnr | TYPE RJGF01-FLIFNR, " | |||
| lv_iispkb | TYPE RJGF05, " | |||
| lv_iispgp | TYPE RJGF01, " | |||
| lv_retcode | TYPE RJLG21-R2_SUBRC, " | |||
| lv_irjgfaddr1 | TYPE RJGFADDR1. " |
|   CALL FUNCTION 'ISP_UPDATE_KREDITOR' "IS-M/SD: Change Vendor from IS-M/SD to Another ERP System |
| EXPORTING | ||
| IISPKA | = lv_iispka | |
| IISPKB | = lv_iispkb | |
| IISPGP | = lv_iispgp | |
| IRJGFADDR1 | = lv_irjgfaddr1 | |
| IMPORTING | ||
| MESSAGE | = lv_message | |
| FLIFNR | = lv_flifnr | |
| RETCODE | = lv_retcode | |
| . " ISP_UPDATE_KREDITOR | ||
ABAP code using 7.40 inline data declarations to call FM ISP_UPDATE_KREDITOR
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.| "SELECT single FLIFNR FROM RJGF01 INTO @DATA(ld_flifnr). | ||||
| "SELECT single R2_SUBRC FROM RJLG21 INTO @DATA(ld_retcode). | ||||
Search for further information about these or an SAP related objects