SAP DX_SPLIT_FILE Function Module for

Search SAP Function Modules

DX_SPLIT_FILE is a standard dx split file 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 split file FM, simply by entering the name DX_SPLIT_FILE into the relevant SAP transaction such as SE37 or SE38.

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

Function DX_SPLIT_FILE 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_SPLIT_FILE'"
  EXPORTING
   FILENAME =  "File Name
*  PROJECT =  "Data Transfer Project
*  SUBPROJECT =  "Data Transfer Subproject
*  RUNDEF =  "Data Transfer - Run Definition
*  RUNID =  "Data Transfer Run
   OBJECTTYPE =  "Business object type
   PROGTYPE =  "Program Type
   PROGNAME =  "Program Name
   SPLITYPE =  "
*  NUM_RECORD =  "
*  NUM_LINE =  "
*  DELSOURCE = ' ' "
*  DELTARGET = ' ' "

 IMPORTING
   TOT_RECORD_NO =  "
   RETURN =  "

TABLES
*  T_SPLIT_FILE =  "
*  T_OPEN_FILE =  "

.

IMPORTING Parameters details for DX_SPLIT_FILE

FILENAME - File Name

Data type: DXFILEN-FILENAME
Optional: No
Call by Reference: Yes

PROJECT - Data Transfer Project

Data type: DXATTRIB3-PROJECT
Optional: Yes
Call by Reference: Yes

SUBPROJECT - Data Transfer Subproject

Data type: DXATTRIB3-SUBPROJECT
Optional: Yes
Call by Reference: Yes

RUNDEF - Data Transfer - Run Definition

Data type: DXATTRIB3-RUNDEF
Optional: Yes
Call by Reference: Yes

RUNID - Data Transfer Run

Data type: DXRUN-RUNID
Optional: Yes
Call by Reference: Yes

OBJECTTYPE - Business object type

Data type: DXATTRIB3-OBJECTTYPE
Optional: No
Call by Reference: Yes

PROGTYPE - Program Type

Data type: DXATTRIB3-PROGTYPE
Optional: No
Call by Reference: Yes

PROGNAME - Program Name

Data type: DXATTRIB3-PROGNAME
Optional: No
Call by Reference: Yes

SPLITYPE -

Data type: DXATTRIB3-SPLITTYPE
Optional: No
Call by Reference: Yes

NUM_RECORD -

Data type: DXATTRIB3-OBJECTNO
Optional: Yes
Call by Reference: Yes

NUM_LINE -

Data type: DXATTRIB3-LINESNO
Optional: Yes
Call by Reference: Yes

DELSOURCE -

Data type: DXATTRIB3-DELSOURCE
Default: ' '
Optional: Yes
Call by Reference: Yes

DELTARGET -

Data type: DXATTRIB3-DELTARGET
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for DX_SPLIT_FILE

TOT_RECORD_NO -

Data type: DXATTRIB3-OBJECTNO
Optional: No
Call by Reference: Yes

RETURN -

Data type: DXRETURN
Optional: No
Call by Reference: Yes

TABLES Parameters details for DX_SPLIT_FILE

T_SPLIT_FILE -

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

T_OPEN_FILE -

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

Copy and paste ABAP code example for DX_SPLIT_FILE 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.

ABAP code using 7.40 inline data declarations to call FM DX_SPLIT_FILE

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