Patent Application
20140210838
Business software such as enterprise resource planning (ERP) software implements business processes by modeling business data as business objects (BOs) with data exchange between the BOs. The business data provided via BOs can be accessed through mechanisms such as graphical user interfaces (GUIs), forms, and analytical reports.
Conventional business software typically displays BO data in a text, numeric, or chart format. While such an interface can present large amounts of data to a user, there are many drawbacks to this approach. By viewing BO data in a text, numeric, or chart format, for analytical purposes, it is difficult to identify specific BO data with particular attributes. Although a search may be performed on the BO data to narrow the results, such a search may require additional steps and may be time consuming, especially if the search has to be performed multiple times. In addition, BO data presented in a numeric table format is typically not interesting to a user.
Embodiments may be discussed in systems to visually display information about BOs. In an embodiment, a mapping between a business object and a corresponding visual representation of the business object may be read. The mapping may include a relationship between the business object's attributes and the visual representation's visual attributes. The mapping may include a relationship between the business object's attribute values and the visual representation's visual attribute values. The visual representation may be displayed on a graphical user interface based on the mapping.
In an embodiment, the visual representation may be displayed relative to a visual context displayed on the graphical user interface. In an embodiment, in response to an activation of the visual representation, a magnified view of the visual representation may be displayed. In an embodiment, in response to a user action performed on the magnified view of the visual representation, information associated with the business object may be modified. In an embodiment, in response to a user action performed on the magnified view of the visual representation, an electronic communication with a person associated with the business object may be initiated. In an embodiment, in response to the activation, additional visual attributes of the visual representation may be displayed. In an embodiment, in response to a user action performed on the visual representation, information associated with the business object may be modified. In an embodiment, in response to a user action performed on the visual representation, an electronic communication with a person associated with the business object may be initiated.
Business software usually includes a standard set of BOs which can be utilized by the software user to model a business entity. For example, business software may include BOs representing business entities such as contacts, sales opportunities, trade promotions, sales orders, sales quotes, customer quotes, service documents, etc. Each BO may include attributes which define metadata associated with the BO. For example, a business promotion BO may represent a business promotion offered by a first company through a second company to consumers. The first company may be a soft drink company and the second company may be a major retailer. The promotion may have a start date and an end date (a promotion period). The promotion may offer the product, for example, a soft drink, for the promotion period at a particular sale price. The business promotion BO may include attributes such as the name of the second company, the size of the second company, the type of the second company, the name of the promotion product, the sale price of the product during the promotion, the price of the product without the promotion, the quantity of the product sold during the promotion, the start date of the promotion, and the end date of the promotion.
In an embodiment, the attributes of a BO may include other associated BOs. For example, a company BO may represent a customer company. The customer company may include employees who serve as communication contacts. To reflect this relationship, the company BO may include contact BOs representing the communication contacts.
Conventional business software typically displays BO data in a text, numeric, or chart format. While such an interface can present large amounts of data to a user there are many drawbacks to this approach. By viewing BO data in a text, numeric, or chart format, for analytical purposes, it is difficult to identify specific BO data with particular attributes. Although a search may be performed on the BO data to narrow the results, such a search may require additional steps and may be time consuming, especially if the search has to be performed multiple times. In addition, BO data presented in a numeric table format is typically not interesting to a user. A user utilizing the BO data may be more motivated to analyze the BO data if the data is presented in a more “attention-grabbing” manner. For example, videogame enthusiasts may be more motivated to analyze BO data if the data is presented in a more interactive fashion.
To address the above issues, in an embodiment, BO data may be presented in a visual format.
In another example, visual attributes of the customer visual representations 102, 104, and 106 may indicate the customer satisfaction associated with the underlying customer BOs. The customer associated with visual representation 102 may be unhappy, the customer associated with visual representation 104 may be satisfied, and the customer associated with visual representation 106 may be very happy. Therefore, a lightning visual attribute may be displayed with visual representation 102 to indicate that the associated customer is unhappy, a cloud visual attribute may be displayed with visual representation 104 to indicate that the associated customer is satisfied, and a sunshine visual attribute may be displayed with visual representation 102 to indicate that the associated customer is very happy.
In an embodiment, the GUI 100 may display one or more visual contexts and the BO visual representations may be displayed relative to the one or more visual contexts to convey additional information about the underlying BOs. A visual context may be any visual element which displays possible values of one or more business attributes. For example, a visual context may be a geographical map, a scale, a chart, etc. In an exemplary embodiment, a geographical map 110 may be displayed on GUI 100 as a visual context. The underlying customer BOs of visual representations 102, 104, and 106 may be associated with a geographical location. Specifically, the geographical location associated with the customer BO may be the location of the customer's headquarters. Each visual representation 102, 104, and 106 may be displayed at a position relative to the geographical map 110 to indicate the approximate geographical location of the customer.
In an embodiment, a BO visual representation may be activated to display additional details associated with the BO visual representation. In an embodiment, activating a BO visual representation may trigger a “zooming in” and a magnified view of the activated BO visual representation may be presented on the GUI.
In an embodiment, actions may be performed on visual representations, magnified views of the visual representations, visual attributes, and/or visual contexts. In response to the actions, information associated with the corresponding BOs may be altered. For example, an action may be performed by a user such as a sales manager to reflect a successful business opportunity which resulted in a sales order. The action may be visually dragging the corresponding business opportunity attribute 212.01 from the set of business opportunity attributes 212 to the set of sales order attributes 216. Responsive to the action, the business opportunity attribute 212.01 may be visually converted into a sales order attribute. The underlying customer BO of visual representation 206 may be automatically modified to reflect the conversion. In an embodiment, the changes to the underlying BOs may be persisted in a storage device such as a database.
In an embodiment, a communication may be initiated and/or transmitted in response to actions performed on visual representations, magnified views of the visual representations, visual attributes, and/or visual contexts. For example, a user may want to send an e-mail to a business contact at the customer company represented by visual representation 206. Therefore, the user may right-click on the corresponding contact visual attribute 214.01 and select an option to “send e-mail” from a right-click menu. Responsive to the action, the user may be presented with an e-mail composition window 218 prefilled with the e-mail address of the business contact corresponding to visual attribute 214.01. The user may then send the e-mail 218 to the business contact. Although e-mail is discussed as a form of communication for illustration purposes, in other embodiments, any form of communication may be initiated and/or transmitted including text message (such as text messages sent using a Short Message Service (SMS) and/or Multimedia Messaging Service (MMS)), multimedia chat, video chat, telephone call, audio conference, video conference, and application specific communication such as a Skype®, Google® chat, and WhatsApp® message.
A person having ordinary skill in the art will appreciate that activation of visual representations of BOs and actions performed on visual representations may be implemented in many ways including implementation through a mouse, keyboard, trackball, joystick, motion sensor, sensor on a touch screen of a device displaying the GUI, etc. In an embodiment, activation of displayed elements may be implemented through output from a motion sensor. For example, shaking and/or tilting a PC tablet with a motion sensor in a particular manner may activate the displayed elements.
Multiple mappings may define multiple levels of relationships between the BO visual representations/attributes. For example, mapping 321 may define the relationship between the BO visual representations/attributes' values shown in
A person having ordinary skill in the art will appreciate that the mappings shown in
A person having ordinary skill in the art will appreciate that although the discussion above refers to visual representations and visual attributes of BOs, the principles described also apply to audio-visual representations and/or audio-visual attributes of BOs. Visual representations/attributes/contexts may include still images, moving images, and/or videos.
A person having ordinary skill in the art will appreciate that while internal systems 430 and external systems 450 are included in
Each of the systems in
In an embodiment, memory 413 may contain different components for retrieving, presenting, changing, and saving data. Memory 413 may include a variety of memory devices, for example, Dynamic Random Access Memory (DRAM), Static RAM (SRAM), flash memory, cache memory, and other memory devices. Additionally, for example, memory 413 and processing device(s) 412 may be distributed across several different computers that collectively comprise a system.
Database 411 may include any type of data storage adapted to searching and retrieval. The database 411 may include SAP database (SAP DB), Informix, Oracle, DB2, Sybase, and other such database systems. The database 411 may include SAP's HANA (high performance analytic appliance) in-memory computing engine and other such in-memory databases.
Processing device 412 may perform computation and control functions of a system and comprises a suitable central processing unit (CPU). Processing device 412 may comprise a single integrated circuit, such as a microprocessing device, or may comprise any suitable number of integrated circuit devices and/or circuit boards working in cooperation to accomplish the functions of a processing device. Processing device 412 may execute computer programs, such as object-oriented computer programs, within memory 413.
The foregoing description has been presented for purposes of illustration and description. It is not exhaustive and does not limit embodiments of the invention to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from the practicing embodiments consistent with the invention. For example, some of the described embodiments may include software and hardware, but some systems and methods consistent with the present invention may be implemented in software or hardware alone. Additionally, although aspects of the present invention are described as being stored in memory, this may include other computer readable media, such as secondary storage devices, for example, solid state drives, or DVD ROM; the Internet or other propagation medium; or other forms of RAM or ROM.
