ABAP OO Class Methods

FITV_VERSIONING_INTERFACE SAP Interface - Interface to BAdI: FITV_VERSIONING_BADI_DEF







FITV_VERSIONING_INTERFACE 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 FITV_VERSIONING_INTERFACE~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 FITV_VERSIONING_INTERFACE 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 FITV_VERSIONING_INTERFACE





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...



TRIGGER_VERSIONING - Adjustment of Archiving Rule for Travel Forms


FITV_VERSIONING_INTERFACE Attributes

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


NameDescriptionInitial Value
CON_CREATE_ARCHIV Archive Document '2'
CON_NO_ARCHIV Do Not Archive Document '1'




Events of the Class FITV_VERSIONING_INTERFACE

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...