SAP EXIT_SAPLIWP3_010 Function Module for Determine Due Packages for Performance-Based Strategy Plans

Search SAP Function Modules

EXIT_SAPLIWP3_010 is a standard exit sapliwp3 010 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Due Packages for Performance-Based Strategy 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 exit sapliwp3 010 FM, simply by entering the name EXIT_SAPLIWP3_010 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLIWP3_010 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 'EXIT_SAPLIWP3_010'"Determine Due Packages for Performance-Based Strategy Plans
  EXPORTING
   SAP_MPLA_IMP =  "Maintenance Plan
   SAP_MMPT_IMP =  "
   SAP_OFFZE_IMP =  "Offset in Current Cycle

 IMPORTING
   SAP_OFFZE_EXP =  "Offset in Current Cycle
   SAP_CALLS_ON_HOLD =  "X = Deletion of Waiting Calls Immediately Available in IP30
   SAP_UPDATE =  "X = Offset Change Occurred

TABLES
   SAP_MHIS_IMP =  "Scheduling Records
   SAP_VER_PAK_IMP =  "Maintenance Packages

EXCEPTIONS
   NO_UPDATE = 1 

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
CONVERSION_EXIT_EAMQF_INPUT NOTRANSL: Konvertierungs-Exit TPLNR, extern -> intern
CONVERSION_EXIT_EAMQF_OUTPUT NOTRANSL: Konvertierungs-Exit TPLNR, intern -> extern
IWP3_CALL_CUSTOMER_EXTENSION NOTRANSL: Call customer exit und BADI
IWP3_CALL_SCHEDULING_LIST NOTRANSL: Terminübersicht in Listform
IWP3_CCMPLAN_CHECK_MPLAN_ATTR Check if maintenance plan attributes are adequate
IWP3_CCMPLAN_COPY_HEADER Copy header of a maintenance plan
IWP3_CCMPLAN_COPY_MAINT_ITEMS Copy maintenance items of a maintenance plan
IWP3_CCMPLAN_COPY_MAINT_PLAN Copy the given maintenance plan
IWP3_CCMPLAN_COPY_SCHED_PARAMS Copy scheduling parameters of a maintenance plan
IWP3_CCMPLAN_GET_DEFAULTS Get Maintenance Plan default values from TPMUS table
IWP3_CCMPLAN_GET_REF_DATA Get the referenced maintenance plan data
IWP3_CCMPLAN_OPEN_COPY_POPUP Open popup for copying maintenance plan from reference
IWP3_CCMPLAN_SHLP_EXIT Search Help Exit for Reference Maintenance Plan
IWP3_FILL_ENVIRONMENT_DISPLAY NOTRANSL: Versorgen der Variablen für die Umfeldanzeige
IWP3_FILL_GLOBAL_DATA NOTRANSL: Fuellen globale Daten
IWP3_GET_FCODE NOTRANSL: Get IWP3 f_code
IWP3_GET_IND_CONFIRMATION_DATE NOTRANSL: Liefert Indikator 'Rückmeldedatum' je Wartungsplantyp
IWP3_GET_LOOP_EXIT Get maximum number of calls with same date
IWP3_GET_TERMTEXTE NOTRANSL: Texte der Abrufart Terminierung
IWP3_MCP_GET_IND_ENHANCEMENT NOTRANSL: Flag für Erweiterung Mehrfachzählerplan prüfen
IWP3_MCP_SET_IND_MCP_SF NOTRANSL: Setzen des Indicators MCP_SF für Mehrfachzählerplan
IWP3_MPLAN_CHECK_CHANGED NOTRANSL: Prüfen ob Wartungsplan geändert wurde
IWP3_MPLAN_ENHANCEMENT_POINT NOTRANSL: Aufruf eines Enhancement Point für MPLAN_CHECKS
IWP3_READ_T399W NOTRANSL: Lesen/Puffern der Tabelle T399W (Wartungsplantyp Parameter)
IWP3_SCHEDULE_CALCULATION NOTRANSL: Kostensimulation für Wartungspläne
IWP3_SCROLL_OBJECT_LIST NOTRANSL: Übernahme sichtbarer Zeilen in Tabelcontrol der Objektliste
IWP3_SHOW_VALID_PACKAGES NOTRANSL: Display valid packages for selection
IWP3_STICHTAGS_CHECK NOTRANSL: Holen globale Daten
IWP3_WRITE_CHANGEDOC_MHIO NOTRANSL: Änderungsbelege Wartungsplanabrufe
IWP3_WRITE_CHANGEDOC_MHIS NOTRANSL: Änderungsbelege Wartungsplanabrufe/-historie
IWP3_WRITE_CHANGEDOC_MITEM NOTRANSL: Änderungsbelege Wartungspositionen
IWP3_WRITE_CHANGEDOC_MPLAN NOTRANSL: Änderungsbelege Wartungspläne

IMPORTING Parameters details for EXIT_SAPLIWP3_010

SAP_MPLA_IMP - Maintenance Plan

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

SAP_MMPT_IMP -

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

SAP_OFFZE_IMP - Offset in Current Cycle

Data type: MHIS-OFFZE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for EXIT_SAPLIWP3_010

SAP_OFFZE_EXP - Offset in Current Cycle

Data type: MHIS-OFFZE
Optional: No
Call by Reference: Yes

SAP_CALLS_ON_HOLD - X = Deletion of Waiting Calls Immediately Available in IP30

Data type: MPLA-AEKNZ
Optional: No
Call by Reference: Yes

SAP_UPDATE - X = Offset Change Occurred

Data type: MPLA-AEKNZ
Optional: No
Call by Reference: Yes

TABLES Parameters details for EXIT_SAPLIWP3_010

SAP_MHIS_IMP - Scheduling Records

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

SAP_VER_PAK_IMP - Maintenance Packages

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

EXCEPTIONS details

NO_UPDATE - No Change

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EXIT_SAPLIWP3_010 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.

ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLIWP3_010

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