Patent Application
20070271107
The accompanying drawings, which are incorporated in and constitute a part of this specification, show certain aspects of the present invention and, together with the description, help explain some of the principles associated with the invention. In the drawings,
Reference will now be made in detail to the invention, examples of which are illustrated in the accompanying drawings. The implementations set forth in the following description do not represent all implementations consistent with the claimed invention. Instead, they are merely some examples consistent with certain aspects related to the invention. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
Client system 110 may include one or more processors, such as computers, to interface with server system 130. User interface 120 may provide an interface to allow a user to interact, through service manager 140, with other applications, such as service providers 160-161 and their corresponding business objects stored in repositories 171-172. Moreover, a service, such as service 160 may call another service, such as context-dependent service provider 161 to obtain context dependent value help. Value help information may be information, such as values, to help a user perform a task (e.g. complete a purchase order). This value help information may be provided based on context, such as the context of information provided by the user or the context of the service. For example, if the user inputs Germany (“GE”) as the destination country for the purchase order, a context-dependent service provider 161 may be called to provide context-dependent value help information. In this example, the context-dependent service provider 161 returns, for the context “GE,” a complete list of the regions (also referred to as provinces) associated with the country code “GE” determined at runtime.
Moreover, another service provider (not shown) may also call context-dependent service provider 161 to obtain context-dependent value help. For example, a service provider may generate shipping documents for a user at user interface 120. In this example, the service provider may receive an input from a user that the destination country for the shipping documents is GE, enabling the service provider to call context-dependent service provider 161 with the context “GE.” The context-dependent service provider 161 responds by calling the shipping documents service provider to provide the value help information (e.g. regions in a Germany), which allows the shipping documents service provider to generate value help information for display at user interface 120. Accordingly, context-dependent service provider 161 provides a service that provides value help information to other services or applications—reducing and/or eliminating the need for each of these other services to include their own dedicated value help information.
A user may be any type of user, such as a system designer, a software developer, and/or a processor. User interface 120 may include a browser to provide content from service providers 160-161. In some implementations, SAP Web Dynpro (commercially available from SAP AG, Walldorf, Germany) is used as a model-based development environment for generating user interface 120, although other development environments can also be used.
Network connections 150a-150e may include, alone or in any suitable combination, a telephony-based network, a local area network (LAN), a wide area network (WAN), a dedicated intranet, wireless LAN, the Internet, an intranet, a wireless network, a bus, or any other communication mechanisms. Further, any suitable combination of wired and/or wireless components and systems may provide network connections 150a-150e. Moreover, network connections 150a-150e may be embodied using bi-directional, unidirectional, or dedicated communication links. Network connections 150a-150e may also implement standard transmission protocols, such as Transmission Control Protocol/Internet Protocol (TCP/IP), Hyper Text Transfer Protocol (HTTP), SOAP, RPC, or other protocols.
Server system 130 may include one or more processors, such as computers, to interface with other computers, such as client system 110. Client system 110 may call service manager 140 at server 130. Although service manager 140, service providers 160-161, and repositories 171-172 are depicted within server 130, they can each be located anywhere and distributed among multiple locations.
Moreover, when service manager 140 is called by user interface 120, service manager 140 may call a procedure to instantiate service provider 160. As used herein, the term “instantiate” means, in an object oriented programming environment, an object of a particular class, and, more generally, includes deploying, customizing, running and/or executing an application. Service provider 160 may be implemented as a service which may be called by service manager 140. An example of a service is a Web service, although any other type of application accessible through a network may be used. When service provider 160 is instantiated by service manager 140, service provider 160 may also instantiate one or more corresponding business objects. For example, a user of user interface 120 may access service provider 160 to interact with a product catalog or sales order. The data and methods associated with providing the product catalog or sales order to user interface 120 correspond to a business object. A business object may also include a business object node, which refers to a portion of the business object. In some instances, a business object may be implemented as a data structure including methods and/or procedures associated with that data. Returning to the above product catalog example, a business object node may refer to another object, such as a price or a product description, included within the business object. Business objects and nodes may be stored in a repository, such as repositories 171 or 172.
Repositories 171-172 may be implemented as a storage device for storing information associated with business objects including their metadata. Repositories 171-172 may store information associated with the business objects (e.g., the data and methods associated with the product catalog or sales order) including metadata for the business objects. For example, repositories 171-172 may store a list of business object nodes including an identifier (ID) and data content. The ID of a business object refers to an identifying memory address of a business object node that uniquely identifies individual business object nodes within repositories 171-172. The memory address can be used to access and read data content of a particular business object node. For example, an ID of a business object node may consist of a directory structure and filename associated with the business object node. Repositories 171-172 may be implemented as an enterprise services repository, although any other computer-readable storage medium may be used.
Repositories 171-172 may also store metadata regarding one or more business objects. Metadata may be defined as data about data. For example, metadata may refer to information about the data itself, such as content, quality, condition, origin, size, formatting, characteristics of data, and the like. The eXtensible Markup Language (XML) is a specific example of metadata because it is a format used to define other data objects. Metadata may include a schema. A schema is the organization or structure, such as the organization of a database or the structure of an object in an object oriented program. In object oriented programming, modeling (i.e., the analysis of objects that are used in a business or other context and the identification of the relationships among these data objects) leads to a schema, which can be stored in repositories 171-172 as a schema. The schema can be depicted visually as a structure or a formal text-oriented description (e.g., script). For example, metadata may be in the form of database tables. The metadata may include information such as the number of nodes in a business object, the name(s) of the nodes, the position of a node in the business object hierarchy, the structure of a node, associations, actions, and default queries on a node. An exemplary XML data schema is further described below in relation to
The schema, which depicts business object nodes and how they are associated to one another, may be considered metadata and stored in a repository, such as repository 171. Moreover, the schema may be considered a “model” of how to implement these business object nodes. The model may serve as a template to enable the composition of other models for business objects and their nodes. The models may also be used to generate script for generating code for the business objects and their nodes. The schema may be stored as metadata in repository 171. During the final implementation of system 100, a user would interact (e.g. view, fill-ins, store, and the like) with a service provider to access the business objects (e.g. business objects for a purchase order) stored at the repository 171.
At runtime, the destination address business object node 201d may prompt the user to provide an address. Runtime refers to any time other than when business objects in repositories 171 and 172 are being designed. One of the fields for the destination address that the user may enter is the country code (e.g. GE, USA, GB, etc.). Destination address node 201d depicts the field for the country code as “customer_country” 220. Based on the country code that the user inputs, the destination address business object 201d may determine that context-dependent value help information should be determined by making a call to context-dependent service provider 222. Value help information may be information, such as values, to help a user perform a task (e.g. complete a purchase order). This value help information may be provided based on the context of the information from the user. For example, if the user inputs Germany (“GE”) as the destination country for the purchase order, context-dependent value help information may provide provinces associated with the context of country code (e.g. Germany or GE) determined at runtime. Once the destination address business object node 201d determines that a call to the context-dependent service provider 161 is required, the destination address business object node 198d may call the context-dependent service provider 161 by, for example, sending a Simple Object Access Protocol (SOAP) message or making a Remote Procedure Call to context-dependent service provider 161.
Once the destination address business object node 201d calls the context-dependent service provider 161, the context-dependent service provider 161 receives the call. The call to context-dependent service provider 161 may include information identifying the context of the call. In this case, the call would include runtime information, such as country code GE. Once the call is received, the context-dependent service provider 161 may instantiate one or more corresponding business object nodes that may be stored in repository 172.
Once the context-dependent service provider 161 determines the list of province codes associated with the context, in this case the country code GE (i.e. Germany), the service provider 160 may receive the context-dependent value help information from the context-dependent service provider 161. Once the service provider 160 receives this context-dependent value help information, the service provider 160 may instantiate any additional business objects to incorporate the received context-dependent value help information.
Once the call is received at context-dependent service provider 161, context-dependent service provider 161 may instantiate the business object nodes for the country code 201e for Germany and corresponding regions or province codes 201f (e.g. Baden-Württemberg, Bayern, Berlin, Brandenburg, Bremen, Hamburg, Hessen, Mecklenburg-Vorpommern, Niedersachsen, Nordrhein-Westfalen, Rheinland-Pfalz, Saarland, Sachsen, Sachsen-Anhalt, Schleswig-Holstein, and Thüringen) at step 330. Once the province list is generated by business object node 201f, context-dependent service provider 161 may call service provider 160 to provide the context-dependent information, such as the list of provinces that correspond to the country code Germany at step 340. This call may include the original context, such as “GE,” and the corresponding provinces. The service provider 160 may receive the call from the context-dependent service provider 161 at step 350. Finally, the service provider 160 may incorporate the list of provinces associated the country code Germany at step 360. Once this list is incorporated, the user may be presented with a list of the provinces corresponding to Germany, and the user may select the desired province as part of the destination address.
In this example, the list of provinces depend on the country code that may be entered by the user. Based on the “context” of the country code (e.g. “Germany”), the service provider 160 may receive the call from the context-dependent service provider 161 that includes the list of provinces that correspond to the country code Germany. The above example of context-dependent service provider 161 providing context-dependent value help is only exemplary since service provider 161 may provide any other context-dependent value help information. For example, based on the context of “destination address,” context-dependent service provider 161 may provide a sales order item that contains only the products that can be shipped to that destination address. For example, if the context of “destination address” is only accessible by air, then flammable materials may not be listed in the value help provided by context-dependent service provider 161 to service provider 160 for a sales order. Also, there may be a set quantity of each product that the user may purchase based on the destination address. Context-dependent value help information may thus be used to determine the type of product that may be ordered and the quantity of each product. Moreover, although the context may based on information provided by a user at runtime, any other context may be used. For example, the state or status of the service 160 may be used to determine the context for which value help information should be determined.
At runtime, user interface 120 calls service manager 140. Service manager 140 may call a procedure to instantiate service provider 160. When service provider 160 is instantiated, service provider 160 may also instantiate one more business objects for a sales order. The business objects, which include business object nodes, may be stored in repository 171. For example, business object nodes may exist for a sales order 201a, the sales order items 201b included with sales order 201a, and the corresponding product description 201c. The user may then select one or more products 402 as sales order items. The business object node 201c for the corresponding product description may display the product description 404, and the user may select a desired quantity 406 of the product. The destination address business object node 201d may display entry fields for the user to enter a user name 408, a destination street address 410, and a destination country 412.
When the user enters the destination country 412, destination address business object 201d may determine that context-dependent value help information should be determined. Once the destination address business object node 201d determines that a call to the context-dependent service provider 161 is required (See, e.g.,
Once the context-dependent service provider 161 determines the list of province codes associated with the context, in this case the country code GE (i.e. Germany), the service provider 160 may receive the context-dependent value help information from the context-dependent service provider 161. When the service provider 160 receives this context-dependent value help information, the service provider 160 may instantiate any additional business objects to incorporate the received context-dependent value help information. Once the additional business objects are instantiated, a list of provinces in Germany 414 may be provided to user interface 120 for display so that the user may select the appropriate province for the destination address.
The foregoing description is intended to illustrate but not to limit the scope of the invention, which is defined by the scope of the appended claims. Other embodiments are within the scope of the following claims.
