MXPA06004908A - Serialized inventory control system and method - Google Patents

Abstract

Systems and techniques for tracking inventory include a serialized inventory control system configured to receive serialized information, apply validation rules to the serialized information, flag exceptions to the validation rules, and report the exceptions. The serialized inventory control system includes database logic to check that that serialized information does not exist for an entering inventory item and that serialized information does exist for an exiting inventory item.

Description

SYSTEM AND METHOD FOR THE CONTROL OF SERIALIZABLE INVENTORIES FIELD OF THE INVENTION The present invention generally relates to systems and techniques for tracking entities and, most particularly, to a system and method for tracking serial numbers or other discrete items.

BACKGROUND OF THE INVENTION In a product distribution environment, it is common for a company to track the movement and inventory status. For effective inventory control, a company must generally have the ability to collect inventory information for each item, review the current status of an item in its life cycle, issue and track the status of purchase orders and work orders , monitor production and distribution, and provide stock adjustments. The accuracy and availability of such inventory information is vital since carriers, customers, operations and various areas of the company typically rely on such information to report purposes, as well as to make business decisions in the short and long term. The Enterprise Resource Planning (ERP) systems have been developed in an attempt to integrate, manage and analyze information for companies. In general, an ERP system can also control inventories by providing information online and / or real time, data standardization, analysis and reporting capabilities that can be used by a company to produce efficiencies and optimize operations. In some cases, the ERP system can gather data from various sources such as manufacturers, distributors, suppliers and customers and use that information for financial planning, accounting, human resource allocation, ercadotecnia and / or manufacturing. ERP systems typically run as off-the-shelf software packages installed on database platforms (eg, Oracle, MS SQL Server, SQLBase, Sybase, SAP, DB2 / 400, DB2 / MVS, DB2 / Unix, Informix). Although existing ERP systems can be offered with different sets of functions and can allow a certain degree of personalization, in many cases, these ERP systems are inadequate to meet the precise requirements of particular industries.

In the telecommunications industry, for example, a vast amount of information is associated with the distribution of subscriber equipment. In particular, a wireless telephone equipment may be associated with serialized information such as an Electronic Serial Number (ESN), i.e., a unique identification number integrated into a microchip in the manufacturer's equipment. Typically, the ESN is transmitted when a call is placed and verified electronically to prevent fraudulent use of the equipment. Other serialized information may also be associated with the equipment such as, for example, an International Mobile Equipment Identification (IMEI), a mobile identification number (MIN), one or more unlock codes for the equipment, one or more codes of Subscriber Information Module (SIM) card. In addition, a finished equipment assembly may consist of several basic components (e.g., speakers, microphones, keyboards, displays, tones, processors, chip sets, memories, displays, batteries) and aggregate components (e.g., communication devices). , cameras, location technologies, media players), each one associated with its own serialized information. Therefore, the administration of any significant volume of inventories in the telecommunications industry requires dealing with the exponential growth in the administration of serialized information. However, ERP systems do not provide the scalability necessary to manage and effectively coordinate the millions of serialized transactions handled by distributors every month. Specifically, due to the size and growth of the transaction volume, the mainframe architecture of existing ERP systems can not support the tracing of serialized information such as ESN. Accordingly, there is a need for systems and methods to accurately track a large number of serialized items in the telecommunications industry and other environments.

SUMMARY OF THE INVENTION In a general aspect, systems and techniques to track inventories include a signaling inventory control system configured to receive serialized information, apply validation rules to serialized information, indicate exceptions to validation rules, and report exceptions. The serialized inventory control system includes database logic to check that serialized information does not exist for an inbound inventory item and that serialized information does not exist for an existing inventory item. Aspects of the present invention can be executed by means of an apparatus and / or a computer program stored in a computer readable medium. The computer readable medium can comprise a disk, a client device, a network device, a host device, and / or a propagated signal. Other features and advantages will be apparent from the following description, including the figures, and the claims.

BRIEF DESCRIPTION OF THE FIGURES Figure 1 illustrates one embodiment of a communication system according to the present invention. Figure 2 illustrates one embodiment of a communication system in accordance with the present invention. Figure 3 illustrates one embodiment of a communication system according to the present invention. Figure 4 is a flow chart of a method embodiment according to the present invention.

