SAP J_1S_SHIPPING_DATA_GET_BUNDLE Function Module for









J_1S_SHIPPING_DATA_GET_BUNDLE is a standard j 1s shipping data get bundle 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 j 1s shipping data get bundle FM, simply by entering the name J_1S_SHIPPING_DATA_GET_BUNDLE into the relevant SAP transaction such as SE37 or SE38.

Function Group: J1S5
Program Name: SAPLJ1S5
Main Program: SAPLJ1S5
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function J_1S_SHIPPING_DATA_GET_BUNDLE 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 'J_1S_SHIPPING_DATA_GET_BUNDLE'"
EXPORTING
* CONTAINERNR = "
* PRODSEQ = "

TABLES
OUT_BUNDLE = "
.



IMPORTING Parameters details for J_1S_SHIPPING_DATA_GET_BUNDLE

CONTAINERNR -

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

PRODSEQ -

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

TABLES Parameters details for J_1S_SHIPPING_DATA_GET_BUNDLE

OUT_BUNDLE -

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

Copy and paste ABAP code example for J_1S_SHIPPING_DATA_GET_BUNDLE 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_out_bundle  TYPE STANDARD TABLE OF J_1S_RBUND, "   
lv_containernr  TYPE JVTGEBINDE-GEBINDENR, "   
lv_prodseq  TYPE JVTVERZPLZ-PRODSEQ. "   

  CALL FUNCTION 'J_1S_SHIPPING_DATA_GET_BUNDLE'  "
    EXPORTING
         CONTAINERNR = lv_containernr
         PRODSEQ = lv_prodseq
    TABLES
         OUT_BUNDLE = lt_out_bundle
. " J_1S_SHIPPING_DATA_GET_BUNDLE




ABAP code using 7.40 inline data declarations to call FM J_1S_SHIPPING_DATA_GET_BUNDLE

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 GEBINDENR FROM JVTGEBINDE INTO @DATA(ld_containernr).
 
"SELECT single PRODSEQ FROM JVTVERZPLZ INTO @DATA(ld_prodseq).
 


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!