SAP OIUY1_ROY_TX_AM1_DRIVER Function Module for GLO Current and Amendment Oil driver

Search SAP Function Modules

OIUY1_ROY_TX_AM1_DRIVER is a standard oiuy1 roy tx am1 driver SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for GLO Current and Amendment Oil 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 am1 driver FM, simply by entering the name OIUY1_ROY_TX_AM1_DRIVER 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_AM1_DRIVER 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_AM1_DRIVER'"GLO Current and Amendment Oil driver
  EXPORTING
   ROY_EXEC_PARAM =  "Execution Parameters for Royalty Reporting
   AMND_YYYYMM =  "Year and Month for Amended Reports
   PROFILE =  "Profile for Reporting
*  AMND_FLAG =  "Single-character flag
*  NO_DIALOG =  "Single-Character Flag
*  RPT_ID =  "Legal report Identifier for tax and royalty reports

EXCEPTIONS
   INVALID_PROFILE = 1    GET_DATA_ERROR = 2    NO_STRUCTURE_FOUND = 3    NO_SMARTFORM_FOUND = 4    NO_DATA_TO_PRINT = 5    NO_STATUS = 6 

.

IMPORTING Parameters details for OIUY1_ROY_TX_AM1_DRIVER

ROY_EXEC_PARAM - Execution Parameters for Royalty Reporting

Data type: ROIUREP_EXEC_PARAM
Optional: No
Call by Reference: Yes

AMND_YYYYMM - Year and Month for Amended Reports

Data type: OIUREP_AMND_STAT-YEAR_MONTH_AMND
Optional: No
Call by Reference: Yes

PROFILE - Profile for Reporting

Data type: OIUREP_RPT_PRFL-PROFILE
Optional: No
Call by Reference: Yes

AMND_FLAG - Single-character flag

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

NO_DIALOG - Single-Character Flag

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

RPT_ID - Legal report Identifier for tax and royalty reports

Data type: OIUREP_LGL_REPORT_ID
Optional: Yes
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_SMARTFORM_FOUND - No Smartform found for output

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_DATA_TO_PRINT - No data to Print in the Form

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_STATUS - can not find status detail entry

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIUY1_ROY_TX_AM1_DRIVER 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.

ABAP code using 7.40 inline data declarations to call FM OIUY1_ROY_TX_AM1_DRIVER

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