SAP L_TO_ADD_ITEM_INT Function Module for NOTRANSL: Fortschreiben der internen Tabellen nach L_TO_PREPARE_ITEM_INT
L_TO_ADD_ITEM_INT is a standard l to add item int SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Fortschreiben der internen Tabellen nach L_TO_PREPARE_ITEM_INT 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 l to add item int FM, simply by entering the name L_TO_ADD_ITEM_INT into the relevant SAP transaction such as SE37 or SE38.
Function Group: L03A
Program Name: SAPLL03A
Main Program: SAPLL03A
Appliation area: L
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function L_TO_ADD_ITEM_INT 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 'L_TO_ADD_ITEM_INT'"NOTRANSL: Fortschreiben der internen Tabellen nach L_TO_PREPARE_ITEM_INT.
EXPORTING
* I_JCPOS = "Count Parameters
IMPORTING
E_LTAP_VB = "Transfer order item
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_SAPLL03A_001 Internal Putaway Strategy: Find Storage Bin
EXIT_SAPLL03A_002 Internal Putaway Strategy: Check Specified Storage Bin
EXIT_SAPLL03A_003 Internal Putaway Strategy: Update New Items in Internal Tables
EXIT_SAPLL03A_004 Internal Putaway Strategy: Update Internal Tables of Deleted Items
EXIT_SAPLL03A_005 Internal Stock Removal Strategy: Determine and Sort Stocks
EXIT_SAPLL03A_006 Internal Stock Removal Strategy: Check Default Bin
EXIT_SAPLL03A_007 Internal Stock Removal Strategy: Update Internal Tables of New Items
EXIT_SAPLL03A_008 Internal Stock Removal Strategy: Update Internal Tables of Deleted Items
EXIT_SAPLL03A_009 Overdelivery and if Necessary Underdelivery Via User Exit
EXIT_SAPLL03A_010 Exit: Calculation of Total Planned TO Processing Time
EXIT_SAPLL03A_011 Adjustment of Planned TO Item Processing Time for TO Confirmation
EXIT_SAPLL03A_012 Adjustment of Transfer Order Split for Transfer Order Creation
EXIT_SAPLL03A_013 User Exit for Picking: Strict FIFO
IMPORTING Parameters details for L_TO_ADD_ITEM_INT
I_JCPOS - Count Parameters
Data type: NUMC4Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for L_TO_ADD_ITEM_INT
E_LTAP_VB - Transfer order item
Data type: LTAP_VBOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for L_TO_ADD_ITEM_INT 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_i_jcpos | TYPE NUMC4, " | |||
lv_e_ltap_vb | TYPE LTAP_VB. " |
  CALL FUNCTION 'L_TO_ADD_ITEM_INT' "NOTRANSL: Fortschreiben der internen Tabellen nach L_TO_PREPARE_ITEM_INT |
EXPORTING | ||
I_JCPOS | = lv_i_jcpos | |
IMPORTING | ||
E_LTAP_VB | = lv_e_ltap_vb | |
. " L_TO_ADD_ITEM_INT |
ABAP code using 7.40 inline data declarations to call FM L_TO_ADD_ITEM_INT
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