SAP ISP_CHECK_PARTNER_CREATE Function Module for IS-M/SD: Create Business Partner Subscriber (Input Check)









ISP_CHECK_PARTNER_CREATE is a standard isp check partner create 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: Create Business Partner Subscriber (Input Check) 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 check partner create FM, simply by entering the name ISP_CHECK_PARTNER_CREATE 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_CHECK_PARTNER_CREATE 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_CHECK_PARTNER_CREATE'"IS-M/SD: Create Business Partner Subscriber (Input Check)
EXPORTING
* ABO_KU = "
* MK_POST_DATA = "
IABLAUF = "
* XFLG_ERROR_ON_HALFCODING = 'X' "
* I_KNA1 = "Customer Master (General Part)

IMPORTING
OBUKRS = "
OJGT_ANLEGEN = "
OJGTSADR = "
OKNA1 = "
OTJG43 = "
OORTSKUNDE = "

TABLES
TKNVI = "

EXCEPTIONS
ERROR = 1 ADDRESS_NOT_COMP = 2 WRONG_INPUT = 3
.



IMPORTING Parameters details for ISP_CHECK_PARTNER_CREATE

ABO_KU -

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

MK_POST_DATA -

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

IABLAUF -

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

XFLG_ERROR_ON_HALFCODING -

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

I_KNA1 - Customer Master (General Part)

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

EXPORTING Parameters details for ISP_CHECK_PARTNER_CREATE

OBUKRS -

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

OJGT_ANLEGEN -

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

OJGTSADR -

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

OKNA1 -

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

OTJG43 -

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

OORTSKUNDE -

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

TABLES Parameters details for ISP_CHECK_PARTNER_CREATE

TKNVI -

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

EXCEPTIONS details

ERROR -

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

ADDRESS_NOT_COMP -

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

WRONG_INPUT -

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

Copy and paste ABAP code example for ISP_CHECK_PARTNER_CREATE 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_error  TYPE STRING, "   
lt_tknvi  TYPE STANDARD TABLE OF KNVI, "   
lv_abo_ku  TYPE JKEXT_F_ABOKU, "   
lv_obukrs  TYPE TVKO-BUKRS, "   
lv_mk_post_data  TYPE JKEXT_F_MK, "   
lv_ojgt_anlegen  TYPE JGTGPNR-XGPSPE, "   
lv_address_not_comp  TYPE JGTGPNR, "   
lv_iablauf  TYPE JGD00_ABLAUF, "   
lv_ojgtsadr  TYPE JGTSADR, "   
lv_wrong_input  TYPE JGTSADR, "   
lv_okna1  TYPE KNA1, "   
lv_xflg_error_on_halfcoding  TYPE KNA1, "   'X'
lv_i_kna1  TYPE KNA1, "   
lv_otjg43  TYPE TJG43, "   
lv_oortskunde  TYPE RJGAU_MK-XORTSPR. "   

  CALL FUNCTION 'ISP_CHECK_PARTNER_CREATE'  "IS-M/SD: Create Business Partner Subscriber (Input Check)
    EXPORTING
         ABO_KU = lv_abo_ku
         MK_POST_DATA = lv_mk_post_data
         IABLAUF = lv_iablauf
         XFLG_ERROR_ON_HALFCODING = lv_xflg_error_on_halfcoding
         I_KNA1 = lv_i_kna1
    IMPORTING
         OBUKRS = lv_obukrs
         OJGT_ANLEGEN = lv_ojgt_anlegen
         OJGTSADR = lv_ojgtsadr
         OKNA1 = lv_okna1
         OTJG43 = lv_otjg43
         OORTSKUNDE = lv_oortskunde
    TABLES
         TKNVI = lt_tknvi
    EXCEPTIONS
        ERROR = 1
        ADDRESS_NOT_COMP = 2
        WRONG_INPUT = 3
. " ISP_CHECK_PARTNER_CREATE




ABAP code using 7.40 inline data declarations to call FM ISP_CHECK_PARTNER_CREATE

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 BUKRS FROM TVKO INTO @DATA(ld_obukrs).
 
 
"SELECT single XGPSPE FROM JGTGPNR INTO @DATA(ld_ojgt_anlegen).
 
 
 
 
 
 
DATA(ld_xflg_error_on_halfcoding) = 'X'.
 
 
 
"SELECT single XORTSPR FROM RJGAU_MK INTO @DATA(ld_oortskunde).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!