US20060287939A1 - Methods and systems for grouping and managing stock requests - Google Patents
Methods and systems for grouping and managing stock requests Download PDFInfo
- Publication number
- US20060287939A1 US20060287939A1 US11/130,104 US13010405A US2006287939A1 US 20060287939 A1 US20060287939 A1 US 20060287939A1 US 13010405 A US13010405 A US 13010405A US 2006287939 A1 US2006287939 A1 US 2006287939A1
- Authority
- US
- United States
- Prior art keywords
- wave
- stock
- stock request
- request
- template
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 73
- 238000012544 monitoring process Methods 0.000 claims description 22
- 238000012856 packing Methods 0.000 claims description 20
- 238000012384 transportation and delivery Methods 0.000 claims description 12
- 230000000694 effects Effects 0.000 claims description 5
- 238000003860 storage Methods 0.000 abstract description 7
- 230000008569 process Effects 0.000 description 32
- 238000012545 processing Methods 0.000 description 22
- 238000010586 diagram Methods 0.000 description 12
- 238000013068 supply chain management Methods 0.000 description 10
- 238000007726 management method Methods 0.000 description 9
- 238000012546 transfer Methods 0.000 description 8
- 230000008859 change Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000000047 product Substances 0.000 description 2
- 241000143229 Idaea consanguinaria Species 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 239000013065 commercial product Substances 0.000 description 1
- 238000010924 continuous production Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
- G06Q20/203—Inventory monitoring
Definitions
- the present invention generally relates to methods and systems for grouping and managing requests to move stock in a warehouse or other storage facilities. More particularly, the invention relates to methods and systems for grouping stock requests based on the attributes of those requests and then managing the release of the grouped requests for processing in the warehouse.
- the order goes through various stages before the customer receives the purchased item. For instance, a supplier of the item may determine a shipping route and the means for shipment. The order may then be sent to a warehouse as a stock request so that the item can be collected, packed, and shipped to the customer.
- a transfer order is an instruction to move items from a source location (such as a source storage bin) to a destination location (such as a destination storage bin) within a warehouse complex.
- a TO may contain information included in the stock request, such as, but not limited to, the item and the quantity of the item to be moved, the source and destination locations, and shipping information.
- This process can be very time-consuming.
- a warehouse can only fill a certain number of TOs each day since each worker would potentially be working on an order-by-order basis, and for each TO, on an item-by-item basis.
- the process can cause high inefficiencies if the worker simply processes each TO serially. For instance, it would be inefficient for the worker to make repeated trips to the same warehouse area to retrieve an item as opposed to retrieving those items in just one trip to that area. This process may also cause congestion within a warehouse if multiple workers collect items from the same areas in the warehouse at the same time.
- a warehouse worker may manually group certain stock requests based on certain attributes of each request. For instance, the worker may manually group requests based on, for example, a shipping destination or item associated with each request.
- the manually created group of stock requests (sometimes referred to as a “wave”) may then be released to a warehouse worker as a TO for processing.
- Such a process can also be time-consuming and lead to errors.
- the worker depending on how many requests are received each minute, hour, or day, would have to look at each request to decide how it should be grouped with the other requests based on the various request attributes.
- the worker can easily overlook one or more stock requests or attributes of the requests, and thus, may have to separately process a request that could have been more efficiently processed when grouped with other requests.
- the above process also leads to congestion in the warehouse since workers could be instructed to process two different groups of requests for items in the same area of the warehouse.
- this system becomes very cumbersome as the number of requests to be processed increases, or in cases where the items for each request are located in more than one warehouse.
- a computer-implemented method for releasing stock requests to a warehouse.
- the method may comprise: receiving a stock request including one or more attributes about a stock item; generating a condition record reflecting a predetermined set of conditions to be met by the attributes of a stock request; determining whether the attributes of the received stock request meet the conditions of the condition record; associating a wave template of the condition record with the stock request if a determination is made that the stock request does meet the condition record; creating a wave object based on each stock request associated with the wave template; and releasing the wave object to the warehouse for fulfillment of each stock request associated with the wave object.
- a computer system for releasing stock requests to a warehouse may comprise: means for receiving a stock request including one or more attributes about a stock item; means for generating a condition record reflecting a predetermined set of conditions to be met by the attributes of a stock request; means for determining whether the attributes of the received stock request meet the conditions of the condition record; means for associating a wave template of the condition record with the stock request if a determination is made that the stock request does meet the condition record; means for creating a wave object based on each stock request associated with the wave template; and means for releasing the wave object to the warehouse for fulfillment of each stock request associated with the wave object.
- computer-readable medium containing instructions for performing a method for releasing stock requests to a warehouse.
- the computer-readable medium may comprise receiving a stock request including one or more attributes about a stock item; generating a condition record reflecting a predetermined set of conditions to be met by the attributes of a stock request; determining whether the attributes of the received stock request meet the conditions of the condition record; associating a wave template of the condition record with the stock request if a determination is made that the stock request does meet the condition record; creating a wave object based on each stock request associated with the wave template; and releasing the wave object to the warehouse for fulfillment of each stock request associated with the wave object.
- FIG. 1 depicts an exemplary system environment, consistent with an embodiment of the present invention
- FIG. 2 is a block diagram of an exemplary wave management module, consistent with an embodiment of the present invention.
- FIG. 3 is a flowchart of an exemplary method for releasing waves to a warehouse, consistent with an embodiment of the present invention
- FIGS. 4 ( a - b ) are diagrams of two exemplary wave templates, consistent with an embodiment of the present invention.
- FIGS. 5 ( a - b ) are diagrams of two exemplary condition records, consistent with an embodiment of the present invention.
- FIGS. 6 ( a - b ) are diagrams of two exemplary stock requests, consistent with an embodiment of the present invention.
- FIG. 7 is an exemplary flowchart of a wave generation process, consistent with an embodiment of the present invention.
- FIGS. 8 ( a - b ) are diagrams of the exemplary stock requests of FIG. 6 ( a - b ) processed by the exemplary condition records of FIG. 5 ( a - b ), consistent with an embodiment of the present invention
- FIG. 9 is a diagram of an exemplary wave template, consistent with an embodiment of the present invention.
- FIG. 10 is a flowchart of an exemplary wave monitoring process, consistent with an embodiment of the present invention.
- Systems and methods consistent with the invention manage the release of stock requests to a warehouse or other storage facilities for processing in the form of a wave.
- the term “wave” refers to a data object identifying a set of stock requests grouped according to one or more attributes of the stock requests.
- transfer orders or TOs may then be created to instruct movements of the corresponding stock items in furtherance of the stock requests.
- Systems consistent with the invention account for various attributes of a stock request, including, but not limited to, the type of stock items, shipping destinations, shipping priority classes of each stock item, and the locations within a warehouse between which the stock items are to be moved. The system may also consider additional restrictions such as stock items that have already been moved to another location within a warehouse, and restrictions relating to customer information.
- an item refers to any product or good stored in a warehouse or other facility.
- an item may comprise a part for manufacturing, a finished product, or a part used to provide a service to a customer.
- An item may also comprise a commercial product, such as a book, an office supply, an article of clothing, an electronic device, a home appliance, or any other type of merchandise.
- an item in the context of a warehouse environment for an automotive or machinery supplier, an item may comprise an automotive part, an engine part, or a heavy equipment part and the like.
- FIG. 1 depicts an exemplary system environment, consistent with an embodiment of the present invention.
- System 100 may contain a customer relation management module (CRM) 102 , which may be a computer or network of computers for supporting customer communications.
- CRM 102 may be implemented as part of a larger customer relationship management system.
- CRM 102 may receive customer orders and send information related to the customer orders to a Supply Chain Management (SCM) system 103 through network 106 .
- SCM Supply Chain Management
- SCM system 103 may send the customer orders to the SCM system 103 as “stock requests.”
- SCM system 103 may then send the stock requests to the wave manager 104 through network 106 .
- SCM Supply Chain Management
- Network 106 can be any data communications network including a combination of networks, such as the Internet, corporate intranets, a local area network, and other networks compatible with a networking protocol such as TCP/IP.
- Wave manager 104 may be a computer or network of computers that may receive stock request information from SCM 103 and, in response, schedule the release of a wave to a warehouse.
- system 100 may also include several databases 108 , 110 , and 112 .
- Each database or set of databases in system 100 may include information that can be accessed through a database protocol such as, in one embodiment, Structured Query Language (SQL).
- Orders database 108 may be a database or set of databases which may be accessed by wave manager 104 through network 106 .
- Orders database 108 may store any information related to the stock requests received from SCM 103 . This information could be, but is not limited to, the number of items in a request, the shipping destination of each item, the shipping priority class of each item, the location of each item in the warehouse, the scheduled shipping date of an item, and the quantity of each item included in the request.
- Template database 110 may be a database or a set of databases, which may also accessed by the wave manager 104 .
- Template database 110 may store wave templates used by system 100 when generating a wave, as described in greater detail below.
- a wave template may be initially determined by wave manager 104 and may be based on, but is not limited to, the day and time when the wave may be released.
- Template database 110 may also store condition records, each of which are associated with a wave template, as described in greater detail below.
- Wave database 112 may be a database or a set of databases that store information related to the groups of stock requests that are released to the warehouse for TO creation. As noted above, a “wave” refers to a grouping of one or more stock requests. Further, each wave may be associated with stock requests having a common wave template (stored in database 110 ) assigned by system 100 .
- FIG. 2 is a block diagram of an exemplary wave management module, consistent with an embodiment of the present invention.
- Wave manager 104 may include at least one central processing unit (CPU) 202 , an I/O interface 204 , a network interface 206 , and memory 210 .
- CPU 202 may execute instructions associated with the processes contained in memory 210 and transmit results to other subsystems of wave manager 104 over a high speed interconnect or data bus 208 .
- I/O interface 204 is an interface that may be used to couple wave manager 104 to devices such as a keyboard, a mouse, a display device, and any other I/O device useful in operating and managing wave manager 104 as is understood by one of skill in the art.
- the network interface 206 may be used to communicate with network 106 ( FIG. 1 ).
- memory 210 may include: customer interface process 212 that may have program instructions that, when executed, receive the stock request information from SCM 103 ( FIG. 1 ); wave template creation process 214 that may have program instructions that, when executed, create a wave template that includes attributes of when the wave is released to the warehouse for processing; condition records creation process 216 that may have program instructions that, when executed, create one or more condition records to be compared against each stock request received from SCM 103 ; wave generation process 218 that may have program instructions that, when executed, generate a wave that includes one or more stock requests; and wave monitor process 220 that may have program instructions that, when executed, allow wave manager 104 to release monitor the processing of the waves.
- FIG. 3 is a flowchart of an exemplary method for releasing waves to a warehouse, consistent with an embodiment of the present invention. The flow diagram is described with reference to the embodiment of system 100 depicted in FIG. 1 .
- Wave manager 104 may first create the wave templates (stage 302 ).
- the wave templates correspond to all the possible waves that should be released to the warehouse. Examples of wave template creation is discussed further with regard to FIGS. 4 a and 4 b .
- Wave manager 104 may then create the condition records using various attributes of stock requests and associate each condition record with a wave template created in stage 302 (stage 304 ). Condition record creation is discussed further with regard to FIGS. 5 a and 5 b.
- Wave manager 104 may then receive the stock requests from SCM 103 (stage 306 ).
- the stock request may include several types of data.
- each request may include, but is not limited to, an identification of the requested stock item, the requested quantity of the stock item, the location of the stock item in the warehouse, the shipping date, the shipping priority class, and the shipping destination.
- Customer interface process 212 may be executed by CPU 202 for receiving the information corresponding to the stock request.
- Wave generation process 218 may generate waves that correspond to groups of the received stock requests (stage 308 ). As described further below, process 218 may assign one or more wave templates to a stock request based on the information of a respective data type of the stock request. Each data type may correspond to a particular attribute of the stock request. Process 218 may then generate waves based on stock requests having the same assigned wave template.
- the wave generation process of stage 308 is described in further detail below with respect to FIGS. 7 and 8 ( a - b ).
- wave monitor process 220 of wave manager 104 may be used to release the wave to the warehouse for processing including the creation of TOs to instruct movement of the particular stock items corresponding to the generated wave and the subsequent execution of those TOs, and to monitor the activities of the wave before and after the wave is released to the warehouse for processing (stage 310 ).
- An exemplary embodiment of the wave monitoring process of stage 310 is described in further detail below with respect to FIG. 10 .
- FIGS. 4 a and 4 b are diagrams of two exemplary wave templates, consistent with an embodiment of the present invention.
- a wave template is one attribute of a wave.
- Wave manager 104 may create as many wave templates as needed.
- Each wave template may be assigned to one or more waves to be released to the warehouse for processing.
- wave template 400 is defined by three different attributes, the template ID 410 , which is “Wave Template 1,” the release time 420 that is set for “10:00,” and the wave completion time 430 that is “12:00.” Therefore, any wave with Wave Template 1 may be released on 10:00 and completed by 12:00.
- Wave template 400 will be referred to from now on by the template ID “Wave Template 1.” FIG.
- Wave template 440 has a template ID “Wave Template 2,” a release time of “15:00,” and a wave completion time of “18:00.”
- Wave templates may contain fields other than template ID, release time and release day.
- a wave template may be defined by any of the following fields: a cutoff time, a cutoff days, a release time, a release days, a picking completion time, a picking completion days, a packing completion time, a packing completion days, a wave completion time, a wave calendar, a wave status, a wave type, and a wave category.
- Each wave template may be assigned to a wave in the wave generation stage (see stage 308 of FIG. 3 ).
- FIGS. 5 a and 5 b are diagrams of exemplary condition records consistent with an embodiment of the present invention.
- Wave manager 104 may select from different data types (i.e., attributes) of a stock request in determining a condition record.
- manager 104 may define conditions for a condition record by selecting one or more data types, such as destination, warehouse picking area, shipping priority class, and shipping time, and define values for those selected data types that would thus correspond to a particular wave template.
- Manager 104 may specify as many data types as preferred, and can logically combine each selected data type with an “AND” operation.
- a first attribute in a condition record may be selected as based on the destination data type having a value corresponding to “New York,” while a second attribute may be selected as based on a destination data type and a warehouse picking area data type having respective values corresponding to “District of Columbia” and picking area 8 (“PA8”).
- wave manager 104 in determining the first condition record 500 , is able to select the following data types for the condition record: destination 502 , warehouse picking area 504 , priority class 506 , shipping time 508 , and wave template 510 .
- wave manager 104 has not defined data types 502 , 506 , or 508 as conditions, but has defined only warehouse picking area 504 as a condition. More specifically, in this example, wave manager 104 has selected “PA2” or “picking area 2” 510 as conditions for data type 504 .
- Wave manager 104 has also defined condition record 500 to be associated with Wave Template 1, 514 (see 400 of FIG. 4 a ). Wave manager 104 may have picked any of the existing wave templates to be associated with condition record 500 .
- FIG. 5 b also illustrates another condition record 520 .
- wave manager 104 has selected “HIGH” 514 as the condition for data type priority class 506 .
- Wave manager 104 has defined condition record 520 to be associated with Wave Template 2, 524 (see 420 of FIG. 4 b ).
- FIGS. 5 a and 5 b thus, illustrate exemplary condition records as defined by wave manager 104 by defining conditions to be met by one or more stock requests.
- wave manager 104 may select more than one condition for the condition record.
- wave manager 104 may also select a picking area as well as an operation class. In this scenario, all the conditions in the condition record are processed with the “AND” operand.
- FIGS. 6 a and 6 b are diagrams of two exemplary stock requests, consistent with an embodiment of the present invention.
- the first stock request 600 includes three rows of data 602 , 604 , 606 , with each row including a stock item description 608 , a picking area 610 in the warehouse where the stock item is located, and the number of units 612 of the stock item requested by the stock request.
- FIG. 6 a the first stock request 600 includes three rows of data 602 , 604 , 606 , with each row including a stock item description 608 , a picking area 610 in the warehouse where the stock item is located, and the number of units 612 of the stock item requested by the stock request.
- the second stock request 610 includes three rows of data 612 , 614 , and 616 , with each row including a stock item description 618 , the shipping priority class 620 for each stock item, the number of units 622 of the stock item requested by the stock request, the warehouse picking area 624 , the delivery date 626 of the stock request, and the delivery date 628 of the stock request.
- Each row of data represents a part of the stock request order.
- data types 608 , 610 , 612 , 618 , 620 , 622 , 624 , 626 , and 628 may be used by system 100 to determine a particular wave template to associate with the respective stock request.
- embodiments of the present invention are not limited to these particular stock requests, but will be referred to only for illustrating exemplary embodiments consistent with the present invention.
- FIG. 7 is a flowchart of an exemplary wave generation process consistent with an embodiment of the present invention.
- the process of FIG. 7 may correspond, for example, to the wave generation process of stage 308 of FIG. 3 .
- wave manager 104 may first compare each stock request or portions of each stock request with all of the condition records created in stage 304 (stage 720 ).
- Wave manager 104 may analyze each stock request or portions of each stock request to determine whether it meets the conditions of one or more of the condition records. More specifically, wave manger 104 may determine whether the data types of a stock request match with or meet the conditions defined for one or more condition records by comparing the information of each data type with the conditions of each condition record (stage 730 ).
- wave manager 104 determines that the stock request or portions of the stock request does not meet the conditions of any condition records, the stock request is not added to a wave (stage 740 ). Therefore, this stock request or portion of a stock request will not be sent to the warehouse for processing.
- wave manager 104 may then determine whether a stock request matches or meets the conditions of more than one condition record (stage 750 ). If wave manager 104 determines the stock request does meet the condition of more than one condition record, wave manager 104 may then determine the most optimal wave template of the condition records to associate with the stock request (stage 760 ). For example, if the stock request matches two condition records, and each condition record is associated with a first and a second wave template, wave manager 104 may determine which wave template may be the most optimal wave template for the stock request based on delivery date of the stock request.
- Wave manager 104 may determine that the first wave template may be associated with a release day that is too late to meet the delivery date of the stock request. Therefore, wave manager 104 may associate the second wave template with the stock request. This will be explained further with regard to FIG. 8 b.
- wave manager 104 may assign the wave template corresponding to the condition record to the stock request (stage 762 ). Wave manager 104 may then determine whether a wave corresponding to the wave template already exists (stage 770 ). If the wave corresponding to the wave template does not exist, wave manager 104 may create the wave using the wave template and assign the stock request to the new wave (stage 790 ). As stated above, the wave refers to a data object identifying a set of stock requests grouped according to a commonly assigned wave template. Once the wave template is assigned to a wave, wave manager 104 may determine the time constraints and other attributes for the wave. These time constraints and other wave attributes are further described with respect to FIG. 9 .
- wave manager 104 may assign the stock request corresponding to the wave template to the wave (stage 780 ). Any stock request or portions of a stock request assigned to the particular wave template will thus be associated with the new wave object. A wave may therefore reflect each stock request or portions of stock requests that have been assigned the same wave template.
- wave manager 104 may determine that a stock request or a portion of a stock request is assigned a particular wave template that was previously assigned to a wave, in other words, the wave template of the stock request or portion of the stock request may not be a new wave template that is being assigned to a new wave; it may have been assigned to a wave when it was created. Since the wave generation process may be a continuous process, wave manager 104 may then determine whether the wave for the particular wave template has already been released to the warehouse for processing. Determination of whether a wave has already been released may depend on the wave status which is discussed further in FIG. 9 .
- Wave manager 104 may not be able to associate the stock request or portion of the stock request with the released wave. Wave manager 104 may therefore create a new wave for the same wave template, and then assign the stock request or portion of the stock request to this new wave.
- FIGS. 8 ( a - b ) are diagrams of the exemplary stock requests of FIG. 6 ( a - b ) processed by the exemplary condition records of FIGS. 5 ( a - b ), consistent with an embodiment of the present invention. More specifically, for the example of FIGS. 8 a and 8 b , wave manager 104 may compare stock requests 600 and 610 to condition records 500 and 520 . Further, in this example, wave manager 104 may assign a wave template to each row of stock requests 600 and 610 (e.g., assign a respective wave template to rows 602 , 604 , 606 , 612 , 614 , and 616 , each representing a portion of the stock request).
- a wave template to each row of stock requests 600 and 610 (e.g., assign a respective wave template to rows 602 , 604 , 606 , 612 , 614 , and 616 , each representing a portion of the stock request).
- wave manager 104 may first compare stock request 600 and 610 to all the condition records, in this scenario, condition records 500 and 520 .
- Condition record 500 requires that that the stock item be located in warehouse picking area “PA2.” Accordingly, wave manager 104 may first compare row 602 of stock request 600 to condition record 500 . The stock item A of row 602 is located in “PA2.” Accordingly, wave manager 104 may assign Wave Template 1 to the row 602 of stock request 500 , associated with “100 units of A in picking area 2, unless another condition record matches row 602 . If row 602 matches the conditions of another condition record, wave manager 104 would then have to determine the optimal wave template associated with each condition record for the stock request (see 760 of FIG. 7 ). For row 604 and 606 , since the warehouse picking area is picking area 4, row 604 and 606 do not match condition record 500 , therefore rows 604 and 606 will not be assigned Wave Template 1.
- Wave manager 104 may then compare rows 602 , 604 , and 606 with condition record 520 .
- the first condition for condition record 520 is that the priority class is “High.” Rows 602 , 604 , and 606 do not have a priority class associated with them, and therefore, wave manager 104 may not assign wave template 2, associated with condition record 520 , to rows 602 , 604 , or 606 . Since there are only two condition records created in this example, wave manager 104 may not assign a wave template to rows 604 and 606 (stage 804 ), and the stock requests 604 and 606 may not be added to a wave (see stage 740 of FIG. 7 ). Wave manager 104 may then assign Wave Template 1 to row 612 because it was the only condition record that matched (stage 802 ).
- wave manager may compare rows 610 , 612 , and 614 to condition record 500 .
- Row 612 has a picking area of “PA2.” Therefore, wave manager 104 may assign Wave Template 1, corresponding to condition record 500 , to the stock request in row 612 .
- Rows 614 and 616 do not have a picking area of “PA2,” and do not therefore meet the conditions of condition record 500 .
- the stock requests associated with these rows will not be assigned Wave Template 1 (see stage 740 of FIG. 7 ).
- Wave manager 104 may then compare stock requests 612 , 614 , and 616 with condition record 520 .
- the first condition for condition record 520 is that the priority class must be “high.” Since row 612 does have a “high” priority class, wave manager 104 may assign wave template 2, corresponding to condition record 520 to row 612 . Wave manager 104 may then compare row 614 with condition record 520 . Since row 614 has a “low” priority class and therefore does not satisfy the condition of condition record 520 , it cannot be assigned Wave Template 2 (stage 808 ). For similar reasons, wave manager 104 would not assign row 616 to Wave Template 2 (stage 810 ). Since row 612 meets the conditions for both condition record 500 and 520 (stage 806 ), wave manager 104 may have to determine the most optimal wave template for the stock request (see 760 of FIG. 7 ).
- Wave manager 104 may use the delivery date of row 612 to determine the most optimal wave template to associate with row 612 .
- Row 612 of stock request 610 has a delivery date of “20040215” and a delivery time of “19:00.”
- Wave Template 1 has a wave completion time “18:00” and Wave Template 2 has a wave completion time “12:00.” Both wave templates may have a Wave Calendar allowing the waves to occur Monday-Friday, therefore there may exist a wave each weekday.
- wave manager 104 may assign Wave Template 1, or Template 2 to row 612 .
- wave manager 104 may assign Wave Template 1 to row 612 .
- Wave Template 1 is the optimal wave template because the release day of Wave Template 1 allows for delivery of the stock associated with row 612 by 20040215, 19:00 (stage 812 ). If an optimal wave is not found by wave manager 104 , the stock request will not be assigned to any wave.
- FIG. 9 illustrates an exemplary wave attribute header portion consistent with an embodiment of the present invention.
- a wave data object may include data defining different attributes of the wave object, as shown in FIG. 9 . These wave attributes may be stored in a header portion of the wave data object. In other words, the wave attributes may be stored as part of the file or data segment corresponding to the wave data object.
- the wave header holding these attributes may include a wave template 914 .
- Wave template 914 is one of the wave templates created by wave manger 104 in stage 302 of FIG. 3 .
- Wave template 914 may be a pointer to the template database 110 , which may store the wave template associated with the one or more condition records created by wave manager 104 (see 304 of FIG. 3 ).
- the wave object may also include any of a number of other attributes in the header section, which wave manager 104 may use to monitor the processing status of the wave.
- These other attributes may, for example, include any of the following attributes:
- the remainder of the wave data object file may comprise data identifying the one or more stock requests (not pictured) assigned to the wave template.
- the wave data object may include, for each associated stock request, a pointer to the actual stock request located in orders database 108 .
- FIG. 10 is a flowchart of an exemplary wave monitoring process consistent with an embodiment of the present invention.
- the process of FIG. 10 may correspond, for example, to the wave monitor process of stage 310 of FIG. 3 .
- wave manager 104 desires to monitor a particular wave, wave manager 104 may access that wave from wave database 112 by performing a search based on any of the wave attributes stored in the wave header file of the wave data object, as discussed with respect to FIG. 9 .
- wave manager 104 may search for a wave based on the wave's release time 922 or based on the wave's picking completion time 926 .
- Wave manager 104 may also search for a wave using a particular stock request ID assigned to a stock request.
- wave manager 104 may then determine whether the wave should be released to the warehouse (stage 1010 ). Wave manager 104 may make this determination by analyzing the release time 922 and release days 924 in the wave object header section. As noted above, releasing of a wave to the warehouse refers to the process of creating TOs that instruct how stock items should be moved in furtherance of the stock requests. The creation of TOs may be done by a warehouse management application compatible with, for example, the Extended Warehouse Management (EWM) software which is part of the mySAP SCM Solution provided by SAP Aktiengesellschaft, Walldorf, Germany.
- EWM Extended Warehouse Management
- wave manager 104 may change one or more wave attributes (stage 1020 ).
- Changing a wave attribute may include, but is not limited to, changing the cutoff time 918 , cutoff days 920 , release time 922 , release days 924 , picking completion time 926 , picking completion days 928 , packing completion time 930 , packing completion days 932 , loading completion time 934 , wave calendar 926 , wave status 938 , wave type 940 , and wave category 942 , which may all be located in the wave header section (see FIG. 9 ).
- Wave manager 104 may, for example, change the release time 922 to a different time than originally set. For example, a wave may have a release time of “Monday 9:00 am.” Wave manager 104 may override this release time attribute ( 922 ) and change the release time to a different time, which may be “Monday 8:00 am,” such that the wave should be released on “Monday at 8:00 am” instead of “9:00 am.” Another way wave manager 104 may also hold the wave for possible releasing at a later time. Wave manager 104 may “hold” a wave by changing the wave status 938 in the wave header section to “yes.” If wave manager 104 “holds” a wave, the wave would not be released to the warehouse even if the wave release time 922 indicates that the wave should be released.
- a wave that is on “hold” can only be released by wave manager 104 .
- Wave manager 104 may release the wave by changing the wave status 940 to “no.” A wave may only be held if the wave has not been released. A wave is released if the wave status 940 indicates “released.”
- Wave manager 104 may also delete a wave. When a wave is deleted, it is deleted from the wave database 112 , such that the wave is never released to the warehouse for processing. Once a wave is deleted, all stock requests or portions of a stock requests that were previously assigned to the deleted wave then become unassigned. In one embodiment, wave manager 104 may then reassign stock requests to another wave. Reassigning stock requests may comprise of changing the wave template of each stock request to another wave template or adding the stock requests to an existing wave with the same wave template as the wave that the stock requests were unassigned.
- Wave manager 104 may also change the wave population of a wave that wave manager 104 may have created earlier (stage 1030 ). Changing a wave population may include, but is not limited to, removing a stock request from a wave, adding a stock request to a wave, unassigning a stock request from an existing wave, and/or reassigning a stock request to another wave. Wave manager 104 may remove a stock request from a wave by deleting the stock request ID from the body of the wave object file. Wave manager 104 may add a stock request to a wave by adding the stock request ID associated with a particular stock request to the wave object file. Unassignment of a stock request may be possible before and after the wave release time 922 has passed.
- Wave manager 104 may also add a stock request to a wave by merging one or more waves into one wave. In merging one or more waves, wave manager 104 may remove the stock requests by deleting the stock request IDs from the wave object file of the first wave and adding these stock request IDs to the wave object file of the second wave. Similarly, wave manager 104 may split a wave into two or more separate waves. Wave manager 104 may split a wave by creating a new wave with the same header section as the first wave, and move select stock request IDs from the first wave to the new wave.
- the one or more stock requests of the wave may first be sent to a picking location determination module, before the TOs are created by the warehouse management application.
- This picking location determination module determines the location of each of the stock items described in the stock requests within the warehouse.
- wave manager 104 may allocate the stock in the inventory to each stock request so that the stock in the warehouse will be available when the TO is released for processing. Once the stock in the inventory is allocated for each stock request, the warehouse management application may then create one or more TOs.
- a TO may be created for each stock request or each portion of a stock request in each wave. Once the warehouse management application creates the TOs, the TOs may then be released to the warehouse for processing. During TO processing, each TO is carried out by the warehouse workers, where the stock items described in each stock request are moved from the source location (such as a source storage bin) to the destination location (such as a destination storage bin) within the warehouse complex.
- the systems and methods disclosed herein may be embodied in various forms including, for example, a data processor, such as a computer that also includes a database.
- a data processor such as a computer that also includes a database.
- the above-noted features and other aspects and principles of the present invention may be implemented in various environments. Such environments and related applications may be specially constructed for performing the various processes and operations according to the invention or they may include a general-purpose computer or computing platform selectively activated or reconfigured by code to provide the necessary functionality.
- the processes disclosed herein are not inherently related to any particular computer or other apparatus, and may be implemented by a suitable combination of hardware, software, and/or firmware.
- various general-purpose machines may be used with programs written in accordance with teachings of the invention, or it may be more convenient to construct a specialized apparatus or system to perform the required methods and techniques.
- Systems and methods consistent with the present invention also include computer readable media that include program instruction or code for performing various computer-implemented operations based on the methods and processes of the invention.
- the media and program instructions may be those specially designed and constructed for the purposes of the invention, or they may be of the kind well known and available to those having skill in the computer software arts.
- Examples of program instructions include, for example, machine code, such as produced by a compiler, and files containing a high level code that can be executed by the computer using an interpreter.
Abstract
Description
- I. Field of the Invention
- The present invention generally relates to methods and systems for grouping and managing requests to move stock in a warehouse or other storage facilities. More particularly, the invention relates to methods and systems for grouping stock requests based on the attributes of those requests and then managing the release of the grouped requests for processing in the warehouse.
- II. Background of the Invention
- When a customer places an order to purchase an item, the order goes through various stages before the customer receives the purchased item. For instance, a supplier of the item may determine a shipping route and the means for shipment. The order may then be sent to a warehouse as a stock request so that the item can be collected, packed, and shipped to the customer.
- During normal operations, the warehouse may receive many requests for different stock items each day. The items associated with each respective request may be located in different areas of the warehouse, and may require shipment to different destinations, as well as by different shipping priority classes. Typically, the requests to move stock within the warehouse are issued as transfer orders. A transfer order (or “TO”) is an instruction to move items from a source location (such as a source storage bin) to a destination location (such as a destination storage bin) within a warehouse complex. A TO may contain information included in the stock request, such as, but not limited to, the item and the quantity of the item to be moved, the source and destination locations, and shipping information. Upon receiving a TO, a warehouse worker will identify from the TO the items to be moved and determine where each is located in the warehouse. The worker may then go to each location to collect the ordered items. Once the items are collected, the worker then packs the items and ships them to the destination specified on the order.
- This process can be very time-consuming. A warehouse can only fill a certain number of TOs each day since each worker would potentially be working on an order-by-order basis, and for each TO, on an item-by-item basis. Further, the process can cause high inefficiencies if the worker simply processes each TO serially. For instance, it would be inefficient for the worker to make repeated trips to the same warehouse area to retrieve an item as opposed to retrieving those items in just one trip to that area. This process may also cause congestion within a warehouse if multiple workers collect items from the same areas in the warehouse at the same time.
- To manage the processing of TOs in a warehouse, a warehouse worker may manually group certain stock requests based on certain attributes of each request. For instance, the worker may manually group requests based on, for example, a shipping destination or item associated with each request. The manually created group of stock requests (sometimes referred to as a “wave”) may then be released to a warehouse worker as a TO for processing.
- Such a process, however, can also be time-consuming and lead to errors. The worker, depending on how many requests are received each minute, hour, or day, would have to look at each request to decide how it should be grouped with the other requests based on the various request attributes. The worker can easily overlook one or more stock requests or attributes of the requests, and thus, may have to separately process a request that could have been more efficiently processed when grouped with other requests. The above process also leads to congestion in the warehouse since workers could be instructed to process two different groups of requests for items in the same area of the warehouse. Furthermore, this system becomes very cumbersome as the number of requests to be processed increases, or in cases where the items for each request are located in more than one warehouse.
- Existing methods and systems for grouping stock requests also suffer from other drawbacks. For instance, such systems do not give a worker the capability to monitor the processing status of the grouped requests. For instance, if the worker subsequently decides not to process the grouped requests, existing systems do not allow the worker to efficiently cancel that processing instruction or to hold it for processing at a later time. Further, existing systems do not allow the worker to remove and add stock requests to a previously created group of requests or to provide an interface to manage the processing status of the group. In a busy delivery or supply chain environment, this can result in substantial delays and inefficiencies.
- In view of the foregoing, there is a need for improved systems and methods for grouping and managing stock requests in a warehouse environment.
- Consistent with embodiments of the present invention, methods and systems are disclosed for releasing stock requests to a warehouse in groups or “waves,” including managing the activity of the waves before and after they are sent to the warehouse. In accordance with one embodiment, a computer-implemented method is provided for releasing stock requests to a warehouse. The method may comprise: receiving a stock request including one or more attributes about a stock item; generating a condition record reflecting a predetermined set of conditions to be met by the attributes of a stock request; determining whether the attributes of the received stock request meet the conditions of the condition record; associating a wave template of the condition record with the stock request if a determination is made that the stock request does meet the condition record; creating a wave object based on each stock request associated with the wave template; and releasing the wave object to the warehouse for fulfillment of each stock request associated with the wave object.
- In accordance with another embodiment, a computer system for releasing stock requests to a warehouse is provided. The system may comprise: means for receiving a stock request including one or more attributes about a stock item; means for generating a condition record reflecting a predetermined set of conditions to be met by the attributes of a stock request; means for determining whether the attributes of the received stock request meet the conditions of the condition record; means for associating a wave template of the condition record with the stock request if a determination is made that the stock request does meet the condition record; means for creating a wave object based on each stock request associated with the wave template; and means for releasing the wave object to the warehouse for fulfillment of each stock request associated with the wave object.
- In yet another embodiment, computer-readable medium containing instructions for performing a method for releasing stock requests to a warehouse is provided. The computer-readable medium may comprise receiving a stock request including one or more attributes about a stock item; generating a condition record reflecting a predetermined set of conditions to be met by the attributes of a stock request; determining whether the attributes of the received stock request meet the conditions of the condition record; associating a wave template of the condition record with the stock request if a determination is made that the stock request does meet the condition record; creating a wave object based on each stock request associated with the wave template; and releasing the wave object to the warehouse for fulfillment of each stock request associated with the wave object.
- Additional objects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objects and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
- It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed. Further, features and/or variations may be provided in addition to those set forth herein. For example, embodiments of the invention may be directed to various combinations and subcombinations of the features described in the detailed description.
- The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various embodiments of the invention and together with the description, serve to explain the principles of the invention. In the drawings:
-
FIG. 1 depicts an exemplary system environment, consistent with an embodiment of the present invention; -
FIG. 2 is a block diagram of an exemplary wave management module, consistent with an embodiment of the present invention; -
FIG. 3 is a flowchart of an exemplary method for releasing waves to a warehouse, consistent with an embodiment of the present invention; - FIGS. 4(a-b) are diagrams of two exemplary wave templates, consistent with an embodiment of the present invention;
- FIGS. 5(a-b) are diagrams of two exemplary condition records, consistent with an embodiment of the present invention;
- FIGS. 6(a-b) are diagrams of two exemplary stock requests, consistent with an embodiment of the present invention;
-
FIG. 7 is an exemplary flowchart of a wave generation process, consistent with an embodiment of the present invention; - FIGS. 8(a-b) are diagrams of the exemplary stock requests of
FIG. 6 (a-b) processed by the exemplary condition records ofFIG. 5 (a-b), consistent with an embodiment of the present invention; -
FIG. 9 is a diagram of an exemplary wave template, consistent with an embodiment of the present invention; and -
FIG. 10 is a flowchart of an exemplary wave monitoring process, consistent with an embodiment of the present invention. - The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar parts. While several exemplary embodiments and features of the invention are described herein, modifications, adaptations and other implementations are possible, without departing from the spirit and scope of the invention. For example, substitutions, additions, or modifications may be made to the components illustrated in the drawings, and the exemplary methods described herein may be modified by substituting, reordering or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the invention. Instead, the proper scope of the invention is defined by the appended claims.
- Systems and methods consistent with the invention manage the release of stock requests to a warehouse or other storage facilities for processing in the form of a wave. As used herein, the term “wave” refers to a data object identifying a set of stock requests grouped according to one or more attributes of the stock requests. When a wave is released, transfer orders or TOs may then be created to instruct movements of the corresponding stock items in furtherance of the stock requests. Systems consistent with the invention account for various attributes of a stock request, including, but not limited to, the type of stock items, shipping destinations, shipping priority classes of each stock item, and the locations within a warehouse between which the stock items are to be moved. The system may also consider additional restrictions such as stock items that have already been moved to another location within a warehouse, and restrictions relating to customer information.
- As used herein, the term “item” refers to any product or good stored in a warehouse or other facility. By way of example, an item may comprise a part for manufacturing, a finished product, or a part used to provide a service to a customer. An item may also comprise a commercial product, such as a book, an office supply, an article of clothing, an electronic device, a home appliance, or any other type of merchandise. By way of further example, in the context of a warehouse environment for an automotive or machinery supplier, an item may comprise an automotive part, an engine part, or a heavy equipment part and the like.
-
FIG. 1 depicts an exemplary system environment, consistent with an embodiment of the present invention.System 100 may contain a customer relation management module (CRM) 102, which may be a computer or network of computers for supporting customer communications. In one embodiment,CRM 102 may be implemented as part of a larger customer relationship management system.CRM 102 may receive customer orders and send information related to the customer orders to a Supply Chain Management (SCM)system 103 throughnetwork 106.CRM 102 may send the customer orders to theSCM system 103 as “stock requests.”SCM system 103 may then send the stock requests to thewave manager 104 throughnetwork 106.Network 106 can be any data communications network including a combination of networks, such as the Internet, corporate intranets, a local area network, and other networks compatible with a networking protocol such as TCP/IP.Wave manager 104 may be a computer or network of computers that may receive stock request information fromSCM 103 and, in response, schedule the release of a wave to a warehouse. - As shown in
FIG. 1 ,system 100 may also includeseveral databases system 100 may include information that can be accessed through a database protocol such as, in one embodiment, Structured Query Language (SQL).Orders database 108 may be a database or set of databases which may be accessed bywave manager 104 throughnetwork 106.Orders database 108 may store any information related to the stock requests received fromSCM 103. This information could be, but is not limited to, the number of items in a request, the shipping destination of each item, the shipping priority class of each item, the location of each item in the warehouse, the scheduled shipping date of an item, and the quantity of each item included in the request. -
Template database 110 may be a database or a set of databases, which may also accessed by thewave manager 104.Template database 110 may store wave templates used bysystem 100 when generating a wave, as described in greater detail below. A wave template may be initially determined bywave manager 104 and may be based on, but is not limited to, the day and time when the wave may be released.Template database 110 may also store condition records, each of which are associated with a wave template, as described in greater detail below. -
Wave database 112 may be a database or a set of databases that store information related to the groups of stock requests that are released to the warehouse for TO creation. As noted above, a “wave” refers to a grouping of one or more stock requests. Further, each wave may be associated with stock requests having a common wave template (stored in database 110) assigned bysystem 100. -
FIG. 2 is a block diagram of an exemplary wave management module, consistent with an embodiment of the present invention.Wave manager 104 may include at least one central processing unit (CPU) 202, an I/O interface 204, anetwork interface 206, andmemory 210.CPU 202 may execute instructions associated with the processes contained inmemory 210 and transmit results to other subsystems ofwave manager 104 over a high speed interconnect ordata bus 208. I/O interface 204 is an interface that may be used to couplewave manager 104 to devices such as a keyboard, a mouse, a display device, and any other I/O device useful in operating and managingwave manager 104 as is understood by one of skill in the art. Thenetwork interface 206 may be used to communicate with network 106 (FIG. 1 ). - In one embodiment,
memory 210 may include:customer interface process 212 that may have program instructions that, when executed, receive the stock request information from SCM 103 (FIG. 1 ); wavetemplate creation process 214 that may have program instructions that, when executed, create a wave template that includes attributes of when the wave is released to the warehouse for processing; conditionrecords creation process 216 that may have program instructions that, when executed, create one or more condition records to be compared against each stock request received fromSCM 103;wave generation process 218 that may have program instructions that, when executed, generate a wave that includes one or more stock requests; andwave monitor process 220 that may have program instructions that, when executed, allowwave manager 104 to release monitor the processing of the waves. -
FIG. 3 is a flowchart of an exemplary method for releasing waves to a warehouse, consistent with an embodiment of the present invention. The flow diagram is described with reference to the embodiment ofsystem 100 depicted inFIG. 1 . -
Wave manager 104 may first create the wave templates (stage 302). The wave templates correspond to all the possible waves that should be released to the warehouse. Examples of wave template creation is discussed further with regard toFIGS. 4 a and 4 b.Wave manager 104 may then create the condition records using various attributes of stock requests and associate each condition record with a wave template created in stage 302 (stage 304). Condition record creation is discussed further with regard toFIGS. 5 a and 5 b. -
Wave manager 104 may then receive the stock requests from SCM 103 (stage 306). The stock request may include several types of data. For instance, each request may include, but is not limited to, an identification of the requested stock item, the requested quantity of the stock item, the location of the stock item in the warehouse, the shipping date, the shipping priority class, and the shipping destination.Customer interface process 212 may be executed byCPU 202 for receiving the information corresponding to the stock request. -
Wave generation process 218 may generate waves that correspond to groups of the received stock requests (stage 308). As described further below,process 218 may assign one or more wave templates to a stock request based on the information of a respective data type of the stock request. Each data type may correspond to a particular attribute of the stock request.Process 218 may then generate waves based on stock requests having the same assigned wave template. The wave generation process ofstage 308 is described in further detail below with respect toFIGS. 7 and 8 (a-b). After thewave generation process 218 determines the waves,wave monitor process 220 ofwave manager 104 may be used to release the wave to the warehouse for processing including the creation of TOs to instruct movement of the particular stock items corresponding to the generated wave and the subsequent execution of those TOs, and to monitor the activities of the wave before and after the wave is released to the warehouse for processing (stage 310). An exemplary embodiment of the wave monitoring process ofstage 310 is described in further detail below with respect toFIG. 10 . -
FIGS. 4 a and 4 b are diagrams of two exemplary wave templates, consistent with an embodiment of the present invention. A wave template is one attribute of a wave.Wave manager 104 may create as many wave templates as needed. Each wave template may be assigned to one or more waves to be released to the warehouse for processing. As shown inFIG. 4 a,wave template 400 is defined by three different attributes, thetemplate ID 410, which is “Wave Template 1,” therelease time 420 that is set for “10:00,” and thewave completion time 430 that is “12:00.” Therefore, any wave withWave Template 1 may be released on 10:00 and completed by 12:00.Wave template 400 will be referred to from now on by the template ID “Wave Template 1.”FIG. 4 b is a second wave template consistent with an embodiment of the present invention.Wave template 440 has a template ID “Wave Template 2,” a release time of “15:00,” and a wave completion time of “18:00.” Wave templates may contain fields other than template ID, release time and release day. For example, a wave template may be defined by any of the following fields: a cutoff time, a cutoff days, a release time, a release days, a picking completion time, a picking completion days, a packing completion time, a packing completion days, a wave completion time, a wave calendar, a wave status, a wave type, and a wave category. Each wave template may be assigned to a wave in the wave generation stage (seestage 308 ofFIG. 3 ). -
FIGS. 5 a and 5 b are diagrams of exemplary condition records consistent with an embodiment of the present invention.Wave manager 104 may select from different data types (i.e., attributes) of a stock request in determining a condition record. For example,manager 104 may define conditions for a condition record by selecting one or more data types, such as destination, warehouse picking area, shipping priority class, and shipping time, and define values for those selected data types that would thus correspond to a particular wave template.Manager 104 may specify as many data types as preferred, and can logically combine each selected data type with an “AND” operation. For example, a first attribute in a condition record may be selected as based on the destination data type having a value corresponding to “New York,” while a second attribute may be selected as based on a destination data type and a warehouse picking area data type having respective values corresponding to “District of Columbia” and picking area 8 (“PA8”). - In the exemplary embodiment of
FIG. 5 a, in determining thefirst condition record 500,wave manager 104 is able to select the following data types for the condition record:destination 502,warehouse picking area 504,priority class 506,shipping time 508, andwave template 510. In this example, however,wave manager 104 has not defineddata types warehouse picking area 504 as a condition. More specifically, in this example,wave manager 104 has selected “PA2” or “pickingarea 2” 510 as conditions fordata type 504.Wave manager 104 has also definedcondition record 500 to be associated withWave Template 1, 514 (see 400 ofFIG. 4 a).Wave manager 104 may have picked any of the existing wave templates to be associated withcondition record 500. -
FIG. 5 b also illustrates anothercondition record 520. In this exemplary condition record,wave manager 104 has selected “HIGH” 514 as the condition for datatype priority class 506.Wave manager 104 has definedcondition record 520 to be associated withWave Template 2, 524 (see 420 ofFIG. 4 b).FIGS. 5 a and 5 b, thus, illustrate exemplary condition records as defined bywave manager 104 by defining conditions to be met by one or more stock requests. - In another embodiment,
wave manager 104 may select more than one condition for the condition record. For example,wave manager 104 may also select a picking area as well as an operation class. In this scenario, all the conditions in the condition record are processed with the “AND” operand. -
FIGS. 6 a and 6 b are diagrams of two exemplary stock requests, consistent with an embodiment of the present invention. As shown inFIG. 6 a, thefirst stock request 600 includes three rows ofdata stock item description 608, a pickingarea 610 in the warehouse where the stock item is located, and the number ofunits 612 of the stock item requested by the stock request. As shown inFIG. 6 b, thesecond stock request 610 includes three rows ofdata stock item description 618, theshipping priority class 620 for each stock item, the number ofunits 622 of the stock item requested by the stock request, thewarehouse picking area 624, thedelivery date 626 of the stock request, and thedelivery date 628 of the stock request. Each row of data represents a part of the stock request order. As described further below,data types system 100 to determine a particular wave template to associate with the respective stock request. As will be appreciated by those skilled in the art, embodiments of the present invention are not limited to these particular stock requests, but will be referred to only for illustrating exemplary embodiments consistent with the present invention. -
FIG. 7 is a flowchart of an exemplary wave generation process consistent with an embodiment of the present invention. The process ofFIG. 7 may correspond, for example, to the wave generation process ofstage 308 ofFIG. 3 . Referring toFIG. 7 ,wave manager 104 may first compare each stock request or portions of each stock request with all of the condition records created in stage 304 (stage 720).Wave manager 104 may analyze each stock request or portions of each stock request to determine whether it meets the conditions of one or more of the condition records. More specifically,wave manger 104 may determine whether the data types of a stock request match with or meet the conditions defined for one or more condition records by comparing the information of each data type with the conditions of each condition record (stage 730). Ifwave manager 104 determines that the stock request or portions of the stock request does not meet the conditions of any condition records, the stock request is not added to a wave (stage 740). Therefore, this stock request or portion of a stock request will not be sent to the warehouse for processing. - If
wave manager 104 determines the stock request or portions of a stock request do meet the condition of one condition record,wave manager 104 may then determine whether a stock request matches or meets the conditions of more than one condition record (stage 750). Ifwave manager 104 determines the stock request does meet the condition of more than one condition record,wave manager 104 may then determine the most optimal wave template of the condition records to associate with the stock request (stage 760). For example, if the stock request matches two condition records, and each condition record is associated with a first and a second wave template,wave manager 104 may determine which wave template may be the most optimal wave template for the stock request based on delivery date of the stock request.Wave manager 104 may determine that the first wave template may be associated with a release day that is too late to meet the delivery date of the stock request. Therefore,wave manager 104 may associate the second wave template with the stock request. This will be explained further with regard toFIG. 8 b. - Once
wave manager 104 determines the most optimal wave template for the stock request or portions of a stock request, or if the stock request only matches one condition record,manager 104 may assign the wave template corresponding to the condition record to the stock request (stage 762).Wave manager 104 may then determine whether a wave corresponding to the wave template already exists (stage 770). If the wave corresponding to the wave template does not exist,wave manager 104 may create the wave using the wave template and assign the stock request to the new wave (stage 790). As stated above, the wave refers to a data object identifying a set of stock requests grouped according to a commonly assigned wave template. Once the wave template is assigned to a wave,wave manager 104 may determine the time constraints and other attributes for the wave. These time constraints and other wave attributes are further described with respect toFIG. 9 . - If the wave corresponding to the wave template already exists,
wave manager 104 may assign the stock request corresponding to the wave template to the wave (stage 780). Any stock request or portions of a stock request assigned to the particular wave template will thus be associated with the new wave object. A wave may therefore reflect each stock request or portions of stock requests that have been assigned the same wave template. - In one embodiment,
wave manager 104 may determine that a stock request or a portion of a stock request is assigned a particular wave template that was previously assigned to a wave, in other words, the wave template of the stock request or portion of the stock request may not be a new wave template that is being assigned to a new wave; it may have been assigned to a wave when it was created. Since the wave generation process may be a continuous process,wave manager 104 may then determine whether the wave for the particular wave template has already been released to the warehouse for processing. Determination of whether a wave has already been released may depend on the wave status which is discussed further inFIG. 9 . If the wave has already been released, the wave status may be “released,” andwave manager 104 may not be able to associate the stock request or portion of the stock request with the released wave.Wave manager 104 may therefore create a new wave for the same wave template, and then assign the stock request or portion of the stock request to this new wave. - FIGS. 8(a-b) are diagrams of the exemplary stock requests of
FIG. 6 (a-b) processed by the exemplary condition records of FIGS. 5 (a-b), consistent with an embodiment of the present invention. More specifically, for the example ofFIGS. 8 a and 8 b,wave manager 104 may comparestock requests condition records wave manager 104 may assign a wave template to each row ofstock requests 600 and 610 (e.g., assign a respective wave template torows - Referring now to
FIG. 8 a,wave manager 104 may first comparestock request condition records Condition record 500 requires that that the stock item be located in warehouse picking area “PA2.” Accordingly,wave manager 104 may first comparerow 602 ofstock request 600 tocondition record 500. The stock item A ofrow 602 is located in “PA2.” Accordingly,wave manager 104 may assignWave Template 1 to therow 602 ofstock request 500, associated with “100 units of A in pickingarea 2, unless another condition record matchesrow 602. Ifrow 602 matches the conditions of another condition record,wave manager 104 would then have to determine the optimal wave template associated with each condition record for the stock request (see 760 ofFIG. 7 ). Forrow area 4,row condition record 500, thereforerows Wave Template 1. -
Wave manager 104 may then comparerows condition record 520. The first condition forcondition record 520 is that the priority class is “High.”Rows wave manager 104 may not assignwave template 2, associated withcondition record 520, torows wave manager 104 may not assign a wave template torows 604 and 606 (stage 804), and the stock requests 604 and 606 may not be added to a wave (seestage 740 ofFIG. 7 ).Wave manager 104 may then assignWave Template 1 to row 612 because it was the only condition record that matched (stage 802). - Referring now to
FIG. 8 b, wave manager may comparerows condition record 500. Row 612 has a picking area of “PA2.” Therefore,wave manager 104 may assignWave Template 1, corresponding tocondition record 500, to the stock request inrow 612.Rows condition record 500. The stock requests associated with these rows will not be assigned Wave Template 1 (seestage 740 ofFIG. 7 ). -
Wave manager 104 may then comparestock requests condition record 520. The first condition forcondition record 520 is that the priority class must be “high.” Sincerow 612 does have a “high” priority class,wave manager 104 may assignwave template 2, corresponding tocondition record 520 torow 612.Wave manager 104 may then comparerow 614 withcondition record 520. Sincerow 614 has a “low” priority class and therefore does not satisfy the condition ofcondition record 520, it cannot be assigned Wave Template 2 (stage 808). For similar reasons,wave manager 104 would not assignrow 616 to Wave Template 2 (stage 810). Sincerow 612 meets the conditions for bothcondition record 500 and 520 (stage 806),wave manager 104 may have to determine the most optimal wave template for the stock request (see 760 ofFIG. 7 ). -
Wave manager 104 may use the delivery date ofrow 612 to determine the most optimal wave template to associate withrow 612. Row 612 ofstock request 610 has a delivery date of “20040215” and a delivery time of “19:00.”Wave Template 1 has a wave completion time “18:00” andWave Template 2 has a wave completion time “12:00.” Both wave templates may have a Wave Calendar allowing the waves to occur Monday-Friday, therefore there may exist a wave each weekday. In order for the stock ofrow 612 to be delivered by 20040215 by 19:00,wave manager 104 may assignWave Template 1, orTemplate 2 to row 612. However, in order to minimize the time where the goods stay on the staging,wave manager 104 may assignWave Template 1 to row 612. Therefore,Wave Template 1 is the optimal wave template because the release day ofWave Template 1 allows for delivery of the stock associated withrow 612 by 20040215, 19:00 (stage 812). If an optimal wave is not found bywave manager 104, the stock request will not be assigned to any wave. -
FIG. 9 illustrates an exemplary wave attribute header portion consistent with an embodiment of the present invention. A wave data object may include data defining different attributes of the wave object, as shown inFIG. 9 . These wave attributes may be stored in a header portion of the wave data object. In other words, the wave attributes may be stored as part of the file or data segment corresponding to the wave data object. The wave header holding these attributes may include awave template 914.Wave template 914 is one of the wave templates created bywave manger 104 instage 302 ofFIG. 3 .Wave template 914 may be a pointer to thetemplate database 110, which may store the wave template associated with the one or more condition records created by wave manager 104 (see 304 ofFIG. 3 ). - The wave object may also include any of a number of other attributes in the header section, which wave
manager 104 may use to monitor the processing status of the wave. These other attributes may, for example, include any of the following attributes: -
- a
cutoff time 918, which may be the time by when stock requests should be added to the wave to be included before the wave is released to the warehouse for processing (e.g., when a transfer order (TO) is issued to instruct a worker to move a particular stock item); - a
cutoff days 920, which may be the number of days before a wave is completed that stock requests should be added to the wave in order to be included before the wave is released; - a
release time 922, which may be the time at which the wave should be released; - release
days 924, which may be the number of days before the wave is completed that it should be released; - a picking
completion time 926, which may be the time by when the worker should complete collecting from the warehouse the particular stock items listed in the transfer order - a
picking completion days 928, which may be the number of days before a wave is completed that the worker should complete collecting from the warehouse the particular stock items listed in the transfer order; - a
packing completion time 930, which may be the time by when the worker should complete packing the stock items listed in the transfer order that were previously collected from the warehouse; - a
packing completion days 932, which may be the number of days before the wave is completed that the worker should complete packing the stock items listed in the transfer order that were previously collected from the warehouse; - a
wave completion time 934, which may be the time that the loading of the previously packed stock items should occur in order to ship the items and thus the wave is completed; - a
wave calendar 936, which may be a factory calendar assigned to the wave which defines which days are working days. All calculations based on the number of days (e.g., picking days) are based on this wave calendar; - a
wave status 938, which may be a “hold” or “not hold” option that determines whether to hold the release of a wave; and - a
wave type 940 which may be different types of waves with special characteristics and behaviors. - a
wave category 942, which may be different categories of waves with special characteristics and behaviors.
- a
- The remainder of the wave data object file may comprise data identifying the one or more stock requests (not pictured) assigned to the wave template. For example, the wave data object may include, for each associated stock request, a pointer to the actual stock request located in
orders database 108. -
FIG. 10 is a flowchart of an exemplary wave monitoring process consistent with an embodiment of the present invention. The process ofFIG. 10 may correspond, for example, to the wave monitor process ofstage 310 ofFIG. 3 . Ifwave manager 104 desires to monitor a particular wave,wave manager 104 may access that wave fromwave database 112 by performing a search based on any of the wave attributes stored in the wave header file of the wave data object, as discussed with respect toFIG. 9 . For example,wave manager 104 may search for a wave based on the wave'srelease time 922 or based on the wave's pickingcompletion time 926.Wave manager 104 may also search for a wave using a particular stock request ID assigned to a stock request. - Once
wave manager 104 has selected a wave, as shown inFIG. 10 ,wave manager 104 may then determine whether the wave should be released to the warehouse (stage 1010).Wave manager 104 may make this determination by analyzing therelease time 922 and releasedays 924 in the wave object header section. As noted above, releasing of a wave to the warehouse refers to the process of creating TOs that instruct how stock items should be moved in furtherance of the stock requests. The creation of TOs may be done by a warehouse management application compatible with, for example, the Extended Warehouse Management (EWM) software which is part of the mySAP SCM Solution provided by SAP Aktiengesellschaft, Walldorf, Germany. - If the wave has not been released,
wave manager 104 may change one or more wave attributes (stage 1020). Changing a wave attribute may include, but is not limited to, changing thecutoff time 918,cutoff days 920,release time 922,release days 924, pickingcompletion time 926, pickingcompletion days 928, packingcompletion time 930, packingcompletion days 932, loadingcompletion time 934,wave calendar 926,wave status 938,wave type 940, andwave category 942, which may all be located in the wave header section (seeFIG. 9 ). -
Wave manager 104 may, for example, change therelease time 922 to a different time than originally set. For example, a wave may have a release time of “Monday 9:00 am.”Wave manager 104 may override this release time attribute (922) and change the release time to a different time, which may be “Monday 8:00 am,” such that the wave should be released on “Monday at 8:00 am” instead of “9:00 am.” Anotherway wave manager 104 may also hold the wave for possible releasing at a later time.Wave manager 104 may “hold” a wave by changing thewave status 938 in the wave header section to “yes.” Ifwave manager 104 “holds” a wave, the wave would not be released to the warehouse even if thewave release time 922 indicates that the wave should be released. In exemplary embodiments, a wave that is on “hold” can only be released bywave manager 104.Wave manager 104 may release the wave by changing thewave status 940 to “no.” A wave may only be held if the wave has not been released. A wave is released if thewave status 940 indicates “released.” -
Wave manager 104 may also delete a wave. When a wave is deleted, it is deleted from thewave database 112, such that the wave is never released to the warehouse for processing. Once a wave is deleted, all stock requests or portions of a stock requests that were previously assigned to the deleted wave then become unassigned. In one embodiment,wave manager 104 may then reassign stock requests to another wave. Reassigning stock requests may comprise of changing the wave template of each stock request to another wave template or adding the stock requests to an existing wave with the same wave template as the wave that the stock requests were unassigned. -
Wave manager 104 may also change the wave population of a wave that wavemanager 104 may have created earlier (stage 1030). Changing a wave population may include, but is not limited to, removing a stock request from a wave, adding a stock request to a wave, unassigning a stock request from an existing wave, and/or reassigning a stock request to another wave.Wave manager 104 may remove a stock request from a wave by deleting the stock request ID from the body of the wave object file.Wave manager 104 may add a stock request to a wave by adding the stock request ID associated with a particular stock request to the wave object file. Unassignment of a stock request may be possible before and after thewave release time 922 has passed. -
Wave manager 104 may also add a stock request to a wave by merging one or more waves into one wave. In merging one or more waves,wave manager 104 may remove the stock requests by deleting the stock request IDs from the wave object file of the first wave and adding these stock request IDs to the wave object file of the second wave. Similarly,wave manager 104 may split a wave into two or more separate waves.Wave manager 104 may split a wave by creating a new wave with the same header section as the first wave, and move select stock request IDs from the first wave to the new wave. - Once
wave manager 104 determines that a wave object should be released for TO creation, the one or more stock requests of the wave may first be sent to a picking location determination module, before the TOs are created by the warehouse management application. This picking location determination module determines the location of each of the stock items described in the stock requests within the warehouse. After the pick locations are determined for each stock item,wave manager 104 may allocate the stock in the inventory to each stock request so that the stock in the warehouse will be available when the TO is released for processing. Once the stock in the inventory is allocated for each stock request, the warehouse management application may then create one or more TOs. - A TO may be created for each stock request or each portion of a stock request in each wave. Once the warehouse management application creates the TOs, the TOs may then be released to the warehouse for processing. During TO processing, each TO is carried out by the warehouse workers, where the stock items described in each stock request are moved from the source location (such as a source storage bin) to the destination location (such as a destination storage bin) within the warehouse complex.
- Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
- The foregoing description of possible implementations consistent with the present invention does not represent a comprehensive list of all such implementations or all variations of the implementations described. The description of only some implementations should not be construed as an intent to exclude other implementations. One of ordinary skill in the art will understand how to implement the invention in the appended claims in may other ways, using equivalents and alternatives that do not depart from the scope of the following claims.
- The systems and methods disclosed herein may be embodied in various forms including, for example, a data processor, such as a computer that also includes a database. Moreover, the above-noted features and other aspects and principles of the present invention may be implemented in various environments. Such environments and related applications may be specially constructed for performing the various processes and operations according to the invention or they may include a general-purpose computer or computing platform selectively activated or reconfigured by code to provide the necessary functionality. The processes disclosed herein are not inherently related to any particular computer or other apparatus, and may be implemented by a suitable combination of hardware, software, and/or firmware. For example, various general-purpose machines may be used with programs written in accordance with teachings of the invention, or it may be more convenient to construct a specialized apparatus or system to perform the required methods and techniques.
- Systems and methods consistent with the present invention also include computer readable media that include program instruction or code for performing various computer-implemented operations based on the methods and processes of the invention. The media and program instructions may be those specially designed and constructed for the purposes of the invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of program instructions include, for example, machine code, such as produced by a compiler, and files containing a high level code that can be executed by the computer using an interpreter.
Claims (51)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/130,104 US7890389B2 (en) | 2005-05-17 | 2005-05-17 | Methods and systems for grouping and managing stock requests |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/130,104 US7890389B2 (en) | 2005-05-17 | 2005-05-17 | Methods and systems for grouping and managing stock requests |
Publications (2)
Publication Number | Publication Date |
---|---|
US20060287939A1 true US20060287939A1 (en) | 2006-12-21 |
US7890389B2 US7890389B2 (en) | 2011-02-15 |
Family
ID=37574565
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/130,104 Active 2029-02-14 US7890389B2 (en) | 2005-05-17 | 2005-05-17 | Methods and systems for grouping and managing stock requests |
Country Status (1)
Country | Link |
---|---|
US (1) | US7890389B2 (en) |
Cited By (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070156493A1 (en) * | 2005-12-30 | 2007-07-05 | Mathias Tebbe | Architectural desigh for time recording application software |
US20070233539A1 (en) * | 2006-03-30 | 2007-10-04 | Philipp Suenderhauf | Providing human capital management software application as enterprise services |
US20070233575A1 (en) * | 2006-03-30 | 2007-10-04 | Arthur Berger | Architectural design for strategic sourcing application software |
US20090082902A1 (en) * | 2007-09-24 | 2009-03-26 | International Business Machines Corporation | Warehouse Management System Based on Pick Velocity |
US20090164343A1 (en) * | 2007-12-20 | 2009-06-25 | International Business Machines Corporation | Auto-cascading clear to build engine for multiple location order level parts management |
US20100070556A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Data Migration Application Software |
US20120117075A1 (en) * | 2010-11-04 | 2012-05-10 | Electron Database Corporation | Systems and methods for grouped request execution |
US8312416B2 (en) | 2006-04-13 | 2012-11-13 | Sap Ag | Software model business process variant types |
US8311904B2 (en) | 2008-12-03 | 2012-11-13 | Sap Ag | Architectural design for intra-company stock transfer application software |
US8315900B2 (en) | 2007-12-31 | 2012-11-20 | Sap Ag | Architectural design for self-service procurement application software |
US8316344B2 (en) | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
US8315926B2 (en) | 2008-09-18 | 2012-11-20 | Sap Ag | Architectural design for tax declaration application software |
US8321832B2 (en) | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
US8321831B2 (en) | 2005-12-30 | 2012-11-27 | Sap Ag | Architectural design for internal projects application software |
US8321308B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for manual invoicing application software |
US8321306B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
US8321250B2 (en) | 2008-09-18 | 2012-11-27 | Sap Ag | Architectural design for sell from stock application software |
US8326703B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US8327319B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
US8326702B2 (en) | 2006-03-30 | 2012-12-04 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8326706B2 (en) | 2008-09-18 | 2012-12-04 | Sap Ag | Providing logistics execution application as enterprise services |
US8352338B2 (en) | 2008-09-18 | 2013-01-08 | Sap Ag | Architectural design for time recording application software |
US8370794B2 (en) | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
US8374896B2 (en) | 2008-09-18 | 2013-02-12 | Sap Ag | Architectural design for opportunity management application software |
US8380553B2 (en) | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
US8380549B2 (en) | 2008-09-18 | 2013-02-19 | Sap Ag | Architectural design for embedded support application software |
US8386325B2 (en) | 2008-09-18 | 2013-02-26 | Sap Ag | Architectural design for plan-driven procurement application software |
US8396749B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US8396761B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing product catalog software application as enterprise services |
US8396731B2 (en) | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
US8401936B2 (en) | 2007-12-31 | 2013-03-19 | Sap Ag | Architectural design for expense reimbursement application software |
US8402426B2 (en) | 2005-12-30 | 2013-03-19 | Sap Ag | Architectural design for make to stock application software |
US8401908B2 (en) | 2008-12-03 | 2013-03-19 | Sap Ag | Architectural design for make-to-specification application software |
US8401928B2 (en) | 2008-09-18 | 2013-03-19 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US8438119B2 (en) | 2006-03-30 | 2013-05-07 | Sap Ag | Foundation layer for services based enterprise software architecture |
US8442850B2 (en) | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US8447657B2 (en) | 2007-12-31 | 2013-05-21 | Sap Ag | Architectural design for service procurement application software |
US8510143B2 (en) | 2007-12-31 | 2013-08-13 | Sap Ag | Architectural design for ad-hoc goods movement software |
US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US8538864B2 (en) | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
US8595077B2 (en) | 2008-09-18 | 2013-11-26 | Sap Ag | Architectural design for service request and order management application software |
US8660904B2 (en) | 2005-12-30 | 2014-02-25 | Sap Ag | Architectural design for service request and order management application software |
US8671033B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Architectural design for personnel events application software |
US8671035B2 (en) | 2008-12-11 | 2014-03-11 | Sap Ag | Providing payroll software application as enterprise services |
US8671034B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing human capital management software application as enterprise services |
US8671032B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing payment software application as enterprise services |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US8738476B2 (en) | 2008-12-03 | 2014-05-27 | Sap Ag | Architectural design for selling standardized services application software |
US8818884B2 (en) | 2008-09-18 | 2014-08-26 | Sap Ag | Architectural design for customer returns handling application software |
US20160140489A1 (en) * | 2014-11-13 | 2016-05-19 | Alibaba Group Holding Limited | Managing warehouse information |
CN110717701A (en) * | 2018-07-13 | 2020-01-21 | 阿里巴巴集团控股有限公司 | Simulation wave generation method and device and electronic equipment |
US11055661B1 (en) * | 2020-02-17 | 2021-07-06 | Coupang Corp. | Warehouse inventory item location consolidations based on real-time volumetric space utilization |
US11475394B2 (en) * | 2021-02-22 | 2022-10-18 | Coupang Corp. | Method and apparatus for providing information |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10235640B2 (en) * | 2010-11-03 | 2019-03-19 | International Business Machines Corporation | Cost-based migration waves planning |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030177050A1 (en) * | 2001-12-27 | 2003-09-18 | Manugistics, Inc. | System and method for order group planning with attribute based planning |
-
2005
- 2005-05-17 US US11/130,104 patent/US7890389B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030177050A1 (en) * | 2001-12-27 | 2003-09-18 | Manugistics, Inc. | System and method for order group planning with attribute based planning |
Cited By (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8326703B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US8688495B2 (en) | 2005-12-30 | 2014-04-01 | Sap Ag | Architectural design for time recording application software |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US8660904B2 (en) | 2005-12-30 | 2014-02-25 | Sap Ag | Architectural design for service request and order management application software |
US20070156493A1 (en) * | 2005-12-30 | 2007-07-05 | Mathias Tebbe | Architectural desigh for time recording application software |
US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US8402426B2 (en) | 2005-12-30 | 2013-03-19 | Sap Ag | Architectural design for make to stock application software |
US8396731B2 (en) | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
US8316344B2 (en) | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
US8380553B2 (en) | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
US8370794B2 (en) | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
US8321831B2 (en) | 2005-12-30 | 2012-11-27 | Sap Ag | Architectural design for internal projects application software |
US8327319B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
US8538864B2 (en) | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
US8396749B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US20070233539A1 (en) * | 2006-03-30 | 2007-10-04 | Philipp Suenderhauf | Providing human capital management software application as enterprise services |
US20070233575A1 (en) * | 2006-03-30 | 2007-10-04 | Arthur Berger | Architectural design for strategic sourcing application software |
US8326702B2 (en) | 2006-03-30 | 2012-12-04 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8442850B2 (en) | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
US8438119B2 (en) | 2006-03-30 | 2013-05-07 | Sap Ag | Foundation layer for services based enterprise software architecture |
US8396761B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing product catalog software application as enterprise services |
US8321832B2 (en) | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
US8312416B2 (en) | 2006-04-13 | 2012-11-13 | Sap Ag | Software model business process variant types |
US20090082902A1 (en) * | 2007-09-24 | 2009-03-26 | International Business Machines Corporation | Warehouse Management System Based on Pick Velocity |
US8407108B2 (en) | 2007-09-24 | 2013-03-26 | International Business Machines Corporation | Warehouse management system based on pick velocity |
US20090164343A1 (en) * | 2007-12-20 | 2009-06-25 | International Business Machines Corporation | Auto-cascading clear to build engine for multiple location order level parts management |
US8671033B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Architectural design for personnel events application software |
US8671032B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing payment software application as enterprise services |
US8315900B2 (en) | 2007-12-31 | 2012-11-20 | Sap Ag | Architectural design for self-service procurement application software |
US8401936B2 (en) | 2007-12-31 | 2013-03-19 | Sap Ag | Architectural design for expense reimbursement application software |
US8671034B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing human capital management software application as enterprise services |
US8510143B2 (en) | 2007-12-31 | 2013-08-13 | Sap Ag | Architectural design for ad-hoc goods movement software |
US8447657B2 (en) | 2007-12-31 | 2013-05-21 | Sap Ag | Architectural design for service procurement application software |
US8386325B2 (en) | 2008-09-18 | 2013-02-26 | Sap Ag | Architectural design for plan-driven procurement application software |
US8315926B2 (en) | 2008-09-18 | 2012-11-20 | Sap Ag | Architectural design for tax declaration application software |
US8374896B2 (en) | 2008-09-18 | 2013-02-12 | Sap Ag | Architectural design for opportunity management application software |
US8352338B2 (en) | 2008-09-18 | 2013-01-08 | Sap Ag | Architectural design for time recording application software |
US8380549B2 (en) | 2008-09-18 | 2013-02-19 | Sap Ag | Architectural design for embedded support application software |
US8401928B2 (en) | 2008-09-18 | 2013-03-19 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8321250B2 (en) | 2008-09-18 | 2012-11-27 | Sap Ag | Architectural design for sell from stock application software |
US20100070556A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Data Migration Application Software |
US8818884B2 (en) | 2008-09-18 | 2014-08-26 | Sap Ag | Architectural design for customer returns handling application software |
US8595077B2 (en) | 2008-09-18 | 2013-11-26 | Sap Ag | Architectural design for service request and order management application software |
US8326706B2 (en) | 2008-09-18 | 2012-12-04 | Sap Ag | Providing logistics execution application as enterprise services |
US8321308B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for manual invoicing application software |
US8401908B2 (en) | 2008-12-03 | 2013-03-19 | Sap Ag | Architectural design for make-to-specification application software |
US8321306B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
US8738476B2 (en) | 2008-12-03 | 2014-05-27 | Sap Ag | Architectural design for selling standardized services application software |
US8311904B2 (en) | 2008-12-03 | 2012-11-13 | Sap Ag | Architectural design for intra-company stock transfer application software |
US8671035B2 (en) | 2008-12-11 | 2014-03-11 | Sap Ag | Providing payroll software application as enterprise services |
US8336051B2 (en) * | 2010-11-04 | 2012-12-18 | Electron Database Corporation | Systems and methods for grouped request execution |
US20120117075A1 (en) * | 2010-11-04 | 2012-05-10 | Electron Database Corporation | Systems and methods for grouped request execution |
US20160140489A1 (en) * | 2014-11-13 | 2016-05-19 | Alibaba Group Holding Limited | Managing warehouse information |
CN110717701A (en) * | 2018-07-13 | 2020-01-21 | 阿里巴巴集团控股有限公司 | Simulation wave generation method and device and electronic equipment |
US11055661B1 (en) * | 2020-02-17 | 2021-07-06 | Coupang Corp. | Warehouse inventory item location consolidations based on real-time volumetric space utilization |
US11475394B2 (en) * | 2021-02-22 | 2022-10-18 | Coupang Corp. | Method and apparatus for providing information |
Also Published As
Publication number | Publication date |
---|---|
US7890389B2 (en) | 2011-02-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7890389B2 (en) | Methods and systems for grouping and managing stock requests | |
US9152941B2 (en) | Systems and methods for automated parallelization of back-order processing | |
US6006193A (en) | Computer executable workflow control system | |
US7802204B2 (en) | Data visualization for service requests | |
US8386342B2 (en) | Method, system, and computer program product for performing inventory management | |
US20090013106A1 (en) | Flexible and error resistant data buffering and connectivity | |
US20070129984A1 (en) | Systems and methods for consolidating order processing items | |
US20060059060A1 (en) | Systems and methods for executing planning services | |
US20060059005A1 (en) | Systems and methods for managing data in an advanced planning environment | |
US20060059059A1 (en) | Systems and methods for managing the execution of services | |
MXPA01002771A (en) | Computer-implemented product development planning method. | |
US20070124213A1 (en) | Systems and methods for automatically assigning an incoming quantity of goods in response to an event | |
US20070100881A1 (en) | Method, system and storage medium for identifying and allocating surplus inventory | |
US20230153892A1 (en) | Electronic Device for Managing Logistics Information and Control Method Thereof | |
US20100153952A1 (en) | Methods, systems, and computer program products for managing batch operations in an enterprise data integration platform environment | |
CN113298503A (en) | Government affair-oriented workflow management system and database and table dividing method thereof | |
EP1519289A1 (en) | Method for maintaining information about multiple instances of an activity | |
CN101046822B (en) | Centralized management of data nodes | |
US7373212B2 (en) | Allocating products using classifications of orders for the products | |
US8396762B2 (en) | Systems and methods for validating subsititution chains of an order | |
US20060224431A1 (en) | Data processing method, system and computer program | |
US8200701B2 (en) | Handling of data in a data sharing system | |
Braune et al. | Applying genetic algorithms to the optimization of production planning in a real-world manufacturing environment | |
US20070106546A1 (en) | Systems and methods for automatically selecting a plurality of specific order items from a plurality of order items | |
US10496081B2 (en) | Method for fulfilling demands in a plan |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAP AKTIENGESELLSCHAFT, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HAREL, ORIT;HADARI, MALKIEL;MANDEL, ALEXANDER;AND OTHERS;SIGNING DATES FROM 20050414 TO 20050501;REEL/FRAME:016579/0378 Owner name: SAP AKTIENGESELLSCHAFT, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HAREL, ORIT;HADARI, MALKIEL;MANDEL, ALEXANDER;AND OTHERS;REEL/FRAME:016579/0378;SIGNING DATES FROM 20050414 TO 20050501 |
|
AS | Assignment |
Owner name: SAP AG, GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:SAP AKTIENGESELLSCHAFT;REEL/FRAME:017377/0349 Effective date: 20050609 Owner name: SAP AG,GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:SAP AKTIENGESELLSCHAFT;REEL/FRAME:017377/0349 Effective date: 20050609 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: SAP SE, GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:SAP AG;REEL/FRAME:033625/0334 Effective date: 20140707 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |