DX_PROJECT_GET_COMPLETE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name DX_PROJECT_GET_COMPLETE into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
DX_PROJECT
Released Date:
Not Released
Processing type: Normal fucntion module
CALL FUNCTION 'DX_PROJECT_GET_COMPLETE' "
EXPORTING
project = " dxsubpro-project Data Transfer Project
IMPORTING
projectdata = " dxproj Sub-Projects for Mass Data Transfer to R/3
* TABLES
* projecttext = " dxproj_t Project Texts for Mass Data Transfer to R/3
* subprojectdata = " dxsubpro Sub-Projects for Mass Data Transfer to R/3
* subprojecttext = " dxsubpro_t Sub-Project Texts for Mass Data Transfer to R/3
* rundefdata = " dxrundef Run definition of mass data transfer into R/3
* rundeftext = " dxrundef_t Run Definition Texts for Mass Data Transfer
* taskdata = " dxtasks Tasks for Mass Data Transfer to R/3
* tasktext = " dxtasks_t Task Texts for Mass Data Transfer to R/3
* attribdata = " dxattrib Attributes for Transfer Using BAPIs
* attribdata2 = " dxattrib2 Task Attributes
* attribdata3 = " dxattrib3 Attribute of Task of Type Split
* attribdata4 = " dxattrib4 Attributes of Task of Type MAP DMCW
* input_files = " dxfilelp Assignment of Files to Tasks
* output_files = " dxfilelp Assignment of Files to Tasks
* rundata = " dxrun Data Transfer Run to R/3
EXCEPTIONS
PROJECT_DOES_NOT_EXIST = 1 "
DB_ERROR = 2 "
NO_AUTHORITY = 3 "
. " DX_PROJECT_GET_COMPLETE
The ABAP code below is a full code listing to execute function module DX_PROJECT_GET_COMPLETE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_projectdata | TYPE DXPROJ , |
| it_projecttext | TYPE STANDARD TABLE OF DXPROJ_T,"TABLES PARAM |
| wa_projecttext | LIKE LINE OF it_projecttext , |
| it_subprojectdata | TYPE STANDARD TABLE OF DXSUBPRO,"TABLES PARAM |
| wa_subprojectdata | LIKE LINE OF it_subprojectdata , |
| it_subprojecttext | TYPE STANDARD TABLE OF DXSUBPRO_T,"TABLES PARAM |
| wa_subprojecttext | LIKE LINE OF it_subprojecttext , |
| it_rundefdata | TYPE STANDARD TABLE OF DXRUNDEF,"TABLES PARAM |
| wa_rundefdata | LIKE LINE OF it_rundefdata , |
| it_rundeftext | TYPE STANDARD TABLE OF DXRUNDEF_T,"TABLES PARAM |
| wa_rundeftext | LIKE LINE OF it_rundeftext , |
| it_taskdata | TYPE STANDARD TABLE OF DXTASKS,"TABLES PARAM |
| wa_taskdata | LIKE LINE OF it_taskdata , |
| it_tasktext | TYPE STANDARD TABLE OF DXTASKS_T,"TABLES PARAM |
| wa_tasktext | LIKE LINE OF it_tasktext , |
| it_attribdata | TYPE STANDARD TABLE OF DXATTRIB,"TABLES PARAM |
| wa_attribdata | LIKE LINE OF it_attribdata , |
| it_attribdata2 | TYPE STANDARD TABLE OF DXATTRIB2,"TABLES PARAM |
| wa_attribdata2 | LIKE LINE OF it_attribdata2 , |
| it_attribdata3 | TYPE STANDARD TABLE OF DXATTRIB3,"TABLES PARAM |
| wa_attribdata3 | LIKE LINE OF it_attribdata3 , |
| it_attribdata4 | TYPE STANDARD TABLE OF DXATTRIB4,"TABLES PARAM |
| wa_attribdata4 | LIKE LINE OF it_attribdata4 , |
| it_input_files | TYPE STANDARD TABLE OF DXFILELP,"TABLES PARAM |
| wa_input_files | LIKE LINE OF it_input_files , |
| it_output_files | TYPE STANDARD TABLE OF DXFILELP,"TABLES PARAM |
| wa_output_files | LIKE LINE OF it_output_files , |
| it_rundata | TYPE STANDARD TABLE OF DXRUN,"TABLES PARAM |
| wa_rundata | LIKE LINE OF it_rundata . |
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_projectdata | TYPE DXPROJ , |
| ld_project | TYPE DXSUBPRO-PROJECT , |
| it_projecttext | TYPE STANDARD TABLE OF DXPROJ_T , |
| wa_projecttext | LIKE LINE OF it_projecttext, |
| it_subprojectdata | TYPE STANDARD TABLE OF DXSUBPRO , |
| wa_subprojectdata | LIKE LINE OF it_subprojectdata, |
| it_subprojecttext | TYPE STANDARD TABLE OF DXSUBPRO_T , |
| wa_subprojecttext | LIKE LINE OF it_subprojecttext, |
| it_rundefdata | TYPE STANDARD TABLE OF DXRUNDEF , |
| wa_rundefdata | LIKE LINE OF it_rundefdata, |
| it_rundeftext | TYPE STANDARD TABLE OF DXRUNDEF_T , |
| wa_rundeftext | LIKE LINE OF it_rundeftext, |
| it_taskdata | TYPE STANDARD TABLE OF DXTASKS , |
| wa_taskdata | LIKE LINE OF it_taskdata, |
| it_tasktext | TYPE STANDARD TABLE OF DXTASKS_T , |
| wa_tasktext | LIKE LINE OF it_tasktext, |
| it_attribdata | TYPE STANDARD TABLE OF DXATTRIB , |
| wa_attribdata | LIKE LINE OF it_attribdata, |
| it_attribdata2 | TYPE STANDARD TABLE OF DXATTRIB2 , |
| wa_attribdata2 | LIKE LINE OF it_attribdata2, |
| it_attribdata3 | TYPE STANDARD TABLE OF DXATTRIB3 , |
| wa_attribdata3 | LIKE LINE OF it_attribdata3, |
| it_attribdata4 | TYPE STANDARD TABLE OF DXATTRIB4 , |
| wa_attribdata4 | LIKE LINE OF it_attribdata4, |
| it_input_files | TYPE STANDARD TABLE OF DXFILELP , |
| wa_input_files | LIKE LINE OF it_input_files, |
| it_output_files | TYPE STANDARD TABLE OF DXFILELP , |
| wa_output_files | LIKE LINE OF it_output_files, |
| it_rundata | TYPE STANDARD TABLE OF DXRUN , |
| wa_rundata | LIKE LINE OF it_rundata. |
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name DX_PROJECT_GET_COMPLETE or its description.