SAP DX_PROJECT_IMPORT Function Module for
DX_PROJECT_IMPORT is a standard dx project import 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 dx project import FM, simply by entering the name DX_PROJECT_IMPORT into the relevant SAP transaction such as SE37 or SE38.
Function Group: DX_PROJECT
Program Name: SAPLDX_PROJECT
Main Program: SAPLDX_PROJECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function DX_PROJECT_IMPORT 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 'DX_PROJECT_IMPORT'".
TABLES
* PROJECTS = "Projects for Mass Data Transfer to R/3
EXCEPTIONS
CANCELED_BY_USER = 1 ERROR_WITH_BALLOG = 2 ERROR_WITH_FILE = 3 NO_AUTHORITY = 4
TABLES Parameters details for DX_PROJECT_IMPORT
PROJECTS - Projects for Mass Data Transfer to R/3
Data type: DXPROJOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
CANCELED_BY_USER -
Data type:Optional: No
Call by Reference: Yes
ERROR_WITH_BALLOG -
Data type:Optional: No
Call by Reference: Yes
ERROR_WITH_FILE -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DX_PROJECT_IMPORT 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_projects | TYPE STANDARD TABLE OF DXPROJ, " | |||
| lv_canceled_by_user | TYPE DXPROJ, " | |||
| lv_error_with_ballog | TYPE DXPROJ, " | |||
| lv_error_with_file | TYPE DXPROJ, " | |||
| lv_no_authority | TYPE DXPROJ. " |
| CALL FUNCTION 'DX_PROJECT_IMPORT' " |
| TABLES | ||
| PROJECTS | = lt_projects | |
| EXCEPTIONS | ||
| CANCELED_BY_USER = 1 | ||
| ERROR_WITH_BALLOG = 2 | ||
| ERROR_WITH_FILE = 3 | ||
| NO_AUTHORITY = 4 | ||
| . " DX_PROJECT_IMPORT | ||
ABAP code using 7.40 inline data declarations to call FM DX_PROJECT_IMPORT
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.Search for further information about these or an SAP related objects