US20030216979A1 - Mutable general ledger account structure - Google Patents
Mutable general ledger account structure Download PDFInfo
- Publication number
- US20030216979A1 US20030216979A1 US10/421,375 US42137503A US2003216979A1 US 20030216979 A1 US20030216979 A1 US 20030216979A1 US 42137503 A US42137503 A US 42137503A US 2003216979 A1 US2003216979 A1 US 2003216979A1
- Authority
- US
- United States
- Prior art keywords
- segment
- account
- type
- identification
- graphical user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
Definitions
- This invention relates generally to general ledger software systems.
- the typical financial application handles only data.
- the structure is hard coded at compile time, the application is programmed about the hard coded structure, and then at run time the structure can be populated, but cannot be changed without tearing into the application programming.
- FIGS. 1 A-E illustrate a conventional model.
- the GLAccountType table is metadata that represents all segment types of each chart of accounts. The relative position of each segment type in a table defines the chart of accounts format.
- the GLSegmentType table which represents metadata, constrains each segment type.
- the GLSegmentType table defines the name and each segment type length.
- the GLAccount table is data that represents each entry in the chart of accounts. The value of each segment occurs in the defined relative position for each segment type.
- the GLSegment table constrains each segment value, which is the data value of each segment. The database cannot enforce the constraints and therefore the application must enforce them.
- the present invention provides a computer program product that includes a data structure for representing a general ledger account.
- the data structure includes an account type table, an account table, a segment type table, a segment table, and an association table.
- the account type table includes one or more account type identification and an associated account type name, wherein one of the account type names is primary account.
- the account table includes one or more account identification and an associated account type identification from the account type table.
- the segment type table includes one or more segment type identification and an associated segment type name, display position, status, length, and account type identification from the account type table.
- the segment table includes one or more segment identification and an associated segment value and segment type identification from the segment type table.
- the association table includes an association between the segment identification from the segment table and account identification from the account table.
- the computer program product includes a graphical user interface (GUI).
- GUI graphical user interface
- the GUI allows for entering an account type into the data structure, for entering a segment into the data structure, and for changing display positions in the segment type table.
- the graphical user interface component further allows for deactivating a segment, changing the size of a segment, and changing the segment value in the segment table.
- FIG. 1A-E are pictorial representations of a prior art database model for a general ledger account structure
- FIG. 2 is a pictorial representation of a structural database model for a general ledger account structure formed in accordance with the present invention
- FIGS. 3 - 7 are tables that represent the structural database model shown in FIG. 2;
- FIGS. 8 - 11 , 13 , 14 , 18 , 20 , 21 , and 23 are example graphical user interfaces formed in accordance with the present invention for interacting with the database model.
- FIGS. 12 , 15 - 17 , 19 , and 22 are tables that illustrate the actions performed in the graphical user interfaces.
- the present invention is a database model 40 for a general ledger account.
- a GLAccount is comprised of an arbitrary number of GLSegments.
- GLSegmentType describes each GLSegment.
- Each GLSegmentType and GLAccount has a GLAccountType.
- GLAccountType indicates how an account is used, e.g., recording transactions for actual events, budgeting, or consolidation.
- GLSegmentType defines each segment of the multipartite GL account, e.g., company, department, and account.
- GLSegment stores the segment number and title, e.g., “4420.10 Salary Expense.”
- GLAccount and the many-to-many relationship between GLAccount and GLSegment assemble the segment numbers and titles into a single complete GL account.
- a common occurrence in Chart of Accounts reorganizations is the addition of a new account segment.
- This example shows the contents of the tables shown in FIG. 2 before and after addition of a segment.
- the account in the “before” case consists of a company and an account segment.
- In the “after” case it consists of company, department, and account.
- This simple example demonstrates that none of the extant data in the tables GLAccount, GLSegment, and GLAccountSegment is altered for this reorganization. Only the metadata in GLSegmentType is changed.
- a GLAccountType table 60 includes metadata that represents each chart of accounts.
- the GLAccountType table 60 includes a glAccountTypeID column and a glAccountType/Name column.
- One of the items in the glAccountType ID column is identified as a primary chart of accounts. Any number of alternate charts of accounts are also present in the GLAccountType table 60.
- a GLAccount table 70 is data that represents the chart of accounts.
- the GLAccount table 70 includes a glAccountID column and a glAccountTypeID column.
- a GLSegmentType table 80 is metadata that represents each segment type of a chart of accounts.
- the GLSegmentType table 80 includes a glSegmentType ID column, a glSegmentTypeName column, a displayPosition column, a status column, a maxLength column, and a glAccountTypeID column.
- Each chart of accounts represents segments in any order. Each chart can have different segment types.
- the GLSegmentType table 80 allows the user to change the number, order, and length of segment types that make up each chart of accounts.
- the GLSegmentType table 80 also allows a segment to be active or inactive.
- a GLSegment table 90 includes the value of each segment.
- the GLSegment table 90 includes a gISegmentID column, a glSegrnentValue column, and a glSegmentTypeID column.
- a GLAccount_GLSegment association table 100 represents the relationship between the GLAccount table 70 and the GLSegment table 90.
- the GLAccount_GLSegment table 100 includes a glAccountID column and a glSegmentID column.
- FIGS. 8 - 11 , 13 , 14 , 18 , 20 , 21 , and 23 illustrate exemplary Graphical User Interfaces (GUIs) and various database structural functions that can be performed using the GUIs.
- GUI Graphical User Interfaces
- the GUI is a window 200 that includes the following alterable fields: General Ledger Account Type field 208 ; Segment Type field 210 ; Display Position field 212 ; and Maximum Length field 214 .
- the entries in the fields corresponds to storage locations in one or more of the above described tables.
- the window 200 also includes Active/Inactive status selection fields 220 , and Save, Cancel, and Edit buttons.
- the General Ledger Account Type field 208 and the Segment Type field 210 are pull-down menus that allow the user to select from predefined lists of associated entries or create new entries.
- a company has set up an order (display order) of chart of account segments as follows:
- the user simply changes the relative display position values in the Display Position fields 212 in the Account segment Type window 200 and a Department segment Type window 240 (FIG. 9).
- the Display Position field 212 of the Account segment type window 200 is changed from 2 to 3 (FIGS. 8, 10) and the Display Position field 212 of the Department segment type window 240 is changed from 3 to 2 (FIGS. 9, 11).
- FIG. 12 the change that occurred in FIGS. 10 and 11 is illustrated in the GLSegmentType table 80.
- a company has grown and decided to add a product segment to the chart of accounts in order to track detail by product.
- the user adds a new record to the General Ledger Segment Type table called “Product” using the GUI window 200 .
- the order of the chart of accounts now becomes:
- FIG. 13 illustrates a GUI window 280 before the addition of a new record.
- FIG. 14 illustrates the GUI window 290 after the addition of a record of a Segment Type Product with Display Position equal to 5. The Active status is marked and an arbitrary Maximum Length value is inserted.
- new records are entered into the bottom rows of the GLSegmentType table 80, the GLSegment table 90 and the GLAccountGLSegment association table 100.
- the company decides the use of the product segment has become too cumbersome and wants to suspend use.
- the user marks the product segment type as inactive using Active/Inactive status selection fields 220 (See FIG. 18).
- the status field is changed in the GLSegment table 80 as shown in FIG. 19.
- the order of the chart of accounts now is as follows:
- a General Ledger Segments window 360 allows a user to change the segment value of affected segments in a Segment Value field 370 .
- the General Ledger Segments window 360 also includes a General Ledger Account Type pull-down field 372 , a Segment Type pull-down field 374 , a Segment Description field 380 , and Status field section 390 that allows selection of Active, Inactive, or Report.
- the window 360 also includes Save, Cancel, and Exit buttons. The changes performed in the window 360 are reflected in one or more of the corresponding tables.
Abstract
A computer program product and method for representing a general ledger account. The data structure includes an account type table, an account table, a segment type table, a segment table, and an association table. The account type table includes account type identification and an associated account type name. The account table includes account identification and an associated account type identification from the account type table. The segment type table includes one or more segment type identification and an associated segment type name, display position, status, length, and account type identification from the account type table. The segment table includes one or more segment identification and an associated segment value and segment type identification from the segment type table. The association table includes an association between the segment identification from the segment table and account identification from the account table.
Description
- This application claims priority from Provisional Application Ser. Nos. 60/375,192 (Our Ref: FXAG.1.1001) and 60/375,202 (Our Ref: FXAG.1.1002) both of which were filed Apr. 22, 2002, and are hereby incorporated by reference.
- This invention relates generally to general ledger software systems.
- A significant business problem exists for defining charts of accounts for business, government, and non-profit organizations. For conventional accounting information systems, the general ledger account structure must be chosen and fixed before the chart of accounts can be populated. (The account structure consists of a string of primarily numeric characters which is subdivided into segments. Each segment has a fixed starting position and a fixed length.) After financial transactions have been created, the structure of the general ledger account for these transactions cannot be changed.
- This inability to change account structure is a particularly challenging problem for rapidly growing organizations whose business needs are changing. Currently, the only solution is to redefine the chart of accounts periodically to provide the additional required information content to the management of the organization. This either (1) creates a discontinuity between fiscal years for comparative purposes, or (2) requires a significant one-time software engineering effort to convert data from the old general ledger account structure to the new structure. Such conversions create major concerns for data integrity, system availability, and system reliability.
- In case (2) above, data conversion is often beyond the means of a rapidly growing business because software development resources are scarce and expensive. Also, significant business risk is involved because the data conversion might not be 100% successful. Finally, software development resources are often needed to support the direct line of business.
- The typical financial application handles only data. As far as the application is concerned, the structure is hard coded at compile time, the application is programmed about the hard coded structure, and then at run time the structure can be populated, but cannot be changed without tearing into the application programming.
- Most chart of account systems rely on a fixed number of segments and often a fixed field length for each segment. The example described below is one of the more elegant versions of the current architecture. They allow the user to create variable number of segments of variable length. However, they require that the defined structure be “frozen” and thus becomes “fixed” once it has been defined. While the user may make changes to the structure, it cannot be done on-the-fly, nor can it be done without significant complications. Again, with our system, it can be changed on-the-fly and existing data remains consistent with the new structure.
- The following text is from the Oracle Financials Handbook:
- “It is also difficult to change your Accounting Flexfield after it has been frozen and has been used to capture data through transaction processing. Changing your structures after-the-fact may create data inconsistencies that could impact the behavior of your application or require a complex conversion program. As soon as you are satisfied, freeze your Accounting Flexfield structure to prohibit unnecessary modifications. You must freeze and compile your flexfield definition before you use your flexfield.”
- The following illustrates an example of the above identified problem. FIGS.1A-E illustrate a conventional model. Four tables represent a basic conventional model. The GLAccountType table is metadata that represents all segment types of each chart of accounts. The relative position of each segment type in a table defines the chart of accounts format. The GLSegmentType table, which represents metadata, constrains each segment type. The GLSegmentType table defines the name and each segment type length. The GLAccount table is data that represents each entry in the chart of accounts. The value of each segment occurs in the defined relative position for each segment type. The GLSegment table constrains each segment value, which is the data value of each segment. The database cannot enforce the constraints and therefore the application must enforce them.
- Therefore, there exists a need for easily adaptable general ledger accounting software where adaptability is not performed through complex changes in the application program.
- The present invention provides a computer program product that includes a data structure for representing a general ledger account. The data structure includes an account type table, an account table, a segment type table, a segment table, and an association table. The account type table includes one or more account type identification and an associated account type name, wherein one of the account type names is primary account. The account table includes one or more account identification and an associated account type identification from the account type table. The segment type table includes one or more segment type identification and an associated segment type name, display position, status, length, and account type identification from the account type table. The segment table includes one or more segment identification and an associated segment value and segment type identification from the segment type table. The association table includes an association between the segment identification from the segment table and account identification from the account table.
- In accordance with another embodiment of the present invention, the computer program product includes a graphical user interface (GUI). The GUI allows for entering an account type into the data structure, for entering a segment into the data structure, and for changing display positions in the segment type table. The graphical user interface component further allows for deactivating a segment, changing the size of a segment, and changing the segment value in the segment table.
- BRIEF DESCRIPTION OF THE DRAWINGS
- The preferred and alternative embodiments of the present invention are described in detail below with reference to the following drawings.
- FIG. 1A-E are pictorial representations of a prior art database model for a general ledger account structure;
- FIG. 2 is a pictorial representation of a structural database model for a general ledger account structure formed in accordance with the present invention;
- FIGS.3-7 are tables that represent the structural database model shown in FIG. 2;
- FIGS.8-11, 13, 14, 18, 20, 21, and 23 are example graphical user interfaces formed in accordance with the present invention for interacting with the database model; and
- FIGS.12, 15-17, 19, and 22 are tables that illustrate the actions performed in the graphical user interfaces.
- As shown in FIG. 2, the present invention is a
database model 40 for a general ledger account. In themodel 40, a GLAccount is comprised of an arbitrary number of GLSegments. GLSegmentType describes each GLSegment. Each GLSegmentType and GLAccount has a GLAccountType. - GLAccountType indicates how an account is used, e.g., recording transactions for actual events, budgeting, or consolidation.
- GLSegmentType defines each segment of the multipartite GL account, e.g., company, department, and account.
- GLSegment stores the segment number and title, e.g., “4420.10 Salary Expense.”
- GLAccount and the many-to-many relationship between GLAccount and GLSegment assemble the segment numbers and titles into a single complete GL account.
- A common occurrence in Chart of Accounts reorganizations is the addition of a new account segment. This example shows the contents of the tables shown in FIG. 2 before and after addition of a segment. The account in the “before” case consists of a company and an account segment. In the “after” case, it consists of company, department, and account. This simple example demonstrates that none of the extant data in the tables GLAccount, GLSegment, and GLAccountSegment is altered for this reorganization. Only the metadata in GLSegmentType is changed.
- “Before” Case: Company-Account
GLAccountType ID Name AT1 Actuals AT2 Budget GLSegmentType Display ID Name Position Status MaxLength GLAccountType ST1 Company 1 Active 3 AT1 ST2 Account 2 Active 6 AT1 GLSegment ID Value GLSegmentType S1 100 ST1 S2 442001 ST2 GLAccount ID GLAccountType A1 AT1 GLAccountSegment GLAccount GLSegment A1 S1 A1 S2 GLAccountType ID Name AT1 Actuals AT2 Budget - Note that the second row in this table is the only change to a record that exists in the “Before” case; and that this table contains metadata, not the fundamental transactional data of an enterprise.
Display- Max- ID Name Position Status Length GLAccountType ST1 Company 1 Active 3 AT1 ST2 Account 3 Active 6 AT1 ST3 Department 2 Active 2 AT1 GLSegment ID Value GLSegmentType S1 100 ST1 S2 442001 ST2 S3 70 ST3 GLAccount ID GLAccountType A1 AT1 GLAccountSegment GLAccount GLSegment A1 S1 A1 S2 A1 S3 - As shown in FIGS.3-7, five tables (stored in memory) represent the database 15
model 40. As shown in FIG. 3, a GLAccountType table 60 includes metadata that represents each chart of accounts. The GLAccountType table 60 includes a glAccountTypeID column and a glAccountType/Name column. One of the items in the glAccountType ID column is identified as a primary chart of accounts. Any number of alternate charts of accounts are also present in the GLAccountType table 60. - As shown in FIG. 4, a GLAccount table 70 is data that represents the chart of accounts. The GLAccount table 70 includes a glAccountID column and a glAccountTypeID column.
- As shown in FIG. 5, a GLSegmentType table 80 is metadata that represents each segment type of a chart of accounts. The GLSegmentType table 80 includes a glSegmentType ID column, a glSegmentTypeName column, a displayPosition column, a status column, a maxLength column, and a glAccountTypeID column. There could be any number of segment types in the GLSegmentType table 80, such as company, department, project, program, product, etc. Each chart of accounts represents segments in any order. Each chart can have different segment types. The GLSegmentType table 80 allows the user to change the number, order, and length of segment types that make up each chart of accounts. The GLSegmentType table 80 also allows a segment to be active or inactive.
- As shown in FIG. 6, a GLSegment table 90 includes the value of each segment. The GLSegment table 90 includes a gISegmentID column, a glSegrnentValue column, and a glSegmentTypeID column.
- As shown in FIG. 7, a GLAccount_GLSegment association table 100 represents the relationship between the GLAccount table 70 and the GLSegment table 90. The GLAccount_GLSegment table 100 includes a glAccountID column and a glSegmentID column.
- FIGS.8-11, 13, 14, 18, 20, 21, and 23 illustrate exemplary Graphical User Interfaces (GUIs) and various database structural functions that can be performed using the GUIs. As shown in FIG. 8, the GUI is a
window 200 that includes the following alterable fields: General Ledger Account Type field 208;Segment Type field 210;Display Position field 212; andMaximum Length field 214. The entries in the fields corresponds to storage locations in one or more of the above described tables. Thewindow 200 also includes Active/Inactive status selection fields 220, and Save, Cancel, and Edit buttons. The General Ledger Account Type field 208 and theSegment Type field 210 are pull-down menus that allow the user to select from predefined lists of associated entries or create new entries. - Changing the Order of Segments:
- In one example, a company (user) has set up an order (display order) of chart of account segments as follows:
- Company: Account: Department: Project
- The user decides that the following order would make it easier to report on the chart using a new generic report writer:
- Company: Department: Account: Project
- In order accomplish this change, the user simply changes the relative display position values in the Display Position fields212 in the Account
segment Type window 200 and a Department segment Type window 240 (FIG. 9). TheDisplay Position field 212 of the Accountsegment type window 200 is changed from 2 to 3 (FIGS. 8, 10) and theDisplay Position field 212 of the Departmentsegment type window 240 is changed from 3 to 2 (FIGS. 9, 11). As shown in FIG. 12, the change that occurred in FIGS. 10 and 11 is illustrated in the GLSegmentType table 80. - Add a New Segment (Record):
- In one embodiment, a company has grown and decided to add a product segment to the chart of accounts in order to track detail by product. The user adds a new record to the General Ledger Segment Type table called “Product” using the
GUI window 200. The order of the chart of accounts now becomes: - Company: Department: Account: Project: Product
- FIG. 13 illustrates a GUI window280 before the addition of a new record. FIG. 14 illustrates the GUI window 290 after the addition of a record of a Segment Type Product with Display Position equal to 5. The Active status is marked and an arbitrary Maximum Length value is inserted. As shown in FIGS. 15-17, new records are entered into the bottom rows of the GLSegmentType table 80, the GLSegment table 90 and the GLAccountGLSegment association table 100.
- Remove a Segment Type:
- In another embodiment, the company decides the use of the product segment has become too cumbersome and wants to suspend use. The user marks the product segment type as inactive using Active/Inactive status selection fields220 (See FIG. 18). The status field is changed in the GLSegment table 80 as shown in FIG. 19. The order of the chart of accounts now is as follows:
- Company: Account: Department: Project
- Change the Size of a Segment Field
- The company realizes that their department identifier length is too short (Maximum Length field214) and they need to expand the field and change all the department codes. As shown in FIGS. 20 and 21, the user changes the maximum length value in the
Maximum Length field 214. The change in length is reflected in the GLSegment table 80, as shown in FIG. 22. - Change the Value of a Segment
- The company decides to reorganize the order of departments and wants to change the department numbers throughout the organization. As shown in FIG. 23, a General Ledger Segments window360 allows a user to change the segment value of affected segments in a Segment Value field 370. The General Ledger Segments window 360 also includes a General Ledger Account Type pull-down field 372, a Segment Type pull-
down field 374, a Segment Description field 380, and Status field section 390 that allows selection of Active, Inactive, or Report. The window 360 also includes Save, Cancel, and Exit buttons. The changes performed in the window 360 are reflected in one or more of the corresponding tables. - While the preferred embodiment of the invention has been illustrated and described, as noted above, many changes can be made without departing from the spirit and scope of the invention. Accordingly, the scope of the invention is not limited by the disclosure of the preferred embodiment. By way of example and not limitation, in one alternate embodiment, this invention can be used in conjunction with the invention described in our co-pending application entitled FOOD TRACING AND TRACKING SYSTEM AND METHOD (Serial number not yet assigned) filed on Apr. 22, 2003, and which is hereby incorporated by reference.
Claims (12)
1. A computer program product comprising a data structure for representing a general ledger account, the data structure comprising:
an account type table including one or more account type identification;
an account table including one or more account identification and an associated account type identification from the account type table;
a segment type table including one or more segment type identification and account type identification from the account type table;
a segment table including one or more segment identification and segment type identification from the segment type table; and
an association table including an association between the segment identification from the segment table and account identification from the account table.
2. The computer program product of claim 1 , further comprising:
a graphical user interface component comprising:
a first component for entering a segment into the data structure; and
a second component for changing display positions in the segment type table.
3. The computer program product of claim 2 , wherein the first component includes one or more of the following fields: an account type field, a segment type field, a display position field, one or more length fields; and a status selection component.
4. The computer program product of claim 2 , wherein the graphical user interface component further comprises a third component for deactivating a segment.
5. The computer program product of claim 2 , wherein the graphical user interface component further comprises a third component for changing the size of a segment.
6. The computer program product of claim 2 , wherein the graphical user interface component further comprises a third component for changing the segment value in the segment table.
7. A method for representing a general ledger account, the method comprising:
storing an account type table including one or more account type identification;
storing an account table including one or more account identification and an associated account type identification from the account type table;
storing a segment type table including one or more segment type identification and account type identification from the account type table;
storing a segment table including one or more segment identification and segment type identification from the segment type table; and
storing an association table including an association between the segment identification from the segment table and account identification from the account table.
8. The method of claim 7 , further comprising:
entering a segment into the data structure using a graphical user interface; and
changing display positions in the segment type table using the graphical user interface.
9. The method of claim 8 , wherein the graphical user interface includes an account type field, a segment type field, a display position field, one or more length fields, and a status selection component.
10. The method of claim 8 , further comprising deactivating a segment using the graphical user interface.
11. The method of claim 8 , further comprising changing the size of a segment using the graphical user interface.
12. The method of claim 8 , further comprising changing the segment value in the segment table using the graphical user interface.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/421,375 US20030216979A1 (en) | 2002-04-22 | 2003-04-22 | Mutable general ledger account structure |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US37520202P | 2002-04-22 | 2002-04-22 | |
US37519202P | 2002-04-22 | 2002-04-22 | |
US10/421,375 US20030216979A1 (en) | 2002-04-22 | 2003-04-22 | Mutable general ledger account structure |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030216979A1 true US20030216979A1 (en) | 2003-11-20 |
Family
ID=29254577
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/421,375 Abandoned US20030216979A1 (en) | 2002-04-22 | 2003-04-22 | Mutable general ledger account structure |
US10/421,630 Active - Reinstated 2026-10-28 US8392225B2 (en) | 2002-04-22 | 2003-04-22 | Food tracing and tracking system and method |
US13/736,887 Abandoned US20130124375A1 (en) | 2002-04-22 | 2013-01-08 | Food tracing and tracking system and method |
US14/180,123 Abandoned US20140172653A1 (en) | 2002-04-22 | 2014-02-13 | Food tracing and tracking system and method |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/421,630 Active - Reinstated 2026-10-28 US8392225B2 (en) | 2002-04-22 | 2003-04-22 | Food tracing and tracking system and method |
US13/736,887 Abandoned US20130124375A1 (en) | 2002-04-22 | 2013-01-08 | Food tracing and tracking system and method |
US14/180,123 Abandoned US20140172653A1 (en) | 2002-04-22 | 2014-02-13 | Food tracing and tracking system and method |
Country Status (5)
Country | Link |
---|---|
US (4) | US20030216979A1 (en) |
EP (1) | EP1504390A4 (en) |
JP (1) | JP2005523507A (en) |
AU (1) | AU2003225162A1 (en) |
WO (1) | WO2003090036A2 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050154628A1 (en) * | 2004-01-13 | 2005-07-14 | Illumen, Inc. | Automated management of business performance information |
US20050154769A1 (en) * | 2004-01-13 | 2005-07-14 | Llumen, Inc. | Systems and methods for benchmarking business performance data against aggregated business performance data |
US20120151411A1 (en) * | 2010-12-09 | 2012-06-14 | Oracle International Corporation | Mechanism to input, search and create complex data strings within a single dialog |
US20140101007A1 (en) * | 2012-10-04 | 2014-04-10 | Quickdash, Llc | Methods and apparatus for providing data normalization, scalability and maintainability |
US9483799B2 (en) | 2010-07-12 | 2016-11-01 | Qvinci Software, Llc | Methods and apparatus for the aggregation of data |
US9600136B1 (en) * | 2013-03-11 | 2017-03-21 | Workday, Inc. | Data object extensibility |
US10304095B2 (en) * | 2008-02-04 | 2019-05-28 | Thomson Reuters Global Resources Unlimited Company | System and method for accounting gateway |
US11625662B2 (en) | 2016-09-22 | 2023-04-11 | Qvinci Software, Llc | Methods and apparatus for the manipulating and providing of anonymized data collected from a plurality of sources |
Families Citing this family (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9704108B2 (en) * | 2002-06-07 | 2017-07-11 | Jda Software Group, Inc. | System and method for network visualization and plan review |
ATE456843T1 (en) | 2003-09-05 | 2010-02-15 | Sensitech Inc | AUTOMATIC PROCESSING OF DATA ACCUMULATED BY SENSORS MONITORING SUPPLY CHAIN PROCESSES |
US20050108024A1 (en) * | 2003-11-13 | 2005-05-19 | Fawcett John Jr. | Systems and methods for retrieving data |
US7552860B2 (en) | 2004-04-23 | 2009-06-30 | Seiko Instruments Inc. | Product history management method, apparatus, and program, label issuing method, apparatus, and program, and identification information issuing apparatus |
US7580916B2 (en) * | 2005-03-15 | 2009-08-25 | Microsoft Corporation | Adjustments to relational chart of accounts |
US11954715B2 (en) | 2006-02-27 | 2024-04-09 | Trace Produce, LLC | Methods and systems for accessing information related to an order of a commodity |
US10229441B2 (en) * | 2006-02-27 | 2019-03-12 | Trace Produce, LLC | Methods and systems for accessing information related to an order of a commodity |
NO326945B1 (en) * | 2007-03-19 | 2009-03-16 | Science Linker As | Authenticated Database System. |
WO2009046396A1 (en) * | 2007-10-04 | 2009-04-09 | Growers Express, Llc | Crop production, planning, management, tracking and reporting system and method |
EP2323083A1 (en) * | 2009-10-21 | 2011-05-18 | ecs Beratung & Service GmbH | Technical classification system |
US10262283B2 (en) * | 2009-12-01 | 2019-04-16 | Thomson Reuters Global Resources Unlimited Company | Methods and systems for generating supply chain representations |
TW201121665A (en) * | 2009-12-18 | 2011-07-01 | Zhen-Zhang Zhu | Failure alarm method of fruit selector. |
CA2776577C (en) * | 2010-10-05 | 2021-03-30 | Bayer Cropscience Lp | A system and method establishing an agricultural pedigree for at least one agricultural product |
US8285593B2 (en) * | 2010-10-29 | 2012-10-09 | International Business Machines Corporation | Identifying source material associated with food products using bill of material |
US20140122184A1 (en) | 2012-10-29 | 2014-05-01 | Elwha Llc | Food Supply Chain Automation Grocery Information System And Method |
US20140122262A1 (en) * | 2012-10-29 | 2014-05-01 | Elwha Llc | Food Supply Chain Automation Residential Food Management Interface Information System And Method |
US20140122487A1 (en) * | 2012-10-29 | 2014-05-01 | Elwha Llc | Food Supply Chain Automation Farm Testing System And Method |
US9704122B2 (en) | 2012-10-29 | 2017-07-11 | Elwha Llc | Food supply chain automation farm tracking system and method |
US20140122168A1 (en) * | 2012-10-29 | 2014-05-01 | Elwha Llc | Food Supply Chain Automation Residential Information System And Method |
US20140122296A1 (en) * | 2012-10-29 | 2014-05-01 | Elwha Llc | Food Supply Chain Automation Grocery Operations Interface Information System and Method |
US8886671B1 (en) | 2013-08-14 | 2014-11-11 | Advent Software, Inc. | Multi-tenant in-memory database (MUTED) system and method |
US10339619B2 (en) | 2015-08-25 | 2019-07-02 | Scott Arthur William Muirhead | Method and apparatus for presenting supply chain information to a consumer |
US20180075406A1 (en) | 2016-09-15 | 2018-03-15 | Bext Holdings, Inc. | Systems and methods of use for commodities analysis, collection, resource-allocation, and tracking |
WO2019246399A1 (en) * | 2018-06-20 | 2019-12-26 | Google Llc | Digital ledger for unique item ids with ownership |
US11276032B2 (en) | 2018-10-12 | 2022-03-15 | International Business Machines Corporation | Intelligent classification for product pedigree identification |
US11836656B2 (en) | 2019-09-06 | 2023-12-05 | International Business Machines Corporation | Cognitive enabled blockchain based resource prediction |
US11875304B2 (en) | 2020-06-29 | 2024-01-16 | Walmart Apollo, Llc | Methods and apparatus for grouping items |
US11481718B1 (en) * | 2020-09-08 | 2022-10-25 | Shellfish Solutions | System and methods for automatically tracking seafood |
US11669411B2 (en) | 2020-12-06 | 2023-06-06 | Oracle International Corporation | Efficient pluggable database recovery with redo filtering in a consolidated database |
US20220391822A1 (en) * | 2021-06-03 | 2022-12-08 | National Yunlin University Of Science And Technology | Traceability management method for supply chains of agricultural, fishery and animal husbandry products |
US20230245134A1 (en) * | 2022-02-02 | 2023-08-03 | Walmart Apollo, Llc | System and method for automatic product source tracing |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5117356A (en) * | 1989-07-28 | 1992-05-26 | Dns, Inc. | Automated ledger account maintenance system |
US5390113A (en) * | 1990-04-05 | 1995-02-14 | Sampson; Wesley C. | Method and electronic apparatus for performing bookkeeping |
US5478990A (en) * | 1993-10-14 | 1995-12-26 | Coleman Environmental Systems, Inc. | Method for tracking the production history of food products |
US20010051948A1 (en) * | 1998-12-07 | 2001-12-13 | Uppili Srinivasan | Method and system for representing and accessing object-oriented data in a relational database system |
US20020158765A1 (en) * | 1998-03-09 | 2002-10-31 | Pape William R. | Method and system for livestock data collection and management |
US6584453B1 (en) * | 1998-08-21 | 2003-06-24 | Oracle Corporation | Reversible move/merge operation for a general ledger |
US6668253B1 (en) * | 1999-09-08 | 2003-12-23 | Reynolds & Reynolds Holdings, Inc. | Enterprise information management system and methods |
US7120597B1 (en) * | 2000-12-27 | 2006-10-10 | Kermit Knudtzon | Computerized accounting systems and methods |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US158765A (en) * | 1875-01-12 | Improvement in lubricating-boxes | ||
US5315505A (en) * | 1987-08-12 | 1994-05-24 | Micro Chemical, Inc. | Method and system for providing animal health histories and tracking inventory of drugs |
US5157687A (en) * | 1989-06-29 | 1992-10-20 | Symbol Technologies, Inc. | Packet data communication network |
US5478970A (en) * | 1994-02-03 | 1995-12-26 | D. G. O'brien, Inc. | Apparatus for terminating and interconnecting rigid electrical cable and method |
US5673647A (en) * | 1994-10-31 | 1997-10-07 | Micro Chemical, Inc. | Cattle management method and system |
US6342839B1 (en) * | 1998-03-09 | 2002-01-29 | Aginfolink Holdings Inc. | Method and apparatus for a livestock data collection and management system |
US6446680B1 (en) * | 1998-09-30 | 2002-09-10 | Creative Edge Design Group, Ltd. | System for processing and packaging milk and other beverages |
US6377296B1 (en) * | 1999-01-28 | 2002-04-23 | International Business Machines Corporation | Virtual map system and method for tracking objects |
US20050261991A1 (en) * | 1999-10-12 | 2005-11-24 | Kennamer Jack J | Monitoring and tracking system and method |
US6629081B1 (en) * | 1999-12-22 | 2003-09-30 | Accenture Llp | Account settlement and financing in an e-commerce environment |
WO2001048651A1 (en) * | 1999-12-23 | 2001-07-05 | Encos Ltd | System and method for monitoring supply chains |
EP1299806A1 (en) * | 2000-06-01 | 2003-04-09 | Efarm, Inc. | Transactional supply chain system and method |
US7027975B1 (en) * | 2000-08-08 | 2006-04-11 | Object Services And Consulting, Inc. | Guided natural language interface system and method |
FR2813683B1 (en) | 2000-09-07 | 2003-01-17 | Lionel Guivarch | METHOD FOR MANAGING INFORMATION RELATING TO THE LIFE PATH OF A PLURALITY OF FOOD PRODUCTS |
US20020049643A1 (en) * | 2000-09-27 | 2002-04-25 | Church Diana L. | On-line ingredient exchange system and method |
GB2372346A (en) * | 2001-02-19 | 2002-08-21 | Moy Park Ltd | Tracing components of a production chain |
US7003759B2 (en) * | 2001-06-21 | 2006-02-21 | Codefast, Inc. | Collection makefile generator |
US20080077481A1 (en) * | 2002-02-07 | 2008-03-27 | Micro Beef Technologies, Ltd. | Livestock management systems and methods |
AU2003275489A1 (en) * | 2002-10-08 | 2004-05-04 | Food Security Systems, L.L.C. | System and method for identifying a food event, tracking the food product, and assessing risks and costs associated with intervention |
US6830010B2 (en) * | 2002-10-22 | 2004-12-14 | Heartland Premium Beef, Inc. | Quality assurance program and method for meat production |
US7026939B2 (en) * | 2003-02-10 | 2006-04-11 | Phase Iv Engineering, Inc. | Livestock data acquisition and collection |
-
2003
- 2003-04-22 AU AU2003225162A patent/AU2003225162A1/en not_active Abandoned
- 2003-04-22 EP EP03721873A patent/EP1504390A4/en not_active Withdrawn
- 2003-04-22 US US10/421,375 patent/US20030216979A1/en not_active Abandoned
- 2003-04-22 JP JP2003586713A patent/JP2005523507A/en active Pending
- 2003-04-22 WO PCT/US2003/012844 patent/WO2003090036A2/en active Application Filing
- 2003-04-22 US US10/421,630 patent/US8392225B2/en active Active - Reinstated
-
2013
- 2013-01-08 US US13/736,887 patent/US20130124375A1/en not_active Abandoned
-
2014
- 2014-02-13 US US14/180,123 patent/US20140172653A1/en not_active Abandoned
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5117356A (en) * | 1989-07-28 | 1992-05-26 | Dns, Inc. | Automated ledger account maintenance system |
US5390113A (en) * | 1990-04-05 | 1995-02-14 | Sampson; Wesley C. | Method and electronic apparatus for performing bookkeeping |
US5478990A (en) * | 1993-10-14 | 1995-12-26 | Coleman Environmental Systems, Inc. | Method for tracking the production history of food products |
US20020158765A1 (en) * | 1998-03-09 | 2002-10-31 | Pape William R. | Method and system for livestock data collection and management |
US6584453B1 (en) * | 1998-08-21 | 2003-06-24 | Oracle Corporation | Reversible move/merge operation for a general ledger |
US20010051948A1 (en) * | 1998-12-07 | 2001-12-13 | Uppili Srinivasan | Method and system for representing and accessing object-oriented data in a relational database system |
US6668253B1 (en) * | 1999-09-08 | 2003-12-23 | Reynolds & Reynolds Holdings, Inc. | Enterprise information management system and methods |
US7120597B1 (en) * | 2000-12-27 | 2006-10-10 | Kermit Knudtzon | Computerized accounting systems and methods |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050154628A1 (en) * | 2004-01-13 | 2005-07-14 | Illumen, Inc. | Automated management of business performance information |
US20050154769A1 (en) * | 2004-01-13 | 2005-07-14 | Llumen, Inc. | Systems and methods for benchmarking business performance data against aggregated business performance data |
US10304095B2 (en) * | 2008-02-04 | 2019-05-28 | Thomson Reuters Global Resources Unlimited Company | System and method for accounting gateway |
US9483799B2 (en) | 2010-07-12 | 2016-11-01 | Qvinci Software, Llc | Methods and apparatus for the aggregation of data |
US20120151411A1 (en) * | 2010-12-09 | 2012-06-14 | Oracle International Corporation | Mechanism to input, search and create complex data strings within a single dialog |
US9721040B2 (en) * | 2010-12-09 | 2017-08-01 | Oracle International Corporation | Mechanism to input, search and create complex data strings within a single dialog |
US20140101007A1 (en) * | 2012-10-04 | 2014-04-10 | Quickdash, Llc | Methods and apparatus for providing data normalization, scalability and maintainability |
US9858624B2 (en) * | 2012-10-04 | 2018-01-02 | Qvinci Software, Llc | Methods and apparatus for providing data normalization, scalability and maintainability |
US9600136B1 (en) * | 2013-03-11 | 2017-03-21 | Workday, Inc. | Data object extensibility |
US11625662B2 (en) | 2016-09-22 | 2023-04-11 | Qvinci Software, Llc | Methods and apparatus for the manipulating and providing of anonymized data collected from a plurality of sources |
Also Published As
Publication number | Publication date |
---|---|
AU2003225162A8 (en) | 2003-11-03 |
JP2005523507A (en) | 2005-08-04 |
WO2003090036A3 (en) | 2004-02-26 |
AU2003225162A1 (en) | 2003-11-03 |
WO2003090036A2 (en) | 2003-10-30 |
US8392225B2 (en) | 2013-03-05 |
US20130124375A1 (en) | 2013-05-16 |
US20140172653A1 (en) | 2014-06-19 |
US20030236768A1 (en) | 2003-12-25 |
EP1504390A2 (en) | 2005-02-09 |
EP1504390A4 (en) | 2007-10-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20030216979A1 (en) | Mutable general ledger account structure | |
US7143099B2 (en) | Historical data warehousing system | |
US7401094B1 (en) | Automated generation of dynamic data entry user interface for relational database management systems | |
Garg et al. | Roles and practices in management accounting today | |
US6839719B2 (en) | Systems and methods for representing and editing multi-dimensional data | |
US7191188B2 (en) | Method and apparatus for creating an adaptive application | |
US8428982B2 (en) | Monitoring business performance | |
US7853610B2 (en) | Virtual foldering system for blending process and content in a collaborative environment | |
US7788305B2 (en) | Hierarchy nodes derived based on parent/child foreign key and/or range values on parent node | |
DE102007011150B4 (en) | Method and system for managing data in a workflow process | |
US20050273352A1 (en) | Business method for continuous process improvement | |
US20040088650A1 (en) | Methods and apparatus for generating a spreadsheet report template | |
US20030061225A1 (en) | Hierarchical hybrid OLAP scenario management system | |
US20060224473A1 (en) | Adjustments to relational chart of accounts | |
US20060224617A1 (en) | Unstructured business metadata manager | |
US7720810B2 (en) | Synchronization of application documentation across database instances | |
US7398264B2 (en) | Simplifying movement of data to different desired storage portions depending on the state of the corresponding transaction | |
US7860869B2 (en) | Computer-implemented electronic diary to enter locked legal notes for historical archival | |
US20030061226A1 (en) | Data loader for handling imperfect data and supporting multiple servers and data sources | |
JP2023065627A (en) | Information processing system, information processing method, and information processing program | |
WO2005015460A1 (en) | Mutable general ledger account structure | |
US9400814B2 (en) | Hierarchy nodes derived based on parent/child foreign key and/or range values on parent node | |
US20060020642A1 (en) | Synchronization of application rules across database instances | |
US8185915B2 (en) | Meta-architecture for multi-tiered enterprise software application and system | |
Lenning | Drilling for information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |