Abstract: Computer-readable media, methods, and systems are disclosed for facilitating source to target translation and synchronization of production details for manufacturing of one or more production articles. A plurality of versioned technical design inputs in structured and unstructured formats is received. A plurality of translation inputs corresponding to one or more parameters associated with the plurality of versioned technical design inputs is received. A mapping of the plurality of versioned technical design inputs to a plurality of manufacturing data elements associated with one or more data models of a manufacturing system is automatically generated, based on the plurality of translation inputs. Finally, a plurality of manufacturing routings for implementing production of the one or more production articles is generated.

Abstract: The disclosure generally describes methods, software, and systems for providing solution descriptions. A problem description of a problem is received, from a client, at a cloud-based reasoning service. A solution description for a solution to the problem is received. Case metadata for a case defining the problem and solution are generated by the cloud-based reasoning service. The case metadata, including the problem description and solution description, are stored by the cloud-based reasoning service in a cases repository associating solutions with problems. A new problem is received at the cloud-based reasoning service. An automated analysis of the new problem is performed, and a comparison is made of the new problem with existing solutions in the cases repository to identify solutions matching the new problem. A new solution description is provided that is based on a match between the new problem description and the problem description and using the problem solution.

Abstract: The disclosure generally describes methods, software, and systems for providing solution descriptions. A problem description of a problem is received, from a client, at a cloud-based reasoning service. A solution description for a solution to the problem is received. Case metadata for a case defining the problem and solution are generated by the cloud-based reasoning service. The case metadata, including the problem description and solution description, are stored by the cloud-based reasoning service in a cases repository associating solutions with problems. A new problem is received at the cloud-based reasoning service. An automated analysis of the new problem is performed, and a comparison is made of the new problem with existing solutions in the cases repository to identify solutions matching the new problem. A new solution description is provided that is based on a match between the new problem description and the problem description and using the problem solution.

Abstract: The disclosure generally describes methods, software, and systems for providing solution descriptions. A problem description of a problem is received, from a client, at a cloud-based reasoning service. A solution description for a solution to the problem is received. Case metadata for a case defining the problem and solution are generated by the cloud-based reasoning service. The case metadata, including the problem description and solution description, are stored by the cloud-based reasoning service in a cases repository associating solutions with problems. A new problem is received at the cloud-based reasoning service. An automated analysis of the new problem is performed, and a comparison is made of the new problem with existing solutions in the cases repository to identify solutions matching the new problem. A new solution description is provided that is based on a match between the new problem description and the problem description and using the problem solution.

Abstract: Technologies are described for creating activity object instances corresponding to collection object instances, and for conducting tests between activity object instances and collection objects instances, and within a set of activity object instances. Tests can include determining whether collection object instances have counterpart activity object instances, and evaluating a collection object instance with respect to a corresponding activity object instance. Activity object instances can be set to be performed in a sequence, and a test can determine whether the sequence is consistent with sequencing rules. When activity object instances are automatically created from collection object instances, a user can be presented with a graphical user interface that includes representations of activity object instances, and the user can manipulate the graphical user interface to provide precedence information.

Abstract: Technologies are described for creating activity object instances corresponding to collection object instances, and for conducting tests between activity object instances and collection objects instances, and within a set of activity object instances. Tests can include determining whether collection object instances have counterpart activity object instances, and evaluating a collection object instance with respect to a corresponding activity object instance. Activity object instances can be set to be performed in a sequence, and a test can determine whether the sequence is consistent with sequencing rules. When activity object instances are automatically created from collection object instances, a user can be presented with a graphical user interface that includes representations of activity object instances, and the user can manipulate the graphical user interface to provide precedence information.

Abstract: The disclosure generally describes methods, software, and systems for providing solution descriptions. A problem description of a problem is received, from a client, at a cloud-based reasoning service. A solution description for a solution to the problem is received. Case metadata for a case defining the problem and solution are generated by the cloud-based reasoning service. The case metadata, including the problem description and solution description, are stored by the cloud-based reasoning service in a cases repository associating solutions with problems. A new problem is received at the cloud-based reasoning service. An automated analysis of the new problem is performed, and a comparison is made of the new problem with existing solutions in the cases repository to identify solutions matching the new problem. A new solution description is provided that is based on a match between the new problem description and the problem description and using the problem solution.

Abstract: An interface provides decision support in complex problem environments. An interface engine selectively communicates with a database to display (e.g., in tree form) proposed decisions and various corresponding outcomes resulting from cause-effect relationships of selected decisions. Structured data objects store state information (e.g., current/projected/target) of multi-faceted, inter-connected entities. Object metadata can include entity attributes and/or entity relationship details. The interface allows traversing the tree to explore the cause-effect relationships and/or validate various solution paths. The tree (including the proposed decisions, outcomes, and solution paths) may be initially generated up front, based upon particular problem scenario characteristics. Limited subsequent interaction between the interface engine and the underlying backend data store may enhance speed/performance/user experience.

Abstract: Example methods and systems are directed to dispatching database tasks. An application may access data associated with a task. The data may indicate features (e.g., processing functionality) that will be used to complete the task. The application may determine whether all such features are implemented in the database layer. The application may dispatch the task to the database layer if all features are implemented therein. The application may perform the task in the application layer if one or more of the features are not available in the database layer. In some example embodiments, the task involves materials requirements planning. Such a task may include determining, for a given bill of materials (“BOM”), the quantity of materials available on-hand, the quantity available from suppliers, the transport or delivery time for the various quantities, and other data regarding the BOM.

