SCM360 Capacity Planning

              SCM360

Release 640   04/06/2006  

0

nSystem R/3, Enterprise - SAP APO 3.1

n2003/Q3

n50063191

0.2

nSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

nMicrosoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

nIBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

nOracle is a registered trademark of Oracle Corporation.

nUNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

nCitrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

nHTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

nJava is a registered trademark of Sun Microsystems, Inc.

nJavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

nMaxDB is a trademark of MySQL AB, Sweden. 

nSAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

nThese materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

1

1.2

nWhen you plan with both Supply Network Planning (SNP) and Production Planning and Detailed Scheduling (PP/DS), the production horizon is used to separate the responsibilities for these two planning functions (modules):

Supply Network Planning is used for medium to long-term planning across the entire supply chain (particularly if there are several plants and distribution centers). Requirements are therefore aggregated for a determined bucket (for example, a day). In this case it is irrelevant whether a requirement lies in an early or late shift, in this case, the requirements are merely planned roughly - when exactly the breaks take place is not considered. As well as a temporal aggregated, you can also execute in SNP (if desired) a spatial aggregated planning: You can define your own 'bucket resources' to use in SNP, which then represent, for example, the available capacity of an entire hall. Because you create your own PPMs for SNP (that can usually be copied from the PP/DS PPMs), you can describe the production on these bucket resources. Order sequences are not involved in the temporal area of SNP planning.

PP/DS is used for short-term planning, in which orders have to be dispatched precisely to the second and order sequences must be considered (sequencing, sequence optimization).

nAs soon as a requirement falls within the production horizon, it is no longer planned by the SNP planning run, but instead by the production planning run in PP/DS. However, orders can be created or changed manually in Production Planning and Detailed Scheduling across the entire time axis, independently of the production horizon. In automatic planning/production planning run, orders are only created within the production horizon. In Supply Network Planning, however, orders cannot be created or changed within the production horizon.

1.3

nIn this example, demand management is to take place in the R/3. The result of this planning, the planned independent requirements, are transferred to production planning in APO via an integration model. Planning in APO results in planned orders being created that are then transferred to the R/3 as the execution system.

nDemand management in the R/3 can take place manually, it can be based on a forecast, or resort to the functions of Sales and Operations Planning (SOP). Planned independent requirements are created as a result and then transferred to APO. Planned independent requirements are also to be included in the integration model.

nThe planned independent requirements are the starting point for production planning in APO. Existing warehouse stocks should also flow into the planning.

nThe result of production planning is planned orders in APO that are to be transferred to the R/3 for information. In the next step, APO will trigger the conversion into manufacturing orders (production and process orders) and transfer them to the R/3 for execution.

nTo ensure that the materials are not unnecessarily re-planned in R/3, they should be marked with an MRP type to exclude them from requirements planning. When a BOM explosion is required in R/3, use MRP type X0.

1.4

nThe selection of transaction data transferred to APO is determined in an integration model that you define in the R/3. All transaction data is displayed in APO on orders that vary according to the ATP categories.

nThe initial transfer of transaction data takes place first via the APO Core Interface. As a rule, the change transfer between R/3 and APO automatically connects itself for transaction data objects that are part of an active integration model. New transaction data or changes to the existing transaction data are automatically transferred (for transaction data of the APO component SNP, you can control in Customizing whether a real-time or a periodic retransfer is to be executed).

nThe APO transaction data objects are not identical to those of the R/3. All R/3 transaction data is transferred to APO as orders.

nPlanned independent requirements can usually only be transferred from R/3 to APO. The retransfer of planned independent requirements, that you need if you only execute demand planning in APO, must be triggered from APO demand planning by a separate transaction.

nFor planned orders and purchase requisitions, you can control in APO (PP/DS Customizing) that they are only transferred from APO to R/3 if the conversion indicator is set.

1.5

nSimultaneous material and capacity planning: You can define resources in the resource master as 'finite' resources (planning-critical resources). Activities of orders are created on these resources if there is sufficient capacity available for the order quantity on the relevant date. If capacity is not available, the system searches for a date on which the order activity can be dispatched taking the capacity situation into consideration.

nPrecise time planning: Dependent requirements and orders are created with time specifications.

nPlanning of alternative resources: If there is insufficient capacity at a resource, the activity can be rescheduled on alternative resources (maintain in the PPM).

nMachine commitment optimization: Orders may have been created in the planning over time, with order sequences that are not optimal. You can therefore change the sequence and resource assignment of existing orders using the optimization run.

1.6
Exercise Data

Explanation of the symbols in the exercises and solutions

Data in the exercises for SAP R/3

Data in the exercises for SAP APO