SAP AMC_PATTERN_RECEIVER_SESSION Function Module for Internal use only: Create AMC receiver session for certain channel id
AMC_PATTERN_RECEIVER_SESSION is a standard amc pattern receiver session SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Internal use only: Create AMC receiver session for certain channel id processing and below is the pattern details for this FM, 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 amc pattern receiver session FM, simply by entering the name AMC_PATTERN_RECEIVER_SESSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SAMC_PATTERN_TEST
Program Name: SAPLSAMC_PATTERN_TEST
Main Program: SAPLSAMC_PATTERN_TEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function AMC_PATTERN_RECEIVER_SESSION 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 'AMC_PATTERN_RECEIVER_SESSION'"Internal use only: Create AMC receiver session for certain channel id.
EXPORTING
* IV_ACTION = 'S' "S: Send, R: Recieve
IV_MESSAGE = "
IV_CHANNEL_ID = "Identifier of the ABAP Messaging Channel
IV_CHANNEL_EXTENSION_ID = "Extension to the Channel Ids
IV_BACK_CHANNEL_ID = "Identifier of the ABAP Messaging Channel
IV_BACK_CHANNEL_EXTENSION_ID = "Extension to the Channel Ids
IMPORTING
EV_MESSAGE = "
IMPORTING Parameters details for AMC_PATTERN_RECEIVER_SESSION
IV_ACTION - S: Send, R: Recieve
Data type: SYINPUTDefault: 'S'
Optional: No
Call by Reference: No ( called with pass by value option)
IV_MESSAGE -
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
IV_CHANNEL_ID - Identifier of the ABAP Messaging Channel
Data type: AMC_CHANNEL_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_CHANNEL_EXTENSION_ID - Extension to the Channel Ids
Data type: AMC_CHANNEL_EXTENSION_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_BACK_CHANNEL_ID - Identifier of the ABAP Messaging Channel
Data type: AMC_CHANNEL_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_BACK_CHANNEL_EXTENSION_ID - Extension to the Channel Ids
Data type: AMC_CHANNEL_EXTENSION_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AMC_PATTERN_RECEIVER_SESSION
EV_MESSAGE -
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AMC_PATTERN_RECEIVER_SESSION 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_iv_action | TYPE SYINPUT, " 'S' | |||
| lv_ev_message | TYPE STRING, " | |||
| lv_iv_message | TYPE STRING, " | |||
| lv_iv_channel_id | TYPE AMC_CHANNEL_ID, " | |||
| lv_iv_channel_extension_id | TYPE AMC_CHANNEL_EXTENSION_ID, " | |||
| lv_iv_back_channel_id | TYPE AMC_CHANNEL_ID, " | |||
| lv_iv_back_channel_extension_id | TYPE AMC_CHANNEL_EXTENSION_ID. " |
|   CALL FUNCTION 'AMC_PATTERN_RECEIVER_SESSION' "Internal use only: Create AMC receiver session for certain channel id |
| EXPORTING | ||
| IV_ACTION | = lv_iv_action | |
| IV_MESSAGE | = lv_iv_message | |
| IV_CHANNEL_ID | = lv_iv_channel_id | |
| IV_CHANNEL_EXTENSION_ID | = lv_iv_channel_extension_id | |
| IV_BACK_CHANNEL_ID | = lv_iv_back_channel_id | |
| IV_BACK_CHANNEL_EXTENSION_ID | = lv_iv_back_channel_extension_id | |
| IMPORTING | ||
| EV_MESSAGE | = lv_ev_message | |
| . " AMC_PATTERN_RECEIVER_SESSION | ||
ABAP code using 7.40 inline data declarations to call FM AMC_PATTERN_RECEIVER_SESSION
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_iv_action) | = 'S'. | |||
Search for further information about these or an SAP related objects