SAP ISM_SHIPORDPOS_GETLIST Function Module for Determine List of Shipping Order Items
ISM_SHIPORDPOS_GETLIST is a standard ism shipordpos getlist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine List of Shipping Order Items 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 ism shipordpos getlist FM, simply by entering the name ISM_SHIPORDPOS_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: JVSO
Program Name: SAPLJVSO
Main Program: SAPLJVSO
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISM_SHIPORDPOS_GETLIST 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 'ISM_SHIPORDPOS_GETLIST'"Determine List of Shipping Order Items.
EXPORTING
* SHIPORDNBR = "Address-Based Shipping Order Number
* REFDOC = "
* DATE_VALID = "Date
* DATE_VALID_TO = "To-Date
* DISTRICT = "Carrier Route
* DELIV_ROUND = "IS-M: Delivery Round
* VIABILITY = "Sequence Number for Delivery/Home Delivery Viability Set
* FROMPOSNBR = "Address-Based Shipping Order Item Number
* TOPOSNBR = "Address-Based Shipping Order Item Number
MAX_ROWS = 0 "Maximum Number of Selected Entries
* INCOMPLETE = "IS-M: Viability Data Incomplete for Item
* ADDRESS_CHANGED = "IS-M/SD: Address changed
* DOCNBR_CUST = "IS-M/SD: Customer Document Number
* DOCPOSNBR_CUST = "IS-M/SD: Customer Document Item Number
* DOCNBR_TYPE = "IS-M/SD: Origin of document number
TABLES
* IN_ADRNR_TAB = "
SHIPORDPOSLIST = "IS-M/SD Shipping Order Item
* SHIPADDRESSLIST = "IS-M/SD: Extended Adress Management
RETURN = "
EXCEPTIONS
NOTHING_FOUND = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLJVSO_001 IS-M: User Exit for Logistical Delivery Type and Shipping Date of Delivery
EXIT_SAPLJVSO_002 IS-M/SD User Exit for Importing Shipping Orders
IMPORTING Parameters details for ISM_SHIPORDPOS_GETLIST
SHIPORDNBR - Address-Based Shipping Order Number
Data type: SHIPORDNBROptional: Yes
Call by Reference: No ( called with pass by value option)
REFDOC -
Data type: REMELD_ISPOptional: Yes
Call by Reference: No ( called with pass by value option)
DATE_VALID - Date
Data type: DOptional: Yes
Call by Reference: No ( called with pass by value option)
DATE_VALID_TO - To-Date
Data type: DOptional: Yes
Call by Reference: No ( called with pass by value option)
DISTRICT - Carrier Route
Data type: BEZIRKOptional: Yes
Call by Reference: No ( called with pass by value option)
DELIV_ROUND - IS-M: Delivery Round
Data type: BEZRUNDEOptional: Yes
Call by Reference: No ( called with pass by value option)
VIABILITY - Sequence Number for Delivery/Home Delivery Viability Set
Data type: LIEFBARNROptional: Yes
Call by Reference: No ( called with pass by value option)
FROMPOSNBR - Address-Based Shipping Order Item Number
Data type: SHIPORDPOSNBROptional: Yes
Call by Reference: No ( called with pass by value option)
TOPOSNBR - Address-Based Shipping Order Item Number
Data type: SHIPORDPOSNBROptional: Yes
Call by Reference: No ( called with pass by value option)
MAX_ROWS - Maximum Number of Selected Entries
Data type: TBMAXSELOptional: No
Call by Reference: No ( called with pass by value option)
INCOMPLETE - IS-M: Viability Data Incomplete for Item
Data type: XUNVLIEFEROptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRESS_CHANGED - IS-M/SD: Address changed
Data type: JVADDRESS_CHANGEDOptional: Yes
Call by Reference: No ( called with pass by value option)
DOCNBR_CUST - IS-M/SD: Customer Document Number
Data type: JV_DOCNBR_CUSTOptional: Yes
Call by Reference: No ( called with pass by value option)
DOCPOSNBR_CUST - IS-M/SD: Customer Document Item Number
Data type: JV_DOCPOSNBR_CUSTOptional: Yes
Call by Reference: No ( called with pass by value option)
DOCNBR_TYPE - IS-M/SD: Origin of document number
Data type: JV_DOCNBR_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISM_SHIPORDPOS_GETLIST
IN_ADRNR_TAB -
Data type: JSA01_ADRESS_TABOptional: Yes
Call by Reference: Yes
SHIPORDPOSLIST - IS-M/SD Shipping Order Item
Data type: JVSOPOptional: No
Call by Reference: Yes
SHIPADDRESSLIST - IS-M/SD: Extended Adress Management
Data type: JVSOP_ADDRESSOptional: Yes
Call by Reference: Yes
RETURN -
Data type: JYMSG_T_MSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOTHING_FOUND - No suitable items found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_SHIPORDPOS_GETLIST 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_shipordnbr | TYPE SHIPORDNBR, " | |||
lt_in_adrnr_tab | TYPE STANDARD TABLE OF JSA01_ADRESS_TAB, " | |||
lv_nothing_found | TYPE JSA01_ADRESS_TAB, " | |||
lv_refdoc | TYPE REMELD_ISP, " | |||
lv_date_valid | TYPE D, " | |||
lv_date_valid_to | TYPE D, " | |||
lv_district | TYPE BEZIRK, " | |||
lv_deliv_round | TYPE BEZRUNDE, " | |||
lv_viability | TYPE LIEFBARNR, " | |||
lv_fromposnbr | TYPE SHIPORDPOSNBR, " | |||
lt_shipordposlist | TYPE STANDARD TABLE OF JVSOP, " | |||
lv_toposnbr | TYPE SHIPORDPOSNBR, " | |||
lt_shipaddresslist | TYPE STANDARD TABLE OF JVSOP_ADDRESS, " | |||
lt_return | TYPE STANDARD TABLE OF JYMSG_T_MSG, " | |||
lv_max_rows | TYPE TBMAXSEL, " 0 | |||
lv_incomplete | TYPE XUNVLIEFER, " | |||
lv_address_changed | TYPE JVADDRESS_CHANGED, " | |||
lv_docnbr_cust | TYPE JV_DOCNBR_CUST, " | |||
lv_docposnbr_cust | TYPE JV_DOCPOSNBR_CUST, " | |||
lv_docnbr_type | TYPE JV_DOCNBR_TYPE. " |
  CALL FUNCTION 'ISM_SHIPORDPOS_GETLIST' "Determine List of Shipping Order Items |
