SAP SPROJECT_SET_END_DATE Function Module for









SPROJECT_SET_END_DATE is a standard sproject set end date 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 sproject set end date FM, simply by entering the name SPROJECT_SET_END_DATE into the relevant SAP transaction such as SE37 or SE38.

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



Function SPROJECT_SET_END_DATE 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 'SPROJECT_SET_END_DATE'"
EXPORTING
PROJECT_ID = "
END_DATE = "
.



IMPORTING Parameters details for SPROJECT_SET_END_DATE

PROJECT_ID -

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

END_DATE -

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

Copy and paste ABAP code example for SPROJECT_SET_END_DATE 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_project_id  TYPE SPRO_HEAD-PROJECT_ID, "   
lv_end_date  TYPE SPRO_HEAD-END_DATE. "   

  CALL FUNCTION 'SPROJECT_SET_END_DATE'  "
    EXPORTING
         PROJECT_ID = lv_project_id
         END_DATE = lv_end_date
. " SPROJECT_SET_END_DATE




ABAP code using 7.40 inline data declarations to call FM SPROJECT_SET_END_DATE

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 PROJECT_ID FROM SPRO_HEAD INTO @DATA(ld_project_id).
 
"SELECT single END_DATE FROM SPRO_HEAD INTO @DATA(ld_end_date).
 


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!