SAP SET_SOURCE_TYPE Function Module for Analyze the transfer order data to display adequate source screen









SET_SOURCE_TYPE is a standard set source type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Analyze the transfer order data to display adequate source screen 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 set source type FM, simply by entering the name SET_SOURCE_TYPE into the relevant SAP transaction such as SE37 or SE38.

Function Group: LMGT
Program Name: SAPLLMGT
Main Program: SAPLLMGT
Appliation area: L
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SET_SOURCE_TYPE 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 'SET_SOURCE_TYPE'"Analyze the transfer order data to display adequate source screen
EXPORTING
I_POST_CHANGE = "Indicator of posting changes

IMPORTING
O_SOURCE_TYPE = "Data type
O_BULK_PICK = "Bulk indicator

TABLES
T_TO_ITEMS = "TO items
.




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_SAPLLMGT_001 Extension for barcode translation
EXIT_SAPLLMGT_083 User exit for print

IMPORTING Parameters details for SET_SOURCE_TYPE

I_POST_CHANGE - Indicator of posting changes

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

EXPORTING Parameters details for SET_SOURCE_TYPE

O_SOURCE_TYPE - Data type

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

O_BULK_PICK - Bulk indicator

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

TABLES Parameters details for SET_SOURCE_TYPE

T_TO_ITEMS - TO items

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

Copy and paste ABAP code example for SET_SOURCE_TYPE 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_to_items  TYPE STANDARD TABLE OF LTAP, "   
lv_i_post_change  TYPE C, "   
lv_o_source_type  TYPE C, "   
lv_o_bulk_pick  TYPE C. "   

  CALL FUNCTION 'SET_SOURCE_TYPE'  "Analyze the transfer order data to display adequate source screen
    EXPORTING
         I_POST_CHANGE = lv_i_post_change
    IMPORTING
         O_SOURCE_TYPE = lv_o_source_type
         O_BULK_PICK = lv_o_bulk_pick
    TABLES
         T_TO_ITEMS = lt_t_to_items
. " SET_SOURCE_TYPE




ABAP code using 7.40 inline data declarations to call FM SET_SOURCE_TYPE

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!