DETAILED DESCRIPTION OF THE INVENTION Figure 1 illustrates one embodiment of an exemplary communications system to automatically present a visual representation showing a relationship between entities involved in a commercial deal. To summarize, several elements in the figure are represented as monolithic structures. However, it will be understood that each structure may include numerous interconnected computing elements and / or components designed to operate in accordance with aspects of the present invention. As shown, the communication system includes a client system 10 connected through a network 15 to a guest system 20. The client system 10 and the guest system 20 are configured to communicate and exchange information through the network 15. The guest system 20 may include and / or be part of an information delivery network, such as, for example, the Internet, the World Wide Web, an online service provider, a private network, and / or any other digital and / or analog wireless and / or wired network that provides information. In general, the client system 10 includes a computer system that has hardware and / or software components to connect to the network 15 and the guest system 20. The client system 10 and the guest system 20 can each include , one or more computing systems and can be structured and accommodated to establish communication using various communication protocols to establish connections between the network elements and / or to operate within or in coordination with one or more different systems (for example, the Internet and / or Network). In one embodiment, the client system 10 and the host system 20 each include one or more devices operating under the command of a controller (e.g., client controller 11, guest controller 21). Dashed lines are to indicate that in some executions, the controller, or parts thereof considered collectively, may command one or more elements of the systems to operate as described. Accordingly, the functions described in the present invention can be executed as software that controls one or more elements of the client system 10 and / or the host system 20. An example of a device is a general-purpose computer with the ability to respond a, and execute instructions in a defined way. Other examples include a special purpose computer, a personal computer (PC), a workstation, a server, a laptop, a network-enabled telephone, a personal digital enabled assistant (PDA), a microprocessor, an integrated circuit, or any other component, machine , tool, equipment or some combination thereof with the ability to respond to, and execute instructions. An example of a driver is a program or software application installed on one or more devices. Other examples include codes, sets of instructions, signals or some combination thereof to provide instructions independently or collectively. The controller can be executed using any convenient computing language and / or object-oriented techniques. The controller can also be a device (for example, a workstation or PC, a microprocessor, a network server, a Java virtual machine, or a specific application integrated circuit) and can be incorporated permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of delivering instructions. In particular, the controller (e.g., computer program, software application) can be stored in a storage medium (e.g., disk, device, propagated signal), so that if a storage medium is read by a system of computation, the functions described in the present invention are executed. The network 15 may include one or more delivery systems for directly or indirectly connecting the client system 10 and the host system 20. Examples of delivery systems include, but are not limited to, a local area network (LAN), a Wide area network (WAN), the Internet, the Network, a telephone network, a radio network, a television network, a cable network, a satellite network, and / or any other wired or wireless communications network configured to carry data Each network, in turn, may include elements, such as, for example, intermediate nodes, proxy servers, firewalls, routers, switches, adapters, outlets, and wired or wireless data paths, configured to direct and / or provide data. . In one embodiment, host system 20 is configured to accurately track a high volume (for example, 2 million units per month) of serialized information. Examples of serialized information include, but are not limited to: a Number of Electronic Series (ESN), an International Mobile Equipment Identification (IMEI), a mobile identification number (MIN), an unlock code for the equipment, a Subscriber Information Module (SIM) card code, a number standard of a finished equipment assembly, a serial number of a basic component (for example, speakers, microphones, keyboards, screens, tones, processors, chipsets, memories, displays, batteries) and an aggregate component (for example , communication devices, cameras, location technologies, multimedia players), of a finished equipment, immigration information (for example, visa) and / or information on hotel transactions (for example, payment reservation). In one execution, host system 20 may be designed as a discrete entity tracking system for managing a large volume of serial numbers encountered when managing wireless equipment products. The guest system 20 can track the movement and status of articles and communicate information to manufacturers, distributors, carriers, customers, operations and other areas of the company and partners. Other potential uses of this technology include, but are not limited to, tracking "entries" and "exits" of people entering and leaving a country (for example, tracking visa information) and reconciling or eliminating a high number of complex situations payable-to / payable-that occur in the hotel industry. As shown in figure 1, host system 20 contains three layers of system: a system of Enterprise Resource Planning (ERP) 22 (for example, Solo on IV V4.21), a system of Serialized Inventory Control (SIC). ) 23, and a Manufacturing system 24 (eg, VAIK, ABC, SNDB). Typically, the systems will employ a common database platform (for example Server 2000 MS SQL) with business logic that resides in the appropriate modules. In general, the modules can be executed as hardware and / or software to execute the operations described below. It will be understood that although some components of the host system 20 are shown as monolithic structures, each may include numerous elements (e.g., servers, routers, switches, firewalls, outlets, databases, tables, disks, hard disk drive, etc.) in various modalities. In general, the ERP system 22 can be configured to cover information on cost and quantity of inventories, while the SIC system 23 can be configured to maintain serialized information. The manufacturing system 24 can be configured to incorporate business rules and manage operational manufacturing steps (compliance) for a particular industry or technology.

