SAP SALP_GET_COLLREORG_SCHEME Function Module for
SALP_GET_COLLREORG_SCHEME is a standard salp get collreorg scheme 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 salp get collreorg scheme FM, simply by entering the name SALP_GET_COLLREORG_SCHEME into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALP
Program Name: SAPLSALP
Main Program: SAPLSALP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SALP_GET_COLLREORG_SCHEME 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 'SALP_GET_COLLREORG_SCHEME'".
EXPORTING
SYSID = "System ID
* USE_PRIO = 'X' "Single-Character Flag
MCNAME = "Context name
NUMRANGE = "
UID = "CID
CLASS = "
MTECLASS = "
PARENT_UID = "ALert: Unique Identifier for Monitoring Types (used in TID)
PARENT_MTECLASS = "CCMS Monitoring Architecture: Name of MTE class
CRAT = "Alert: Assignment of Reorg/Coll Schema to MTE (Sorted Table)
IMPORTING
ASSIGNTAB = "Alert: Assignment of Reorg/Coll Schema to MTE (Sorted Table)
EXCEPTIONS
NO_ASSIGNMENT_FOR_TID = 1
IMPORTING Parameters details for SALP_GET_COLLREORG_SCHEME
SYSID - System ID
Data type: SYSYSIDOptional: No
Call by Reference: Yes
USE_PRIO - Single-Character Flag
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MCNAME - Context name
Data type: ALMCNAMEOptional: No
Call by Reference: Yes
NUMRANGE -
Data type: ALTIDNUMRGOptional: No
Call by Reference: Yes
UID - CID
Data type: ALTIDUIDOptional: No
Call by Reference: Yes
CLASS -
Data type: ALTIDMTCLOptional: No
Call by Reference: Yes
MTECLASS -
Data type: ALMTECLASSOptional: No
Call by Reference: Yes
PARENT_UID - ALert: Unique Identifier for Monitoring Types (used in TID)
Data type: ALTIDUIDOptional: No
Call by Reference: Yes
PARENT_MTECLASS - CCMS Monitoring Architecture: Name of MTE class
Data type: ALMTECLASSOptional: No
Call by Reference: Yes
CRAT - Alert: Assignment of Reorg/Coll Schema to MTE (Sorted Table)
Data type: ALPFASSIGN_S_TABOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SALP_GET_COLLREORG_SCHEME
ASSIGNTAB - Alert: Assignment of Reorg/Coll Schema to MTE (Sorted Table)
Data type: ALPFASSIGN_S_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ASSIGNMENT_FOR_TID -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SALP_GET_COLLREORG_SCHEME 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_sysid | TYPE SYSYSID, " | |||
| lv_assigntab | TYPE ALPFASSIGN_S_TAB, " | |||
| lv_no_assignment_for_tid | TYPE ALPFASSIGN_S_TAB, " | |||
| lv_use_prio | TYPE CHAR1, " 'X' | |||
| lv_mcname | TYPE ALMCNAME, " | |||
| lv_numrange | TYPE ALTIDNUMRG, " | |||
| lv_uid | TYPE ALTIDUID, " | |||
| lv_class | TYPE ALTIDMTCL, " | |||
| lv_mteclass | TYPE ALMTECLASS, " | |||
| lv_parent_uid | TYPE ALTIDUID, " | |||
| lv_parent_mteclass | TYPE ALMTECLASS, " | |||
| lv_crat | TYPE ALPFASSIGN_S_TAB. " |
|   CALL FUNCTION 'SALP_GET_COLLREORG_SCHEME' " |
| EXPORTING | ||
| SYSID | = lv_sysid | |
| USE_PRIO | = lv_use_prio | |
| MCNAME | = lv_mcname | |
| NUMRANGE | = lv_numrange | |
| UID | = lv_uid | |
| CLASS | = lv_class | |
| MTECLASS | = lv_mteclass | |
| PARENT_UID | = lv_parent_uid | |
| PARENT_MTECLASS | = lv_parent_mteclass | |
| CRAT | = lv_crat | |
| IMPORTING | ||
| ASSIGNTAB | = lv_assigntab | |
| EXCEPTIONS | ||
| NO_ASSIGNMENT_FOR_TID = 1 | ||
| . " SALP_GET_COLLREORG_SCHEME | ||
ABAP code using 7.40 inline data declarations to call FM SALP_GET_COLLREORG_SCHEME
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.| DATA(ld_use_prio) | = 'X'. | |||
Search for further information about these or an SAP related objects