SAP CONVERT_OCI_FIELDS Function Module for NOTRANSL: Converts OCI (HTML) Fields to SAP Fields
CONVERT_OCI_FIELDS is a standard convert oci fields 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: Converts OCI (HTML) Fields to SAP Fields 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 convert oci fields FM, simply by entering the name CONVERT_OCI_FIELDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPLM_MT_VARIANT
Program Name: SAPLRPLM_MT_VARIANT
Main Program: SAPLRPLM_MT_VARIANT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CONVERT_OCI_FIELDS 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 'CONVERT_OCI_FIELDS'"NOTRANSL: Converts OCI (HTML) Fields to SAP Fields.
EXPORTING
IV_KATALOGID = "Identifier for allowed catalogs
IMPORTING
ET_OCI_CONVERT = "RDV : Table type for OCI convert
IMPORTING Parameters details for CONVERT_OCI_FIELDS
IV_KATALOGID - Identifier for allowed catalogs
Data type: KATALOGIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CONVERT_OCI_FIELDS
ET_OCI_CONVERT - RDV : Table type for OCI convert
Data type: TT_OCI_CONVERTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CONVERT_OCI_FIELDS 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_iv_katalogid | TYPE KATALOGID, " | |||
| lv_et_oci_convert | TYPE TT_OCI_CONVERT. " |
|   CALL FUNCTION 'CONVERT_OCI_FIELDS' "NOTRANSL: Converts OCI (HTML) Fields to SAP Fields |
| EXPORTING | ||
| IV_KATALOGID | = lv_iv_katalogid | |
| IMPORTING | ||
| ET_OCI_CONVERT | = lv_et_oci_convert | |
| . " CONVERT_OCI_FIELDS | ||
ABAP code using 7.40 inline data declarations to call FM CONVERT_OCI_FIELDS
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