The control of the serialized information with the SIC system 23 allows the ERP system 23 and the manufacturing system 24 to remain substantially independent. In one embodiment, the SIC system 23 is linked, or otherwise integrated, with the ERP system 22 and the manufacturing system 24 (e.g., VAIK, ABC, SNDB). For example, the SIC system 23 can function as a third-party vertical alignment software service that integrates the ERP system 22 and the manufacturing systems 24 to allow an infinitely scalable platform for the management of "inputs" and "outputs" of numbers. series or other discrete items. Although the ERP system 22, the SIC system 23 and the manufacturing system 24 are tightly integrated, said systems can still be considered substantially independent in terms of process. That is, the interfaces between the systems are configured to complement and not interfere with the functionality of the others. In an execution, the SIC system 23 may include interfaces and / or tables for retrieving information from, moving information to, and / or processing information from the ERP system 22 and the manufacturing system 24. The SIC 23 system can maintain a perpetual record for all transactions of receipt and disbursements for both physical and virtual inventory items. The SIC 23 system can also track site and location data and other cost generating information as indicated by business needs. The SIC 23 system can employ referential integrity constraints at the database level to handle large volumes of transactions. SIC 23 can maintain a sum of serialized numbers corresponding to the balances of stock items covered by the ERP 22. The serial number records managed by the SIC 23 system can provide details that support the quantity and costs of the inventory in the ERP system 23. In one execution, the ERP system 22 initiates and implements operating procedures that involve the financial cycle (ie General Ledger Book, Accounts Receivable, Accounts Payable, Cash Money Manager) and the distribution cycle (ie Sales, Inventory) of items in inventory. Examples of transactions that can be covered by the ERP system 22 include, but are not limited to: Purchase Order Receipts (PO), PO Returns, Inventory Receipts, Manufacturing (fulfillment), Transfers, Activations, Adjustments, Sales and / or Sales Returns (RFC). To support such transactions, the systemERP 22 can transfer inventory information (for example, purchase data, cost data, accounts payable data, sales data, accounts receivable data, and / or balance data) to one or more financial modules.

Referring to Figure 2, one embodiment of the ERP system 22 includes a plurality of financial modules that include a purchase module 220, an inventory module 222, and an order management module 224. The purchase module 220 can be configured to cover receipts and returns of purchase orders. In this mode, the purchase module 220 allows a user to generate a purchase order, enter the receipt of the purchase order, and enter the purchase order refunds. A purchase order can have data fields including, for example: Item ID, Contract Quantity (Qty), Unloading Cost, Vendor, and Agreed Date. For existing purchase orders and purchase order receipts, a user can enter a negative PO receipt in the purchase module 220 to indicate a purchase order return. The purchase module 220 can also allow a user to update and save data. The inventory module 222 can be configured to cover the inventory receipt, inventory transfer, inventory activation, and inventory adjustments. In this mode, the inventory module 222 is responsible for maintaining the status of the cost, location and quantity (for example, Qty in PO, Qty in Production, Inactive, Damaged and Available for Sale) of inventory items. The inventory module 222 may allow a user to adjust the inventory (eg, by lot) by filling in the data fields including, for example: Article Id, quantity (with a +/- sign to indicate adjustment), cost ( with a +/- sign to indicate adjustment), site, cube location and date. The inventory module 222 may also allow a user to transfer inventory by filling in the data fields that include, for example: Article Id, quantity, DE and PARA information (site and cube) and date. To activate the inventory, that is, transfer an inventory lot from an inactivated cube to an activated cube, the inventory module 222 can display a screen that allows a user to identify the site and location of the inactive cube and then automatically define a active cube The order management module 224 can be configured to cover manufacturing (compliance) procedures as well as sales and sales returns. In this embodiment, the order management module 224 allows a user to create and update a work order. The data fields of a work order can include, for example: product, planned quantity to produce, date and site (carrier). The order management module 224 can display a screen corresponding to a particular consignor that allows a user to print a work order, register a work order with a manufacturing module, confirm the movement of the inventory from a warehouse to a work area. production, and / or verify the location of the inventory (for example, the bucket). The order management module 224 may also allow a user to create a sales order and / or a sales return by filling in the data fields including, for example: Items, planned quantity to send, date, site and cube location. In one execution, the SIC system 23 maintains the serialized information for transactions involving the entry of items into a system, and the output of items from a system. The SIC 23 system monitors incoming transactions and outgoing transactions and tracks the net balance of inventories within the system. Records are created and updated as articles enter and leave the system on an approximate real-time basis. The SIC 23 system includes logic to verify that serialized information does not exist for an inventory item that has just entered the system and that there is serialized information for an inventory item that is leaving the system. The SIC 23 system provides real-time audit and exception monitoring for components as well as for finished goods.

