SAP OCS_API_CONVERT_SYSINFO_XML Function Module for
OCS_API_CONVERT_SYSINFO_XML is a standard ocs api convert sysinfo xml 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 ocs api convert sysinfo xml FM, simply by entering the name OCS_API_CONVERT_SYSINFO_XML into the relevant SAP transaction such as SE37 or SE38.
Function Group: OCS_API
Program Name: SAPLOCS_API
Main Program: SAPLOCS_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OCS_API_CONVERT_SYSINFO_XML 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 'OCS_API_CONVERT_SYSINFO_XML'".
EXPORTING
IV_SYSINFO_XML = "
IMPORTING
EV_SID = "
EV_HOST = "
EV_INSTNO = "
EV_SYSTEM_TYPE = "
ET_PRDVERS_SPS = "
TABLES
* ET_CVERS = "
* ET_PRDVERS = "
* ET_SWFEATURE = "
* ET_SWFEATUREINC = "
* ET_SFW_COMPS = "
* ET_BFUNC = "
EXCEPTIONS
TRANSFORMATION_ERROR = 1
IMPORTING Parameters details for OCS_API_CONVERT_SYSINFO_XML
IV_SYSINFO_XML -
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for OCS_API_CONVERT_SYSINFO_XML
EV_SID -
Data type: CHAR30Optional: No
Call by Reference: Yes
EV_HOST -
Data type: SYHOSTOptional: No
Call by Reference: Yes
EV_INSTNO -
Data type: CHAR10Optional: No
Call by Reference: Yes
EV_SYSTEM_TYPE -
Data type: STRINGOptional: No
Call by Reference: Yes
ET_PRDVERS_SPS -
Data type: TT_INSTSWPROD_SPSOptional: No
Call by Reference: Yes
TABLES Parameters details for OCS_API_CONVERT_SYSINFO_XML
ET_CVERS -
Data type: SPAM_CVERSOptional: Yes
Call by Reference: Yes
ET_PRDVERS -
Data type: PRDVERSOptional: Yes
Call by Reference: Yes
ET_SWFEATURE -
Data type: SWFEATUREOptional: Yes
Call by Reference: Yes
ET_SWFEATUREINC -
Data type: SWFEATUREINCOptional: Yes
Call by Reference: Yes
ET_SFW_COMPS -
Data type: SPAM_CVERSOptional: Yes
Call by Reference: Yes
ET_BFUNC -
Data type: OCSBFCOMPOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
TRANSFORMATION_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OCS_API_CONVERT_SYSINFO_XML 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_ev_sid | TYPE CHAR30, " | |||
| lt_et_cvers | TYPE STANDARD TABLE OF SPAM_CVERS, " | |||
| lv_iv_sysinfo_xml | TYPE STRING, " | |||
| lv_transformation_error | TYPE STRING, " | |||
| lv_ev_host | TYPE SYHOST, " | |||
| lt_et_prdvers | TYPE STANDARD TABLE OF PRDVERS, " | |||
| lv_ev_instno | TYPE CHAR10, " | |||
| lt_et_swfeature | TYPE STANDARD TABLE OF SWFEATURE, " | |||
| lv_ev_system_type | TYPE STRING, " | |||
| lt_et_swfeatureinc | TYPE STANDARD TABLE OF SWFEATUREINC, " | |||
| lt_et_sfw_comps | TYPE STANDARD TABLE OF SPAM_CVERS, " | |||
| lv_et_prdvers_sps | TYPE TT_INSTSWPROD_SPS, " | |||
| lt_et_bfunc | TYPE STANDARD TABLE OF OCSBFCOMP. " |
|   CALL FUNCTION 'OCS_API_CONVERT_SYSINFO_XML' " |
| EXPORTING | ||
| IV_SYSINFO_XML | = lv_iv_sysinfo_xml | |
| IMPORTING | ||
| EV_SID | = lv_ev_sid | |
| EV_HOST | = lv_ev_host | |
| EV_INSTNO | = lv_ev_instno | |
| EV_SYSTEM_TYPE | = lv_ev_system_type | |
| ET_PRDVERS_SPS | = lv_et_prdvers_sps | |
| TABLES | ||
| ET_CVERS | = lt_et_cvers | |
| ET_PRDVERS | = lt_et_prdvers | |
| ET_SWFEATURE | = lt_et_swfeature | |
| ET_SWFEATUREINC | = lt_et_swfeatureinc | |
| ET_SFW_COMPS | = lt_et_sfw_comps | |
| ET_BFUNC | = lt_et_bfunc | |
| EXCEPTIONS | ||
| TRANSFORMATION_ERROR = 1 | ||
| . " OCS_API_CONVERT_SYSINFO_XML | ||
ABAP code using 7.40 inline data declarations to call FM OCS_API_CONVERT_SYSINFO_XML
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