Summary
This note provides information about release restrictions for SCM 5.0.
SCM, release restrictions
When SCM 5.0 was released, restrictions still applied to the productive use of certain functions (SAP wishes to inform customers of these restrictions here).
-----------------------------------------------------------------------
THIS NOTE HAS BEEN REPLACED BY THE IMPLEMENTATION RECOMMENDATIONS GIVEN FOR SCM 5.0. PLEASE CHECK NOTE: 1413544
-----------------------------------------------------------------------
IS-MP-PP
No release
Order Combination for Mill Products
The functionality of order combination of mill products is not released in general. However after consultation with SAP Mill Solution Management and depending on the scenario it can be used.
( Changed at 15.11.2005 )
Release with restrictions
Collection of release information and restriction notes for Service Parts Execution
Below you can find a list of notes that describe the relevant restrictions for Service Parts Execution: 821101 - Service Parts Management: Prerequisites 860427 - SPM: Prerequisites and restrictions (only internal) 859252 - Implementation guide for supplier cross-docking General restrictions: 852235 - Release Limitations for mySAP ERP 2005 852008- Release Restrictions for SAP NetWeaver 2004s 838402 -Non-Unicode installations: drawbacks and shortcomings
( Changed at 08.12.2005 )
Release with restrictions
Interchangeability: General Restrictions
Interchangeability cannot be used in conjunction with configurable products (neither CBF nor CDP). Parallel discontinuation in which several products are discontinued dependent on another is not supported. Only 1:1 relations/substitutions are supported. Complex product interchangeability of the form 1:M (where 1 product can be substituted by several other products), N:1 or N:M is not supported. In the master data maintenance (ta incmd/ui) you have the possibility to maintain succeeding and preceding quantity factors for an interchangeability group. All applications in SCM 5.0 do not support this functionality. The use of assemblies in interchangeability groups is not supported. Interchangeability cannot be used together with aggregated planning in SNP: the SNP disaggregation only works for SNP planned production orders and purchase requisitions. Substitution orders are not disaggregated.
( Changed at 03.04.2009 )
Release with restrictions
BAPI for ATP: not for Third party processing
Since SCM 4.1 a BAPI for ATP is available. The main restriction of the new BAPI is the lack of of user interaction (dialogue) and the fact that no third party processing scenarios are supported by this new BAPI.
( Changed at 08.11.2005 )
Continuous input /output only for output products
In the chemical industry for example, process orders running for several weeks at a time are constantly producing finished goods. Up to SCM 4.0, an availability check only takes into account output after the end date of the process order. Therefore an availability check will underestimate the availability by a large proprotion and will not give any usable results. Since SCM 4.1, it is possible to split the output quantity for the finished good proportionally over the process order duration. The limitation is that, this functionality is only possible for the output products of an process order and not for the input products.
( Changed at 08.11.2005 )
Backorder Processing - Stock Transport Requisitions
Stock Transport Requisitions (STR) are supported in BOP with ERP 2005. Because STRs do not support the new logic for requested date / time and quantity and do also not support product substitution and subitems, this can also be not supported during Backorder Processing / Reassignment of Order Confirmation. Product substitution for Stock Transfer Orders (STO) will only be supported for ERP 2005, location substitution is not supported.
( Changed at 08.11.2005 )
ATP Substitution Preselection
Only "rules immediately" is possible (set automatically); Suppression of subitems in RBA-STR usually not possible.
( Changed at 08.11.2005 )
Third Party Order Processing (TPOP)
TPOP is only possible in SPM system landscape (CRM system). Also regard the general SPM limitations. Consolidation is not possible with TPOP. Functionality is deactivated because of CRM limitations. If used SD-CO is not possible. Consolidation is not possible with TPOP redirection generally.
( Changed at 08.11.2005 )
Order Due Lists (ODL) inbound
An ODL can be filled only with following document type items: - sales order - delivery (not accepted by ODL of type "obtain confirmation"; only accepted if the delivery is a stock transfer delivery or it's pre-decessor is a CRM sales order) - stock transport order - stock transport requisition
( Changed at 05.04.2007 )
ATP category change
Using category profiles is possible only with activities "Changes of Stock Data" and "Change of Purchase Order Document" (to be checked)
( Changed at 08.11.2005 )
Back Order Processing (BOP) does not support deliveries
BOP Filters apply for BOP and Order Due Lists. However, deliveries are not supported in BOP filters, only in Order Due Lists.
( Changed at 08.11.2005 )
Reassignement of Order Confirmations (ROC) - indicator value
During confirmation of a high priority order on cost of lower priority order SCM returns a special result indicator value. This value can be evaluated by the order management system and used for blocking the high priority order until the subsequent de-confirmation of lower priority items is successfully finished. The evaluation of ROC result indicator is not supported by ERP (R/3).
( Changed at 08.11.2005 )
Reassignement of Order Confirmations (ROC) - de-confirmation of deliveries
De-confirmation is possible for deliveries only if delivery is a stock transfer delivery or it's pre-decessor is a CRM sales order - Successors of ERP Sales orders are not supported
( Changed at 08.11.2005 )
Rounding to packspecs with global ATP is not possible with R/3
Rounding to packspecs with global ATP is not possible with R/3, but only with CRM 5.0.
( Changed at 08.11.2005 )
Rounding with gATP is not possible for Kit-components and MLATP-components
Rounding with global ATP is not possible for Kit-components and MLATP-components
( Changed at 08.11.2005 )
Rounding with gATP is not possible for Product Allocation and Forecast Check
Rounding with global ATP is not possible for Product allocation check and Forecast-check
( Changed at 08.11.2005 )
Rounding to sales units with gATP is only possible for STOs in ERP 2005 in DEIG scenario
Rounding to sales units with global ATP is only possible for Stock Transfer orders (STOs) in ERP 2005 in DEIG scenario
( Changed at 08.11.2005 )
Parameter dependent safety stock check with G-ATP is not possible for R/3
Parameter dependent safety stock check with global ATP is not possible for R/3. Result neutral check not supported.
( Changed at 08.11.2005 )
Event-driven quantity assignment (EDQA) triggered by quantity release in a sales order
EDQA can be triggered only when confirmed quantity of a location product is reduced in a sales order. EDQA can for example not be triggered when the quantity is released just by shifting the material availability date of confirmation
( Changed at 08.11.2005 )
Event-driven quantity assignment (EDQA) with Rules-Bases ATP Check (RBA)
Items that shall obtain confirmation may have used RBA. During EDQA a substituting location product can replace the location product of such an item. In multilevel RBA scenarios like "kit in kit" this substitution is possible on upper component level.
( Changed at 08.11.2005 )
Sourcing: KITs and One-To-Many processes within G-ATP are not possible when checking from R/3
KITs and One-To-Many processes within global ATP are not possible when checking from R/3, but with CRM 5.0.
( Changed at 08.11.2005 )
Order Due Lists (ODL) monitor
Back Order Processing (BOP) cannot be started from ODL monitor of type "Lose Confirmation".
( Changed at 08.11.2005 )
Safety Stock
Result neutral check and enhanced confirmation logic not supported.
( Changed at 08.11.2005 )
Rules based ATP
Combination of restricted number of entities/substitutions cannot be combined with overdelivery tolerances.
( Changed at 08.11.2005 )
Multi item single delivery location
This development will not be able to run an optimization process in such a complexity as requested in above Development request. Valid are only locations from the predetermined location list in which all products are defined, it is not sufficient that a substitution material is valid. Only Main Requirements are allowed for this functionality(HPOS) In Rules based check there will be following limitations: - No PPM#s - No location activity possible - Location list will be substituted by location from initial list - No validity handling possible - No characteristic substitution - No alternative Locations - No exclusions - No Location-Product Lists - No TPOP / ROC - No Production - Only rules immediately is possible (will be set automatic if a location list evolved) - No manual overrides possible - Not with classic interchangebility - Not with different units of messure - No other Kardinality than 1:1 - No 1:N substitution - In connection with 'ATP Substitution Preselection' 'Single location predetermination' will win - No consolidation
( Changed at 08.11.2005 )
Correction Report for Delivery and Sales Order Requirements
The Correction Report for Delivery and Sales Order Requirements (/SAPAPO/SDRQCR21) is only integrated to ERP as an order entry system. CRM is not supported.
( Changed at 08.11.2005 )
Delivery Group Correlation
Delivery Group Correlation in unchecked deliveries does not support correlation profiles. It is a simple time correlation on the last date.
( Changed at 08.11.2005 )
Propagation in multi-level scenarios (Part I: BOMLVL)
BOM-explosion after the Product Availability Check for KIT or MATP is not supported.
( Changed at 08.11.2005 )
Propagation in multi-level scenarios (Part II: RBA triggered STRs)
RBA with location determinations triggering the creation of a STR should not be mixed with standard location determination within one rule.
( Changed at 08.11.2005 )
Route determination for unchecked deliveries
Scheduling in unchecked deliveries does not have context information for route determination.
( Changed at 08.11.2005 )
Sourcing: nested multi-level scenarios
A component of a One-to-many substitution or a kit must not be a One-to-Many replacement or a kit itself. The same is true for substitutions of the component.
( Changed at 08.11.2005 )
Backorder processing
A KIT component must not be touched in an interactiv backorder resolution process (BOPI), since there is no quantity correlation carried out after the changes.
( Changed at 08.11.2005 )
Rules based ATP - calculation profile & KITs/MATP
A calculation profile with overdelivery tolerances must NOT be used on component level of KITs or in MATP.
( Changed at 08.11.2005 )
Rules based ATP - location determination & KITs/MATP
Location determination and product substitution must NOT be mixed for KIT components and for MATP components.
( Changed at 08.11.2005 )
Allocation Check in Stock Transfer Orders - Delivery Groups
Stock Transfer Order (STO's) do not support the delivery group correlation.
( Changed at 08.11.2005 )
LocProd-Substitutions and Consolidation
The consolidation process does not work, if the rules use location-product-substitution-procedures (either within INC-Md or classic RBA-MD).
( Changed at 08.11.2005 )
Release with restrictions
Backorder processing for Stock Transfer Orders - Rescheduling
The rescheduling for Stock Transfer Orders is done in LC during the update. Rescheduling is supported during Backorder processing (BOP) but the results are only consistent with LC scheduling if Configurable Process Scheduling (CPS) is used
( Changed at 08.11.2005 )
Release with restrictions
Backorder Processing on Schedule line level incl. Stock Transfer Orders
The Sales order data are more substantial than the Stock Transfer Order Data. Some of this data ("missing" in STOs) can be used for sort and filter criterias in BOP. In BOP only the common filter sort criterias are considered when STOs are included.
( Changed at 08.11.2005 )
Backorder Processing on Schedule line level incl. Stock Transfer Orders
The Sales order data are more substantial than the Stock Transfer Order Data. Some of this data ("missing" in STOs) can be used for sort and filter criterias in BOP. In BOP only the common filter sort criterias are considered when STOs are included.
( Changed at 08.11.2005 )
Release with restrictions
Interchangeability cannot be used in the Capable-to-Promise Scenario
You cannot plan with product interchangeability in the CTP scenario.
( Changed at 15.11.2005 )
Bucket Oriented CTP
For bucket oriented CTP the resource master was enhanced with PP/DS buckets and a new scheduling mode for bucket finite scheduling was developed. These two developments are only to be used for CTP exclusively. Bucket finite scheduling is not supported in the following planning methods: - Production Planning Heuristics - Manual Order Processing - Scheduling Heuristics. Additionally, interactive PP/DS bucket-finite scheduling in the planning board should be avoided because it might not produce the desired results. The bucket oriented CTP check is performed only for resources which are used only as primary resources and calendar resources. The PP/DS buckets of a resource are nothing more than time aggregations; therefore the capacity aggregation of resource hierarchies or alternatives is not supported. The number of PP/DS bucket vectors per resource is limited to 1. The PP/DS bucket vector has the dimension #time# and no other dimensions are supported. The following strategy settings will not be considered in PP/DS bucket-finite scheduling: - Synchronization - Non-Working Times - Consider Campaign Requirement Note: The above-mentioned restrictions and the ones to follow are strictly valid for CTP. The Characteristics-Dependent-Planning (CDP) and specially the bucket oriented block planning will use PP/DS bucket vector and all scheduling modes related to it, however it does not necessarily mean that it will abide by the CTP relevant restrictions. The bucket oriented capacity check for block planning that was released with APO 3.1 is substituted by the bucket oriented CTP process. See also note 744400
( Changed at 06.12.2005 )
Release with approval of SAP or after consultation with SAP
MLATP/RBA with STOs - Restricted Integration with PP/DS and SNP
The functions Multilevel ATP and Rules-based ATP triggered Stock Transfer Orders are technically based on ATP trees. The scenario and the technical bases lead to restrictions described in note 510313.
( Changed at 08.11.2005 )
Release with restrictions
RBA-Subitems and Procure/Make-to-order
The RBA may lead to subitems when substituting locations or products. In case of customer individual requirements (e.g. make-to-order) the account assignment is not consistently copied to the subitems.
( Changed at 08.11.2005 )
Consolidation Location and Product Allocation (PAL)
Consolidation Location scenario is NOT designed to work with PAL. This is because the system does not differentiate between the two purposes of PAL, sales-driven or capacity-driven, which lead to different behavior.
( Changed at 24.10.2008 )
Release with restrictions
Interchangeability: FFF classes
FFF classes can be used in SNP, CTM and G-ATP. In PP/DS and DP they are not supported.
( Changed at 27.03.2007 )
No release
Characteristic propagation (CDP)and PPM
The object dependencies of R/3 are not transferred to APO. The CDP definitions and characteristic propagation have to be maintained manually in APO. Bill of materials and routings in R/3 must be Maximal bill of materials and maximal routings. Object dependencies may only linked to non APO relevant components/operations. If nevertheless object dependencies exist the retransfer will lead to inconsistencies. If you want to run preliminary costing you need to create a separate CO- bill of material/routing. If a node (operation in the routing/ component Bill of material) is being deleted in R/3 and then the PPM (which already exists in APO) is again ciff'ed (retransferred) you 'll lose the CDP-definitions in the node in the APO-PPM plan- usually the PPM plan gets inconsistent and nerd to be remaintained in APO. Please see also the OSS note 495825. Please note that since APO 4.1, the PDS (product data structure) is available in conjunction with CDP to integrate BOMs and routings including knowledge dependencies from R/3 to APO, as an alternative. For integration of characteristics and class master data for CDP, cf. note 714929.
( Changed at 02.11.2005 )
Release with restrictions
Distinguish 0 and nothing
This new functionality is only available for LiveCache time series key figures. For Characteristics-Based Forecasting (CBF) the new functionality is not supported.
( Changed at 26.10.2005 )
Seasonality in Demand Planning
The seasonal planning functionality is neither available for SNP planning areas, nor for DP planning areas with Characteristics-Based Forecasting (CBF) or Bill of Material (BOM) functionality. Due to the technical realization of the seasonality functionality, planning on seasonal level can only be performed for key figures which are based on liveCache time series. The function to prevent time desegregation of data in the past will be active for time series based key figures in DP and SNP, but not for key figures with other data sources (e.g. orders or InfoProvider). It is not possible to access data on seasonal level via BAPI. Collaborative Planning is not available for season planning. Forecasting in background or interactively is not possible on seasonal level. When using the locking option #Detailed Lock# in planning areas with seasonal planning functionality, the key figure specific locking option (#Key-Figure-Specific Lock#) is not available for technical reasons. When using the recommended liveCache locking option instead of the detailed locking, the key figure specific locking is available.
( Changed at 26.10.2005 )
Authorization checks
Forecasting: Batch Forecast is not executed, if the batch user is not authorized to change data for one of the characteristic value combinations for the selection as-signed to the batch job (only relevant if BW Authorization Concept for Characteristics is enabled, see below). A suitable message (including batch user name and selection) is written into the job log. BW Authorization Concept for Characteristics: When a batch job is started and the BW Authorization Concept for Characteristics is enabled, an authorization check will be performed at the beginning. If the executing user has no authorization for at least one of the selected characteristic value combinations, the batch job will be aborted (without doing anything) and a corresponding message (including user name) is written into the job log. CBF characteristics are not supported.
( Changed at 26.10.2005 )
Parallel mass processing
If persistent aggregates are used for a planning area the automatic parallel execution can not be used for the following processes: - Proportional factors calculation - DP mass processing: macro - DP mass processing: forecast - Creating time series objects - Load data from infocube - Copy planning version The automatic parallel execution of loading data from infocube cannot be used if navigational attributes are used in the aggregation level. The automatic parallel execution of loading data from infocube can only be used for loading data into liveCache key figures of the planning area . That means if a planning area key figure is defined as InfoCube key figure the automatic parallel execution of loading data from infocube is not supported. The automatic parallel execution of copying planning version and loading data from infocube cannot be used if characteristic assignment (mapping of different characteristics) is used for the process. The automatic parallel execution of copying planning version cannot be used for copying data between two different planning areas which are linked to two different planning object structures. The automatic parallel execution of copying planning version can only be used if all source and target key figures are liveCache key figures. If infoCube key figures are involved the automatic parallel execution is not supported. The automatic parallel execution of copying planning version and loading data from infocube cannot be used if the planning area is used for Characteristic based forecasting (CBF).
( Changed at 26.10.2005 )
Demand Planning - Multiclient Capabilities
SCM 5.0 is based on SAP NetWeaver BI 7.0. This enables DP to work with multiple clients without need of ABAP modifications (see note 522569). The following restrictions apply: - BW client must be defined at the beginning of the implementation and can not be changed afterwards. - Client copies should be avoided. - All BW-objects (like SAP BW Info Cubes, Info Objects, Info Sources and Data Source Systems) are client independent. The BW-Administrator Workbench can only be accessed in the BW-client. If InfoObjects or InfoCubes are created in a non-BW-client, they have to be activated in the BW-client. The same is true for Planning Object Structures and Aggregates; the generated InfoCube/Aggregate also have to be activated in the BW-client. Data Sources have to be created in the system where Data should be extracted from. InfoSources have to be created in the BW-client. - Planning Object Structures names must be unique across clients - Planning Areas and Planning Object Structures can only be accessed in the client where they have been created. - Only one global logical BW data source system can be defined on only for the "SAP BW client". Data loads from an SAP R/3 system or from files can only be performed from "SAP BW client"
( Changed at 26.10.2005 )
Fixing of values within a macro
The following limitation applies only if the compatibility mode for a macro book is enabled: It is not possible to change a fixed value either within one macro with different steps, within one collective macro with different macros or within one macro sequence within an event (e.g.default). Please consider the following notes: # 643517 - Macrobuilder: Fixing key figures with a macro # 687074 - Macros: General notes on fixing with macros. If the compatibility mode is disabled for a macro book, also fixed values can be changed by using the corresponding key figure change mode
( Changed at 26.10.2005 )
Promotion and Realignment
Realignment and Promotion only works if the function REALIGNMENT with the option delete source has been chosen. Any other option from the realignment tool will not deliver any results if promotions are involved. The realignment job will be terminated.
( Changed at 26.10.2005 )
Aggregated Phase In / Out
The following restrictions apply: - The functionality will not work with key figures stored in InfoCubes. - The calculation rule for the structural disaggregation of the forecast key figure and the corrected forecast key figure has to be pro rata or disaggregation according to another key figure. - The functionality does not include phase-in/out action on the historical horizon only on the forecast horizon. If phase-in/out profiles are effective in historical and forecast horizons the new function will only change data in the forecast horizon. - Aggregated Phase In / Out will only be carried out for the forecast key figure not for the key figure corrected forecast for reasons of performance and data volume. - The process is not executed if the "average days in period" function in univariate forecast profiles is active.
( Changed at 26.10.2005 )
Realignment
The following restrictions apply: - Realignment/Copy Table: The size of the generated realignment and copy table and therefore the number of characteristics in these tables are restricted. This is a general technical restriction of a DB-table in which a line can't exceed an estimated total of around 2000 characters. - DP-BOM: When using the DP-BOM functionality with the new realignment logic which has been introduced with SCM 4.0, not all characteristics can be used for the realignment and copy process. Characteristic 9APPMNAME and the characteristics representing the product can only be used as selection criteria for the realignment process. For both characteristics the 'From'- and the 'To'-value need to be the same. - CBF: For CBF Realignment and copy process from one product to another product is only possible if these two products are using the same CBF profile. - Promotions: For promotions the copy process is not supported. It is not possible to realign promotions using cannibalization. The version to which the promotion is linked to must be initialized. Promotions are automatically deactivated when realigned. - InfoCubes with aggregates: The realignment and copy process does not work for Infocubes with aggregates. - Selections: User defined (Shuffler-) selections are not considered during the realignment and copy process. Generated selections are not considered during the copy process. - Option 'Add': The option 'add values' is not supported for key figures with aggregation type A (average) and 'D' (Average at the Lowest Level of Detail). This restriction is valid for the copy and the realignment process.
( Changed at 26.10.2005 )
Data Realignment
Since SCM 4.1 within data realignment (transaction /SAPAPO/RLGCOPY) there is an option to specify individual key figures for which the data is copied or that are to be initialized. This option is not supported for InfoCube key figures and InfoCube Realignment. Here the data is copied always for all key figures.
( Changed at 26.10.2005 )
Forecast Strategy 56: Forecast with Automatic Model Selection
Forecast profiles are only generated and assigned if automatic model selection II is used in the univariate profile of the master forecast profile in the activity for DP mass processing. Automatic model selection II does not use second order exponential smoothing approaches.
( Changed at 26.10.2005 )
Parallel processing of the proportional factor calculation
The automatic parallel execution of the proportional factor calculation is only supported if the same planning area is used as source and target. In particular it is not possible to calculate the proportional factors in parallel from an InfoCube or other planning areas. In addition the automatic parallel execution of the proportional factor calculation is only supported if no persistent aggregates are used for the planning area.
( Changed at 26.10.2005 )
Promotion Planning / Cannibalization Group
Restriction: For promotions with more characteristics than the one defined as the promotion level, the cannibalization group is only effective for these combinations which also have the same characteristic values for these characteristics.
( Changed at 26.10.2005 )
Release with approval of SAP or after consultation with SAP
PPDS-PPM transfer of R/3 data changes (ECM):CF7- Modification
OSS Note 453198 "PPM: Transferring BOM components without a key date" also known as CF7 solution.
( Changed at 02.11.2005 )
Customizing CIF in APO
Some Customizing Settings depend on the target system. In these cases, you cannot transport them from the test/quality system into the productive system.
( Changed at 02.11.2005 )
Integration R/3 source list
It is possible to specify a supplying plant in the source list instead of a external supplier. This type of source list records will not be integrated with APO # they will simply be left out. Source list records which specifies a supplying plant are not integrated . Changes in source lists will not immediate transfered. Transfer of the source list can only be triggered by periodicall processing the change pointers.
( Changed at 02.11.2005 )
Deletion of R/3 Orders, Orders created not by BAPIs
# As default it will not be possible to remove orders, which are marked as R/3 orders. As there might be scenarios (e.g. testing) where it still might be useful, this function should be easily activated (e.g. modification) by an administrator/developer. # As default it will not be possible to remove orders, which were not created using BAPIs (e.g. inspection lots, #). # The deletion of objects is not communicated to external (R/3) systems. That means no events are sent.
( Changed at 02.11.2005 )
Deleted Orders will not be transferred
# Deleted orders will not be transferred. This is also the case if e.g. events exist for these orders. # Which transaction data can be transferred depends on the used BAPIs. Only the data provided for these BAPIs can be transferred. This does also mean, that eventually not all transaction data can be transferred.
( Changed at 02.11.2005 )
Phantom components not supported for RTO-Integration
Phantom components are not supported for RTO integration. The subcontractor location is not integrated with the similar R/3-subcontracting MRP-Area. The subconstracor is APO stand alone and has to be created manually in APO.
( Changed at 02.11.2005 )
Risk of inconsistency with CIF CCR by VMI Orders with extended scheduling
You can now use the /SAPAPO/CIF_DELTAREPORT3 report to delete VMI sales (with errors) that cannot be transferred to SAP R/3. Problems can occur if MBDAT in APO is unequal MBDAT in R/3 Solution: implementation of a BADI /sapapo/cif_delta3 The BAdI /SAPAPO/CIF_DELTA3 can be used to determine which SAP R/3 and SAP APO objects are to be compared using the compare/reconcile function (transaction /SAPAPO/CCR) of the Core Interface (CIF). -> Example code is available
( Changed at 02.11.2005 )
Collaborative Planning
Link to Alert Monitor from CLPSDP (Coll. DP/SNP) using the ITS parameter ~URLamon is not supported in the workflow scenario and in the CLPSDP session which is started from Collaborative Alert Monitor.
( Changed at 02.11.2005 )
Collaborative Supply and Demand Planning
Limitations for Selection Shuffler function in Coll. Demand and Supply Planning - The maximum number of the conditions which can be specified is 20, as in Interactive Planning. - The selection which is created in Collaborative Planning will be assigned to the user who created it, directly under the user folder in the selection profile. It is not supported to store the selection under the subfolder.
( Changed at 02.11.2005 )
BAPI: ProcurementOrderAPS
Restrictions regarding CreateFromSNP method (creating SNP / Deployment purchase requisition) # Only the limited location types (Production plant / Distribution center) will be supported for source and target location in this BAPI. # VMI order / scenario is out of focus in this project, the customer location (Location type 1010 for Customer ) will not be supported as source and target location. # The following objects will not be supported as a source of supply: - Subcontract - Scheduling Agreement - Contract # The method ProcurementOrderAPS.CreateFromSNP does not support the maintenance of Deployment Purchase order, but only Purchase requisition. (The object type will be decided depends on the SNP customizing #Configure Transfer to OLTP systems#) Restrictions regarding Event Control # If the Event (Change pointer) should be generated by BAPI, the Internal number assignment has to be used during the creation of orders. This means that the parameter EXT_NUMBER_ASSIGNMENT has to contain the fixed value # #
( Changed at 02.11.2005 )
System Spanning scheduling APO - R/3 for stock transport orders
This solution will not ensure that there will be the same dates calculated if you have the same product/plant if you create the stock transport orders/stock transport requisitions in APO or R/3. The solution will be provided for stock transport requisitions and stock transport orders
( Changed at 02.11.2005 )
Performance Im-provements in CIF Deltareport
The parallelization of data selection will not be available for stocks, transports and maintenance&service planning.
( Changed at 02.11.2005 )
Integration and Usage of De-fense-specific Data
# The advice code and the new requirement priority are not displayed in SCM planning tables # The integration of force elements and supply relationships will only be availably if the DFPS ADD-ON is installed and activated in the SAP ERP system. # The manual change of the advice code of an item does not trigger a new automatically ATP check even if the new advice code could due to other ATP results. The new advice code settings are only taken into account if the ATP check is executed manually. # The advice code and the new requirement priority are not displayed in SCM planning tables # The integration of force elements and supply relationships will only be availably if the DFPS ADD-ON is installed and activated in the SAP ERP system. # The manual change of the advice code of an item does not trigger a new automatically ATP check even if the new advice code could due to other ATP results. The new advice code settings are only taken into account if the ATP check is executed manually.
( Changed at 02.11.2005 )
Stock Transport Order in purchasing applications
This functionality will only be available for purchasing applications that use the business logic of the new Purchasing Order (PO) transactions, i. e. # only for stock transport orders (STO), not for stock transport purchase requisitions and not for stock transport scheduling agreements; # only for the new purchasing transactions ME21N ff; # only for the new mass transaction for automatic creation of purchase orders from requisitions ME59N. The only exception is STO items created from SCM via CIF, because CIF still uses the coding of the #old# PO. Also in this case we would use the new functionality if customizing is set accordingly. If the new functionality is switched on, we could get different results from ATP check depending on the use of the old transaction ME22 or the new transaction ME22N. Therefore we cannot allow the processing of STOs created with transactions ME21N/ME59N with transaction ME22. Further restriction: As now in purchasing standard, schedule lines will only be created and changed on daily, not on secondly basis.
( Changed at 02.11.2005 )
Stock Transport Order and product interchangeability
The functionality of product interchangeability in Stock Transport Orders (STO)s will not support - purchasing requisitions and scheduling agreements; - old purchase transaction e.g. ME21; - rescheduling in ERP, therefore in fall-back case no rescheduling is possible. It will be only available as part of the defense solution, i. e. for customers with Enterprise Add On for Defense Forces and Public Security (EA-DFPS) switched on. The fallback scenario is only available for defense customers who use an ERP system with DIMP switched on. No manual changes of sub items with exchange material are possible. Therefore the handling in case of inconsistencies between confirmed quantity in STO/delivery and real quantity in warehouse at time of goods issue can only be resolved as follows: - Either deletion and recreation of STO and delivery; or - post goods issue with #real# quantity (reduce delivered quantity), post goods receipt and set delivery complete indicator, correct situation in warehouse, create new STO item.
( Changed at 02.11.2005 )
Release with restrictions
Transformation of R/3 master recipe to APO
Relationships between phases of different recipes won't be supported. No material quantity calculation. No product flow (container resource)
( Changed at 02.11.2005 )
Release with restrictions
PPDS-PPM transfer of R/3 data changes (ECM)
Please check following notes before you use the PPM transfer of changes functionality: 508773 Composite SAP note for CORE - transfer of data changes 508779 Composite SAP note for PPM transfer of data changes
( Changed at 02.11.2005 )
Release with restrictions
Integration of workcenters with APO CIF
Following functionalities are not supported with the integration of workcenters with APO CIF: ***************************************************************** Transfer of APO resources into R/3 capacities. A CIF like one to one transfer of shift sequences, shifts and breaks. A one to one mapping of R/3-like capacity intervals to any corresponding APO object. R/3 maintenance of APO objects used by the APO resource (like e.g. set up matrix) Retransfer of objects which may depend on changes of R/3 workcenters or capacities (like transfer of routing when standard value key has changed)
( Changed at 02.11.2005 )
Release with restrictions
Overlapping: Flow manufacturing & interoperation time in the production order
Please refer to OSS Note 604878 which is frequently updated with the latest information.
( Changed at 02.11.2005 )
Inspection lots in APO
Changeability in APO Inspection lots cannot be created, changed and deleted in APO. This implies that inspection lots are sent from R/3 to APO only and never from APO to R/3. The only option to delete inspection lots in APO will be offered by the CCR tool. Link to the manufacturing or purchase order: In R/3, each inspection lot has a field indicating from which manufacturing order or purchase order the goods receipt which created the inspection lot was done. In APO, we will not have such a link. The inspection lot in APO does not have and does not show the information which manufacturing order or purchase order was its origin. However, inspections lots particitpate in the logics of preserving fixed pegging relationships that can be used since SCM 4.1. Changes on batch characteristic values during the life time of the inspection lot: When the inspection lot is assigned to a batch, it will take over the the batch characteristic values in APO only if the values are maintained before or when the inspection lot is created. Any changes to the batch characteristic values during the lifetime of the inspection lot in R/3 will not be taken over into the inspection lot in APO. The unrestricted stock which is created with a positive usage decision in R/3 will take over the batch characteristic values in APO. Prerequisites for taking over batch characteristics with inspection lots : Activating an integration model for inspection lots does not automatically trigger that batch characteristic valuations are sent in advance. This is achieved with activating an integration model for stocks. Reconciliation reports etc. in R/3: After any reconciliation report run in R/3 which has an impact on inspection lots and / or QM stocks ... the CCR tool must be started to reconcile the situation between APO an ... and in case of deletion of inspection stocks in R/3, the tool from the switch concept to get rid of super numerous inspection stocks in APO ( in R/3, the tool from the Inspection lots excluded from APO integration: Not covered by this integration concept are.............. Inspection lots which are do not have the status Quantity posting posting required (e.g. inspection lots for in-production checks, inspection lots for planned orders,#.). Inspection lots for handling units (R/3 Handling Unit Management)
( Changed at 02.11.2005 )
Remaining duration adjustments
RESTRICTIONS The solution covers adjustments of the Remaining Durations in APO exclusively. The current R/3 confirmation doesn't reduce capacity requirements level in APO. This will not change with the new solution even if in R/3 the capacity requirement reduction takes place. The part of the R/3 capacity requirements for production order integration without PPM/RTO in APO remains unchanged. The solution is only valid for PP-production ordres, not for PPPI-process orders or repetitive manufacturing orders. (For process orders in R/3 release 4.70 the capacity requirement reduction can be configured similar to the PP-workcenters in R/3 but these customizing isn't valid for the confirmations). Partial confirmation of an activity allows the maintenance of a forecast finish (date) or adjusted defaulted forecast values. These values are not transfered to APO and therefore APO doesn't expect that the left activity differentiate from the original planned activity.
( Changed at 02.11.2005 )
Release with restrictions
Integration of SNP Planned Orders
Outside of the SNP- production horizon changes regarding partial released planned orders into production orders are not transferred from R/3 to APO. The initial load from R/3 to APO always creates PP/DS planned orders for the order types: make to order production, engineer-to-order production and planned independent requirement with type 'VP'. This behavior is independent from the value of the field 'Create Planned Orders as SNP Planned Orders' at the screen to activate the integration model. The deletion or creation of planned orders always is transferred from R/3 to APO.
( Changed at 02.11.2005 )
Release with restrictions
Availability of stock types for pegging
The functionality does not include full CIF integration between the customizing of availability of stock in R/3 and the location product master data in APO. The fields to set the availability of stock types are added to the CIF structures. But in standard, they are not filled from table T399D to protect the more detailed configuration in APO master data. The update through CIF can be achieved by implementing a customer-exit. In standard, the default settings are used for all location products in APO.
( Changed at 02.11.2005 )
Release with approval of SAP or after consultation with SAP
MRP Areas
The usage of stock transport orders (instead of stock transfer reservations) to transfer stock between MRP areas implies R/3 enterprise release 4.70 extension 2.0, see also note 594318. This functionality should be used only after consultation with SAP.
( Changed at 06.12.2005 )
Special Procurement Types
The following special procurement types from R/3 are supported in APO: Subcontracting, stock transfer, phantom assembly, production in alternative plant (called "production in alternative location" in APO). The following special procurement types from R/3 are not supported in APO: Withdrawal from alternative plant, direct production / collective order, phantom in planning.
( Changed at 06.12.2005 )
iPPE Workbench Express
The iPPE Workbench Express is not released at all for R/3 integration and CDP.
( Changed at 06.12.2005 )
WUF just available for APO Master Data objects
The Where-Used-For Framewrok is only available for APO Master Data Objects: - location - product - locationproduct - lane - quotation - resource - PPM - PDS It is not connected to other SCM components like ICH, LIME etc.
( Changed at 02.11.2005 )
Report for Customizing comparison
This report is just planned for comparing data between R/3 and APO; taking over customizing values from one system to other is only possible for the following constellation: taking over locations from R/3 to APO.
( Changed at 02.11.2005 )
Restricted availability of change documents functionality
Change-documents are available for the following APO master data objects: - location - product - locationproduct - lane - quotation - Partnerproduct - partnerlocation - orderguideline
( Changed at 02.11.2005 )
Hierarchies can be used with the following restrictions
# The levels of the hierarchies are fixed. It will only be allowed to add more than one parent to a given hierarchy-node. # Character schema hierarchy and generated hierarchies will not be available as #Net-work-Hierarchies# # Extented hierarchies can not be maintained via CIF even when used in the TP/VS application (transportation zones). # It is not possible to display all the parents for a child (a kind of where-used list on child). # For PDS hierarchy the parent node can only be a PDS-node, for the added child nodes PDS and iPPEs are possible.
( Changed at 02.11.2005 )
Enhancement Concept for Master Data Tables
- No floating point or RAW fields are allowed - Enhancement structures of BAPIs will not enhanced automatically - Only location, product and location product are supported - Version dependent data will not be supported
( Changed at 02.11.2005 )
Material Group for Transportation Lane
# The quotations are not maintainable with product groups. # It is not possible to create product specific means of transportation for product groups. # Procurement relationships (information records, contracts, scheduling agreements) based on product groups are not supported
( Changed at 02.11.2005 )
Serial Numbers
In R/3 a material may have a serial number. There's no processing of serial numbers in APO.
( Changed at 06.12.2005 )
Release with restrictions
Interchangeability Master Data of R/3 is not considered in APO
No integration of R/3 material master discontinuation and R/3 material versions via CIF with APO.
( Changed at 15.11.2005 )
Release with restrictions
Model Mix Planning
Regarding limitations for Model-Mix planning see note 627377. The functionality of the Genetic Algorithm for multi lines is limited and should be used only after consultation with SAP. E. g. only the lines belonging to the planning segment and the restrictions assigned to those lines are taken into account during the optimisation run. The Model-Mix-Planning algorithms do not take the priorities of the customer independent requirements into account. MMP also daoesn't consider the settings made in the "Model and Version Management".
( Changed at 06.12.2005 )
Operation Split
The functionality of operation split is not supported in APO. See also note 441777.
( Changed at 06.12.2005 )
Release with restrictions
Container Resource
Regarding limitations of the container resource see note 498223. Please note that the optimizer doesn't support the container resource.
( Changed at 06.12.2005 )
Release with restrictions
Performance SNP Optimizer
Depending on the data volume and usage of discretization (e.g. use of lot sizes or cost functions), the performance of the SNP Optimizer can be critical. To check the feasibility of an SNP optimization problem in terms of performance, a dedicated sizing sheet exists on the Service Marketplace (SCM Technology). Please fill in the Excel sheet and check the result directly. You can use the optimizer sizing sheet for APO 4.x to do an optimizer sizing for APO 5.0. This should be done in an early phase of the project (Blueprint). If necessary (depending on the output of the Excel Sheet), please ask for the dedicated consultancy service for optimization mentioned on this page, too.
( Changed at 15.11.2005 )
Explanation Tool and Automatic Cost Generation for SNP Optimization
Explantion Tool: 1. Solution Indicators Aggregation of the different solution quality indicators will only be supported in a limited way. In order to have a quick overview the global aggregation on model level will be shown directly. The most detailed level for location-product-specific indicators will also be shown directly. Aggregation levels in between (e.g. on location or product level) can be simulated by the report functionality of ALV or by an export of the data to the Business Warehouse. 2. Explanation Mode Plans/solutions stored in the liveCache will not be explained. Only solutions stored in the optimizers output-log can be explained. Therefore, existence of the input- and output-log is mandatory for using the explanation tool. Only cost-optimal deployment is supported. Special deployment strategies like fair-share or push cannot be considered for explanation. Only one possible explanation is generated. As a consequence, the explanation need not be unique. Resolving plan-exceptions according to derived reasons does NOT imply that after re-optimization excep-tions is #solved#, i.e. disappears In case of cost push models, the explanation given can contain more reasons as required just for satisfying a certain backlog. In case of explaining discrete problems, it can be that only for a subset of plan-exceptions explanations can be found due to time-limit/complexity reasons. SNP Optimizer relevant systems settings should not be changed between optimization and explanation run since otherwise no explanation can be found. Since the explanation tool does not relax calendars it cannot propose/detect capacity problem on non-working days. This is in particular relevant if the bucket profile contains daily buckets. The product availability analysis checks only whether there exists a source of supply for each product but not whether its available within the planning horizon. Therefore, non-deliveries due to PPM or transport-validities or the usage of time-phased PPM parameters cannot be detected. Instead, a leadtime problem may be detected. The explanation tool cannot explain non-deliveries or safety violation caused by sub-optimal solutions. Therefore, it is important that solutions that are the result of a discrete problem have sufficiently high solu-tion quality. Automatic Coct Generation (ACG) will not generate # Cost functions (procurement, means of transport, production) # Costs for resource capacity extension # Costs for resource usage # Costs for minimum resource utilization # Costs for means of transport # Shelf-Life Cost The automatic cost generation (ACG) will generate a cost model that triggers the SNP or deployment optimizer to maximize the service level. Due to the fact that e.g. no information is given about potential fix costs, or for additional shifts, trade off decisions cannot be taken in a meaningful way. For further information, please check the documentation, too.
( Changed at 15.11.2005 )
Release with approval of SAP or after consultation with SAP
Safety Stock in PP/DS
To consider dynamic safety stock (e.g. safety days supply) in PP/DS the new alerts - stock below safety stock - stock below target stock and - stock exceeds target stock are provided. Characteristics, shelf-life and min-max pegging intervals are not considered for the new stock alert types. The R/3 customizing value for the percentage of safety stock availability will not be integrated with APO. The product master data must be maintained within APO to utilize the target stock level method functionality. Enhancements in SNP are not part of this project. Therefore, time-dependend target stock level methods will not be supported by PPDS. Consequently, target stock alerts are only generated when a static target stock level method is used. The fill level of the container resource is not affected by this development. For planning PP/DS does not take all possible values into account that can be maintained on the lot size tab in the APO product master - in contrast to SNP planning. PP/DS supports the following entries: - Reorder point method: 2 (Reorder supply from location product master) - Target stock level method: Target days' supply from product master) - Safety stock method: - No Safety Stock - SB Safety Stock from Location Product Master - SZ Safety Days' Supply from Location Product Master - SM Max.of Safety Stock and Safety Days'Sup.from Loc.Prod.Master - MZ Safety Days' Supply (Time-Based Maintenance) - MB Safety Stock (Time-Based Maintenance) - MM Max.of Safety Stock and Safety Days' Sup.(Time-Based Maint.)
( Changed at 06.12.2005 )
Fixed Pegging
Fixed pegging in APO is not kept during all document type changes in R/3 . Note 698427 lists all supported document type changes. The stock transfer orders have two nodes - fix pegging is kept for the supply node at the target location, but not for the requirement node at the source location. Not supported at all are forecasts and forecast consumption, scheduling agreements (neither SD nor MM) and REM backflush, since these are not sensible from a process point of view. Collective orders are not supported in APO and consequently neither by fix pegging. Assembly processing is not supported either (no integration of R/3 assembly orders (planned orders)). The document type changes from customer inquiry to customer quotation and from customer quotation to sales order are not supported. The document type changes from transport order to delivery is not supported. The limitations of fix pegging for some further functions and processes are described in note 704583. Additionally some comments: Subcontracting: For the subcontracting process with production at the supplier the finished product at the supplier location is always planned with fix pegging. This fix pegging arc can not be deleted with any heuristic (e.g. SAP_PP_11). Shelf Life: Fix pegging does not take shelf life restrictions into account. Make to Order: Though it is technically possible to use fix pegging in a make to order scenario as well, it does not make much sense because the assignment between demand and receipt is already given by the account planning segment. Prioritisation: Fix pegging does not calculate any priorities itself, but it can propagate the priorities from the requirement. Batch Determination: Batch determination in R/3 is not influenced in any way by the fixed pegging in APO. The batch determination in R/3 does not trigger the creation of the according fix pegging arc in APO. It is however possible to use the heuristic SAP_PP_019 to create fix pegging in APO based on the same batches - but this is not an online process. A prerequisite for this is that no fix pegging existed before. Quantity Propagation: Changes in the order quantity of a requirement does not lead to the adjustment of the order quantity of a fix pegged receipt element and vice versa. Multiple scheduling lines in sales and purchase orders: Many information for the integration between R/3 and APO is based on the order item and not on the schedule line item. Therefore during document type change the quantities for the fix pegging will be kept for the order item but not necessarily for the correct schedule line. The Heuristic for Creating Fixed Pegging can be called before or after a MRP-level-based Pro-duction Planning run. During the planning of single products or between MRP-levels in a Production Planning Run it is not possible to include the SAP_PP_019-Heuristic, because there is no possibility in the Stan-dard Heuristic Framework to integrate other Heuristics additionally to the product heuristics. If users want to integrate similar logic, than provided by SAP_PP_019, within the Product Heuristic (e.g. in SAP_PP_002 Standard Lot Heuristic), the BadI /SAPAPO/RRP_PLANNING has to be used to create Fixed Pegging before the Net-Requirements-Calculation (Method PEGID_GET_IO). As mentioned above, the ATP against Pegging can be done by defining the production type #Characteristic Evaluation#. In this case restrictions are described in note 601813: - Scope of Check - Specific availability check for sublocation and version (LiveCache- Pegging is neither storage location-specific nor version-specific). Therefore Fixed Pegging should be used to establish such kind of relationship (e.g. Batches) - Past Receipts are always taken into account (as Past Receipts are always inte-grated in LC-Pegging) - Advanced confirmation logic - ATP against Pegging and ATP against Time Series cannot be combined in Rules Based ATP - Check Horizon According to the solution for Release SCM 4.1 (PP/DS-ATP including Fixed Pegging), the restrictions #Scope of Check# and #Check Horizon# do not apply any more.
( Changed at 06.12.2005 )
Classification System (CDP vs. VC/iBase)
If the components for subcontracting are planned with CDP, the characteristic values are not transferred to R/3. Classification is not used for components of inhouse production orders. The iPPE side access does not support CDP classification. Reference characteristics: It is necessary to transfer first characteristics and then BOM and routings. So it is not possible to read APO master data information in the BAdI implementation. The use of different configuration schemes - characteristic dependent planning (CDP) and variant configuration (VC) - within one client is not released without special consultation by SAP. With this functionality the classification system can be defined on product level, but it is not possible to use VC below a component with CDP classification. The integration of VC characteristics both for the mixed scenario and for the VC only scenario requires a R/3 release 4.6b or higher. In the delta report the classification is checked for - VC regarding the same configuration reference and - CDP regarding the existence of characteristics. It is possible to perform an extended configuration check for the classification with the effect that the value of the characteristics is checked as well. Consistency Check in live Cache (transaction OM17): # Consistency of information for characteristics# based time series is not checked # Some checks do not prove full consistency, but only carry out important plausibility checks # Checks for VC Configuration only apply to active planning version (planning version 000) # Correction of inconsistencies may require subsequent execution of CIF delta report. There is no link between this functionality and CIF delta report.
( Changed at 06.12.2005 )
Pegging with Delivery Tolerances and "Use total supply"
This functionality should be used only after consultation with SAP. The functionalities "delivery tolerances", "use entire receipt" and "use total stock" (see product master, tab "Demand") only lead to satisfying results in very simple cases. For example the combination of partial delivery and delivery tolerance leads to incorrect results because the system can not calculate the delivery tolerance correctly in case of a partial delivery. It therefore is necessary to contact SAP in order to evaluate if the mentioned functionalities can be used in the customer's scenario.
( Changed at 06.12.2005 )
Fault Tolerant Scheduling
Fault tolerant scheduling is only used for the scheduling of orders and can not be used for the creation of orders. No Backtracking in Scheduling: A scheduling action might affect more than operation. However, each operation is scheduled only once, independently of previous operations and in a given sequence. If a scheduling problem consisting of several operations might be solved by an allowed violation of a constraint for the first operation, the scheduling action might terminate without solution nevertheless because the problem only occurs at the second operation. Fault Tolerant Option "Schedule Infinitely": If "schedule infinitely" is chosen as the fault tolerant option, the scheduling modes "insert operation", "insert operation and close gaps" and "squeeze in" might cause that some operations are pushed outside the planning horizon (the operation sequence is kept with these scheduling modes). Infinite scheduling does not allow scheduling outside the planning horizon, therefore the scheduling action might terminate without solution.
( Changed at 06.12.2005 )
Reference Operation Sets
Reference operation sets are only integrated for PDS and for orders, not for the PPM. The prerequisite for the integration of reference operation sets is Plug-In release 2004.1 and APO release 4.1 or higher releases.
( Changed at 06.12.2005 )
Scheduling Mode "Close Gaps"
Depending on the complexity of the scenario and the planning environment the system is not always able to schedule the operation and close existing gaps although the scheduling mode "insert and close gaps" is used.
( Changed at 06.12.2005 )
Production Data Structure (PDS)
The supported functionality of the PDS differs from the PPM. The differences are described in note 744445. The limitations regarding the PDS functionality are described in the following: Block Planning: # Classification of operations with class type 018 is not possible for recipes. If recipes are used on R/3 sides and Block Planning should be used on APO side, a BAdI has to be implemented for the classification of the activities. Variant Configuration & Object Dependencies: # The transfer of object dependency and classification from R/3 to APO with the PP/DS runtime objects works only with R/3 release 4.6B and above. # The integration of variant configuration can only be used with R/3 CDP # To add characteristic requirements to an input node it is necessary to implement the BAdi method CHANGE_EXPL_RESULT of BAdi /SAPAPO/CULLRTOEXPL or using an ABAP class which must be maintained at the input node. In case of non-configurable BOM, it is possible to set default requirements by maintaining batch classification in the BOM. # Restrictions exist in mixed scenarios (VC (Variant Configuration) and CDP). It is not supported to have components (input and output nodes) that are relevant for a variant configuration scenario below a CDP relevant master output. CDP relevant components below a VC relevant master output will be only valuated with a copy of the configuration of the master output or with an own instance configuration that comes from a multilevel configuration. It is not possible to valuate them per object dependency that is linked to the component. PP-PI / Recipes: # The integration of the PDS with R/3 for recipe can only be used with R/3 release 4.6B and higher. # Relationships between phases of different recipes won't be supported. # No material quantity calculation. # No product flow (container resource) . Comparison Report PDS and R/3-Explosion: The comparison report (transaction /SAPAPO/RTO_ORD_COMP) does not compare - sub-operations and secondary resources - set up groups and set up keys - configuration of the input and output products - durations of order internal relationships Continuous Input / Output has to be set via BAdI. The PDS is NOT RELEASED for the following functionalities: # parameter efficiency # extended order generation (EOG) # multiple output planning (MOP). Planning with Phantoms: When using the PDS it is not allowed to use the same phantom several times in the BOM of a finished product if a component of this phantom is assigned to different operations in the routing. SNP-PDS Generation from R/3: # No ECM for operations, activities, modes and capacity requirements. # Only the data that is valid at the provided routing explosion date will be considered for the PDS # Only bucket or mixed resources (else error during transfer) # No product variants, configuration will be ignored # Fixed duration (multiple of days) is required # No breaks between the activities are modeled (will be ignored) # Only linear chains of activities are modeled. # Relations in recipes will be checked and cause an error if not linear. # Only the standard sequence of the routing will be considered. # TDPP only via BAdi SNP-PPM Generation: It is not possible to generate SNP-PPMs from a PP/DS-PDS. Instead the generation of the SNP-PDS from R/3 should be used (as mentioned above).
( Changed at 06.12.2005 )
Multi Level Scheduling Framework
The idea of the Multi-Level Scheduling Framework is to provide a basis for heuristics which are able to tackle more complex scheduling problems by processing the activity network instead of single activities. The Multi-Level Scheduling Framework is not yet released for customer developments, because SAP might change the interface without compatibility. Order validity is considered in that way that orders that can't be scheduled finitely on a resource, are scheduled deallocated within the order validity. If it isn't possible to schedule the orders deallocated within the validity interval, then the orders will remain on its original position. The following constraints are not supported by this heuristic: # relationships with maximum length (order internal, or between activities of different orders, i.e. pegging arcs with maximum length) # continuous I/O # shelf life # characteristics # container resource # production campaign constraints # block planning # synchronisation on multi resources
( Changed at 06.12.2005 )
PP/DS Horizon
The field "PP/DS Horizon" in the APO master data has three characters. Therefore the maximum number that can be entered is 999. That means that the maximum length of the PP/DS horizon is 999 days.
( Changed at 06.12.2005 )
Keep Activity Dates When Transferring Orders to APO
The functionality to keep activity dates provides the possibility to avoid APO doing a rescheduling when orders are transferred from R/3 to APO. The operations of production orders have to have the status DSEX in R/3 to keep their activity dates in APO. The activity dates of planned orders are generally retained, as long as the PPM/PDS is not reexploded. Limitiations: Goods receipt time processing activities are scheduled always. However, with correct and unchanged settings at the handling resource and with an unchanged goods receipt processing time this should not have an impact on the dates of the goods receipt time processing activity. Not all finite strategies are supported with this functionality. For some finite strategies the systems switches to infinite scheduling in case that the activity dates shall be kept. However, SAP recommends infinite strategies in the strategy profile for CIF integration anyhow. Keeping activity dates will overrule the settings for synchronisation for a resource. If activity dates are kept in APO existing violations of other boundary conditions in APO will not be removed, e.g. violations of pegging relationships and relationsips between operations.
( Changed at 06.12.2005 )
Overlap & Continuous Input/ Output
Overlap due to a continuous production (quantities are continuously handed over to the next processing step instead of only at the end) can be modeled in two ways: - within an order by order internal relationships a start - start relationship can be defined - between orders the functionality of continuous consumption can be used. Note that continuous consumption is only considered in production planningheuristics and not in scheduling heuristics. Continuous consumption does not work with external procurement and sales orders. The heuristic "SAP_PP_C001" must not be called by the heuristic "SAP_PP_Q001". See further explanations in the customizing where the heuristics are maintained and see also note 448960. Since APO 4.1 continuous output is considered by ATP. Note 604878 contains additional information to this topic.
( Changed at 06.12.2005 )
Transfer Planner from R/3 to APO
The planner in APO does not correspond to the MRP controller in R/3 and is not transferred to APO. If it is desired to match the MRP controller to the APO planner, it has to be considered that the field planner in APO has three characters and is independent from a location (in contrast to R/3). .
( Changed at 06.12.2005 )
Planning Without Final Assembly
The system only creates safety stock in the make-to-stock segment. Only demands in the make-to-stock segment can consume stock.
( Changed at 06.12.2005 )
Planning with Validity Restrictions of BOMs and Routings
Regarding planning with limited validities of BOMs and routings see documentation note 385602.
( Changed at 06.12.2005 )
Lot-Sizing Procedure Fixing and Splitting
The lot-sizing procedure #Fixing and splitting# (FS) only exists in R/3 and not in APO. Explanation and recommendation: If planning is performed in R/3, all partial lots created when using FS cover exactly one requirement and are scheduled in a sequence (in contrast to FX where all partial lots are scheduled to start at the same time). Though the planning is executed infinitely the procedure FS therefore spreads the planned orders. This makes a finite planning that might be done later in R/3 easier especially if there aren#t any planned orders of other products using the same resource. In APO this lot-sizing procedure is not available because better possibilities exist to create a finite schedule for planned orders.
( Changed at 06.12.2005 )
Accessibility
The Resource Planning Table is not intended to handle or to be used for such business functions: - Planning of multi resources. - Planning of bucket resources. - Displaying network information (pegging, relationships) The function shall be callable only from those transactions which call the screen #Receipts View#, which is screen 1000 from function group /SAPAPO/RRP_FRAMES. That includes the transactions: 1. /SAPAPO/RRP4 #Receipts View# 2. /SAPAPO/RRP7 #Mass Conversion/Transfer of Planned receipts in Active Planning Version# 3. /SAPAPO/SNP2PPDS #Conversion of SNP Orders into PP/DS Orders# 4. /SAPAPO/CDPS0 #DPS Variable View# and other related transactions 5. /SAPAPO/RPT #Product Planning Table#
( Changed at 06.12.2005 )
CTP
Note 426563 describes most of the limitations for CTP. CTP and Periodic Lot Size: CTP and period lot size are mutually exclusive. See also note 426563. CTP and Safety Stock: The combination of safety stock / saftey days' supply and CTP is not supported in APO. See also note 426563. CTP and Backorder Processing: CTP can not be used for backorder processing. If backorder processing is performed for products that use CTP, existing receipts are considered but no new receipts are created. See also note 426563. CTP and Rules-Based ATP: This functionality should be used only after consultation with SAP. Due to the fact that CTP uses the order live cache and not the ATP time series, the use of CTP in combination with other rules within a rules based ATP check might undermine the purpose of the ATP rules. For example if a maximum allowed delay is used in a first rule to prevent the usage of stock on hand for demands in the future, CTP (production directly) is called with the complete required quantity (though there is stock available). In this case CTP performs a net requirement calculation and does not create any additional receipts. See also note 426563. CTP and Co-Products: The combination of CTP and co-products (i.e. more than one output product of a planned order is planned with CTP) is not supported in APO. For further information about CTP see also note 426563 CTP and ECM / Validity Limitations: This functionality should be used only after consultation with SAP. Due to capacity restrictions a planned order might be scheduled after the requirement date (which is the explosion date). If the scheduled date is outside the validity horizon for the order, a new order explosion is required with probably different components or operations which would lead to very time consuming calculations and possibly even loops. The CTP algorithm therefore supports only one new order explosion and terminates with an error if this is not successful. For further information about CTP see also note 426563. CTP and Planning Strategies / Forecast Consumption: The planning strategy "Planning Without Final Assembly" and "Planning Product" are not supported with CTP. The planning strategy "Planning With Final Assembly" is only supported with CTP if the ATP time series are used for the ATP check (production type "standard" in the check mode). Else the forecast demands reduce the available quantity.
( Changed at 06.12.2005 )
CDP and ATP with Characteristic Time Series
This functionality should be used only after consultation of SAP. If ATP time series are used with characteristic values, it is possible to enter the required selection criteria in the sales order and use these later for batch determination with CDP. Due to the integration of the characteristic values this is only supported for the process sales orders / delivery / batch stock. If no characteristic values are assigned to a requirement it is possible to get an overconfirmation, since the ATP check is carried out on locationproduct, sublocation, batch and characteristic level independently. The receipts without specified characteristic values (often planned receipts) are not used for the ATP confirmation for a requirement with a specified characteristic value. Furthermore, the integration of selection criteria for batch determination with CDP is only supported for R/3 release 4.6B and higher.
( Changed at 06.12.2005 )
CDP and Block Planning
Unspecified characteristics in planning and pegging: Concerning CDP there are limitations regarding unspecified characteristics in planning and pegging. See note 526883. Block planning: Regarding block planning see note 528189.
( Changed at 06.12.2005 )
Finite Scheduling in MRP
Finite scheduling in the MRP run is not possible for new installations. For upgrades this functionality should be used only after consultation with SAP. Regarding finite planning please pay attention to note 459694 and 551124. Explicitly the usage of the heuristic SAP_MRP_002 which is mentioned in the first note requires consultation with SAP.
( Changed at 06.12.2005 )
Shelf Life
Regarding the shelf life functionality see notes 339576 and 391018.
( Changed at 07.12.2005 )
Partial Delivery of Output Products
The full quantity of an in-house order is available at one discrete point in time, usually at the end of the order (with the exception of continuous input/output, see the according limitation). A partial delivery of the output product is not supported in APO. It is not recommended to split in-house orders in order to create a workaround for the partial delivery of the output products because this may lead to performance problems.
( Changed at 06.12.2005 )
Calculation of capacity requirements, durations and component requirements
The calculation of capacity requirements, durations and component requirements are calculated with the formula X = (Order quantity) * A + B. In contrast to R/3 other formulas are not supported in APO.
( Changed at 06.12.2005 )
PP/DS Optimisation
The PP/DS-optimizer is only scheduling orders, it does not create orders and does not change lot sizes. The optimizer does not consider storage resources. For a complete list of limitations see note 840887. Performance: To check the feasibility of a PP/DS optimisation problem in terms of performance a dedicated sizing sheet exists: http://service.sap.com/scm -> mySap SCM Technology -> Performance: Performance & Configuration -> System Requirements for SAP PAO Optimizer -> PP/DS Optimizer Sizing Calculator This sizing sheet should be used in an early phase of the project (Blueprint). If necessary (depending on the output of the Excel Sheet), please ask for the dedicated consultancy service for optimisation mentioned on this page, too.
( Changed at 06.12.2005 )
Usage of LPP (Long Products Planning)
If LPP (Long Products Planning) solution is used note 880091 has to be considered.
( Changed at 06.12.2005 )
No collective conversation triggered out of the Planning Board
The new transaction is not integrated into the Planning board. That means the selection and transfer of blocks from the planning board into the new transaction is not supported neither the mass conversation directly triggered out of the Planning Board.
( Changed at 15.11.2005 )
Some planning scenarios within consideration of lengthallowence are not supported
From the planning point of view, either the operation duration or the operation capacity requirement may be variable # not both at the same time. The solution does not support scenarios where the operation duration is fixed and the operation varies according to operation quantity. Not supported as well, are set-up durations which have been modified using an available BADI. Setup times are fixed in the PDS.
( Changed at 15.11.2005 )
Subcontracting
In APO it is not possible to change the dependent demand for subcontracting purchase requisitions. Note, that subcontracting in APO is modelled with the help of two orders . A planned order in the subcontractor location produces the material in that location and a stock transfer requisition transfers the material from the subcontractor location to the demand location. You can not change the transfer demand for the finished item in the subcontractor location and you can not change the component demand in the subcontractor location either.
( Changed at 08.03.2006 )
Release with restrictions
Collaborative Management of Delivery Schedules (CMDS)
CMDS and ATP: CMDS uses the ATP basic method "Product availability check". Other methods can not be used. However, an extended confirmation logic can be added to the ATP basic method "Product availability ckeck". This functionality should be used only after consultation with SAP. This addendum consists of two parts: The confirmed quantities remain allocated to the single orders even if there's no product availability of the minimum confirmed quantity. The distribution of the ATP quantities that are still available is executed per schedule line and not per item. Ask SAP about the necessary system settings. CMDS and TP/VS: CMDS does not work in combination with TP/VS.
( Changed at 06.12.2005 )
Release with restrictions
Interchangeability in PP/DS
In PP/DS, there are several restrictions: - in-house production orders with multiple substitutions cannot be transferred to R/3 - Subcontracting and collaboration using scheduling agreements (CMDS) do not take product interchangeability into account - planning with shelf life data is only possible with restrictions - only specific procurement planning heuristics are suitable as product heuristics, e.g. the procurement planning heuristic that plan according to a reorder point method does not take account of product interchangeability For more detailed information, please check the online documentation (SAP library) for SAP Supply Chain Management: Cross-Application Topics -> Product Interchangeability -> Product Interchangeability in PP/DS: Prerequisites Additionally, the following restrictions also apply for PP/DS. - FFF classes can only be used in SNP and G-ATP. In CTM, PP/DS and DP they are not supported. - Interchangeability cannot be used in conjunction with configurable products (neither CBF nor CDP). Parallel discontinuation in which several products are discontinued dependent on another is not supported. Only 1:1 relations/substitutions are supported. Complex product interchangeability of the form 1:M (where 1 product can be substituted by several other products), N:1 or N:M is not supported. The use of assemblies in interchangeability groups is not supported.
( Changed at 15.11.2005 )
Release with restrictions
Rapid-Planning-Matrix
The Rapid-Planning-Matrix can only be used in combination with the iPPE and with production line resources and not in combination with shop floor resources (single, multi, single-mixed and multi-mixed). The Transaction RPMBAL to display capacity utilisation (capacities of resources and their utilization by activities coming from RPM LC matrices) is not released. See also note 699773.
( Changed at 06.12.2005 )
Release with approval of SAP or after consultation with SAP
Reservation Planning
This application may only be implemented in customer projects with SAP participation that have SAP's consent. Before commencing the project, an evaluation of the project scope and the processes to be covered must be completed together with SAP. The reason for this is that extra integrational programming is always required per customer in order to implement Reservation Planning. The reservation planning method can not be combined with any APO-ATP- method. Only the check quantity equal one in each order line item is supported.
( Changed at 06.12.2005 )
Release with restrictions
Explanation Tool in CTM
Explanation functionality: - Plans/solutions stored in the liveCache will not be explained. - Only the partial and non-delivery of demands will be explained. - Only a current planning run will be explained. It will not be possible to explain a planning run from an old log-file. - Explanations refer to a specific CTM engine run. Generally, a CTM planning run may consist of several engine calls (sequential safety stock, interval planning; parallel planning). Solution indicators: - Only bucket utilization of a resource will be considered, that means time-continuous planning has to use mixed resources.
( Changed at 15.11.2005 )
Quota Arrangement With Demand Splitting is not supported in subcontracting process
Quota arrangement with demand splitting is not supported in a subcontracting scenario, i.e. demand splitting (of a dependend demand) at the subcontractor location according to quotas is not supported, because the integration of several planned orders for subcontracting to ERP is not possible.
( Changed at 19.02.2008 )
CTM cannot create multiple Fixed Pegging links for the same material assigned to the same activity.
CTM cannot create multiple Fixed Pegging links for the same material assigned to the same activity.
( Changed at 09.07.2008 )
Release with restrictions
Manual Transport of CTM Profile settings
Using this function one can transfer the settings of a CTM profile from one system to another, but consider the following limitation: The CTM profile refers to some additional objects (e.g. calendar, planning version, master data selection ID etc.) for selecting the master and transaction data used for planning. Only the reference to the objects as used in CTM profile will be transported. The objects details or the objects iteself will not be transported. The users has to ensure that the objects refered in the transported CTM profile should exists in the traget system. The transport log will list all such objects that do not exists in target system. This has to be manually corrected by the users. This manual transport report is only meant to be used for updating the profile settings. For successful transports it is required that the master data objects referred in CTM profile should exists in both the source and the target system. E.g. Only the the ID for a particular calendar is used in the CTM profile. Thus also only the reference to this calendar will be transported. The calendar itself schoul exist in the target system if one wants to use it. Therefore the calendar needs to be transported separately.
( Changed at 15.11.2005 )
PPM/PDS in CTM Planning
- Activities need to be in linear sequence - Breaks between activies can only be modeled for PP/DS PPMs, exception the function "Maximum intervall between activities" allows a global break value in SNP PPM (The function can be found in the CTM Profile Tab Setting - Master Data Setting - Inhouse production ... In former Releases the Parameter ACTREL_MAX could be used for this.) - Activity relation only: END -START supported - No support for set up matrixes; utilization parameter; set up activity - The restriction is that the output of the head component, i.e. the output of the location-product for which the PPM/PDS was selected, needs to be at the last activity. - PI Operations ( Process Industry Operations) are ignored - No off set times supported; yield always available at the end of the activity - For PP/DS PPMs a primary resource must be defined - Utilization and Unscheduled breaks NOT supported only for time continuous resources (works fine for bucket resources)
( Changed at 07.07.2008 )
Documentation - Time Phased Safety Stock planning in CTM
For planning a time phased safety stock (e.g. when using the advanced safety stock methods from SNP) CTM provides two alternative methods which have their own restrictions. 1. Standard Safety Stock planning The standard safety stock method of CTM consits of two internal runs of the CTM engine which are not visible for the user. Because of this two runs it is not possible to consider decreasing safety stock. Example: Week1 Week2 Week3 Saftey Stock 100 150 100 Fcst 200 200 200 CTM Net Requiremnt 300 250 200 (not 150) In Week3 the safety stock decreases from 150 to 100. Thus 50 would be available to fulfill demands. CTM can not consider this thus it would plan 200 to fulfill the forecast instead of planning 150 and using 50 of the safety stock from week2. In order to overcome this and to have 150 planned instead of 200 it is necessary to use the CTM intervall planning which can be performance intensive. 2. Alternative Safety Stock Method (Control Parameter SSTOCK_MODE) When using this setting CTM uses a totally different safety stock method This method carries out only one run. Thus it can consider decreasing time phased safety stock without intervall planning. This method can not consider all prioritisation criteria which can be normally used for CTM. It can not consider the descriptive characteristics for example. Additionlly when using this method fixed pegging can only be created within a supply tree. The supply tree will always be pegged dynamic to the independent requirement to be satisfied. In other words fixed pegging is only planned between dependant requirements but never between independent requirements.
( Changed at 15.11.2005 )
Goods Receipt Times in CTM
The function #goods receipt times# is only supported if the following conditions are fulfilled: 1. All possible output products (main output products and co-products) of a SNP or PP/DS plan need to have the same #goods receipt times# and the same "receiving calendars". 2. This is also necessary to consider in case one product is produced in another location. Thus the product#s #goods receipt times# and "receiving calendars" need to be identical as well. Production in another location is a function, which can be used to model a product, which is produced in location A, but its output appears in location B. In case different receiving calendars or receipt times are maintained for the out put products of one plan the goods receipt times are not taken into account. The master data checker of CTM is also checking this and comes back with a message in case the times or the calendars are not identical. For output products of different plans it is possible to have different calendars or receipt times. But note only if the output products refer to DIFFERENT plans. Note also: - Between the last activity of a plan or PPM and the goods receipt activity it is not possible to have any kind of break. This activities must follow seamlessly after each other. - Handlings-resourses are not supported by CTM. - For planned orders only goods reciept times are possible. Goods issue times does not exit. - This behavior is not valid for procurement orders.
( Changed at 15.11.2005 )
Product Interchangeability / Material Discontinuation in CTM
Since SCM 4.0 a limited material discontinuation with CTM is possible. This means that only 1:1 relation-ships can be modeled. Thus one product can be replaced by exact one other product in a certain period. Further more the standard use-up strategy can be used but also here certain limits exist. In other words the stock of the preceding product can be used up in the period defined for the interchangeability. For further details see the SCM 4.0 documentation at Multi Level Supply and Demand Matching - CTM # Product interchangeability in CTM. Please also consider following restrictions: -The interchangeability is only working outside the production horizon -Super-session beyond discontinuation is not considered. Discontinuation is defined by a 1:1 relationship and forward substitution -CTM does not support the reversed substitution direction, that also allows the substitution of a product with the predecessor product during a substitution relationship of category "Fully Exchangeable". -FFF-classes (Form-Fit-Function-classes) are not supported -Use-up limited by quantity is not considered. Further more a consequently, total use-up of a discontinued product cannot be assured. -The discontinuation in CTM is based on substitutions rules. -In CTM the order selection treads existing substitution orders like other order types. As a new feature, the production horizon is used as fixing horizon for substitution orders.
( Changed at 15.11.2005 )
Set-up activitiy / set-up Matrices in CTM
SYSTEM BEHAVIOUR BEFORE APO 40: Input components had to be assigned to the first activity, no scheduling of SET UP activity.( CTM deleted this activity from the dataset send to the CTM engine.) To assign all input components to the first activity (unequal SET UP ACTIVITY) the parameter COMP_REASSIGN had to be used. PROBLEM: Some input components were produced far too early this lead to high inventory cost in scenarios with long throughput times. SOLUTION: SINCE APO 40 the SET UP ACTIVITY will be scheduled and all INPUT COMPONENTS are planned according the start of the activity they belong to. ( No reassignment nescessary for input components) LIMITATION: * The output components still need be assigned to the last activity of a PPM using the parameter COMP_REASSIGN * CTM does not support SET UP MATRICES
( Changed at 15.11.2005 )
Maximum Pegging Length (Max earliness ) in CTM
The Max Pegging Length is used to restrict the time goods would be stored as inventory. This function is only working in backwards scheduling mode.
( Changed at 15.11.2005 )
Make to order process in CTM
Since SCM 4.0 CTM can also support Make to Order + This is only possible when using CTM time continous planning. .
( Changed at 15.11.2005 )
Forecasting w/o final assembly in CTM
Since SCM 4.0 CTM supports also forecasting without final assembly. The same restrictions which are vaild for for PP/DS are also valid for CTM. Additionally SNP has only display access to those planned orders. For displaying the order BAdi SAPAPO/SDP_INTERACT, Method: GET_KEYF_SPECIALS needs to be activated. In addition all restrictions for PP/DS are also valid for CTM * FCST w/o Final Ass. is only valid for the first level of the BOM * Safety Stock will be created only for the make-to-stock-segment * CTM supports FCST w/o Final Ass. only for inhouse production * Only demands in the make-to-stock-segment can consume stock.
( Changed at 15.11.2005 )
Production in another Location in CTM
SYSTEM BEHAVIOR In order to plan a product which has to be produced in location A while planning responsibility lies in the location B you have to main- tain the planning location in the PPM (PDS or IPPE) This will trigger an automated process: Planned order with receipt of the finished product in the planning location B and the issue of the components in producing location A. ENHANCEMENT: * No stock of the finished product in the production location Reduction of stock and throughput time. * No additional transportation lanes between production location and planning location nescessary. Less administrative effort. * This process is supported also in integrated scenarios R/3-APO LIMITATIONS: * This process is not meant to model subcontracting or distribution scenarions due to the simplified method. In subcontracting and transportation scenarios the transportation lanes and other transport relevant masterdata are essential to model the relations, quotas, transportation time and lotsizes, etc. * It is not possible with the new "Prod in another location scenario" to group the various demands to build lots for the production in the producing location.
( Changed at 15.11.2005 )
Switch off dynamic pegging in CTM
SYSTEM BEHAVIOR: You have the possibility now to switch off the by default activated DYNAMIC PEGGING. In the location Product master, tabstrip DEMAND. The system will not perform any dynamic pegging. POSSIBLE AREA OF APPLICATION: ++PROBLEM AREAS: * In some CTM scenarios the active Dynamic Pegging created irritating results. In case of fixed pegging all supplies outside the specified planning horizon have been pegged dynamic to demands outside the planning horizon instead of being available for demands inside. * In some CTM scenarios rounding blurrings lead to dynamic pegging lanes between very small quantities of demand and supplies. If those connections where crossing the planning horizon the solution tree for inside the planning horizon was fixed ( CTM logic). ++PLANNING APPRAOCH: * The CTM planning run should only show fixed pegging lanes. SOLUTION: With the new switch off possibility, you can prevent that the above described effects occur. The recomended set up would be fixed pegging with the effect only the demands and supplies within the planning horizon are involved. The dynamic pegging is a key function for some other applications. Those will be affected when the switch off has been activated.(Limitat) LIMITATIONS: + PP/DS Optimizer uses the pegging relations to calculate time delay or storage cost, without pegging information these analysis will not be carried out. + Some PP/DS Heuristics need pegging infomation in order to perform the detailed scheduling planning + Alert Display, the quantity alerts and the time alerts will be incorrrect due to missing pegging information. More detail please refer to the APO documentation PP/DS Basic functions/ pegging/ Switch off dynamic pegging.
( Changed at 15.11.2005 )
Lotzise Limitations in CTM
Periodic lot sizes and the reorder point method is not supported by CTM. All other methods: Lot for Lot, max./min. lotsize and rounding values are supported by CTM.
( Changed at 15.11.2005 )
Forward scheduling in CTM
If forward scheduling is used certain restrictions need to be taken into account: - The max.earliness is not working with forward scheduling Max Earliness = Max Pegging Length = MPL The MPL is one of two new functions available since SCM 4.0. It is used to restrict the time goods stored as inventory. This function is only working in backward scheduling mode. - All the different CTM late demand handling strategies are not working with forward sched. In case of late demand handling CTM stays in forward scheduling mode and tries to find a supply as early as possible. - Target days of Supply (TDS) is also not applicable with forward scheduling.
( Changed at 15.11.2005 )
Goods issue/receipt Dates/times in CTM
New System behaviour: Goods receipt and goods issue times will be taken into account during the scheduling. The system will regard the shipping and the receiving calendar for the involved locations LIMITATION: * The Goods receipt and Goods Issue times will only be applicable for external procurement process. No GR/GI times for inhouse production. * Handling Resources are not supported.
( Changed at 15.11.2005 )
Aggregated Planning with CTM
# Only 2 level product location hierarchies are supported by CTM # The aggregated planning function is only possible in case of SNP bucket planning scenario, i.e. only SNP PPMS/PDS hierarchy is considered as only the resource hierarchy for bucket resources is available at the moment. # Order types should also be of type SNP. In case of aggregated planning with hierarchy then the op-tion to use PPDS order types will be disabled # Aggregation step is always executed at run time and hence the aggregation results cannot be saved for later displaying i.e. physical aggregation of orders by CTM is not possible. Physical ag-gregation is possible with SNP interactive planning. # Interactive processes like changing, creating and deleting an aggregated order is not possible in CTM. It can be only performed with SNP interactive planning # Netting / planning with substitution orders is not possible as substitution orders are not integrated to R/3(AFS), though they can be used in case no integration of such orders is required. # The SNP disaggregation only works for SNP planned production orders and purchase requisitions. Substitution orders are not disaggregated. # Supply Distribution function does not recognize any hierarchy definitions # Same UOM should be maintained for both the header and sub product # The standard safety stock planning(default method) is not supported for hierarchy. Only the ex-tended method (using SSTOCK_MODE parameter) is supported. # MTO, Planning without final assembly , Subcontracting scenarios can be used for planning but they are as not supported for the standard disaggregation process Descriptive characteristics for sub products cannot be used
( Changed at 03.04.2009 )
CTM-Accessibility and connect ATP rules
The following restrictions apply: - Interchangeability Master data (INCMD) substitutions support 1:n-AND relations which is not supported by CTM these substitutions have to be deleted for CTM. - INCMD substitutions support n:1-AND relations which is not supported by CTM. In case of ATP rules with INCMD this is not a problem as the ATP does not support n:1-AND relations either. - INCMD substitutions support quantity factors which is not supported by CTM. - With INCMD substitutions ATP rules support lists of validity periods for a single substitution. These lists can contain gaps. CTM will not support these lists and will still read just one validity period specified in the existing ATP rules interface. - Today ATP rules support finding and evaluating more than one rule by specifying more than one inclusive rule. CTM only supports one inclusive rule. With the modifications for Service Parts Management the rule determination process will support more than one rule strategy, i.e. for each processed rule strategy one or more rules will be found/evaluated. CTM will only support one inclusive rule strategy and an arbitrary number of exclusive rule strategies. - Maximum number of substitutions and substitutions entity will not be supported by CTM. This specifies how many substitutions can be used for the confirmation. It can be specified whether the number of substitutions is valid for location or location products. - Consolidation location will not be supported by CTM. At the level of the ATP rule (//RBA02, fields CONS_LOCID, DIRSHIP, DELGRP_CORR) a location can be specified that will serve as a single point of confirmation. All applied substitutions will finally be represented by a transport order to the consolidation location from where the actual confirmation takes place. The consolidation location leads to new substitutions in the ATP rules interface, these substitutions have to be deleted for CTM. - Reassignment of confirmation will not be supported by CTM. Confirmed and allocated quantities can be reassigned in ATP, this is not relevant for CTM. - Only the current functionality of rules supported by CTM will be used from the ATP rules inter-changeability master data - New functions offered by interchangeability master data for ATP rules are NOT supported by CTM
( Changed at 15.11.2005 )
Demand split and contract info for CTM
Consideration of Contract Info when Creating Purchase Requisitions: Subcontracting is not supported. The supply chain viewer will not be enhanced. Demand Split for Quota Arrangement: Fractions required from the different sources are calculated from the quota arrangement, but are not adapted to lot size settings. Thus resulting supply may deviate from quota arrangement. Fractions supplied from the different sources may deviate also from quota arrangement in constraint situations when fallback strategy is applied. Demand split features like a minimum partial quantity or pooling of requirements are not supported. Disaggregation of transactional data: If the disaggregation should be able to disaggregate the value of each bucket always without any residual, the rounding values on item level have to be all the same within one group and the rounding value on group level has to be a multiple of this. Also the minimum lot size of the group level should be bigger or equal to the minimum lot size on item level. This is only a recommendation. Disaggregation works also without these restrictions. The disaggregation of subcontracting orders, scheduling agreements, VMI orders and planning results from deployment or TLB heuristic are not supported by the disaggregation functionality. Disaggregation of Resource Consumption: This new function is only available for production resources. The validity dates (from/to) of the sub-ppms and the validity dates (from/to) of the corresponding header-ppms have to be identical. Extraction of Aggregated Data It will not be possible to extract aggregated data from aggregates 9AACPR, 9ALA, 9AMALA, 9AMALASA, 9AMALOSA, and 9AMAPR. For resource-related aggregates, only the resource hierarchy will be considered.
( Changed at 15.11.2005 )
FFF classes: Integration and usage in CTM
The integration of FFF classes from ERP to APO is only possible, if DIMP functionality is activated in ERP. Standard ECC without DIMP functionality activated doesn#t contain any interchangeability master data. There will be no integration of substitution orders from APO to ERP. This is not a new limitation; the limitation exists since substitution orders were introduced with APO3.0.
( Changed at 15.11.2005 )
Parallelization in CTM
It is not possible to use rules in combination with parallelization. In CTM profile maintenance the corresponding setting will be excluded. Demand and supply simulation in CTM profile transaction is not supported. Demand and supply lists are available only with restrictions.
( Changed at 15.11.2005 )
Transport and Handling Resources in CTM
Resource Attributes: The transportation resource size is not considered. Time-continuous, calendar, and mixed resources must have 100% utilization and no unscheduled breaks. Goods Receipt for Production: Goods receipt for a specific production plan is only considered if all possible output products use the same handling resource. Only capacity consumption for main output is considered. Especially, production at another location with a handling resource at the planning location does not create a goods receipt activity in the following scenarios: - Co-products exist - Production version for production location exists Supply Chain Viewer The supply chain viewer (transaction /SAPAPO/CTMVIEWER) is not enhanced to display individual activities and resource consumptions for external procurement
( Changed at 15.11.2005 )
Release with approval of SAP or after consultation with SAP
SNP Propagation Planning
The SNP propagation planning (planning area SNP 9ASNP01, transaction /SAPAPO/SNPSOP) can only be used with times series live Cache. In productive systems, this functionality should be used only after consultation of SAP.
( Changed at 15.11.2005 )
Descriptive Characteristics
Manual changes for descriptive characteristics are not possible.
( Changed at 15.11.2005 )
Scheduling Agreements in SNP
Procurement scheduling agreements are supported by the SNP Heuristics but not by the SNP Optimiser. The calls from sales scheduling agreements are planning relevant but they are only displayed as a total and not for each individual customer.
( Changed at 15.11.2005 )
Subcontracting in SNP
Subcontracting in SNP is supported by both the SNP Heuristic and the SNP Optimiser. Capacity Leveling for subcontracting resources is not supported. Deployment and TLB of subcontracting orders (from the subcontractor to the receiving plant) are also not supported. The planned order at the subcontractor and the transport order from the subcontractor to the plant are not planned separately, i.e. there are only time lags due to the respective calendars. Therefore it is recommended for the SNP Optimiser that either the production capacity at the subcontractor or the transport capacity should be a constraint but not both. For subcontracting with third-party provision in SNP, for every subcontracting component that has to be sent directly from the supplier to the subcontractor, transportation lanes from the supplier (start location) to the subcontractor (destination location) have to be created manually. The associated external procurement relationship has to be assigned to the transportation lanes . If you want to use subcontracting with source location in SNP and PPMs are used, then for each subcontracting component that you want to send from the plant to to the subcontractor, you have to manually create a transportation lane from the plant (start location) to the subcontractor (destination location).
( Changed at 15.11.2005 )
Aggregated Supply Network Planning
Due to the nature of aggregated planning, some limitations regarding the consideration of item level constraints apply. The following restrictions apply: If the disaggregation should be able to disaggregate the value of each bucket always without any residual, the rounding values on item level have to be all the same within one group and the rounding value on group level has to be a multiple of this. Also the minimum lot size of the group level should be bigger or equal to the minimum lot size on item level. This is only a recommendation. Disaggregation works also without these restrictions. If replenishment for multiple levels (locations) of the supply chain should be planned via aggregated planning, the following conditions have to be met: - The same groups have to be defined in all locations - The disaggregation has to be executed in a specific order (beginning with the end of the supply chain where demand exists on the item level) in order to get disaggregation demand for all levels. - No cycles are allowed within the planned levels of the supply chain. The release of the planned production from SNP to PP/DS works on item level. No disaggregation will be done in the release step. If the resource consumption of fixed orders on item level should be considered properly, the following conditions regarding resources have to be met: - The same resources on item level as well as on group level have to be used. - Also the PPMs and lanes on item and group level have to be similar in terms of resource consumption. Otherwise the resource capacity on group level should be the sum of the different resource types of the item level. Also if multiple PPMs are used on item level, the resource consumption of the group level PPM should be the sum of the different PPM types of the item level. The PPMs on product group level cannot be generated automatically. Product dependent parameters (e.g. production/transport horizon) will considered only on the group level.
( Changed at 11.05.2007 )
Requirement Strategies and Forecast Consumption in SNP
SNP only supports strategy 10 (anonymous make-to-stock production) and 20 (planning with final assembly). Strategies 30 (planning without final assembly) and 40 (planning product) are not supported. SNP supports as PIR segment only the "Net Segment" that is used in strategy 10 and 20 in standard APO. This is valid for the SNP Heuristic and for the SNP Optimiser. Planned Independent Requirements (PIR) Segment: the quantities for make-to-order operations are in general planned separately to those for make-to-stock operations. These areas are known as PIR segments. In general you can only plan within a PIR segment. This means that you cannot consume planned independent requirements for a make-to-stockscenario. However a special segment to cover exactly this is offered, the PIR segment Planning without final assembly, without individual requirements. For more details, see the F1 help for the PIR Segment field in the requirements strategy. Supply Network Planning (SNP) cannot work with the individual customer segment. For example demand in this segment is not shown in SNP. Consequently you should not use requirements strategies that use this segment: in the standard system these are the strategies 30 and 40. However, by activating and using the BADI /SAPAPO/SDP_INTERACT (Interface GET_KEYF_SPECIALS) it is possible to display orders from the segment "Make-to-Order" and/or orders from the segment "Planning without final assembly". But it is only possible to display these orders, planning with strategy 30 or 40 is not possible!
( Changed at 15.11.2005 )
Shelf Life in SNP
Shelf life in SNP is not supported. Please check note 574321. For specific cases, the SNP Optimizer is able to consider shelf life, but the functionality is limited. Details can be found in note 579556.
( Changed at 15.11.2005 )
Interactive Order Maintenance in SNP
Mass copy and mass fixing/unfixing of orders in SNP interactive planning is only possible for planned production orders, not for planned stock transfer orders.
( Changed at 15.11.2005 )
SNP Release to DP: Using descriptive characteristics for stock elements
In the release from DP to SNP descriptive characteristics can be added to the forecast order which can be used to control the CTM planning run. Afterwards the constrained CTM result can be released back to DP by descriptive characteristics using the pegging between the forecast order and the planned receipts. For pegged stock elements the release to DP using the descriptive characteristics is not possible.
( Changed at 15.11.2005 )
SNP Master Data
Quota arrangement: By mass maintenance of quota arrangement, the means of transport can not be changed Time dependent penalty costs: By mass maintenance of time dependent penalty costs, the valid date can not be changed. The time horizons are absolute dates. Rolling horizons are not supported . Time series key figures: By mass maintenance of TS key figures, Values will not be extended further and must be maintained newly.
( Changed at 15.11.2005 )
AFS-SNP: Handling of the order group object in SNP
Order Group only supported by SNP Aggregated Planning: The order group is SNP specific and not generic. This implicates that only SNP Aggregated Planning does use order group data and functions. Other functions in APO (e.g. PPDS Product View) are not be able to display order group information or to select orders based on group information or to apply any group related functionality. Deployment: SNP Deployment does not support grouped orders since deployment does notsupport Aggregated Planning. As a result a deployment run does not reuse the group information of the processed SNP planned stock transfer orders. Deployment does also not attach group information to the createddeployment-confirmed stock transfer orders. TLB: Following the argumentation as for deployment also SNP TLB does not support grouped orders. VMI: The VMI process, especially the creation of sales orders in R/3, does not support the order group. Within the global AFS project the VMI process is modeled in ICH (Inventory Collaboration Hub). Intransit orders created in SNP: Manually created Intransit orders in SNP interactive planning will not have any order group information. Forecasts created in SNP: Manually created Forecast orders in SNP interactive planning will not have any order group information. Interchangebility: Since Substitution orders are not supported in the disaggregation, ordergroups are not supported for Sub-stitution orders. Scheduling Agreements: Since Scheduling Agreement orders are not supported in the disaggregation, order groups are not sup-ported for Scheduling Agreements. Subcontracting: Subcontracting orders will not be disaggregated or physically aggregated Release from SNP to DP: The release from SNP to DP do not use the group information and does notutilize the location product hierarchy for transferring SNP order data to DP key figures. Extended Release from DP to SNP: The extended release from DP to SNP can create SNP planned production orders, SNP purchase requisitions and SNP planned stock transfer orders. These orders do not have any group information when they are created by the extended release. BAPIs for creating/reading orders: BAPIs do not support the order group in SCM 5.0 means the existing orderBAPIs for orders are not able to create or retrieve order group information.
( Changed at 15.11.2005 )
AFS-SNP: Aggregation settings for Safety Stock Planning
Safety Stock Planning Time-dependent parameters of standard safety stock methods MB, MZ, and MM have to be stored in time series liveCache key figures to allow method parameter aggregation. There will be no inheritance logic "product hierarchy ? location product hierarchy" for aggregation settings (method parameter aggregation, historical data aggregation), i.e., aggregation settings will always be read from location product hierarchy. There will be no mass maintenance for aggregation settings. There will be no disaggregation functionality for safety stock values. Capacity Leveling In Aggregated Planning only production resources will be supported. When determining PPM/PDS to shift orders to the header level lot size restrictions will not be considered. When leveling a header resource it will not be allowed to specify its sub resources as alternative resources.
( Changed at 15.11.2005 )
AFS-SNP: Capacity View for Aggregated Resources
Capacity View for Aggregated Resources The key figure #production (planned)# is editable in the grid and in the detail view. The key figure #aggregated production (plnd)# in the grid is not editable. The detailed screen for that key figure is also not editable.
( Changed at 15.11.2005 )
AFS-SNP: Aggregated Planning with SNP Optimizer
SNP Optimizer When Optimizer runs on the header level, the setup statuses of the sub resources cannot be considered by cross-period lot size planning. Usage of aggregated Sources Of Supply This scenario is only valid for In-House Production, e.g. the disaggregation is only available for production resources. Further on the SNP Heuristic will use aggregated sources of supply only for In-House Production.
( Changed at 15.11.2005 )
AFS-SNP: Master data integration (means of transport)
Master data: Over the CIF it will be only delivered the transportation lane header and header product / SKU specific transportation lanes. A transportation lane is only valid, if it contains at least one means of transportation. Means of transportation cannot be delivered from a R/3 in a standard way; therefore the transferred lanes are not consistent. The missing means of transportation has to be maintained manually or over appropriate BADI. The product hierarchy may have only 2 levels (parent and child level).
( Changed at 15.11.2005 )
Scheduling of orders
The scheduling of orders in APO or the integration of orders to R3 can be different: - Optimizer will always use Forward Scheduling instead of Backward Scheduling like in the Data Management Layer. Therefore we will get deviations regarding the start date of activities. - There is only a harmonization between SNP and CTM. Regarding the Scheduling of activities no breaks between activities are allowed, which can be maintained by the customer in CTM. - In contrast to CTM or PPDS, the Optimizer will use the calendar of calendar-resource for scheduling activities except for Goods Receipt activities. - In R/3 we have only one calendar, the factory calendar, to schedule the GR Activity. In APO this is the production calendar.
( Changed at 15.11.2005 )
TLB & Deployment Heuristic: use of reservation quantities
It is only possible to use the functionality with planning areas, which contains the timeseries keyfigure for display of reservation quantities. The functionality is only available as part of realtime-deployment with the option 'Replan all existing Deployment Stock transfer orders'. Because it is necessary to carry out reading and deletion of deployment STOs and to start a restricted SNP location heuristic for all destination location products (in addition to the 'normally' deployment steps) it is possible, that a large selection leads to a decrease of performance. This has to be considered using the functionality and during planning of massprocessing Jobs.
( Changed at 15.11.2005 )
Direct Shipment (DS) functionality
The DS functionality is relevant for a small range of products. The activation, means maintenance at the transportation lane, is product specific. This has to be done to ensure that only relevant products will be in the scope of the customer. The Direct Shipment functionality will not consider quotations. The new functionality will use the TLB but will not create TLB orders. When calling the TLB in the Direct Shipment mode the following option will be deactivated: - Priorization of demands. - Calculation of ATD quantities. The Direct Shipment functionality will only be introduced to the SNP-Heuristic. There is no relevance for the Deployment run because here the DS-Lane can be prioritized, using fair share rules. The consideration of Resource Calendars is only relevant for the In-House Production scenario.
( Changed at 15.11.2005 )
Capacity Leveling: consideration of resources, PPMs/PDS and lot sizes
SNP Capacity Leveling takes production and transportation resources into account. In Release SCM 5.0 only alternative production resources will be considered. It means, only production orders will be able to be moved to other PPM/PDS. By heuristic method the leveling resource and alternative resources cannot be consumed in one PDS/PPM. Otherwise it may generate overloads in a circle, because heuristic method considers resources only locally. Additionally, if more than one PDS/PPM is defined for the same location product and consumes the same alternative resource, heuristic method will consider only the PDS/PPM with the highest priority. The other PDS/PPMs will be ignored. Neither the maximal nor the minimal lot size of PDS/PPMs is considered by heuristic method to create new orders. By optimizer method they are interpreted as maximal and minimal production quantity on one day.
( Changed at 15.11.2005 )
Parallelization of SNP Applications
For the on-line complete or delta SNP master data initialization by transaction /SAPAPO/MSDP_ADMIN, report /SAPAPO/TS_PAREA_INITIALIZE or report /SAPAPO/TS_LCM_CONS_CHECK or activated by an SNP transaction a parallelization will not be possible. This is because - a parallelization profile cannot be specified in the case of delta master data initialization triggered by an SNP application - the master process in on-line mode is a dialogue process which undergoes a run time re-striction, thus it is likely that the whole initialization fails because there is insufficient time available for the master process - for DP parallel processing in online mode is not possible. To ensure a common handling of the master data initialization for SNP and DP, we will not support parallel processing in online mode. The consistency check report /SAPAPO/TS_LCM_CONS_CHECK cannot find obsolete master data when parallel processing is chosen. To check for obsolete master data a sequential run must be executed. The master data situation that causes errors is in most cases missing master data.
( Changed at 15.11.2005 )
Consideration of GR times for PPM/PDS-validity
The consideration of GR times for PPM/PDS-validity is different between different applications and R/3: - Optimizer will always use Forward Scheduling instead of Backward Scheduling like in the DM Layer. Therefore we will get deviations regarding the start date of activities. - There is only a harmonization between SNP and CTM. Regarding the Scheduling of activities no breaks between activities are allowed, which can be maintained by the customer in CTM. - In contrast to CTM or PPDS the Optimizer will use the calendar of calendar-resource for schedul-ing activities except for Goods Receipt activities. - In R/3 we have only one calendar, the factory calendar, to schedule the GR Activity. In APO this is the production calendar.
( Changed at 15.11.2005 )
AFS-SNP: Aggregation and Disaggregation
Single-level Allocation of Receipt and Issue on Sublevel (SKU-Netting): Stock transfer order created by Single-level Allocation of Receipt and Issue on Sublevel will NOT be grouped across different sub location products according to the locations product hierarchy since the header level information for grouping is not available on sub level. For a location product only the location products with are direct external procurement sources are consid-ered to allocate existing receipts (single level). Subsequent sourcing through the network to find and allo-cate existing receipts (multi level) is NOT supported by this function. The allocation is only done for receipts which can be utilized by external procurement. Allocation via in-house production is NOT supported. Disaggregation of transactional data: If the disaggregation should be able to disaggregate the value of each bucket always without any residual, the rounding values on item level have to be all the same within one group and the rounding value on group level has to be a multiple of this. Also the minimum lot size of the group level should be bigger or equal to the minimum lot size on item level. This is only a recommendation. Disaggregation works also without these restrictions. The disaggregation of subcontracting orders, scheduling agreements, VMI orders and planning results from deployment or TLB heuristic are not supported by the disaggregation functionality. Enhancements for Disaggregation of Resource Consumption This new function is only available for production resources. The validity dates (from/to) of the sub-ppms and the validity dates (from/to) of the corresponding header-ppms have to be identical. Extraction of Aggregated Data It will not be possible to extract aggregated data from aggregates 9AACPR, 9ALA, 9AMALA, 9AMALASA, 9AMALOSA, and 9AMAPR. For resource-related aggregates, only the resource hierarchy will be considered. Interchangeability cannot be used together with aggregated planning in SNP: the SNP disaggregation only works for SNP planned production orders and purchase requisitions. Substitution orders are not disaggregated.
( Changed at 03.04.2009 )
Stock Transport Order in purchasing applications
This functionality will only be available for purchasing applications that use the business logic of the #new# Purchasing Order (PO) transactions, i. e. # only for stock transport orders (STO), not for stock transport purchase requisitions, not for stock transport scheduling agreements; # only for the #new# purchasing transactions ME21N ff; # only for the #new# mass transaction for automatic creation of purchase orders from requisitions ME59N. The only exception is STO items created from SCM via CIF, because CIF still uses the coding of the #old# PO. Also in this case we would use the new functionality if customizing is set accordingly. If the new functionality is switched on, we could get different results from ATP check depending on the use of the #old# transaction ME22 or the #new# transaction ME22N. Therefore we cannot allow the processing of STOs created with transactions ME21N/ME59N with transaction ME22. Further restriction: As now in purchasing standard, schedule lines will only be created and changed on daily, not on secondly basis.
( Changed at 15.11.2005 )
Stock Transport Order and product interchangeability
The functionality of product interchangeability in Stock Transport Orders (STO)s will not support - purchasing requisitions and scheduling agreements; - old purchase transaction e.g. ME21; - rescheduling in ERP, therefore in fall-back case no rescheduling is possible. It will be only available as part of the defense solution, i. e. for customers with Enterprise Add On for Defense Forces and Public Security (EA-DFPS) switched on. The fallback scenario is only available for defense customers who use an ERP system with DIMP switched on. No manual changes of sub items with exchange material are possible. Therefore the handling in case of inconsistencies between confirmed quantity in STO/delivery and real quantity in warehouse at time of goods issue can only be resolved as follows: - Either deletion and recreation of STO and delivery; or - post goods issue with #real# quantity (reduce delivered quantity), post goods receipt and set delivery complete indicator, correct situation in warehouse, create new STO item.
( Changed at 15.11.2005 )
Excel-Upload in Demand Planning
The solution works only within SCM Demand Planning. Supply Network Planning is not supported.
( Changed at 15.11.2005 )
Auxiliary Key Figures in SNP Planning Areas
Auxiliary key figures cannot be created anymore in APO releases > 3.1. However, if you have done an upgrade from a previous APO release, then you can still use the auxiliary key figures which you have created in previous APO releases < 4.0, but you cannot add any new ones.
( Changed at 15.11.2005 )
Navigation Attributes Can Not be Used in SNP
Navigation attributes cannot be used in SNP. For a detailed explanation, please check note 453644.
( Changed at 15.11.2005 )
All SNP applications do not consider the fixed material consumption in PPM plan
All SNP applications do not consider the fixed material consumption in PPM plan.
( Changed at 15.11.2005 )
Release with restrictions
Sourcing of Forecast Process: only working for one-level-supply chain
Sourcing will only work for the customer locations and source location layer connected to the customer locations (one level of the supply chain). The customer locations and transportation lanes (with active flag "relevant for sourcing of forecast process") between source and customer locations have to be maintained as APO master date.
( Changed at 15.11.2005 )
Sourcing of Forecast Process: Manual changes limited
Manual changes of the sourcing decision or manual sourcing will only be possible for the possible changes of transactional data that exist in SCM 5.0. There is no additional functionality within the sourcing of forecast process. For instance, the sourced forecasts can be changed in the product view (ta: sapapo/rrp3), but this is not reflected and will not update the corresponding allocations (ta: ac42). You have to change these allocations then manually, too.
( Changed at 15.11.2005 )
Sourcing of Forecast Process: Fixing of sourcing decisions not possible
Automatic or manual fixing of sourcing decisions or parts of the sourcing decision at the source locations is not possible, except for the possible fixing mechanisms that exist in SCM 5.0; in particular, the sourced forecasts cannot be fixed.
( Changed at 15.11.2005 )
Sourcing of Forecast Process cannot be started from the SNP planning board
Sourcing of Forecast Process cannot be started from the SNP planning board. It can only be started in the background with ta sapapo/snpsrc.
( Changed at 15.11.2005 )
Sourcing of Forecast Process: hierarchical view of allocation situation is not possible
A hierarchical view of the allocation situation is not possible, because of the standard functionality of allocations. The allocation situation can only be viewed for one characteristic combination at a time (ta /sapapo/ac42).
( Changed at 15.11.2005 )
Sourcing of Forecast Process is independent of the VMI process
Sourcing is independent of the VMI process and does not interact with it . For a customer location product only VMI or Sourcing is possible, but not both processes to the same time. If the flag "relevant for sourcing" is set at the transportation lane, then the customer location product is relevant for the sourcing of forecast process, otherwise it is relevant for the VMI process.
( Changed at 15.11.2005 )
Sourcing of Forecast Process is only suppported by the SNP Optimizer
The SNP optimizer is the only tool supporting the SOF process. All other applications like e.g. CTM or SNP heuristics do not support this process.
( Changed at 15.11.2005 )
Sourcing of Forecast Process: transportation lot sizes and capacities not supported
It is not allowed to use transport lot sizes or rounding values for the sourcing process at the lanes between the sources and the customer. Additonally, transportation capacities are not supported, too.
( Changed at 15.11.2005 )
Sourcing of Forecast Process: different scheduling in SNP optimizer and ATP
The scheduling for determining the material availability date/delivery date of the sales orders during an ATP check and the SNP optimizer considering the transportation lane is different. This can lead to shifts in buckets for the forecast orders at the sources (plants) created by the sourcing process.
( Changed at 15.11.2005 )
Sourcing of Forecast Process can only be performed in the active version.
The sourcing scenario can only be performed in the active version (#000#).
( Changed at 15.11.2005 )
Sourcing of Forecast Process: definition of DP planning area; mapping of DP and SNP planning area
The DP planning area has to have the following 4 characteristics: allocation group, product, plant and customer. In the mapping of the DP to the SNP planning area you have to defined the final DP key figure which represents the forecast that should be sourced.
( Changed at 15.11.2005 )
Sourcing of forecast process: customer consignment and sourcing are not supported simultaneously
Customer consignment: Consignment stock can be held in R/3 and might be transferred via CIF into APO in the case that a customer location is modelled in APO. If a customer location is not modelled in APO, customer stock data is not visible in APO. Customer consignment and sourcing will not be supported simultaneously. The reason is that customer consignment stock could be tracked in APO at the customer location. That would affect the sourcing process what is not intended. Basis of the sourcing process is that there is no transactional data at the customer location.
( Changed at 15.11.2005 )
Sourcing of Forecast Process: no hierarchical consumption
There will be no hierarchical consumption. Consumption for descriptive characteristics is only available for each characteristic combination and for the default value. All forecasts that are not included in the sourcing have to be released using the default value. If you have, for instance, the descriptive characteristics product and sold-to-party for sales orders, the forecast must have the same characteristics. Otherwise, no consumption will take place. The default value can be maintained in consumption group maintenance (ta : /SAPAPO/CSP1) for a characteristic. The idea is to have only specific instances of a characteristic (such as customer) where there are values for in a characteristic combination in DP. All other values will be summarized with the same charateristic value (e.g. 10 specific customers with specific descriptive characteristic values, and 100 unspecific ones that are summarized by one characteristic value).The value used for summarizing is the default value. Although there is no hierarchical functionality on descriptive characteristics, with the default value at least there can be an unspecific group of characteristic value instances , its some kind of very basic work-around for the missing hierarchy functionality. The default value is used in case a characteristic combination with the requested value is not available in DP (it substitutes the requested value).
( Changed at 15.11.2005 )
Release with restrictions
Interchangeability cannot be used in Deployment/TLB
Deployment/TLB do not support interchangeability. Since Deployment/TLB is usually used in the very short-term horizon, this might probably not be a real problem in most scenarios.
( Changed at 15.11.2005 )
Release with restrictions
Interchangeability: SNP substitutions orders not transferred to R/3
SNP product substitution orders that are generated and linked to SNP planned orders are not transferred to R/3. Product substitutions for distribution demands can also not transferred to the R/3 system. If you want to transfer substitution orders to R/3, you have to use PP/DS functionality.
( Changed at 15.11.2005 )
Interchangeability: SNP Heuristics - INC only supported with location heuristic
If you want to use heuristics in SNP, only the location heuristic support the interchangeability functionality. Interchangeability cannot be used in connection with network or multi- level heuristic. However, in transaction //SNP01 you can maintain the location heuristic in the way that its behaviour corresponds to the network or multi-level heuristic.
( Changed at 15.11.2005 )
Interchangeability: SNP substitutions orders not transferred to R/3
SNP product substitution orders that are generated and linked to SNP planned orders are not transferred to R/3. Product substitutions for distribution demands can also not transferred to the R/3 system. If you want to transfer substitution orders to R/3, you have to use PP/DS functionality.
( Changed at 15.11.2005 )
Release with restrictions
Advanced Safety Stock Planning Methods
The Advanced Safety Stock Planning Methods (AT, AS, BT, BS) should only be used, if the following conditions apply: Backorder Case: Shortfall quantities are delivered when available (by subsequent delivery), i.e. no demand will ever get lost. No-Delay Approach: Shortfall quantities that can not be covered by safety stock will be procured by alternative means of the planner (e.g. express delivery). If these conditions do not apply, the methods can be used, but the resulting safety stock will be (much) too high/low.
( Changed at 22.02.2008 )
Release with restrictions
Supersession
In APO-SPP of SCM 5.0 only 1:1, 1:N and M:1 supersession relationships are supported, N:M is not supported. In SCM 5.0 FFF classes are also not supported.
( Changed at 06.12.2005 )
MRP areas
Within APO-SPP MRP areas are only used to model contract packagers. A usage of MRP areas for other purposes is not intended and not possible.
( Changed at 06.12.2005 )
Simultaneuos usage of SCM-APO-SPP and core SCM-APO planning functionality
It is not intended to use (simulataneously) APO-SPP-DRP and APO-SNP or APO-SPP-Deployment and APO-Deployment respectively for the same part/location combination. A simultaneous usage of both will lead - due to different logic of planning philosophies and algorithms - to inconsistent planning results.
( Changed at 02.02.2006 )
TLB and VMI processe of core APO planning functionality
For planning of service parts the Transport Load Builder is not supported. This is true as well for related VMI-scenarios.
( Changed at 06.12.2005 )
Macros
In contrast to SCM-APO-DP / - SNP there is no macro functionality available
( Changed at 06.12.2005 )
Key Figures
In contrast to SCM-APO-DP / -SNP, key figures and their processing logic are predefined and can not be changed
( Changed at 06.12.2005 )
Alert Monitor
Alert Monitor is not residing in APO, but as part of the overall shortage analysis within ICH. ICH is the focal point for the planner to evaluate the planning situation
( Changed at 06.12.2005 )
Procurement Relationships / Transportation Lanes
Within SCM-APO-SPP only Scheduling agreements and contracts, which are flagged "externally planned" in ERP are supported
( Changed at 06.12.2005 )
Subcontracting
In the current SPP solution planning of subcontracting is not supported
( Changed at 06.12.2005 )
Kitting
In the current SPM solution a Kit-to-order process is supported across several solution components. From a planning perspective supply of the kit components is planned. However, within SPP there is no planning functionality to create a planned order for a kit-to-stock scenario
( Changed at 06.12.2005 )
Capacity Constraints
In the SPP solution there is no capacity planning functionality (i.e. handling, warehouse, transportation). The only exception is the process of remanufacturing, where in DRP capacity constraints communicated from supplier are taken into account in DRP planning
( Changed at 06.12.2005 )
Solution Component Architecture
General requirements regarding system landscape components and their release versions for utilization of full capabilities of Service Parts Management functionality are listed in Release Note 821101. For the utiliziation of Service Parts Planning functionality within SCM-APO-SPP those prerequisites regarding system landscape are valid as well for those components, which are directly interfacing with SCM-APO-SPP: * SAP Enterprise Core Component 6.0 (SAP ECC) * SAP Customer Relationship Management 5.0 (SAP CRM) * SAP Supply Chain Management 5.0 (SAP SCM) --> Service Parts Planning (SPP) in SAP Advanced Planning and Optimization (SAP APO) --> SAP Inventory Collaboration Hub (SAP ICH) * SAP Enterprise Portal 6.0 (SAP EP) * SAP Business Information Warehouse BI Content 7.0.2 (SAP BW) The feasibility of utilization of different solution components and release versions is subject to a customer-specific analysis and especially the potentially required integration work subject to a customer-specific implementation.
( Changed at 02.02.2006 )
Forecasting on part location-level
In SCM-APO-SPP the forecast is always and exclusively based on the combination of part and location. In contrast to APO-DP it is for example not paossible to flexibly generate a forecast on an aggregated level, i.e. product group level, and subsequently to disgaggregate this forecast on part location level. However, within SCM 5.0 APO-SPP-Forecasting and APO-DP are integrated on a data layer. This means, that key figures from APO-SPP can be read from APO-DP and Forecast results (key figures) generated/ changed in APO-DP may be copied back to APO-SPP. This integration possibility would have to be used, if scenarios are supposed to be used, which generate forecasts on an other tha part / location level.
( Changed at 02.02.2006 )
Integration SPP - APO-DP
In an integrated scenario, where SPP is used for forecasting on part / location level and DP for i.e. (interactive) forecasting an additional aggregated levels, separate planning object structures and Infocubes have to be used and modelled. In the standard solution realignment in SPP for example does not automatically lead to a realignment of corresponding data in APO-DP. Realignment in APO-DP does also not automatically lead to a realignment of corresponding data in SPP. For this a customer-specific solution has to be implemented, ensuring that relevant realignments executed in SPP are consistently reflected in APO-DP.
( Changed at 02.02.2006 )
Demand based on sales orders (customer orders) only
The current SPP process of capture demand only extracts and manages demand history, which is related to sales orders. Demand coming from service orders or other sources may be extracted into APO-BW, however - currently there is no predefined functionality to handle demand from other objects than sales orders. Furthermore in SC-APO-SPP 5.0 forecasting is exclusively based on demand . Forecasting on basis o installed base information and leading indicators is not part of the solution.
( Changed at 02.02.2006 )
Integration SPP - APO-PP/DS
Integration is not tested and not intended. Please note, that especially the use of the product view for interactive processing is not supported . Furthermore the SPP is not able to create / handle planned (manufacturing) orders as well as dependent requirements resulting from BoM explosion.
( Changed at 02.02.2006 )
Release with restrictions
Scheduling of receipt elements in APO-SPP and ERP
Depending on Customizing scheduling in APO-SPP and in ERP 2005 may not lead to the same, consistent results.
( Changed at 06.12.2005 )
Shelf life
Shelf life is not supported In SCM-APO-SPP
( Changed at 06.12.2005 )
Characteristics-based planning, variant products and descriptive characteristics
Characteristics-based planning, variant configuration and descriptive characteristics are not supported within APO SPP in SCM 5.0
( Changed at 06.12.2005 )
Release with restrictions
Consumption of forecast by customer orders
Within APO-SPP there is no option of consuming forecast by effective customer orders. Supply planning is solely driven by actual forecast figures and potentially additional demand types as fixed requirements.
( Changed at 06.12.2005 )
Release with restrictions
Carrier Selection - Continuous move
The information of continous move shipments is not displayed in all releases, please check documentation for more detail. For continous move shipments, the round trips are restricted to two shipments.
( Changed at 26.10.2005 )
TP/VS Order Split - Maximum break for loading/unloading
Maximum breaks for loading/unloading may not be always correctly respected by optimizer in case of deconsolidation to freight units of package size.
( Changed at 26.10.2005 )
Carrier Selection - Businee share
The business share (within carrier selection) applies only to shipments that are taken into account by optimizer.
( Changed at 26.10.2005 )
TP/VS Order Split
TPVS SCM 5.0 Order split functionality will be restricted to following order types: sales order, purchase order, stock transfer order, VMI sales order, outbound delivery (outbound delivery - only for R/3 releases 4.7 and later). Important characteristic of TPVS order split is that no schedule lines are generated per splitted freight units/deliveries. Therefore, if APO gATP has to determine MAD date using TPVS planning results, it may use only one of possible several TPVS shipment dates (in particular the earliest good#s issue date for MAD determination). It is not possible to combine items which belong to different orders into one freight unit.It may only be done using ship_with functionality. It is only possible to create up to 9999 split freight units for one order. Applying splitting rules before optimization may lead to increasing complexity of optimization problem. Therefore package size should be set as large as possible in particular shipping process. If freight unit requested delivery dates are changed in transaction /sapapo/vssp, corresponding order dates are not changed in OLTP system. Freight unit quantities can be manually increased to values, which in total exceed original order quantities (overdelivery). In this case delivery(ies) can only be created with these quantities, if overdelivery doesn't exceed tolerance specified in sales order (or unlimited tolerance indicator is set). Otherwise deliveries are created for available quantities only. If quantity costs (LTL costs) are used based on transportation lanes, it is required, that all cost units of measure for all lanes for the same Means of Transport have the same Dimension. Control rules: if deliveries are created manually in OLTP for order planned in TPVS which was splitted into several freight units, adjustment of shipments is not performed, in particular, deliveries do not replace corresponding freight units in shipments. It is recommended always to create deliveries in OLTP from TPVS, if sales orders are being planned on TPVS shipments. The usage of characteristics information is limited to SD-objects (Sales Orders and Deliveries). The usage of shipping points is limited to SD-objects (Sales Orders and Deliveries). The usage of one-time addresses is limited to SD-objects (Sales Orders and Deliveries).
( Changed at 26.10.2005 )
Using of deliveries with multiple pick-up locations
If delieveries are transferred from SAP R/3 side to SAP APO, the delivery must not contain more than one pick-up location. As deliveries are consolidated for transportation planning, only one location can be taken into account. In case multiple locations are assigned (e.g. for items produced in different plants), the first location will be taken into account.
( Changed at 26.10.2005 )
Dynamic Route Determination (DRD) from the ERP system
Dynamic route determination is called in the global availability check (only) when a sales document from the ERP system (R/3 system as of Release 4.6C) is processed. (This function is not available for deliveries or CRM documents.) For further information about the documentation and restrictions regarding this topic check note 307611.
( Changed at 02.02.2006 )
CMDS and SAP TP/VS
Collaborative Management of Scheduling Agreement Releases (CMDS) does not work in combination with SAP TP/VS.
( Changed at 26.10.2005 )
Release with restrictions
Integration of SAP R/3 with TP/VS
The handling of shipments between SAP APO and SAP R/3 must be known to create a smooth handling of the planning process. Please see note 448487 for details. SAP TP/VS Integration with SAP R/3 4.6B : Please contact SAP TP/VS Development. SAP TP/VS Integration with SAP R/3 below 4.6B : not supported.
( Changed at 26.10.2005 )
Planning of returns
Please take care of the following restrictions applying to the use of returns: SAP R/3 side: No Meaningful Scheduling with Returns and Returns Deliveries No Returns Items in Standard Orders and Outbound Deliveries No Returns Items for External Plants (SAP R/3 4.7) Returns with Special Stocks (see note 445241) No Normal Items in Returns SAP APO side: No Updating of Returns No Updating of Returns Deliveries No Requirements Planning for Planned Receipts from Returns No product allocation
( Changed at 26.10.2005 )
Integration of multiple R/3 Systems with SAP TP/VS
The following scenario is not supported by SAP TP/VS 5.0: Integration of two or more SAP R/3 Systems with SAP TP/VS in order to plan and create planned shipments with mixed shipment stages of both SAP R/3 systems. The split of the shipments and update from SAP R/3 in case of changes is not supported. Reason: the transportation object on SAP APO side does have a complete different data structure with regard to the transportation object on SAP R/3 side.
( Changed at 26.10.2005 )
Release with restrictions
User Exit at carrier assignment
Currently no User Exit in the area of function module call /SAPAPO/VS_SHIPMENT_PUBLISH (as in transaction /SAPAPO/VS511 is available. This means no enhancements regarding the standard process: "publishing shipments to a carrier" may be performed (E.g. for preventing shipments to be published without a carrier assigned).
( Changed at 26.10.2005 )
Release with restrictions
SAP TP/VS Optimization Volume
Depending on the volume of data used within one optimization performance or memory problems could occur. Please clarify the following data: orders inside optimization horizon: Dimensions Transportation groups Involved locations (including hubs) Involved hubs Means of transport Available vehicles Average Number of breaks per vehicle Schedule-based means of transport Average Number of stops per schedule based means of transport Available schedule vehicles Opening time resources Average number of open intervals per opening time resource Loading resources Average number of breaks per loading resource Please use TP/VS Optimizer Sheet on the Service Marketplace (SCM Technology area). If degree of complexity is high, please contact Development via an OSS message component SCM-APO-OPT-VS.
( Changed at 31.10.2005 )
Use of schedules
Still some restrictions apply for the use of schedules for SAP APO as part of SCM 5.0. Please see note 483297 for details.
( Changed at 26.10.2005 )
Release with restrictions
Document Flow
Document Flow creation for EM works only if you have an asynchronous connection between the Application system and Event Management.
( Changed at 21.11.2005 )
SCEM WCL 5.0
SCEM WCL 5.0 SP1 has been delivered with SAP J2EE 7.0 SP4. JNET, which is part of the SAP J2EE Engine, can not work properly in the headless mode. In the standard delivery the parameter -Djava.awt.headless=true had been set. This parameter has to be removed. Please follow the note 919820 to get more Information, how you can remove this parameter.
( Changed at 21.02.2006 )
Release restrictions: visibility processes
Regarding the release restrictions for the visibility processes, please check note 677373.
( Changed at 21.11.2005 )
Integration of SAP EM & Document Flow (DF) - Performance
Integration DF # for performance considerations, not recommended for Handling Unit.
( Changed at 21.11.2005 )
WCL
Multiple parameter inputs is not valid for fast entry screen in WCL. Index Values Parameter is not applicable for Value Sets: All Value Sets will be shown one after another (without more link). It is not possible to assign the field "Number of Indexed Values" into the Value Sets.
( Changed at 13.10.2006 )
Integration of SAP EM & Document Flow (DF)
DF node can only be deleted by sending an explicit event message and trigger an activity to do that. The deletion of event handler won't delete the DF node automatically.
( Changed at 21.11.2005 )
Release with restrictions
Multiple currency handling not supported for F&R
Business Background Retail companies have typically different currencies they are dealing with: Depending on vendors they know many different currencies for products they buy (e.g. overseas procurement) Typically purchase prices, scales, restrictions and resulting purchase orders and invoices are negotiated and created in the vendor#s currency This is also common for national retailers Purchase conditions can depend on vendor (supplying location) , receiving location and product (and many other criteria#) Depending on the sales markets/distribution chains retailers operate, there are different sales prices for location products Resulting Problems Usability A user cannot maintain or see currency related fields as they exist in reality, e.g. a vendor minimum order value in the vendors currency HKD will be converted in EUR. Conversion discrepancies As data will be converted during inbound processing if the currency is different than the client currency and a currency conversion may take place at different points in time, different underlying conversion rates will be used. This can lead to less data accuracy.
( Changed at 15.11.2005 )
APO and F&R cannot be run in the same client
APO and F&R cannot be run in the same client, because F&R allows empty target locations in lanes
( Changed at 15.11.2005 )
BI release
The lowest release BI release that can be used for F&R 5.0 = BI content 3.52 / 3.53 (Refer to note 731215).
( Changed at 15.11.2005 )
Missing moving average cost (MAC)
MAC = Moving Average Cost is used in our F&R Analytics BI Content to evaluate several KPIs at moving average cost. Currently the MAC is not provided by the BI Content 7.0.2 or any lower releases. History: The MAC was planned to be delivered by Standard BW Content, as part of the attributes of 0MATPLANT. The plan changed, no MAC information was delivered as part of the Standard BW Content. List of object that are affected by the missing moving average cost (MAC) in our F&R analytics BI content: - InfoCube 0FRE_C05 (F&R Weekly figures) update rules for the key figure Weekly Average Stock Cost - InfoCube 0FRE_C10 (Dead Stock) update rule for the key figure Stock Cost (at moving average) - InfoCube 0FRE_C04 (Stock Exceptions # Overstocks) update rule for the key figure Overstock Cost - InfoCube 0FRE_C02 (Stock Exceptions - Stockouts & Lost Sales) update rule for the key figure Lost Consumption Cost - InfoCube 0FRE_C03 (Stock Exceptions - Stockouts & Undelivered Product) update rule for the key figure Lost Consumption Cost - InfoCube 0FRE_C01 (Stock Exceptions-Understocks) update rule for the key figure Understock Cost We also use these attributes (i.e. Moving Average cost attributes of InfoObject 0MAT_PLANT) in our Gross Margin Return on Investment report, here we use the POS InfoCube 0RPA_C02 (Store/Article/Week) and the key figure Cost in Cost Value (0RPA_CST, which is at moving average) to calculate (through calculated key figures) several other F&R key figures like: Weekly consumption at cost Weekly average stock at cost Gross margin percentage and GMROI (Gross margin return on investment)
( Changed at 15.11.2005 )
Release with restrictions
Integration
Connection between R/3 / ERP and SCM is restricted to R/3 / ERP Retail (4.6C up to ERP 2004). Refer to SAP Note 157755. In ECC 6.0 (ERP 2005) the Enterprise Extention: EA-Retail as well as the Business Function Set SAP Retail have to be activated. Alternatively both settings can be activated with the function SFW5.
( Changed at 15.11.2005 )
Release with restrictions
Supplier Collaboration: Some products cannot be ordered from diff. suppliers in diff. processes
A material that is obtained from a supplier as part of a scheduling agreement release procedure cannot be obtained in ERP from another supplier within an SMI scenario. This also applies to all procurement combinations where a supplier orders the material on the basis of the net demand calculation (for example, forecast delivery schedules or purchase orders) at the same time as another supplier obtains this material via SMI or inbound delivery control. Such combinations are also not possible. The following is a brief explanation of the reasons for the limitation: The quota arrangement function that we also use for multisourcing refers to goods receipts (synonym: procurement elements, demand coverage elements). In other words, the sources of supply of the procurement elements are assigned in accordance with the procurement quotas maintained and the quotas are updated correspondingly. These procurement elements (for example, purchase orders, scheduling agreement delivery schedules, production orders, and so on) are created by the MRP run to cover demand. These procurement elements (for example, scheduling agreement delivery schedules) can then be divided among multiple sources (suppliers) in MRP in accordance with quota arrangements, in other words, a source of supply is assigned to each procurement element. Within the framework of stock procurement in MRP (at SAP), all procurement elements can potentially cover all demands, in other words, there is no separation of the requirements elements (for example, in accordance with the SMI case and the non-SMI case) and there is also no separation of the procurement elements.
( Changed at 06.12.2005 )
Supplier Collaboration: EWM integration
EWM integration only via ERP in SPM scenario
( Changed at 06.12.2005 )
Supplier Collaboration: Purchase Orders in the SMI Process
Purchase Orders in the SMI Process are not taken into account for the projected stock and the reduction of planned receipts
( Changed at 06.12.2005 )
Supplier Collaboration: Purchasing group not supported in PO in SMI process
Purchasing group not supported in PO in SMI process.
( Changed at 06.12.2005 )
Supplier Collaboration: Unloading Point in ICH has 20 characters only (ERP: 25)
Unloading Point in ICH has 20 characters only (ERP: 25)
( Changed at 06.12.2005 )
Mappings from ERP IDoc to XML
Mappings from ERP IDoc to XML are only provided for #A2A# communication (OED ERP <#> ICH) and vice versa. Please note that this means that in case of supplier collaboration SAP doesnot deliver a mapping XML format to the supplier's system and in case of customer collaboration SAP doesn't deliver a mapping XML format to the customer's systems
( Changed at 06.12.2005 )
SAP does not provide mappings from the SAP B2B XML messages
SAP does not provide mappings from the SAP B2B XML messages used by ICH to external standards (and vice versa).
( Changed at 06.12.2005 )
ICH supports only base unit of measure for all user interfaces
ICH supports only base unit of measure for all user interfaces
( Changed at 06.12.2005 )
Supplier Collaboration: SAP ICH 5.0 doesn't support end to end CPFR Processes
SAP ICH 5.0 doesn't support end to end CPFR Processes
( Changed at 06.12.2005 )
Supplier Collaboration: Integration with APO for scheduling agreement release
Integration with APO for scheduling agreement release and corresponding confirmations is tested and released by SAP only for mySAP SCM5.0
( Changed at 06.12.2005 )
Customer Collaboration: Returns Instruction, Returns ASN: Only as part of SPM returns scenario
Returns Instruction, Returns ASN: can only be used as part of SPM returns scenario.
( Changed at 06.12.2005 )
Customer Collaboration: Return Delivery Instruction Notification
Return Delivery Instruction Notification: item level group ID only 3 characters
( Changed at 06.12.2005 )
Customer Collaboration: purchase order change by customer
The only purchase order changes considered in the responsive replenishment scenario are PO-Numbers, which are transferred into the Sales Order via the IDOC ORDRSP. No other order changes are taken into account.
( Changed at 06.12.2005 )
Customer Collaboration: inventory split
The functionality for inventory split concerning baseline/promotion and out of stock calculation require that inventory and sales data are sent in one Product Activity XML message. This is a limitation related to the Data Import Controller which is one process step in the Responsive Replenishment Scenario. Consider that e. g. sending inventory report and sales report in two EDI files wouldn't work, unless it can be put in one Product Activity XML message.
( Changed at 06.12.2005 )
Customer Collaboration: Sourcing in RR Replenishment
Sourcing in RR Replenishment is based on validity of transportation lanes with regard to current date only.
( Changed at 06.12.2005 )
Customer Collaboration: Material determination takes into acocunt the current date only
Material determination takes into acocunt the current date only
( Changed at 06.12.2005 )
Customer Collaboration: No ATP check is performed within RR planning
No ATP check is performed within RR planning
( Changed at 06.12.2005 )
Customer Collaboration: No deployment algorithm is performed within RR planning
No deployment algorithm is performed within RR planning
( Changed at 06.12.2005 )
For browsers supported by BSPs please have a look at note 598860.
For Browsers supported by BSPs please have a look at note 598860.
( Changed at 06.12.2005 )
Set up of unique order numbers by having several SAP R/3s connected to the SAP ICH System
A purchase order or a release is unique for a customer. The data storage in the ODM is partner dependent. It is not allowed in the SAP R/3s to use overlapping number ranges for PO and Release numbers. Therefore, if more than 1 SAP R/3 are connected to the SAP ICH System you need to create in SAP ICH 1 a Customer Partner for each backend system.
( Changed at 06.12.2005 )
No Handling Unit mapping is carried out on SAP XI
No Handling Unit (HU) mapping is carried out on SAP XI while converting the Replenishment Order Notification XML to the ORDERS.ORDERS05 IDoc.
( Changed at 06.12.2005 )
(Dis-)aggregation functionality over locations and/or products is not provided for SAP ICH 5.0
Please note that (dis-)aggregation functionality over locations and/or products is not provided for SAP ICH 5.0 in standard.
( Changed at 06.12.2005 )
Muliple order numbers
On ICH order document numbers must be unique by business partner. A simultaneous use of the same number for different systems of the same business partner is not supported.
( Changed at 06.12.2005 )
Customer Collaboration: Sourcing in RR Replenishment
Sourcing based on transportation guidelines is only supported for promotions
( Changed at 06.12.2005 )
Authorization concept for ITS links
Links to ITS Web GUI screens are not controlled by the ICH authorization object C_ICH_USER, but can be disabled with a BADI implementation
( Changed at 06.12.2005 )
Time Series Locking
Locking of time series udpates from the user interface of ICH is not provided
( Changed at 06.12.2005 )
ERP: SMI PO contract reference
In ERP there can be a single contract reference for each vendor generated PO only.
( Changed at 06.12.2005 )
Supplier Collaboration - Purchase Order (PO): No Supersession PO for Demand Monitor
The Demand Monitor cannot be used to show data derived from purchase orders, which take part in the SPM supersession process.
( Changed at 06.12.2005 )
Release with restrictions
ERP: Cancellation of ASN
Cancellation of ASN cannot be transmitted to ERP
( Changed at 06.12.2005 )
Supplier Collaboration: Serial Numbers Check
Serial Numbers not checked against master data Serial number Uniqueness only ensured within ASN
( Changed at 06.12.2005 )
Supplier Collaboration: Serial Number Maintenance
Serial Number Maintenance not on ASN Create but only on ASN Details Screen
( Changed at 06.12.2005 )
Supplier Collaboration: No ASN Re-Direction on ICH
No ASN Re-Direction on ICH
( Changed at 06.12.2005 )
Accessability of ASN printout
Accessability: ASN print form is provided by SAP only with smartform technology. An Adobe form solution is possible on a customer project basis
( Changed at 06.12.2005 )
Release with restrictions
ERP: PO outbound message when final delivery
There is no PO outbound message from ERP when final delivery indicator (ELIKZ) is set during goods receipt posting
( Changed at 06.12.2005 )
ERP: PO outbound message when goods receipt
There is no PO outbound message from ERP when goods receipt quantity is change
( Changed at 06.12.2005 )
ERP: Rejection of PO items
Rejection of PO items (confirmation with zero quantitity and rejection status) cannot be received by ERP
( Changed at 06.12.2005 )
ERP: Transmission of goods recipient vendor
Transmission of goods recipient vendor with standard PO IDOC only with user exit
( Changed at 06.12.2005 )
ERP: Transmission of 'ordering address' vendor
Transmission of 'ordering address' vendor with standard PO IDOC only with user exit
( Changed at 06.12.2005 )
ERP: ERP cannot send final delivery indicator with standard IDOC
ERP cannot send final delivery indicator with standard IDOC. To close POs on ICH, a customer project solution is required. Alternatively one can work with ASNs on ICH and use delivery tolerances from master data to close PO items
( Changed at 06.12.2005 )
ERP: Changes of the delivery date of the sales order item
Please be aware of that changes of the delivery date of the sales order item made in SAP R/3 SD (Sales and Distribution component) are not transferred back to SAP ICH 5.0 This is a SAP R/3 Backend Integration limitation in regards to the responsive replenishment scenario.
( Changed at 06.12.2005 )
The deletion of sales orders or sales order items in SAP R/3 is not allowed
The deletion of sales orders or sales order items in SAP R/3 is not allowed,because the information cannot be transferred via IDoc to the XML. Usually the order or order item will be cancelled/rejected in SAP R/3 instead of deleted.
( Changed at 06.12.2005 )
Supplier Collaboration: SMI and SNI ERP integration
ERP side integration functionality for SMI (including Multisourcing) and SNI is provided with Plugin 2004.1 SP10 for Releases 4.6C and later, and with ERP 2005
( Changed at 06.12.2005 )
Supplier Collaboration: Full-Update Transmission of standard PO IDOCs
ICH needs full update mode for transmission of standard PO IDOCs: user exit required
( Changed at 06.12.2005 )
ERP: Transmission of delivery tolerances
ERP does not transmit delivery tolerances with standard IDOC. Delivery Tolerances from Lane master Data can be used on ICH.
( Changed at 06.12.2005 )
ERP: PO message on component change
ERP does not trigger outbound message when components were changed within the PO.
( Changed at 06.12.2005 )
Deletion of Sales Order Items in ERP
The deletion of sales orders or sales order items in SAP R/3 is not allowed, because the information cannot be transferred via IDoc to the XML. Usually the order or order item will be cancelled/rejected in SAP R/3 instead of deleted.
( Changed at 06.12.2005 )
Blocked Kanban Transmission
Transmission of number of blocked kanbans with the ICH kanban master data report and transmission of the supply area description text is only available in ERP2005 SP2 and Plug-In 2004.1 SP11.
( Changed at 06.12.2005 )
ERP:Restrictions regarding Goods receipts handling by sending out Proof of Deliveries
ERP: Restrictions regarding Goods receipts handling by sending out Proof of Deliveries (OPOD output message type) from SAP R/3 to SAP ICH 5.0 Please consider that sending out of a Proof of delivery (message output type = OPOD) after posting a (Partial)Goods receipt has certain restrictions which needs to be reflected in SAP ICH 5.0 related supplier collaboration processes: * Goods receipt process for inbound delivery (T-Code VL32N)# #POD can be sent out only once, therefore a partial goods receipt #booking does not make sense. Full good receipt is possible!# * Goods receipt process via T-Code MIGO##### #Sending out of a POD immediately via MIGO is not supported# There are different options for transferring (Partial) Goods receipts information to SAP ICH 5.0 by using the RSMIPROACT report (Please read the SAP ICH 5.0 online documentation - section 'Overview of processing GR data from SAP-R/3').
( Changed at 07.06.2006 )
Release with restrictions
Supplier Collaboration: Kanban and scheduling agreement releases
ICH supports only forecast releases but not JIT releases as preview of Kanban requriements
( Changed at 06.12.2005 )
Release with restrictions
ERP: contract manufacturing scenario
The ICH contract manufacturing scenario is based on functionality introduced in SAP ERP 2005. Lower ERP or R/3 releases have tio be enhanced in a customer project.
( Changed at 06.12.2005 )
ERP: Goods receipt quantity of the PO
Components assigned to a schedule line in ICH should be changeable until a goods receipt happened in SAP ERP, exact until open quantity equal requested quantity. The BAPI_PO_CHANGE, which is sent from SAP ERP to ICH, however, does not contain the goods receipt quantity of the PO schedule line. This needs to enhanced in a customer project. Alternatively, one can work with ASNs.
( Changed at 06.12.2005 )
All PO items and PO components must refer to SCM master data
All PO items and PO components must refer to SCM master data
( Changed at 06.12.2005 )
Supplier Collaboration: Integration to Contract Manufacturer´s ERP system
SAP does not provide integration of an ERP system on contract manufacturer side, in particular with regard to additional information in the purchase orders like components.
( Changed at 06.12.2005 )
Release with restrictions
Receipt of scheduling agreements
SAP ICH 5.0 is not able to handle scheduling agreements that contain schedule lines belonging to multiple scheduling agreement items.
( Changed at 06.12.2005 )
HU in Replenishment Order Notification
No Handling Unit (HU) mapping is carried out on SAP XI while converting the Replenishment Order Notification XML to the ORDERS.ORDERS05 IDoc.
( Changed at 06.12.2005 )
Delivery Schedule Notification with Multiple Release
ICH is not able to handle scheduling agreement release messages that contain schedule lines belonging to multiple scheduling agreement items.
( Changed at 06.12.2005 )
Release with restrictions
Supplier Collaboration: PO data is not integrated into SNI time series data
PO data is not integrated into SNI time series data
( Changed at 06.12.2005 )
Supplier Collaboration: Data extraction from Contract Manufacturer's ERP system
SAP does not offer data extraction for SNI scenario from Contract Manufacturer's ERP system
( Changed at 07.12.2005 )
Supplier Collaboration: SNI integration product activity
SNI integration product activity messages may be posted only by OEM or contract manufacturer for OEM managed or contract manufacturer managed components, respectively.
( Changed at 06.12.2005 )
Supplier Collaboration: SNI location products
In the SNI scenario, a given product number can be used within one location only as a OEM owned or CM owned product.
( Changed at 06.12.2005 )
Release with restrictions
Customer Collaboration:Display confirmed quantities via ICH 5.0 Transport Load Builder UserInterface
It is not possible to display confirmed quantities (ATP checked quantities) via the SAP ICH 5.0 Transport Load Builder User Interface (TLB UI). This effects the backend integration as Sales Order Procesing is one process step within the Responsive Replenishment Scenario.
( Changed at 06.12.2005 )
Header Data
| Release Status: | Released for Customer |
| Released on: | 11.12.2009 11:10:32 |
| Master Language: | English |
| Priority: | Recommendations/additional info |
| Category: | Consulting |
| Primary Component: | SCM-CA-PER SCM Performance Cross Application |
| Secondary Components: | SCM-APO-ATP Global Available-to-Promise |
| SCM-APO-SNP Supply Network Planning (SNP) | |
| SCM-APO-PPS Production Planning and Detailed Scheduling | |
| SCM-APO-SCC Supply Chain Cockpit (SCC) | |
| SCM-APO-FCS Demand Planning | |
| SCM-APO-MD Master Data | |
| SCM-APO-OCX ActiveX controls | |
| SCM-APO-OPT Optimization | |
| SCM-APO-INT Interfaces | |
| SCM-APO-CA-CDP Characteristics-dependent Planning | |
| SCM-APO-SCC-BF Basic Functions | |
| SCM-APO-AMO Alert Monitor | |
| SCM-APO-SCE Supply Chain Engineer | |
| SCM-APO-SCC-CMS Cockpit Main Screen | |
| SCM-APO-FCS-BF Basic Functions | |
| SCM-APO-FCS-STF Statistical Forecasting | |
| SCM-APO-FCS-INF Interactive Forecasting | |
| SCM-APO-FCS-PRP Promotion Planning | |
| SCM-APO-FCS-LCP Lifecycle Planning | |
| SCM-APO-FCS-MAP Mass Processing | |
| SCM-APO-FCS-EVA Please use Component SCM-APO-FCS | |
| SCM-APO-SNP-BF Basic Functions | |
| SCM-APO-SNP-OPT Optimization of Supply Network Plan | |
| SCM-APO-SNP-INS Interactive SNP | |
| SCM-APO-SNP-DPL Deployment | |
| SCM-APO-SNP-TLB Transport Load Builder | |
| SCM-APO-SNP-MAP Mass Processing | |
| SCM-APO-PPS-SCF Scheduling Functions | |
| SCM-APO-PPS-EVA Evaluation | |
| SCM-APO-ATP-BF Basic Functions | |
| SCM-APO-ATP-BOP Backorder Processing | |
| SCM-APO-ATP-EST Explanation & Simulation | |
| SCM-APO-ATP-RBA Rules-Based Available-To-Promise (ATP) | |
| SCM-APO-OPT-BF Basic Functions | |
| SCM-APO-OPT-PPS Production Planning and Detailed Scheduling | |
| SCM-APO-OPT-SNP Supply Network Planning | |
| SCM-APO-INT-EXT Interface to External Systems | |
| SCM-APO-MD-MO Model | |
| SCM-APO-MD-VM Version Management | |
| SCM-APO-MD-LO Location | |
| SCM-APO-MD-PR Product | |
| SCM-APO-MD-RE Resource | |
| SCM-APO-MD-PPM Production Process Model | |
| SCM-APO-CA-COP Collaborative Planning | |
| SCM-APO-PPS-PCM Production Campaign | |
| SCM-APO-INT-IMO Integration Model | |
| SCM-APO-INT-MD Master Data | |
| SCM-APO-INT-STK Stock | |
| SCM-APO-INT-PPS PP-DS / Production and Process Order | |
| SCM-APO-INT-MD-SUS Supersession Chains | |
| SCM-APO-INT-RP Requirements Planning/Planned Order | |
| SCM-APO-INT-DP Demand Planning | |
| SCM-APO-INT-PUR Purchasing / Purch. Req. and Order, Transfer Order | |
| SCM-APO-INT-SLS Sales | |
| SCM-APO-INT-PPE Integrated Product Process Engineering | |
| SCM-APO-VS Vehicle Scheduling | |
| SCM-APO-VS-BF Basic Functions | |
| SCM-APO-VS-OPT Vehicle Scheduling Optimization | |
| SCM-APO-VS-INS Interactive Vehicle Scheduling | |
| SCM-APO-VS-CAS Carrier Selection | |
| SCM-APO-VS-MAP Integration | |
| SCM-APO-PPS-MMP Model Mix Planning | |
| SCM-APO-PPS-RPM Rapid Planning Matrix | |
| SCM-APO-PPS-AHT Action Handler and Production Tracking | |
| SCM-APO-PPS-PPC Product and Process Confirmation | |
| SCM-APO-OPT-SEQ Sequencing | |
| SCM-APO-MD-SRC Sources of Supply | |
| SCM-APO-PMO Plan Monitor | |
| SCM-APO-CPR Collaborative Procurement | |
| SCM-APO-CPR-SCH Scheduling Agreement | |
| SCM-APO-CPR-SCT Subcontracting | |
| SCM-APO-CPR-TRA Stock Transfer | |
| SCM-APO-CPR-QUO Quota Arrangement | |
| SCM-APO-INT-MD-RE Resource | |
| SCM-APO-INT-MD-PR Product | |
| SCM-APO-INT-MD-LO Location | |
| SCM-APO-INT-MD-PPM Production Process Model | |
| SCM-APO-INT-STK-RS Manual Reservation | |
| SCM-APO-INT-PCM Production Campaign | |
| SCM-APO-INT-DP-PIR Planned Independent Requirement | |
| SCM-APO-INT-DP-PRM Retail Promotion / Consumption Data | |
| SCM-APO-INT-PUR-SQ Sources of Supply | |
| SCM-APO-INT-PUR-SUB Subcontracting | |
| SCM-APO-MD-CL Classes and Characteristics | |
| SCM-APO-MD-TL Transportation Lanes | |
| SCM-APO-CA-VC Variant Configuration | |
| SCM-APO-FCS-CHS Characteristics-based Forecasting | |
| SCM-APO-SNP-SFT Safety Stock Planning | |
| SCM-APO-INT-MD-CLC Classes and Characteristics | |
| SCM-APO-INT-CON Configuration | |
| SCM-APO-ATP-SCH Time and Scheduling Functions | |
| SCM-APO-SDM Multi-Level Supply & Demand Matching | |
| SCM-APO-SDM-CTM Capable-to-Match | |
| SCM-APO-SDM-SUD Supply Distribution | |
| SCM-APO-SDM-SCV Supply Chain Viewer | |
| SCM-APO-PPS-SL Shelf Life | |
| SCM-APO-PPS-HEU Heuristics | |
| SCM-APO-PPS-HEU-REM Repetitive Manufacturing Heuristics | |
| SCM-APO-PPS-HEU-DS Detailed Scheduling Heuristics | |
| SCM-APO-PPS-HEU-PP PP Heuristics | |
| SCM-FC-PMC Process Management and Control | |
| SCM-APO-PPS-PSH Push Production APO | |
| SCM-APO-PPS-WP Workplace | |
| SCM-APO-MD-PDS Production Data Structure | |
| SCM-APO-INT-MD-PDS Production Data Structure | |
| SCM-APO-ATP-PRD ATP in Combination with Production | |
| SCM-APO-SNP-SCH SNP Schedule Agreement Processing | |
| SCM-APO-INT-SNP Please use Component from area APO-SNP* or APO-INT* | |
| SCM-APO-PPS-PPT Product Planning Table | |
| SCM-APO-PPS-PPT-PRE Presentation Product Planning Table | |
| SCM-APO-PPS-PPT-FCT Scheduling Functions Product Planning Table | |
| SCM-APO-PPS-DST Detailed Scheduling Planning Board | |
| SCM-APO-PPS-DST-PRE Presentation Detailed Scheduling Planning Board | |
| SCM-APO-PPS-DST-FCT Scheduling Functions Detailed Scheduling Planning Board | |
| SCM-APO-PPS-PVW Product View | |
| SCM-APO-PPS-PVW-PRE Presentation Product View | |
| SCM-APO-PPS-PVW-FCT Scheduling Functions Product View | |
| SCM-APO-PPS-SNP Conversion SNP to PP/DS | |
| SCM-APO-PPS-POM Planned Order Management (for iPPE-based orders) | |
| SCM-APO-PPS-CDS Sales Scheduling Agreement Processing | |
| SCM-APO-PPS-POM-PRE Presentation Planned Order Management | |
| SCM-APO-PPS-POM-FCT Functions Planned Order Management | |
| SCM-APO-PPS-S2L Supply-to-Production | |
| SCM-APO-WFM Workforce Management | |
| SCM-APO-CA-PER Performance | |
| SCM-APO-ATP-BF-PAC Product Availability Check | |
| SCM-APO-ATP-BF-FCS Check against Forecast | |
| SCM-APO-ATP-BF-PAL Check against Product Allocations | |
| SCM-APO-ATP-PRD-MATP Multi-Level ATP | |
| SCM-APO-ATP-PRD-CTP Capable-To-Promise | |
| SCM-APO-OPT-VS Vehicle Scheduling Optimization | |
| SCM-APO-INT-SLS-IB Inbound APO | |
| SCM-APO-INT-SLS-OBOP Outbound APO Backorder Processing | |
| SCM-APO-INT-SLS-OVMI Outbound APO VMI | |
| SCM-APO-INT-SLS-OCRM Outbound APO CRM | |
| SCM-APO-PPS-MOP Multiple Output Planning | |
| SCM-APO-PPS-ATP ATP-Check for Inhouse Production within APO | |
| SCM-APO-SNP-VMI Vendor-Managed-Inventory | |
| SCM-APO-VS-INS-UI User Interface | |
| SCM-APO-VS-INS-CF Central Functions | |
| SCM-APO-VS-MAP-DL Deliveries R/3 | |
| SCM-APO-VS-MAP-SH Shipments R/3 | |
| SCM-APO-VS-MAP-FC Freight Costs | |
| SCM-APO-SNP-CAP Capacity Leveling | |
| SCM-APO-FCS-EXT Extraction | |
| SCM-APO-FCS-CSP Forecast Consumption | |
| SCM-APO-PPS-RSP Reservation Planning | |
| SCM-APO-INT-PPS-GI Goods Receipt to Production/Process Orders | |
| SCM-APO-INT-PPS-CNF Confirmation | |
| SCM-APO-INT-CCR CIF Compare and Refresh | |
| SCM-APO-INT-CCR-FRW Framework | |
| SCM-APO-INT-CCR-EP Purchasing | |
| SCM-APO-INT-CCR-IP In-House Production | |
| SCM-APO-INT-CCR-STK Stock | |
| SCM-APO-INT-CCR-SLS Sales and Distribution | |
| SCM-APO-INT-CCR-SHP Shipments | |
| SCM-APO-SNP-MAC MacroBuilder | |
| SCM-APO-SNP-RF Release to Demand Planning | |
| SCM-APO-FCS-MAC MacroBuilder | |
| SCM-APO-FCS-RF Release | |
| SCM-APO-FCS-BOM DP BOM | |
| SCM-APO-FCS-RLG Realignment | |
| SCM-APO-MSP Maintenance and Service Planning | |
| SCM-EM-AS Application System | |
| SCM-EM-MGR Event Manager | |
| SCM-EM-AS-CNF Application System Configuration | |
| SCM-EM-AS-CON Application Control Processing | |
| SCM-EM-AS-EVG Event Generation | |
| SCM-EM-MGR-ISQ Information System and Queries | |
| SCM-EM-MGR-EVP Event Processing | |
| SCM-EM-MGR-CON Control Processing | |
| SCM-EM-MGR-CNF Configuration | |
| SCM-EM-MGR-ADM Administration | |
| SCM-APO-MD-VM-CMD Copy Master Data | |
| SCM-APO-MD-VM-CTR Copy Transactional Data (orders and inventories) | |
| SCM-APO-MD-VM-CTS Copy Planning Version SNP/DP Time Series | |
| SCM-APO-MD-CAL Planning Calendar | |
| SCM-APO-PPS-FOT Flexible Order Transactions | |
| SCM-APO-ATP-PRD-PL Planning Receipts CTP Scenario | |
| SCM-APO-ATP-PRD-TC Conversion ATP Tree Structures | |
| SCM-APO-ATP-RBA-STO RBA Triggered Stock Transfer | |
| SCM-APO-INT-CDS Sales Scheduling Agreement Processing | |
| SCM-APO-PPS-RET Restriction Management | |
| SCM-APO-INT-MP Interfaces Mill Product | |
| SCM-APO-INT-CUS Customizing | |
| SCM-FRE-MD Master data | |
| SCM-FRE-IF Interfaces | |
| SCM-FRE-TSM Time Series Management | |
| SCM-FRE-FRP FRP Functions | |
| SCM-FRE-OPM Order Proposal Management | |
| SCM-FRE-DIF Demand Influencing Factor | |
| SCM-FRE-ANA Analytics | |
| SCM-FRE-RWB Replenishment Workbench | |
| SCM-FRE-EXC Exception Handling | |
| SCM-APO-MD-INC Product and Location Interchangeability | |
| SCM-APO-SNP-INC Interchangeability in SNP | |
| SCM-APO-FCS-INC Interchangeability in DP | |
| SCM-APO-PPS-LPP Long Products Planning | |
| SCM-APO-PPS-INC Interchangeability in PP/DS | |
| SCM-APO-INT-CCR-CDS Sales Scheduling Agreement Processing | |
| SCM-APO-INT-CPP Postprocessing Records of CIF Error Handling | |
| SCM-APO-INT-QM Inspection Lot Integration | |
| SCM-ECT-LIM Logistics Inventory Mangement Engine | |
| SCM-BAS-DF Cross-System and Cross-Partner Document Flow | |
| SCM-BAS-ODM Order Document Management | |
| SCM-BAS-SCH Configurable Process Scheduling | |
| SCM-BAS-UIF UI Framework | |
| SCM-BAS-ANO Alert Notification Engine | |
| SCM-BAS-TSM Time Series Data Management | |
| SCM-BAS-BIF Business Interface Layer | |
| SCM-ICH-FCS Forecasting | |
| SCM-ICH-IMO Inventory Monitor | |
| SCM-ICH-ASN Advanced Shipping Notification | |
| SCM-ICH-REL Scheduling Agreement Release | |
| SCM-ECT-LIM-AI Application Interface | |
| SCM-ECT-LIM-AC Application Component | |
| SCM-ECT-LIM-PI Plug-In | |
| SCM-FC-PA Partner Ascertainment | |
| SCM-FC-UI User Interface | |
| SCM-APO-PPS-POV Product Overview | |
| SCM-BAS-MDL Master Data Layer | |
| SCM-APO-INT-DP-AFS Apparel and Footwear Industry | |
| SCM-FRE-SUI Store User Interface | |
| SCM-APO-OCX-SCR APOGrid Scripting | |
| SCM-APO-OCX-BF OCX Basic Functions | |
| SCM-APO-CA-CDP-BRG Block Requirements Generation | |
| SCM-APO-CA-CDP-BLK Blockplanning | |
| SCM-APO-CA-CDP-PPM Characteristics Propagation | |
| SCM-APO-CA-CDP-MAT Material Master: CDP Classification | |
| SCM-APO-INT-MD-CDP Classes and Characteristics (CDP relvant) | |
| SCM-APO-INT-CON-VC Variant Configuration | |
| SCM-APO-INT-CON-CDP Configuration CDP | |
| SCM-APO-INT-POR Project Order | |
| SCM-APO-INT-MOR Maintenance Order | |
| SCM-BAS-AMO Alert Monitor | |
| SCM-BAS-PAK Packing Basics | |
| SCM-APO-MD-CL-CDP Characteristics-dependent Planning | |
| SCM-APO-INT-CCR-QM Inspection Lots | |
| SCM-BAS-PSM Planning Service Manager | |
| SCM-APO-MD-PDS-SIM Display and Simulation | |
| SCM-APO-MD-PDS-GEN Generation | |
| SCM-APO-MD-PDS-EXP Explosion for Order Creation | |
| SCM-APO-PPS-FP Fixed Pegging | |
| SCM-APO-ATP-PRD-CHE Characteristics Evaluation | |
| SCM-APO-INT-CCR-CON Configuration | |
| SCM-BAS-STM Status Management | |
| SCM-ECT-LIM-PST Posting | |
| SCM-ECT-LIM-QUE Query | |
| SCM-ECT-LIM-INV Inventory | |
| SCM-ICH-MD Master Data | |
| SCM-ICH-NDC Net Demand Calculation | |
| SCM-ICH-PRO Promotion Planning | |
| SCM-ICH-TLB Transport Load Builder | |
| SCM-ICH-REP Reporting | |
| SCM-ICH-DIO Data Inbound / Data Outbound Management | |
| SCM-ICH-AMO Alert Monitor | |
| SCM-APO-INT-CC CIF-Cockpit | |
| SCM-APO-INT-CCR-MOR Maintenance Order | |
| SCM-APO-INT-CCR-POR Project Order | |
| SCM-ICH-PO Purchase Order and Replenishment Order | |
| SCM-FRE-ERP SAP F&R-SAP ERP Interfaces | |
| SCM-EWM-ARC Archiving | |
| SCM-EWM-AUT Authorization | |
| SCM-EWM-DLP Delivery Processing | |
| SCM-EWM-DLP-INT Integration | |
| SCM-EWM-DLP-INT-WM Warehouse Management | |
| SCM-EWM-DLP-INT-TCP Integration to Customs Procedures/Global Trade Services | |
| SCM-EWM-DLP-INT-TMS Integration to Transportation Management System | |
| SCM-EWM-DLP-INT-SR Integration to Shipping and Receiving/Yard Management | |
| SCM-EWM-DLP-INT-QM Integration with Quality Management | |
| SCM-EWM-DLP-BF Basic Functions/Services | |
| SCM-EWM-DLP-BF-CRN Create/Activate/Reject Requests/Notifications | |
| SCM-EWM-DLP-BF-CDD Create Delivery Documents | |
| SCM-EWM-DLP-BF-MDD Maintain Delivery Documents (Reject, Adjust) | |
| SCM-EWM-DLP-BF-WDV Warehouse-Request-Specific Determinations/Validations | |
| SCM-EWM-DLP-BF-HC Hierarchies/Correlations | |
| SCM-EWM-DLP-BF-BM Batch Management | |
| SCM-EWM-DLP-BF-PAC Packing | |
| SCM-EWM-DLP-BF-CWM Confirmation Warehouse Management | |
| SCM-EWM-DLP-BF-GM Goods Movements (GR/GI/Reversal/Posting Change) | |
| SCM-EWM-DLP-BF-CD Change Documents | |
| SCM-EWM-DLP-BF-ARC Archiving | |
| SCM-EWM-DLP-SF Specific Process Functions | |
| SCM-EWM-DLP-SF-ID Inbound Delivery | |
| SCM-EWM-DLP-SF-RT Returns | |
| SCM-EWM-DLP-SF-OD Outbound Delivery | |
| SCM-EWM-DLP-SF-ST Stock Transfers/Posting Changes | |
| SCM-EWM-DLP-CFG Configuration | |
| SCM-EWM-DLP-CFG-ACT IMG activity | |
| SCM-EWM-DLP-CFG-CNT Configuration Content | |
| SCM-EWM-DLP-UI User Interface | |
| SCM-EWM-DLP-ENH Enhancement Possibilities | |
| SCM-EWM-EH Exception Handling | |
| SCM-EWM-IF Interfaces | |
| SCM-EWM-IF-ERP ERP | |
| SCM-EWM-IF-ERP-DLP Delivery Processing | |
| SCM-EWM-IF-ERP-RET Returns | |
| SCM-EWM-IF-ERP-GM Goods Movements | |
| SCM-EWM-IF-WCU Warehouse Control Units | |
| SCM-EWM-IF-MFS Material Flow System | |
| SCM-EWM-IF-BW BW | |
| SCM-EWM-IF-GTS GTS | |
| SCM-EWM-IF-GTS-TP Transit Procedures | |
| SCM-EWM-IF-GTS-CC Compliance Check | |
| SCM-EWM-IF-GTS-BWH Bonded Warehouse | |
| SCM-EWM-MD Master Data | |
| SCM-EWM-MD-SL Slotting | |
| SCM-EWM-MD-PS Packaging Specification | |
| SCM-EWM-MD-WL Warehouse Layout | |
| SCM-EWM-MD-PM Product Master | |
| SCM-EWM-MD-BA Batches | |
| SCM-EWM-MON Monitoring | |
| SCM-EWM-MON-MDS Master Data/Stock | |
| SCM-EWM-MON-DEL Delivery | |
| SCM-EWM-MON-WO Warehouse Order | |
| SCM-EWM-MON-SR Shipping and Receiving | |
| SCM-EWM-MON-WIP Work in Progress | |
| SCM-EWM-MON-PI Physical Inventory | |
| SCM-EWM-MON-QM Quality Management | |
| SCM-EWM-PI Physcial Inventory | |
| SCM-EWM-PI-PIP Physical Inventory Planning | |
| SCM-EWM-PI-PIC Physical Inventory Counting | |
| SCM-EWM-PI-DA Difference Analyzer | |
| SCM-EWM-PRN Printing | |
| SCM-EWM-PRN-WO Warehouse Order | |
| SCM-EWM-PRN-DEL Delivery | |
| SCM-EWM-PRN-FD Freight Document | |
| SCM-EWM-PRN-VAS VAS Order | |
| SCM-EWM-PRN-SR Shipping and Receiving Documents | |
| SCM-EWM-PRN-PID Physical Inventory Document | |
| SCM-EWM-PRN-HU Handling Unit | |
| SCM-EWM-QM Quality Management | |
| SCM-EWM-QM-RP Returns Processing | |
| SCM-EWM-QM-CO Counting | |
| SCM-EWM-QM-WC Work Center | |
| SCM-EWM-QM-MD Master Data | |
| SCM-EWM-QM-FUP Follow-Up Processing | |
| SCM-EWM-QM-UI UI Configuration | |
| SCM-EWM-RF Radio Frequency Processing | |
| SCM-EWM-RF-LD Loading | |
| SCM-EWM-RF-ULD Unloading | |
| SCM-EWM-RF-PUT Putaway | |
| SCM-EWM-RF-DEC Deconsolidation | |
| SCM-EWM-RF-PCK Picking | |
| SCM-EWM-RF-PAC Packing | |
| SCM-EWM-RF-IGM Internal Goods Movements | |
| SCM-EWM-RF-PI Physical Inventory | |
| SCM-EWM-RF-QM Quality Management | |
| SCM-EWM-RF-IQ Inquiries | |
| SCM-EWM-RF-FW Framework/Wizard | |
| SCM-EWM-SR Shipping and Receiving | |
| SCM-EWM-SR-MD Master Data | |
| SCM-EWM-SR-CON Configuration | |
| SCM-EWM-SR-IN Inbound | |
| SCM-EWM-SR-OUT Outbound | |
| SCM-EWM-SR-YM Yard Management | |
| SCM-EWM-VAS Value-Added Services | |
| SCM-EWM-VAS-OR VAS Order | |
| SCM-EWM-VAS-WC Work Center | |
| SCM-EWM-WAV Wave Management | |
| SCM-EWM-WC Work Center | |
| SCM-EWM-WC-PAC Packing | |
| SCM-EWM-WC-DEC Deconsolidation | |
| SCM-EWM-WOP Warehouse Order Processing | |
| SCM-EWM-WOP-SC Storage Control | |
| SCM-EWM-WOP-RM Resource Management | |
| SCM-EWM-WOP-PUT Putaway | |
| SCM-EWM-WOP-PCK Picking | |
| SCM-EWM-WOP-PC Posting Changes | |
| SCM-EWM-WOP-REA Rearrangement | |
| SCM-EWM-WOP-REP Replenishment | |
| SCM-EWM-WOP-AHM Ad Hoc Movements | |
| SCM-EWM-WOP-BF Basic Functions | |
| SCM-EWM-WOP-BF-WTC Warehouse Task Creation | |
| SCM-EWM-WOP-BF-WOC Warehouse Order Creation | |
| SCM-EWM-WOP-BF-CC Confirmation/Cancellation | |
| SCM-EWM-WOP-BF-HU Handling Units | |
| SCM-EWM-WOP-BF-SN Serial Numbers | |
| SCM-EWM-TM Transportation Management | |
| SCM-EWM-RG Routing Guide | |
| SCM-BAS-EHS EH&S Service | |
| SCM-BAS-EHS-DG Dangerous Goods Management | |
| SCM-BAS-EHS-HM Hazardous Substance Management | |
| SCM-BAS-EHS-PM Phrase Management | |
| SCM-BAS-EHS-BS EH&S Services | |
| SCM-BAS-PAK-HU Handling Units | |
| SCM-BAS-PAK-PS Packaging Specification | |
| SCM-BAS-PAK-AP Automatic Packing | |
| SCM-APO-PPS-RPT Resource Planning Table | |
| SCM-APO-OPT-CS Carrier Selection Optimization | |
| SCM-APO-VS-FU Freight Unit Processing | |
| SCM-APO-VS-RD Dynamic Route Determination | |
| SCM-APO-ATP-RG ATP in Combination with Routing Guide | |
| SCM-BAS-TDL Transaction Data Layer | |
| SCM-ICH-RET Returns | |
| SCM-ICH-KNB Kanban | |
| SCM-ICH-SNI Supply Network Inventory | |
| SCM-ICH-SCO Supplier Confirmations | |
| SCM-ICH-ERP ERP-SNC Integration | |
| SCM-FRE-REF References | |
| SCM-APO-ATP-PSS Parameter-dependent ATP Safety Stock | |
| SCM-APO-ATP-PRD-KIT Kits | |
| SCM-APO-ATP-ODL Order due list | |
| SCM-APO-ATP-EQA Event-Driven Quantity Assignment | |
| SCM-APO-ATP-CND Condition Technique (ATP) | |
| SCM-BAS-COR Correlation Services | |
| SCM-APO-MD-HI Hierarchy | |
| SCM-BAS-MD Master Data | |
| SCM-BAS-MD-SCU Supply Chain Unit | |
| SCM-APO-ATP-RND Rounding | |
| SCM-APO-ATP-ROC Reassignment of Order Confirmations | |
| SCM-APO-ATP-TPO Third-Party Order Processing | |
| SCM-APO-FCS-DC Demand Combination | |
| SCM-APO-FCS-SEA Seasonal Planning | |
| SCM-APO-INT-AFS AFS | |
| SCM-APO-SPP Service Parts Planning | |
| SCM-APO-SPP-CPD Historical Data Capture and Maintenance | |
| SCM-APO-SPP-SFC Service Parts Forecasting | |
| SCM-APO-SPP-SIP Service Parts Inventory Planning | |
| SCM-APO-SPP-SDR Service Parts DRP | |
| SCM-APO-SPP-SDE Service Parts Deployment | |
| SCM-APO-SPP-SRE DRP Approval and Release | |
| SCM-APO-SPP-SFA Service Fill Analysis | |
| SCM-APO-SPP-INB Inbound Delivery Monitor | |
| SCM-APO-SPP-SHA Shortage Analysis | |
| SCM-FRE-CPF Collaborative Planning, Forecasting and Replenishment (CPFR) | |
| SCM-FRE-FRP-SAF SAF |
Affected Releases
|
Related Notes
