SAP OIUY1_ROY_TX_UT3_DOWNLOAD Function Module for UT1 Driver
OIUY1_ROY_TX_UT3_DOWNLOAD is a standard oiuy1 roy tx ut3 download SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for UT1 Driver 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 oiuy1 roy tx ut3 download FM, simply by entering the name OIUY1_ROY_TX_UT3_DOWNLOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUREP_ROY_DRIVERS
Program Name: SAPLOIUREP_ROY_DRIVERS
Main Program: SAPLOIUREP_ROY_DRIVERS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUY1_ROY_TX_UT3_DOWNLOAD 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 'OIUY1_ROY_TX_UT3_DOWNLOAD'"UT1 Driver.
EXPORTING
ROY_EXEC_PARAM = "Execution Parameters for Royalty Reporting
AMND_YYYYMM = "Year and Month for Amended Reports
PROFILE = "Report profile
* AMND_FLAG = "Single-character flag
TABLES
DOWNLOAD_DATA = "contains 4 table elements of 250 Bytes
EXCEPTIONS
INVALID_PROFILE = 1 GET_DATA_ERROR = 2 NO_STRUCTURE_FOUND = 3 NO_DATA_TO_PRINT = 4
IMPORTING Parameters details for OIUY1_ROY_TX_UT3_DOWNLOAD
ROY_EXEC_PARAM - Execution Parameters for Royalty Reporting
Data type: ROIUREP_EXEC_PARAMOptional: No
Call by Reference: Yes
AMND_YYYYMM - Year and Month for Amended Reports
Data type: OIUREP_AMND_STAT-YEAR_MONTH_AMNDOptional: No
Call by Reference: Yes
PROFILE - Report profile
Data type: OIUREP_RPT_PRFL-PROFILEOptional: No
Call by Reference: Yes
AMND_FLAG - Single-character flag
Data type: CHAR1Optional: Yes
Call by Reference: Yes
TABLES Parameters details for OIUY1_ROY_TX_UT3_DOWNLOAD
DOWNLOAD_DATA - contains 4 table elements of 250 Bytes
Data type: ROIUY1_ROY_TX_DOWNLOADOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_PROFILE - Invalid Profile
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GET_DATA_ERROR - Error in obtaining reporting entities
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_STRUCTURE_FOUND - No Structure found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_DATA_TO_PRINT - No data to Download
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIUY1_ROY_TX_UT3_DOWNLOAD 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: | ||||
| lt_download_data | TYPE STANDARD TABLE OF ROIUY1_ROY_TX_DOWNLOAD, " | |||
| lv_roy_exec_param | TYPE ROIUREP_EXEC_PARAM, " | |||
| lv_invalid_profile | TYPE ROIUREP_EXEC_PARAM, " | |||
| lv_amnd_yyyymm | TYPE OIUREP_AMND_STAT-YEAR_MONTH_AMND, " | |||
| lv_get_data_error | TYPE OIUREP_AMND_STAT, " | |||
| lv_profile | TYPE OIUREP_RPT_PRFL-PROFILE, " | |||
| lv_no_structure_found | TYPE OIUREP_RPT_PRFL, " | |||
| lv_amnd_flag | TYPE CHAR1, " | |||
| lv_no_data_to_print | TYPE CHAR1. " |
|   CALL FUNCTION 'OIUY1_ROY_TX_UT3_DOWNLOAD' "UT1 Driver |
| EXPORTING | ||
| ROY_EXEC_PARAM | = lv_roy_exec_param | |
| AMND_YYYYMM | = lv_amnd_yyyymm | |
| PROFILE | = lv_profile | |
| AMND_FLAG | = lv_amnd_flag | |
| TABLES | ||
| DOWNLOAD_DATA | = lt_download_data | |
| EXCEPTIONS | ||
| INVALID_PROFILE = 1 | ||
| GET_DATA_ERROR = 2 | ||
| NO_STRUCTURE_FOUND = 3 | ||
| NO_DATA_TO_PRINT = 4 | ||
| . " OIUY1_ROY_TX_UT3_DOWNLOAD | ||
ABAP code using 7.40 inline data declarations to call FM OIUY1_ROY_TX_UT3_DOWNLOAD
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.| "SELECT single YEAR_MONTH_AMND FROM OIUREP_AMND_STAT INTO @DATA(ld_amnd_yyyymm). | ||||
| "SELECT single PROFILE FROM OIUREP_RPT_PRFL INTO @DATA(ld_profile). | ||||
Search for further information about these or an SAP related objects