SAP ISU_S_PARTNER_CREATE Function Module for INTERNAL: Create Business Partner









ISU_S_PARTNER_CREATE is a standard isu s 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 INTERNAL: Create 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 isu s partner create FM, simply by entering the name ISU_S_PARTNER_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: ES01
Program Name: SAPLES01
Main Program: SAPLES01
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISU_S_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 'ISU_S_PARTNER_CREATE'"INTERNAL: Create Business Partner
  EXPORTING
*  X_PARTNER =  "
*  X_WINDOW =  "
*  X_REL_KZ = 'X' "
*  X_MUSTER_KUN =  "
*  X_TESTRUN =  "
*  X_ACCEPT_ERROR = 'X' "Indicator
*  X_SAVE_TO_LEAVE = 'X' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  X_VALDT =  "
*  X_UPD_ONLINE =  "
*  X_TYPE =  "Business partner category
*  X_GROUP =  "
*  X_BPKIND =  "
*  X_FIRST_SCREEN =  "
*  X_NO_DIALOG =  "
*  X_AUTO =  "Automation data

 IMPORTING
   Y_DB_UPDATE =  "Indicator: Database Change
   Y_EXIT_TYPE =  "Return Mode
   Y_NEW_PARTNER =  "

TABLES
*  XT_RLTYPES =  "

EXCEPTIONS
   EXISTING = 1    FOREIGN_LOCK = 2    NOT_AUTHORIZED = 3    INPUT_ERROR = 4    GENERAL_FAULT = 5
.




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_SAPLES01_001 Duplicate Check: Business Partner
EXIT_SAPLES01_030 Before PBO Customer Subscreen
EXIT_SAPLES01_031 After PAI Customer Subscreen

IMPORTING Parameters details for ISU_S_PARTNER_CREATE

X_PARTNER -

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

X_WINDOW -

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

X_REL_KZ -

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

X_MUSTER_KUN -

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

X_TESTRUN -

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

X_ACCEPT_ERROR - Indicator

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

X_SAVE_TO_LEAVE - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

X_VALDT -

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

X_UPD_ONLINE -

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

X_TYPE - Business partner category

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

X_GROUP -

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

X_BPKIND -

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

X_FIRST_SCREEN -

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

X_NO_DIALOG -

Data type: REGEN-NO_DIALOG
Optional: Yes
Call by Reference: Yes

X_AUTO - Automation data

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

EXPORTING Parameters details for ISU_S_PARTNER_CREATE

Y_DB_UPDATE - Indicator: Database Change

Data type: REGEN-DB_UPDATE
Optional: No
Call by Reference: Yes

Y_EXIT_TYPE - Return Mode

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

Y_NEW_PARTNER -

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

TABLES Parameters details for ISU_S_PARTNER_CREATE

XT_RLTYPES -

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

EXCEPTIONS details

EXISTING - Object Already Exists

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

FOREIGN_LOCK - Object is Currently Locked

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

NOT_AUTHORIZED - Missing Authorization

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

INPUT_ERROR - Invalid Automation Data

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

GENERAL_FAULT - Other

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

Copy and paste ABAP code example for ISU_S_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_existing  TYPE STRING, "   
lv_x_partner  TYPE BUT000-PARTNER, "   
lt_xt_rltypes  TYPE STANDARD TABLE OF BUP_PARTNERROLES, "   
lv_y_db_update  TYPE REGEN-DB_UPDATE, "   
lv_x_window  TYPE REGEN-KENNZX, "   
lv_x_rel_kz  TYPE REGEN-KENNZX, "   'X'
lv_x_muster_kun  TYPE EKUND-MUSTER_KUN, "   
lv_x_testrun  TYPE REGEN-KENNZX, "   
lv_x_accept_error  TYPE REGEN-KENNZX, "   'X'
lv_x_save_to_leave  TYPE BOOLE-BOOLE, "   'X'
lv_x_valdt  TYPE BUSHDR_DI-VALDT, "   
lv_y_exit_type  TYPE REGEN-EXIT_TYPE, "   
lv_foreign_lock  TYPE REGEN, "   
lv_x_upd_online  TYPE REGEN-UPD_ONLINE, "   
lv_y_new_partner  TYPE ISU01_PARTNER_DATA, "   
lv_not_authorized  TYPE ISU01_PARTNER_DATA, "   
lv_x_type  TYPE BUS000FLDS-TYPE, "   
lv_input_error  TYPE BUS000FLDS, "   
lv_x_group  TYPE TB001-BU_GROUP, "   
lv_general_fault  TYPE TB001, "   
lv_x_bpkind  TYPE BUT000-BPKIND, "   
lv_x_first_screen  TYPE REGEN-KENNZX, "   
lv_x_no_dialog  TYPE REGEN-NO_DIALOG, "   
lv_x_auto  TYPE ISU01_PARTNER_AUTO. "   

  CALL FUNCTION 'ISU_S_PARTNER_CREATE'  "INTERNAL: Create Business Partner
    EXPORTING
         X_PARTNER = lv_x_partner
         X_WINDOW = lv_x_window
         X_REL_KZ = lv_x_rel_kz
         X_MUSTER_KUN = lv_x_muster_kun
         X_TESTRUN = lv_x_testrun
         X_ACCEPT_ERROR = lv_x_accept_error
         X_SAVE_TO_LEAVE = lv_x_save_to_leave
         X_VALDT = lv_x_valdt
         X_UPD_ONLINE = lv_x_upd_online
         X_TYPE = lv_x_type
         X_GROUP = lv_x_group
         X_BPKIND = lv_x_bpkind
         X_FIRST_SCREEN = lv_x_first_screen
         X_NO_DIALOG = lv_x_no_dialog
         X_AUTO = lv_x_auto
    IMPORTING
         Y_DB_UPDATE = lv_y_db_update
         Y_EXIT_TYPE = lv_y_exit_type
         Y_NEW_PARTNER = lv_y_new_partner
    TABLES
         XT_RLTYPES = lt_xt_rltypes
    EXCEPTIONS
        EXISTING = 1
        FOREIGN_LOCK = 2
        NOT_AUTHORIZED = 3
        INPUT_ERROR = 4
        GENERAL_FAULT = 5
. " ISU_S_PARTNER_CREATE




ABAP code using 7.40 inline data declarations to call FM ISU_S_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 PARTNER FROM BUT000 INTO @DATA(ld_x_partner).
 
 
"SELECT single DB_UPDATE FROM REGEN INTO @DATA(ld_y_db_update).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_window).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_rel_kz).
DATA(ld_x_rel_kz) = 'X'.
 
"SELECT single MUSTER_KUN FROM EKUND INTO @DATA(ld_x_muster_kun).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_testrun).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_accept_error).
DATA(ld_x_accept_error) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_save_to_leave).
DATA(ld_x_save_to_leave) = 'X'.
 
"SELECT single VALDT FROM BUSHDR_DI INTO @DATA(ld_x_valdt).
 
"SELECT single EXIT_TYPE FROM REGEN INTO @DATA(ld_y_exit_type).
 
 
"SELECT single UPD_ONLINE FROM REGEN INTO @DATA(ld_x_upd_online).
 
 
 
"SELECT single TYPE FROM BUS000FLDS INTO @DATA(ld_x_type).
 
 
"SELECT single BU_GROUP FROM TB001 INTO @DATA(ld_x_group).
 
 
"SELECT single BPKIND FROM BUT000 INTO @DATA(ld_x_bpkind).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_first_screen).
 
"SELECT single NO_DIALOG FROM REGEN INTO @DATA(ld_x_no_dialog).
 
 


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!