How about a WIKI section called "SAP Internals Cross-Reference" ????

[former_member181923]

For details on what I mean, please see my reply to Bharathwaj here:<br><br>

<a href="/people/david.halitsky/blog/2007/03/16/workflow-delegation-badi-selection-and-wdj-polymorphism-its-deja-vu-all-over-again </a>

[marilyn_pratt]

The beauty of the Wiki is that you can indeed add a page if you think some content is missing. I'm not sure if your title really communicates your meaning, but if you want to diagram relatedness of modules and functions you are welcome to do so. If you have a good feel for where you think this page should live, go ahead and create it. If it is a new space you are looking to create, a good justification for one should be articulated and when there is some agreement around that, it can be created.

[former_member181923]

HI MP -

I'd be happy to title the page with anything that anyone thinks is a good title.

To give an example of what I mean by "internals cross-reference", I want to do a Wiki entry which correlates and explains any differences between the actual pieces of code that allow programmers to transfer data back and forth between:

1) "EnjoySAP" screen controls and program-accessible memory;

2) ABAP OO controls (e.g. ALVs, trees) and program-accessible memory;

3) WDA controllers and UI's;

4) WDJ controllers and UI's

5) WF tasks/steps and containers

If you can come up with a better descriptive title for this entry that "internals cross-reference", I'd be happy to use it.

regards

djh

[marilyn_pratt]

Still not clear if these means generally "different techniques" "comparison approach". Maybe the word "internals" is throwing me.

Coding alternatives, approaches...sorry, if I'm dense, but I don't see an emerging theme.

[former_member181923]

Hi Marilyn -

I don't want to start a Wiki page whose purpose is not immediately clear from its title.

So how about:

"Holistic SAP: Interrelationships among SAP Coding Constructs"

The idea here is that much of what goes on at SDN is sharing of information on certain specific SAP coding constructs, without any reference to how these constructs are related to other SAP coding constructs that folks may have previously encountered in other SAP coding contexts.

In a "holistic" view of SAP, on the other hand, the emphasis is on how specific SAP coding constructs are actually closely related to other SAP coding constructs that seem, at first glance, to be very different.

Regards

djh

[marilyn_pratt]

Thanks for your tenacity and patience in explaining to me. It's beginning to make more sense. Now, how to create some logical structure by which to group these. You made some suggestions above, but I'm not sure I would understand why one would be looking from one or the other without a bit of context.

Does it make sense to put these into some scenario framework (when you need to do "x" you can accomplish this by "a", "b", "c".)

Are you thinking of this as a separate space? Is this a subset of the coding gallery already created?

[former_member181923]

Hi Marilyn -

Glad we're converging ...

The kind of stuff I have in mind wouldn't really belong to the coding gallery because the point is not to show a "neat" example of coding construct X.

Rather, it is to exhibit "trivial" examples of coding construct X, Y, and Z in order to show how X, Y, and Z are really "doing the same thing" (from a technical point of view, not a functional point of view.)

So regarding "placement", maybe the best idea is for me to wait till I get my "Profile" invite and then put a couple of actual entires out there.

That way, you (and SDN mgmt) can decide whether the stuff warrants its own space in the SDN Wiki (where anyone can contribute), or whether it should just stay in my own profile area.

regards

djh