Reading values in an object table

[Dart, Jocelyn]

Hi Mark, Yes technically you could do it this way BUT it's bad for long term
maintenance,
re-usability, integrity of the object-oriented design, etc., etc., etc.
 
Besides which, there is very little effort required to do things the "best
practices" way,
i.e. by creating a new attribute referring to a field on the same table.
 
All you have to do is cursor on the "Attributes" line, press create, pick
your field
from the dictionary and you will find it automatically refers to the
existing SELECT
statement to get the data!
 
By the way, this also works on your sub-object type if the SELECT statement
is in the
parent object type.
 
You only have to code new SELECT statements if you want to add a field from
a different,
not-yet-coded table.
 
And of course, if your workflows are getting down to this level, consider
sending an ABAP-er to
BC610 (Workflow programming).
Regards,
        Jocelyn Dart
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Bertrand, Scott
Sent: Tuesday, 25 July 2000 7:54 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Reading values in an object table
 
 
Mark
 
I believe that the data would be available, via reference 'OBJECT-_BKPF'.
It would be only available internally to the program, and it might look
strange to someone examining the object code at a later date.  I would weigh
the performance gains against ongoing maintenance and support.
 
Regards,
Scott Bertrand
SAP Newtown SQ,PA
 
-----Original Message-----
From: Mark Huffman [mailto:m.r.huffman at worldnet.att.net]
Sent: Monday, July 24, 2000 4:31 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Reading values in an object table
 
 
I am wondering what the effort involved is to grab a value from an
object table when the field is not defined as an Attribute.
 
There are lots of business objects defined with only a handful of
attributes, but the underlying table might have dozens of fields. Are
these fields generally available within the object program because of
the read that occurs near the beginning of the program or is the only
way to read them to define new attributes and then read the values with
a swc_get_property statement?
 
Specifically I am interested in reading additional values from BSEG.
 
Any comments? Don't tell me to write a new select statement because I am
trying to use the macros and tools within object programming.
 
Mark