SAP AMC_SEND_BINARY Function Module for
AMC_SEND_BINARY is a standard amc send binary 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 amc send binary FM, simply by entering the name AMC_SEND_BINARY into the relevant SAP transaction such as SE37 or SE38.
Function Group: AMC_RUNTIME
Program Name: SAPLAMC_RUNTIME
Main Program: SAPLAMC_RUNTIME
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function AMC_SEND_BINARY 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_SEND_BINARY'".
EXPORTING
CHANNEL_TAB = "
MESSAGE_TAB = "
IMPORTING
THROUGHPUT = "
EXCEPTIONS
AMC_ERROR = 1
IMPORTING Parameters details for AMC_SEND_BINARY
CHANNEL_TAB -
Data type: AMC_CHANNEL_IDENTITY_TABOptional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_TAB -
Data type: AMC_MESSAGE_BINARY_TABOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AMC_SEND_BINARY
THROUGHPUT -
Data type: DECFLOAT34Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
AMC_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for AMC_SEND_BINARY 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_amc_error | TYPE STRING, " | |||
lv_throughput | TYPE DECFLOAT34, " | |||
lv_channel_tab | TYPE AMC_CHANNEL_IDENTITY_TAB, " | |||
lv_message_tab | TYPE AMC_MESSAGE_BINARY_TAB. " |
  CALL FUNCTION 'AMC_SEND_BINARY' " |
EXPORTING | ||
CHANNEL_TAB | = lv_channel_tab | |
MESSAGE_TAB | = lv_message_tab | |
IMPORTING | ||
THROUGHPUT | = lv_throughput | |
EXCEPTIONS | ||
AMC_ERROR = 1 | ||
. " AMC_SEND_BINARY |
ABAP code using 7.40 inline data declarations to call FM AMC_SEND_BINARY
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