SAP PM_PARTNER_INIT Function Module for NOTRANSL: Partnerverarbeitung initialisieren









PM_PARTNER_INIT is a standard pm partner init 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: Partnerverarbeitung initialisieren 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 init FM, simply by entering the name PM_PARTNER_INIT into the relevant SAP transaction such as SE37 or SE38.

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



Function PM_PARTNER_INIT 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_INIT'"NOTRANSL: Partnerverarbeitung initialisieren
EXPORTING
AKTYP = "Activity Category
* PARVW_VERA = 'ZM' "Person responsible (QM)
* PARVW_AUTO = 'ZM' "Author (QM)
* REFRESH = 'X' "Initialize partner processing completely
* VKORG = ' ' "Sales organization
* VTWEG = ' ' "Distrib. channel
* SPART = ' ' "Division
* EQUNR = ' ' "Equipment
* TPLNR = ' ' "FunctLocation
* READ_ALL = 'X' "
* SERVICE_FLAG = ' ' "
OBJNR = "Object number
* TEXT = ' ' "
* NO_SORT = "
* NO_TABIX_DET = "
* NO_TEXT_DET = "
* IP_OBJECT_ARCH = ' ' "Object Archived
OBTYP = "Object category
PARGR = "Partner Determination Procedure
* PARVW_AP = 'AP' "Standard contact person function
* PARVW_INT = 'ZM' "Standard function internal partner
* PARVW_KUND = 'AG' "Standard customer function
* PARVW_LIEF = 'LF' "Standard vendor function
* PARVW_HER = 'HR' "

IMPORTING
OFFSET = "Internal Tables, Current Row Index
.




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_INIT

AKTYP - Activity Category

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

PARVW_VERA - Person responsible (QM)

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

PARVW_AUTO - Author (QM)

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

REFRESH - Initialize partner processing completely

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

VKORG - Sales organization

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

VTWEG - Distrib. channel

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

SPART - Division

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

EQUNR - Equipment

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

TPLNR - FunctLocation

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

READ_ALL -

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

SERVICE_FLAG -

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

OBJNR - Object number

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

TEXT -

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

NO_SORT -

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

NO_TABIX_DET -

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

NO_TEXT_DET -

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

IP_OBJECT_ARCH - Object Archived

Data type: IIND
Default: ' '
Optional: Yes
Call by Reference: Yes

OBTYP - Object category

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

PARGR - Partner Determination Procedure

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

PARVW_AP - Standard contact person function

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

PARVW_INT - Standard function internal partner

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

PARVW_KUND - Standard customer function

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

PARVW_LIEF - Standard vendor function

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

PARVW_HER -

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

EXPORTING Parameters details for PM_PARTNER_INIT

OFFSET - Internal Tables, Current Row Index

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