Abstract: An interface provides decision support in complex problem environments. An interface engine selectively communicates with a database to display (e.g., in tree form) proposed decisions and various corresponding outcomes resulting from cause-effect relationships of selected decisions. Structured data objects store state information (e.g., current/projected/target) of multi-faceted, inter-connected entities. Object metadata can include entity attributes and/or entity relationship details. The interface allows traversing the tree to explore the cause-effect relationships and/or validate various solution paths. The tree (including the proposed decisions, outcomes, and solution paths) may be initially generated up front, based upon particular problem scenario characteristics. Limited subsequent interaction between the interface engine and the underlying backend data store may enhance speed/performance/user experience.

Abstract: A method, a system and a computer program product for generating a change request object to and associating the generated object with an existing business object are disclosed. A desired update to a first business object is created. The first business object contains a plurality of attributes, where each attribute in the plurality of attributes has a value. Based on the created update, a second business object is generated. The second business object contains at least one change to a value of an attribute of the first business object and a copy of the value of the attribute of the first business object. The value of the attribute in the first business object is compared with a copy of the value of the attribute contained in the generated second business object. Based on the comparison, the second business object is associated with the first business object.

Abstract: Transactional data associated with a specific instance of a business scenario that includes an intersecting process feature requiring prerequisite action by a prerequisite process feature that is part of another business scenario can be linked to a scenario model providing a linearized representation in which other process features of the business scenario, the intersecting process feature, and the prerequisite process feature are arranged in a linear sequence. A navigation pane including a linear progression of user interface elements representing the linear sequence can be concurrently displayed with a work pane including other user interface elements corresponding to functionality provided by business software architecture features related to a currently selected process feature.

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.

Abstract: Example methods and systems are directed to dispatching database tasks. An application may access data associated with a task. The data may indicate features (e.g., processing functionality) that will be used to complete the task. The application may determine whether all such features are implemented in the database layer. The application may dispatch the task to the database layer if all features are implemented therein. The application may perform the task in the application layer if one or more of the features are not available in the database layer. In some example embodiments, the task involves materials requirements planning. Such a task may include determining, for a given bill of materials (“BOM”), the quantity of materials available on-hand, the quantity available from suppliers, the transport or delivery time for the various quantities, and other data regarding the BOM.

Abstract: Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing service request and order management. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include an Outbound Delivery process component, a Site Logistics Processing process component, an Inventory Processing process component, a Customer Requirement Processing process component, a Supply and Demand Matching process component, a Logistics Execution Control process component, a Service Request Processing process component, a Service Order Processing process component, and a Service Confirmation Processing process component.

Abstract: Transactional data associated with a specific instance of a business scenario that includes an intersecting process feature requiring prerequisite action by a prerequisite process feature that is part of another business scenario can be linked to a scenario model providing a linearized representation in which other process features of the business scenario, the intersecting process feature, and the prerequisite process feature are arranged in a linear sequence. A navigation pane including a linear progression of user interface elements representing the linear sequence can be concurrently displayed with a work pane including other user interface elements corresponding to functionality provided by business software architecture features related to a currently selected process feature.

Abstract: A current transactional context of a user of a business software architecture can be detected, optionally in response to a guidance request received from the user. At least one matching business process feature related to the current transactional context can be determined by comparing the current transactional context with process metadata in a process repository, and the matching business process feature can be compared to scenario metadata defining a set of business process features that are part of each of a plurality of business scenarios within the business configuration to identify at least one matching business scenario containing the matching business process feature. In a user interface, the at least one matching business process feature and the identified matching business scenario that contains the at least one matching business process feature can be highlighted.

Abstract: A business process relating to a reference business object and a specific instance of the business process to which the specific instance of the business object belongs can be identified. Instances of other business objects related to the identified specific instance of the business process or business scenario can be retrieved, and a status of each business process feature in the specific instance of the business process or business scenario can be calculated. A navigation pane of the user interface can display a plurality of first user interface elements illustrating a sequence of the plurality of business process features required to complete the business process or business scenario instance. The plurality of user interface elements can indicate a status of process steps for the identified specific instance of the business process or business scenario.

Abstract: A system and method are described for intelligently sourcing demand forecasts within a supply chain management (“SCM”) system based on a constrained supply chain model, in light of material and resource constraints. For example, a computer implemented method according to one embodiment of the invention comprises: calculating a demand forecast identifying anticipated demand for a product over a specified time period; identifying current sales orders for the product with delivery dates scheduled during the specified time period; generating an open forecast for the product based on the current sales orders and the anticipated demand; and sourcing different percentages of the open forecast from different plants, the percentages selected based on supply chain material and/or resource constraints. In addition, after the demand forecast is sourced, one embodiment of the invention employs additional techniques for intelligently sourcing new sales orders entering the SCM system.

Abstract: Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing a make to stock process. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include an Accounting process component; a Production process component; a Site Logistics process component; a Confirmation and Inventory process component; a Customer Requirement Processing process component; a Demand Forecast Processing process component; a Supply and Demand Matching process component; a Production Trigger and Response process component; an In-house Requirement Processing process component; a Sales Scheduling Agreement Processing process component; and a Demand Planning process component.