SAP PARTNER_CONVERSION_INT_TO_EXT Function Module for NOTRANSL: Partnernummerumschlüsselung in externe Partnernummer

Search SAP Function Modules

PARTNER_CONVERSION_INT_TO_EXT is a standard partner conversion int to ext 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: Partnernummerumschlüsselung in externe Partnernummer 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 partner conversion int to ext FM, simply by entering the name PARTNER_CONVERSION_INT_TO_EXT into the relevant SAP transaction such as SE37 or SE38.

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

Function PARTNER_CONVERSION_INT_TO_EXT 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 'PARTNER_CONVERSION_INT_TO_EXT'"NOTRANSL: Partnernummerumschlüsselung in externe Partnernummer
  EXPORTING
   PARTNER_FUNCTION_RECEIVER =  "Recipient partner function
   PARTNER_NUMBER_RECEIVER =  "Recipient partner number
   PARTNER_FUNCTION_TO_CONVERT =  "Partner function to be converted
   PARTNER_NUMBER_TO_CONVERT =  "Partner number to be converted

 IMPORTING
   EXTERNAL_PARTNER_NUMBER =  "External Partner Number

EXCEPTIONS
   NO_CONVERSION = 1 

.

IMPORTING Parameters details for PARTNER_CONVERSION_INT_TO_EXT

PARTNER_FUNCTION_RECEIVER - Recipient partner function

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

PARTNER_NUMBER_RECEIVER - Recipient partner number

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

PARTNER_FUNCTION_TO_CONVERT - Partner function to be converted

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

PARTNER_NUMBER_TO_CONVERT - Partner number to be converted

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

EXPORTING Parameters details for PARTNER_CONVERSION_INT_TO_EXT

EXTERNAL_PARTNER_NUMBER - External Partner Number

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

EXCEPTIONS details

NO_CONVERSION -

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

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

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