SAP ISP_KREDITOR_FSYS_MAINTAIN Function Module for IS-M: Synchronization for Non-SAP System: Vendor

Search SAP Function Modules

ISP_KREDITOR_FSYS_MAINTAIN is a standard isp kreditor fsys maintain 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: Synchronization for Non-SAP System: Vendor 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 kreditor fsys maintain FM, simply by entering the name ISP_KREDITOR_FSYS_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_KREDITOR_FSYS_MAINTAIN 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_KREDITOR_FSYS_MAINTAIN'"IS-M: Synchronization for Non-SAP System: Vendor
  EXPORTING
   EVENT_IN =  "Action to Execute
   JGTGPNR_IN =  "
   JGTSADR_IN =  "Address Data
   LFA1_IN =  "
   LFB1_IN =  "Customer Data
   LFBK_IN =  "
   WAERS =  "
*  APPKL_IN = 'J' "

 IMPORTING
   FLIFNR_OUT =  "
   RC =  "

.

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_SAPLJG20_002 IS-M/SD: User Exit for BP Transfer R/3 -> R/2 for Additional Field
EXIT_SAPLJG20_003 IS-M/SD: User Exit for BP Transfer R/3 -> R/2 for Additional Field

IMPORTING Parameters details for ISP_KREDITOR_FSYS_MAINTAIN

EVENT_IN - Action to Execute

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

JGTGPNR_IN -

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

JGTSADR_IN - Address Data

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

LFA1_IN -

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

LFB1_IN - Customer Data

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

LFBK_IN -

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

WAERS -

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

APPKL_IN -

Data type: TJU01-APPKL
Default: 'J'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISP_KREDITOR_FSYS_MAINTAIN

FLIFNR_OUT -

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

RC -

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

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

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