TP_1G_CLIENT_FILE_DELETE SAP Function module

TP_1G_CLIENT_FILE_DELETE 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 TP_1G_CLIENT_FILE_DELETE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FITP_GALILEO_GENERAL
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM TP_1G_CLIENT_FILE_DELETE - TP 1G CLIENT FILE DELETE

CALL FUNCTION 'TP_1G_CLIENT_FILE_DELETE' "
  EXPORTING
    contexthandler =            " ftps_api-ctxtid  Context handler
    connect_param =             " ta23profile_sync  Assignment Parameters for Preference Synchronization
  CHANGING
    pernr_upd =                 " ftps_pernr_upd  Control Parameters For GDS Profile Synchronization
  EXCEPTIONS
    NO_DESTINATION = 1          "               No RFC destination found
    CONNECTION_ERROR = 2        "               Connection Error
    INVALID_CONTEXT = 3         "               Invalid context
    RFC_ERROR = 4               "               RFC Connection Error
    FILE_DELETION_FAILED = 5    "
    GENERAL_API_ERROR = 6       "               General API error
    .  "  TP_1G_CLIENT_FILE_DELETE

ABAP code example for Function Module TP_1G_CLIENT_FILE_DELETE

The ABAP code below is a full code listing to execute function module TP_1G_CLIENT_FILE_DELETE 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).

DATA(ld_pernr_upd) = 'Check type of data required'.


DATA(ld_contexthandler) = 123 

DATA(ld_connect_param) = 'some text here'.
.

CALL FUNCTION 'TP_1G_CLIENT_FILE_DELETE'
  EXPORTING
    contexthandler =             ld_contexthandler
    connect_param =              ld_connect_param
  CHANGING
    pernr_upd =                  ld_pernr_upd
  EXCEPTIONS
    NO_DESTINATION =             1
    CONNECTION_ERROR =           2
    INVALID_CONTEXT =            3
    RFC_ERROR =                  4
    FILE_DELETION_FAILED =       5
    GENERAL_API_ERROR =          6
    .  "  TP_1G_CLIENT_FILE_DELETE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

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_pernr_upd
 
 TYPE FTPS_PERNR_UPD ,
ld_contexthandler
 
 TYPE FTPS_API-CTXTID ,
ld_connect_param
 
 TYPE TA23PROFILE_SYNC .


ld_pernr_upd = 'some text here'.

ld_contexthandler = 123 
ld_connect_param = 'some text here'.