SAP MY_GOODS_ISSUES_GET Function Module for









MY_GOODS_ISSUES_GET is a standard my goods issues get 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 my goods issues get FM, simply by entering the name MY_GOODS_ISSUES_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: RNIW
Program Name: SAPLRNIW
Main Program: SAPLRNIW
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MY_GOODS_ISSUES_GET 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 'MY_GOODS_ISSUES_GET'"
  EXPORTING
*  I_SOURCE_FLAG =  "
   I_BUKRS =  "Company Code
   IS_NIWE =  "Transfer Structure for Lowest Value Determination
*  IS_NIWE1 =  "Transfer Structure for Lowest Value Determination
*  IS_NIWE2 =  "Transfer Structure for Lowest Value Determination

TABLES
   T_BEW =  "Structure for Devaluations due to Range of Cov./Non-Movement
   TRA_MATNR =  "Structure of a Range Table for an 18 Character Field
   TRA_WERKS =  "Structure of a range table for a character (4) field
   TRA_BWTAR =  "Structure of a Range Table for a (10) Character Field

EXCEPTIONS
   NOT_FOUND = 1
.



IMPORTING Parameters details for MY_GOODS_ISSUES_GET

I_SOURCE_FLAG -

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

I_BUKRS - Company Code

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

IS_NIWE - Transfer Structure for Lowest Value Determination

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

IS_NIWE1 - Transfer Structure for Lowest Value Determination

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

IS_NIWE2 - Transfer Structure for Lowest Value Determination

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

TABLES Parameters details for MY_GOODS_ISSUES_GET

T_BEW - Structure for Devaluations due to Range of Cov./Non-Movement

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

TRA_MATNR - Structure of a Range Table for an 18 Character Field

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

TRA_WERKS - Structure of a range table for a character (4) field

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

TRA_BWTAR - Structure of a Range Table for a (10) Character Field

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for MY_GOODS_ISSUES_GET 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_t_bew  TYPE STANDARD TABLE OF SNIWEBEW, "   
lv_not_found  TYPE SNIWEBEW, "   
lv_i_source_flag  TYPE C, "   
lv_i_bukrs  TYPE BUKRS, "   
lt_tra_matnr  TYPE STANDARD TABLE OF RANGE_C18, "   
lv_is_niwe  TYPE SNIWE, "   
lt_tra_werks  TYPE STANDARD TABLE OF RANGE_C4, "   
lv_is_niwe1  TYPE SNIWE1, "   
lt_tra_bwtar  TYPE STANDARD TABLE OF RANGE_C10, "   
lv_is_niwe2  TYPE SNIWE2. "   

  CALL FUNCTION 'MY_GOODS_ISSUES_GET'  "
    EXPORTING
         I_SOURCE_FLAG = lv_i_source_flag
         I_BUKRS = lv_i_bukrs
         IS_NIWE = lv_is_niwe
         IS_NIWE1 = lv_is_niwe1
         IS_NIWE2 = lv_is_niwe2
    TABLES
         T_BEW = lt_t_bew
         TRA_MATNR = lt_tra_matnr
         TRA_WERKS = lt_tra_werks
         TRA_BWTAR = lt_tra_bwtar
    EXCEPTIONS
        NOT_FOUND = 1
. " MY_GOODS_ISSUES_GET




ABAP code using 7.40 inline data declarations to call FM MY_GOODS_ISSUES_GET

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



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!