7. A processor-implemented method to execute on one or more processors that perform the method, comprising: publishing at least one stored application-agnostic generic back end data model accessible to a user interface and a development environment; receiving an enterprise-specific configuration context; filtering generic back end data attributes associated with the at least one stored application-agnostic generic back end data model based on the enterprise-specific configuration context, to generate enterprise-specific derived model attributes associated with an enterprise-specific derived data model; generating an enterprise-specific user interface based on the enterprise-specific derived model attributes; deriving a set of mapping rules based on the enterprise-specific derived model attributes, the mapping rules to transform an end-user request received via the enterprise-specific user interface into a transformed request that communicates directly with the at least one stored application-agnostic generic back end data model; storing the set of mapping rules to be used to direct run-time data model request transformation activity based on the end-user request received via the enterprise-specific user interface; and publishing one of a modified catalog or a modified sales order via the enterprise-specific user interface, the modified catalog and the modified sales order derived from an original catalog and an original sales order, respectively, and the set of mapping rules.
7. A processor-implemented method to execute on one or more processors that perform the method, comprising: publishing at least one stored application-agnostic generic back end data model accessible to a user interface and a development environment; receiving an enterprise-specific configuration context; filtering generic back end data attributes associated with the at least one stored application-agnostic generic back end data model based on the enterprise-specific configuration context, to generate enterprise-specific derived model attributes associated with an enterprise-specific derived data model; generating an enterprise-specific user interface based on the enterprise-specific derived model attributes; deriving a set of mapping rules based on the enterprise-specific derived model attributes, the mapping rules to transform an end-user request received via the enterprise-specific user interface into a transformed request that communicates directly with the at least one stored application-agnostic generic back end data model; storing the set of mapping rules to be used to direct run-time data model request transformation activity based on the end-user request received via the enterprise-specific user interface; and publishing one of a modified catalog or a modified sales order via the enterprise-specific user interface, the modified catalog and the modified sales order derived from an original catalog and an original sales order, respectively, and the set of mapping rules. 12. The method of claim 7 , wherein the generic back end data attributes comprise at least one of appended table structures, extension points, or status schema.