SAP SPROJECT_GET_INTERNAL_DATA Function Module for









SPROJECT_GET_INTERNAL_DATA is a standard sproject get internal data 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 get internal data FM, simply by entering the name SPROJECT_GET_INTERNAL_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function SPROJECT_GET_INTERNAL_DATA 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_GET_INTERNAL_DATA'"
IMPORTING
PROJECT_ID = "Project Name
USE_CENTRAL_LOG_COMPS = "
IS_GLOBAL_ROLLOUT_ACTIV = "
DISPLAY = "General Flag
MAINTAIN_VIEW = "General Flag
MAINTAIN_LANDSCAPE = "General Flag
MAINTAIN_TRANSPORTS = "General Flag
PROJECT_TITLE = "Module Title
PROD_LANDSCAPE = "Hierarchy maintenance attribute value
PROJECT_RESPONSIBLE = "
PROJECT_LANGUAGE = "

TABLES
* OBJECTLIST = "
* RESOURCES = "
.



EXPORTING Parameters details for SPROJECT_GET_INTERNAL_DATA

PROJECT_ID - Project Name

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

USE_CENTRAL_LOG_COMPS -

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

IS_GLOBAL_ROLLOUT_ACTIV -

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

DISPLAY - General Flag

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

MAINTAIN_VIEW - General Flag

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

MAINTAIN_LANDSCAPE - General Flag

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

MAINTAIN_TRANSPORTS - General Flag

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

PROJECT_TITLE - Module Title

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

PROD_LANDSCAPE - Hierarchy maintenance attribute value

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

PROJECT_RESPONSIBLE -

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

PROJECT_LANGUAGE -

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

TABLES Parameters details for SPROJECT_GET_INTERNAL_DATA

OBJECTLIST -

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

RESOURCES -

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

Copy and paste ABAP code example for SPROJECT_GET_INTERNAL_DATA 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:
lt_objectlist  TYPE STANDARD TABLE OF SPRO_OBJECTLIST_TAB, "   
lv_project_id  TYPE PROJECT_ID, "   
lv_use_central_log_comps  TYPE FLAG, "   
lv_is_global_rollout_activ  TYPE FLAG, "   
lv_display  TYPE FLAG, "   
lt_resources  TYPE STANDARD TABLE OF SPRO_RESOURCE_TAB, "   
lv_maintain_view  TYPE FLAG, "   
lv_maintain_landscape  TYPE FLAG, "   
lv_maintain_transports  TYPE FLAG, "   
lv_project_title  TYPE TPROJECTT-TITLE, "   
lv_prod_landscape  TYPE TPROJ_GEN-VALUE, "   
lv_project_responsible  TYPE TPROJECT-RESPONSIBL, "   
lv_project_language  TYPE TPROJECT-PROJ_LANG. "   

  CALL FUNCTION 'SPROJECT_GET_INTERNAL_DATA'  "
    IMPORTING
         PROJECT_ID = lv_project_id
         USE_CENTRAL_LOG_COMPS = lv_use_central_log_comps
         IS_GLOBAL_ROLLOUT_ACTIV = lv_is_global_rollout_activ
         DISPLAY = lv_display
         MAINTAIN_VIEW = lv_maintain_view
         MAINTAIN_LANDSCAPE = lv_maintain_landscape
         MAINTAIN_TRANSPORTS = lv_maintain_transports
         PROJECT_TITLE = lv_project_title
         PROD_LANDSCAPE = lv_prod_landscape
         PROJECT_RESPONSIBLE = lv_project_responsible
         PROJECT_LANGUAGE = lv_project_language
    TABLES
         OBJECTLIST = lt_objectlist
         RESOURCES = lt_resources
. " SPROJECT_GET_INTERNAL_DATA




ABAP code using 7.40 inline data declarations to call FM SPROJECT_GET_INTERNAL_DATA

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 TITLE FROM TPROJECTT INTO @DATA(ld_project_title).
 
"SELECT single VALUE FROM TPROJ_GEN INTO @DATA(ld_prod_landscape).
 
"SELECT single RESPONSIBL FROM TPROJECT INTO @DATA(ld_project_responsible).
 
"SELECT single PROJ_LANG FROM TPROJECT INTO @DATA(ld_project_language).
 


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!