Managing consistent interfaces for demand planning business objects across heterogeneous systems
First Claim
Patent Images
1. A computer-implemented method for configuring a planning environment for defining relevant planning parameters, the method steps performed by a processor and comprising:
- generating a first message by a first application, the first application executing in an environment of computer systems providing message-based services, wherein the first message comprises a request to create a demand planning scenario and includes a first message package hierarchically organized in memory as;
a demand planning scenario create request message entity; and
a demand planning scenario package, where the demand planning scenario package includes a demand planning scenario entity, a key figure package, a characteristic package, and a periodicity package, wherein the demand planning scenario entity includes an ID, a description, and a measure unit, wherein the key figure package includes at least one key figure entity, where each key figure entity includes a demand plan key figure ID, a demand plan key figure type code, a demand plan key figure disaggregation on-fact code, a demand plan key figure accuracy code, a negative values allowed indicator, a zero allowed indicator, and a zero fixable allowed indicator, wherein the characteristic package includes at least one characteristic entity, where each characteristic entity includes a demand plan characteristic ID, and wherein the periodicity package includes at least one periodicity entity, where each periodicity entity includes a calendar unit code;
processing a second message received from a second application in response to the second application'"'"'s processing of the first message according to the hierarchical organization of the first message package, the second application executing in the environment of computer systems providing message-based services, wherein the second message is a confirmation concerning the request to create a demand planning scenario and includes a second message package hierarchically organized in memory as;
a demand planning scenario create confirmation message; and
a demand planning scenario package and a log package, where the demand planning scenario create confirmation message includes a demand planning scenario entity, wherein the demand planning scenario entity includes an ID and a description, and wherein the log package includes a log entity;
generating a third message by the first application, wherein the third message comprises a request to change a demand planning scenario and includes a third message package including a demand planning scenario package;
processing a fourth message received from the second application in response to the second application'"'"'s processing of the third message, wherein the fourth message comprises a confirmation concerning the request to change a demand planning scenario and includes a fourth message package;
generating a fifth message by the first application, wherein the fifth message comprises a request to delete a demand planning scenario and includes a fifth message package comprising a demand planning scenario package;
processing a sixth message received from the second application in response to the second application'"'"'s processing of the fifth message, wherein the sixth message comprises a confirmation concerning the request to delete a demand planning scenario and includes a sixth message package;
generating a seventh message by the first application, wherein the seventh message comprises an inquiry by ID to return the details of a demand planning scenario and includes a seventh message package comprising a demand planning scenario package that includes a demand planning scenario selection by ID entity;
processing an eighth message received from the second application in response to the second application'"'"'s processing of the seventh message, wherein the eighth message comprises a response concerning the inquiry by ID to return the details of a demand planning scenario and includes an eighth message package;
generating a ninth message by the first application, wherein the ninth message comprises an inquiry to return a list of available demand planning scenarios and includes a ninth message package comprising a demand planning scenario package; and
processing a tenth message received from the second application in response to the second application'"'"'s processing of the ninth message, wherein the tenth message comprises a response concerning the inquiry to return a list of available demand planning scenarios and includes a tenth message package.
2 Assignments
0 Petitions
Accused Products
Abstract
A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. Specifically, example business objects include DemandPlanningScenario, DemandPlanningScenarioTemplate, and DemandPlanningView.
305 Citations
15 Claims
-
1. A computer-implemented method for configuring a planning environment for defining relevant planning parameters, the method steps performed by a processor and comprising:
-
generating a first message by a first application, the first application executing in an environment of computer systems providing message-based services, wherein the first message comprises a request to create a demand planning scenario and includes a first message package hierarchically organized in memory as; a demand planning scenario create request message entity; and a demand planning scenario package, where the demand planning scenario package includes a demand planning scenario entity, a key figure package, a characteristic package, and a periodicity package, wherein the demand planning scenario entity includes an ID, a description, and a measure unit, wherein the key figure package includes at least one key figure entity, where each key figure entity includes a demand plan key figure ID, a demand plan key figure type code, a demand plan key figure disaggregation on-fact code, a demand plan key figure accuracy code, a negative values allowed indicator, a zero allowed indicator, and a zero fixable allowed indicator, wherein the characteristic package includes at least one characteristic entity, where each characteristic entity includes a demand plan characteristic ID, and wherein the periodicity package includes at least one periodicity entity, where each periodicity entity includes a calendar unit code; processing a second message received from a second application in response to the second application'"'"'s processing of the first message according to the hierarchical organization of the first message package, the second application executing in the environment of computer systems providing message-based services, wherein the second message is a confirmation concerning the request to create a demand planning scenario and includes a second message package hierarchically organized in memory as; a demand planning scenario create confirmation message; and a demand planning scenario package and a log package, where the demand planning scenario create confirmation message includes a demand planning scenario entity, wherein the demand planning scenario entity includes an ID and a description, and wherein the log package includes a log entity; generating a third message by the first application, wherein the third message comprises a request to change a demand planning scenario and includes a third message package including a demand planning scenario package; processing a fourth message received from the second application in response to the second application'"'"'s processing of the third message, wherein the fourth message comprises a confirmation concerning the request to change a demand planning scenario and includes a fourth message package; generating a fifth message by the first application, wherein the fifth message comprises a request to delete a demand planning scenario and includes a fifth message package comprising a demand planning scenario package; processing a sixth message received from the second application in response to the second application'"'"'s processing of the fifth message, wherein the sixth message comprises a confirmation concerning the request to delete a demand planning scenario and includes a sixth message package; generating a seventh message by the first application, wherein the seventh message comprises an inquiry by ID to return the details of a demand planning scenario and includes a seventh message package comprising a demand planning scenario package that includes a demand planning scenario selection by ID entity; processing an eighth message received from the second application in response to the second application'"'"'s processing of the seventh message, wherein the eighth message comprises a response concerning the inquiry by ID to return the details of a demand planning scenario and includes an eighth message package; generating a ninth message by the first application, wherein the ninth message comprises an inquiry to return a list of available demand planning scenarios and includes a ninth message package comprising a demand planning scenario package; and processing a tenth message received from the second application in response to the second application'"'"'s processing of the ninth message, wherein the tenth message comprises a response concerning the inquiry to return a list of available demand planning scenarios and includes a tenth message package. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A computer-implemented method for using a preconfigured template for a standard demand planning scenario, the method steps performed by a processor and comprising:
-
generating a first message by a first application, the first application executing in an environment of computer systems providing message-based services, wherein the first message comprises a request to create a demand planning scenario template and includes a first message package hierarchically organized in memory as; a demand planning scenario template create request message entity; and a demand planning scenario template package, where the demand planning scenario template package includes a demand planning scenario template entity, a key figure package, a characteristic package, and a periodicity package, where the demand planning scenario template entity includes an ID, a description, and a measure unit code wherein the key figure package includes at least one key figure entity, where each key figure entity includes a demand plan key figure ID, a demand plan key figure type code, a demand plan key figure disaggregation on-fact code, a demand plan key figure disaggregation on-time value, a demand plan key figure accuracy code, a negative values allowed indicator, a zero allowed indicator, and a zero fixable allowed indicator, wherein the characteristic package includes at least one characteristic entity, where each characteristic entity includes a demand plan characteristic ID, and wherein the periodicity package includes at least one periodicity entity, where each periodicity entity includes a calendar unit code; processing a second message received from a second application in response to the second application'"'"'s processing of the first message according to the hierarchical organization of the first message package, the second application executing in the environment of computer systems providing message-based services, wherein the second message comprises a confirmation concerning the request to create a demand planning scenario template and includes a second message package hierarchically organized in memory as; a demand planning scenario template create confirmation message entity; and a demand planning scenario template package and a log package, the demand planning scenario template package includes a demand planning scenario template entity, where the demand planning scenario entity includes an ID and a description, and wherein the log package includes a log entity; generating a third message by the first application, wherein the third message comprises a request to change a demand planning scenario template and includes a third message package including a demand planning scenario template package that includes a key figure package, a characteristic package, and a periodicity package; processing a fourth message received from the second application in response to the second application'"'"'s processing of the third message, wherein the fourth message comprises a confirmation concerning the request to change a demand planning scenario template and includes a fourth message package; generating a fifth message by the first application, wherein the fifth message comprises a request to delete a demand planning scenario template and includes a fifth message package including a demand planning scenario template package; processing a sixth message received from the second application in response to the second application'"'"'s processing of the fifth message, wherein the sixth message comprises a confirmation concerning the request to delete a demand planning scenario template and includes a sixth message package; generating a seventh message by the first application, wherein the seventh message comprises an inquiry by ID to return details of a demand planning scenario template and includes a seventh message package including a demand planning scenario package that includes a demand planning scenario template selection by ID entity; processing an eighth message received from the second application in response to the second application'"'"'s processing of the seventh message, wherein the eighth message comprises a response concerning the inquiry by ID to return details of a demand planning scenario template and includes an eighth message package; generating a ninth message by the first application, wherein the ninth message comprises an inquiry to return a list of available demand planning scenario templates and includes a ninth message package including a demand planning scenario template package; and processing a tenth message received from the second application in response to the second application'"'"'s processing of the ninth message, wherein the tenth message comprises a response concerning the inquiry to return a list of available demand planning scenario templates and includes a tenth message package. - View Dependent Claims (7, 8, 9, 10)
-
-
11. A computer-implemented method for displaying and presenting planning data related to a planning process, the method comprising:
-
generating a first message by a first application, the first application executing in an environment of computer systems providing message-based services, wherein the first message comprises an inquiry for the details of a demand planning view and includes a first message package hierarchically organized in memory as; a demand planning view by ID query message entity; and a demand planning view package, where the demand planning view package includes a demand planning view selection by ID entity, wherein the demand planning view selection by ID entity includes a demand planning view ID; processing a second message received from a second application in response to the second application'"'"'s processing of the first message according to the hierarchical organization of the first message package, the second application executing in the environment of computer systems providing message-based services, wherein the second message comprises a response to the inquiry for the details of a demand planning view and includes a second message package hierarchically organized in memory as; a demand planning view by ID response message entity; and a demand planning view package, where the demand planning view package includes a demand planning view entity, a key figure package, a characteristic package, and a time series period package, and a log package, where the demand planning view entity includes an ID, a description, system administrative data, and a demand planning scenario ID, where the key figure package includes at least one key figure entity, where each key figure entity includes a demand plan key figure, a description, and a planning version ID, wherein the characteristic package includes at least one characteristic entity, where each characteristic entity includes a demand plan characteristic ID and a description, wherein the time series period package includes at least one time series period entity, where each time series period entity includes an ID, a description, and a date period, and wherein the log package includes a log entity; generating a third message by the first application, wherein the third message comprises an inquiry for the identifying elements of demand planning views and includes a third message package including a demand planning view package; processing a fourth message received from the second application in response to the second application'"'"'s processing of the third message, wherein the fourth message comprises a response to the inquiry for the identifying elements of demand planning views and includes a fourth message package; generating a fifth message by the first application, wherein the fifth message comprises an inquiry for the identifying elements of demand planning views assigned to a particular demand planning scenario and includes a fifth message package including a demand planning view package; processing a sixth message received from the second application in response to the second application'"'"'s processing of the fifth message, wherein the sixth message comprises a response to the inquiry for the identifying elements of demand planning views assigned to the particular demand planning scenario and includes a sixth message package; generating a seventh message by the first application, wherein the seventh message comprises a request to create a demand plan selection for a particular demand planning view and includes a seventh message package including a demand planning view package that includes a demand plan selection package; processing an eighth message received from the second application in response to the second application'"'"'s processing of the seventh message, wherein the eighth message comprises a confirmation concerning the request to create a demand plan selection for a particular demand planning view and includes an eighth message package; generating a ninth message by the first application, wherein the ninth message comprises a request to delete a demand plan selection from a particular demand planning view and includes a ninth message package including a demand planning view package that includes a demand plan selection; and processing a tenth message received from the second application in response to the second application'"'"'s processing of the ninth message, wherein the tenth message comprises a confirmation to the request to delete a demand plan selection from the particular demand planning view and includes a tenth message package. - View Dependent Claims (12, 13, 14, 15)
-
Specification