SAP ISU_PARTNER_ID_FROM_COMM Function Module for

Search SAP Function Modules

ISU_PARTNER_ID_FROM_COMM is a standard isu partner id from comm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 partner id from comm FM, simply by entering the name ISU_PARTNER_ID_FROM_COMM into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_PARTNER_ID_FROM_COMM 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_PARTNER_ID_FROM_COMM'"
  EXPORTING
   X_SEARCHSTRING =  "
   X_COMMUNICATIONTYPE =  "
*  X_CASESENSITIVESMTP = ' ' "
*  X_COUNTRYKEY = ' ' "
*  X_ONLYUNIQUE = ' ' "

 IMPORTING
   Y_UNIQUEPARTNER =  "
   Y_ISUNIQUE =  "
   Y_NOTFOUND =  "
   YT_PARTNERLIST =  "

EXCEPTIONS
   COMMTYPE_INVALID = 1    INTERNAL_ERROR = 2 

.

IMPORTING Parameters details for ISU_PARTNER_ID_FROM_COMM

X_SEARCHSTRING -

Data type: C
Optional: No
Call by Reference: Yes

X_COMMUNICATIONTYPE -

Data type: AD_COMM
Optional: No
Call by Reference: Yes

X_CASESENSITIVESMTP -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

X_COUNTRYKEY -

Data type: LAND1
Default: SPACE
Optional: Yes
Call by Reference: Yes

X_ONLYUNIQUE -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_PARTNER_ID_FROM_COMM

Y_UNIQUEPARTNER -

Data type: BU_PARTNER
Optional: No
Call by Reference: Yes

Y_ISUNIQUE -

Data type: XFELD
Optional: No
Call by Reference: Yes

Y_NOTFOUND -

Data type: XFELD
Optional: No
Call by Reference: Yes

YT_PARTNERLIST -

Data type: IEBU_PARTNER_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

COMMTYPE_INVALID -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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

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