SAP ALINK_CHANGE_CLIENT_DIRECT Function Module for









ALINK_CHANGE_CLIENT_DIRECT is a standard alink change client direct 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 alink change client direct FM, simply by entering the name ALINK_CHANGE_CLIENT_DIRECT into the relevant SAP transaction such as SE37 or SE38.

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



Function ALINK_CHANGE_CLIENT_DIRECT 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 'ALINK_CHANGE_CLIENT_DIRECT'"
EXPORTING
ZMANDT = "
TOAV0 = "
IGNORE_DOUBLE_LINKS = "

EXCEPTIONS
ERROR_INSERT = 1 ERROR_SOURCE = 2 ERROR_TARGET = 3 ERROR_DELETION = 4 ERROR_UNIQUE = 5 ERROR_MANDANT = 6
.



IMPORTING Parameters details for ALINK_CHANGE_CLIENT_DIRECT

ZMANDT -

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

TOAV0 -

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

IGNORE_DOUBLE_LINKS -

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

EXCEPTIONS details

ERROR_INSERT -

Data type:
Optional: No
Call by Reference: Yes

ERROR_SOURCE -

Data type:
Optional: No
Call by Reference: Yes

ERROR_TARGET -

Data type:
Optional: No
Call by Reference: Yes

ERROR_DELETION -

Data type:
Optional: No
Call by Reference: Yes

ERROR_UNIQUE -

Data type:
Optional: No
Call by Reference: Yes

ERROR_MANDANT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ALINK_CHANGE_CLIENT_DIRECT 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:
lv_zmandt  TYPE SYMANDT, "   
lv_error_insert  TYPE SYMANDT, "   
lv_toav0  TYPE TOAV0, "   
lv_error_source  TYPE TOAV0, "   
lv_error_target  TYPE TOAV0, "   
lv_ignore_double_links  TYPE CHAR1, "   
lv_error_deletion  TYPE CHAR1, "   
lv_error_unique  TYPE CHAR1, "   
lv_error_mandant  TYPE CHAR1. "   

  CALL FUNCTION 'ALINK_CHANGE_CLIENT_DIRECT'  "
    EXPORTING
         ZMANDT = lv_zmandt
         TOAV0 = lv_toav0
         IGNORE_DOUBLE_LINKS = lv_ignore_double_links
    EXCEPTIONS
        ERROR_INSERT = 1
        ERROR_SOURCE = 2
        ERROR_TARGET = 3
        ERROR_DELETION = 4
        ERROR_UNIQUE = 5
        ERROR_MANDANT = 6
. " ALINK_CHANGE_CLIENT_DIRECT




ABAP code using 7.40 inline data declarations to call FM ALINK_CHANGE_CLIENT_DIRECT

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!