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
Tag Archives: ABAP
ABAP – Multiple implementations of a “Single implementation only BAdI”
It is a problem when you need to have multiple implementations of a BAdI which does not implicitly allow multiple implementations by its definition. How to bypass this limitation? Continue reading
ABAP – APO Planning book macros on aggregated levels
Here I’d like to present my solution of a problem in APO planning books where it was necessary to load multiple products and locations at the same time into the planning view and execute some Default macros on all of them. Continue reading
ABAP – How to declare a variable dynamically
In case you need to create a variable dynamically during runtime with different type, length or precision, you can use the following piece of code to achieve the same – the variable is created dynamically based on given type, length and number of decimals. Continue reading
ABAP – Export Transport request to local file system
All development or customizing in SAP is written into a transport request unless it is a local object not intended to be transported ($TMP package). Sometimes it might be useful to backup your development but in SAP this task is quite complicated to export all programs, classes, standard texts, …
Therefore there is an option to export the whole development encapsulated on a transport request level. And that’s what this article is about – exporting development encapsulated in a transport request to local file system. Continue reading
ABAP – Validation of manual input
I faced a scenario where I had an ALV grid where all columns were made generic of type (let’s make it simple) CHAR255. Each column has its name in field catalog in format TABNAME-FIELDNAME (+ more human readable column header texts of course). What I needed to achieve was to make validation of data that user entered in the ALV cells. Since the cell validation is not available by default (because of type CHAR255) I had to make it dynamically.
In this article I’d like to share my solution Continue reading
ABAP – create dynamic variable knowing reference tabname and fieldname
If you want to create a variable during runtime knowing only the reference table name and its field name (in string form), you can achieve it following the code presented in this article Continue reading
ALV tutorial 11 – Edit & Save changes
In this tutorial I’ll show how to enable only the specific cells of a grid to be editable. Continue reading
Dynpro – How to disable functions instead of hiding them in a screen
If you need to manipulate with a screen dynamically, sometimes you need to enable/disable some functions/buttons in the toolbar. Standard exclusion of function when setting PF-STATUS will by default hide the excluded functions. But what if you want to display them, but just in disabled state ? Continue reading
ALV – Dynpro controlled by a global class
In this article I’ll present an approach how to handle a screen with a global ABAP class. The idea is simple – we will create a class which will listen to PAI and PBO events raised by the screen. All data processing and screen element manipulation is done in the class code. Let’s check out how exactly it is done Continue reading