SAP LASP_EVALUATION Function Module for LASP: Evaluierung eines taktgenauen Plans









LASP_EVALUATION is a standard lasp evaluation 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: Evaluierung eines taktgenauen Plans 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 evaluation FM, simply by entering the name LASP_EVALUATION 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_EVALUATION 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_EVALUATION'"LASP: Evaluierung eines taktgenauen Plans
EXPORTING
OBJID_IV = "Identifikations-Nr. des Linienabschnitts
* VIEW_IV = 'I' "Flag für ankommende oder weggehende Sicht
* PER_PAT_CHANGED_IV = "Flag für Änderung des Periodenrasters
* INCL_NDISP_ORDER_IV = "Include non-dispatched planned orders

IMPORTING
DT_ET = "Einzel-Auslastungen
DS_ET = "Gesamt-Auslastungen

CHANGING
* PER_PAT = "Periodenraster

EXCEPTIONS
NOT_SELECTED = 1 WORKSTATION_NOT_FOUND = 2
.




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_EVALUATION

OBJID_IV - Identifikations-Nr. des Linienabschnitts

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

VIEW_IV - Flag für ankommende oder weggehende Sicht

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

PER_PAT_CHANGED_IV - Flag für Änderung des Periodenrasters

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

INCL_NDISP_ORDER_IV - Include non-dispatched planned orders

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

EXPORTING Parameters details for LASP_EVALUATION

DT_ET - Einzel-Auslastungen

Data type: LASP_DT_TA
Optional: No
Call by Reference: Yes

DS_ET - Gesamt-Auslastungen

Data type: LASP_DS_TA
Optional: No
Call by Reference: Yes

CHANGING Parameters details for LASP_EVALUATION

PER_PAT - Periodenraster

Data type: PERIOD_PATTERN
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NOT_SELECTED - Es wurde nicht initialisiert

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

WORKSTATION_NOT_FOUND - Arbeitsplatz wurde nicht gefunden

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

Copy and paste ABAP code example for LASP_EVALUATION 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_dt_et  TYPE LASP_DT_TA, "   
lv_per_pat  TYPE PERIOD_PATTERN, "   
lv_objid_iv  TYPE CRHD-OBJID, "   
lv_not_selected  TYPE CRHD, "   
lv_ds_et  TYPE LASP_DS_TA, "   
lv_view_iv  TYPE C, "   'I'
lv_workstation_not_found  TYPE C, "   
lv_per_pat_changed_iv  TYPE C, "   
lv_incl_ndisp_order_iv  TYPE C. "   

  CALL FUNCTION 'LASP_EVALUATION'  "LASP: Evaluierung eines taktgenauen Plans
    EXPORTING
         OBJID_IV = lv_objid_iv
         VIEW_IV = lv_view_iv
         PER_PAT_CHANGED_IV = lv_per_pat_changed_iv
         INCL_NDISP_ORDER_IV = lv_incl_ndisp_order_iv
    IMPORTING
         DT_ET = lv_dt_et
         DS_ET = lv_ds_et
    CHANGING
         PER_PAT = lv_per_pat
    EXCEPTIONS
        NOT_SELECTED = 1
        WORKSTATION_NOT_FOUND = 2
. " LASP_EVALUATION




ABAP code using 7.40 inline data declarations to call FM LASP_EVALUATION

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 OBJID FROM CRHD INTO @DATA(ld_objid_iv).
 
 
 
DATA(ld_view_iv) = 'I'.
 
 
 
 


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!