[70] in sapr3-soft
Problem - ABAP/4 Batch programming difference rel 2.2 / 3.0D
daemon@ATHENA.MIT.EDU (Jim Hawthorne)
Sun Feb 23 08:37:16 1997
To: sapr3-soft@MIT.EDU
Date: 23 Feb 1997 08:11:40 -0500
From: Jim Hawthorne <jimh@jimboh.demon.co.uk> (by way of SAP Moderator <sap-request@realtimeusa.com>)
SAP is attempting to add features to ABAP which are found in newer
languages such as JAVA and Visual BASIC. Release
3.0E (which doesn't work properly yet !!!! has facilities for users
to
implement their own GUI (at last !!) and a mechanism known
as session manager which in theory should help people to set up
specific
menus etc. instead of having to wade through screens
of menus / transactions, a lot of which are unnecessary anyway - e.g
if
I am in Finance I don't even want to see most of the MM
menus.
In order to do this a lot of the screen handling programs have had to
be modified so that they retrieve their data and build the
screen dynamically. This screen could therefore be different at each
installation, or even in each client. While I am a great
believer in object oriented technology there is a price to pay for
this.
In rel 2.2 Batch programming (BDC) was relatively straight
forward. If you wanted to know where a field came from you merely
pressed F1 on the screen , and then pressed technical info
and you got the field e.g VBRK-LAND1. With release 3 you get often get
a
generic selection field such as STAZ1-SEL2 or
something equally indecipherable. This makes Batch programming rather
a
nightmare - especially when you add subscreens
etc. For example try and work out the screen and field sequences for
transaction MSC2 !!
Has anybody got a good way of "simulating" the rel 2.2 mechanism or is
this SAP's subtle way of suggesting that at some
future release (5, 6 or whatever) batch programming will no longer be
supported.
Any Ideas would be welcome.
Thanx in advance Jim
