SAP ICL_PARTNER_GET Function Module for Read Partner Data (Buffered)

Search SAP Function Modules

ICL_PARTNER_GET is a standard icl partner get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Partner Data (Buffered) 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 icl partner get FM, simply by entering the name ICL_PARTNER_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function ICL_PARTNER_GET 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 'ICL_PARTNER_GET'"Read Partner Data (Buffered)
  EXPORTING
   I_PARTNER =  "
*  I_ADDRNUMBER =  "Address Number
*  I_BKVID =  "Bank Details ID
*  I_XSUPPR_DESCR_DI = 'X' "Do not Return Descriptions in DI

 IMPORTING
   E_BUT000 =  "
   E_BUT000_ADDRESS =  "
   E_DESCRIPTION =  "
   E_DESCRIPTION_NAME =  "
   E_DESCRIPTION_ADDR =  "BP: Address description
   E_BUT0BK =  "BP: Bank details (Read)

TABLES
*  T_ADDRESS =  "BP: Addresses with Addr. Data (Read)
*  T_BUT0BK =  "BP: Bank details (Read)

EXCEPTIONS
   NOT_FOUND = 1    WRONG_PARAMETERS = 2 

.

IMPORTING Parameters details for ICL_PARTNER_GET

I_PARTNER -

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

I_ADDRNUMBER - Address Number

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

I_BKVID - Bank Details ID

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

I_XSUPPR_DESCR_DI - Do not Return Descriptions in DI

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

EXPORTING Parameters details for ICL_PARTNER_GET

E_BUT000 -

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

E_BUT000_ADDRESS -

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

E_DESCRIPTION -

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

E_DESCRIPTION_NAME -

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

E_DESCRIPTION_ADDR - BP: Address description

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

E_BUT0BK - BP: Bank details (Read)

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

TABLES Parameters details for ICL_PARTNER_GET

T_ADDRESS - BP: Addresses with Addr. Data (Read)

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

T_BUT0BK - BP: Bank details (Read)

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

EXCEPTIONS details

NOT_FOUND -

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

WRONG_PARAMETERS -

Data type:
Optional: No
Call by Reference: Yes

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

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