SAP PM_PARTNER_LENGTH Function Module for NOTRANSL: Partnernummer in korrekte Länge konvertieren

Search SAP Function Modules

PM_PARTNER_LENGTH is a standard pm partner length 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: Partnernummer in korrekte Länge konvertieren 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 length FM, simply by entering the name PM_PARTNER_LENGTH 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_LENGTH 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_LENGTH'"NOTRANSL: Partnernummer in korrekte Länge konvertieren
  EXPORTING
   PARNR_IMP =  "Partner number (Export)
*  PARVW =  "Partner function
*  NRART =  "Partner type

 IMPORTING
   PARNR_EXP =  "Partner number (Export)
   NRART_EXP =  "Partner type (Export)

EXCEPTIONS
   PARVW_AND_NRART_INITAL = 1    INVALID_PARVW = 2 

.

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_LENGTH

PARNR_IMP - Partner number (Export)

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

PARVW - Partner function

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

NRART - Partner type

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

EXPORTING Parameters details for PM_PARTNER_LENGTH

PARNR_EXP - Partner number (Export)

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

NRART_EXP - Partner type (Export)

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

EXCEPTIONS details

PARVW_AND_NRART_INITAL - Partner function and type are initial

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)

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

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