SAP APO详解编程语言

APO概念

SAP (APO)是mySAP SCM 解决方法中的非常重要的计划类组件。

APO是advanced planner and optimizer(高级计划优化器)的缩写。

它是SAP产品中最大的组件之一。 APO是整套的用于提高供应链，供应预测，计划，优化的整体知识的供应链计划应用。

SAP APO包括了八个等级，分别是

network design（网络设计）,

supply network planning（供应网络计划）,

demand planning（需求计划）,

production planning and detailed scheduling（生产计划和详细调度）,

transportation planning （运输计划）and vehicle scheduling（运输调度）,

global availability and supply chain collaboration（全球可用性和供应链协作）。

SAP APO系统包含的主要的模块有：

　　Supply Chain Cockpit 供应链主控室

　　Demand Planning 需求计划

　　Supply Network Planning 供应链网络计划

　　Global ATP(Available To Promise) 全局ATP

　　Transport Planning/ Vehicle Scheduling 运输计划/运输工具调度

　　Service Parts Planning 服务部件计划

　　Production Plan/ Detailed Scheduling(PP/DS) 生产计划/ 详细调度

SAP APO其实不是一个单独可以运行的程序，它实际是需要ERP系统的后台支持，比方说在SAP R/3中执行。SAP R/3 通过可以实时支持主数据(master data)和交易数据(transaction data) 的APO Core Interface中心接口和APO系统进行通信。

这种基于SAP R/3 后台的和APO的实时通信，以及所有和生产，销售，供应的数据都可以不经过任何批处理直接快捷的从一个系统传递到另外一个系统。

APO应该是R/3里面的计划的高级形态，一般来说，APO和R/3(或是ECC）都是独立的系统，系统之间通过CIF通信，APO的大部分基本数据都由CIF传过来的，而且是单向的，以保证数据的一致性。在APO里，以R/3(或ECC）传过来的数据基础之上，又会增加许多APO独有的参数，以支持在APO里面的高级的计划功能。所有的计划出来的结果，又会实时地传回到R/3(ECC)里面。既APO仅仅是一个功能详细强大的计划工具，计划的结果还是要在R/3(ECC)里面处理。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

As it relates to Master Data there will potentially be three types of master data:

. Master data for supply planning in SNP or PP/DS such as BOMs, routing, material masters and resources necessary for creating supply plans. This data is transferred to SAP SCM by the CIF interface.

. BW master data: required data related to characteristics such as sold-to party, sales organization, divisions and so on, for example texts, attributes and hierarchies. This data is extracted by programs in BW and appears in tables within the BW system in SAP SCM.

. Demand Planning master data: Master data specifically for Demand Planning, called characteristic value combinations. This data is created in SAP SCM Demand Planning and stored in the Planning Object Structure.

There are four different types of movement data:
• OLTP orders: current planning data from your ECC system such as sales orders, stock, production/purchase orders. This data uses the CIF interface to populate SAP SCM.

• BW: historical aggregated transactional data on sales orders,
production/purchasing orders for forecasting or analysis. This data is
extracted by programs in BW and appears in InfoCubes within the BW
system in SAP SCM.

• SCM orders: planning results from SNP, PP/DS, DEPL and TP/VS. This data can be transferred to the performing OLTP systems by the CIF interface.

• SCM time series: planning results from SAP SCM Demand Planning.
These are saved in liveCache planning areas and can be released to SAP
SCM or OLTP systems as planned independent requirements. Orders and time series can also be periodically stored in InfoCubes in SAP SCM.