SAP S95_MAINT_WORK_ORDER_TRIGGER Function Module for Trigger S95 MaintenanceWorkOrder message after saving PM Order

Search SAP Function Modules

S95_MAINT_WORK_ORDER_TRIGGER is a standard s95 maint work order trigger SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Trigger S95 MaintenanceWorkOrder message after saving PM Order 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 s95 maint work order trigger FM, simply by entering the name S95_MAINT_WORK_ORDER_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

Function Group: S95_ERP_ENHANCEMENTS
Program Name: SAPLS95_ERP_ENHANCEMENTS
Main Program: SAPLS95_ERP_ENHANCEMENTS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function S95_MAINT_WORK_ORDER_TRIGGER 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 'S95_MAINT_WORK_ORDER_TRIGGER'"Trigger S95 MaintenanceWorkOrder message after saving PM Order
  EXPORTING
   EVENT =  "Name of Event
   RECTYPE =  "Type of Event Receiver, Here: Task ID
   OBJTYPE =  "Type of Triggering Object
   OBJKEY =  "Key of Triggering Object
*  EXCEPTIONS_ALLOWED = ' ' "Indicator Showing Whether FM Can Raise Exceptions

 IMPORTING
   REC_ID =  "Key of Receiving Object

TABLES
   EVENT_CONTAINER =  "Event Container

EXCEPTIONS
   READ_FAILED = 1    CREATE_FAILED = 2 

.

IMPORTING Parameters details for S95_MAINT_WORK_ORDER_TRIGGER

EVENT - Name of Event

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

RECTYPE - Type of Event Receiver, Here: Task ID

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

OBJTYPE - Type of Triggering Object

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

OBJKEY - Key of Triggering Object

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

EXCEPTIONS_ALLOWED - Indicator Showing Whether FM Can Raise Exceptions

Data type: SWEFLAGS-EXC_OK
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for S95_MAINT_WORK_ORDER_TRIGGER

REC_ID - Key of Receiving Object

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

TABLES Parameters details for S95_MAINT_WORK_ORDER_TRIGGER

EVENT_CONTAINER - Event Container

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

EXCEPTIONS details

READ_FAILED - Read Definition for Task Failed

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

CREATE_FAILED - Create Work Item Failed

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

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

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