Abstract: Techniques and solutions are described for transferring metadata between software applications. A translation framework stores metadata models in a standard format. Source applications can cause metadata models to be stored in the translation framework in the standard format. A target application can receive metadata models, or elements thereof, from the translation framework, which metadata models can be optionally converted from the standard format to a target format used by the target application. The translation framework can store annotations to a metadata model in the form of custom metadata types. The custom metadata types can be used by one or both of the target application and a source application. Source applications can cause values to be stored for annotations they support. Target applications can read values for annotations they support. Source applications and target applications do not write or read, respectively, unsupported annotations.

Abstract: Techniques and solutions are described for transferring metadata between software applications. A translation framework stores metadata models in a standard format. Source applications can cause metadata models to be stored in the translation framework in the standard format. A target application can receive metadata models, or elements thereof, from the translation framework, which metadata models can be optionally converted from the standard format to a target format used by the target application. The translation framework can store annotations to a metadata model in the form of custom metadata types. The custom metadata types can be used by one or both of the target application and a source application. Source applications can cause values to be stored for annotations they support. Target applications can read values for annotations they support. Source applications and target applications do not write or read, respectively, unsupported annotations.

Abstract: In an example embodiment a market data management system allows users to track information regarding commodities. A representative market data management system comprises physical commodity objects including a plurality of fields that describe a real world commodity, market identifier objects including market identifier codes, and contract specification objects including a plurality of fields that describe a derivative contract specification for a particular commodity traded at a particular commodity market. In the data model, a one to many relationship may exist for a physical commodity object and contract specification objects (e.g., a given commodity may be traded according to different derivative contract specifications). The data model may also allow a many to many relationship between contract specification objects and market identifier objects (e.g.

Abstract: A system receives a commodity identification, a curve type, and a curve category. The system also receives an interpolation identification, an extrapolation identification, a read procedure, and a maximum number of days for a readback. The system further receives contract data, the contract data including a market identifier code, a derivative contract specification (DCS) identification, and a price type. The system uses the contract data to generate a commodity curve based on DCS, and displays the commodity curve based on DCS on an electronic display unit.

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. In some operations, software creates, updates, or otherwise processes information related to an outbound delivery business object.

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. In some operations, software creates, updates, or otherwise processes information related to a goods tag, a production bill of material hierarchy, and/or a release order template business object.