LC bapi limit

Also evil: when using LC BAPIs, for example BAPI_MOSRVAPS_GETLIST, one has to pay attention not to call the function with too many parameters in the selection tables. And what is that limit? Maybe

gc_apo_bapi_max_range_entries  type sy-index value '150'

from APO_BAPI_CONSTANTS.

For all entries is evil

It was not the first time that I was bitten by this. One time should have been enough to learn, but using for all entries in select queries really requires extra care. If you write

select *
from afpo
into table lt_afpo
for all entries in lt_aufnr
where aufnr = lt_aufnr-aufnr.

be sure to guarantee that lt_aufnr will never be empty, or else, you end up with an internal table with all data from the database table. Arggh.

Code Inspector

I read this post about the code inspector tool. It made me curious enough to request the install (OSS note 543359). It is a static code analyser, probably a better checker than transaction SLIN.

About the SAP community forum

If you happen to read the forums at SAP community you may have noticed the large number of reply posts having only thank you, that was very helpful, great post, etc. Are people unusually polite there? Or are they trying to collect points to receive the bottle fastener.

Development Quick Links

From sapfans, a link to an ABAP function list . And another list. Some notes on using HTTP_POST function.

User*exit hacking

Here is a very useful trick to access and change variables outside the scope of an user-exit function. For example, in exit EXIT_SAPMM07M_001 you can set the text in the material document, but no other MSEG field is supposed to be changed. Using field symbols you can access and change any field from the outer scope (this example sets the external post amount to 99).

CONSTANTS: c_mseg(21)  VALUE '(SAPMM07M)MSEG'.

FIELD-SYMBOLS: <fc> TYPE MSEG.

ASSIGN (c_mseg) TO <fc>.
<fc>-exbwr = 99.

But, of course, doing this is higly unrecommended. If they find you doing it, the'll send an agent to deactivate your ... *disconnected*