AW: Attributes as object types

[Becker Stephan (extern)]

This is an interesting feature of workflow, and as far as I know is not
documented anywhere:
 
If you define the reference as type object (CHECK the object type =
reference
radio button and insert the name of the object type) AND enter a =
database
field that MUST BE completely defined by the key of the object you are
creation the attribute for, then the system can determine the object
attribute completely if you let it insert the code for the attribute.
 
If the key of the attribute object CANNOT be uniquely determined by the =
key
of the main object, then you need to implement the attribute yourself. =
If
you let the system automatically create the code for the implementation =
in
such a case, you will see '???????' parts in the select statements that =
are
not in the key.
 
Stephan
 
-----Urspr=FCngliche Nachricht-----
Von: Roehlen, Peter [mailto:PRoehlen at powercor.com.au]
Gesendet: Freitag, 8. M=E4rz 2002 08:44
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Attributes as object types
 
 
Hello workflowers,
 
I'm seeking some guidance from anyone who has come across the following
problem:
 
When we add a new attribute to a business object type, we usually try =
to
make the 'type reference' of the attribute itself an 'object type'.  An
object type as the type reference is typically a lot more useful to =
workflow
designers than just the field value; doing this can often meet the =
needs of
future workflow templates as well.  For example: if someone asks me to =
add
the 'Superior Functional Location' as an attribute to business type
ZBUS0010, "Functional Location", I would automatically make the new
attribute reference an object type (in this case it would also be =
ZBUS0010)
rather than just reference the ABAP dictionary field.
 
The ease with which a regular attribute can be made to reference an =
object
type is a tribute to the SAP designers, however when we do this there =
is
often one problem that continually crops up: If the field value for the
attribute is initial - ie with no value - then the object reference is
'nothing'.  This causes workflow templates to terminate if you use the
attribute in a Condition step.  If, however, the attribute references =
the
ABAP dictionary field then the initial value causes no problem.
 
One work around is to have two attributes for each field, one =
referencing
the appropriate object type and the other the ABAP dictionary field.  =
This
is pretty ugly though.
 
Has anyone got any thoughts on the above?
 
Peter Roehlen
Team Lead - SAP Technical & Development
Powercor Australia Ltd
0409 950 263
 
 
 
 
**********************************************************************
Powercor Australia Ltd. This email and any file attachments are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email in
error please tell us immediately by return email and delete the
document.
**********************************************************************