In this article I’ll show how to implement local exception class which will use all the benefits of interface IF_T100_MESSAGE – it will simply use the message classes for generating exception messages. Continue reading
If you want to restrict creation of transports (and their release to further systems) based on rules applied on a transport description, you can use method described in this example. Continue reading
This is just a note that you should be aware of using different kind of space character.
The classical space – you can type it by pressing spacebar – has unicode number U+0020.
The NO-BREAK space character is different – you can type it by pressing ALT+255 – this character will look the same like normal space but in unicode it will have number U+00A0. Continue reading
This is a demo webdynpro application to show you a list of all available colors you can use in your WebDynpros.
Adapter design pattern provides unique INTERFACE to the outside world for different functionality encapsulated in separate implementations. Continue reading
I experienced lot of confusion when I faced internal tables with header lines during my professional life. Therefore I strongly advice NOT to use internal tables with header lines. But they are heavily used in older programs so it’s good to know what is the difference between how to clear the header line and how to clear the itab contents and how it is different from internal tables WITHOUT header line. Continue reading
This article is a tutorial on how to create a View Cluster on top of SAP tables. It is extremly useful when you have several SAP tables with hierarchical dependency. This hierarchy is nicely visible on eg. MARA -> MARC -> MARD tables where the KEY grows from MATNR (MARA table) to MATNR + WERKS (MARC) to MATNR + WERKS + LGORT (MARD). To view/edit data using this hierarchy folding you can use the “View clusters” approach.
Factory Method design pattern provides unique interface to object instantiation. The decision on which object is to be instantiated is hidden from the outside world in the code. Using this approach different objects can be instantiated dynamically. Continue reading
In software engineering, the singleton pattern is a design pattern that restricts the instantiation of a class to one object. This is useful when exactly one object is needed to coordinate actions across the system. The concept is sometimes generalized to systems that operate more efficiently when only one object exists, or that restrict the instantiation to a certain number of objects. The term comes from the mathematical concept of a singleton. Continue reading
APO system offers only 5 product specific and another 5 product-location specific, version dependent fields called AT101 – AT105 and ATT01 – ATT05. But what if you need MORE than these 10 extra fields to be version dependent? You can generate more extra fields using the EEWB (Easy Enhancement Workbench) but this tool generates the extra fields as version independent (all planning versions will share the same values).
In this article I’ll show how to make these extra fields made by EEWB version dependent. Continue reading