EXPORTING | ||
SHIPORDNBR | = lv_shipordnbr | |
REFDOC | = lv_refdoc | |
DATE_VALID | = lv_date_valid | |
DATE_VALID_TO | = lv_date_valid_to | |
DISTRICT | = lv_district | |
DELIV_ROUND | = lv_deliv_round | |
VIABILITY | = lv_viability | |
FROMPOSNBR | = lv_fromposnbr | |
TOPOSNBR | = lv_toposnbr | |
MAX_ROWS | = lv_max_rows | |
INCOMPLETE | = lv_incomplete | |
ADDRESS_CHANGED | = lv_address_changed | |
DOCNBR_CUST | = lv_docnbr_cust | |
DOCPOSNBR_CUST | = lv_docposnbr_cust | |
DOCNBR_TYPE | = lv_docnbr_type | |
TABLES | ||
IN_ADRNR_TAB | = lt_in_adrnr_tab | |
SHIPORDPOSLIST | = lt_shipordposlist | |
SHIPADDRESSLIST | = lt_shipaddresslist | |
RETURN | = lt_return | |
EXCEPTIONS | ||
NOTHING_FOUND = 1 | ||
. " ISM_SHIPORDPOS_GETLIST |
ABAP code using 7.40 inline data declarations to call FM ISM_SHIPORDPOS_GETLIST
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