Simplifying the mass-management of binding master data in SAP PLM recipe management

OData support
Supervisor:
Dr. Martinek Péter
Department of Electronics Technology

Goals

Study the SAP PLM Recipe Management, mainly the structure of the specification master data and the definition of the constraints which are used during the compliance check. In addition, study of SAP web-UI technologies, the Web Dynpro, the Floorplan Manager and the PLM UI Framework were also needed to be studied.

Using the above-described elements, I created an application which supports defining constraints to the compliance check. Such constraint can be for example a food must not contain more carbon hydrate than 10 %, or it must not contain aspartam or a toothpaste must contain at least 1500 ppm fluor. With my constraint maintenance application, the Fast Constraint Maintenance (FCM), it is possible to define constraints to an arbitrary application area and regulation. It is also possible to modify or delete existing constraints or create new ones. The tables which supports the input contain the same fields which are also needed to be filled during defining constraints in the Change Specification application. The constraints defined by this application become part of the master data as if they were defined in the specifcation application.

Implementation

The first part of this essay can be divided into three parts. In the first, I present the software developing methodologies used by SAP. These are the Scrum and the Lean and these are described in chapter 2. The 3rd chapter details the technologies with which the application is implemented. I detail here the Web Dynpro and the Floorplan Manager. Moreover, I present the PLM UI Framework, which ensures standardized data exchange between the UI and the backend.

In the second part of the essay, from chapter 5, I present the structure and design of the application, the UI and the service provider. Besides the class diagrams, which shows the static structure of the application, I show sequence diagram which depicts the data transfer from the UI to the backend. In addition, I detail the structure of the backend class, the Business Object class which provides not only the business data to the UI but also the field control.

Downloads

Please sign in to download the files of this thesis.