SAP LASP_INITIALIZE Function Module for LASP: Initialisierung für eine taktzeitgenaue Einplanung von Aufträgen
LASP_INITIALIZE is a standard lasp initialize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for LASP: Initialisierung für eine taktzeitgenaue Einplanung von Aufträgen 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 lasp initialize FM, simply by entering the name LASP_INITIALIZE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SP01
Program Name: SAPLSP01
Main Program: SAPLSP01
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LASP_INITIALIZE 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 'LASP_INITIALIZE'"LASP: Initialisierung für eine taktzeitgenaue Einplanung von Aufträgen.
EXPORTING
T001W_IS = "Werk
HORIZON_IS = "Betrachtungshorizont
* MODE_IV = 'X' "Änderungs-Anzeigekennzeichen
* TSPP0_IS = "Planungsprofil
* TSPP1_IS = "Verfahrensprofil
* MAX_DISST_IV = 0 "Maximale Dispositionsstufe
* MANUELL_DISPATCH_IV = ' ' "automatisch manuell Einplanen
* HEIJUNKA_MODE_IV = ' ' "Heijunka modus
* NO_PLAF_UPLOAD_IV = ' ' "No Planned Order Upload
TABLES
* LDLHD_IT = "Linie
* MT61D_IT = "Dispositionsrelevanter Teil des Materiallstammes
* MKAL_IT = "Fertigungsversion
* PLAF_IT = "Planaufträge
* LDLPD_ET = "Linienabschnitte
EXCEPTIONS
INVALID_DATA_COMBINATION = 1 PRODUCTIONVERSION_NOT_EXIST = 10 TIME_CALCULATION_ERROR = 11 INVALID_HORIZON = 2 PLANT_NOT_EXIST = 3 PLANNING_PROFILE_NOT_EXIST = 4 ALGORITHM_PROFILE_NOT_EXIST = 5 LINE_NOT_EXIST = 6 WORKSTATION_NOT_EXIST = 7 LINEZONE_NOT_EXIST = 8 INVALID_WORKINGTIMEAXIS = 9
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_SAPLSP01_001 Creates a Desired Sequence and Date Records
IMPORTING Parameters details for LASP_INITIALIZE
T001W_IS - Werk
Data type: T001WOptional: No
Call by Reference: No ( called with pass by value option)
HORIZON_IS - Betrachtungshorizont
Data type: LASP_INTERVAL_STOptional: No
Call by Reference: No ( called with pass by value option)
MODE_IV - Änderungs-Anzeigekennzeichen
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TSPP0_IS - Planungsprofil
Data type: TSPP0Optional: Yes
Call by Reference: No ( called with pass by value option)
TSPP1_IS - Verfahrensprofil
Data type: TSPP1Optional: Yes
Call by Reference: No ( called with pass by value option)
MAX_DISST_IV - Maximale Dispositionsstufe
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
MANUELL_DISPATCH_IV - automatisch manuell Einplanen
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
HEIJUNKA_MODE_IV - Heijunka modus
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_PLAF_UPLOAD_IV - No Planned Order Upload
Data type: BOOLEANDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LASP_INITIALIZE
LDLHD_IT - Linie
Data type: LDLHDOptional: Yes
Call by Reference: No ( called with pass by value option)
MT61D_IT - Dispositionsrelevanter Teil des Materiallstammes
Data type: MT61DOptional: Yes
Call by Reference: No ( called with pass by value option)
MKAL_IT - Fertigungsversion
Data type: MKALOptional: Yes
Call by Reference: No ( called with pass by value option)
PLAF_IT - Planaufträge
Data type: PLAFOptional: Yes
Call by Reference: No ( called with pass by value option)
LDLPD_ET - Linienabschnitte
Data type: LDLPDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_DATA_COMBINATION - Ungültige Datenkombination
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PRODUCTIONVERSION_NOT_EXIST - Fertigungsversion existiert nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TIME_CALCULATION_ERROR - Terminierungsfehler
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_HORIZON - Ungültiger Betrachtungshorizont
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PLANT_NOT_EXIST - Werk existiert nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PLANNING_PROFILE_NOT_EXIST - Planungsprofil existiert nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ALGORITHM_PROFILE_NOT_EXIST - Verfahrensprofil existiert nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LINE_NOT_EXIST - Linie existiert nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WORKSTATION_NOT_EXIST - Arbeitsplatz existiert nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LINEZONE_NOT_EXIST - Linienpositionen existieren nicht
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_WORKINGTIMEAXIS - Arbeitszeitdefinition ist ungültig
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LASP_INITIALIZE 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_ldlhd_it | TYPE STANDARD TABLE OF LDLHD, " | |||
| lv_t001w_is | TYPE T001W, " | |||
| lv_invalid_data_combination | TYPE T001W, " | |||
| lv_productionversion_not_exist | TYPE T001W, " | |||
| lv_time_calculation_error | TYPE T001W, " | |||
| lt_mt61d_it | TYPE STANDARD TABLE OF MT61D, " | |||
| lv_horizon_is | TYPE LASP_INTERVAL_ST, " | |||
| lv_invalid_horizon | TYPE LASP_INTERVAL_ST, " | |||
| lt_mkal_it | TYPE STANDARD TABLE OF MKAL, " | |||
| lv_mode_iv | TYPE C, " 'X' | |||
| lv_plant_not_exist | TYPE C, " | |||
| lt_plaf_it | TYPE STANDARD TABLE OF PLAF, " | |||
| lv_tspp0_is | TYPE TSPP0, " | |||
| lv_planning_profile_not_exist | TYPE TSPP0, " | |||
| lt_ldlpd_et | TYPE STANDARD TABLE OF LDLPD, " | |||
| lv_tspp1_is | TYPE TSPP1, " | |||
| lv_algorithm_profile_not_exist | TYPE TSPP1, " | |||
| lv_max_disst_iv | TYPE I, " 0 | |||
| lv_line_not_exist | TYPE I, " | |||
| lv_manuell_dispatch_iv | TYPE C, " SPACE | |||
| lv_workstation_not_exist | TYPE C, " | |||
| lv_heijunka_mode_iv | TYPE C, " SPACE | |||
| lv_linezone_not_exist | TYPE C, " | |||
| lv_no_plaf_upload_iv | TYPE BOOLEAN, " SPACE | |||
| lv_invalid_workingtimeaxis | TYPE BOOLEAN. " |
|   CALL FUNCTION 'LASP_INITIALIZE' "LASP: Initialisierung für eine taktzeitgenaue Einplanung von Aufträgen |
| EXPORTING | ||
| T001W_IS | = lv_t001w_is | |
| HORIZON_IS | = lv_horizon_is | |
| MODE_IV | = lv_mode_iv | |
| TSPP0_IS | = lv_tspp0_is | |
| TSPP1_IS | = lv_tspp1_is | |
| MAX_DISST_IV | = lv_max_disst_iv | |
| MANUELL_DISPATCH_IV | = lv_manuell_dispatch_iv | |
| HEIJUNKA_MODE_IV | = lv_heijunka_mode_iv | |
| NO_PLAF_UPLOAD_IV | = lv_no_plaf_upload_iv | |
| TABLES | ||
| LDLHD_IT | = lt_ldlhd_it | |
| MT61D_IT | = lt_mt61d_it | |
| MKAL_IT | = lt_mkal_it | |
| PLAF_IT | = lt_plaf_it | |
| LDLPD_ET | = lt_ldlpd_et | |
| EXCEPTIONS | ||
| INVALID_DATA_COMBINATION = 1 | ||
| PRODUCTIONVERSION_NOT_EXIST = 10 | ||
| TIME_CALCULATION_ERROR = 11 | ||
| INVALID_HORIZON = 2 | ||
| PLANT_NOT_EXIST = 3 | ||
| PLANNING_PROFILE_NOT_EXIST = 4 | ||
| ALGORITHM_PROFILE_NOT_EXIST = 5 | ||
| LINE_NOT_EXIST = 6 | ||
| WORKSTATION_NOT_EXIST = 7 | ||
| LINEZONE_NOT_EXIST = 8 | ||
| INVALID_WORKINGTIMEAXIS = 9 | ||
| . " LASP_INITIALIZE | ||
ABAP code using 7.40 inline data declarations to call FM LASP_INITIALIZE
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.| DATA(ld_mode_iv) | = 'X'. | |||
| DATA(ld_manuell_dispatch_iv) | = ' '. | |||
| DATA(ld_heijunka_mode_iv) | = ' '. | |||
| DATA(ld_no_plaf_upload_iv) | = ' '. | |||
Search for further information about these or an SAP related objects