SAP OIUREP_GET_ROY_LOG Function Module for Performs basic checks related to various months and base data
OIUREP_GET_ROY_LOG is a standard oiurep get roy log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Performs basic checks related to various months and base 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 oiurep get roy log FM, simply by entering the name OIUREP_GET_ROY_LOG into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUREP_ROY_MASTER_MNT
Program Name: SAPLOIUREP_ROY_MASTER_MNT
Main Program: SAPLOIUREP_ROY_MASTER_MNT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUREP_GET_ROY_LOG 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 'OIUREP_GET_ROY_LOG'"Performs basic checks related to various months and base data.
EXPORTING
ROY_EXEC_PARAM = "Execution Parameters for Royalty Reporting
MASTER_DATA = "Indicator for master data (E for entity, O for Owner and P for Profile)
FOR_YYYYMM = "YYYYMM for which master data to be obtained
MASTER_KEY = "Table Key for Royalty Reporting Master Data
TABLES
ROY_LOG = "Changes to master data for reporting
EXCEPTIONS
INVALID_RPT_YYYYMM = 1 INVALID_FOR_YYYYMM = 2 NO_BASE_YYYYMM = 3
IMPORTING Parameters details for OIUREP_GET_ROY_LOG
ROY_EXEC_PARAM - Execution Parameters for Royalty Reporting
Data type: ROIUREP_EXEC_PARAMOptional: No
Call by Reference: Yes
MASTER_DATA - Indicator for master data (E for entity, O for Owner and P for Profile)
Data type: CHAR1Optional: No
Call by Reference: Yes
FOR_YYYYMM - YYYYMM for which master data to be obtained
Data type: ROIUREP_EXEC_PARAM-YEAR_MONTHOptional: No
Call by Reference: Yes
MASTER_KEY - Table Key for Royalty Reporting Master Data
Data type: OIUREP_ROY_LOG-TABLE_KEYOptional: No
Call by Reference: Yes
TABLES Parameters details for OIUREP_GET_ROY_LOG
ROY_LOG - Changes to master data for reporting
Data type: OIUREP_ROY_LOGOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_RPT_YYYYMM - Reporting YYYYMM is greater than the next reporting YYYYMM
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_FOR_YYYYMM - For YYYYMM is greater than the Reporting YYYYMM
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_BASE_YYYYMM - No base month defined in customizing
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIUREP_GET_ROY_LOG 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_roy_log | TYPE STANDARD TABLE OF OIUREP_ROY_LOG, " | |||
| lv_roy_exec_param | TYPE ROIUREP_EXEC_PARAM, " | |||
| lv_invalid_rpt_yyyymm | TYPE ROIUREP_EXEC_PARAM, " | |||
| lv_master_data | TYPE CHAR1, " | |||
| lv_invalid_for_yyyymm | TYPE CHAR1, " | |||
| lv_for_yyyymm | TYPE ROIUREP_EXEC_PARAM-YEAR_MONTH, " | |||
| lv_no_base_yyyymm | TYPE ROIUREP_EXEC_PARAM, " | |||
| lv_master_key | TYPE OIUREP_ROY_LOG-TABLE_KEY. " |
|   CALL FUNCTION 'OIUREP_GET_ROY_LOG' "Performs basic checks related to various months and base data |
| EXPORTING | ||
| ROY_EXEC_PARAM | = lv_roy_exec_param | |
| MASTER_DATA | = lv_master_data | |
| FOR_YYYYMM | = lv_for_yyyymm | |
| MASTER_KEY | = lv_master_key | |
| TABLES | ||
| ROY_LOG | = lt_roy_log | |
| EXCEPTIONS | ||
| INVALID_RPT_YYYYMM = 1 | ||
| INVALID_FOR_YYYYMM = 2 | ||
| NO_BASE_YYYYMM = 3 | ||
| . " OIUREP_GET_ROY_LOG | ||
ABAP code using 7.40 inline data declarations to call FM OIUREP_GET_ROY_LOG
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 FROM ROIUREP_EXEC_PARAM INTO @DATA(ld_for_yyyymm). | ||||
| "SELECT single TABLE_KEY FROM OIUREP_ROY_LOG INTO @DATA(ld_master_key). | ||||
Search for further information about these or an SAP related objects