SAP SD_PARTNER_DISPLAY Function Module for Displaying Partners in SD (Customers, Vendors, Contacts)









SD_PARTNER_DISPLAY is a standard sd 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 Displaying Partners in SD (Customers, Vendors, Contacts) 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 sd partner display FM, simply by entering the name SD_PARTNER_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

Function Group: V02P
Program Name: SAPLV02P
Main Program: SAPLV02P
Appliation area: V
Release date: 02-Feb-1994
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SD_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 'SD_PARTNER_DISPLAY'"Displaying Partners in SD (Customers, Vendors, Contacts)
  EXPORTING
*  NEXT_PARTNER = ' ' "Function 'next partner' in status active
   NUMBER =  "Partner number
   PARTNER_FUNCTION =  "Partner usage
*  PARTNER_MAINTAIN = ' ' "Partner maintenance
*  SALES_CHANNEL = ' ' "Distribution channel (only for customers)
*  SALES_DIVISION = ' ' "Division (only for customers)
*  SALES_ORG = ' ' "Sales organization (only for customers)
*  SCREEN_NUMBER = 110 "Starting screen for customers and vendors

 IMPORTING
   FUNCTION_CODE =  "Function code for further processing

EXCEPTIONS
   FUNCTION_NOT_ALLOWED = 1    OBJECT_NOT_ALLOWED = 2    PARTNER_FUNCTION_NOT_VALID = 3    PARTNER_NOT_EXIST = 4
.



IMPORTING Parameters details for SD_PARTNER_DISPLAY

NEXT_PARTNER - Function 'next partner' in status active

Data type: RF02D-SELKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NUMBER - Partner number

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

PARTNER_FUNCTION - Partner usage

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

PARTNER_MAINTAIN - Partner maintenance

Data type: RF02D-SELKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SALES_CHANNEL - Distribution channel (only for customers)

Data type: KNVV-VTWEG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SALES_DIVISION - Division (only for customers)

Data type: KNVV-SPART
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SALES_ORG - Sales organization (only for customers)

Data type: KNVV-VKORG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SCREEN_NUMBER - Starting screen for customers and vendors

Data type: T185-PANEL
Default: 110
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SD_PARTNER_DISPLAY

FUNCTION_CODE - Function code for further processing

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

EXCEPTIONS details

FUNCTION_NOT_ALLOWED - No transaction authorization

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

OBJECT_NOT_ALLOWED - No object authorization (authorization group)

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

PARTNER_FUNCTION_NOT_VALID - Partner usage is not allowed

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

PARTNER_NOT_EXIST - Partner does not exist

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

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

DATA:
lv_next_partner  TYPE RF02D-SELKZ, "   SPACE
lv_function_code  TYPE T185-FCODE, "   
lv_function_not_allowed  TYPE T185, "   
lv_number  TYPE KNA1-KUNNR, "   
lv_object_not_allowed  TYPE KNA1, "   
lv_partner_function  TYPE KNVP-PARVW, "   
lv_partner_function_not_valid  TYPE KNVP, "   
lv_partner_maintain  TYPE RF02D-SELKZ, "   SPACE
lv_partner_not_exist  TYPE RF02D, "   
lv_sales_channel  TYPE KNVV-VTWEG, "   SPACE
lv_sales_division  TYPE KNVV-SPART, "   SPACE
lv_sales_org  TYPE KNVV-VKORG, "   SPACE
lv_screen_number  TYPE T185-PANEL. "   110

  CALL FUNCTION 'SD_PARTNER_DISPLAY'  "Displaying Partners in SD (Customers, Vendors, Contacts)
    EXPORTING
         NEXT_PARTNER = lv_next_partner
         NUMBER = lv_number
         PARTNER_FUNCTION = lv_partner_function
         PARTNER_MAINTAIN = lv_partner_maintain
         SALES_CHANNEL = lv_sales_channel
         SALES_DIVISION = lv_sales_division
         SALES_ORG = lv_sales_org
         SCREEN_NUMBER = lv_screen_number
    IMPORTING
         FUNCTION_CODE = lv_function_code
    EXCEPTIONS
        FUNCTION_NOT_ALLOWED = 1
        OBJECT_NOT_ALLOWED = 2
        PARTNER_FUNCTION_NOT_VALID = 3
        PARTNER_NOT_EXIST = 4
. " SD_PARTNER_DISPLAY




ABAP code using 7.40 inline data declarations to call FM SD_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.

"SELECT single SELKZ FROM RF02D INTO @DATA(ld_next_partner).
DATA(ld_next_partner) = ' '.
 
"SELECT single FCODE FROM T185 INTO @DATA(ld_function_code).
 
 
"SELECT single KUNNR FROM KNA1 INTO @DATA(ld_number).
 
 
"SELECT single PARVW FROM KNVP INTO @DATA(ld_partner_function).
 
 
"SELECT single SELKZ FROM RF02D INTO @DATA(ld_partner_maintain).
DATA(ld_partner_maintain) = ' '.
 
 
"SELECT single VTWEG FROM KNVV INTO @DATA(ld_sales_channel).
DATA(ld_sales_channel) = ' '.
 
"SELECT single SPART FROM KNVV INTO @DATA(ld_sales_division).
DATA(ld_sales_division) = ' '.
 
"SELECT single VKORG FROM KNVV INTO @DATA(ld_sales_org).
DATA(ld_sales_org) = ' '.
 
"SELECT single PANEL FROM T185 INTO @DATA(ld_screen_number).
DATA(ld_screen_number) = 110.
 


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!