SAP RSSM_FILL_SHIP Function Module for Shadow table to fill InfoPackages
RSSM_FILL_SHIP is a standard rssm fill ship SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Shadow table to fill InfoPackages 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 rssm fill ship FM, simply by entering the name RSSM_FILL_SHIP into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSSM_TRANSPORT
Program Name: SAPLRSSM_TRANSPORT
Main Program: SAPLRSSM_TRANSPORT
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSSM_FILL_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 'RSSM_FILL_SHIP'"Shadow table to fill InfoPackages.
EXPORTING
I_LOGDPID = "
I_WRITE = "Boolean
IMPORTING
E_LOGDPID = "Logical InfoPackage Variant (ID)
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for RSSM_FILL_SHIP
I_LOGDPID -
Data type: RSLDPIO-LOGDPIDOptional: No
Call by Reference: Yes
I_WRITE - Boolean
Data type: RS_BOOLOptional: No
Call by Reference: Yes
EXPORTING Parameters details for RSSM_FILL_SHIP
E_LOGDPID - Logical InfoPackage Variant (ID)
Data type: RSLDPIO-LOGDPIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSSM_FILL_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: | ||||
| lv_failed | TYPE STRING, " | |||
| lv_e_logdpid | TYPE RSLDPIO-LOGDPID, " | |||
| lv_i_logdpid | TYPE RSLDPIO-LOGDPID, " | |||
| lv_i_write | TYPE RS_BOOL. " |
|   CALL FUNCTION 'RSSM_FILL_SHIP' "Shadow table to fill InfoPackages |
| EXPORTING | ||
| I_LOGDPID | = lv_i_logdpid | |
| I_WRITE | = lv_i_write | |
| IMPORTING | ||
| E_LOGDPID | = lv_e_logdpid | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " RSSM_FILL_SHIP | ||
ABAP code using 7.40 inline data declarations to call FM RSSM_FILL_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 LOGDPID FROM RSLDPIO INTO @DATA(ld_e_logdpid). | ||||
| "SELECT single LOGDPID FROM RSLDPIO INTO @DATA(ld_i_logdpid). | ||||
Search for further information about these or an SAP related objects