US20070162492A1 - Reconstruction of historic business object state - Google Patents
Reconstruction of historic business object state Download PDFInfo
- Publication number
- US20070162492A1 US20070162492A1 US11/322,471 US32247105A US2007162492A1 US 20070162492 A1 US20070162492 A1 US 20070162492A1 US 32247105 A US32247105 A US 32247105A US 2007162492 A1 US2007162492 A1 US 2007162492A1
- Authority
- US
- United States
- Prior art keywords
- business object
- change
- platform
- platform change
- general
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
Abstract
A method includes creating a platform change document in a platform change business object in response to detecting a change in a general business object, retrieving the general business object in a current state, applying a change associated with the platform change document from the platform change business object to the general business object to reconstruct the general business object in a historic state. The method further includes enabling a change agent in the general business object.
Description
- Many businesses are now required to keep an audit trail for many aspects of the business. In some instances this need is dictated by accounting practices, such as the general rules for accounting. In other instances, a business needs to keep an audit trail in order to meet legal requirements. For example, the Sarbanes Oaxley Act requires that an audit trail must be kept within a business. The Internal Revenue Service also requires that an audit trail be maintained. In addition, other governmental bodies also require that an audit trail be maintained. In still other instances, there is a need for an audit trail in manufacturing situations. For example, the Federal Food and Drug Administration in the United States requires that an audit trail be kept regarding the manufacture of pharmaceuticals. With such an audit trail, the manufacturer can detect if changes occurred if a portion of a manufactured product was determined to be harmful.
- In some instances, the audit trail may require specific historic documents. A paper trail must be available. Keeping physical documents requires space, an extensive document management plan, and a work force to maintain the document management plan.
-
FIG. 1 is a block diagram of an overall computing environment, according to an example embodiment. -
FIG. 2 is a display of a model of a business object, according to an example embodiment. -
FIGS. 3A, 3B , and 3C formFIG. 3 which is a schematic view of a portion of the computing environment that includes a platform change business object, according to an example embodiment. -
FIG. 4 is a schematic of a portion of a database that includes a plurality of platform change documents in a platform change business object, according to an example embodiment. -
FIG. 5 is a model of a platform change business object, according to an example embodiment. -
FIG. 6 is a flow diagram of a method for producing a platform change business object, according to an example embodiment. -
FIG. 7 is a flow diagram of a method for reconstruction of a historical state of a business object, according to an example embodiment. -
FIG. 8 is a flow diagram of a method for querying a first platform change business object and a second platform change business object, according to an example embodiment. -
FIG. 9 is a flow diagram of another method for producing a platform change business object, according to an example embodiment. -
FIG. 10 is a schematic of a computer system that executes programming, according to an example embodiment. - In the following description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments which may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that structural, logical and electrical changes may be made without departing from the scope of the present invention. The following description is, therefore, not to be taken in a limited sense, and the scope of the present invention is defined by the appended claims.
- The functions or algorithms described herein are implemented in software or a combination of software and human implemented procedures in one embodiment. The software comprises computer executable instructions stored on computer readable media such as memory or other type of storage devices. The term “computer readable media” is also used to represent carrier waves on which the software is transmitted. Further, such functions correspond to modules, which are software, hardware, firmware or any combination thereof. Multiple functions are performed in one or more modules as desired, and the embodiments described are merely examples. The software is executed on a digital signal processor, ASIC, microprocessor, or other type of processor operating on a computer system, such as a personal computer, server or other computer system.
-
FIG. 1 is a block diagram of acomputing system 100, according to an example embodiment. Thecomputing environment 100 includes auser interface 110, anapplication program level 120 and a comprehensive integration andapplication platform layer 130. The comprehensive integration and application platform layer works with an existing infrastructure to enable and manage change. The comprehensive integration andapplication platform 130 includes a plurality of business applications, known as business components, which reduce the need for custom integration. The comprehensive integration and application platform includes abusiness component application platform 130 also includes abusiness component 200, which includes various integration tools for performing business analysis on business information within thecomputing environment 100. Theapplication program layer 120 also includes a number ofdistributed objects object -
FIG. 2 is a display of amodel 200 of a business object, such asbusiness object 121, according to an example embodiment. A business object or object has a structure that includes aroot 210, nodes such asnodes sub node 230. Associated with a business or aroot 210 is a grouping of information related to the business object root orroot 210. Some of the information is held in fields such as 211 and 212. The information is also held in anode 220 which in turn also represents a grouping of information such as data and logic which are held infields root 210 andnode 220 is asub node 230.Sub node 230 holds another grouping of information that includes data and logic that are held infields business object 200 also includes anothernode 240. Node 240 is at the same level asnode 220 and includes another grouping of data and logic which includesfield 241. Therefore, it is seen thatobject 200 orbusiness object 200 has a structure which includes aroot 210, nodes, such asnodes sub node 230. It should be noted thatFIG. 2 shows a simplified example of the structure of an object orbusiness object 200. In actuality, a business object orobject 200 may have a more complex structure. However, the principles as set forth inFIG. 2 will be followed where each root, node and/or sub node includes a grouping of information that can include data and logic. - In some embodiments, the structure of the business object or an outline of the business object is used to form a model of the
business object 200. A model is useful for the purposes of designing and programming in a business object, such asbusiness object 200. A model of thebusiness object 200 shows the structure. In some embodiments, the model is referred to as a template. A template or model can take on any form just so it shows the structure of the object orbusiness object 200. As shown inFIG. 2 , the template is formed on a spreadsheet, such as an Excel spreadsheet. Excel is a registered trademark of Microsoft Corporation. -
FIGS. 3A, 3B and 3C formFIG. 3 which is a schematic view of a portion of acomputing environment 300 that includes auser interface 310, abusiness object 320, and a platformchange business object 340. The portion of thecomputing environment 300 also includes achange document agent 336 which is associated with thebusiness object 320. Thebusiness object 320 includes an interface to theuser interface 310. Through theuser interface 310, various images from aBO image module 321 may be viewed. Thebusiness object 320 also includes processes or methods fordocument mapping 322, call backmapping 323, retrieving before and afterimages 324, and for providingadditional data 325. Thebusiness object 320 also includes a switch or enablement device for enabling thechange document agent 336. When enabled, thechange document agent 336 detects changes in thebusiness object 320 and signals the platformchange business object 340 of those changes. The platform change business object creates a platform change document in response to the change document agent detecting a change in thebusiness object 320. Thechange document agent 336 alerts a createprocess 341 within the platformchange business object 340. The createprocess 341 creates a platform change document in a portion of adatabase 350 which is controlled or within the platformchange business object 340. - The platform
change business object 340 also includes a process for deletinginformation 342, a method or process for retrievinginformation 343, a method for retrieving byassociation 344, a method for querying 345, and a method forreconstruction 346. The portion of thedatabase 350 also includes a method forcreation 351, a method fordeletion 352, a method or process for retrieving 353, and a method for querying 355. The method to retrieve byassociation 344 is connected to the method to retrieve 353 found in the portion of thedatabase 350. The database portion of the platformchange business object 340 also includes a call backagent 358 for obtaining additional information from thebusiness object 320. Thus, in operation when theswitch 330 is enabled to enable thechange document agent 336, changes in thebusiness object 320 are detected and in response to the detected changes, a platform change document is created in the platformchange business object 340. Specifically, thechange document agent 336 calls a createprocess 341 within the platform change business object which in turn enables the platform change document to be created in thedatabase 350 or portion of thedatabase 350 associated with the platformchange business object 340. - The portion of the
computing environment 300 also includes atransaction manager 370. Thetransaction manager 370 includes services that interact with theuser interface 310. Such services include a retrieveprocess 373, a retrieve byassociation process 374 and aquery process 375. Thetransaction manager 370 also includes other services that may be provided in the future or may be provided for interacting with theuser interface 310 in other systems. Thetransaction manager 370 also includes a modifyingmethod 379 that interacts with the createmethod 341 and the delete method orprocess 342 of the platformchange business object 340. It should be noted that thebusiness object 320 may be referred to as a general business object since it is not specific to any particular application process or information but is applicable to any business object in a computer system such as system 100 (seeFIG. 1 ). -
FIG. 4 is a schematic of a portion of adatabase 350 that includes a plurality ofplatform change documents business object 320, a platform change object is produced and stored in thedatabase portion 350 of the platformchange business object 340. Thus, there may be n number of changes that occur since the change document agent 336 (seeFIG. 3 ) is enabled. It should be noted that some business objects or in some systems thechange document agent 336 is enabled at the time of production of the system. In other words, an end user would have to disable thechange document agent 336. In the absence of disabling thechange document agent 336, thechange document agent 336 will create platform change documents, such as 411, 412, 413, 490 in a portion of thedatabase 350 of the platformchange business object 340. - Platform change documents are maintained as a business object.
FIG. 5 is amodel 500 of a platformchange business object 340, according to an example embodiment. The platform change documents object includes afirst node 510 and asecond node 520. Thefirst node 510 contains or carries the header attributes. Thesecond node 520 carries the item attributes. The header node or thefirst node 510 contains the header, and respective root node of the platform change documents business objects and also provides the following elements: -
- ChangeDocumentID=GUID which identifies a Platform Change Document
- BOName=Name respectively type of the Business Object which was changed
- ObjectID=Identifier of the instance of the Business Object which was changed
- UserName=Name of the Individual who changed the Business Object instance
- ChangeDateTime=Date and Time of the Change in UTC
- TransactionName=Name of the transaction which was used to change the Business Object instance
- TransactionID=Identifier of the instance of the transaction which was used to change the Business Object instance
- PlatformChangeDocumentitem is the item of a Platform Change Document. For every element which was changed in a Business Object instance, one PlatformChangeDocumentitem node is created. It provides the following elements:
-
- ChangeDocumentItemID=GUID which identifies the item of a Platform Change Document
- BONodeName=Node of the Business Object which contains the element whose instance was changed
- ObjectItemID=Identifier of the Node
- BONodeElementName=Name of the element whose instance was changed
- Modification TypeCode=Defines whether the Business Object Instance was Created, Updated or Deleted
- BONodeElementOldValue=Old Value of the instance of the element which was changed. This field is only used if the corresponding field in the BO is a value field with a currency code assigned
- BONodeElementOldQuantity=Old Value of the instance of the element which was changed. This field is only used if the corresponding field in the BO is a value field with a currency code assigned
- BONodeElementOldText=Old Value of the instance of the element which was changed. This field is used for all other data types. For convenience of the Business Objects, also the value of BONodeElementOldValue or BONodeElementOldQuantity is copied into BONodeElementOldText
- BONodeElementNewValue=New Value of the instance of the element which was changed. This field is only used if the corresponding field in the BO is a value field with a currency code assigned.
- BONodeElementNewQuantity=New Value of the instance of the element which was changed. This field is only used if the corresponding field in the BO is a quantity field with a Unit of Measure code assigned.
- BONodeElementNewText=New Value of the instance of the element which was changed. This field is used for all other data types. For convenience of the Business Objects, also the value of BONodeElementOldValue or BONodeElementOldQuantity is copied into BONodeElementOldText.
- ChangeReasonCode=Reason for the change
- A
system 300 includes ageneral business object 320, a platformchange business object 340, and achange agent 336 associated with thegeneral business object 320 that detects a change in thegeneral business object 320 and creates aplatform change document 500 in the platformchange business object 340. Thechange agent 336 automatically creates aplatform change document 500 in the platform changedocument business object 340 in response to detecting a change in thegeneral business object 320. Thesystem 300 is an enablement device, such as aswitch 330. Theenablement device 330 enables thechange agent 336 to automatically create aplatform change document 500 in the platformchange business object 310 in response to detecting a change in thegeneral business object 320. Thesystem 300 can also include a transaction control ortransaction manager 370. In one embodiment, theenablement device 330 acts through thetransaction control 370. The platformchange business object 340 includes a change time and a change date and other attributes as discussed with respect toFIG. 5 . Theplatform change document 500 in the platformchange business object 340 tracks the changes to thegeneral business object 320. The platformchange business object 340 includes acallback agent 358 to enable the callback agent to populate the platformchange business object 340 with selected attributes. - A platform change apparatus includes a mechanism for detecting changes in a
general business object 320 and automatically recording the changes in a platformchange business object 340. The platformchange business object 340 includes aplatform change document 500 related to a change in thegeneral business object 320. The platformchange business object 340 stores the changes to thegeneral business object 320. Thesystem 300 also includes a reconstruction device orreconstruction process 346 that retrieves thegeneral business object 320 in a current state and applies changes made to thegeneral business object 320 and recorded in the platformchange business object 340 to the retrieved current state to reconstruct thegeneral business object 320 in a desired historic state. Thechange agent 336 of thesystem 300 automatically creates a platform change document in the platform changedocument business object 340 in response to detecting a change in thegeneral business object 220. Theplatform change document 500 includes the changes made at a selected time. The call back system oragent 358 retrieves additional information from thegeneral business object 320 which, in some embodiments, is used to create a previous state of thegeneral business object 320. -
FIG. 6 is a flow diagram of amethod 600 for producing a platformchange business object 614, according to an example embodiment. Themethod 600 includes enabling a change agent associated with ageneral business object 610, detecting a change with thechange agent 612, and creating a platform change document in a platform change business object in response to detecting a change in thegeneral business object 614. Detecting achange 612 and creating a platform change document in a platformchange business object 614 is done automatically. Creating a platform change document in a platformchange business object 614 includes placing transaction identifying information in the platform change document, indicating a type of modification in the platform change document, placing old information in the platform change document, placing new information in the platform change document, placing a date associated with a change in the platform change document, and placing comments for the change in the platform change document. Other items can also be changed or noted in the createdplatform change document 500. In addition, the call back agent 358 (seeFIG. 3 ), in some embodiments, will call back to thegeneral business object 320 to obtain further attributes associated with thegeneral business object 320. -
FIG. 9 is a flow diagram of anothermethod 900 for producing a platform change business object that includes platform change documents, according to another example embodiment. Themethod 900 includes enabling thechange agent 910, and processing thechange notification 912. The change mode is determined as depicted bydecision box 914. If the change is a create type of change, themethod 900 includes retrieving the after image of theinstance 916, and preparing theplatform change documents 918 and storing the change documents in adatabase 920. A platform change business object, in one example embodiment, controls the storage of the platform change documents in the database. If the change mode is an update type of change, themethod 900 includes retrieving the before and after image of theinstance 930, detecting the changes of the attribute valudes of theinstance 932, and preparing theplatform change documents 934 and storing the change documents in adatabase 920. If the change is a delete type of change, themethod 900 includes retrieving the before image of theinstance 940, and preparing theplatform change documents 942 and storing the change documents in adatabase 920. -
FIG. 7 is a flow diagram of amethod 700 for reconstruction of a historical state of a business object, according to an example embodiment. Themethod 700 includes creating a platform change document in a platform change business object in response to detecting a change in ageneral business object 710, retrieving the general business object in acurrent state 712, applying a change associated with the platform change document from the platform change business object to the general business object to reconstruct the general business object in ahistoric state 714. Themethod 700 further includes enabling a change agent in thegeneral business object 710. Applying the change associated with the platform change document in a platform change business object includes applying a plurality of changes in an order where the latest change is first applied. In some embodiments, applying the change associated with the platform change document in a platform change business object includes applying a plurality of changes in a reverse time order. Themethod 700 also includes querying the platformchange business object 718. The query can includes a general business object name, a user name, a date timestamp, and the like. The method also includes querying the platform change business object and querying the general business object with the same query system. In some embodiments, the platform change business object includes a call back agent orsystem 358 that retrieves additional data from thegeneral business object 320. - The platform
change business object 340 is structured and modeled in the same fashion as any other business object in the computing environment 100 (seeFIG. 1 ). As a result, the systems and processes that apply to any object or business object in the computing environment 100 (seeFIG. 1 ) also applies to the platform changedocuments business object 340. For example, the platformchange business object 340 can be queried using thequery process 375 in the transaction manager as well as thequery process 345, which is found in the platformchange business object 340. The queries can be made through theuser interface 310. Queries can include the querying of a platform change document based upon the business object name, the outcome of the object ID, the user name of the person who made the change, the changed date, time, the transaction name or a transaction ID. In other words, all of the elements in the header node 510 (seeFIG. 10 ) can be used to form a query. It should also be noted that several business objects may have their change document agent, such aschange document agent 336, enabled. In this particular instance, then a platformchange business object 340 could include platform change documents from one of several business objects or one of several general business objects. Again, thequerying process change business object 340. -
FIG. 8 is a flow diagram of amethod 800 for querying a first platform change business object and a second platform change business object, according to an example embodiment. Themethod 800 includes creating a first platform change document in a first platform change business object in response to detecting a change in a firstgeneral business object 810, creating a second platform change document in a second platform change business object in response to detecting a change in a secondgeneral business object 812, and querying the first platform change business object and the second platform change business object using thesame querying system 814. The querying system can also be used to query a first business object and a second business object. Themethod 800 also includes retrieving at least one of the first general business object or the second general business object in acurrent state 816. The method also includes applying the change documents from at least one of the first platform change business object or the second platform change business object to the current state in reverse order to reconstruct the general business object in ahistoric state 818. - A block diagram of a
computer system 2000 that executes programming for performing the above algorithm is shown inFIG. 9 , according to an example embodiment. A general computing device in the form of acomputer 2010, may include aprocessing unit 2002,memory 2004,removable storage 2012, andnon-removable storage 2014.Memory 2004 may includevolatile memory 2006 andnon-volatile memory 2008.Computer 2010 may include—or have access to a computing environment that includes—a variety of computer-readable media, such asvolatile memory 2006 andnon-volatile memory 2008,removable storage 2012 andnon-removable storage 2014. Computer storage includes random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM) & electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD ROM), Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium capable of storing computer-readable instructions.Computer 2010 may include or have access to a computing environment that includesinput 2016,output 2018, and acommunication connection 2020. The computer may operate in a networked environment using a communication connection to connect to one or more remote computers. The remote computer may include a personal computer (PC), server, router, network PC, a peer device or other common network node, or the like. The communication connection may include a Local Area Network (LAN), a Wide Area Network (WAN) or other networks. - Computer-readable instructions stored on a computer-readable medium are executable by the
processing unit 2002 of thecomputer 2010. A hard drive, CD-ROM, and RAM are some examples of articles including a computer-readable medium. For example, acomputer program 2025 capable of providing a generic technique to perform access control check for data access and/or for doing an operation on one of the servers in a component object model (COM) based system according to the teachings of the present invention may be included on a CD-ROM and loaded from the CD-ROM to a hard drive. The computer-readable instructions allowcomputer system 2000 to provide generic access controls in a COM based computer network system having multiple users and servers. - A machine-readable medium including a set of instructions that, when executed by a machine, perform a method that includes enabling a change agent associated with a
general business object 610, detecting a change in the general business object with thechange agent 612, and creating a platform change document in a platform change business object in response to detecting a change in thegeneral business object 614. - A machine-readable medium including a set of instructions that, when executed by a machine, perform the method that includes creating a platform change document in a platform change business object in response to detecting a change in a
general business object 710, retrieving the general business object in acurrent state 712, applying a change associated with the platform change document from the platform change business object to the general business object to reconstruct the general business object in ahistoric state 714. - A machine-readable medium including a set of instructions that, when executed by a machine, perform the method that includes creating a first platform change document in a first platform change business object in response to detecting a change in a first
general business object 810, creating a second platform change document in a second platform change business object in response to detecting a change in a secondgeneral business object 812, and querying the first platform change business object and the second platform change business object using thesame querying system 814. - The Abstract is provided to comply with 37 C.F.R. §1.72(b) to allow the reader to quickly ascertain the nature and gist of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.
Claims (20)
1. A method comprising:
creating a platform change document in a platform change business object in response to detecting a change in a general business object;
retrieving the general business object in a current state;
applying a change associated with the platform change document from the platform change business object to the general business object to reconstruct the general business object in a historic state.
2. The method of claim 1 further comprising enabling a change agent in the general business object.
3. The method of claim 1 wherein applying the change associated with the platform change document in a platform change business object includes applying a plurality of changes in an order where the latest change is first applied.
4. The method of claim 1 wherein applying the change associated with the platform change document in a platform change business object includes applying a plurality of changes in a reverse time order.
5. The method of claim 1 further comprising querying the platform change business object.
6. The method of claim 5 wherein the query includes a general business object name.
7. The method of claim 5 wherein the query includes a user name to allow viewing change documents related to a general business object made by the user.
8. The method of claim 5 wherein the query includes a date timestamp.
9. The method of claim 1 further comprising querying the platform change business object and querying the general business object with the same query system.
10. The method of claim 1 wherein the platform change business object includes a call back system that retrieves additional data from the general business object.
11. A machine-readable medium including a set of instructions that, when executed by a machine, perform the method of claim 1 .
12. A system comprising:
a general business object;
a platform change business object; and
a reconstruction device that retrieves the general business object in a current state and applies changes made to the general business object and recorded in the platform change business object to the retrieved current state to reconstruct the general business object in a desired historic state.
13. The system of claim 12 further comprising a change agent automatically creates a platform change document in the platform change document business object in response to detecting a change in the general business object.
14. The system of claim 12 further comprising a call back system for retrieving additional information from the general business object.
15. The system of claim 14 wherein the additional information from the general business object is used to create a previous state of the general business object.
16. A method comprising:
creating a first platform change document in a first platform change business object in response to detecting a change in a first general business object;
creating a second platform change document in a second platform change business object in response to detecting a change in a second general business object; and
querying the first platform change business object and the second platform change business object using the same querying system.
17. The method of claim 16 wherein the querying system can also be used to query a first business object and a second business object.
18. The method of claim 16 further comprising retrieving at least one of the first general business object or the second general business object in a current state.
19. The method of claim 16 further comprising applying the change documents from at least one of the first platform change business object or the second platform change business object to the current state in reverse order to reconstruct the general business object in a historic state.
20. A machine-readable medium including a set of instructions that, when executed by a machine, perform the method of claim 16.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/322,471 US20070162492A1 (en) | 2005-12-30 | 2005-12-30 | Reconstruction of historic business object state |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/322,471 US20070162492A1 (en) | 2005-12-30 | 2005-12-30 | Reconstruction of historic business object state |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070162492A1 true US20070162492A1 (en) | 2007-07-12 |
Family
ID=38233945
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/322,471 Abandoned US20070162492A1 (en) | 2005-12-30 | 2005-12-30 | Reconstruction of historic business object state |
Country Status (1)
Country | Link |
---|---|
US (1) | US20070162492A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070214034A1 (en) * | 2005-08-30 | 2007-09-13 | Michael Ihle | Systems and methods for managing and regulating object allocations |
CN107967554A (en) * | 2017-11-15 | 2018-04-27 | 金华市公安局交通警察支队 | The alert doctor's postal Trinity convenience service platform of one kind and method |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030058277A1 (en) * | 1999-08-31 | 2003-03-27 | Bowman-Amuah Michel K. | A view configurer in a presentation services patterns enviroment |
US20030105761A1 (en) * | 2001-11-21 | 2003-06-05 | Mikael Lagerman | Historic network configuration database |
US6584467B1 (en) * | 1995-12-08 | 2003-06-24 | Allstate Insurance Company | Method and apparatus for obtaining data from vendors in real time |
US20030140058A1 (en) * | 2002-01-18 | 2003-07-24 | Vitria Technology, Inc. | Method and apparatus for sharing information between applications using common objects |
US6615209B1 (en) * | 2000-02-22 | 2003-09-02 | Google, Inc. | Detecting query-specific duplicate documents |
US6658423B1 (en) * | 2001-01-24 | 2003-12-02 | Google, Inc. | Detecting duplicate and near-duplicate files |
US20040039720A1 (en) * | 2001-12-31 | 2004-02-26 | Hodges Donna K. | Method for providing platform independent business rules |
US6839702B1 (en) * | 1999-12-15 | 2005-01-04 | Google Inc. | Systems and methods for highlighting search results |
US20050066306A1 (en) * | 2003-09-24 | 2005-03-24 | Salleh Diab | Direct deployment of a software application from code written in tables |
US20050234942A1 (en) * | 2004-04-13 | 2005-10-20 | Bea Systems, Inc. | System and method for content and schema lifecycles |
US7043488B1 (en) * | 2000-01-21 | 2006-05-09 | International Business Machines Corporation | Method and system for storing hierarchical content objects in a data repository |
US7072934B2 (en) * | 2000-01-14 | 2006-07-04 | Saba Software, Inc. | Method and apparatus for a business applications server management system platform |
US7089583B2 (en) * | 2000-01-14 | 2006-08-08 | Saba Software, Inc. | Method and apparatus for a business applications server |
US20060184569A1 (en) * | 2005-02-16 | 2006-08-17 | Michael Aakolk | Data processing systems and methods |
US20060282458A1 (en) * | 2005-04-22 | 2006-12-14 | Igor Tsyganskiy | Methods and systems for merging business process configurations |
US7243103B2 (en) * | 2002-02-14 | 2007-07-10 | The Escher Group, Ltd. | Peer to peer enterprise storage system with lexical recovery sub-system |
US7246254B2 (en) * | 2003-07-16 | 2007-07-17 | International Business Machines Corporation | System and method for automatically and dynamically optimizing application data resources to meet business objectives |
-
2005
- 2005-12-30 US US11/322,471 patent/US20070162492A1/en not_active Abandoned
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6584467B1 (en) * | 1995-12-08 | 2003-06-24 | Allstate Insurance Company | Method and apparatus for obtaining data from vendors in real time |
US20030058277A1 (en) * | 1999-08-31 | 2003-03-27 | Bowman-Amuah Michel K. | A view configurer in a presentation services patterns enviroment |
US6839702B1 (en) * | 1999-12-15 | 2005-01-04 | Google Inc. | Systems and methods for highlighting search results |
US7089583B2 (en) * | 2000-01-14 | 2006-08-08 | Saba Software, Inc. | Method and apparatus for a business applications server |
US7072934B2 (en) * | 2000-01-14 | 2006-07-04 | Saba Software, Inc. | Method and apparatus for a business applications server management system platform |
US7043488B1 (en) * | 2000-01-21 | 2006-05-09 | International Business Machines Corporation | Method and system for storing hierarchical content objects in a data repository |
US6615209B1 (en) * | 2000-02-22 | 2003-09-02 | Google, Inc. | Detecting query-specific duplicate documents |
US6658423B1 (en) * | 2001-01-24 | 2003-12-02 | Google, Inc. | Detecting duplicate and near-duplicate files |
US20030105761A1 (en) * | 2001-11-21 | 2003-06-05 | Mikael Lagerman | Historic network configuration database |
US20040039720A1 (en) * | 2001-12-31 | 2004-02-26 | Hodges Donna K. | Method for providing platform independent business rules |
US20030140058A1 (en) * | 2002-01-18 | 2003-07-24 | Vitria Technology, Inc. | Method and apparatus for sharing information between applications using common objects |
US7243103B2 (en) * | 2002-02-14 | 2007-07-10 | The Escher Group, Ltd. | Peer to peer enterprise storage system with lexical recovery sub-system |
US7246254B2 (en) * | 2003-07-16 | 2007-07-17 | International Business Machines Corporation | System and method for automatically and dynamically optimizing application data resources to meet business objectives |
US20050066306A1 (en) * | 2003-09-24 | 2005-03-24 | Salleh Diab | Direct deployment of a software application from code written in tables |
US20050234942A1 (en) * | 2004-04-13 | 2005-10-20 | Bea Systems, Inc. | System and method for content and schema lifecycles |
US20060184569A1 (en) * | 2005-02-16 | 2006-08-17 | Michael Aakolk | Data processing systems and methods |
US20060282458A1 (en) * | 2005-04-22 | 2006-12-14 | Igor Tsyganskiy | Methods and systems for merging business process configurations |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070214034A1 (en) * | 2005-08-30 | 2007-09-13 | Michael Ihle | Systems and methods for managing and regulating object allocations |
CN107967554A (en) * | 2017-11-15 | 2018-04-27 | 金华市公安局交通警察支队 | The alert doctor's postal Trinity convenience service platform of one kind and method |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP3887564B2 (en) | Integrated database combination system | |
US8095618B2 (en) | In-memory caching of shared customizable multi-tenant data | |
US7836080B2 (en) | Using an access control list rule to generate an access control list for a document included in a file plan | |
US8150803B2 (en) | Relationship data management | |
US7523121B2 (en) | Relationship data management | |
US6363388B1 (en) | Apparatus and system for an adaptive data management architecture | |
US8131560B2 (en) | Systems and methods for managing regulatory information | |
US7634508B2 (en) | Processing of duplicate records having master/child relationship with other records | |
JP2011081828A (en) | System and method for integrating, managing and coordinating customer activities | |
WO2007002686A9 (en) | Method and apparatus for data integration and management | |
US20060004597A1 (en) | Method and system for grouping events | |
US11163834B2 (en) | Filtering collaboration activity | |
WO2007081666A2 (en) | Relationship data management | |
US20080005143A1 (en) | Methods and apparatus for automatically creating composite configuration items in configuration management database | |
US20130346426A1 (en) | Tracking an ancestry of metadata | |
US10424005B2 (en) | Methods, systems, and computer readable media for managing order processing and fallout in an order management system | |
US7325003B2 (en) | Method and system for mapping datasources in a metadata model | |
US8214410B2 (en) | Conflict management in a versioned file system | |
US20030055672A1 (en) | Method of defining functional configuration of business application system | |
US20120109698A1 (en) | Logical chart of accounts with hashing | |
US20070162492A1 (en) | Reconstruction of historic business object state | |
US20070156776A1 (en) | Change documents and method | |
US20100011019A1 (en) | Database Business Components Code Generator | |
US20230054316A1 (en) | Retrieval of unstructured data in dpp information access | |
US20070022137A1 (en) | Data source business component generator |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAP AG, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VASING, KRITESH;PIELKA, KAI UWE;REEL/FRAME:017442/0245 Effective date: 20060314 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |