GuiXT Developer Toolkit used to generate GuiXT screens
11) User makes a
request via SAPGUI (e.g. VA01)
2) SAP responds with VA01 screen
3) GuiXT screen modifications are applied and SAPGUI draws new screen for VA01
SAP GUI
GuiXT®
1
2
3
Presenter
Presentation Notes
So how does it work? Here is the basic architecture. When a user goes into SAPGUI and goes to a transaction code, the request goes to the backend server, the SAP backend server runs the ABAP code as it normally does, and sends the package to SAPGUI and SAPGUI draws the screen. If you have GuiXT activated and there is a script on that particular transaction, before SAPGUI draws the screen, GuiXT intercepts the packet, applies the changes that you have in the script for that screen, repackages the info, sends it back to SAPGUI and then SAPGUI draws the new screen. So there is no change in the backend application server. You are not changing any of the existing security or validations or the business logic, and there is no ABAP required to have a simplified GuiXT screen for your users.
The engine itself is included with SAP GUI, but you can only simplify one screen at a time. In order to aggregate multiple screens, tabs, and transactions onto one or more screens, you need to license one of our touchpoints, Desktop (SAP GUI), mobile or web touchpoint which requires a pass through server. You can connect the native client iOS or Android app (available in the Appstore or PlayStore) directly to your backend SAP system, but you will only see native SAP screens on your device, and will not gain the full benefit of Liquid UI. Let’s see what some of these fully customized Uis looks like starting with the Sales and Distribution module.
Other solutions on the market today are based on a multitude of middleware stacks, that are not integrated with one another. Development is done on each of these silo’d platforms, with no reusable components, then deployed to the various touchpoints. Often times, either Java or ABAP is required which requires deep coding, tessting, debugging, deployment and the full software development lifecycle or new front end tools on the market are for web/desktop environments only.
The liquid UI technology is a unified platform meaning you can develop once and deploy to any of the mobile or desktop touchpoints. This could be a browser or portal, a scangun, an iOS or Android smartphone or tablet, or back to SAP GUI. You can also create an excel spreadsheet or PDF document with the same development effort.
Goods receipts are used to record the items that are received which have been sent using the information from a purchase order. The goods receipt is important as it moves the items into stock, updating the stock levels and allowing the items to be used in the production process. If an item is received into stock, the value of the item is posted to the company accounts. With standard SAP, the MIGO transaction requires the user to input data on a number of tabs. Using Liquid UI, this is all brought down to a simplified user experience. �As you can see, the names of labels have been changed, etc.
We have also introduced to the market new ways to manage and monitor multiple work orders from ONE screen. New GuiXT Plant Maintenance solutions not only streamline standard SAP transactions, but also provide reports on large amounts of data, easily organized enhancing the ability to view, interpret and make mass changes without having to manually navigate through SAP screens and tabs. Our Plant Maintenance Console provides customers with: Significantly increased productivity Reduced costs due to keeping assets running at peak performance Increased response times via access to and real-time analysis of system data There is a launchpad on the left to quickly navigate to the appropriate transaction. The center section includes a matrix of pushbuttons that show the number of work orders sorted by priority and different statuses. When you click on any one of these pushbuttons, a summary of the work orders appears on the right side. In this example, the green indicator square shows the pushbutton that was pressed, and on the right shows 32 work orders. As you can see, this one screen provides everything a Supervisor needs. You can also select Planner or Scheduler to get slightly different views for the same plant.
Founded by 2 Ex-SAP employees Dr. Gerhard Rode and thomas Ewe. Gerhard was 50th employee at SAP and is the inventor of ABAP. Also know as father of ABAP. Thomas Ewe worked at SAP labs and was instrumental in the development of Java gui Vast experience across all modules and industries to draw from and Experience that helps avoiding pit falls Unified UI strategy platform with patented connectivity across touchpoints, SAP @ your fingertips
• Download the native iOS or Android app, tell us what you like or don't like.
• As a token of our appreciation, everyone receives a free 30-day Designer, Plant Maintenance Console, iOS, or Android license (including Support) after completing the survey.