Then we can replace the original standard GUI status ( l_pfstatus) and its program ( l_pfprogram) by our custom objects. Yes, we can develop a new custom program and insert a GUI Status as the program component, and we also add a new button, saying Custom Header, into the Application Toolbar of the GUI Status. OK, I believe some people have got another idea on the solution now. The attributes DYNPRO and PROG indicate the current screen and program. (Yes, this is my idea on first solution)Īlso by debugging, I found the application GUI Status is set in method PBO of class CL_WINDOW_MM (Inheriting from class CL_COMPOSITE_SCREEN_VIEW_MM), and the GUI Status is determined by method EXCLUDING_FUNCTIONS. When I investigate the program at this point, I believe we can add a new subscreen (or more than one) onto the tabstrip by adopting the similar approach.
#Megui count run updater plus#
If you press F1 help on the screen field, you will find the program of screen editor is different from the program of the main screen.īy debugging, I found the function module MEGUI_BUILD_REQ_HEADER_PLUGIN is used for integrated to components of tabstrip, and the text editor is plus to tabstrip in this function module. Generally, there only a Texts subscreen on the tabstrip. As the description of MEGUI, all the components related to user interface of purchasing documents are integrated into/by this function group, for example, screens, GUI statuses (In my opinion, MEGUI is just like the View of MVC pattern).įor the purchase requisition application, the main screen is 0014 of program SAPLMEGUI (or function group MEGUI), and GUI Status is REQ of program SAPLMEGUI (or function group MEGUI). This function module is a component of function group MEGUI (User interface for purchasing document).
#Megui count run updater code#
In source code of triggered program RM_MEREQ_GUI, the function module MEGUI_MAINTAIN is invoked. For these transactions, the triggered program is RM_MEREQ_GUI (See SE93). A glance and investigation on purchase requisition applicationĪs everyone knows, the transactions for purchase requisition generally include ME51N, ME52N, ME53N, ME54N. The result of the idea is we have an enhancement function for purchase requisition, but I hope the idea can also provide us a new thinking for other similar enhancement requirements.ġ. Actually, I like the first one(And I think most of you too)
#Megui count run updater how to#
In this document, I would like to share two solutions on how to make a custom header for purchase requisition. So, in case of receiving a requirement on making a custom header for purchase requisition or adding a new screen on header level, generally we will take an alternative solution, for example, add a custom screen tab on purchase item level, users can input header data on item level and the data should be item-dependent or item-independent, or even design a new application program to achieve the requirements.īut now, thanks for the new generation of enhancement technique, we can achieve the requirement by the implicit enhancement, and plus some SMOD/CMOD enhancement and Badi. Of course this approach is hardly acceptable. Some years ago we really cannot do it unless we put lots of effort on changing standard program. Well, it seems that it is not possible to adding a custom screen for purchase requisition header level. No standard enhancement and even no database design for purchase requisition header. For example, EKKO and EKPO for purchase order, VBAK and VBAP for sales order, BKPF and BSEG for FI documents……įor purchase requisition, it seems that the data is stored on item level, we only have EBAN for purchase requisition (other database table is not taken into account in this blog, for example account assignment table EBKN).
A general designing of database table for business documents should commonly have Header and Items, some has Schedule Lines.
But just as my knowledge, SAP has not provided any user-exit/Badi/SMOD for enhancing the screen of header part of purchase requisition.Īnd as we also know, purchase requisition database designing is different from other businesses object documents.
I had saw some threads/posts in SAP forums, they were asking for the solutions on how to adding a custom screen/tab on the purchase requisition.
0 kommentar(er)
