The present invention is directed to the field of data modeling in the context of enterprise resources planning, supply chain management, warehouse management, and customer relations management, and more specifically to inventory management.
Manufacturers and suppliers of products use back-office computerized systems to provide support for functions in enterprise resources planning (ERP), supply chain management (SCM), and warehouse management (WMS). Such functions include manufacturing, marketing, inventory control, procurement and financing.
Also available are front-office computerized systems, which provide support to product vendors and distributors. In the context of inventory management, such front-office functions include analysis of historical customer demand for products, stocking and replenishment of inventory, and providing information resources for delivery of inventory and service to consumers. In order to take advantage of such front-office software computerized systems, their users typically must store data in forms usable by the front-office computerized system, which often differ significantly from the forms usable with back-office computerized systems.
Thus, when some or all aspects of inventory are managed by both back-office and front-office computerized systems, there is a need to synchronize the inventory information in both computerized systems. Generally, in order for front-office computerized systems to communicate with back-office computerized systems that are already being used, the user must manually regenerate data from the back-office computerized systems in forms usable by the front-office computerized systems, and vice versa. Such manual regeneration has several significant disadvantages, including: (1) it is often expensive; (2) it often requires a substantial amount of time to complete; (3) it must be repeated each time data changes in either the back-office system or the front-office system; and (4) it is prone to errors.
In view of the foregoing, an automated approach for transforming data used by a back-office computerized system for use by a front-office computerized system, and vice versa, is needed.
According to certain embodiments, the synchronization of inventory information addresses the needs of a company that deploys multiple computer applications, obtained from multiple vendors of computer applications, in the company's inventory management system. The synchronization operation provides a user of the inventory management system the same view of the inventory information across the various computer applications. All changes in the inventory information need to be captured and made accessible to all relevant computer applications in the inventory management system. For example, when an inventory item is received into inventory, shipped for an order, or has a change in its availability status (such as “reserved” status from “on hand” status), such inventory information need to be captured and made accessible to relevant computer applications in the inventory management system.
For purposes of explanation, assume that a company's inventory management system includes a front-office system for customer interfacing operations. Further, assume that the company's inventory management system also includes a back-office system that includes an inventory cost accounting application, for example. The computer applications of the front-office system uses a data model that is distinct from the data model used in back-office system's computer applications.
Inventory items are physically stored in a central distribution warehouse, at a field service office, in one or more field service engineer's trunk, or at a third party vendor's location. Assume that the various computer applications associated with inventory management used by the central distribution warehouse, the field service office, the field service engineer, and the third party vendor, are part of the front-office system. An inventory cost accounting application, for example, from the back-office system will need to share inventory information with the front-office system computer applications. Thus, a common data storage model is needed so that the various computer applications across the company's inventory management system can share the inventory information.
When a front-office call center receives an order from a customer, the call center can commit the availability of inventory parts and labor to the customer even though such inventory parts are stocked by different partners across a multiplicity of systems, only if the call center and the multiplicity of systems share inventory information. An important aspect to the inventory management is to ensure that the multiplicity of applications across the systems share the same inventory balance information. Thus, any inventory balance information that occurs in the front-office needs to be synchronized with that of the back-office.
Inventory balance implies the quantity available for a product (stock keeping unit) at an inventory location for a particular inventory level. A stock keeping unit is an instance of a product (part number) at an inventory location. An example of a stock keeping unit is “30 GB Hard Drive” at “Chicago Field Office”. Inventory level is also known as a product bucket. Inventory level is a classification of a stock keeping unit, based on its availability code and status code. Examples of availability codes are “on hand-good”, or “on hand-defective”, or “customer owned-good”, etc.
To explain, the synchronization of inventory balance information is the process of synchronizing the Inventory Balance information between the back-office systems (source systems or external systems) and the front-office systems (target systems). For purposes of explanation, the synchronization of inventory balance information is described with reference to the back-office systems as source systems or external systems and the front-office systems as target systems. The inventory balance information is stored per inventory location, per product, and per bucket in all the relevant systems. Synchronization is made possible by using an integration process that assumes that the application from the source system (source application) is the master of the inventory balance information, and will update the target inventory balance information to reflect the balance in the source system. The inventory balance information in the target system is updated by creating a transaction that will result in the right balance for the particular inventory location. For example, inventory balance is updated by committing an inventory transaction.
An inventory balance record contains the Inventory location Id, the inventory product Id, the bucket code, and the quantity of products available per bucket. The integration application process for synchronizing inventory balance information may be invoked at regular intervals by the source system in order to update the target system's Inventory Balance to reflect the source system's inventory balance information.
The inventory balance integration application process (IAP) includes the following operations:
The above inventory balance integration process occurs at periodic intervals when the inventory balances between inventory systems are not the same. There may be multiple reasons for the inventory balances between inventory systems to be different. For example,
In some cases, the back office system may be the system that performs inventory transactions and the front-office may be used to reflect the inventory balances. In that case, the back office application will pass the inventory balance to integration server. The integration server will convert the balance into an inventory transaction (after accounting for the difference between the current balance in the front-office versus the current balance in the back-office) and submit such a transaction to the front-office system's database. Thus, the inventory balance information in the front-office system (target system) is updated by generating an inventory transaction to account for the difference (delta).
Inventory balance information includes the source inventory location name, the product, and the balance of inventory. If the product is serialized, then a list of asset/serial number is specified. The number of assets specified is equal to the balance field. The integration server will request the current balance from the target application (which is an application of the front-office system). At that point, the integration server may lock the balance record so that no more changes can be made to the record until the synchronize inventory balance transaction complete. The integration server will compare the balances and create an inventory transaction for the delta.
The following is a process flow for synchronizing inventory balance information between source and target systems.
The following is the common object definition for Inventory Balance information, according to certain embodiments of the invention. The information that the common object for Inventory balance may include the following:
A software facility (hereafter “the facility”) for automatically converting inventory balance information, is described. In some embodiments, the facility converts inventory balance information from a form used by the source system to a form used by the target system. In certain embodiments, back-office systems are those that provide support for such functions as manufacturing, marketing, inventory control, procurement and financing. In certain embodiments, front-office system are those that provide support for such functions as analysis of historical customer demand for products, stocking and replenishment of inventory, and providing information resources for delivery of inventory and service to consumers, and sales.
In some embodiments, such as embodiments adapted to converting inventory balance information in the first source format, the facility converts inventory balance information by converting the inventory balance information that is in the first source format into an intermediate format. The intermediate format is then used to convert the inventory balance information into the target format.
By performing such conversions, embodiments of the facility enable a user of a first computerized system who has stored inventory balance information in a first format for use by the first computerized system to readily make the stored inventory balance information available for use in a second computerized system that utilizes a second format in a cost-efficient and time-efficient manner.
The facility (not shown) converts some or all inventory balance information that is in the source format into the target format by using an intermediate format of the inventory balance information. In certain embodiments, such conversions are performed with the aid of one or more other computer systems, such as integration server system 120. Components of the facility may reside on and/or execute on any combination of these computer systems, and intermediate results from the conversion may similarly reside on any combination of these computer systems.
The computer systems shown in
It will be understood by those skilled in the art that the facility may transform inventory balance information from a number of different source systems and from a number of different source software packages to a number of target systems and/or to a number of target software packages.
In
In
In
In
In
It will be appreciated by those skilled in the art that the above-described facility may be straightforwardly adapted or extended in various ways. For example, the facility may be used to transform various other kinds of inventory balance information, and may be used to transform inventory balance information between a variety of other formats.
In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. Thus, the sole and exclusive indicator of what is the invention, and is intended by the applicants to be the invention, is the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Any express definitions set forth herein for terms contained in such claims shall govern the meaning of such terms as used in the claims. Hence, no limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of such claim in any way. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
This application claims the benefit of U.S. Provisional Patent Application No. 60/457,434 filed Mar. 24, 2003, entitled, “INVENTORY BALANCE SYNCHRONIZATION AND COMMON OBJECT,” by Kahlon et al., and which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4714995 | Materna et al. | Dec 1987 | A |
5220500 | Baird et al. | Jun 1993 | A |
5311438 | Sellers et al. | May 1994 | A |
5349643 | Cox et al. | Sep 1994 | A |
5416917 | Adair et al. | May 1995 | A |
5446880 | Balgeman et al. | Aug 1995 | A |
5566332 | Adair et al. | Oct 1996 | A |
5646862 | Jolliffe et al. | Jul 1997 | A |
5699527 | Davidson | Dec 1997 | A |
5708828 | Coleman | Jan 1998 | A |
5724575 | Hoover et al. | Mar 1998 | A |
5727158 | Bouziane et al. | Mar 1998 | A |
5742588 | Thornberg et al. | Apr 1998 | A |
5758355 | Buchanan | May 1998 | A |
5764543 | Kennedy | Jun 1998 | A |
5806075 | Jain et al. | Sep 1998 | A |
5930156 | Kennedy | Jul 1999 | A |
5930764 | Melchione et al. | Jul 1999 | A |
5953710 | Fleming | Sep 1999 | A |
5970490 | Morgenstern | Oct 1999 | A |
5983194 | Hogge et al. | Nov 1999 | A |
6032136 | Brake et al. | Feb 2000 | A |
6053947 | Parson | Apr 2000 | A |
6167380 | Kennedy et al. | Dec 2000 | A |
6178418 | Singer | Jan 2001 | B1 |
6182053 | Rauber et al. | Jan 2001 | B1 |
6216130 | Hougaard et al. | Apr 2001 | B1 |
6226649 | Bodamer et al. | May 2001 | B1 |
6233566 | Levine et al. | May 2001 | B1 |
6236997 | Bodamer et al. | May 2001 | B1 |
6275812 | Haq et al. | Aug 2001 | B1 |
6336124 | Alam et al. | Jan 2002 | B1 |
6341289 | Burroughs et al. | Jan 2002 | B1 |
6343275 | Wong | Jan 2002 | B1 |
6377952 | Inohara et al. | Apr 2002 | B1 |
6385620 | Kurzius et al. | May 2002 | B1 |
6434567 | De La Huerga | Aug 2002 | B1 |
6463430 | Brady et al. | Oct 2002 | B1 |
6556950 | Schwenke et al. | Apr 2003 | B1 |
6569207 | Sundaresan | May 2003 | B1 |
6591260 | Schwarzhoff et al. | Jul 2003 | B1 |
6631382 | Kouchi et al. | Oct 2003 | B1 |
6668253 | Thompson et al. | Dec 2003 | B1 |
6681223 | Sundaresan | Jan 2004 | B1 |
6738975 | Yee et al. | May 2004 | B1 |
6754679 | Oheda | Jun 2004 | B2 |
6778651 | Jost et al. | Aug 2004 | B1 |
6792431 | Tamboli et al. | Sep 2004 | B2 |
6826542 | Virgin et al. | Nov 2004 | B1 |
6826568 | Bernstein et al. | Nov 2004 | B2 |
6828963 | Rappoport | Dec 2004 | B1 |
6883004 | Bahl et al. | Apr 2005 | B2 |
6889260 | Hughes | May 2005 | B1 |
6898783 | Gupta et al. | May 2005 | B1 |
6912719 | Elderon et al. | Jun 2005 | B2 |
6944514 | Matheson | Sep 2005 | B1 |
6947947 | Block et al. | Sep 2005 | B2 |
6961760 | Li et al. | Nov 2005 | B2 |
6996776 | Makely et al. | Feb 2006 | B1 |
7013485 | Brown et al. | Mar 2006 | B2 |
7043687 | Knauss et al. | May 2006 | B2 |
7062540 | Reddy et al. | Jun 2006 | B2 |
7065499 | Seth et al. | Jun 2006 | B1 |
7085729 | Kennedy et al. | Aug 2006 | B1 |
7093200 | Schreiber et al. | Aug 2006 | B2 |
7099350 | Peterson | Aug 2006 | B2 |
7111010 | Chen | Sep 2006 | B2 |
7111077 | Starkovich et al. | Sep 2006 | B1 |
7124112 | Guyan et al. | Oct 2006 | B1 |
7133882 | Pringle et al. | Nov 2006 | B1 |
7139766 | Thomson et al. | Nov 2006 | B2 |
7143100 | Carlson et al. | Nov 2006 | B2 |
7162540 | Jasen et al. | Jan 2007 | B2 |
7257594 | Tamboli et al. | Aug 2007 | B2 |
7257820 | Fischer et al. | Aug 2007 | B2 |
7287041 | Barnes-Leon et al. | Oct 2007 | B2 |
7337192 | Stark et al. | Feb 2008 | B2 |
7349861 | Fischer et al. | Mar 2008 | B1 |
7370009 | Notani et al. | May 2008 | B1 |
7412404 | Tenorio | Aug 2008 | B1 |
7680818 | Fan et al. | Mar 2010 | B1 |
20010011245 | Duhon | Aug 2001 | A1 |
20010051907 | Kumar et al. | Dec 2001 | A1 |
20020007343 | Oyama et al. | Jan 2002 | A1 |
20020019765 | Mann et al. | Feb 2002 | A1 |
20020023004 | Hollander et al. | Feb 2002 | A1 |
20020035431 | Ell | Mar 2002 | A1 |
20020035488 | Aquila et al. | Mar 2002 | A1 |
20020040313 | Hunter et al. | Apr 2002 | A1 |
20020040339 | Dhar et al. | Apr 2002 | A1 |
20020085020 | Carroll, Jr. | Jul 2002 | A1 |
20020095456 | Wensheng | Jul 2002 | A1 |
20020116234 | Nagasawa | Aug 2002 | A1 |
20020123983 | Riley et al. | Sep 2002 | A1 |
20020133510 | Lau | Sep 2002 | A1 |
20020138582 | Chandra et al. | Sep 2002 | A1 |
20020169863 | Beckwith et al. | Nov 2002 | A1 |
20020169867 | Mann et al. | Nov 2002 | A1 |
20020174417 | Sijacic et al. | Nov 2002 | A1 |
20020178077 | Katz et al. | Nov 2002 | A1 |
20020184085 | Lindia et al. | Dec 2002 | A1 |
20020184148 | Kahn et al. | Dec 2002 | A1 |
20020188513 | Gil et al. | Dec 2002 | A1 |
20020188538 | Robertson et al. | Dec 2002 | A1 |
20030014440 | Bussert et al. | Jan 2003 | A1 |
20030018502 | Rodriguez | Jan 2003 | A1 |
20030023580 | Braud et al. | Jan 2003 | A1 |
20030033437 | Fischer et al. | Feb 2003 | A1 |
20030071852 | Stimac | Apr 2003 | A1 |
20030097642 | Arai et al. | May 2003 | A1 |
20030110104 | King et al. | Jun 2003 | A1 |
20030131018 | Godoy et al. | Jul 2003 | A1 |
20030163597 | Hellman et al. | Aug 2003 | A1 |
20030163603 | Fry et al. | Aug 2003 | A1 |
20030229529 | Mui et al. | Dec 2003 | A1 |
20040002982 | Ersek et al. | Jan 2004 | A1 |
20040015515 | Beisiegel et al. | Jan 2004 | A1 |
20040034661 | Barron et al. | Feb 2004 | A1 |
20040039576 | He et al. | Feb 2004 | A1 |
20040093351 | Lee et al. | May 2004 | A1 |
20040122826 | Mackie | Jun 2004 | A1 |
20040128188 | Leither et al. | Jul 2004 | A1 |
20040162773 | Del Rey et al. | Aug 2004 | A1 |
20040199536 | Barnes Leon et al. | Oct 2004 | A1 |
20040215503 | Allpress et al. | Oct 2004 | A1 |
20040249854 | Barnes-Leon et al. | Dec 2004 | A1 |
20050021383 | Fliess et al. | Jan 2005 | A1 |
20050021391 | Lu et al. | Jan 2005 | A1 |
20050091249 | Hanson et al. | Apr 2005 | A1 |
20050160361 | Young | Jul 2005 | A1 |
20050197880 | Walsh et al. | Sep 2005 | A1 |
20060271446 | Barnes-Leon et al. | Nov 2006 | A1 |
20070033531 | Marsh | Feb 2007 | A1 |
20070203710 | Habichler et al. | Aug 2007 | A1 |
20070208577 | Barnes-Leon et al. | Sep 2007 | A1 |
20070208878 | Barnes-Leon et al. | Sep 2007 | A1 |
20070214020 | Srinivasan et al. | Sep 2007 | A1 |
20070214063 | Kahlon et al. | Sep 2007 | A1 |
20070214064 | Kahlon et al. | Sep 2007 | A1 |
20070214065 | Kahlon et al. | Sep 2007 | A1 |
20070225949 | Sundararajan et al. | Sep 2007 | A1 |
20070226037 | Garg et al. | Sep 2007 | A1 |
20070226049 | Muralitharan et al. | Sep 2007 | A1 |
20070226093 | Chan et al. | Sep 2007 | A1 |
20070250408 | Barnes-Leon et al. | Oct 2007 | A1 |
20070250419 | Kumar et al. | Oct 2007 | A1 |
20070265944 | Catahan, Jr. et al. | Nov 2007 | A1 |
Number | Date | Country |
---|---|---|
101 50 391 | May 2002 | DE |
2001 256308 | Sep 2001 | JP |
WO 0143031 | Jun 2001 | WO |
WO 0188759 | Nov 2001 | WO |
WO 03003641 | Jan 2003 | WO |
Entry |
---|
“Cross Access Introduces SERIESfour; Offers Native, Fast, Scalable Legacy Data Connectivity for Data Marts, ERP Applications,” PR Newswire; New York; Jan. 18, 1999; pp. 1-3. Downloaded from http://proquest.umit.com. |
Hardwick, Martin, David L. Spooner, Rom Rando, and K.C. Morris, “Sharing Manufacturing Information in Virtual Enterprises;” Communication of the ACM; vol. 39, No. 2; Feb. 1996; pp. 46-54. Downloaded from http://delivery.acm.org. |
Kappelhoff, Ralph, “Integration of ERP to the Final Control Elements;” ISA Transactions; 1998; vol. 36, No. 4; pp. 229-238. Downloaded from http://www.sciencedirect.com. |
Nori, Anil K. et al., “Bringing Objects to the Mainstream,” Compcon Proceedings, IEEE San Jose, California, Feb. 23-26, 1997, pp. 136-142. |
PTC: Siebel Systems and PTC create strategic alliance to leverage enriched information across product development, sales and service; Combination of Siebel eBusiness Applications and PTC Collaborative Product Development solutions to deliver competitive advantage, M2 Presswire, Conventry: Jan. 24, 2002, 3 pages (retrieved from ProQuest.com). |
Wilson, J.R., “Aerospace Looks for Lift from e-commerce,” Intervia, Geneva, Jul./Aug. 2001; vol. 56, Issue 655, 6 pages (retrieved from ProQuest.com). |
XML/EDI Group. “Guidelines for using XML for Electronic Data Interchange.” Presented at XML One-San Jose, Sep./Oct. 2001. Downloaded from http://web.archive.org/web/20040413182700/http://www.xmledi-group.org/. |
NPL—XML—Schema—CE.pdf, A tutorial published by the SML governing body of w3.org regarding the use of SML Schemas and Complex Data Elements. Downloaded on Jun. 10, 2009 from http://www.w3schools.com/Schema/schema—intro.asp? and http://www.w3schools.com/Schema/schema—complex.asp? and http://www.w3.schools.com/Schema/schema—complex—empty.asp?;7 pages. |
Routledge et al., UML and XML Schema, 2002, pp. 1-10. |
Walter J. Savitch, “Java an Introduction to Computer Science & Programming,” 2000, p. 478. |
Walter J. Savitch, “Java an Introduction to Computer Science & Programming,” 2000, pp. 458-467. |
Walter J. Savitch, “Java an Introduction to Computer Science & Programming”, 2000, p. 1. |
“Fortis Investments Implements Unified Employee Management System Across 12 Countries” (Business Wire, Jul. 2004). |
“Extract Simplifies File Conversion” Software Markets, Dec. 2, 1991. Retrieved via Dialog on Aug. 16, 2010. |
Cover Pages “Siebel's Universal Application Network” Apr. 8, 2002 downloaded from xml.coverpages.org May 6, 2010. |
Cover Pages “Siebel Announces Success with Universal Application Network (UAN)” Apr. 21, 2004 downloaded from xml.coverpages.org May 6, 2010. |
Michael Kay, Editor “XSL Transformations (XSLT) Version 2.0 W3C Working Draft May 2, 2003” downloaded from http://www.w3.org/TR/2003/WD-xslt20-20030502/ May 6, 2010. |
Eric Gropp “Transforming XML Schemas” Jan. 15, 2003; downloaded from xml.com May 6, 2010. |
Sonic Software Corporation, Power Schemas With Stylus Studio™; Jan. 2004. |
Number | Date | Country | |
---|---|---|---|
20070214063 A1 | Sep 2007 | US |
Number | Date | Country | |
---|---|---|---|
60457434 | Mar 2003 | US |