IDEAS home Printed from https://ideas.repec.org/h/spr/sprchp/978-3-540-92942-0_3.html
   My bibliography  Save this book chapter

SAP APO Architecture

In: Supply Chain Management with SAP APO¿

Author

Listed:
  • Jörg Thomas Dickersbach

Abstract

SAP APO™ consists technically of three parts: the database, the SAP BI™ data mart and the live cache. The SAP BI™ data mart consists of info cubes. The live cache is basically a huge main memory where the planning and the scheduling relevant data are kept to increase the performance for complex calculations. Though there is technically only one live cache per installation, the data is stored in three different ways depending on the application: as a number per time period (month, week, day) and key figure (time series), as an order with a category, date and exact time (hour: minute: second) and as a quantity with a category and a date in the ATP time series. We will refer to the according parts of the live cache as time series live cache, order live cache and ATP time series live cache. Demand planning uses much of the SAP BI™ functionality and relies on the info cubes as data interface to any other system – SAP ERP™, SAP SEM™ or flat file. Therefore the historical data is always persistent in an info cube. For processing the data is written into the time series live cache. SNP and PP/DS use mainly the order live cache, though SNP is able to access the time series live cache as well, since there are many structural similarities between DP and SNP. ATP at last relies only on the ATP time series live cache. This way of data storage implies a certain redundancy, because orders are stored both in the order live cache and in the ATP time series live cache. The data model is however quite different, and the redundant data storage enables better performance for the applications. TP/VS finally uses the order live cache to reference other orders. Figure 3.1 shows how the SAP APO™ modules use the live cache and the data integration for transactional data from SAP ERP™ to SAP APO™.

Suggested Citation

  • Jörg Thomas Dickersbach, 2009. "SAP APO Architecture," Springer Books, in: Supply Chain Management with SAP APO¿, chapter 3, pages 15-29, Springer.
    • Handle: RePEc:spr:sprchp:978-3-540-92942-0_3
    DOI: 10.1007/978-3-540-92942-0_3
    as

    Download full text from publisher

    To our knowledge, this item is not available for download. To find whether it is available, there are three options:
    1. Check below whether another version of this item is available online.
    2. Check on the provider's web page whether it is in fact available.
    3. Perform a search for a similarly titled item that would be available.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:sprchp:978-3-540-92942-0_3. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.