Referring to Figure 2, one embodiment of the SIC system 23 includes a database structure 230, a production interface 240, a Serial Number System Data Entry Application (SNS), an ENTER_SET procedure 260, a INPUT_DoOR agent 270, and a report generation interface 280. In general, the database structure 230 can be configured to store values belonging to serial number transactions. The production interface 240 can be configured to be integrated with, and manage information from a manufacturing system 24. The SNS 250 Data Entry Application can be configured to allow a user to record the serial number data in various ways . The END ENTRY procedure 260 can be configured to update and / or verify the integrity - of the serialized recorded information (for example, for a given inventory lot or consignor in the ERP system 22). The PUERT_ENTER 270 agent can be configured to look up records available in the database structure 230 and the ERP system 22. The report generation interface 280 can be configured to create and modify reports. Figure 3 illustrates a modality of a database structure 230 which includes a table SNS_UnÍc? 231, a SEND_WRIGHT_DISK 232 box, a SEND_WRIGHT_POST 233 box, a RECEIVE_WRIGHT_INTERDAY 234, a RECEIVE_TRABAJO_FUERA 235, an SNS_DENTRO 236, a SNS_FUERA 237, and an SNS_MST 238 table. The SNS_Unico 231 box can be configured to ensure that it is not have scanned and returned two identical items at the same time. The SEND_TRABAJO_DENTRO 232 box can be configured to save values for serial number transactions. In this mode, the SEND_WRAP_INTERDAY box 232 can save the values of each serial number transaction, including: the batch number, module, type, line number, item, serial number, sign and status. The SEND_WRAPDAY_INTERDAY box 232 can store the positive data entries (for example, new Serial Numbers) of the Data Entry Application 250 and / or the production applications interface 240. The SEND_WRITER_DISK 232 box can save these values, rather than are moved to the SNS_DENTRO 236 box by the PUERT_ENTRADA_SNS 270 agent, when the appropriate conditions are met. The SEND_TRABAJO_FUERA 233 box can be configured to save values for serial number transactions. In this mode, the SEND_TRABAJO_FUERA 233 box can store the values of each serial number transaction, including: the batch number, module, type, line number, article, serial number, sign and status. The SEND_WATER_FILTER table 233 can store the negative data entries (for example, Discarded Serial Numbers) of the Data Input Application 250 and / or the production applications interface 240. The SEND_WRITE_FIT 233 box can save these values, rather than are moved to the SNS_FUERA 237 box by the PUERT_ENTRADA_SNS 270 agent, when the appropriate conditions are met. The RECEIVE_TRABAJO_DENTRO 234 box can be configured to save values for serial number transactions. In this mode, the RECEIVE_TRABAJO_DENTRO 234 box can store the values of each serial number transaction, including: the batch number, module, type, line number, item, serial number, sign, and status. The RECEIVE JOB_INTERDAY 234 box can store the positive data entries (for example, new Serial Numbers) of the SNS Data Entry Application 250 and / or the production applications interface 240. The RECEIVE_TRABAJO_DENTRO 234 box can save these values, before they are moved to the box SNS_DENTRO 236 by the agent of PUERTA_ENTRADA_SNS 270, when the appropriate conditions are met.