Copy and paste ABAP code example for PM_PARTNER_INIT 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_aktyp  TYPE T365-AKTYP, "   
lv_offset  TYPE SY-TABIX, "   
lv_parvw_vera  TYPE IHPA-PARVW, "   'ZM'
lv_parvw_auto  TYPE IHPA-PARVW, "   'ZM'
lv_refresh  TYPE IHPA, "   'X'
lv_vkorg  TYPE VIQMEL-VKORG, "   SPACE
lv_vtweg  TYPE VIQMEL-VTWEG, "   SPACE
lv_spart  TYPE VIQMEL-SPART, "   SPACE
lv_equnr  TYPE EQUI-EQUNR, "   SPACE
lv_tplnr  TYPE IFLO-TPLNR, "   SPACE
lv_read_all  TYPE IFLO, "   'X'
lv_service_flag  TYPE IFLO, "   ' '
lv_objnr  TYPE ONR00-OBJNR, "   
lv_text  TYPE CAUFVD-ARTTEXT, "   SPACE
lv_no_sort  TYPE C, "   
lv_no_tabix_det  TYPE C, "   
lv_no_text_det  TYPE C, "   
lv_ip_object_arch  TYPE IIND, "   ' '
lv_obtyp  TYPE TJ03-OBTYP, "   
lv_pargr  TYPE TPAER-PARGR, "   
lv_parvw_ap  TYPE IHPA-PARVW, "   'AP'
lv_parvw_int  TYPE IHPA-PARVW, "   'ZM'
lv_parvw_kund  TYPE IHPA-PARVW, "   'AG'
lv_parvw_lief  TYPE IHPA-PARVW, "   'LF'
lv_parvw_her  TYPE IHPA-PARVW. "   'HR'

  CALL FUNCTION 'PM_PARTNER_INIT'  "NOTRANSL: Partnerverarbeitung initialisieren
    EXPORTING
         AKTYP = lv_aktyp
         PARVW_VERA = lv_parvw_vera
         PARVW_AUTO = lv_parvw_auto
         REFRESH = lv_refresh
         VKORG = lv_vkorg
         VTWEG = lv_vtweg
         SPART = lv_spart
         EQUNR = lv_equnr
         TPLNR = lv_tplnr
         READ_ALL = lv_read_all
         SERVICE_FLAG = lv_service_flag
         OBJNR = lv_objnr
         TEXT = lv_text
         NO_SORT = lv_no_sort
         NO_TABIX_DET = lv_no_tabix_det
         NO_TEXT_DET = lv_no_text_det
         IP_OBJECT_ARCH = lv_ip_object_arch
         OBTYP = lv_obtyp
         PARGR = lv_pargr
         PARVW_AP = lv_parvw_ap
         PARVW_INT = lv_parvw_int
         PARVW_KUND = lv_parvw_kund
         PARVW_LIEF = lv_parvw_lief
         PARVW_HER = lv_parvw_her
    IMPORTING
         OFFSET = lv_offset
. " PM_PARTNER_INIT




ABAP code using 7.40 inline data declarations to call FM PM_PARTNER_INIT

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 AKTYP FROM T365 INTO @DATA(ld_aktyp).
 
"SELECT single TABIX FROM SY INTO @DATA(ld_offset).
 
"SELECT single PARVW FROM IHPA INTO @DATA(ld_parvw_vera).
DATA(ld_parvw_vera) = 'ZM'.
 
"SELECT single PARVW FROM IHPA INTO @DATA(ld_parvw_auto).
DATA(ld_parvw_auto) = 'ZM'.
 
DATA(ld_refresh) = 'X'.
 
"SELECT single VKORG FROM VIQMEL INTO @DATA(ld_vkorg).
DATA(ld_vkorg) = ' '.
 
"SELECT single VTWEG FROM VIQMEL INTO @DATA(ld_vtweg).
DATA(ld_vtweg) = ' '.
 
"SELECT single SPART FROM VIQMEL INTO @DATA(ld_spart).
DATA(ld_spart) = ' '.
 
"SELECT single EQUNR FROM EQUI INTO @DATA(ld_equnr).
DATA(ld_equnr) = ' '.
 
"SELECT single TPLNR FROM IFLO INTO @DATA(ld_tplnr).
DATA(ld_tplnr) = ' '.
 
DATA(ld_read_all) = 'X'.
 
DATA(ld_service_flag) = ' '.
 
"SELECT single OBJNR FROM ONR00 INTO @DATA(ld_objnr).
 
"SELECT single ARTTEXT FROM CAUFVD INTO @DATA(ld_text).
DATA(ld_text) = ' '.
 
 
 
 
DATA(ld_ip_object_arch) = ' '.
 
"SELECT single OBTYP FROM TJ03 INTO @DATA(ld_obtyp).
 
"SELECT single PARGR FROM TPAER INTO @DATA(ld_pargr).
 
"SELECT single PARVW FROM IHPA INTO @DATA(ld_parvw_ap).
DATA(ld_parvw_ap) = 'AP'.
 
"SELECT single PARVW FROM IHPA INTO @DATA(ld_parvw_int).
DATA(ld_parvw_int) = 'ZM'.
 
"SELECT single PARVW FROM IHPA INTO @DATA(ld_parvw_kund).
DATA(ld_parvw_kund) = 'AG'.
 
"SELECT single PARVW FROM IHPA INTO @DATA(ld_parvw_lief).
DATA(ld_parvw_lief) = 'LF'.
 
"SELECT single PARVW FROM IHPA INTO @DATA(ld_parvw_her).
DATA(ld_parvw_her) = 'HR'.
 


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!