This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
SNP HorizonsSNP Prod Horizon – No planned orders createdSNP Stk Trans Horizon – No PurReq createdExtended SNP Prod Horizon – only manual planned orders in this horizon, must be in complement with SNP Prod Horizon, not standalone
SNP plans in buckets, not to individual orders by datesand times
Data can be stored in Order liveCache or Times SeriesBuckets can be defined as daily, weekly, or monthlyTime bucket profiles are used to define the buckets and planning horizonDifferent buckets can be used over the planning horizon
Example for a 12-month planning horizon:Week 1 to 4 – dailyWeek 5 to 30 – weeklyRest – monthly
Demand and supply is grouped together to one number per bucket
Same as Distribution Receipt (Planned), but as STO plant (receiving side)Distribution Receipt (TLB)
Same as Distribution Receipt (Planned), but as a stock transfer to the plant (receiving side)
Distribution Receipt (Confirmed)
Same as Distribution Receipt (Planned) for subcontracting materials (receiving side)
Distribution Receipt (Subcontracting)
Stock transfers that are generated during the SNP planning process, and updated in every planning phase. The distribution receipt shows the receiving location’s view of these stock transfers (the view from the supplying location is provided by the distribution demand). This will be created as above, but on receipts side.
Distribution Receipt (Planned)
Stock Transport Order (created during TLB run). Distribution Demand TLB will consume Distribution Demand Confirmed.
Distribution Demand (TLB)
Same as Distribution Demand (Planned), but as a stock transfer to the receiving plant. These are also called Deployment Requisitions. Distribution Demand Planned is populated by the deployment process based on inventory Available-to-Deploy (ATD). Distribution Demand Confirmed will consume the Distribution Demand Planned.
Distribution Demand (Confirmed)
Same as Distribution Demand (Planned) for subcontracting materialsDistribution Demand (Subcontracting)
Stock transfers that are generated during the SNP planning process and updated in every planning phase. The distribution demand shows the supplying location’s view of these stock transfers (the view from the receiving location is provided by the distribution receipts). This will be populated after Distributed Resource Planning (DRP) run for non-subcontracting materials.
Distribution Demand (Planned)
This will come from SAP ERP into SAP APO via CIF. Sales orders will consume the forecast.
Sales Order
This will come from Demand Planning after DP release to SNPForecast
Macros function similarly to formulas in spreadsheets, but are more advanced and provide greater flexibility
Macros are assigned to Planning Books and Data ViewsCan be executed automatically or on demand by the user
Can choose from SAP-provided standard macros or build custom macros in SAP APO
Unlike in DP, SNP has many standard macros provided by SAPStandard macros might be sufficient most of the time
Custom macros are like “user-defined” formulasProvide planners with the ability to model user-specific planning scenarios based on individual business tasksCan create context- and user-specific planning views
Can trigger alerts in the Alert Monitor or Data View to inform the planner of specific business situations
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
Core Interface (CIF) for Master Data Transfer (cont.)
Transfer of master dataSAP ERP is the execution system for master data, and it retains ownership of all master dataCIF always transfers SAP APO-relevant master data from SAP ERP to SAP APO
Core interface performs initial data transfer as well as subsequent data changesSubsequent data changes can be scheduled to run in real time or periodically
It is recommended to schedule master data change transfer periodically during off hours for performance and system integrity reasonsIt is possible to set the definitions of SAP APO-relevant master data in SAP ERP or via CIF user exits. New “SAP APO” fields often have to be set up in SAP ERP because they do not currently exist there.
Factory calendars in SAP APO are the same as in SAP ERPDefine workdays of a week and holidaysCan be synchronized with SAP ERP via Transfer Global Settings
Transfer Global Settings Global master data settings available for transfer from connected SAP ERP source system:
Units of currencyUnits of measureFiscal year variantsFactory calendars
Various available options for transfer: Update tablesRebuild tablesTcode: RSA1
Set of rules that defines the offset of the user’s local time from Coordinated Universal Time (UTC)
UTC replaces the term Greenwich Mean Time (GMT)
The local time of a particular location or user depends on theirposition on the globeThe offset of a location from UTC is influenced by:
Geography (position on the globe) Political factors (time zones are assigned for a country, region, or even a postal code) Daylight Saving Time (DST), if applicable
Time zones are important master data that help derive realistic lead times for procurement proposals during planning runsCan be set by the user in his or her user profile settings (txn. SU3)
The Transportation Lane defines:Which location is the source of a product to a target locationRelationship between two locationsThe transport lead time
Needs to be in sync with routes in SAP ERPThe means of transportation (truck, train, plane, etc.)The capacities of each means of transport in a lane, including:
VolumeWeight Number of pallets
Products that can be transported from the source to the target location (defined for each lane)
Product assignments can be maintained via Special Procurement Key in SAP ERP
Resources are created to represent the capacities and working times of production lines, equipment, and laborProduction resources can be transferred from SAP ERP to SAP APO
Production resources are typically CIF’d from SAP ERP to SAP APO
Capacity information is maintained in SAP APO, not in SAP ERP
Needed in SAP ERP and SAP APO for link between routing/recipe in SAP ERP and PPM/PDS in SAP APO
Handling, storage, and transportation resources are created and maintained in SAP APO onlyMixed resources can be used in both SNP and PP/DS, and are recommended to use as much as possible
Very difficult to change resource type later if PP/DS is used
Converting a PP/DS Product Process Model to an SNP Product Process Model
Production versions (including routing and BOM) are transferred as PP/DS PPM from SAP ERP to SAP APO
SAP APO allows you to generate SNP Production Process Models (PPMs) based on existing PP/DS PPMs
Conversion options for generation of SNP PPMs are:SNP PPM generation with lot size margin SNP PPM generation without lot size margin
Conversion process needs to be repeated for subsequent changes that were made to routings/BOMs and/or PP/DS PPM SNP PPM can be created directly in SAP APO without reference to a PP/DS PPM
Transaction to maintain PPMsUser exit to create PPMs programmatically (BEST option)
A structure generated in SAP APO from a production version or Bill of Material in SAP ERP … similar to the PPMContains information about the production resource and the component assignment for the production of a productYou can use PDS as a source of supply for in-house production in PP/DS, SNP, Capable-to-Match (CTM), and Demand Planning (DP) areasSNP PDS can be transferred separate from PP/DS PDSCannot be maintained in SAP APOCan select to use on the Product Master – PP/DS TabAlternate object to PPM going forward (SAP SCM 4.1 and above)
Restrictions exist which might require use of PPMsSee also SAP Notes 705018, 709884, and 744445
Engineering Change Management (ECM) for PP/DSSubcontracting in SNP is fully integrated with SAP ERPDirect transfer of SNP-PDS from SAP ERP (no conversion step)Use of object dependenciesin SAP APOOrder-BOM and WBS-BOMRapid planning matrix
Functionalities supported byPPM, but not by PDS:
Maintenance in SAP APOPush-productionContainer resourcesNet flag for component scrapStep function for the standard value of the durationOverrule the synchronization setting of the resource onactivity levelRestriction of the validity requirements of an order onactivity level
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
SNP HeuristicHeuristics run creates an Infinite Supply PlanSourcing can be done via quota arrangementsCapacity leveling as second step for finite plan
Capable-to-Match (CTM) profile and rules-drivenSourcing based on priorities or quota arrangementsFinite capacity planning possibleSNP and PP/DS modes possible
SNP OptimizerCost/penalty-drivenFinite capacity planning possibleFull constraint-based planning possible
Plans/creates infinite supply plan to satisfy demand requirements in the supply chain networkCapable of handling quota arrangement functionality for source determinationExplodes the BOM and generates supplies in the network
Capacity leveling is done in a separate step Address capacity over and under loadCan be executed interactively or in background jobAlternative Resource option as of SAP APO 5.0
Heuristics can be run either interactively or in the background.The following three options are available interactively through the planning book:1) Location Heuristics – Plans only selected location product2) Network Heuristics – Plans the selected product for all
locations3) Multi-level Heuristics – Plans the selected product with all
components at all locationsNote: Multi-level Heuristics is not available to run in the background, but there is an option to take components into account in the planning run
Backward and Forward leveling is supportedBackward: Looks in the past for available capacityForward: Looks in the future for available capacityBackward/Forward: Looks for capacity in both directions
Alternative resource option in SAP APO 5.0Check box to activate the optionProcurement Priority on the PPM/PDS is used to determine the order in which the alternates are selectedAll Relevant Resources = Select ALL existing resources in SAP APOResource = Specific resource(s) as defined by userSelection Profile = Resources as defined in the profileSource Determination Level: Use only if Resource Hierarchy exists (AGG)
Only Header Level: All subresources are replaced by header resourcesOnly Sublevel: All header resources replaced by subresourcesAll Levels: Resource set remains unchanged
Supply Distribution after or before a CTM planning run transferssurplus receipts and stocks available to other location in the supply chain model To ensure a feasible transfer, lot sizes as well as transportation and handling resources are now considered during the supply distribution
New supply distribution is incorporated into CTM planning runOne level push of surplus supply happens according to the outbound quota
Just like Heuristics, Optimizer is a quantity-based, cross-location planning engineUnlike Heuristics, the Optimizer takes cost-based constraints to arrive to a most feasible and cost-effective solutionOptimization is based on linear and mixed integer linear programmingThe Optimizer does not use quotas, but can create them
Note: As of SAP APO 5.1 – inbound quotas are supported
The Optimizer uses linear programming methods for planning, such that it simultaneously considers all relevant factors, making the entire chain as a single problemThe objective of the Optimizer is to find the optimal solution to an equation (target function) in which all the cost and penalty factors are considered simultaneouslySince the Optimizer assesses alternatives this way, it can determine the best feasible plan on the lowest cost SNP Optimizer run modes:
Running the Optimizer from the Interactive Planning Desktop Running the Optimizer in the background– Likely way to run it in a live environment
The use of fixed and minimum lot sizes and time-dependent costs (cost functions) will require a discrete runDiscrete runs have the potential to significantly increase the run time to arrive at an optimal solution
Costs are generated based on determined business goalsCosts used during generation will override maintained costsNot all costs are generatedGeared towards less complex modelsSNP Cost Profile not taken into consideration
SNP Optimization respects time-dependent inbound quota arrangements on procurements from source locations, external suppliers, and in-house productionDeviation from quotas are penalized and visualized with the Objective functionIt is possible to define inbound quotas for products or product groups
Product Group Time-dependencyPenalty for deviation below target quantityPenalty for deviation above target quantity
Profit Driven Supply Network Optimization — Penalty Groups
Consider penalty groups to prioritize customers or customer segments within SNP optimizationUse the grouping as input for layered SNP Optimization to sequentially plan customer segments according to their importance
Safety Stock Yes Yes Yes Min/Max lot-size Yes Yes Yes1 Rounding value Yes Yes Yes1, 7 Transportation Duration Yes Yes Yes Selection of Means of Transport (Dates vs. Costs)
Yes Yes Yes
Stock Transfer Horizon Yes Yes3 Yes2 Production Duration Yes Yes Yes Production Resource No4 Yes Yes Transport Resource No5 No5 Yes Handling Resource No5 No5 Yes Storage Resource No5 No5 Yes Quota Arrangements Yes Yes No6 Procurement Priority of Transportation Lane
Yes Yes No8
1 With discrete optimization only but not with linear2 Setting in Optimizer profile3 Setting in control setting 4 Not in SNP Heuristic, but can be done with
capacity leveling step
5 Capacity loads are calculated but no finite planning6 SNP Optimizer can be used to create quota
arrangements – YES in SAP SCM 5.17 Either from product master or transportation lane8 Transportation cost is used to select means of transport
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
Deployment determines which distribution center and VMI customers’ demand can be covered by current receiptsIf quantities are not sufficient, or if they exceed the demand, deployment can make adjustments to the stock transfers made by the SNP runOrders created by this tool are called Deployment Stock Transfers
Deployment is only used to confirm stock transfers (actual routeplanning, transport service selection, and delivery generation are handled by TP/VS)
Available-to-Deploy (ATD) quantity defines the quantity that is available in the delivering plant for distributionDefined by ATR (receipt) and ATI (issue) category groups in customizing, and assigned to Location master or Product master at the location level (SAP SCM 5.0) Receipts (Available-to-Receipts) can be stock on-hand, production orders, purchase orders, etc.Issues (Available-to-Issues) can be STOs, sales orders, deployment orders, etc.
Date: ATD Quantity: Requirements:
Detailed requirements per DC:
Today
Supp
ly
Dem
and05.01.2007
06.01.200707.01.2007
1000900400
100 (DC1)500 (DC2)800 (DC1+2)
DC1DC2
200600
Deployment ResultsPlant to DC1Plant to DC2Plant to DC1Plant to DC2
Prioritization of deployment stock transfers: IntroductionDeployment priority further optimizes the deployment processDeployment prioritization considers deployment orders from Deployment Heuristic or Optimizer as inputPrioritization sets a priority number for all deployment stock transfersPrioritize can be displayed during Truck Load Building (TLB)
Prioritization function groups the deployment stock transfers into three categories:
Cat. 1 – stock transfers for fulfilling shortagesCat. 2 – stock transfers for fulfilling safety stock levelCat. 3 – stock transfers for fulfilling planned replenishments above safety stock levels
Deployment prioritization assigns a priority number to all deployment stock transfers by categoryThe assigned shipment priority number indicates the relative urgency of the deployment stock transfer
Factor above safety stock after deployment stock transfer receivedi.e., 14 = 1.4 X of safety stock
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
TLB changes the stock transfer orders (confirmed) from the deployment run into TLB ordersStock transfer orders are grouped together until maximum capacity is achievedIf minimum capacity is not achieved, it has to be processed manually There is no tracking of resource usage, product-specific constraints, or special transport requirements
Some basic modeling of constraints is possible by means of transport
If the planned transport orders do not meet the minimum or maximum requirements, an alert is generatedOnly for stock transfer and does not include deliveries for sales orders
The TLB Profile minimum and maximum values are definedTLB uses lot size profile when building loadsLoad Method: Options on how to load the means of transport (Product by Product, Equal Loading)Pull-in Horizon: Number of days from today’s date during which the TLB can take into account existing deployment stock transfers to create TLB shipments
Transport loads generated by the tool can be seen in the Interactive Planning tool by dayIf minimum capacity was not met within the pull-in horizon, TLB stock transfers for later deliveries can be moved manuallyDrag and Drop functionality for unconverted deployment stock transfers is available
Stock Transfer Requisition After SNP Planning RunWhen a Stock Transfer Requisition is created at the receiving location, it creates a distribution demand at the sending location
Distribution Demand (Planned) after SNP Heuristic, CTM, or SNP Optimizer run
The Deployment Order Confirmed is displayed as Distribution Demand (Confirmed). Note that the Stock Transfer Requisitions disappear from Distribution Demand (Planned) line.
The TLB Order/STO is displayed as Distribution Demand (TLB-Confirmed). Note that the Stock Transfer Requisitions disappear from Distribution Demand (Confirmed) line.
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
Alert Monitor provides users with visibility of exception cases in the Supply Network Plan
You can define, by user: Which type of alerts to show and their thresholds using Overall ProfilesWhat data is displayed in Alert Monitor using Display Hierarchies
Exceptions are calculated using macrosSAP provides standard macros and the ability to build your own macros to create customized alerts
Alerts are generated for user-defined planning situations involving Location products and ResourcesThe Alert Monitor is organized by profiles per application area:
SDP alert profile – monitoring DP and SNP alertsTLB alert profile – monitoring TLB and Deployment alertsVMI alert profile – monitoring VMI alerts
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
Business goal: To ensure (high) service level of product at the lowest cost despite fluctuations in the various levels of the supply chain
Problem:At which locations within the supply chain do you want to have safety stock?How much safety stock do you want to hold at a particular location?
Interpretation of service levelAlpha (shortfall event-oriented)
Expected number of periods with complete delivery fulfillment/total number of periodsPercentage of how often product is delivered on time
Beta (shortfall quantity-oriented)Expected quantity delivered in time/expected total demand Percentage of how much of ordered quantity is delivered
Choosing a service level depends on:Customer satisfaction
Alpha – complete delivery necessaryBeta – partial delivery possible
Costs for late deliveriesAlpha – backlog-independent (fix) costs of late delivery are significant Beta – backlog-dependent (variable) costs of late delivery are significant
Business goal: To include key customers in Supply Chain Planning
Benefits overview:Capability for the manufacturer to perform the replenishment planning tasks for their business partnersEnable better decision support for vendors, along with more knowledge and control over the logistical processIncrease visibility to actual customer demand as well as customer inventory levelsAllow manufacturers to make better decisions on how to deploy goods across various customers, which leads to:
Min/max replenishment The inventory is maintained within a fixed bandNew sales order is generated as soon as the inventory reaches the lowest level of the bandSales order quantity will replenish the inventory to the maximum of the band
Forecast-based replenishmentThe inventory is calculated to maintain forecast coverage for the specified number of daysSales order is generated as soon as the inventory drops below the calculated amountSales order quantity will replenish inventory back to the amount that covers forecasts for a specified number of daysThe strategy has the benefit of being able to account for seasonal spikes in the demand
Lets companies create a feasible procurement plan for subcontract manufacturers, taking into account all materials and capacity constraints
Planning of subcontractor production linesPlanning which bill of material will be used for each subcontract build
Lets companies consider preferred subcontractor production lines by priority or cost Lets planners perform manual adjustments and create subcontract purchase requisitions manually to incorporate any new information into the planning resultsFeatures seamless integration with SAP ERP 6.0 as of Enhancement Package 3
Business scenarioYour company provides components to the supplierSupplier assembles the components and returns the finished product
SAP solution with SNPSupplier is set up as a location in SAP APOIn-house planned order is created at the supplier location to plan assembly of the componentsSubcontracting order is created for the stock transfer from:
Your plant to supplier for componentsSupplier to your plant for assembled end product
Key considerations:Functionality addressed by SNP Heuristics and Optimizer
Followed by manual changes in Interactive PlanningSeparate Planning Book/Data View for subcontracting in Interactive Planning SNP PPM or PDS is needed for relationship of components to the end product
Can be CIF’d from SAP ERPTransportation lanes needed between supplier location and your plant location
Lanes are created via CIFSpecial subcontracting indicator
Relationship is maintained automatically between:Planned order at supplier location and stock transfer requisitions to/from supplier location in SAP APO, andPurchase requisition (subcontracting order) in SAP ERP
In a subcontracting scenario, the plant provides the subcontracting components to the supplier. The supplier assembles the components and returns the finished product.To support this process in SAP APO, in-house-production orders for the source location (supplier’s site) and related subcontracting orders for the stock transfer from supplier to plant, are being created.
Subcontract information record allows several production versions to be defined per subcontract vendor/material relationship, ensuring efficient utilization of existing capacities.
1. The SNP run (Heuristic, Capable-to-Match, or Optimization) determines the subcontractor as the source of supply and generates a subcontracting purchase requisition to transfer the finished product from the source location (subcontractor) to the destination location (plant)
2. The SNP run determines the source(s) of supply (PDS/PPMs) at thesubcontractor and creates the subcontracting in-house-production order(s) in the source location (subcontractor).
The subcontracting purchase requisition can also be created manually in SNP with the ability to assign/change the subcontractor and the source of supply
3. A purchase requisition, which takes the subcontracting components (materials provided to the subcontractor) from subcontracting in-house-production order(s), is generated in the SAP ERP system
Prerequisite to consider multiple production versions in an SNP Subcontracting Process:
Business scenarioConsider full interchangeability and discontinuation of product in the supply chainConsider constraint of limited validity and availability of materials and components in the supply chain
SAP solution with SNPEnables full interchangeability and discontinuation at any productlocation level
Transfer demands for a product that is to be discontinued onto a successor productUse existing stock of a current product to fulfill demand for the successor product
Can be done at any product levelEnd product or components of BOM
Works with SNP Heuristics and the SNP OptimizerIntegrated with DP
Creation of like or phase-in/-out profilesProduct split and realignment
Benefits:Systematic and automated changeover from one product to another
Optimizing product availabilityMinimizing material stocks and scrapSecuring consistent data modelsEnabling continuous process flows
Types of product interchangeability:Discontinuation
A product is replaced by another one Supersession
A chain of products that can replace each otherForm Fit Function (FFF)
Grouping of interchangeable parts, which are identical in respect toall of their technically-relevant propertiesRelated to manufacturer part number functionality
Process steps for standard scenario (product location)1. Aggregated Safety Stock Planning (optional step)
Standard and extended safety stock methods are availableSee also SAP Note 858794
2. Single-Level Supply and Demand Mapping (optional step)Prevents the system from assigning receipts to the wrong demandsduring aggregated planning, due to detailed information no longer being available at aggregated level
3. Aggregate demand, receipts, and stock to product group level (automatically)
Delete all planned replenishment elements on detailed item levelthat are part of the aggregate before performing an aggregated planning run – Optional but recommended way for live environment– Defined in configuration (Basic Settings Maintain Global
Process steps for standard scenario (product location) (cont.)6. Check and adjust plan at product group level or detailed
levelExample – execute capacity leveling at product group level and not item levelAggregate and disaggregate data interactively before and after changes were madeCan be used for Aggregation only without disaggregation
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
Demand Plan is transferred as Planned Independent Requirements (PIRs) to SNP
Demand plan/forecast is stored in buckets/times series data in DPPIRs are stored as orders in SNPFlexibility to have different/many PIRs per location product
Order category FA or FC
Demand Plan is released to a product locationAbility to break up forecast during release via:
Location splits Product splits
Ensure product location master data exits in SNP for all Characteristics Value Combinations (CVCs) in DP
DP has CVCs for product and location independent of SNPSNP needs to have corresponding product master maintained
PP/DS is a detailed planning and scheduling tool ideal for short-term planning
Detailed planning of manufacturing stepsScheduling/sequencing of individual orders
SNP is a bucketed planning tool ideal for mid- to long-term planning
Supply planning across the network to:Determine best sourcing optionCreate a constraint-based production plan in buckets
SAP offers seamless integration for converting orders from SNP to PP/DS through:
SNP production horizon and PP/DS horizonSNP production horizon separates PP/DS planning period from SNP planning period, or they could overlap
Conversion of SNP planned orders to PP/DS planned ordersSAP standard Heuristics are available to convert SNP orders to PP/DS orders inside the SNP horizon
SNP Production Horizon starts after the PP/DS horizon SNP and PP/DS planning areas are unique, SNP orders for all products can be converted to PP/DS orders SNP is used for mid- to long-term planning while PP/DS is used for short-term planning
SNP Production Horizon starts within the PP/DS horizon SNP and PP/DS planning areas overlap, seamless integration of SNP planning into PP/DS planning Useful when SNP has control over certain products and their critical components
Core Interface (CIF) to Integrate SAP ERP and SAP APO
The Core Interface (CIF) is responsible for data exchange between SAP APO and SAP ERPThe CIF is a real-time interface that can link an SAP APO system with multiple SAP ERP systemsThe CIF can perform initial transfer as well as subsequent data changes The CIF can transfer both master data (1 way) and transaction data (both ways)
Customizing in SNP for Transfer of Data to SAP ERP
The above transaction indicates various options available for transfer of data from SNP to SAP ERP (tcode /SAPAPO/SDP110)Periodic transfer is preferred when large volumes of orders are generated, typically after a planning or TLB run
But might be driven by process needs, too (user to review ordersbefore sending to SAP ERP, especially for TLB orders)
Options available for transfer of SNP orders
Options for transferring orders generated from deployment process
Options for transferring orders generated from the
SCM Queue Manager is a tool provided in SAP APO to monitor and resolve queues in the core interface between SAP APO and SAP ERPProvides access to the application log for detailed error analysisTransaction /n/SAPAPO/cq in SAP APO
Application LogIndicates data held up due to an error
Queues by order types that are held up in the interface
SAP-provided transaction to compare and reconcile transaction data between SAP APO and SAP ERPAbility to select specific transaction data for selection of products and locationsAbility to execute in real time or in the backgroundCan be accessed in SAP APO using tcode /n/SAPAPO/ccr
Overview of SNP and how it fits in SAP SCMMaster data in SNPPlanning with SNPDeployment with SNPTruck loading with SNPPlanning by exception with the Alert MonitorSpecial planning topics in SNPIntegration of SNP with DP, PP/DS, and SAP ERPWrap-up
Presentations“Production Master Data Overview and Strategy by BSG Manufacturing Industries,” SAP AGDr. Dirk Meier-Barthold, “Supply Chain Safety Stock Planning,” SAP AGGunter Fertig, “Multi-Level Supply and Demand Matching (CTM),” SAP AGSAPPHIRE 2006 Supplier Collaboration with SAP SNC by BearingPointCTM Workshop 11/2007 – Balaji Rao Gaddam
On your conference CD:73 additional slides discussing key implementation considerations and challenges Supply Chain Engineer (SCE) PrimerHow to Configure Capacity Variants/Intervals in SNPSolution Brief of the SNP Extended Horizon CapabilityDetails on Calendar use in SNP and PP/DSList of Parameter IDs (PIDs) to use in APO for more efficient system performanceCopy of SCM Maintenance Jobs to Schedule and ExecuteHelp on Notes Management
SNP is a mid- to long-term planning tool and is used to create feasible supply plans (Rough Cut Planning)Know your business requirements and why you’re implementing SAP APO SNP to:
Select the most appropriate planning methods and special planning featuresRealize the kind of benefits desired at the beginning of the project
SNP has 3 planning solvers to select from depending on the business requirements:
Heuristics/Capacity Leveling – 2 stepsCapable to Match (CTM) finite planOptimizer
The SNP Optimizer and CTM in SAP APO 5.0 now have an explanation tool that lets the user see planning messages to better explain planning situations
This was not available previously Tightly integrate the Business into the project by:
Having business users as full-time team members on the projectEducating the business community about SAP APO SNP functionality and new processes throughout all project phases, not just at the end right before go-live
Don’t underestimate the effort required to set up and monitor the CIF for interfacing SAP APO with SAP ERP
There will be ABAP development for the CIF user exits
Master data objects are very important to executing a good plan in SNP. Most master data is transferred via CIF from SAP ERP.
Mixed resources can be used in SNP and PP/DSNew production planning object, SNP PDS, can be transferred directly from SAP ERP to SAP APO without a separate program
Copyright 2007-2008 SAP AGAll rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
Wellesley Information Services, 990 Washington Street, Suite 308, Dedham, MA 02026