Oracle Retail Predictive Application Server
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Oracle Retail Predictive Application Server" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Oracle Retail Predictive Application Server|concern=this is nothing more than a press release from 2012 with no claim at all of notability in five years}} ~~~~ Timestamp: 20170405212804 21:28, 5 April 2017 (UTC) Administrators: delete |
The Oracle Retail Predictive Application Server (commonly referred to as RPAS) is a configurable software platform for developing forecasting and planning applications, following a Client/Server OLAP model. The RPAS platform provides capabilities such as a multidimensional database structure (it follows the MOLAP model), batch and online processing, a configurable slice-and-dice user interface, a sophisticated configurable calculation engine, user security and utility functions such as importing and exporting.[1]
RPAS is the foundation for a significant number of applications[2] that are part of the Oracle Retail solution footprint, such as Oracle Retail Demand Forecasting, Oracle Merchandise Financial Planning, Oracle Assortment Planning, Oracle Item Planning, Oracle Size Profile Optimization, Oracle Replenishment Optimization and Oracle Advanced Inventory Planning.
RPAS currently offers 2 data persistence options: a proprietary datastore based on Oracle Berkeley DB, or an Oracle RDBMS (which supports real time updates from external systems but reduces the performance of the MOLAP cubes). Originally the persistence layer (and some of the processing) was based on a MOLAP engine called Accumate/Acumen, originally developed by Mars Inc. for in house reporting and analysis but latterly owned by Lucent. Accumate is now no longer generally available or in support from Lucent. (Limited sustaining support for Accumate is available from Oracle to support older installations of RPAS that were Accumate based, based on a source code license that was held by the predecessor to Oracle Retail, Retek, with the source code license novated to Oracle for support purposes).
References
- ^ Oracle® Retail Predictive Application Server User Guide for the Classic Client, Release 13.3.1, Oracle Corporation, 2012
- ^ Oracle® Retail Assortment Planning, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Category Management, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Item Planning, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Item Planning Configured for COE, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Merchandise Financial Planning, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Demand Forecasting, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Replenishment Optimization, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Regular Price Optimization, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Size Profile Optimization, Release Notes, Release 13.3, Oracle Corporation, 2012
- Oracle® Retail Advanced Inventory Planning, Release Notes, Release 13.3, Oracle Corporation, 2012