Using consumption data and an inventory model to generate a replenishment plan

• US 10,181,107 B2
• Filed: 06/25/2014
• Issued: 01/15/2019
• Est. Priority Date: 06/25/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Gopinath, Nithin, Saindane, Kiran, Zivelin, Nadav, Feldman, Bart, Liebson, Michael, Goyal, Vikash, Periakaruppan, Nagappan, Arkin, Eytan E.
• Primary Examiner(s): Champagne, Luna
• Application Number:
  US14/314,442
• Publication Number:
  US 20150379449A1
• Time in Patent Office: 1,665 Days
• Field of Search: 705 731, 705 738, 705 734
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders

Abstract

A method, system, and computer program product for generating forecasts and replenishment plans. Some embodiments commence upon receiving point-of-sale data, then receiving distribution-level order data in a second data format. The first point-of-sale data comprises an item identifier and a first date or first date range, and the distribution-level order data comprises the item identifier and a second date or second date range. The originators of the order data are determined using address identifiers (e.g., network location identifiers). The received data is combined wherein at least a portion of the point-of-sale data is combined with at least a portion of the distribution-level order data to generate a combined forecast for the item. Further processing includes receiving an inventory model parameter and combining at least a portion of the first point-of-sale consumption data with at least a portion of the distribution-level order data to generate a replenishment plan for the item.

Claims

1. A method comprising:

identifying a computing system having a storage subsystem, wherein the storage subsystem comprises at least one database component having a series of records stored on a computer-readable medium, a first subset of the series of records being from a first plurality of sources, and a second subset of the series of records being from a second plurality of sources;

identifying, from the first subset of the series of records, a first source of data in a first data format, the first data format comprising at least an item identifier and a first date range, the first subset of the series of records having first address identifiers associated with the data in the first data format, the first address identifiers comprising at least one of an IP address, a network identifier, or a uniform resource locator, one more individual records of the data recorded in the first data format using a selected first application programming interface of a first plurality of application programming interfaces, the first application programming interface selected based on an origin of the at least some of the data in the first data format, wherein different application programming interfaces of the first plurality of application programming interfaces are used for processing different formats of the first subset of the series of records from the first plurality of sources;

identifying, from the second subset of the series of records, a second source of data in a second data format, the second data format comprising at least the item identifier and a second date range, the second subset of the series of records having second address identifiers associated with the data in the second data format, the second address identifiers comprising at least one of an IP address, a network identifier, or a uniform resource locator, one more individual records of the data recorded in the second data format using a selected second application programming interface of a second plurality of application programming interfaces, the second application programming interface selected based on an origin of the at least some of the data in the second data format, wherein different application programming interfaces of the second plurality of application programming interfaces are used for processing different formats of the second subset of the series of records from the second plurality of sources, wherein the first date range in the first data format is different from the second date range in the second data format;

converting records from both the first source of data in the first data format and the second source of data in the second data format into a normalized format;

combining at least a portion of the records from the first source of data in the normalized format with at least a different portion of the records from the second source of data in the normalized format to generate combined data for an item;

implementing a first user interface and a second user interface that is different than the first user interface, wherein the first user interface comprises a screen widget having a selector menu for selecting different modifications of data that is displayed on the second user interface, the second user interface displaying a database table comprising;

(i) a first column that identifies a selected modification to the item;

(ii) a second column that holds results from a specific modification of the data that are derived from one or more additional parameters corresponding to the item based on the selected modification from the selector menu in the screen widget, wherein the selected modification is identified in the first column of the second user interface;

(iii) a one or more additional columns that hold the one or more additional parameters corresponding to the selected modification identified in the first column; and

(iv) a plurality of database table rows, each row from the plurality of database table rows corresponding to a different item;

receiving a selection of a modification of data in the first column of the second user interface through the selector menu from the screen widget on the first user interface; and

generating the data corresponding to the item in the second column of the database table within the second user interface based at least on the combined data for the item, the selected modification that was received from the first user interface, and the one or more additional parameters in the one or more additional columns of the second user interface.

2. The method of claim 1, further comprising transmitting a plan for the item to at least one originator of the second source of data.

3. The method of claim 1, further comprising determining a data origin using a first address identifier.

4. The method of claim 3, wherein the first address identifier comprises a site identifier.

5. The method of claim 4, wherein the site identifier comprises at least one of an account number an account type, a site type, a site group, a corresponding IP address, a network identifier, and a URL.

