SAP ISP_PARTNER_SAVE_COMPLETE Function Module for Save Business Partner

Search SAP Function Modules

ISP_PARTNER_SAVE_COMPLETE is a standard isp partner save complete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save Business Partner 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 partner save complete FM, simply by entering the name ISP_PARTNER_SAVE_COMPLETE into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_PARTNER_SAVE_COMPLETE 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_PARTNER_SAVE_COMPLETE'"Save Business Partner
  EXPORTING
   ABO_KU =  "
*  MK_DATA =  "IS-M/AM: BP Data Transfer - M/AM
*  XTEST =  "
*  XUPDATE_TASK =  "
*  IN_ADRP =  "Include structure with ADRP attributes
*  IN_ADNM =  "Include structure with name attributes of the ADRC address
*  IN_ADRC =  "Include structure with ADRC attributes without name fields
*  IN_COMMUNICATION =  "IS-M: Business Partner Fast Creation - Communication
*  IN_BP_TYPE = ' ' "Business Partner Category

 IMPORTING
   GPNR =  "

EXCEPTIONS
   DATA_NOT_CORRECT = 1    NOT_SAVED = 2    BP_ALREADY_EXIST = 3 

.

IMPORTING Parameters details for ISP_PARTNER_SAVE_COMPLETE

ABO_KU -

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

MK_DATA - IS-M/AM: BP Data Transfer - M/AM

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

XTEST -

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

XUPDATE_TASK -

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

IN_ADRP - Include structure with ADRP attributes

Data type: ADRP_STRUC
Optional: Yes
Call by Reference: Yes

IN_ADNM - Include structure with name attributes of the ADRC address

Data type: ADNM_STRUC
Optional: Yes
Call by Reference: Yes

IN_ADRC - Include structure with ADRC attributes without name fields

Data type: ADRC_STRUC
Optional: Yes
Call by Reference: Yes

IN_COMMUNICATION - IS-M: Business Partner Fast Creation - Communication

Data type: RJG_BP_CF_COMMUNICATION
Optional: Yes
Call by Reference: Yes

IN_BP_TYPE - Business Partner Category

Data type: BU_TYPE
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISP_PARTNER_SAVE_COMPLETE

GPNR -

Data type: JGTGPNR-GPNR
Optional: No
Call by Reference: Yes

EXCEPTIONS details

DATA_NOT_CORRECT -

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

NOT_SAVED -

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

BP_ALREADY_EXIST -

Data type:
Optional: No
Call by Reference: Yes

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

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