GDS Reports by Istvan Nemeth Build Your Own SAP Fiori App in the Cloud 2016 Edition SAP Fiori UX Develop Challenge

Transcription

1 GDS Reports by Istvan Nemeth Build Your Own SAP Fiori App in the Cloud 2016 Edition SAP Fiori UX Develop Challenge STORY Manufacturers are using Global Data Synchronization Network to connect their systems and products to trading partners (other manufacturers, suppliers, distributor, retailers) through Data Pools. The highly standardized way of communication provided by GDSN makes B2B data exchange painless and eliminates manual processes. After the development of a brand new product, details are sent to Data Pools for registration. If the product meets the Data Pools formal requirements, manufacturer can publish the product (including availability dates, promotions, etc.) to selected partners. Otherwise an error message is sent back to Manufacturer. SAP has a dedicated solution for this scenario called MDM-GDS. It stores product master data, messaging information (dates, statuses, responsibles) and handles communication between the local system and Data Pools. Reports and analytics of Data Pool responses, product features or partner communcation help Manufacturers to increase their efficiency. That's where GDS Reports comes into play. Segmentation This app is for manufacturer companies communicating their products to partners through Data Pools using SAP MDM- GDS. Targeting Application is specifically for team leaders who are responsible for product synchronization in a manufacturer company. They want to make decisions based on synchronization results and measure employee KPIs to improve productivity. Positioning Application provides the flexibility to create reports based on customer needs (using any field of the database), so it can be adapted to customized segments of the standard SAP application as well. Responsibles can create and display reports without technical and programming knowledge; interactive charts can be used on meetings to present the results. In addition, SAP Fiori ensures the coherent user experience with other SAP products.

2 PERSONA John Improve my decision making and report to my boss 38 year. He has a wife and 2 children. He is working as manager for 4 years. Head of Product Communication Team Decision about employees salary Oversee blocking communication issues Prioritize employees task Report monthly to his boss o Product statuses o Partnerships Easy to use app to fetch product data Dynamic charts to present the results Ability to delegate reporting task to others See real time statistics of communication Create reports for his boss with less effort Measure employee KPIs Reports must be created manually in Excel and Powerpoint He must use 3 applications to extract product information 30% of his work time is wasted to report creation His boss Employees USER EXPERIENCE JOURNEY POINT OF VIEW John, the head of the Product Communication Team needs a way to create meaningful reports fast and efficiently so that he has more time for other work related activities.

3 MOCKUP Screens Published mockup with major navigation entries can be found here. You can clink on Add, Edit, Save buttons and on Icon Tab Bar elements. All of the desired mockup screens has been implemented during the Develop challenge, so detailed description of the screens can be found in the next sections. SAP WEB IDE WORKSPACE OF THE PROJECT

4 SAP WEB IDE APP PROTOTYPE Users can search for reports by name. Report list can be refreshed. On mobile devices, pull down is supported. Report list contains the stored reports, including their category, name, localized creation date, owner user, icon of their type and visibility. Reports can be sorted, filtered and grouped. New reports can be created from the footer. In edit mode, these buttons are disabled. Filter options are listed in a popup. User selects a property from the list, then all of its available values are listed in a new list. Selected filters are shown as numbers in the field list. Sorting field can be chosen from a Select. By default, Name is selected for sorting. Grouping field can be chosen from a Select. By default, no grouping is selected. If both grouping and sorting is seleted, items will be grouped, and sorting will applied inside groups.

5 Report Details Object header contains name, description, creation date, modification date (if any) and category of the selected report. Report data is splitted into 4 sections (tabs). Details section contains additional properties (type, visibility, restrictions and main table). It also holds the list of dimension, measure and filter fields. Reports can be edited and deleted (delete is disabled in sandbox). Report Chart Charts are used to visualize report results. 4 different type of charts are supported: column (default), bar, stacked column, stacked bar. Chart can be fullscreened to use in a presentation. User can turn on legend to highlight measures in the chart.

6 Report Results, Feedbacks Result of the report is visualized in a table. Table columns are generated runtime based on the retrieved data. First n columns are dimensions, further columns are measure values. Application users can comment on reports. They can ask questions, give feedbacks or take a note. Edit/Add forms are used to create/modify report definitions. These definitions are sent to the backend which calculates the report result based on them. Some inputs have predefined value set. They are visualized as combobox. Inputs with high amount of possible values are using suggestions and value helps. In edit mode, list handlers are disabled.

7 Value help contains the name of the selectable entry; in addition it displays the object type. Entries can be searched. If more entries can be selected, entries in the input field (tokens) are excluded from the popup. During the save process mandatory fields are validated. If any of them is empty, the affected fields are marked and error message is displayed. Used technologies, techniques - i18n support for english and hungarian languages. All texts are localized. - Mock server support. In sandbox environment, an OData mock server with custom metadata.xml and test data is used. Edit is supported by mock request. - Draft handling. Creating a new report and modifying an existing one results in a draft which is handled separately from active reports. - Application based on a component. An application wide controller holds the cross properties and functionalities. - Navigation is based on routing by a separated navigation handler. - Report display and edit/add views are shown in the same parent container no routing is required in this case. - Mobile support with navigation. - Form validation. - Value help and suggestion support for fields and tables on the form page. - Handling of busy state at application and at master/detail level. Youtube video minutes long video with english subtitle. Application URL Deployed application can be found here: