SAP Function Modules

comments icon Comments

OIUT3_RENDER_XML SAP Function module - Create Outgoing XML







OIUT3_RENDER_XML is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name OIUT3_RENDER_XML into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: OIUT3_XML
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM OIUT3_RENDER_XML - OIUT3 RENDER XML 





CALL FUNCTION 'OIUT3_RENDER_XML' "Create Outgoing XML
  EXPORTING
    cluster =                   " cl_xml_object_manager  supperclass for business objects
*   header_record =             " roiut2_xml_header  XML header record
*   conn_id =                   " oiut2_int_trace-conn_id  Connection ID
*   biztalk =                   " char1         Generate Biztalk XML
*   outbound =                  " char1         SAP initiated Outbound XML
  TABLES
    xml_tab =                   " roiut2_xml_data_tab  Table to hold the generated XML
*   err_tab =                   " bapiret2      Return parameter
  EXCEPTIONS
    FAILED = 1                  "               Any internal error - XML not created
    COMPLETED_WITH_WARNINGS = 2  "              ZML Created - errors in OIUT2_INT_MESSG
    .  "  OIUT3_RENDER_XML

ABAP code example for Function Module OIUT3_RENDER_XML





The ABAP code below is a full code listing to execute function module OIUT3_RENDER_XML including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_xml_tab    TYPE STANDARD TABLE OF ROIUT2_XML_DATA_TAB,"TABLES PARAM
wa_xml_tab  LIKE LINE OF it_xml_tab
,
it_err_tab    TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_err_tab  LIKE LINE OF it_err_tab
.




DATA(ld_cluster) = 'Check type of data required'.

DATA(ld_header_record) = 'Check type of data required'.
 

SELECT single CONN_ID 
  FROM OIUT2_INT_TRACE 
  INTO @DATA(ld_conn_id).


DATA(ld_biztalk) = 'Check type of data required'.

DATA(ld_outbound) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_xml_tab to it_xml_tab.
 

"populate fields of struture and append to itab
append wa_err_tab to it_err_tab.
.

CALL FUNCTION 'OIUT3_RENDER_XML'
  EXPORTING
    cluster =                    ld_cluster
*   header_record =              ld_header_record
*   conn_id =                    ld_conn_id
*   biztalk =                    ld_biztalk
*   outbound =                   ld_outbound
  TABLES
    xml_tab =                    it_xml_tab
*   err_tab =                    it_err_tab
  EXCEPTIONS
    FAILED =                     1
    COMPLETED_WITH_WARNINGS =    2
    .  "  OIUT3_RENDER_XML

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_cluster  TYPE CL_XML_OBJECT_MANAGER ,
it_xml_tab  TYPE STANDARD TABLE OF ROIUT2_XML_DATA_TAB ,
wa_xml_tab  LIKE LINE OF it_xml_tab,
ld_header_record  TYPE ROIUT2_XML_HEADER ,
it_err_tab  TYPE STANDARD TABLE OF BAPIRET2 ,
wa_err_tab  LIKE LINE OF it_err_tab,
ld_conn_id  TYPE OIUT2_INT_TRACE-CONN_ID ,
ld_biztalk  TYPE CHAR1 ,
ld_outbound  TYPE CHAR1 .




ld_cluster = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_xml_tab to it_xml_tab.
ld_header_record = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_err_tab to it_err_tab.

SELECT single CONN_ID 
  FROM OIUT2_INT_TRACE 
  INTO ld_conn_id.

ld_biztalk = 'Check type of data required'.
ld_outbound = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name OIUT3_RENDER_XML or its description.


   
 

OIUT3_RENDER_XML - Create Outgoing XML
OIUT3_PURGE_INTERFACE_LOGS - Delete Interface Logs based on a table of CID's
OIUT3_PARSE_XML - Parse XML
OIUT3_IMPLICIT_RFC_COMMIT - implicit commit without triggering update tasks
OIUT3_GET_OWNERSHIP_DATA - Ownership Interface Data(Header and Detail)
OIUT3_DELETE_LOG - Delete Interface Logs based on a table of CID's