SAP ISU_S_PARTNER_DISPLAY Function Module for INTERNAL: Display Business Partner

Search SAP Function Modules

ISU_S_PARTNER_DISPLAY is a standard isu s partner display 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: Display 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 display FM, simply by entering the name ISU_S_PARTNER_DISPLAY 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_DISPLAY 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_DISPLAY'"INTERNAL: Display Business Partner
  EXPORTING
   X_PARTNER =  "
*  X_VALDT =  "
*  X_NO_CHANGE =  "Indicator: Display -> Changed Not Permitted
*  X_NO_OTHER =  "
*  X_REL_KZ = 'X' "

 IMPORTING
   Y_DB_UPDATE =  "Indicator: data change
   Y_EXIT_TYPE =  "Return Mode (EXIT, BACK, CANC)
   Y_NEW_PARTNER =  "

TABLES
*  XT_RLTYPES =  "

EXCEPTIONS
   NOT_FOUND = 1    GENERAL_FAULT = 2    NOT_AUTHORIZED = 3    CANCELLED = 4 

.

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_DISPLAY

X_PARTNER -

Data type: BUT000-PARTNER
Optional: No
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_NO_CHANGE - Indicator: Display -> Changed Not Permitted

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

X_NO_OTHER -

Data type: REGEN-NO_OTHER
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)

EXPORTING Parameters details for ISU_S_PARTNER_DISPLAY

Y_DB_UPDATE - Indicator: data change

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

Y_EXIT_TYPE - Return Mode (EXIT, BACK, CANC)

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_DISPLAY

XT_RLTYPES -

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

EXCEPTIONS details

NOT_FOUND - Object Not Found

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)

NOT_AUTHORIZED - Missing Authorization

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

CANCELLED -

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

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

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