4 Steps to Develop a Point of Sales (POS) with SAP Screen Personas 3.0
- by Diony J. Ruiz R., SAP Architect and Senior Consultant, Group Intellego
- October 31, 2016
Learn how to make adjustments to the Create Sales Order transaction (transaction code VA01) using SAP Screen Personas 3.0. See how SAP Screen Personas 3.0 helps make the process of inputting values for a point of sale (POS) order faster and more intuitive than completing this process in a standard SAP system
In this article you will learn:
- Concepts and use of SAP Screen Personas 3.0
- How to create a customized sales order screen, which is similar to a process for point of sales (POS)
The point of sale (POS) is the time and place where a retail transaction is completed. The Create Sales Order transaction in SAP ERP does not make it easy to use touch operations (i.e., a touch screen). It does not provide you with images and buttons for fast, easy creation of a POS.
SAP Screen Personas 3.0 allows productivity through personalization via a simple drag-and-drop approach to modify many common SAP GUI screens to make them more usable as well as more visually appealing. The main goal is to make sales through a screen that is friendly and simple and that with few process steps or clicks, allows touch screen interaction.
SAP Screen Personas 3.0 allows adjustments to SAP transactions, seeking to bring them into a simple and effective style. SAP Screen Personas 3.0 requires installation by a technology team. Use this link to review the requirements and installation processes: https://websmp208.sap-ag.de/~sapidb/012002523100013158972014E.
SAP Screen Personas 3.0 is suitable for processes in SAP settings for desktop use. (Other tools such as SAP Fiori are based on multiplatform use: desktop, mobile, or tablet.)
It is feasible to set the screen for the Create Sales Order transaction (transaction code VA01) so that it can be used as a point of sales (POS). A weakness of the Create Sales Order transaction is that it is not easy to be used as a POS because multiple steps are required to incorporate a material or service for sale. I show you how to develop these screens using SAP Screen Personas 3.0 providing reduced training and support costs with simple, role-based screens that speed ramp-up and minimize user errors. You can also increase compliance and data quality by making it easier to enter information into your system of record.
I make adjustments through SAP Screen Personas 3.0 that are based on the Create Sales Order transaction (transaction code VA01). The first changes are based on the initial screen that appears after you execute transaction code VA01 where the Class Sales Order is selected. Figure 1 shows the initial design screen for SAP Screen Personas 3.0.
Figure 1 shows a demo image for the transaction code VA01 (Create Sales Order) showing what you can perform using Screen Personas 3.0 in an SAP transaction.
The initial SAP Screen Personas screen for the Create Sales Order transaction
After you select the Order Type (by clicking buttons that replace the traditional Order Type field), you move to the next screen in which you incorporate the values Customer, Material, and Quantity.
In Figure 2, you see the prototype of the screen Create Sales Order transaction screen (transaction code VA01) after selection of the Order Type. It is divided into three main areas: Customer data, Item, and Total (net value).
Screen proposal sales order with SAP Screen Personas 3.0
Figures 1 and 2 show the settings that you need to use in the Create Sales Order transaction (transaction code VA01).
In the following four steps I describe how to transform the Create Sales Order transaction (transaction code VA01) in SAP sales and distribution (SD) to a more suitable design for use as a POS. You make modifications to the screens with the solution SAP Screen Personas 3.0.
Would you like to see this full item?