6. The method of claim 1, further comprising maintaining a repository of at least one model parameter.

7. The method of claim 1, wherein the additional parameters correspond to at least one of a confidence interval, a standard error value, or an optional override.

8. The method of claim 1, wherein the first source of data in a first data format is received from a first entity and the second source of data in a second data format is received from a second entity.

9. The method of claim 8, wherein the first entity is different from the second entity.

10. The method of claim 1, further comprising:

transmitting a plan for the item to at least one originator of the second source of data;

determining a data origin using a first address identifier;

maintaining a repository of at least one model parameter; and

wherein;

the first source of data in a first data format is received from a first entity and the second source of data in a second data format is received from a second entity, the first entity is different from the second entity, the first data corresponds to sales data, and the second data format corresponds to distribution data,

the first entity comprises a consumer level entity, and the second entity comprises a distribution level entity,

the normalized format comprises at least time normalized data,

the plan for the item comprises a time range,

the first address identifier comprises a site identifier,

the site identifier comprises at least one of an account number an account type, a site type, a site group, a corresponding IP address, a network identifier, and a URL.

11. A computer program product embodied in a non-transitory computer readable medium, the computer readable medium having stored thereon a sequence of instructions which, when executed by a processor causes the processor to execute a process, the process comprising:

identifying a series of records stored on a computer-readable medium, a first subset of the series of records being from a first plurality of sources, and a second subset of the series of records being from a second plurality of sources;

identifying, from the first subset of the series of records, a first source of data in a first data format, the first data format comprising at least an item identifier and a first date range, the first subset of the series of records having first address identifiers associated with the data in the first data format, the first address identifiers comprising at least one of an IP address, a network identifier, or a uniform resource locator, one more individual records of the data recorded in the first data format using a selected first application programming interface of a first plurality of application programming interfaces, the first application programming interface selected based on an origin of the at least some of the data in the first data format, wherein different application programming interfaces of the first plurality of application programming interfaces are used for processing different formats of the first subset of the series of records from the first plurality of sources;

identifying, from the second subset of the series of records, a second source of data in a second data format, the second data format comprising at least the item identifier and a second date range, the second subset of the series of records having second address identifiers associated with the data in the second data format, the second address identifiers comprising at least one of an IP address, a network identifier, or a uniform resource locator, one more individual records of the data recorded in the second data format using a selected second application programming interface of a second plurality of application programming interfaces, the second application programming interface selected based on an origin of the at least some of the data in the second data format, wherein different application programming interfaces of the second plurality of application programming interfaces are used for processing different formats of the second subset of the series of records from the second plurality of sources, wherein the first date range in the first data format is different from the second date range in the second data format;

converting records from both the first source of data in the first data format and the second source of data in the second data format into a normalized format;

combining at least a portion of the records from the first source of data in the normalized format with at least a different portion of the records from the second source of data in the normalized format to generate combined data for an item;

implementing a first user interface and a second user interface that is different than the first user interface, wherein the first user interface comprises a screen widget having a selector menu for selecting different modifications of data that is displayed on the second user interface, the second user interface displaying a database table comprising;

(i) a first column that identifies a selected modification to the item;

(ii) a second column that holds results from a specific modification of the data that are derived from one or more additional parameters corresponding to the item based on the selected modification from the selector menu in the screen widget, wherein the selected modification is identified in the first column of the second user interface;

(iii) a one or more additional columns that hold the one or more additional parameters corresponding to the selected modification identified in the first column; and

(iv) a plurality of database table rows, each row from the plurality of database table rows corresponding to a different item;

receiving a selection of a modification of data in the first column of the second user interface through the selector menu from the screen widget on the first user interface; and

generating the data corresponding to the item in the second column of the database table within the second user interface based at least on the combined data for the item, the selected modification that was received from the first user interface, and the one or more additional parameters in the one or more additional columns of the second user interface.

12. The computer program product of claim 11, further comprising:

transmitting a plan for the item to at least one originator of the second source of data;

determining a data origin using a first address identifier;

maintaining a repository of at least one model parameter; and

wherein;

the first source of data in a first data format is received from a first entity and the second source of data in a second data format is received from a second entity, the first entity is different from the second entity, the first data corresponds to sales data, and the second data format corresponds to distribution data,

the first entity comprises a consumer level entity, and the second entity comprises a distribution level entity,

the normalized format comprises at least time normalized data,

the plan for the item comprises a time range,

the first address identifier comprises a site identifier,

