CA2332938C - Cross application time sheet - Google Patents
Cross application time sheet Download PDFInfo
- Publication number
- CA2332938C CA2332938C CA002332938A CA2332938A CA2332938C CA 2332938 C CA2332938 C CA 2332938C CA 002332938 A CA002332938 A CA 002332938A CA 2332938 A CA2332938 A CA 2332938A CA 2332938 C CA2332938 C CA 2332938C
- Authority
- CA
- Canada
- Prior art keywords
- data
- time
- time entry
- database
- entry data
- 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.)
- Expired - Lifetime
Links
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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06313—Resource planning in a project environment
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C1/00—Registering, indicating or recording the time of events or elapsed time, e.g. time-recorders for work people
- G07C1/10—Registering, indicating or recording the time of events or elapsed time, e.g. time-recorders for work people together with the recording, indicating or registering of other data, e.g. of signs of identity
-
- 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06312—Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
-
- 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
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1091—Recording time for administrative or management purposes
Abstract
The invention relates to a multi-application time sheet system. Said system comprises a first interface for reproducing an employee identification query. In this system, a work list is checked to select a data acquisition image and verification is carried out to determine whether the time acquisition data is complete. Said system also comprises a data bank for storing the time acquisition data, a sub-system for obtaining authorisation for a part of the time acquisition data, and another interface for storing the time acquisition data in tables. In order to process the time acquisition data, the employee identification query is first reproduced and subsequently received. An input data mask is selected and represented according to the employee identification data. The individual time data stored for individual employees is accepted and verification is carried out to determine whether it is complete. The acquired time data is stored in a data bank and can be stored in tables after an access authorisation has been obtained, for instance for a part of the acquired time data. Said time acquisition data stored in tables is received for further analysis by means of known applications.
Description
Cross Application Time Sheet Background of the Invention Organizations are finding it increasingly difficult to compete in the international marketplace as markets become more global. The increasing competition in many areas of manufacturing, commerce, services, and other forms of busiriess leads to sinking market prices, which in turn causes profit margins to decrease. Meanwhile, rapidly changing technologies lead to greater automation, which increases efficiency and allows corporations to produce more with fewer employees.
This also requires the use of human resources to be optimized in order to reduce costs. Methods of tracking costs associated.with raw material, machinery, rent, shipping and the like are in existence and are being constantly further improved. There is a need to identify and allocate working time spent by employees and contract workers, in order to improve upon the methods used for human resource allocation, verification, approval and planning.
Information on when an ernployee has performed work and for what reason is important for different areas of the organization, such as personnel administration, logistics, and accounting. A uniform record of hours worked wou:Ld allow a great simplification of the work flow in the organization.
Presently, time sheet entries and processing are often done on a micro-level. Time entries inputted by employees in a department are added together by project or by division, and management receives a weekly or monthly report that does little rnore than provide the totals for that particular department. GJhen a project involves several departments working on diverse aspects of the project, it is often difficult to ascertain the total time spent by the various individuals and the costs associated with that time. Very often a given individual may spend a certain number of hours accomplishing a particular task that provides benefits to several projects, in which case it is difficult to accurately determine each project's share of the benefit. For example, a salesperson working for a large corporation may take several trips to visit a customer's facilities. The time spent on such trips, as well as time spent building and maintaininq relationships may be difficult to track in the first place, let alone accurately assign to various projects in which the customer is involved. Similarly, a researcher may discover a method of improving efficiency in a manufacturing process that may be applied to several ongoing projects. As another example, an individual working in the Information Services department of the organization may spend various amounts of time on different projects such as system rnaintenance, upgrading computers for individuals across several departments.
Furthermore, it would be efficient from the organization's point of view to have various departments in the organizations view the time entries of the above individuals. For example, a project manager may wish to determine whether there are enough people working on the project and whether those people are allocating sufficient time for it. Human resources may want to ascertain that employees are correctly allocated to various projects, to determine whether more employees with particular qualifications need to be hired.
Accounting would need to add up the costs associated with different projects to ensure that there are no overruns.
_ 3 _ Presently, there is a need for a system to track time sheet information and compile data for such various applications, without utilizing a complex network of links to coordinate and distribute data. It would be advantageous to have an effective method of tracking time entries and compiling time sheet information to provide information on internal employees' and external service providers' working times for a variety of applications.
Summary of the Invention The present invention relates to a method and system for compiling time entry data in a common or joint data pool and providing the data to multiple applications. By combining data and storing it in one central system, the data may be asynchronously distributed, either automatically c>r on a needed basis.
A transparent system allows additional processing, such as verification and approval, of separate portions of the data pool before the data is distributed.
Corrections or updates to the data are automatically forwarded to the relevant applications.
An object of the invention is to provide a novel method of compiling time entry data from a variety of sources in a data pool and providing the data to several applications.
Another object of the invention is to monitor time entry data and the information derived from them.
Another object of the invention is to improve transparency in the sharing of time entry data across applications.
Another object of the invention is to automatically and asynchronously distribute compilations of time entry data.
Another object of the invention is to apply asynchronous processing on time entry data to be distributed to several applications.
Another object of the invention is to automatically forward corrected or updated time entry data to several applications.
Detailed Description of the Invention Introduction The present invention allows time entries to be managed in an efficient manner through the centralization and subsequent distribution of relevant data.
The present invention was developed as a standardized, cross-application tool of the SAP R13 System. A brief description of the R/3 System follows.
R/3 can be described primarily as an online transaction processing system designed to provide integrated processing of all business routines and transactions. It includes enterprise-wide, integrated solutions, as well as specialized applications for individual, departmental functions. R/3 mirrors all of the business-critical processes of the enterprise -finance, manufacturing, sales, and human resources. It also offers various analytical capabilities to supplement the transaction process_Lng function.
Recent paradigm shifts have forced companies to optimize all business processes along the net-value-added chain through the use of modern data processing and enterprise-wide information management. In order to become successful, companies often network with customers and suppliers such that products and services of high quality can be made available with minimal delay in response to customer demands. R/3 achieves these goals with online integration of data in the company.
The R/3 System is based on the client/server architecture which separates the database, application, and presentation components for greater flexibility.
This enables enterprises to take advantage of the various benefits of the architecture, including the capability to run across a variety of today's most popular UNIX-based hardware platforms. The R/3 System is designed so that the application systems and system functions are decoupled by a clear layer of architecture, with an applicatiori layer and a basis layer. The multilayer architecture of the R/3 System allows optimal load distribution, even in large installations with thousands of users. It has a modular structure with methods for controlling master-slave relationships between individual software components.
Special servers linked by communications networks can be used for certain tasks without losing the integration of data and processes in the overall system. Implementation of separate servers for particular tasks makes optimal use of the performance potential and the different cost structures of available hardware architecture. This allows applications to be partitioned into different services and run on different servers. The fundamental services of the R/3 system (graphical presentation services, application services for handling of the application logic, database services for sto:rage and recovery of business data, etc.) are partitioned and may evolve separately while maintaining interoperability.
The present invention is contemplated for use in conjunction with several applications of the SAP R/3 System, namely Controlling, Persoi:-inel Time Management, Service Management, Plant Maintenance, Project System, and External Services (part of Materials Management).
The invention may be practiced using different hardware and operating system platforms. The invention as described operates as a module of a larger system.
The following descriptio:n is of the best presently contemplated mode of car:rying out the present invention. This description is not to be taken in a limiting sense but is made merely for the purpose of describing the general principles of the invention.
Overview The cross application time sheets ("CATS") system is a system that allows personal time sheet records to be entered for individuals performing duties for an organization. In a preferred embodiment, such time sheet records may be associated with the organization's own employees (internal employees) or outsiders, such as contractors or consultants (external employees), collectively referred to as "employees", wherein each employee is assigned an employee number in the system (the records of CATS data are always related to individuals). Also in a preferred embodiment, administrators may enter the working time of all employees assigned to them.
The invention is explained in more detail below with the aid of particularly preferred exemplary embodiments illustrated in figures, in which:
Fig. 1 is a flowchart rep.resenting an overview of the process utilized by CATS.
Fig. 2 is a flowchart providing a more detailed representation of the entering of raw data into a database.
Fig. 3 is an example of a preferred embodiment of a request screen.
Fig. 4 is an example of a, preferred embodiment of a data entry screen.
Fig. 5 is another exarrple of a preferred embodiment of a data entry screen.
Fig. 6 is an example of a. preferred embodiment of a travel data entry screen.
Fig. 7 is an example of a. preferred embodiment of a goods issue screen.
Fig. 8 is a flowchart providing a more detailed representation of authorizations ar.Ld approvals.
Fig. 9 is a flowchart providing a more detailed representation of transfer of data that initially requires approval.
Referring to Fig. 1, flowchart 1 represents an overview of the process utilized by CATS. The amount of time that work 10 is performed by employees is either recorded directly on the system using CATS interface 20 or through a time sheet 15 that is subsequently recorded in a recording office using CATS interface 20. In preferred embodiments of the invention, the recording office may be at one physical location, or may be a "virtual" office that is distributed across a network. A
user accessing the system, not shown in the figures, may perform checks with applicatioris 30, which in a preferred embodiment include Personnel Time Management 31, External Services 32, Project System 33, Controlling 34, Plant Maintenance 35, and Service Management 36.
These checks include checking the work list while in the request mode, and verifying information in the data entry mode (described in more detail below). In a preferred embodiment, customer-specific enhancements may be applied using user exit 40.
Data is subsequently passed on to database 50 for storage. From database 50 it is possible to report 55 the data. Depending on the customized settings of the system, approval of the data by an authorized individual may be required. If no approval is required, the data is passed to interface database 70. If approval for any portion of the data is required, business workflow selection process 60 determines the type of approval and authorization that is required, arid approval process /
authorization procedure 65 commences. If any adjustments or corrections to the time sheet data is made during approval process / authorization procedure 65, the adjusted or corrected data is sent back to database 50.
On the other hand, data that is approved and requires no adjustments or corrections is passed to interface database 70. Interface database 70 stores data that is passed via data transfer 75 to one or more applications within applications 30.
Entering, Saving and Releasing Data The type of data entered comprises working times together with information that is relevant to further processing and evaluation of data in various areas of the system. By way of example only, the information can relate to documenting the progress of an order in the production department, or can be relevant to payroll accounting in Human Resources. Additional information may be viewed at this time, such as why certain data has not yet been approved.
As stated above, CATS data is always related to individuals. This means that the person entering the data must either provide an employee number, or in the case of rapid record entry (entering similar or identical data across several employees), an employee number must be supplied for the record screen.
An administrator may enter data for several employees in one session. One possible method is to choose a list entry format that allows the relevant data _ 9 _ for all the employees to be entered at once. Another possible method is to select the employees from a list, and enter the data as a single record. Either way, the principal task of the person entering the data is to enter working times together with information relevant for the further processing and evaluation of the data in other applications, such as HLUnan Resources. This information is known as working time attributes. The working time attributes being eritered depend on the activities for which employees enter working times. The working time attributes can vary not only from one company to another, but also from one area of activity to another.
In a preferred embodiment, the working time attributes are entered in fields, some of which may have default values and some of which must contain data before an entry can be saved. The period covered by a data entry may vary, and in a preferred embodiment long periods, such as those associated with leaves of absence, may also be entered.
Referring to Fig. 2, flowchart 2 represents a more detailed description of the entering of raw data into database 50. A user who wishes to record work 10 directly on the system or through time sheet 15 does so through CATS interface 20, which includes request screen 22 (which indicates to the user that CATS interface 20 is in request mode) and data entry screen 26 (which indicates to the user that CATS ir.Lterface 20 is in data entry mode).
Referring to Fig. 3, initial screen 300 is an example of request screen 22. Initial screen 300 allows the entry of an employee number and the desired data entry variant. For example, in a preferred embodiment internal employees are assigned a data entry variant of 11111, while external employees are assigned a data entry variant of "2". In alternative preferred embodiments, different categories, such as department, project, etc., are used to differentiate among data entry variants.
Work list check 23 is performed on the data that was inputted on request screen 22. Work list check 23 entails checking the data with one or more of applications 30 to determine the proper work list associated with the data. The work list in turn defines the data entry screens to be used. Thus, the data input on request screen 22 will determine the appearance of data entry screens that follow, and it allows these screens to be customized for different employee data. In a preferred embodiment, additional customer enhancements may be applied using user exit 24.
At least one data entry screen 26, determined by work list check 23, is subsequently displayed. Referring to Fig. 4, data entry screen 400 is an example of data entry screen 26. Data entry screen 400 allows the entry of the time worked on one or more days. Examples of the types of data that may be entered on data entry screen 26 include hours worked per day, beginning and end times of work performed each day, activity type, activity price, final confirmation indicator (boolean value indicating whether a particular task is completed), remaining work, plain text, type of attendance or absence, and trip number (reference to a particular trip). This list is by no means exhaustive, but is defined for each particular data entry screen 26.
Data entry screen 26 may also be used to specify various target objects (i.e. recipients of the data).
Target objects are entities t:hat model different business objects. Examples of target objects used with SAP R/3 include cost center, order / network, activity /
activity element / split (between activity and activity element), WBS element, and sales order.
Data entry screen 26 may also be used to specify valid senders. Senders are cost centers responsible for performing some tasks or activities. Examples of valid senders used with SAP R/3 include cost center / activity type objects and purchase order number / purchase order item / service number objects.
In a preferred embodiment, administrative data such as the details of who entered or changed the data, and when it was changed or entered, are supplied automatically by the CATS system and do not have to be entered in data entry screen 26. Auxiliary functions make the system easier to use by allowing certain tasks to be performed simply, such as copying data from a work list to a data entry line, copying data from a data entry list to a work list, copying data from one data entry line to another, copying fromi one period (of time) to another period, and scrolling along a temporal axis with function keys or by entering temporal information (e.g., a date or a week number).
In a preferred embodiment, data entry screen 26 displays a spreadsheet or chart that resembles a time recording sheet with a horizontal time axis, as shown in chart 410 of data entry screen 400 and chart 510 of data entry screen 500 in Fig. 5. Depending on the customized settings, data entry screen 26 may show an employee's planned hours in the future (which may be laid down in a work schedule).
In a preferred embodiment, and again depending on the customized settings, a section of data entry screen 26 may display a work list. As described above, an auxiliary function may be used to copy data from the work list to a data entry line. For example, data entry screen 400 shows the result of the execution of a copy function, in which line 420 has beeil copied to line 430.
in a preferred embodiment of the invention, a time axis displayed on data entry screen 26 may be split into flexible periods for entering the data. For example, a period may cover a day, a month, or other length of time. Other features include the possibility of entering actual time of the day in which work is performed, distributing a specified number of hours over a given time period using a distribution function, allowing work schedule data (the target times) to be inputted directly as actual times, entering data for time periods that lie in the future, and entering time data for absences.
It should be noted that the form of data entry used will determine the appearance of data entry screen 26. Various screen fields may be hidden or displayed, and the user may be given some cor.itrol over the layout of data entry screen 26.
In a preferred embodiment, it is possible to navigate from data entry screen 26 to a travel expense data entry screen, an example of which is shown in Fig.
6. In travel data entry screen 600, original Personnel Time Management 31 functionality is available as a transaction call. Furthermore, references to trip numbers may be entered for reporting purposes. However, in this preferred embodiment, approval process or authorization procedure 65 is not used to approve business travel, which has a separate approval procedure.
In a preferred embodiment, it is also possible to navigate from data entry screen 26 to a goods issue screen, an example of which is shown in Fig. 7. In goods issue screen 700, original External Services 32 functionality is available as a transaction call. The number of the goods issue document is stored in database 50.
In a preferred embodiment, actual costs may be determined based upon the data entered. In this embodiment, there are three methods available for determining the actual costs:
1) Actual costs may be ca:lculated via the rate of the type of service involved. This corresponds to the current standard approach.
2) A rate (e.g., per hour) can be entered and the actual time can be evaluated using this rate. Any variances ar(a noted separately in the costing receipt (separate cost receipt items).
This also requires the use of human resources to be optimized in order to reduce costs. Methods of tracking costs associated.with raw material, machinery, rent, shipping and the like are in existence and are being constantly further improved. There is a need to identify and allocate working time spent by employees and contract workers, in order to improve upon the methods used for human resource allocation, verification, approval and planning.
Information on when an ernployee has performed work and for what reason is important for different areas of the organization, such as personnel administration, logistics, and accounting. A uniform record of hours worked wou:Ld allow a great simplification of the work flow in the organization.
Presently, time sheet entries and processing are often done on a micro-level. Time entries inputted by employees in a department are added together by project or by division, and management receives a weekly or monthly report that does little rnore than provide the totals for that particular department. GJhen a project involves several departments working on diverse aspects of the project, it is often difficult to ascertain the total time spent by the various individuals and the costs associated with that time. Very often a given individual may spend a certain number of hours accomplishing a particular task that provides benefits to several projects, in which case it is difficult to accurately determine each project's share of the benefit. For example, a salesperson working for a large corporation may take several trips to visit a customer's facilities. The time spent on such trips, as well as time spent building and maintaininq relationships may be difficult to track in the first place, let alone accurately assign to various projects in which the customer is involved. Similarly, a researcher may discover a method of improving efficiency in a manufacturing process that may be applied to several ongoing projects. As another example, an individual working in the Information Services department of the organization may spend various amounts of time on different projects such as system rnaintenance, upgrading computers for individuals across several departments.
Furthermore, it would be efficient from the organization's point of view to have various departments in the organizations view the time entries of the above individuals. For example, a project manager may wish to determine whether there are enough people working on the project and whether those people are allocating sufficient time for it. Human resources may want to ascertain that employees are correctly allocated to various projects, to determine whether more employees with particular qualifications need to be hired.
Accounting would need to add up the costs associated with different projects to ensure that there are no overruns.
_ 3 _ Presently, there is a need for a system to track time sheet information and compile data for such various applications, without utilizing a complex network of links to coordinate and distribute data. It would be advantageous to have an effective method of tracking time entries and compiling time sheet information to provide information on internal employees' and external service providers' working times for a variety of applications.
Summary of the Invention The present invention relates to a method and system for compiling time entry data in a common or joint data pool and providing the data to multiple applications. By combining data and storing it in one central system, the data may be asynchronously distributed, either automatically c>r on a needed basis.
A transparent system allows additional processing, such as verification and approval, of separate portions of the data pool before the data is distributed.
Corrections or updates to the data are automatically forwarded to the relevant applications.
An object of the invention is to provide a novel method of compiling time entry data from a variety of sources in a data pool and providing the data to several applications.
Another object of the invention is to monitor time entry data and the information derived from them.
Another object of the invention is to improve transparency in the sharing of time entry data across applications.
Another object of the invention is to automatically and asynchronously distribute compilations of time entry data.
Another object of the invention is to apply asynchronous processing on time entry data to be distributed to several applications.
Another object of the invention is to automatically forward corrected or updated time entry data to several applications.
Detailed Description of the Invention Introduction The present invention allows time entries to be managed in an efficient manner through the centralization and subsequent distribution of relevant data.
The present invention was developed as a standardized, cross-application tool of the SAP R13 System. A brief description of the R/3 System follows.
R/3 can be described primarily as an online transaction processing system designed to provide integrated processing of all business routines and transactions. It includes enterprise-wide, integrated solutions, as well as specialized applications for individual, departmental functions. R/3 mirrors all of the business-critical processes of the enterprise -finance, manufacturing, sales, and human resources. It also offers various analytical capabilities to supplement the transaction process_Lng function.
Recent paradigm shifts have forced companies to optimize all business processes along the net-value-added chain through the use of modern data processing and enterprise-wide information management. In order to become successful, companies often network with customers and suppliers such that products and services of high quality can be made available with minimal delay in response to customer demands. R/3 achieves these goals with online integration of data in the company.
The R/3 System is based on the client/server architecture which separates the database, application, and presentation components for greater flexibility.
This enables enterprises to take advantage of the various benefits of the architecture, including the capability to run across a variety of today's most popular UNIX-based hardware platforms. The R/3 System is designed so that the application systems and system functions are decoupled by a clear layer of architecture, with an applicatiori layer and a basis layer. The multilayer architecture of the R/3 System allows optimal load distribution, even in large installations with thousands of users. It has a modular structure with methods for controlling master-slave relationships between individual software components.
Special servers linked by communications networks can be used for certain tasks without losing the integration of data and processes in the overall system. Implementation of separate servers for particular tasks makes optimal use of the performance potential and the different cost structures of available hardware architecture. This allows applications to be partitioned into different services and run on different servers. The fundamental services of the R/3 system (graphical presentation services, application services for handling of the application logic, database services for sto:rage and recovery of business data, etc.) are partitioned and may evolve separately while maintaining interoperability.
The present invention is contemplated for use in conjunction with several applications of the SAP R/3 System, namely Controlling, Persoi:-inel Time Management, Service Management, Plant Maintenance, Project System, and External Services (part of Materials Management).
The invention may be practiced using different hardware and operating system platforms. The invention as described operates as a module of a larger system.
The following descriptio:n is of the best presently contemplated mode of car:rying out the present invention. This description is not to be taken in a limiting sense but is made merely for the purpose of describing the general principles of the invention.
Overview The cross application time sheets ("CATS") system is a system that allows personal time sheet records to be entered for individuals performing duties for an organization. In a preferred embodiment, such time sheet records may be associated with the organization's own employees (internal employees) or outsiders, such as contractors or consultants (external employees), collectively referred to as "employees", wherein each employee is assigned an employee number in the system (the records of CATS data are always related to individuals). Also in a preferred embodiment, administrators may enter the working time of all employees assigned to them.
The invention is explained in more detail below with the aid of particularly preferred exemplary embodiments illustrated in figures, in which:
Fig. 1 is a flowchart rep.resenting an overview of the process utilized by CATS.
Fig. 2 is a flowchart providing a more detailed representation of the entering of raw data into a database.
Fig. 3 is an example of a preferred embodiment of a request screen.
Fig. 4 is an example of a, preferred embodiment of a data entry screen.
Fig. 5 is another exarrple of a preferred embodiment of a data entry screen.
Fig. 6 is an example of a. preferred embodiment of a travel data entry screen.
Fig. 7 is an example of a. preferred embodiment of a goods issue screen.
Fig. 8 is a flowchart providing a more detailed representation of authorizations ar.Ld approvals.
Fig. 9 is a flowchart providing a more detailed representation of transfer of data that initially requires approval.
Referring to Fig. 1, flowchart 1 represents an overview of the process utilized by CATS. The amount of time that work 10 is performed by employees is either recorded directly on the system using CATS interface 20 or through a time sheet 15 that is subsequently recorded in a recording office using CATS interface 20. In preferred embodiments of the invention, the recording office may be at one physical location, or may be a "virtual" office that is distributed across a network. A
user accessing the system, not shown in the figures, may perform checks with applicatioris 30, which in a preferred embodiment include Personnel Time Management 31, External Services 32, Project System 33, Controlling 34, Plant Maintenance 35, and Service Management 36.
These checks include checking the work list while in the request mode, and verifying information in the data entry mode (described in more detail below). In a preferred embodiment, customer-specific enhancements may be applied using user exit 40.
Data is subsequently passed on to database 50 for storage. From database 50 it is possible to report 55 the data. Depending on the customized settings of the system, approval of the data by an authorized individual may be required. If no approval is required, the data is passed to interface database 70. If approval for any portion of the data is required, business workflow selection process 60 determines the type of approval and authorization that is required, arid approval process /
authorization procedure 65 commences. If any adjustments or corrections to the time sheet data is made during approval process / authorization procedure 65, the adjusted or corrected data is sent back to database 50.
On the other hand, data that is approved and requires no adjustments or corrections is passed to interface database 70. Interface database 70 stores data that is passed via data transfer 75 to one or more applications within applications 30.
Entering, Saving and Releasing Data The type of data entered comprises working times together with information that is relevant to further processing and evaluation of data in various areas of the system. By way of example only, the information can relate to documenting the progress of an order in the production department, or can be relevant to payroll accounting in Human Resources. Additional information may be viewed at this time, such as why certain data has not yet been approved.
As stated above, CATS data is always related to individuals. This means that the person entering the data must either provide an employee number, or in the case of rapid record entry (entering similar or identical data across several employees), an employee number must be supplied for the record screen.
An administrator may enter data for several employees in one session. One possible method is to choose a list entry format that allows the relevant data _ 9 _ for all the employees to be entered at once. Another possible method is to select the employees from a list, and enter the data as a single record. Either way, the principal task of the person entering the data is to enter working times together with information relevant for the further processing and evaluation of the data in other applications, such as HLUnan Resources. This information is known as working time attributes. The working time attributes being eritered depend on the activities for which employees enter working times. The working time attributes can vary not only from one company to another, but also from one area of activity to another.
In a preferred embodiment, the working time attributes are entered in fields, some of which may have default values and some of which must contain data before an entry can be saved. The period covered by a data entry may vary, and in a preferred embodiment long periods, such as those associated with leaves of absence, may also be entered.
Referring to Fig. 2, flowchart 2 represents a more detailed description of the entering of raw data into database 50. A user who wishes to record work 10 directly on the system or through time sheet 15 does so through CATS interface 20, which includes request screen 22 (which indicates to the user that CATS interface 20 is in request mode) and data entry screen 26 (which indicates to the user that CATS ir.Lterface 20 is in data entry mode).
Referring to Fig. 3, initial screen 300 is an example of request screen 22. Initial screen 300 allows the entry of an employee number and the desired data entry variant. For example, in a preferred embodiment internal employees are assigned a data entry variant of 11111, while external employees are assigned a data entry variant of "2". In alternative preferred embodiments, different categories, such as department, project, etc., are used to differentiate among data entry variants.
Work list check 23 is performed on the data that was inputted on request screen 22. Work list check 23 entails checking the data with one or more of applications 30 to determine the proper work list associated with the data. The work list in turn defines the data entry screens to be used. Thus, the data input on request screen 22 will determine the appearance of data entry screens that follow, and it allows these screens to be customized for different employee data. In a preferred embodiment, additional customer enhancements may be applied using user exit 24.
At least one data entry screen 26, determined by work list check 23, is subsequently displayed. Referring to Fig. 4, data entry screen 400 is an example of data entry screen 26. Data entry screen 400 allows the entry of the time worked on one or more days. Examples of the types of data that may be entered on data entry screen 26 include hours worked per day, beginning and end times of work performed each day, activity type, activity price, final confirmation indicator (boolean value indicating whether a particular task is completed), remaining work, plain text, type of attendance or absence, and trip number (reference to a particular trip). This list is by no means exhaustive, but is defined for each particular data entry screen 26.
Data entry screen 26 may also be used to specify various target objects (i.e. recipients of the data).
Target objects are entities t:hat model different business objects. Examples of target objects used with SAP R/3 include cost center, order / network, activity /
activity element / split (between activity and activity element), WBS element, and sales order.
Data entry screen 26 may also be used to specify valid senders. Senders are cost centers responsible for performing some tasks or activities. Examples of valid senders used with SAP R/3 include cost center / activity type objects and purchase order number / purchase order item / service number objects.
In a preferred embodiment, administrative data such as the details of who entered or changed the data, and when it was changed or entered, are supplied automatically by the CATS system and do not have to be entered in data entry screen 26. Auxiliary functions make the system easier to use by allowing certain tasks to be performed simply, such as copying data from a work list to a data entry line, copying data from a data entry list to a work list, copying data from one data entry line to another, copying fromi one period (of time) to another period, and scrolling along a temporal axis with function keys or by entering temporal information (e.g., a date or a week number).
In a preferred embodiment, data entry screen 26 displays a spreadsheet or chart that resembles a time recording sheet with a horizontal time axis, as shown in chart 410 of data entry screen 400 and chart 510 of data entry screen 500 in Fig. 5. Depending on the customized settings, data entry screen 26 may show an employee's planned hours in the future (which may be laid down in a work schedule).
In a preferred embodiment, and again depending on the customized settings, a section of data entry screen 26 may display a work list. As described above, an auxiliary function may be used to copy data from the work list to a data entry line. For example, data entry screen 400 shows the result of the execution of a copy function, in which line 420 has beeil copied to line 430.
in a preferred embodiment of the invention, a time axis displayed on data entry screen 26 may be split into flexible periods for entering the data. For example, a period may cover a day, a month, or other length of time. Other features include the possibility of entering actual time of the day in which work is performed, distributing a specified number of hours over a given time period using a distribution function, allowing work schedule data (the target times) to be inputted directly as actual times, entering data for time periods that lie in the future, and entering time data for absences.
It should be noted that the form of data entry used will determine the appearance of data entry screen 26. Various screen fields may be hidden or displayed, and the user may be given some cor.itrol over the layout of data entry screen 26.
In a preferred embodiment, it is possible to navigate from data entry screen 26 to a travel expense data entry screen, an example of which is shown in Fig.
6. In travel data entry screen 600, original Personnel Time Management 31 functionality is available as a transaction call. Furthermore, references to trip numbers may be entered for reporting purposes. However, in this preferred embodiment, approval process or authorization procedure 65 is not used to approve business travel, which has a separate approval procedure.
In a preferred embodiment, it is also possible to navigate from data entry screen 26 to a goods issue screen, an example of which is shown in Fig. 7. In goods issue screen 700, original External Services 32 functionality is available as a transaction call. The number of the goods issue document is stored in database 50.
In a preferred embodiment, actual costs may be determined based upon the data entered. In this embodiment, there are three methods available for determining the actual costs:
1) Actual costs may be ca:lculated via the rate of the type of service involved. This corresponds to the current standard approach.
2) A rate (e.g., per hour) can be entered and the actual time can be evaluated using this rate. Any variances ar(a noted separately in the costing receipt (separate cost receipt items).
3) The rate is determined. via a user exit and the actual hours can then be evaluated using this rate. Any variances are noted separately in the costing receipt (separate cost receipt items). 'I'his technique allows the data to be obtairied on a calculation that depends on the user exit or a customer-specific formula.
Note that in this embodiment if two different rates are used (e.g., normal compensation and overtime compensation), either two lines mtzst be filled out in the time sheet and the appropriate rates must be applied to each, or two different activity types with different associated rates must be used.
Verification check 27 is performed on the data entered in data entry screen 26. Verification check 27 entails checking the data with one or more of applications 30 to determine that proper and sufficient data has been entered in data er.itry screen 26. Data entered in data entry screen 26 cannot be saved without passing verification check 27. Upon a determination by verification check 27 that proper and sufficient data has been entered, additional customer enhancements may be applied using the user exit in a preferred embodiment. The entered data is then stored in database 50.
Referring to Fig. 8, flowchart 3 represents a more detailed description of authorizations and approvals.
Authorization checks distinguish between two kinds of users: those who enter tinte data, and those who approve the data that was entered. It is the latter type of authorization check that applies to data residing in database 50. As stated above, if no approval or authorization is required, the data may be passed to interface database 70. However, if approval for any portion of the data is required, business workflow selection process 60 determines the type of approval and authorization that is required. Once business workflow selection process 60 determines the type of approval and authorization that is required for a given set of data, the data is displayed on the approval screen through approval process / authorization procedure 65.
An employee who approves the entered data must also have the transaction authorization to do so. The transaction authorization of aarticular individual usually depends at least partially upon the identity of the employee whose time entry data needs to be approved (e.g., a supervisor is usually authorized to approve the time entry data of the employees he or she is supervising, but not authorized to approve the time entry data of employees not being supervised by him or her). In a preferred embodiment, such authorization information is stored in an organizational model, which contains relevant information., such as the organizational structure.
I I!
Authorizations may also be assigned on an object-specific basis (e.g., a particular individual or individuals may have authorization to approve for a certain order type only). Authorizations may also be extended as required by individual customers using user exits (customer-specific enhancements).
In a preferred embodiment, approval may be given by an authorized individual in a graduated manner. By way of example only, an individual may approve time entry data of an individual employee, a given period of time entry data of an individual employee, or a given period for an organizational unit (e.g., an entire department's time entry data). Of course, the individual giving approval must be authorized to give such approval.
If approval is not given to a particular data entry, an explanation of the reason for the rejection can be attached to the data. In a preferred embodiment, if data is rejected, either the individual who entered the data or the employee for whom the data was entered is informed via work flow.
Approval procedures can be activated and deactivated by the system administrator, or someone else with the proper authorization, through customization.
Data Transfer Referring to Fig. 9, flowchart 4 shows the transfer of data that require approval. Upon a new entry of data via CATS interface 20 and application of user exit 40, the data is stored in database 50 without approval. As long as the data has not been approved, changes 57 to the data can be made, and changes 57 are reflected in database 50. Although changes 57 to data that has been approved may still be made, those changes 57 to approved data cause a new non-approved entry to be created in database 50. The new non-approved entry must go through the same approval process /
authorization procedure 65 as the original data, and both sets of data are then transferred to the target application.
Upon completion of approval process /
authorization procedure 65, data is written to interface database 70. In a preferred embodiment, interface database 70 contains interface ta:bles for each of the applications 30 involved. The data residing in an interface table is fetched by their associated target application 30 in predetermined time intervals and stored in the target applicatiori database 90. In a preferred embodiment, once data has been transferred to target application database 90, the data is deleted from the associated interface table in interface database 70.
In a preferred embodiment., target application 30 is supplied with data accord.Lng to the following rules:
1) If an operation number or an element number is entered, a completion confirmation is created and data associated with Controlling 34 is written indirectly.
2) If a recipient is entered without an operation number or an element nu:mber, data associated with Controlling 34 is written directly.
3) If a purchase order number or a purchase order item and a service number are entered, data associated with External Services 32 and with Controlling 34 is written indirectly.
Note that in this embodiment if two different rates are used (e.g., normal compensation and overtime compensation), either two lines mtzst be filled out in the time sheet and the appropriate rates must be applied to each, or two different activity types with different associated rates must be used.
Verification check 27 is performed on the data entered in data entry screen 26. Verification check 27 entails checking the data with one or more of applications 30 to determine that proper and sufficient data has been entered in data er.itry screen 26. Data entered in data entry screen 26 cannot be saved without passing verification check 27. Upon a determination by verification check 27 that proper and sufficient data has been entered, additional customer enhancements may be applied using the user exit in a preferred embodiment. The entered data is then stored in database 50.
Referring to Fig. 8, flowchart 3 represents a more detailed description of authorizations and approvals.
Authorization checks distinguish between two kinds of users: those who enter tinte data, and those who approve the data that was entered. It is the latter type of authorization check that applies to data residing in database 50. As stated above, if no approval or authorization is required, the data may be passed to interface database 70. However, if approval for any portion of the data is required, business workflow selection process 60 determines the type of approval and authorization that is required. Once business workflow selection process 60 determines the type of approval and authorization that is required for a given set of data, the data is displayed on the approval screen through approval process / authorization procedure 65.
An employee who approves the entered data must also have the transaction authorization to do so. The transaction authorization of aarticular individual usually depends at least partially upon the identity of the employee whose time entry data needs to be approved (e.g., a supervisor is usually authorized to approve the time entry data of the employees he or she is supervising, but not authorized to approve the time entry data of employees not being supervised by him or her). In a preferred embodiment, such authorization information is stored in an organizational model, which contains relevant information., such as the organizational structure.
I I!
Authorizations may also be assigned on an object-specific basis (e.g., a particular individual or individuals may have authorization to approve for a certain order type only). Authorizations may also be extended as required by individual customers using user exits (customer-specific enhancements).
In a preferred embodiment, approval may be given by an authorized individual in a graduated manner. By way of example only, an individual may approve time entry data of an individual employee, a given period of time entry data of an individual employee, or a given period for an organizational unit (e.g., an entire department's time entry data). Of course, the individual giving approval must be authorized to give such approval.
If approval is not given to a particular data entry, an explanation of the reason for the rejection can be attached to the data. In a preferred embodiment, if data is rejected, either the individual who entered the data or the employee for whom the data was entered is informed via work flow.
Approval procedures can be activated and deactivated by the system administrator, or someone else with the proper authorization, through customization.
Data Transfer Referring to Fig. 9, flowchart 4 shows the transfer of data that require approval. Upon a new entry of data via CATS interface 20 and application of user exit 40, the data is stored in database 50 without approval. As long as the data has not been approved, changes 57 to the data can be made, and changes 57 are reflected in database 50. Although changes 57 to data that has been approved may still be made, those changes 57 to approved data cause a new non-approved entry to be created in database 50. The new non-approved entry must go through the same approval process /
authorization procedure 65 as the original data, and both sets of data are then transferred to the target application.
Upon completion of approval process /
authorization procedure 65, data is written to interface database 70. In a preferred embodiment, interface database 70 contains interface ta:bles for each of the applications 30 involved. The data residing in an interface table is fetched by their associated target application 30 in predetermined time intervals and stored in the target applicatiori database 90. In a preferred embodiment, once data has been transferred to target application database 90, the data is deleted from the associated interface table in interface database 70.
In a preferred embodiment., target application 30 is supplied with data accord.Lng to the following rules:
1) If an operation number or an element number is entered, a completion confirmation is created and data associated with Controlling 34 is written indirectly.
2) If a recipient is entered without an operation number or an element nu:mber, data associated with Controlling 34 is written directly.
3) If a purchase order number or a purchase order item and a service number are entered, data associated with External Services 32 and with Controlling 34 is written indirectly.
4) If only the type of attendance or absence is entered, only data associated with Personnel Time Management 31 is written.
i ,.
in a preferred embodiment, the CATS system may be customized to have data in database 50 copied into a second database 50a for historical data record keeping.
Customizing Settings may be altered via customizing. For example, depending on the data entry variant being used, the following settings may be changed in entry screen 26: field selection, chec:ks, functions (e.g., branching to a travel entry data screen or a goods issue screen), displaying the work list, displaying the work schedule, selection of recipients for work flow).
As stated above, approval procedures can be activated and deactivated. Also as stated above, the CATS system may be customized to have data in database 50 copied into a second database 50a for historical data record keeping.
i ,.
in a preferred embodiment, the CATS system may be customized to have data in database 50 copied into a second database 50a for historical data record keeping.
Customizing Settings may be altered via customizing. For example, depending on the data entry variant being used, the following settings may be changed in entry screen 26: field selection, chec:ks, functions (e.g., branching to a travel entry data screen or a goods issue screen), displaying the work list, displaying the work schedule, selection of recipients for work flow).
As stated above, approval procedures can be activated and deactivated. Also as stated above, the CATS system may be customized to have data in database 50 copied into a second database 50a for historical data record keeping.
Claims (56)
1. A cross-application time-sheet system comprising:
(a) a first interface for displaying a request for employee identification and data entry variant information, receiving said employee identification and data entry variant information, displaying a data entry screen, and accepting employee time records comprising time entry data for at least one employee;
(b) a work list check for selecting said data entry screen based upon said received employee identification and data entry variant information;
(c) a verification check for verifying that said time entry data is complete for at least one of said at least one employee;
(d) a database for storing said time entry data;
(e) a subsystem for obtaining approval for a subset of said time entry data; and (f) a second interface receiving and storing said time entry data, said second interface being linked to a plurality of enterprise management applications, said time entry data being fetched by said applications from said second interface;
said verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
(a) a first interface for displaying a request for employee identification and data entry variant information, receiving said employee identification and data entry variant information, displaying a data entry screen, and accepting employee time records comprising time entry data for at least one employee;
(b) a work list check for selecting said data entry screen based upon said received employee identification and data entry variant information;
(c) a verification check for verifying that said time entry data is complete for at least one of said at least one employee;
(d) a database for storing said time entry data;
(e) a subsystem for obtaining approval for a subset of said time entry data; and (f) a second interface receiving and storing said time entry data, said second interface being linked to a plurality of enterprise management applications, said time entry data being fetched by said applications from said second interface;
said verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
2. The cross application time sheet system of claim 1, wherein said database contains only time entry data which has been verified to be complete by said verification check.
3. The cross-application time sheet system of claim 1, wherein said second interface contains only time entry data receiving said approval.
4. The cross application time sheet system of claim 1, wherein said selecting said data entry screen is further based upon information provided by said plurality of enterprise management applications.
5. The cross-application time sheet system of claim 1, wherein said subsystem obtains approval for a modified version of said subset of said time entry data.
6. The cross-application time sheet system of claim 1, wherein said first interface displays a travel expense data entry screen and a goods issue screen.
7. The cross application time sheet system of claim 1, wherein said time entry data are associated with travel expense data by a trip number.
8. A method of processing time entry data comprising the steps of:
(a) displaying a request for employee identification and data entry variant information;
(b) receiving said employee identification and data entry variant information;
(c) selecting a data entry screen based upon said received employee identification and data entry variant information;
(d) displaying said data entry screen;
(e) accepting employee time records comprising time entry data for at least one employee;
(f) verifying that said time entry data is complete for at least one of said at least one employee;
(g) storing said time entry data in a database;
(h) obtaining approval for a subset of said time entry data; and (i) storing said time entry data in a second database for fetching of said time entry data by a plurality of enterprise management applications linked to the database;
said verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
(a) displaying a request for employee identification and data entry variant information;
(b) receiving said employee identification and data entry variant information;
(c) selecting a data entry screen based upon said received employee identification and data entry variant information;
(d) displaying said data entry screen;
(e) accepting employee time records comprising time entry data for at least one employee;
(f) verifying that said time entry data is complete for at least one of said at least one employee;
(g) storing said time entry data in a database;
(h) obtaining approval for a subset of said time entry data; and (i) storing said time entry data in a second database for fetching of said time entry data by a plurality of enterprise management applications linked to the database;
said verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
9. The method of processing time entry data of claim 8, wherein the step of selecting said data entry screen is further based upon information provided by said plurality of enterprise management applications.
10. The method of processing time entry data of claim 8, wherein said first database contains only time entry data that has been verified to be complete in step (f).
11. The method of processing time entry data of claim 8, further comprising the step of obtaining approval for a modified version of said subset of said time entry data.
12. Method for processing time entry data of claim 8, further comprising the step of displaying a travel expense data entry screen and a goods issue screen.
13. The method of claim 8 further comprising receiving corrected data in the second database from the plurality of enterprise management applications.
14. The method of claim 8 wherein said time entry data are associated with travel expense data by a trip number.
15. A cross application time sheet system comprising:
(a) first interface means for displaying a request for employee identification and data entry variant information, receiving said employee identification and data entry variant information, displaying a data entry screen, and accepting employee time records comprising time entry data for at least one employee;
(b) checking means for selecting said data entry screen based upon said received employee identification and data entry variant information;
(c) means for verifying that said time entry data is complete for at least one of said at least one employee;
(d) database means for storing said time entry data;
(e) means for obtaining approval for a subset of said time entry data; and (f) second interface means for receiving from the database and storing said time entry data, said second interface means being linked to a plurality of enterprise management applications, and said time entry data being stored so as to be fetched by said applications;
said verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
(a) first interface means for displaying a request for employee identification and data entry variant information, receiving said employee identification and data entry variant information, displaying a data entry screen, and accepting employee time records comprising time entry data for at least one employee;
(b) checking means for selecting said data entry screen based upon said received employee identification and data entry variant information;
(c) means for verifying that said time entry data is complete for at least one of said at least one employee;
(d) database means for storing said time entry data;
(e) means for obtaining approval for a subset of said time entry data; and (f) second interface means for receiving from the database and storing said time entry data, said second interface means being linked to a plurality of enterprise management applications, and said time entry data being stored so as to be fetched by said applications;
said verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
16. The cross application time sheet system of claim 15, wherein said selecting said data entry screen is further based upon information provided by said plurality of enterprise management applications.
17. The cross application time sheet system of claim 15, wherein said database means only stores time entry data that has been verified to be complete by said means for verifying.
18. The cross application time sheet system of claim 15, wherein said second interface means only stores time entry data approved by said means for obtaining approval.
19. The cross application time sheet system of claim 15, wherein said first interface means displays a travel expense data entry screen and a goods issue screen.
20. The cross application time sheet system of claim 15, wherein the second interface means receives corrected data from the plurality of enterprise management applications.
21. The cross application time sheet system of claim 15, wherein said time entry data are associated with travel expense data by a trip number.
22. A computer-readable medium having stored thereon a plurality of instructions stored thereon, said plurality of instructions including instructions which, when executed by a processor, cause the processor to perform the steps of:
(a) displaying a request for employee identification and data entry variant information;
(b) receiving said employee identification and data entry variant information;
(c) displaying a data entry screen;
(d) accepting employee time records comprising time entry data for at least one employee;
(e) selecting said data entry screen based upon said received employee identification and data entry variant information;
(f) verifying that said time entry data is complete for at least one of said at least one employee;
(g) storing said time entry data in a database;
(h) obtaining approval for a subset of said time entry data; and (i) storing said time entry data from database in a second database for fetching of said time entry data by a plurality of enterprise management applications linked to the database;
said step of verifying including performing a verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
(a) displaying a request for employee identification and data entry variant information;
(b) receiving said employee identification and data entry variant information;
(c) displaying a data entry screen;
(d) accepting employee time records comprising time entry data for at least one employee;
(e) selecting said data entry screen based upon said received employee identification and data entry variant information;
(f) verifying that said time entry data is complete for at least one of said at least one employee;
(g) storing said time entry data in a database;
(h) obtaining approval for a subset of said time entry data; and (i) storing said time entry data from database in a second database for fetching of said time entry data by a plurality of enterprise management applications linked to the database;
said step of verifying including performing a verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
23. The computer-readable medium of claim 22, wherein the step of selecting said data entry screen is further based upon information provided by said plurality of enterprise management applications.
24. The computer-readable medium of claim 22, wherein said first database contains only time entry data that has been verified to be complete in step (f).
25. The computer-readable medium of claim 22, wherein said plurality of instructions further include additional instructions which, when executed by said processor, cause said processor to perform the step of obtaining approval for a modified version of said subset of said time entry data.
26. The computer-readable medium of claim 22, wherein said plurality of instructions further include additional instructions which, when executed by said processor, cause said processor to perform the step of displaying a travel expense data entry screen and a goods issue screen.
27. The computer-readable medium of claim 22, wherein said plurality of instructions further include additional instructions which, when executed by said processor, cause said processor to perform the step of receiving corrected data in the second database from the plurality of enterprise management applications.
28. The computer-readable medium of claim 22, wherein said time entry data are associated with travel expense data by a trip number.
29. A method of processing time entry data in an R/3 system comprising the steps of:
(a) displaying a request for employee identification and data entry variant information;
(b) receiving said employee identification and data entry variant information;
(c) displaying a data entry screen;
(d) accepting employee time records comprising time entry data for at least one employee;
(e) selecting said data entry screen based upon said received employee identification and data entry variant information;
(f) verifying that said time entry data is complete for at least one of said at least one employee;
(g) storing said time entry data in a database;
(h) obtaining approval for a subset of said time entry data; and (i) storing said time entry data from the database in a second database for fetching of said time entry data by a plurality of R/3 enterprise management applications;
said step of verifying including performing a verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
(a) displaying a request for employee identification and data entry variant information;
(b) receiving said employee identification and data entry variant information;
(c) displaying a data entry screen;
(d) accepting employee time records comprising time entry data for at least one employee;
(e) selecting said data entry screen based upon said received employee identification and data entry variant information;
(f) verifying that said time entry data is complete for at least one of said at least one employee;
(g) storing said time entry data in a database;
(h) obtaining approval for a subset of said time entry data; and (i) storing said time entry data from the database in a second database for fetching of said time entry data by a plurality of R/3 enterprise management applications;
said step of verifying including performing a verification check verifying that the time entry data is complete by communicating with at least one of said plurality of enterprise management applications.
30. A system for processing time entry data, said system comprising:
a first interface receiving time entry data representing work done by one or more workers;
a first database associated with the first interface, said first database receiving the time entry data from the first interface and storing said time entry data;
a second database to which said time entry data is passed from the first database;
a plurality of enterprise management applications supported in the system and linked to said second database;
said second database transferring said time entry data to the applications;
and said first interface checking the time entry data with one or more of said enterprise management applications during entry of said time entry data.
a first interface receiving time entry data representing work done by one or more workers;
a first database associated with the first interface, said first database receiving the time entry data from the first interface and storing said time entry data;
a second database to which said time entry data is passed from the first database;
a plurality of enterprise management applications supported in the system and linked to said second database;
said second database transferring said time entry data to the applications;
and said first interface checking the time entry data with one or more of said enterprise management applications during entry of said time entry data.
31. The system of claim 30, wherein said first interface includes a data entry device, and said time entry data is entered through said data entry device.
32. The system of claim 30, and said first interface determining an appropriate work list for said time entry data based upon said checking.
33. The system of claim 30, and an approval subsystem linked between the first database and the second database, said approval subsystem obtaining approval for a subset of said time entry data, and said subset of said time entry data being passed to the second database only when approval is received.
34. The system of claim 30, and said first interface checking said time entry data including a verification check for verifying that the time entry data is complete for each worker.
35. The system of claim 30, wherein each of said plurality of enterprise management applications is supported on a respective server.
36. The system of claim 30, wherein each of said plurality of enterprise management applications has a respective database for storing the time entry data transferred from the second database.
37. The system of claim 30, wherein said second database stores said time entry data in a plurality of tables, wherein each of said plurality of tables is associated with a respective enterprise management application.
38. The system of claim 37 wherein the associated enterprise management application empties the respective table when the data is transferred therefrom.
39. The system of claim 30 wherein the plurality of enterprise management applications includes personnel time management, external services, project system, controlling, plant maintenance and service management applications.
40. The system of claim 30 wherein the system generates a report from the time entry data stored in the first database.
41. The system of claim 30, wherein the second database receives corrected data from the plurality of enterprise management applications.
42. The system of claim 30, wherein said time entry data are associated with travel expense data by a trip number.
43. A method of processing time entry data, said method comprising:
receiving via a first interface time entry data representing work done by one or more workers;
communicating with one or more of said enterprise management applications during entry of said time entry data;
storing said time entry data in a first database associated with the first interface;
passing said time entry data to a second database;
transferring said time entry data from said second database to a plurality of enterprise management applications supported in the system and linked with said second database.
receiving via a first interface time entry data representing work done by one or more workers;
communicating with one or more of said enterprise management applications during entry of said time entry data;
storing said time entry data in a first database associated with the first interface;
passing said time entry data to a second database;
transferring said time entry data from said second database to a plurality of enterprise management applications supported in the system and linked with said second database.
44. The method of claim 43, wherein said first interface includes a data entry device, said time entry data being entered through said data entry device.
45. The method of claim 44, wherein said time entry data includes an identification of said at least one worker and at least one time record for said at least one worker.
46. The method of claim 43, and further comprising determining an appropriate work list for said time entry data based upon said communicating with one or more of said enterprise management applications.
47. The method of claim 43, further comprising obtaining approval for a subset of said time entry data before passing said subset of said time entry data between the first database and the second database, said subset of said time entry data being passed to the second database only when said approval is received.
48. The method of claim 43, wherein said first interface verifies that the time entry data is complete for each of said at least one worker.
49. The method of claim 43, wherein each of said plurality of enterprise management applications is supported on a respective server and said transferring includes transmission of the time entry data to said servers.
50. The method of claim 43, wherein each of said enterprise management applications has a respective application database, the time entry data transferred from the second database being stored in each of said application databases.
51. The method of claim 43, wherein said storing in said second database includes storing said time entry data in a plurality of tables each associated with a respective application.
52. The method of claim 51 further comprising emptying at least one of said plurality of tables when the time entry data is transferred therefrom.
53. The method of claim 43 wherein the plurality of enterprise management applications includes personnel time management, external services, project system, controlling, plant maintenance and service management applications.
54. The method of claim 43 further comprising generating a report from the time entry data stored in the first database.
55. The method of claim 43 further comprising receiving corrected data in the second database from the plurality of enterprise management applications.
56. The method of claim 43 wherein said time entry data and travel expenses are associated by a trip number.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US09/100,257 | 1998-06-19 | ||
| US09/100,257 US6338097B1 (en) | 1998-06-19 | 1998-06-19 | Cross application time sheet for communicating with one or more enterprise management applications during time data entry |
| PCT/EP1999/004228 WO1999067749A1 (en) | 1998-06-19 | 1999-06-18 | Multi-application time sheet |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2332938A1 CA2332938A1 (en) | 1999-12-29 |
| CA2332938C true CA2332938C (en) | 2009-04-07 |
Family
ID=22278845
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002332938A Expired - Lifetime CA2332938C (en) | 1998-06-19 | 1999-06-18 | Cross application time sheet |
Country Status (7)
| Country | Link |
|---|---|
| US (1) | US6338097B1 (en) |
| EP (1) | EP1088287A1 (en) |
| JP (1) | JP5025850B2 (en) |
| AU (1) | AU765941B2 (en) |
| CA (1) | CA2332938C (en) |
| IL (1) | IL139640A (en) |
| WO (1) | WO1999067749A1 (en) |
Families Citing this family (140)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6477660B1 (en) * | 1998-03-03 | 2002-11-05 | Sap Aktiengesellschaft | Data model for supply chain planning |
| US7305347B1 (en) | 1998-09-09 | 2007-12-04 | Raymond Anthony Joao | Apparatus and method for providing employee benefits and /or employee benefits information |
| US6539379B1 (en) * | 1999-08-23 | 2003-03-25 | Oblix, Inc. | Method and apparatus for implementing a corporate directory and service center |
| EP1337933A4 (en) * | 1999-12-06 | 2008-03-05 | Balance Innovations Llc | A system, method, and computer program for managing storage and distribution of money tills |
| US6753884B1 (en) * | 2000-01-31 | 2004-06-22 | Journyx, Inc. | Method and apparatus for wireless web time and expense entry via time keeping and expense tracking server access |
| US7069498B1 (en) * | 2000-01-31 | 2006-06-27 | Journyx, Inc. | Method and apparatus for a web based punch clock/time clock |
| US6944652B1 (en) * | 2000-01-31 | 2005-09-13 | Journyx, Inc. | Method and apparatus for providing frequent flyer miles and incentives for timely interaction with a time records system |
| US6747679B1 (en) * | 2000-01-31 | 2004-06-08 | Journyx, Inc. | Time keeping and expense tracking server that interfaces with a user based upon a user's atomic abilities |
| US6751650B1 (en) * | 2000-01-31 | 2004-06-15 | Journyx, Inc. | Method and apparatus for monitoring contractor performance |
| US6750885B1 (en) * | 2000-01-31 | 2004-06-15 | Journyx, Inc. | Time keeping and expense tracking server that interfaces with a user based upon a user's atomic abilities |
| US6567822B1 (en) * | 2000-03-21 | 2003-05-20 | Accenture Llp | Generating a data request graphical user interface for use in an electronic supply chain value assessment |
| JP2003529159A (en) * | 2000-03-31 | 2003-09-30 | エスアーペー アクチエンゲゼルシャフト | Matrix method and system for supply chain management |
| US7134137B2 (en) * | 2000-07-10 | 2006-11-07 | Oracle International Corporation | Providing data to applications from an access system |
| US7080077B2 (en) * | 2000-07-10 | 2006-07-18 | Oracle International Corporation | Localized access |
| US7464162B2 (en) * | 2000-07-10 | 2008-12-09 | Oracle International Corporation | Systems and methods for testing whether access to a resource is authorized based on access information |
| US7194764B2 (en) * | 2000-07-10 | 2007-03-20 | Oracle International Corporation | User authentication |
| US7124203B2 (en) * | 2000-07-10 | 2006-10-17 | Oracle International Corporation | Selective cache flushing in identity and access management systems |
| US8661539B2 (en) * | 2000-07-10 | 2014-02-25 | Oracle International Corporation | Intrusion threat detection |
| US9038170B2 (en) | 2000-07-10 | 2015-05-19 | Oracle International Corporation | Logging access system events |
| US7249369B2 (en) | 2000-07-10 | 2007-07-24 | Oracle International Corporation | Post data processing |
| US8204999B2 (en) * | 2000-07-10 | 2012-06-19 | Oracle International Corporation | Query string processing |
| US7376647B1 (en) | 2000-07-18 | 2008-05-20 | Accenture Llp | Method for evaluating activity-based costs of a company |
| US6895438B1 (en) * | 2000-09-06 | 2005-05-17 | Paul C. Ulrich | Telecommunication-based time-management system and method |
| WO2002044981A1 (en) * | 2000-11-28 | 2002-06-06 | Textron Financial Corporation | Method for expediting entry of information into a timesheet system |
| US7415607B2 (en) | 2000-12-22 | 2008-08-19 | Oracle International Corporation | Obtaining and maintaining real time certificate status |
| US7349912B2 (en) * | 2000-12-22 | 2008-03-25 | Oracle International Corporation | Runtime modification of entries in an identity system |
| US7363339B2 (en) | 2000-12-22 | 2008-04-22 | Oracle International Corporation | Determining group membership |
| US8015600B2 (en) * | 2000-12-22 | 2011-09-06 | Oracle International Corporation | Employing electronic certificate workflows |
| US7213249B2 (en) | 2000-12-22 | 2007-05-01 | Oracle International Corporation | Blocking cache flush requests until completing current pending requests in a local server and remote server |
| US7085834B2 (en) * | 2000-12-22 | 2006-08-01 | Oracle International Corporation | Determining a user's groups |
| US7475151B2 (en) | 2000-12-22 | 2009-01-06 | Oracle International Corporation | Policies for modifying group membership |
| US7380008B2 (en) * | 2000-12-22 | 2008-05-27 | Oracle International Corporation | Proxy system |
| US7711818B2 (en) * | 2000-12-22 | 2010-05-04 | Oracle International Corporation | Support for multiple data stores |
| US7802174B2 (en) * | 2000-12-22 | 2010-09-21 | Oracle International Corporation | Domain based workflows |
| US7937655B2 (en) | 2000-12-22 | 2011-05-03 | Oracle International Corporation | Workflows with associated processes |
| US6782379B2 (en) * | 2000-12-22 | 2004-08-24 | Oblix, Inc. | Preparing output XML based on selected programs and XML templates |
| US7581011B2 (en) | 2000-12-22 | 2009-08-25 | Oracle International Corporation | Template based workflow definition |
| US6816871B2 (en) * | 2000-12-22 | 2004-11-09 | Oblix, Inc. | Delivering output XML with dynamically selectable processing |
| US7185022B2 (en) * | 2001-01-26 | 2007-02-27 | Semiconductor Energy Laboratory Co., Ltd. | Work data management system and work data management method |
| US7185364B2 (en) * | 2001-03-21 | 2007-02-27 | Oracle International Corporation | Access system interface |
| JP4224226B2 (en) * | 2001-06-26 | 2009-02-12 | 富士通株式会社 | Display control method, display control system, display control program, and computer-readable medium |
| US7426486B2 (en) * | 2001-10-31 | 2008-09-16 | Call-Tell Llc | Multi-party reporting system and method |
| US7212301B2 (en) * | 2001-10-31 | 2007-05-01 | Call-Tell Llc | System and method for centralized, automatic extraction of data from remotely transmitted forms |
| US7225256B2 (en) * | 2001-11-30 | 2007-05-29 | Oracle International Corporation | Impersonation in an access system |
| US20030126159A1 (en) * | 2001-12-28 | 2003-07-03 | Nwafor John I. | Method and system for rollback of software system upgrade |
| US7216163B2 (en) | 2002-05-15 | 2007-05-08 | Oracle International Corporation | Method and apparatus for provisioning tasks using a provisioning bridge server |
| US7840658B2 (en) | 2002-05-15 | 2010-11-23 | Oracle International Corporation | Employing job code attributes in provisioning |
| US7512585B2 (en) * | 2002-07-11 | 2009-03-31 | Oracle International Corporation | Support for multiple mechanisms for accessing data stores |
| US8375113B2 (en) | 2002-07-11 | 2013-02-12 | Oracle International Corporation | Employing wrapper profiles |
| US7478407B2 (en) | 2002-07-11 | 2009-01-13 | Oracle International Corporation | Supporting multiple application program interfaces |
| US7467142B2 (en) * | 2002-07-11 | 2008-12-16 | Oracle International Corporation | Rule based data management |
| US7206851B2 (en) * | 2002-07-11 | 2007-04-17 | Oracle International Corporation | Identifying dynamic groups |
| US7447701B2 (en) * | 2002-07-11 | 2008-11-04 | Oracle International Corporation | Automatic configuration of attribute sets |
| US7114037B2 (en) * | 2002-07-11 | 2006-09-26 | Oracle International Corporation | Employing local data stores to maintain data during workflows |
| US7428592B2 (en) * | 2002-07-11 | 2008-09-23 | Oracle International Corporation | Securely persisting network resource identifiers |
| US7428523B2 (en) | 2002-07-11 | 2008-09-23 | Oracle International Corporation | Portal bridge |
| US20040024629A1 (en) * | 2002-08-02 | 2004-02-05 | Kirby Jack Reese | Methods and apparatus for project management |
| US20040056889A1 (en) * | 2002-09-23 | 2004-03-25 | Seiichi Katano | Multi-function peripheral |
| US20040172311A1 (en) | 2003-02-28 | 2004-09-02 | Kauderer Steven I. | Method of and system for evaluating underwriting activities |
| US7882132B2 (en) | 2003-10-09 | 2011-02-01 | Oracle International Corporation | Support for RDBMS in LDAP system |
| US7340447B2 (en) * | 2003-10-09 | 2008-03-04 | Oracle International Corporation | Partitioning data access requests |
| US7904487B2 (en) | 2003-10-09 | 2011-03-08 | Oracle International Corporation | Translating data access requests |
| TW200523762A (en) * | 2004-01-05 | 2005-07-16 | Via Tech Inc | An electronic form system and corresponding method |
| US8229810B2 (en) * | 2004-02-25 | 2012-07-24 | Butera Cynthia S | Realtime billable timekeeper method, system and apparatus |
| US20050190398A1 (en) * | 2004-03-01 | 2005-09-01 | Jayasimha Nuggehalli | Multifunction peripheral for data collection and distribution |
| US9830623B2 (en) * | 2004-06-07 | 2017-11-28 | Keal, Inc. | System and method for managing numerous facets of a work relationship |
| US8744934B1 (en) * | 2004-06-07 | 2014-06-03 | Keal, Inc. | System and method for improved time reporting and billing |
| US20060010051A1 (en) * | 2004-07-07 | 2006-01-12 | Sap Aktiengeseilschaft | Method and system for time sheet reporting |
| US20070100834A1 (en) * | 2004-09-15 | 2007-05-03 | John Landry | System and method for managing data in a distributed computer system |
| US8380553B2 (en) * | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
| US20070156500A1 (en) * | 2005-12-30 | 2007-07-05 | Wilfried Merkel | Architectural design for sell from stock application software |
| US20070156550A1 (en) * | 2005-12-30 | 2007-07-05 | Der Emde Martin V | Architectural design for cash and liquidity management application software |
| US8326703B2 (en) * | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
| US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
| US8448137B2 (en) * | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
| US8370794B2 (en) * | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
| US8402426B2 (en) * | 2005-12-30 | 2013-03-19 | Sap Ag | Architectural design for make to stock application software |
| US8321831B2 (en) * | 2005-12-30 | 2012-11-27 | Sap Ag | Architectural design for internal projects application software |
| US20080275713A9 (en) * | 2005-12-30 | 2008-11-06 | Shai Alfandary | Architectural design for physical inventory application software |
| US8688495B2 (en) * | 2005-12-30 | 2014-04-01 | Sap Ag | Architectural design for time recording application software |
| US8327319B2 (en) * | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
| US8676617B2 (en) * | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
| US8396731B2 (en) * | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
| US8316344B2 (en) * | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
| US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
| US8660904B2 (en) * | 2005-12-30 | 2014-02-25 | Sap Ag | Architectural design for service request and order management application software |
| US8688813B2 (en) * | 2006-01-11 | 2014-04-01 | Oracle International Corporation | Using identity/resource profile and directory enablers to support identity management |
| US8538864B2 (en) * | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
| US8326702B2 (en) * | 2006-03-30 | 2012-12-04 | Sap Ag | Providing supplier relationship management software application as enterprise services |
| US8396749B2 (en) * | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
| US20070233575A1 (en) * | 2006-03-30 | 2007-10-04 | Arthur Berger | Architectural design for strategic sourcing application software |
| US20070233539A1 (en) * | 2006-03-30 | 2007-10-04 | Philipp Suenderhauf | Providing human capital management software application as enterprise services |
| US8396761B2 (en) * | 2006-03-30 | 2013-03-12 | Sap Ag | Providing product catalog software application as enterprise services |
| US8442850B2 (en) * | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
| US8438119B2 (en) * | 2006-03-30 | 2013-05-07 | Sap Ag | Foundation layer for services based enterprise software architecture |
| US8321832B2 (en) * | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
| US8312416B2 (en) * | 2006-04-13 | 2012-11-13 | Sap Ag | Software model business process variant types |
| US8645907B2 (en) * | 2006-09-12 | 2014-02-04 | Sandeep Jain | Capturing effort level by task upon check-in to source control management system |
| US20080120152A1 (en) * | 2006-11-21 | 2008-05-22 | Mccrea Frank | System and method for managing numerous facets of a work relationship |
| US20090037246A1 (en) * | 2007-07-31 | 2009-02-05 | Caterpillar Inc. | Resource allocation system and method |
| US8401936B2 (en) * | 2007-12-31 | 2013-03-19 | Sap Ag | Architectural design for expense reimbursement application software |
| US20090171758A1 (en) * | 2007-12-31 | 2009-07-02 | Shai Alfandary | Architectural design for physical inventory application software |
| US8671034B2 (en) * | 2007-12-31 | 2014-03-11 | Sap Ag | Providing human capital management software application as enterprise services |
| US8315900B2 (en) * | 2007-12-31 | 2012-11-20 | Sap Ag | Architectural design for self-service procurement application software |
| US8447657B2 (en) * | 2007-12-31 | 2013-05-21 | Sap Ag | Architectural design for service procurement application software |
| US8671033B2 (en) * | 2007-12-31 | 2014-03-11 | Sap Ag | Architectural design for personnel events application software |
| US20090171811A1 (en) * | 2007-12-31 | 2009-07-02 | Peter Markus A | Architectural Design For Product Catalog Management Application Software |
| US8671032B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing payment software application as enterprise services |
| US8510143B2 (en) * | 2007-12-31 | 2013-08-13 | Sap Ag | Architectural design for ad-hoc goods movement software |
| US8380549B2 (en) * | 2008-09-18 | 2013-02-19 | Sap Ag | Architectural design for embedded support application software |
| US20100070395A1 (en) * | 2008-09-18 | 2010-03-18 | Andreas Elkeles | Architectural design for payroll processing application software |
| US20100070556A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Data Migration Application Software |
| US8374896B2 (en) * | 2008-09-18 | 2013-02-12 | Sap Ag | Architectural design for opportunity management application software |
| US20100070336A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Providing Customer Relationship Management Application as Enterprise Services |
| US8359218B2 (en) * | 2008-09-18 | 2013-01-22 | Sap Ag | Computer readable medium for implementing supply chain control using service-oriented methodology |
| US8352338B2 (en) * | 2008-09-18 | 2013-01-08 | Sap Ag | Architectural design for time recording application software |
| US8315926B2 (en) | 2008-09-18 | 2012-11-20 | Sap Ag | Architectural design for tax declaration application software |
| US8321250B2 (en) * | 2008-09-18 | 2012-11-27 | Sap Ag | Architectural design for sell from stock application software |
| US8401928B2 (en) * | 2008-09-18 | 2013-03-19 | Sap Ag | Providing supplier relationship management software application as enterprise services |
| US8595077B2 (en) * | 2008-09-18 | 2013-11-26 | Sap Ag | Architectural design for service request and order management application software |
| US8386325B2 (en) * | 2008-09-18 | 2013-02-26 | Sap Ag | Architectural design for plan-driven procurement application software |
| US20100082497A1 (en) * | 2008-09-18 | 2010-04-01 | Sap Ag | Providing Foundation Application as Enterprise Services |
| US8326706B2 (en) * | 2008-09-18 | 2012-12-04 | Sap Ag | Providing logistics execution application as enterprise services |
| US8818884B2 (en) * | 2008-09-18 | 2014-08-26 | Sap Ag | Architectural design for customer returns handling application software |
| US8321308B2 (en) * | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for manual invoicing application software |
| US8321306B2 (en) * | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
| US8738476B2 (en) * | 2008-12-03 | 2014-05-27 | Sap Ag | Architectural design for selling standardized services application software |
| US8311904B2 (en) * | 2008-12-03 | 2012-11-13 | Sap Ag | Architectural design for intra-company stock transfer application software |
| US8401908B2 (en) * | 2008-12-03 | 2013-03-19 | Sap Ag | Architectural design for make-to-specification application software |
| US20100153158A1 (en) * | 2008-12-11 | 2010-06-17 | Sap Ag | Providing project management software application as enterprise services |
| US8671035B2 (en) * | 2008-12-11 | 2014-03-11 | Sap Ag | Providing payroll software application as enterprise services |
| US20100153239A1 (en) * | 2008-12-11 | 2010-06-17 | Sap Ag | Providing accounting software application as enterprise services |
| US20100169143A1 (en) * | 2008-12-31 | 2010-07-01 | Peter Carr | System and method for managing numerous facets of a work relationship |
| US9396232B1 (en) * | 2009-10-16 | 2016-07-19 | Iqor Holdings, Inc. | Apparatuses, methods and systems for a rule-integrated virtual punch clock |
| US9454577B1 (en) | 2009-10-16 | 2016-09-27 | Iqor Holdings Inc, Iqor US Inc. | Apparatuses, methods and systems for an employee reimbursement evaluator |
| US8863097B2 (en) | 2010-12-29 | 2014-10-14 | Sap Ag | Providing code list extensibility |
| US9524147B2 (en) | 2013-05-10 | 2016-12-20 | Sap Se | Entity-based cross-application navigation |
| US9594636B2 (en) * | 2014-05-30 | 2017-03-14 | Datto, Inc. | Management of data replication and storage apparatuses, methods and systems |
| GB201504710D0 (en) * | 2015-03-20 | 2015-05-06 | Ibm | Establishing transaction metadata |
| CN106846530A (en) * | 2016-12-25 | 2017-06-13 | 北京中海投资管理有限公司 | A kind of property movement cruising inspection system and method based on NFC technique |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4847791A (en) | 1982-08-16 | 1989-07-11 | Martin Joseph H | Timekeeping system |
| US4819162A (en) | 1985-05-17 | 1989-04-04 | Time Management Corporation | Time clock system including scheduling payroll and productivity analysis capability |
| EP0434875A1 (en) | 1989-12-29 | 1991-07-03 | S K C Software | A resource control system |
| JP2887812B2 (en) * | 1990-02-13 | 1999-05-10 | 富士ゼロックス株式会社 | Time clock |
| JPH0668277A (en) * | 1992-06-16 | 1994-03-11 | Mitsubishi Electric Corp | Data input method and device |
| US5459657A (en) * | 1993-06-21 | 1995-10-17 | Mirage Resorts Incorporated | Employee time entry and accounting system |
| JPH07325870A (en) * | 1994-04-07 | 1995-12-12 | Hiroko Matsuzawa | Time manamgement system |
| US5910010A (en) * | 1994-04-26 | 1999-06-08 | Hitachi, Ltd. | Semiconductor integrated circuit device, and process and apparatus for manufacturing the same |
| US5600554A (en) * | 1994-09-29 | 1997-02-04 | Crucible Materials Corporation | Methods and apparatus for securing, integrating, and manipulating employee payroll and human resource information |
| JPH0944713A (en) * | 1995-07-27 | 1997-02-14 | Casio Comput Co Ltd | Attendance management device and system therefor |
| US5765140A (en) * | 1995-11-17 | 1998-06-09 | Mci Corporation | Dynamic project management system |
| US5991742A (en) * | 1996-05-20 | 1999-11-23 | Tran; Bao Q. | Time and expense logging system |
| JPH10124722A (en) * | 1996-10-24 | 1998-05-15 | Casio Comput Co Ltd | Automatic attendance managing system using radio communication terminal |
| US6049776A (en) * | 1997-09-06 | 2000-04-11 | Unisys Corporation | Human resource management system for staffing projects |
-
1998
- 1998-06-19 US US09/100,257 patent/US6338097B1/en not_active Expired - Lifetime
-
1999
- 1999-06-18 CA CA002332938A patent/CA2332938C/en not_active Expired - Lifetime
- 1999-06-18 JP JP2000556342A patent/JP5025850B2/en not_active Expired - Lifetime
- 1999-06-18 WO PCT/EP1999/004228 patent/WO1999067749A1/en not_active Application Discontinuation
- 1999-06-18 AU AU46132/99A patent/AU765941B2/en not_active Expired
- 1999-06-18 IL IL13964099A patent/IL139640A/en not_active IP Right Cessation
- 1999-06-18 EP EP99929269A patent/EP1088287A1/en not_active Withdrawn
Also Published As
| Publication number | Publication date |
|---|---|
| AU4613299A (en) | 2000-01-10 |
| AU765941B2 (en) | 2003-10-02 |
| CA2332938A1 (en) | 1999-12-29 |
| IL139640A (en) | 2004-02-19 |
| WO1999067749A1 (en) | 1999-12-29 |
| IL139640A0 (en) | 2002-02-10 |
| US6338097B1 (en) | 2002-01-08 |
| JP5025850B2 (en) | 2012-09-12 |
| EP1088287A1 (en) | 2001-04-04 |
| JP2002526819A (en) | 2002-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2332938C (en) | Cross application time sheet | |
| US9177278B2 (en) | Systems and methods for rule inheritance | |
| US20060294235A1 (en) | Management and data handling system and method | |
| US20060010023A1 (en) | System, method and computer program product for managing meeting planning operations | |
| US20090157463A1 (en) | Approver Identification Using Multiple Hierarchical Role Structures | |
| US20020107775A1 (en) | Automated bidding process and system | |
| US7729962B2 (en) | Timecard processing in a procurement management system | |
| US20090157445A1 (en) | Automated Execution of Business Processes Using Two Stage State | |
| US20090182607A1 (en) | Approver Identification Using Multiple Hierarchical Role Structures | |
| US20090182570A1 (en) | Automated Execution of Business Processes Using Two Stage State | |
| US20090157462A1 (en) | Content Hierarchy | |
| WO2003047150A2 (en) | Signature loop authorizing method and apparatus | |
| Lerouge et al. | Managing by projects | |
| Glatzmaier et al. | Project portfolio management with SAP RPM and cProjects | |
| Wu | Small business computers for CPA firms | |
| Debetaz | Rapid cycle-time redesign: Productive at any speed | |
| Summerour Jr et al. | Automated contracting: a productivity study | |
| Nanayakkara | Computer connectivity and networking product inventory system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry |
Effective date: 20190618 |