ABAP OO Class Methods

IF_PT_REQ_REQUEST SAP Interface - Leave Request: Continuity







IF_PT_REQ_REQUEST is a standard SAP interface, see below for any documentation including details of methods, attributes, events etc. Interfaces are defined much the same as a class using the same transactions but act a bit like a template (in none OO terms). For example, a class would implement the interface and then inherit all of the methods etc from it. This provides a mechanism for unrelated objects to use a set of common behaviours and functionality.


You may have seen this already without knowing what it was, within SAP have you ever seen the method name prefixed by the name of an interface such as IF_PT_REQ_REQUEST~METHOD_NAME . This means that the class has implemented an interface and that this method has been inherited from it.


For further relevant information about this interface enter IF_PT_REQ_REQUEST into the relevant SAP transactions such as SE24, SE80. Also see the Resource section below to view other useful tips, screenshots, links and general information related to this SAP interface and its methods. Or even add your own for future reference



Methods of IF_PT_REQ_REQUEST





A method is a coding block that performs a certain procedure (i.e. ABAP functionality) on an object within the overall SAP class. In simple terms if the object is an SAP database table a method could be the procedure to add a record or to delete a record. If you are new to OO in many respects, the implementation of a method is similar to a function module and can be called in a very similar way using CALL METHOD.

Instead of "CALL FUNCTION", Methods are referenced using the following syntax: CALL METHOD CL_ABAP_CHAR_UTILITIES=>methodname EXPORTING/IMPORTING...



ADD_ITEM - Add Request Items
DELETE - Delete Request
GET_ALL_ATTRIBS - Get Request Attributes of Work Area Version
GET_ALL_ATTRIBS_FOR_ALL_VERS - Get Request Attributes of All Request Versions
GET_CURRENT_VERSION_NO - Determine Current Version of Request
GET_INITIATOR - Determine Initiator
GET_NEXT_PROCESSOR - Determine Next Agent
GET_NOTICE - Read Note for Request
GET_OWNER - Determine Owner
GET_RESPONSIBLE - Determine Person Responsible
GET_STATUS - Determine status
GET_WORKAREA_VERSION - Read Work Version
INITIATE_STATE_TRANSITION - Initiate Status Transition
SET_ALL_ATTRIBS - Set Request Attributes
SET_INITIATOR - Set Initiator
SET_NEXT_PROCESSOR - Set Next Agent
SET_NOTICE - Write Note for Request
SET_OWNER - Set Owner
SET_RESPONSIBLE - Set Person Responsible
SET_STATUS - Set Status
SET_VERSION - Set Version of Request
SET_WORKAREA_VERSION - Set Work Version
START_TRANSACTION - Start Transaction
VALIDATE_AND_SIMULATE - Check and Simulate Request
WITHDRAW - Withdraw request


IF_PT_REQ_REQUEST Attributes

List of attributes within class IF_PT_REQ_REQUEST. These can be referenced using the following syntax IF_PT_REQ_REQUEST=>. Although depending on where you are inserting the ABAP code you do need to check if the attribute is public or private.


NameDescriptionInitial Value
FIRST_SUBM_DATE Field of type DATS
FIRST_SUBM_TIME Time in CHAR format
LIST_OF_VERSIONS Table of Request Items
REQUEST_ID Request ID
WORKAREA_VERSION For All Request Headers




Events of the Class IF_PT_REQ_REQUEST

Events are created within your class using special event handler methods. These must be registered at runtime for the event and can then be triggered using the ABAP syntax: RAISE EVENT EXPOTING...