SAP SALI_MA_CREATE_ATTACH Function Module for









SALI_MA_CREATE_ATTACH is a standard sali ma create attach 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 sali ma create attach FM, simply by entering the name SALI_MA_CREATE_ATTACH into the relevant SAP transaction such as SE37 or SE38.

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



Function SALI_MA_CREATE_ATTACH 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 'SALI_MA_CREATE_ATTACH'"
EXPORTING
PARENT_TID = "
NAME = "
TYPECLASS = "
* SUBTYPE = AL_STD_NO_SUBCLASS "
NUMRANGE = "
UNIQUENUM = "
* MT_CLASS = "
* CUSTOMIZING_GROUP = "

IMPORTING
NEW_TID = "
DETAILED_ERROR_TEXT = "

EXCEPTIONS
INVALID_TID = 1 UNABLE_TO_EXPAND_NAME = 2 INVALID_PARAMETERS = 3 COMMUNICATION_FAILURE = 4 OTHER_PROBLEM = 5 WRONG_SEGMENT = 6 INTERNAL_FAILURE_SALS = 7 NO_SUBTYPE_FOR_MSC = 8 NO_MORE_SPACE = 9
.



IMPORTING Parameters details for SALI_MA_CREATE_ATTACH

PARENT_TID -

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

NAME -

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

TYPECLASS -

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

SUBTYPE -

Data type: ALTDEFRC-MTESUBTYPE
Default: AL_STD_NO_SUBCLASS
Optional: Yes
Call by Reference: No ( called with pass by value option)

NUMRANGE -

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

UNIQUENUM -

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

MT_CLASS -

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

CUSTOMIZING_GROUP -

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

EXPORTING Parameters details for SALI_MA_CREATE_ATTACH

NEW_TID -

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

DETAILED_ERROR_TEXT -

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

EXCEPTIONS details

INVALID_TID -

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

UNABLE_TO_EXPAND_NAME -

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

INVALID_PARAMETERS - Invalid parameter

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)

OTHER_PROBLEM -

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

WRONG_SEGMENT -

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

INTERNAL_FAILURE_SALS -

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

NO_SUBTYPE_FOR_MSC -

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

NO_MORE_SPACE -

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

Copy and paste ABAP code example for SALI_MA_CREATE_ATTACH 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_new_tid  TYPE ALGLOBTID, "   
lv_parent_tid  TYPE ALGLOBTID, "   
lv_invalid_tid  TYPE ALGLOBTID, "   
lv_name  TYPE C, "   
lv_detailed_error_text  TYPE STRING, "   
lv_unable_to_expand_name  TYPE STRING, "   
lv_typeclass  TYPE ALGLOBTID-MTCLASS, "   
lv_invalid_parameters  TYPE ALGLOBTID, "   
lv_subtype  TYPE ALTDEFRC-MTESUBTYPE, "   AL_STD_NO_SUBCLASS
lv_communication_failure  TYPE ALTDEFRC, "   
lv_numrange  TYPE ALGLOBTID-MTNUMRANGE, "   
lv_other_problem  TYPE ALGLOBTID, "   
lv_uniquenum  TYPE ALMTCREATE-UNIQUENUM, "   
lv_wrong_segment  TYPE ALMTCREATE, "   
lv_mt_class  TYPE C, "   
lv_internal_failure_sals  TYPE C, "   
lv_customizing_group  TYPE C, "   
lv_no_subtype_for_msc  TYPE C, "   
lv_no_more_space  TYPE C. "   

  CALL FUNCTION 'SALI_MA_CREATE_ATTACH'  "
    EXPORTING
         PARENT_TID = lv_parent_tid
         NAME = lv_name
         TYPECLASS = lv_typeclass
         SUBTYPE = lv_subtype
         NUMRANGE = lv_numrange
         UNIQUENUM = lv_uniquenum
         MT_CLASS = lv_mt_class
         CUSTOMIZING_GROUP = lv_customizing_group
    IMPORTING
         NEW_TID = lv_new_tid
         DETAILED_ERROR_TEXT = lv_detailed_error_text
    EXCEPTIONS
        INVALID_TID = 1
        UNABLE_TO_EXPAND_NAME = 2
        INVALID_PARAMETERS = 3
        COMMUNICATION_FAILURE = 4
        OTHER_PROBLEM = 5
        WRONG_SEGMENT = 6
        INTERNAL_FAILURE_SALS = 7
        NO_SUBTYPE_FOR_MSC = 8
        NO_MORE_SPACE = 9
. " SALI_MA_CREATE_ATTACH




ABAP code using 7.40 inline data declarations to call FM SALI_MA_CREATE_ATTACH

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.

 
 
 
 
 
 
"SELECT single MTCLASS FROM ALGLOBTID INTO @DATA(ld_typeclass).
 
 
"SELECT single MTESUBTYPE FROM ALTDEFRC INTO @DATA(ld_subtype).
DATA(ld_subtype) = AL_STD_NO_SUBCLASS.
 
 
"SELECT single MTNUMRANGE FROM ALGLOBTID INTO @DATA(ld_numrange).
 
 
"SELECT single UNIQUENUM FROM ALMTCREATE INTO @DATA(ld_uniquenum).
 
 
 
 
 
 
 


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!