SAP IBIP_DATASET_SERVER Function Module for NOTRANSL: IBIP: Check dataset exists on remote server

Search SAP Function Modules

IBIP_DATASET_SERVER is a standard ibip dataset server SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: IBIP: Check dataset exists on remote server processing and below is the pattern details for this FM, 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 ibip dataset server FM, simply by entering the name IBIP_DATASET_SERVER into the relevant SAP transaction such as SE37 or SE38.

Function Group: IBIP
Program Name: SAPLIBIP
Main Program: SAPLIBIP
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function IBIP_DATASET_SERVER 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 'IBIP_DATASET_SERVER'"NOTRANSL: IBIP: Check dataset exists on remote server
  EXPORTING
   DS_NAME =  "Local file for upload/download
   TEXTMODE =  "Source File is in Text Format
   ACTIVITY =  "Individual, User-Defined Character
*  RECLENGTH =  "Source File Record Length - Only for Binary Files

 IMPORTING
   ACTIVITY_RC =  "ABAP System Field: Return Code of ABAP Statements

TABLES
   DATA_TAB =  "IBIP: Data transfer template - internal table structure

EXCEPTIONS
   NO_FILE_ON_SERVER = 1    DATASET_ALREADY_EXISTS = 2    DATASET_READ = 3    DATASET_WRITTEN = 4 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLIBIP_001 User Exit: Data Transfer Module (IBIP Batch Input)

IMPORTING Parameters details for IBIP_DATASET_SERVER

DS_NAME - Local file for upload/download

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

TEXTMODE - Source File is in Text Format

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

ACTIVITY - Individual, User-Defined Character

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

RECLENGTH - Source File Record Length - Only for Binary Files

Data type: IBIPPARMS-RECLEN
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for IBIP_DATASET_SERVER

ACTIVITY_RC - ABAP System Field: Return Code of ABAP Statements

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

TABLES Parameters details for IBIP_DATASET_SERVER

DATA_TAB - IBIP: Data transfer template - internal table structure

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

EXCEPTIONS details

NO_FILE_ON_SERVER -

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

DATASET_ALREADY_EXISTS -

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

DATASET_READ -

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

DATASET_WRITTEN -

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

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

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