Online Tutorials & Training Materials | STechies.com
Register Login

Release Restrictions for SCM 5.0

|| || 2

Release Restrictions for SCM 5.0
Stechies

This note provides information about release restrictions for SCM 5.0.


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).


Open Limitation(s)

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 )

SCM

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 )



SCM-APO

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.
( Changed at 15.11.2005 )



SCM-APO-ATP

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 )



No release
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 )



SCM-APO-ATP-BF-PAL

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 )



SCM-APO-ATP-BOP

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 )



SCM-APO-ATP-PRD-CTP

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 )



SCM-APO-ATP-PRD-TC

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 )



SCM-APO-ATP-RBA

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 )



SCM-APO-CA

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 )



SCM-APO-CA-CDP

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 )



SCM-APO-FCS

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 )



SCM-APO-INT

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 )



Release with restrictions
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 ‘ ’ <space>. • The Event will be generated only for Purchase requisitions, for other objects like Purchase Order the event will not be created. • The event will be created only for the purchase requisition which has only one item and schedule line, if it has more than one item / schedule line the event will not be created for that requisition
( 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 )



SCM-APO-INT-MD

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 )



SCM-APO-INT-MD-PPM

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 )



SCM-APO-INT-MD-RE

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 )



SCM-APO-INT-PPS

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 )



SCM-APO-INT-RP

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 )



SCM-APO-INT-STK

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 )



SCM-APO-MD

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 )



Release with restrictions
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 )



No release
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 )



SCM-APO-MD-INC

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 )



SCM-APO-MD-PPM

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 )



No release
Operation Split
The functionality of operation split is not supported in APO. See also note 441777.
( Changed at 06.12.2005 )



SCM-APO-MD-RE

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 )



SCM-APO-OPT-SNP

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 )



SCM-APO-PPS

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 )



Release with restrictions
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 )

 


Comments

  • 15 Apr 2008 10:28 pm
    This is an excellent site , I got many answers to my questions.
    Rupinder
  • 08 Jul 2008 5:35 pm
    Very Good! Serves as a quick handbook reference!

    Venkat

    8th of July 2008

Related Articles

0.014 seconds.