SAP PU12_CONVERSION Function Module for

Search SAP Function Modules

PU12_CONVERSION is a standard pu12 conversion SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 pu12 conversion FM, simply by entering the name PU12_CONVERSION into the relevant SAP transaction such as SE37 or SE38.

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

Function PU12_CONVERSION 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 'PU12_CONVERSION'"
  EXPORTING
   FLDID =  "
   OLD_VERS =  "
   NEW_VERS_NUMC =  "
   KEY_PERNR =  "
*  KEY_SEQNR =  "
*  KEY_FLDID =  "
*  UPDATE = ' ' "
*  CONVERSION_INCLUDE =  "

TABLES
*  KEY_SEQNR_TAB =  "
*  BUFFER =  "
*  BUFFER_DIRECTORY =  "

.

IMPORTING Parameters details for PU12_CONVERSION

FLDID -

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

OLD_VERS -

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

NEW_VERS_NUMC -

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

KEY_PERNR -

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

KEY_SEQNR -

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

KEY_FLDID -

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

UPDATE -

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

CONVERSION_INCLUDE -

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

TABLES Parameters details for PU12_CONVERSION

KEY_SEQNR_TAB -

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

BUFFER -

Data type:
Optional: Yes
Call by Reference: Yes

BUFFER_DIRECTORY -

Data type:
Optional: Yes
Call by Reference: Yes

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

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