The IO_EVENT in the parameter provides you with the event.Ĭode Snippet of Post Exit: The following code snippet is used for calling a custom pop up window.Ĭode Snippet of Post Exit: The following code snippet is used for controlling the visibility of a button. Here we can intercept the FPM events and write your own code. Moreover, it can be used to collect messages which are not handled inside UIBBs and to forward them to the FPM message handler. Click on Pre-exit / Post-exit / Overwrite as per your need and you will be provided with the enhancement method.ĪFTER COMMIT: You can perform cleanup activities such as releasing database locks, releasing other resources, and triggering an event for processing after a successful commit.ĪFTER PROCESS EVENT: It can be used for handling transactional events for example SAVE or CHECK. Here you are provided Pre-exit, Post-exit and Overwrite. to the Web Dynpro component.įor enhancing the component controller methods, double click on component controller and go to the methods tabs. Now using this enhancement you can add custom code, views, methods, etc. Provide the enhancement name and click the check mark icon to continue. The first step is to create an enhancement by clicking the enhance button or CTRL+F4 key. Open this Web Dynpro application using transaction code SE80. Within the package ERP_SLS_LO_OIF, the main Web Dynpro component is LO_OIF_MAIN_COMP. The FPM (Floor Plan Manager) with the Web Dynpro application interface provides you with methods to allow the application to participate in all FPM events that happen during the entire lifetime of the application. The enhancement framework concept is used to create custom views, handling of those custom views and dynamically controlling the visibility of different elements within Lean Order Management.
To quote Roger Manifold, “Good manners don’t cost nothing”. As in many technical endeavors, good housekeeping and cleaning up after yourself is always appreciated. For example, during transaction processing the system locks table entries to prevent other users from updating data while you are processing it. In this entry, I will discuss some of the LOM capabilities for controlling what happens behind the scenes to manage technical events as well as screen content.
In my previous two posts in this series, I discussed how to control field level help information and how to influence the look, feel and flow of the end user experience. If you are looking for ways to enhance order processing for your SAP Solution click here OMS+ Simple Order Management for SAP and check out DataXstream’s OMS+ Solution.Ĭreating Custom Views, Events, and Controlling the Visibility of Data Elements Editor Update: This article originally published in 2012.