The RECEIVE_TRABAJO_FUERA table 235 can be configured to store values for serial number transactions. In this modality, the table RECEIV_TRABAJO_FUERA 235 can save the values of each serial number transaction, including: the batch number, module, type, line number, article, serial number, sign and status. The RECEIVE_TRABAJO_FUERA 235 table can store the negative data entries (for example, Discarded Serial Numbers) of the SNS Data Entry Application 250 and the production applications interface 240. The RECEIVE_TRABAJO_FUERA 235 box can save these values, before they are moved to the SNS_FUERA 237 box by the agent of PUERTA_ENTRADA_SNS 270, when the appropriate conditions are met. The SNS_DENTRO 236 box can be configured to store values for serial number transactions. In this mode, the table SNS_DENTRO 236 is a transactional table that stores values for positive transactions (for example, new Serial Numbers) moved from the box SEND_TRABAJO_DENTRO 232 and / or the table RECEIVES_TRABAJO_DENTRO 234 by the agent of PUERTA__ENTRADA_SNS 270 when they comply with the appropriate conditions. The frame structure can be based on the values of a transactional frame and can maintain them (for example, transactional LotSerT frame) in the ERP system 22. The frame SNS_DENTRO 236 can save reference data. The reference data can link the SNS_DENTRO 236 chart to the SNS_FUERA table 237 to track the disposition or movement of an inventory item. The SNS_FUERA 237 box can be configured to store values for serial number transactions. In this mode, the table SNS_FUERA 237 is a transactional table that stores the negative transactions (for example, discarded Serial Numbers) moved from the SEND_WRAP_FLOOR table 233 and / or the RECEIVE_TRABAJO_FUERA 235 table by the agent of PUERTA_ENTRADA_SNS 270 when the conditions are met appropriate. The frame structure can be based on the values of a transactional frame and can maintain them (for example, transactional LotSerT frame) in the ERP system 22. The frame SNS_FUERA 237 can save reference data. The reference data can link the SNS_DENTRO 236 chart to the SNS_FUERA table 237 to track the disposition or movement of an inventory item. The SNS_MST 238 box can be configured to store values for serial number transactions. In this mode, the SNS_MST 238 box can save scanned serial numbers or, otherwise, be entered into the system. The SNS_MST can save real and previous serial numbers (for example, historical table) for items that are part of the inventory at a given time. In an execution, the SNS_MST 238 box can be used to validate the existence of serialized information. The frame structure can be based on the values of a transactional frame and can maintain them (eg LotSerMST frame) in the ERP system 22. Referring again to FIG. 2, one mode of the SIC 23 system includes a production interface 240 to be integrated with a manufacturing system 24. In general, the production interface 240 can be configured to execute one or more processing related to the manufacturing (compliance) operational phases. The production interface 240 can execute a work order start verification procedure. For example, a work order (WO) may not start production on the store floor without first having been created and activated in the ERP system 22. In one execution, the manufacturing system 24 may use the production interface 240 for ensure the availability of WO. The production interface 240 can execute a serial number validation procedure. For example, the manufacturing system 24 can use the production interface 240 to verify and validate the existence of the serial number in the SIC system 23 (for example, the SNS_MST 238 table). In the execution, the functionality of the manufacturing system 24 can be suspended if errors are found until a supervisor cancels the error review and allows production to continue. The production interface 240 may include a production output procedure. For example, instead of exporting data to the transport operators at the end of a production run, the manufacturing system 24 can save the production output data in an SNS work box. Production output data can include the following information: serial numbers of discarded items (for example, components) and the serial number for the final product (for example, packaging), and the production date. The production interface 240 can execute a device definition procedure. For example, the manufacturing system 24 may require sufficient flexibility to operate with various equipment definitions (for example, components that are required to assemble a finished package). In one execution, the equipment definitions can be maintained in one system (for example, the ERP system 22) and shared with the other systems (for example, the SIC system 23 and the manufacturing system 24). Referring again to Figure 2, one embodiment of the SIC system 23 includes a SNS Data Entry Application 250. In general, the SNS Data Entry Application 250 can be configured to allow a user to record the serial number data in several ways. For example, the SNS Data Entry Application 250 can register serial numbers that are entered manually and / or scanned manually. The SNS Data Entry Application 250 can also record serialized information through the import of files (for example, .csv files) or through the reception of a work order number or group number (for example, Master Box ID) ) and then automatically filling in the corresponding serial numbers. In one execution, the SNS DataInput Application 250 may include a user interface (eg, Basic Visual display) to record the serialized information. In general, the SNS Data Entry Application 250 can be developed using modular development rules and can be designed to be fault tolerant. In one embodiment, the SNS Data Entry Application 250 includes a header / detail screen (grid). The portion of the screen header can capture the identification of the information to be recorded. The header may include data fields such as, for example: type of transaction procedure or inventory that requires serial number identification (for example, Receipt, Purchase Return, Equipment Assembly, Transfer, Activation, Adjustment, Sale or Refund of Sale), lot number, line number, inventory item, number of serial numbers required to be entered, site ID, and location ID. The inventory item, quantity, site ID, and location ID fields can be reference fields populated after the line number selection. The detail part of the screen may include a grid to record the serial numbers. In some modes, the screen allows you to enter only the quantity of items that is defined by the quantity for the selected line number. In an execution, the grid includes the following fields: item number, serial number and master box (at the time of receipt) to allow users to group the serial numbers. The SNNS_Data Input_Application 250 should generally support the selection of data for the header fields, based on the previous selected fields. In some executions, the screen can only accept the registration of serial numbers for valid Batch and / or consignors in the appropriate state, as defined in the processing rules. In one execution, the Application of Input_Data_SNS 250 is configured to apply the validation rules to the data entered. The validation rules may include a mask that requires all the serialized information to comply with some data field definitions for the data type (eg, numeric, hexadecimal) and length. Validation rules also require that there be no duplicates. For example, when new items are registered (for example, receptions, production - finished items, positive adjustments, sales returns) the SNS_Snats_Input_App 250 Application can verify that the serial numbers do not exist as available in the SNS_MST 238 table. The rules Validation may also require existence. For example, when items are discarded (for example, Purchase Returns, Production - Components, Negative Settings, Sales), the SNS_Data Input_Information 250 Application can check that those serial numbers exist as available in the SNS_MST 238 box. In one modality, the Application Input_Data_SNS 250 saves the data in work tables (for example, the table WORK_DENTRO_SNS 232, the table WORK_FUERA_SNS 233) according to the sign of transaction. The Application of Data_Input_SNS 250 may require the confirmation of the user before saving the data in the work tables. When the last line number of a specified batch or consignor has been entered (and confirmed), SNS_Source_Application Application 250 triggers the TERMINATE_INSTALLED_SNS procedure 260. As shown in Figure 2, a SIC 23 system mode includes a TERMINATE_INSTALLED_SNS procedure 260 In general, the TERMINATE_INSTALLED_SNS procedure 260 can be configured to update and / or review the integrity of the serialized information recorded for a given inventory or consignor batch in the ERP system 22, for example. In one execution, the procedure Terminate_Entry_SNS 260 can be triggered by the Input SNS Data Entry 250 or a manufacturing module after serialized information is recorded for a given batch or consignor. When it is triggered by the Input Application_Datas SNS 250 (for example, Receipts, Purchase Returns, Transfers, Activations, Adjustments, Sales and / or Sales Returns), the procedure Terminate_Entry_SNS 260 can update the status of the batch to "settled" (ready for release) if the transaction is originated by the purchase module 220 or the inventory module 222 or you can change the status of the consignor to the last one (for example, ready to be taken by the OM sales journal) if the transaction is originated by the order management module 224. When it is triggered from a manufacturing module, the procedure Terminate_Entry SNS 260 can execute an integrity review task. The integrity review task can review the non-existent serial number components and duplicate serial number components. In cases where a nonexistent serial number is detected, a record is inserted in the SNS_IN 236 box and marked in the SNS_MST 238 box to allow the procedure to continue. In cases where a duplicate serial number is detected, the record in the SNS_MST 238 box is marked as an error. After the integrity review task is performed, the SNS 260 End_Entry procedure can change the OM consignator stage to the last one (for example, ready to be taken over by the OM sales journal) if duplicate serial number conditions do not appear or finished goods for the manufacturing order. As shown in Fig. 2, one embodiment of the SIC system 23 includes an SNS GateInput Sqt 270 agent. In general, the BOOK_SET INPUT 270 agent can be configured to look up records available in the database structure 230 and / or in the EPR system 22. In an execution, the SNS GateInput 270 agent can periodically search (for example, every "n" minute) workframes (for example, SEND_WRIGHT_DART 232 box, SEND_WRIGHT_WRITE 233 box, RECEIVE_WRIGHT_DISTRESS 234, frame RECEIVE_WRITE_WRITE 235 ) for available (existing) records and corresponding batch numbers in the ERP system 22. Once the ERP batch is released, for example, OM where the batch is created and self-released by the OM sales journal, the agent of Entry__Scan 270 can proceed with the insertion of transactions in the transaction boxes (for example, table SNS_DENTRO 236, table SNS_FUERA 237) and delete the transactions of the work boxes (for example, a SEND_WRITING_DISK 232 box, a SEND_WRIGHT_FORCE 233 box, a RECEIVE_TRABAJO_DENTRO 234, a RECEIVE_TRABAJO_FUERA 235 table). In some executions, the agent of Entrance_Port SNS 270 may also require the update of the other tables, depending on the transaction. For example, in case of a new transaction SNS_DENTRO, SNS Gateway_Input 270 agent may require updating of SNS_MST 238 table to register the available serial number article. In case of a new transaction SNS_FUERA, the agent of Gate_Input SNS 270 may require updating the SNS_MST 238 box to remove the serial number item and move it to a historical box as a discarded item. The Entrant_Puert SNS 270 agent can also update the SNS_DENTRO 236 box to record the relation of the record in the SNS_DENTRO 236 box with the record in the SNS_FUERA 237 box that dispatches the item. For manufacturing transactions, it may be required that the SNS_Start_Information 270 agent stores the serial number of the finished good in the SNS_FUERA 237 table for the components of the article and thus maintain the information of how / when an article was used and which components were used. They used to build a particular finished good. For Transfer / Activation transactions, the site and cube location fields in the SNS_DENTRO 236 box and in the SNS_MST 237 box can be updated. As shown in Figure 2, one mode of the SIC system 23 includes a report generation interface 280. In general, the report generation interface 280 can be configured to generate and / or modify reports. In one modality, the reports are generated from the table SNS_DENTRO 236, the table SNS_FUERA 237, and the table SNS_MST 238. The reports may include a nonexistent serial number report that identifies the SNS_DENTRO lines that needed to be inserted to resolve the use of non-existent serial numbers for components of a production order. Reports can also include a duplicate serial number report that identifies SNS_MST records marked as an error when a production order attempts to generate new goods with serial numbers already in use. Referring to Figure 4, a communication system operates in accordance with a method 30 to accurately track a high volume of serialized information. The method 30 can generally involve the reception of serialized information (step 310), the application of validation rules to the serialized information (step 320), the marking of exceptions to the validation rules (step 330), and the generation of reports of the exceptions (step 360). Although particular embodiments and examples are described and illustrated, the method 30 can be executed through any convenient type of hardware (e.g., device, computer, computer system, equipment, component), software (e.g., program, application, set of instructions, code), storage medium (for example, disk, device, propagated signal), or a combination thereof. In step 310, the serialized information is received. In one embodiment, the SIC system 23 receives and maintains the serialized information for transactions involving the entry of items and the output of items from a system. The SIC 23 system monitors incoming transactions and outgoing transactions and tracks the net balance of inventories within the system. Records are created and updated as items that enter and leave the system on a near real-time basis. In one embodiment, the procedure for receiving serialized information is initiated by an ERP system 22 and / or a production module. The ERP 22 system can allow a user to create a purchase order, enter a purchase order receipt, enter refunds of purchase orders, enter an inventory receipt, transfer inventory, activate inventory, adjust inventory, create purchase orders, work, update work orders, monitor work orders, enter sales and enter returns. After entering data in the ERP 22 system, a user could be asked to scan or otherwise enter the serial information involved in the ERP procedure in the SIC 23 system. For example, the user could select from "lines not yet filled in "to enter a block using the data entry capabilities (eg, manual scan, file, etc.). The user can enter serialized information including, for example: Inventory ID and serial numbers, record the receipt of the purchase order, enter a batch number for the inventory transfer, inventory activation, inventory adjustment, record the consignment number OM. The serialized information can be saved in the appropriate work boxes (for example, TRAB table JO_DENTRO_SNS 232 for receipts, TRAB JO_FUERA_SNS 232 for returns). The production of the final goods can be the table for the final goods and for the components shipped, according to the format provided. The tables may include data fields: batch number, module, type, line number, item, serial number, sign (+/- for receipt / returns, status, production reference ID (for production), quantity that is planned to be sent, date, location of the site, and / or location of the cube In the table 320, validation rules apply to serialized information In one embodiment, the SIC 23 system includes logic to check that serialized information does not exist for an article that is just entering the system. and that the serialized information does exist for an inventory item that is exiting the system In one execution, the SNS Data_Application Application 250 is configured to apply validation rules to data entered at the database level.Validation rules may include a mask that requires all serialized information to comply with certain data field definitions for the data type (eg, numeric, hexadecimal) and longi The validation rules may also require that there are no duplicates. For example, when new items are registered (for example, receptions, production - finished items, positive adjustments, sales returns) the Application of Data_SNS_Input 250 can check that the serial numbers do not exist as available in the SNS_MST 238 table. Validation may also require existence. For example, when items are shipped (for example, Purchase Returns, Production - Components, Negative Adjustments, Sales), the SNS_Data_Input_App 250 Application can check that those serial numbers exist as available in the SNS_MST 238 box. The SNS_Data Entry_Application 250 You can check the valid serial numbers (mask) and valid numbers (existing without duplicates) during the data entry procedure and before allowing the entry to be saved. The SNS_Data_Information_Application 250 also checks that there is a line or batch item and that it has not been received. In some executions, after the last serialized information has been registered, the procedure FINISH_INSTALLED_SNS 260 can be triggered to update the ERP system 22. The procedure Terminate_Entry_SNS 260 can update, for example, the status of the purchase order (reception / return of batch), the state of the inventory (transfer / asset / adjust batch), the status of the Consignor OM to the next step that will make it suitable for the OM Daily Sales Book Procedure. The production interface 240 can execute a serial number validation procedure. For example, the manufacturing system 24 can use the production interface 240 to review and validate the existence of the serial number in the SIC system 23 (for example, the SNS MST 238 box). At the time of execution, the functionality of the manufacturing system 24 can be suspended if errors are discovered until a supervisor invalidates the error review and allows production to continue. In some executions, before proceeding with the ERP upgrade, the TERMINATE_INSTALLED_SNS procedure 260 can execute data updates and revisions for assembly transactions. Once the batch is released (for example, purchase order receipt batch, purchase order return batch, inventory equipment batch, inventory transfer batch, inventory activation batch, inventory adjustment batch , lot of sales, lot of returns), the agent of INTRADA_PUERTA_SNS 270 that reviews the records available in the boxes TRABAJO_DENTRO_SNS / TRABAJO_FUERA_SNS will continue moving the transaction records to the SNS_DENTR0 / SNS_FUERA boxes and, consequently, updating the SNS_MST (and SNS_DENTRO) box in the case of returns). The ENTRADA_PUERTA_SNS 270 agent that reviews the records available in the boxes TRABAJO_DENTRO_SNS / TRABAJO_FUERA_SNS will continue moving the transaction records to the SNS_DENTR0 / SNS_FUERA boxes and, therefore, updating the table SNS_MST (and SNS_DENTRO for the case of returns). For inventory transfer transactions, the ENTRADA_PUERTA_SNS 270 agent can update the site and cube location fields in the SNS_DENTRO 236 box and the SNS_MST 238 table when it finds outstanding transfer records in the WORK_DENTRO_SNS 232 box that are related to a batch of transfer of inventory already released. In step 330, the exceptions to the validation rules are marked. In cases where a nonexistent serial number is detected, a record is inserted in the SNS box INSIDE 236 and marked in the SNS_MST 238 box to allow the procedure to continue. In cases where a duplicate serial number is detected, the record in the SNS_MST 238 box is marked as an error. The TERMINAR_ENTRADA_SNS procedure 260 can insert and mark records SNS_DENTR? / SNS_MST for Serial Numbers of Components "dispatched" for a manufacturing procedure that does not exist in the SNS boxes. The TERMINAR_ENTRADA_SNS procedure 260 can mark SNS_MST records as "errors" in cases where the serial number of the finished good (for example, equipment assembly) already exists and is available in the SNS boxes. In step 340 exceptions are reported. In one modality, the SIC 23 system provides real-time auditing and monitoring of exceptions for components as well as for finished goods. In one modality, reports are generated from the table SNS_DENTRO 236, the table SNS_FUERA 237, and the table SNS_MST 238. The reports may include a nonexistent serial number report that identifies the SNS_DENTRO lines that need to be inserted to resolve the use of non-existent serial numbers for components of a production order. Reports can also include a duplicate serial number report that identifies SNS_MST records marked as an error when a production order attempts to generate new goods with serial numbers already in use. As described and illustrated, aspects of the present invention allow accurate tracking of a large volume of serialized information. A number of executions have been described. However, it will be understood that various modifications may be made and that other executions are contemplated within the scope of the following claims.

