SAP SO_LINK_INSERT Function Module for

Search SAP Function Modules

SO_LINK_INSERT is a standard so link insert 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 so link insert FM, simply by entering the name SO_LINK_INSERT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SOB2
Program Name: SAPLSOB2
Main Program: SAPLSOB2
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SO_LINK_INSERT 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 'SO_LINK_INSERT'"
  EXPORTING
   OBJECT_ID =  "
   LINK_ID =  "Object Type
*  OWNER = ' ' "Mailbox owner

EXCEPTIONS
   ACTIVE_USER_NOT_EXIST = 1    COMMUNICATION_FAILURE = 2    OWNER_NOT_EXIST = 3    PARAMETER_ERROR = 4    SUBSTITUTE_NOT_ACTIVE = 5    SUBSTITUTE_NOT_DEFINED = 6    SYSTEM_FAILURE = 7    X_ERROR = 8 

.

IMPORTING Parameters details for SO_LINK_INSERT

OBJECT_ID -

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

LINK_ID - Object Type

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

OWNER - Mailbox owner

Data type: SOUD-USRNAM
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ACTIVE_USER_NOT_EXIST - Active user does not exist

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

COMMUNICATION_FAILURE -

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

OWNER_NOT_EXIST - The owner of the mailbox does not exist

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

PARAMETER_ERROR - Parameter error

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

SUBSTITUTE_NOT_ACTIVE - The substitute is not activated

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

SUBSTITUTE_NOT_DEFINED - Substitute is not defined

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

SYSTEM_FAILURE -

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

X_ERROR - Internal Error

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

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

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