Using workflow container as object key

[Mike Pokraka]

Hmmm, answering all my own questions today, but I figured why not post
them...

Firstly, I realize my first statement was complete nonsense, of course one
can instantiate a BOR object without a DB table key. What I meant was that
it can't be done for objects *based on a table* but for DB entries that do
not yet exist. The real problem I was trying to solve is populate such an
object's attribute before writing it to the DB, e.g. fill items with info
that isn't on the document.

Using classes, it is possible. Better still, it looks like the in-memory
bit works. So I can create item classes that go off into their own
parallel subflows without having nasty multiline container constructions
in the main flow. Keeps things tidy :-)

Cheers
Mike

Mike Pokraka wrote:
> Greetings workflowers,
>
> I've got a requirement where I would normally have to create a table and
a
> custom object type.
> However... I'm thinking that classes free one from the shackles of
needing
> an underlying table, since the constructor could theoretically just as
well read it's key from a call to SAP_WAPI_READ_CONTAINER instead of a
SELECT statement. Has anyone done this? Good or bad?
>
> Taking the idea to the next level, I'm wondering if it's not possible to
skip a stored key alltogether. Since classes store instance data in
memory
> independent of the DB, I could call a method (of a different class)
which
> returns an instance of a class with all the info I need. This would then
be used in the following step to call a subflow with the instance data
becoming import parameters. My question: does WF convert this to Local
Persistent Object References in between successive steps? (Thus it would
destroy my instance data). More importantly, I'm looking at doing this
on
> a 620 system. If it works, will it still work on 640?
>
> Any thoughts appreciated,
> Cheers
> Mike
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>