SAP OPS_SE_TRANSFORM_INPUT_DATA Function Module for Transform the incoming data
OPS_SE_TRANSFORM_INPUT_DATA is a standard ops se transform input data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transform the incoming data 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 ops se transform input data FM, simply by entering the name OPS_SE_TRANSFORM_INPUT_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: OPS_SE_COMMON_CHECKS
Program Name: SAPLOPS_SE_COMMON_CHECKS
Main Program: SAPLOPS_SE_COMMON_CHECKS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OPS_SE_TRANSFORM_INPUT_DATA 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 'OPS_SE_TRANSFORM_INPUT_DATA'"Transform the incoming data.
EXPORTING
I_DEST_DATAELEMENT = "name of the destination data element
I_SOURCE_VALUE = "content of the source field
* I_SOURCE_FNAME = "name of the source field
CHANGING
* C_CONVERTED_FIELD = "Name of ABAP Dictionary Object
* CT_MESSAGES = "Table with BAPI Return Information
EXCEPTIONS
ILLEGAL_INPUT = 1 ERROR_MESSAGE = 2
IMPORTING Parameters details for OPS_SE_TRANSFORM_INPUT_DATA
I_DEST_DATAELEMENT - name of the destination data element
Data type: DDOBJNAMEOptional: No
Call by Reference: Yes
I_SOURCE_VALUE - content of the source field
Data type: STRINGOptional: No
Call by Reference: Yes
I_SOURCE_FNAME - name of the source field
Data type: STRINGOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for OPS_SE_TRANSFORM_INPUT_DATA
C_CONVERTED_FIELD - Name of ABAP Dictionary Object
Data type: ANYOptional: Yes
Call by Reference: Yes
CT_MESSAGES - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ILLEGAL_INPUT -
Data type:Optional: No
Call by Reference: Yes
ERROR_MESSAGE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OPS_SE_TRANSFORM_INPUT_DATA 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_illegal_input | TYPE STRING, " | |||
| lv_c_converted_field | TYPE ANY, " | |||
| lv_i_dest_dataelement | TYPE DDOBJNAME, " | |||
| lv_ct_messages | TYPE BAPIRETTAB, " | |||
| lv_error_message | TYPE BAPIRETTAB, " | |||
| lv_i_source_value | TYPE STRING, " | |||
| lv_i_source_fname | TYPE STRING. " |
|   CALL FUNCTION 'OPS_SE_TRANSFORM_INPUT_DATA' "Transform the incoming data |
| EXPORTING | ||
| I_DEST_DATAELEMENT | = lv_i_dest_dataelement | |
| I_SOURCE_VALUE | = lv_i_source_value | |
| I_SOURCE_FNAME | = lv_i_source_fname | |
| CHANGING | ||
| C_CONVERTED_FIELD | = lv_c_converted_field | |
| CT_MESSAGES | = lv_ct_messages | |
| EXCEPTIONS | ||
| ILLEGAL_INPUT = 1 | ||
| ERROR_MESSAGE = 2 | ||
| . " OPS_SE_TRANSFORM_INPUT_DATA | ||
ABAP code using 7.40 inline data declarations to call FM OPS_SE_TRANSFORM_INPUT_DATA
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