Claims (20)

NOVELTY OF THE INVENTION Having described the present invention, it is considered as a novelty and, therefore, the content of the following is claimed as a priority: CLAIMS

1. - A communication system comprising: a guest system in communication with one or more client systems, the guest system has a serialized inventory control system configured to: receive serialized information; apply validation rules to serialized information; mark the exceptions to the validation rules; and reporting exceptions, where the serialized inventory control system includes database logic to check that serialized information does not exist for an inbound inventory item and that serialized information does exist for an outbound inventory item.

2. - The communication system according to claim 1, characterized in that the serialized information comprises an electronic serial number.

3. - The communications system according to claim 2, characterized in that the electronic serial number is associated with a finished good.

4. - The communications system according to claim 3, characterized in that the finished good comprises an equipment.

5. - The communication system according to claim 2, characterized in that the electronic serial number is associated with a component of a finished good.

6. - The communication system according to claim 1, characterized in that the serialized information comprises immigration data.

7. - The communication system according to claim 1, characterized in that the guest system also includes a business resource planning system.

8. - The communications system according to claim 2, wherein the business resource planning system comprises a purchase module configured to cover the receptions and refunds of purchase.

9. The communications system according to claim 2, characterized in that the business resource planning system comprises an inventory module configured to cover the inventory receipt, the inventory transfer, the inventory activation and the inventory adjustments .

