SAP UPF_OUTPUT_CONVERT Function Module for Planning functions: Conversion Output
UPF_OUTPUT_CONVERT is a standard upf output convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Planning functions: Conversion Output 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 upf output convert FM, simply by entering the name UPF_OUTPUT_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPFC
Program Name: SAPLUPFC
Main Program: SAPLUPFC
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPF_OUTPUT_CONVERT 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 'UPF_OUTPUT_CONVERT'"Planning functions: Conversion Output.
EXPORTING
* I_AREA = "Planning Area
* I_FIELDNAME = "Field Name
* I_CONVEXIT = "Conversion exit
* I_DATATYPE = "Data Type
* I_INTTYPE = "ABAP data type (C,D,N,...)
* I_INTLEN = "Internal length
* I_DECIMALS = "Decimal Places
* I_OUTPUTLEN = "Output Length
I_VALUE_TO_CONVERT = "Value to Be Converted
IMPORTING
E_OUTPUT_VALUE = "
IMPORTING Parameters details for UPF_OUTPUT_CONVERT
I_AREA - Planning Area
Data type: UPC_Y_AREAOptional: Yes
Call by Reference: Yes
I_FIELDNAME - Field Name
Data type: FIELDNAMEOptional: Yes
Call by Reference: Yes
I_CONVEXIT - Conversion exit
Data type: CONVEXITOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATATYPE - Data Type
Data type: DATATYPE_DOptional: Yes
Call by Reference: No ( called with pass by value option)
I_INTTYPE - ABAP data type (C,D,N,...)
Data type: INTTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_INTLEN - Internal length
Data type: INTLENOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DECIMALS - Decimal Places
Data type: DECIMALSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OUTPUTLEN - Output Length
Data type: OUTPUTLENOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VALUE_TO_CONVERT - Value to Be Converted
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UPF_OUTPUT_CONVERT
E_OUTPUT_VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UPF_OUTPUT_CONVERT 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_i_area | TYPE UPC_Y_AREA, " | |||
| lv_e_output_value | TYPE UPC_Y_AREA, " | |||
| lv_i_fieldname | TYPE FIELDNAME, " | |||
| lv_i_convexit | TYPE CONVEXIT, " | |||
| lv_i_datatype | TYPE DATATYPE_D, " | |||
| lv_i_inttype | TYPE INTTYPE, " | |||
| lv_i_intlen | TYPE INTLEN, " | |||
| lv_i_decimals | TYPE DECIMALS, " | |||
| lv_i_outputlen | TYPE OUTPUTLEN, " | |||
| lv_i_value_to_convert | TYPE OUTPUTLEN. " |
|   CALL FUNCTION 'UPF_OUTPUT_CONVERT' "Planning functions: Conversion Output |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| I_FIELDNAME | = lv_i_fieldname | |
| I_CONVEXIT | = lv_i_convexit | |
| I_DATATYPE | = lv_i_datatype | |
| I_INTTYPE | = lv_i_inttype | |
| I_INTLEN | = lv_i_intlen | |
| I_DECIMALS | = lv_i_decimals | |
| I_OUTPUTLEN | = lv_i_outputlen | |
| I_VALUE_TO_CONVERT | = lv_i_value_to_convert | |
| IMPORTING | ||
| E_OUTPUT_VALUE | = lv_e_output_value | |
| . " UPF_OUTPUT_CONVERT | ||
ABAP code using 7.40 inline data declarations to call FM UPF_OUTPUT_CONVERT
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