|Home • Trainings •Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
ABAP Classes in Workflow
Local Conventions within Methods:
Using ABAP Classes in Workflow:
Within the SAP
WebFlow Engine we can use ABAP classes that support the IF_WORKFLOW
interface. Classes that have implemented the IF_WORKFLOW
interface are recognized as workflow-enabled in the Class Builder.
How to create ABAP Classes that support IF_WORKFLOW interface?
The key attributes are used to
define the object key. There can also be other defined attributes other than key
attributes. The SAP WebFlow Engine can access all public attributes of a class.
In the Class Builder there is an
additional column Key
Attributes on the
page as shown below:
need to check this box when we are
defining any attribute as the Key Attribute.
All key fields must be character-type fields (elementary types: CHAR, NUMC) and have a defined length. The maximum length allowed for all key fields is 32 characters. The length of the key field for the persistent display is 32 characters.
In the case of persistent ABAP objects we can use the GUID, which is generated automatically by the object manager when an instance is created.
In addition to all the other data types that the Class Builder supports, we can also define attributes with reference to an object from the Business Object Repository (BOR). To do this, we have to use the structure SWOTOBJID as the data type. The BOR object is determined using the corresponding value.
To assign a BOR object instance to an attribute we need to use the corresponding BOR macros. Normally, this is implemented within the CONSTRUCTOR of a class.
To use the BOR macros in a class, two INCLUDES
must be included.
Ø Include <CNTN03>……………contains the local types
the BOR macros
An example to show how to define Attributes and Key Attributes:
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards