Characteristic's own input screen - Part 6 - move reference data to bapi structures
  ZCL_ABAPBLOG_COM_CLASSIFIC.nugg |
Our characteristics update screen was displayed, data was changes so we need to read the reference data and put the values into BAPI structures in order to be able to save the values to database.
I will use here BAPI_CLASS_READ to read all possible characteristics and COC1_FEATURE_CHECK to get characteristic details.
Importing:
I_DATA TYPE REF TO DATA
Changing:
CT_OBJVALUESNUM TYPE TT_BAPI1003_ALLOC_VALUES_NUM
CT_OBJVALUESCHAR TYPE TT_BAPI1003_ALLOC_VALUES_CHAR
CT_OBJVALUESCURR TYPE TT_BAPI1003_ALLOC_VALUES_CURR
Exceptions:
NO_DATA_TO_PASS
Add a commentCharacteristic's own input screen - Part 5 - show characteristic's own update screen
| ZCL_ABAPBLOG_COM_CLASSIFIC.nugg |
Now we're ready to build the data for screen output, call the update screen and then move the data back from screen to reference data. We will use here:
- COC1_FEATURE_CHECK to get characteristic ID
- CTMS_DDB_INIT to initialize memory
- CTMS_CLASS_DDB to put in memory classification settings
- CTMS_DDB_SET_VAL_FROM_OBJECT to set values in update screen from existing object (option)
- CTMS_DDB_SET_VALUE_INTERNAL to set values in update screen in case of using reference data structure
- CTMS_DDB_SET_VALUE_ONLINE to call the update screen
- CTMS_DDB_HAS_VALUES_INTERNAL to check and get the values from the update screen after user action
- zcl_abapblog_com_classific=>create_structure_for_class to create reference data structure
- zcl_abapblog_com_classific=>move_screen_val_to_ref_data to move screen values to reference data
- zcl_abapblog_com_classific=>clear_initial_line_api_vari to delete initial line for multiple values characteristics
- zcl_abapblog_com_classific=>move_ref_data_to_screen_val to move reference data to update screen values table
Characteristic's own input screen - Part 4 - Move screen values to reference data
| ZCL_ABAPBLOG_COM_CLASSIFIC.nugg |
In previous article I've shown how to move characteristics from reference data to screen values table, this method is doing opposite way from screen values table to reference data structure.
Importing:
IT_VALUES TYPE TT_API_VALI -> screen values table
I_ATNAM TYPE API_VALI-ATNAM -> Characteristic Name
Changing:
C_DATA TYPE REF TO DATA
Exceptions:
NO_DATA_TO_CHANGE
Add a commentCharacteristic's own input screen - Part 3 - Move reference data values to screen
| ZCL_ABAPBLOG_COM_CLASSIFIC.nugg |
Before we can call the screen with the characteristic value to change we need to convert data from our reference data structure to table of type TT_API_VALI. Following method shows how to do it.
Importing:
I_ATNAMTYPE API_VALI-ATNAM ->Characteristic Name
I_DATATYPE REF TO DATA-> our reference data
Changing:
CT_VALUES TYPE TT_API_VALI-> Structure for characteristic screen
Exceptions:
NO_DATA_TO_CHANGE
Add a commentCharacteristic's own input screen - Part 2 - Clear Initial Line
| ZCL_ABAPBLOG_COM_CLASSIFIC.nugg |
We've got method to convert internal value to float, now it's time for next one which I didn't suppose it would be needed but when I was calling CTMS_DDB_SET_VALUE_ONLINE to show input screen with previously filled data by CTMS_DDB_SET_VALUE_INTERNAL then for multiple value characteristic I was always receiving one additional line to these which was passed by me in export parameters. The funny thing was that it wasn't the case when CTMS_DDB_SET_VAL_FROM_OBJECT was used. Of course this line was initial but the values were treated after as imputed by user. So as always I started to debug the code to see why it's happening. Finally I found that internal table WS in the function group CTMS was not refreshed during the call of CTMS_DDB_SET_VALUE_INTERNAL.
As I couldn't refresh it in any call of FM from this function group I had to use old trick with assignment of data from program in memory. But firstly I check with FM CTMS_DDB_HAS_VALUES_INTERNAL if any values are already there.
Importing:
IT_API_CHAR TYPE TT_API_CHAR -> Table type for structure api_char_tab
Add a commentCharacteristic's own input screen - Part 1 - Convert Values To Float
| ZCL_ABAPBLOG_COM_CLASSIFIC.nugg |
Welcome back :-)
Some time ago I presented how I get data from classifications to reference data variable ( or table). If you feel comfortable with my method then we can go further. I had a task to update some characteristic values from ALV grid, this would be not a problem at all if the characteristics would be defined from the begriming, but they weren't. In that case I couldn't just add needed fields to fieldcatalog and call FM to update characteristics when save button was pressed. I realized I need dynamic structure for ALV which will call standard screen for characteristic update. If this could be done then I could omit carrying about type of characteristics (date, number, char ) and if it is single o multiple type. So I started to dig in SAP, debug standard functions and I was finally able to prepare all needed functions.
Some time ago I presented how I get data from classifications to reference data variable ( or table). If you feel comfortable with my method then we can go further. I had a task to update some characteristic values from ALV grid, this would be not a problem at all if the characteristics would be defined from the begriming, but they weren't. In that case I couldn't just add needed fields to fieldcatalog and call FM to update characteristics when save button was pressed. I realized I need dynamic structure for ALV which will call standard screen for characteristic update. If this could be done then I could omit carrying about type of characteristics (date, number, char ) and if it is single o multiple type. So I started to dig in SAP, debug standard functions and I was finally able to prepare all needed functions.
So firstly what was needed (additionally to previously presented methods):
- method to show standard characteristics update screen with possibility to put there own values at call
- method to copy data from my reference data structure to screen values
- method to copy data from my reference data structure to screen values
- method to save characteristic value
- method to convert values from standard type (date, char, number, currency) to characteristic value (in float)
- method to clear initial line which was appearing when standard screen was called without reference to database values.
In this and following parts of this tutorial you'll see all mentioned methods and example of their usage. You can also find the code in attached NUGG file for easier import to your system.
Add a comment
Read more ...
Add a comment
Scan program for authority-check
| ZAB_AUTHORIZATION_CHECK.nugg |
Some years ago I was asked to create a report to check if in our Z-developments we are using authorization check or not. Of course not in all developments you need to have authorization check as sometimes standard SAP function modules provides proper checks inside them, but in many cases developer should take care about them inside the coding. The code I will provide below will scan program for AUTHORITY-CHECK statement and will collect the parameters of the call of AUTHORITY-CHECK. But one thing you have to have in mind, if developer used separate FM or class to check authorization then this report will not show any authorizations for program as it's looking only in the code of the program and not for the authorization-check inside called FM or classes.
Please look through the code or import to your system using nugg file.
Extend allowed runtime of a program
| ZAB_RESET_RUNTIME.nugg |
When you create a report or transaction that handles a lot of data with multiple selects and functions that are doing some manipulation of the data, or you have to call in this report a function module thousand times and you want to be sure that no matter how long it takes it should be done but your system administrators have put some restrictions for time limit then you have to use one of this methods:
- Call commit work whenever you want to reset the counter of running time for your transaction (especially if you haven't done any update into database tables)
- If commit work doesn't work or you don't want to use it at the moment then you could use FM TH_REDISPATCH with the check_runtime parameter equal to 0.
- You could also you FM SAPGUI_PROGRESS_INDICATOR for the same purpose but keep in mind that showing indicator too often can slower your program.
Both of the methods will make that the counter for application runtime will be reset, but be careful this can make you application run really long. Also if you got one select statement which takes more than maximum runtime for your system then it will not help so you have to prepare your coding to be able to use any of this method, like spliting the selects statements to parts or to select single in the loop.
Although it's nice to know this possibility my advice is to not to use it very often as the less time you have for program run the more optimized code you can provide, so it's really something that you use if you do not have other choice and you agreed that with your system admins.
Examples: (run the program and look into SM50 to see the runtime)
Custom selection-screen fields for MD07/MS07
| ZAB_EXTMD07.nugg |
You may noticed that standard transaction MD07 and MS07 offers basic filters on selection-screen which allows user to select materials they are responsible for, the problem comes when in your company users wants to be more precise in filtering or when the responsibility is set not only on a base of MRP controller. Fortunately SAP gives us the possibility to call MD07 and MS07 with our own list of materials using dummy transaction codes MDC7 and MSC7. All you need to do is to prepare a table of type MDMWX, export it to memory 'START_MD07' and call dummy t-code. Bellow you can find an example of the report to call MD07/MS07 with own material list where on selection screen you can find for example purchasing group which is not available in standard. You can also find a link to nugg file.
Selection Screen - Part1 - Parameters
| ZAB_SSDEMO1.nugg |
Today, as a first entry in Beginners part I'd like you to show how to build parameters on selection screen. All this information you can find under F1 help but here you've got visualization of what's written there. Hope it will help to understand this statement. As embed video is my first one then please accept my apologies in case of errors and wrong pronunciations as English is not my native language.
More Articles ...
RM07DOCS
ISOLATE
SELSCREEN
ADT
TechEd
RELEASABLE
DDSHIFACE
Create a nice looking chart with CL
GUI
CHART
ENGINE - Part 3 - Chart Data and render
ALV
GRID
FRIEND
QM ATTACHMENTS
CUSTOM
CONTAINER
KKB
SELECTIONS
READ
ABAP
STRUCTDESCR
CTMS
DDB
HAS
VALUES
INTERNAL
ALINK
CONNECTION
SET
VALUE
ONLINE
SAP TechEd
AT SELECTION-SCREEN OUTPUT
OPR
ALLOCATION
PROVIDE
ESDUS
COMPONENTS
MAINTAIN
TOTLINE
ESRUO
IXML
ELEMENT
MB51
ZDEMO
FALV05 - Adding
Removing
Disabling grid toolbar
SAVE
USER
SETTINGS
UPDATE
PREPARE
PURCHASE
REQUISITION
COC1
FEATURE
CHECK
LOAD
COMPLEX
ITM
COM
ELEMDESCR
Mass replace popup for ALV grid
The SIN of progress indicator
REUSE
DISPLAY
TYPEDESCR
HEADER
HANDLE
MM-
GTGET
GOS
MANAGER
SALV
CONTROLLER
METADATA
LVC
FIELDCATALOG
Classifications - Part 2 - Get Object Details
FALV
FREE
SESSION
MEPO
DOCUMENT
SBCS
SEND
CMD
API
EXTRACT
STREAM
FACTORY
Convert date to and from external date type
ABAP IN ECLIPSE
CLASS
OBJECTS
Enhanced MB51 Part 5 - Export from MB51
XML
GAME
ABAP Favorites Eclipse plugin
