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

Function OIUREP_ROY_PROCESSING 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_ROY_PROCESSING'"Royalty Reporting Main Processing.
EXPORTING
ROY_EXEC_PARAM = "Execution Parameters for Royalty Reporting
EXCEPTIONS
PDCD_NOT_FOUND = 1 VLTP_NOT_FOUND = 2 PURC_NOT_FOUND = 3
IMPORTING Parameters details for OIUREP_ROY_PROCESSING
ROY_EXEC_PARAM - Execution Parameters for Royalty Reporting
Data type: ROIUREP_EXEC_PARAMOptional: No
Call by Reference: Yes
EXCEPTIONS details
PDCD_NOT_FOUND - Invalid Product Code
Data type:Optional: No
Call by Reference: Yes
VLTP_NOT_FOUND - Invalid Volume Type
Data type:Optional: No
Call by Reference: Yes
PURC_NOT_FOUND - PurchaserTaxID not maintained
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIUREP_ROY_PROCESSING 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_pdcd_not_found | TYPE STRING, " | |||
| lv_roy_exec_param | TYPE ROIUREP_EXEC_PARAM, " | |||
| lv_vltp_not_found | TYPE ROIUREP_EXEC_PARAM, " | |||
| lv_purc_not_found | TYPE ROIUREP_EXEC_PARAM. " |
|   CALL FUNCTION 'OIUREP_ROY_PROCESSING' "Royalty Reporting Main Processing |
| EXPORTING | ||
| ROY_EXEC_PARAM | = lv_roy_exec_param | |
| EXCEPTIONS | ||
| PDCD_NOT_FOUND = 1 | ||
| VLTP_NOT_FOUND = 2 | ||
| PURC_NOT_FOUND = 3 | ||
| . " OIUREP_ROY_PROCESSING | ||
ABAP code using 7.40 inline data declarations to call FM OIUREP_ROY_PROCESSING
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