SAP PM_PARTNER_DIALOG Function Module for NOTRANSL: Zentraler Aufruf des SD-Dialogbausteins für Partner









PM_PARTNER_DIALOG is a standard pm partner dialog SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Zentraler Aufruf des SD-Dialogbausteins für 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 pm partner dialog FM, simply by entering the name PM_PARTNER_DIALOG into the relevant SAP transaction such as SE37 or SE38.

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



Function PM_PARTNER_DIALOG 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 'PM_PARTNER_DIALOG'"NOTRANSL: Zentraler Aufruf des SD-Dialogbausteins für Partner
  EXPORTING
*  DISPLAY_ONLY = ' ' "Display Only
*  SUBSCREEN_EXT = 0000 "
*  SUBSCREEN_PROG_EXT = '        ' "
*  QMNUM = ' ' "Notification Number
*  TRANS_TEXT = ' ' "
*  POP_UP = ' ' "
*  EQUNR = ' ' "Equipment Number
*  EXIT = ' ' "
*  OBJNR = ' ' "Object Number
   OBTYP =  "Object Category
*  BINPT = SY-BINPT "
   PARGR =  "Partner Determination Procedure
*  SAVE = ' ' "Save active
*  TPLNR = ' ' "

EXCEPTIONS
   CANCEL = 1    EXIT = 2    SAVE = 3    NO_VALID_SUBSCREEN = 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_SAPLIPAR_002 Selection of Notification Partners
EXIT_SAPLIPAR_003 Customizing Partner Check
EXIT_SAPLIPAR_004 Reading of the Additionally Supported Partner Types
EXIT_SAPLIPAR_005 F4 Help for Additonal Partner Types

IMPORTING Parameters details for PM_PARTNER_DIALOG

DISPLAY_ONLY - Display Only

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

SUBSCREEN_EXT -

Data type: SY-DYNNR
Default: 0000
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUBSCREEN_PROG_EXT -

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

QMNUM - Notification Number

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

TRANS_TEXT -

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

POP_UP -

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

EQUNR - Equipment Number

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

EXIT -

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

OBJNR - Object Number

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

OBTYP - Object Category

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

BINPT -

Data type: SY-BINPT
Default: SY-BINPT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PARGR - Partner Determination Procedure

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

SAVE - Save active

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

TPLNR -

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

EXCEPTIONS details

CANCEL -

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

EXIT -

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

SAVE - Save active

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

NO_VALID_SUBSCREEN -

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

Copy and paste ABAP code example for PM_PARTNER_DIALOG 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_cancel  TYPE STRING, "   
lv_display_only  TYPE RC27X-FLG_SEL, "   SPACE
lv_subscreen_ext  TYPE SY-DYNNR, "   0000
lv_subscreen_prog_ext  TYPE SY-REPID, "   ' '
lv_qmnum  TYPE CAUFVD-QMNUM, "   SPACE
lv_trans_text  TYPE TSTCT-TTEXT, "   SPACE
lv_pop_up  TYPE TSTCT, "   ' '
lv_exit  TYPE TSTCT, "   
lv_equnr  TYPE EQUI-EQUNR, "   SPACE
lv_exit  TYPE EQUI, "   ' '
lv_save  TYPE EQUI, "   
lv_objnr  TYPE ONR00-OBJNR, "   SPACE
lv_no_valid_subscreen  TYPE ONR00, "   
lv_obtyp  TYPE TJ03-OBTYP, "   
lv_binpt  TYPE SY-BINPT, "   SY-BINPT
lv_pargr  TYPE RV02P-PARGR, "   
lv_save  TYPE RV02P, "   ' '
lv_tplnr  TYPE IFLO-TPLNR. "   SPACE

  CALL FUNCTION 'PM_PARTNER_DIALOG'  "NOTRANSL: Zentraler Aufruf des SD-Dialogbausteins für Partner
    EXPORTING
         DISPLAY_ONLY = lv_display_only
         SUBSCREEN_EXT = lv_subscreen_ext
         SUBSCREEN_PROG_EXT = lv_subscreen_prog_ext
         QMNUM = lv_qmnum
         TRANS_TEXT = lv_trans_text
         POP_UP = lv_pop_up
         EQUNR = lv_equnr
         EXIT = lv_exit
         OBJNR = lv_objnr
         OBTYP = lv_obtyp
         BINPT = lv_binpt
         PARGR = lv_pargr
         SAVE = lv_save
         TPLNR = lv_tplnr
    EXCEPTIONS
        CANCEL = 1
        EXIT = 2
        SAVE = 3
        NO_VALID_SUBSCREEN = 4
. " PM_PARTNER_DIALOG




ABAP code using 7.40 inline data declarations to call FM PM_PARTNER_DIALOG

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 FLG_SEL FROM RC27X INTO @DATA(ld_display_only).
DATA(ld_display_only) = ' '.
 
"SELECT single DYNNR FROM SY INTO @DATA(ld_subscreen_ext).
DATA(ld_subscreen_ext) = 0000.
 
"SELECT single REPID FROM SY INTO @DATA(ld_subscreen_prog_ext).
DATA(ld_subscreen_prog_ext) = ' '.
 
"SELECT single QMNUM FROM CAUFVD INTO @DATA(ld_qmnum).
DATA(ld_qmnum) = ' '.
 
"SELECT single TTEXT FROM TSTCT INTO @DATA(ld_trans_text).
DATA(ld_trans_text) = ' '.
 
DATA(ld_pop_up) = ' '.
 
 
"SELECT single EQUNR FROM EQUI INTO @DATA(ld_equnr).
DATA(ld_equnr) = ' '.
 
DATA(ld_exit) = ' '.
 
 
"SELECT single OBJNR FROM ONR00 INTO @DATA(ld_objnr).
DATA(ld_objnr) = ' '.
 
 
"SELECT single OBTYP FROM TJ03 INTO @DATA(ld_obtyp).
 
"SELECT single BINPT FROM SY INTO @DATA(ld_binpt).
DATA(ld_binpt) = SY-BINPT.
 
"SELECT single PARGR FROM RV02P INTO @DATA(ld_pargr).
 
DATA(ld_save) = ' '.
 
"SELECT single TPLNR FROM IFLO INTO @DATA(ld_tplnr).
DATA(ld_tplnr) = ' '.
 


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!