SAP PM_PARTNER_MAINTAIN Function Module for NOTRANSL: Partner in Partnerverarbeitung ändern/hinzufühen









PM_PARTNER_MAINTAIN is a standard pm partner maintain 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: Partner in Partnerverarbeitung ändern/hinzufühen 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 maintain FM, simply by entering the name PM_PARTNER_MAINTAIN 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_MAINTAIN 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_MAINTAIN'"NOTRANSL: Partner in Partnerverarbeitung ändern/hinzufühen
EXPORTING
* OBJNR = ' ' "Object number
* CHECK_DEBITOR = 'X' "
PARNR = "Partners
PARVW = "Partner function
* ADRNR = "
* ADR_HANDLE = "
* TABIX = 0 "Index partner (when changing, otherwise 0)
* TABIX_OBJNR = 0 "Index partner (based on an object number)
* MSGTY = 'E' "Message category
* CPD_POP_UP = 'X' "

IMPORTING
COUNTER = "

EXCEPTIONS
INVALID_PARNR = 1 CPD_CUSTOMER = 2 INVALID_PARVW = 3 PARVW_UNIQUE = 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_MAINTAIN

OBJNR - Object number

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

CHECK_DEBITOR -

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

PARNR - Partners

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

PARVW - Partner function

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

ADRNR -

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

ADR_HANDLE -

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

TABIX - Index partner (when changing, otherwise 0)

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

TABIX_OBJNR - Index partner (based on an object number)

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

MSGTY - Message category

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

CPD_POP_UP -

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

EXPORTING Parameters details for PM_PARTNER_MAINTAIN

COUNTER -

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

EXCEPTIONS details

INVALID_PARNR - Partner not valid

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

CPD_CUSTOMER - One-time customer

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

INVALID_PARVW - Partner function not valid

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

PARVW_UNIQUE - Unique partner already available

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

Copy and paste ABAP code example for PM_PARTNER_MAINTAIN 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_objnr  TYPE IHPA-OBJNR, "   SPACE
lv_counter  TYPE IHPA-COUNTER, "   
lv_invalid_parnr  TYPE IHPA, "   
lv_check_debitor  TYPE IHPA, "   'X'
lv_parnr  TYPE IHPA-PARNR, "   
lv_cpd_customer  TYPE IHPA, "   
lv_parvw  TYPE IHPA-PARVW, "   
lv_invalid_parvw  TYPE IHPA, "   
lv_adrnr  TYPE IHPA-ADRNR, "   
lv_parvw_unique  TYPE IHPA, "   
lv_adr_handle  TYPE IHPAVB-ADR_HANDLE, "   
lv_tabix  TYPE SY-TABIX, "   0
lv_tabix_objnr  TYPE SY-TABIX, "   0
lv_msgty  TYPE SY-MSGTY, "   'E'
lv_cpd_pop_up  TYPE SY. "   'X'

  CALL FUNCTION 'PM_PARTNER_MAINTAIN'  "NOTRANSL: Partner in Partnerverarbeitung ändern/hinzufühen
    EXPORTING
         OBJNR = lv_objnr
         CHECK_DEBITOR = lv_check_debitor
         PARNR = lv_parnr
         PARVW = lv_parvw
         ADRNR = lv_adrnr
         ADR_HANDLE = lv_adr_handle
         TABIX = lv_tabix
         TABIX_OBJNR = lv_tabix_objnr
         MSGTY = lv_msgty
         CPD_POP_UP = lv_cpd_pop_up
    IMPORTING
         COUNTER = lv_counter
    EXCEPTIONS
        INVALID_PARNR = 1
        CPD_CUSTOMER = 2
        INVALID_PARVW = 3
        PARVW_UNIQUE = 4
. " PM_PARTNER_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM PM_PARTNER_MAINTAIN

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 OBJNR FROM IHPA INTO @DATA(ld_objnr).
DATA(ld_objnr) = ' '.
 
"SELECT single COUNTER FROM IHPA INTO @DATA(ld_counter).
 
 
DATA(ld_check_debitor) = 'X'.
 
"SELECT single PARNR FROM IHPA INTO @DATA(ld_parnr).
 
 
"SELECT single PARVW FROM IHPA INTO @DATA(ld_parvw).
 
 
"SELECT single ADRNR FROM IHPA INTO @DATA(ld_adrnr).
 
 
"SELECT single ADR_HANDLE FROM IHPAVB INTO @DATA(ld_adr_handle).
 
"SELECT single TABIX FROM SY INTO @DATA(ld_tabix).
 
"SELECT single TABIX FROM SY INTO @DATA(ld_tabix_objnr).
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_msgty).
DATA(ld_msgty) = 'E'.
 
DATA(ld_cpd_pop_up) = 'X'.
 


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!