10. The communication system according to claim 2, characterized in that the business resource planning system comprises a command management module configured to cover manufacturing procedures, sales transactions and sales return transactions.

11. - The communication system according to claim 1, characterized in that the guest system also comprises a manufacturing system.

12. - The communication system according to claim 1, characterized in that the serialized inventory control system comprises a database structure configured to store values belonging to serial number transactions.

13. - The communication system according to claim 12, characterized in that the serialized inventory control system further comprises a serial number data entry application configured to allow a user to register serialized information.

14. - The communication system according to claim 12, characterized in that the serialized inventory control system comprises a procedure configured to update and check the integrity of the serialized information.

15. - The communication system according to claim 12, characterized in that the serialized inventory control system comprises a procedure to update and review the integrity of the serialized information.

16. - The communication system according to claim 12, characterized in that the serialized inventory control system comprises a report generation interface for creating and modifying reports.

17. - An inventory control method that has the ability to be executed by a computer system, the method includes the steps to: receive serialized information; apply validation rules to serialized information; mark the exceptions to the validation rules; and report exceptions, where the validation rules comprise database logic to check that signaled information does not exist for an input inventory item and that the serialized information does exist-for an item of output inventory.

18. The method according to claim 17, characterized in that the computer system comprises at least one of a guest system and a client system.

19. - A computer program stored in a computer-readable medium, the computer program includes instructions for: receiving serialized information; apply validation rules to serialized information; mark the exceptions to the validation rules; and report the exceptions.

20. The computer program according to claim 19, characterized in that the computer readable medium comprises at least one of a client device, a network device, a host device, a disk and a propagated signal.