the site identifier comprises at least one of an account number an account type, a site type, a site group, a corresponding IP address, a network identifier, and a URL.

13. The computer program product of claim 11, further comprising determining a data origin using a first address identifier.

14. The computer program product of claim 11, further comprising maintaining a repository of at least one model parameter.

15. The computer program product of claim 11, wherein the additional parameters correspond to at least one of a confidence interval, a standard error value, or an optional override.

16. The computer program product of claim 11, wherein the first source of data in a first data format is received from a first entity and the second source of data in a second data format is received from a second entity.

17. The computer program product of claim 16, wherein the first entity is different from the second entity.

18. A system comprising:

a processor;

a storage subsystem comprising at least one database component having a series of records stored on a computer-readable medium, a first subset of the series of records being from a first plurality of sources, and a second subset of the series of records being from a second plurality of sources;

a memory for holding programmable code, wherein the programmable code includes instructions executable by the processor to implement;

a first incoming data processing module identifying, from the first subset of the series of records, a first source of data in a first data format, the first data format comprising an item identifier and a first date or first date range, the first subset of the series of records having first address identifiers associated with the data in the first data format, the first address identifiers comprising at least one of an IP address, a network identifier, or a uniform resource locator, one more individual records of the data recorded in the first data format using a selected first application programming interface of a first plurality of application programming interfaces, the first application programming interface selected based on an origin of the at least some of the data in the first data format, wherein different application programming interfaces of the first plurality of application programming interfaces are used for processing different formats of the first subset of the series of records from the first plurality of sources;

a second incoming data processing module identifying, from the second subset of the series of records, a second source of data in a second data format, the second data format comprising at least the item identifier and a second date or second date range, the second subset of the series of records having second address identifiers associated with the data in the second data format, the second address identifiers comprising at least one of an IP address, a network identifier, or a uniform resource locator, one more individual records of the data recorded in the second data format using a selected second application programming interface of a second plurality of application programming interfaces, the second application programming interface selected based on an origin of the at least some of the data in the second data format, wherein different application programming interfaces of the second plurality of application programming interfaces are used for processing different formats of the second subset of the series of records from the second plurality of sources, wherein the first date range in the first data format is different from the second date range in the second data format; and

a replenishment plan generator combining at least a portion of the first subset of the series of records from the first source of data with at least a portion of the second subset of the series of records from the second source of data to generate a replenishment plan for an item by;

converting records from both the first source of data in the first data format and the second source of data in the second data format into a normalized format;

combining at least a portion of the records from the first source of data in the normalized format with at least a different portion of the records from the second source of data in the normalized format to generate combined data for an item;

implementing a first user interface and a second user interface that is different than the first user interface, wherein the first user interface comprises a screen widget having a selector menu for selecting different modifications of data that is displayed on the second user interface, the second user interface displaying a database table comprising;

(i) a first column that identifies a selected modification to the item;

(ii) a second column that holds results from a specific modification of the data that are derived from one or more additional parameters corresponding to the item based on the selected modification from the selector menu in the screen widget, wherein the selected modification is identified in the first column of the second user interface;

(iii) a one or more additional columns that hold the one or more additional parameters corresponding to the selected modification identified in the first column; and

(iv) a plurality of database table rows, each row from the plurality of database table rows corresponding to a different item;

receiving a selection of a modification of data in the first column of the second user interface through the selector menu from the screen widget on the first user interface; and

generating the data corresponding to the item in the second column of the database table within the second user interface based at least on the combined data for the item, the selected modification that was received from the first user interface, and the one or more additional parameters in the one or more additional columns of the second user interface.

19. The system of claim 18, wherein the first source of data in a first data format is received from a first entity and the second source of data in a second data format is received from a second entity.

20. The system of claim 18, wherein the programmable code includes additional instructions executable by the processor to implement:

transmitting a plan for the item to at least one originator of the second source of data;

determining a data origin using a first address identifier;

maintaining a repository of at least one model parameter; and

wherein;

the first source of data in a first data format is received from a first entity and the second source of data in a second data format is received from a second entity, the first entity is different from the second entity, the first data corresponds to sales data, and the second data format corresponds to distribution data,

the first entity comprises a consumer level entity, and the second entity comprises a distribution level entity,

the normalized format comprises at least time normalized data,

the plan for the item comprises a time range,

the first address identifier comprises a site identifier,

the site identifier comprises at least one of an account number an account type, a site type, a site group, a corresponding IP address, a network identifier, and a URL.