SAP OIUX1_UPDATE_RPT Function Module for Performs Database Updates to legal reports

Search SAP Function Modules

OIUX1_UPDATE_RPT is a standard oiux1 update rpt 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 Database Updates to legal reports 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 oiux1 update rpt FM, simply by entering the name OIUX1_UPDATE_RPT into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIUX1_TAX_MASTER
Program Name: SAPLOIUX1_TAX_MASTER
Main Program: SAPLOIUX1_TAX_MASTER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUX1_UPDATE_RPT 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 'OIUX1_UPDATE_RPT'"Performs Database Updates to legal reports
  EXPORTING
   EXEC_PARAM =  "Execution Parameters for Tax Reporting
   EFF_YYYYMM =  "Sales Year and Month
*  CHECK_UPDATE =  "Single-Character Indicator

TABLES
   RPT =  "Legal reports for update

EXCEPTIONS
   FUTURE_LOG_EXISTS = 1    CHECKING_ERROR = 2    DB_ERROR = 3    INVALID_REQUEST = 4    LOG_ERROR = 5 

.

IMPORTING Parameters details for OIUX1_UPDATE_RPT

EXEC_PARAM - Execution Parameters for Tax Reporting

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

EFF_YYYYMM - Sales Year and Month

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

CHECK_UPDATE - Single-Character Indicator

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

TABLES Parameters details for OIUX1_UPDATE_RPT

RPT - Legal reports for update

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

EXCEPTIONS details

FUTURE_LOG_EXISTS - Log contains data after the eff_yyyymm in the reporting yyyymm

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

CHECKING_ERROR - Checking error

Data type:
Optional: No
Call by Reference: Yes

DB_ERROR - Error updating database

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

INVALID_REQUEST - Invalid request to update database

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

LOG_ERROR - Error in the log

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

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

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