SAP ARFC_DEST_SHIP Function Module for









ARFC_DEST_SHIP is a standard arfc dest ship 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 arfc dest ship FM, simply by entering the name ARFC_DEST_SHIP into the relevant SAP transaction such as SE37 or SE38.

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



Function ARFC_DEST_SHIP 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 'ARFC_DEST_SHIP'"
EXPORTING
* SENDER_ID = "
* SUPPORTABILITY_INFO = "
* UNIT_ID = "

IMPORTING
RETUDATA = "
ASTATE = "
BGRFC_RETRY_KEY = "
BGRFC_RETRY_MAX_COUNT = "
BGRFC_RETRY_DELAY_TIME = "
SHUTDOWN_INSTANCE = "

CHANGING
* SHUTDOWN_ACTIVE = "

TABLES
DATA = "
STATE = "

EXCEPTIONS
NO_STATE_ENTRY_FOUND = 1 NO_END_MARKER_FOUND = 2
.



IMPORTING Parameters details for ARFC_DEST_SHIP

SENDER_ID -

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

SUPPORTABILITY_INFO -

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

UNIT_ID -

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

EXPORTING Parameters details for ARFC_DEST_SHIP

RETUDATA -

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

ASTATE -

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

BGRFC_RETRY_KEY -

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

BGRFC_RETRY_MAX_COUNT -

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

BGRFC_RETRY_DELAY_TIME -

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

SHUTDOWN_INSTANCE -

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

CHANGING Parameters details for ARFC_DEST_SHIP

SHUTDOWN_ACTIVE -

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

TABLES Parameters details for ARFC_DEST_SHIP

DATA -

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

STATE -

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

EXCEPTIONS details

NO_STATE_ENTRY_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_END_MARKER_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ARFC_DEST_SHIP 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:
lt_data  TYPE STANDARD TABLE OF ARFCRDATA, "   
lv_retudata  TYPE SY-INPUT, "   
lv_sender_id  TYPE RFCDES-RFCDEST, "   
lv_shutdown_active  TYPE SAP_BOOL, "   
lv_no_state_entry_found  TYPE SAP_BOOL, "   
lt_state  TYPE STANDARD TABLE OF ARFCRSTATE, "   
lv_astate  TYPE ARFCSSTATE-ARFCSTATE, "   
lv_no_end_marker_found  TYPE ARFCSSTATE, "   
lv_supportability_info  TYPE BGRFC_SUPPORTABILITY_INFO, "   
lv_unit_id  TYPE BGRFC_UNIT_ID, "   
lv_bgrfc_retry_key  TYPE BGRFC_RETRY_KEY, "   
lv_bgrfc_retry_max_count  TYPE INT4, "   
lv_bgrfc_retry_delay_time  TYPE INT4, "   
lv_shutdown_instance  TYPE MSNAME2. "   

  CALL FUNCTION 'ARFC_DEST_SHIP'  "
    EXPORTING
         SENDER_ID = lv_sender_id
         SUPPORTABILITY_INFO = lv_supportability_info
         UNIT_ID = lv_unit_id
    IMPORTING
         RETUDATA = lv_retudata
         ASTATE = lv_astate
         BGRFC_RETRY_KEY = lv_bgrfc_retry_key
         BGRFC_RETRY_MAX_COUNT = lv_bgrfc_retry_max_count
         BGRFC_RETRY_DELAY_TIME = lv_bgrfc_retry_delay_time
         SHUTDOWN_INSTANCE = lv_shutdown_instance
    CHANGING
         SHUTDOWN_ACTIVE = lv_shutdown_active
    TABLES
         DATA = lt_data
         STATE = lt_state
    EXCEPTIONS
        NO_STATE_ENTRY_FOUND = 1
        NO_END_MARKER_FOUND = 2
. " ARFC_DEST_SHIP




ABAP code using 7.40 inline data declarations to call FM ARFC_DEST_SHIP

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 INPUT FROM SY INTO @DATA(ld_retudata).
 
"SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_sender_id).
 
 
 
 
"SELECT single ARFCSTATE FROM ARFCSSTATE INTO @DATA(ld_astate).
 
 
 
 
 
 
 
 


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!