SAP OIU_SPADJ_UPDATE Function Module for Updates Sales Point Adjustment
OIU_SPADJ_UPDATE is a standard oiu spadj update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Updates Sales Point Adjustment 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 oiu spadj update FM, simply by entering the name OIU_SPADJ_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUPC_SP_ADJUSTMENT
Program Name: SAPLOIUPC_SP_ADJUSTMENT
Main Program: SAPLOIUPC_SP_ADJUSTMENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIU_SPADJ_UPDATE 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 'OIU_SPADJ_UPDATE'"Updates Sales Point Adjustment.
EXPORTING
I_SPADJ = "Sales Point Adjustments
I_XXDBACTION = "Database Action Flag
IMPORTING Parameters details for OIU_SPADJ_UPDATE
I_SPADJ - Sales Point Adjustments
Data type: OIUPC_SPADJOptional: No
Call by Reference: Yes
I_XXDBACTION - Database Action Flag
Data type: ROIUPC_SPADJ-XXDBACTIONOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIU_SPADJ_UPDATE 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_i_spadj | TYPE OIUPC_SPADJ, " | |||
| lv_i_xxdbaction | TYPE ROIUPC_SPADJ-XXDBACTION. " |
|   CALL FUNCTION 'OIU_SPADJ_UPDATE' "Updates Sales Point Adjustment |
| EXPORTING | ||
| I_SPADJ | = lv_i_spadj | |
| I_XXDBACTION | = lv_i_xxdbaction | |
| . " OIU_SPADJ_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM OIU_SPADJ_UPDATE
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 XXDBACTION FROM ROIUPC_SPADJ INTO @DATA(ld_i_xxdbaction). | ||||
Search for further information about these or an SAP related objects