SAP SO_WIND_RESUBMISSION Function Module for









SO_WIND_RESUBMISSION is a standard so wind resubmission SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 so wind resubmission FM, simply by entering the name SO_WIND_RESUBMISSION into the relevant SAP transaction such as SE37 or SE38.

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



Function SO_WIND_RESUBMISSION 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 'SO_WIND_RESUBMISSION'"
EXPORTING
* EARLIEST_RESUBMISSION = SY-DATUM "earliest possible resubmission date
* HIDE_TRIGGER = ' ' "Fields ' in dependency' are not displayed
* MULTIPLE_OBJECTS = 'X' "
NEW_RESUBMISSION = "It is a new resubmission
* OBJDES = ' ' "Name of Document
* OBJECT_ID = ' ' "Object Type
OLD_RESUB_DATA = "Data of resubmission
* OWNER = ' ' "Office username of the owner of resubmission

IMPORTING
NEW_RESUB_DATA = "Data of resubmission
OK_CODE = "Return code

EXCEPTIONS
OWNER_NOT_EXIST = 1
.



IMPORTING Parameters details for SO_WIND_RESUBMISSION

EARLIEST_RESUBMISSION - earliest possible resubmission date

Data type: SORS-RSDAT
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

HIDE_TRIGGER - Fields ' in dependency' are not displayed

Data type: SONV-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MULTIPLE_OBJECTS -

Data type: SONV-FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NEW_RESUBMISSION - It is a new resubmission

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

OBJDES - Name of Document

Data type: SOOD-OBJDES
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT_ID - Object Type

Data type: SOODK
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OLD_RESUB_DATA - Data of resubmission

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

OWNER - Office username of the owner of resubmission

Data type: SOUD-USRNAM
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SO_WIND_RESUBMISSION

NEW_RESUB_DATA - Data of resubmission

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

OK_CODE - Return code

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

EXCEPTIONS details

OWNER_NOT_EXIST - Office user does not exist

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

Copy and paste ABAP code example for SO_WIND_RESUBMISSION 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_new_resub_data  TYPE SORSD, "   
lv_owner_not_exist  TYPE SORSD, "   
lv_earliest_resubmission  TYPE SORS-RSDAT, "   SY-DATUM
lv_ok_code  TYPE SY-UCOMM, "   
lv_hide_trigger  TYPE SONV-FLAG, "   SPACE
lv_multiple_objects  TYPE SONV-FLAG, "   'X'
lv_new_resubmission  TYPE SONV-FLAG, "   
lv_objdes  TYPE SOOD-OBJDES, "   SPACE
lv_object_id  TYPE SOODK, "   SPACE
lv_old_resub_data  TYPE SORSD, "   
lv_owner  TYPE SOUD-USRNAM. "   SPACE

  CALL FUNCTION 'SO_WIND_RESUBMISSION'  "
    EXPORTING
         EARLIEST_RESUBMISSION = lv_earliest_resubmission
         HIDE_TRIGGER = lv_hide_trigger
         MULTIPLE_OBJECTS = lv_multiple_objects
         NEW_RESUBMISSION = lv_new_resubmission
         OBJDES = lv_objdes
         OBJECT_ID = lv_object_id
         OLD_RESUB_DATA = lv_old_resub_data
         OWNER = lv_owner
    IMPORTING
         NEW_RESUB_DATA = lv_new_resub_data
         OK_CODE = lv_ok_code
    EXCEPTIONS
        OWNER_NOT_EXIST = 1
. " SO_WIND_RESUBMISSION




ABAP code using 7.40 inline data declarations to call FM SO_WIND_RESUBMISSION

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 RSDAT FROM SORS INTO @DATA(ld_earliest_resubmission).
DATA(ld_earliest_resubmission) = SY-DATUM.
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_ok_code).
 
"SELECT single FLAG FROM SONV INTO @DATA(ld_hide_trigger).
DATA(ld_hide_trigger) = ' '.
 
"SELECT single FLAG FROM SONV INTO @DATA(ld_multiple_objects).
DATA(ld_multiple_objects) = 'X'.
 
"SELECT single FLAG FROM SONV INTO @DATA(ld_new_resubmission).
 
"SELECT single OBJDES FROM SOOD INTO @DATA(ld_objdes).
DATA(ld_objdes) = ' '.
 
DATA(ld_object_id) = ' '.
 
 
"SELECT single USRNAM FROM SOUD INTO @DATA(ld_owner).
DATA(ld_owner) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!