SAPTechno

Note 1240722 - SAP APO 7.0: Corrections to Online Documentation

Header
Version / Date 56 / 2011-09-12
Priority Correction with low priority
Category Documentation error
Primary Component SCM-APO-PPS Production Planning and Detailed Scheduling
Secondary Components SCM-APO-PPS-FOT Flexible Order Transactions

Summary
Symptom

A correction to online documentation is required.

Other terms

SAP Library, Advanced Planning and Optimization, application docu

Solution

Below, you find the corrections grouped according to the application components.

Production Planning and Detailed Scheduling
  • Chapter "Components" (Planned Order Management)

           In the documentation for planned order management, at the end of the "Use" keyblock of the "Components" chapter, the information is missing that it is not possible to edit phantom assemblies and the individual components of a phantom assembly. It is, for example, not possible to fix a phantom assembly or component of a phantom assembly, to replace the current product number by another product number, or to change the quantity of a phantom assembly or phantom assembly component. It is also not possible, to add a phantom assembly to an order or remove a phantom assembly from an order, or to add a component to a phantom assembly or to remove a component from a phantom assembly. Service Parts Planning (SPP)

  • Chapter "Calculating the Shortage Quantity in the Inbound Delivery Monitor"

           The section "Example" should be changed as follows:

           Old text:

           "The Inbound Delivery Monitor determines a total supply shortage of 532 pieces for the limited freeze horizon as follows:

            - Starting quantity (= supply shortage in the Overdue column): 500 pieces

            - 502 > 500; difference: 2 pieces

            - 504 > 502; difference: 2 pieces

            - 506 > 504; difference: 2 pieces

            - 508 > 506; difference: 2 pieces

            - 510 > 508; difference: 2 pieces

            - 437 < 510; no additional supply shortage

            - 359 > 437; difference: 22 pieces

            - 500 pieces + 2 pieces +  2 pieces + 2 pieces + 2 pieces + 2 pieces + 22 pieces = 532 pieces"

           New text:

           "The Inbound Delivery Monitor determines a total supply shortage of 510 pieces for the limited freeze horizon as follows:

            - Starting quantity (= supply shortage in the Overdue column): 500 pieces

            - 502 > 500; difference: 2 pieces

            - 504 > 502; difference: 2 pieces

            - 506 > 504; difference: 2 pieces

            - 508 > 506; difference: 2 pieces

            - 510 > 508; difference: 2 pieces

            - 437 < 510; no additional supply shortage

            - 359 < 437; no additional supply shortage

            - 500 pieces + 2 pieces +  2 pieces + 2 pieces + 2 pieces + 2 pieces = 510 pieces"

           

**********************************************************************************************************************************************
The following corrections are available in the documentation DVDs for SAP SCM 7.0 (material number 50105126) that are available as of June 2011.

Supply Network Planning (SNP)
  • Chapter "Planning Area Administration"

           The chapter has been enhanced as shown in attachment "Locking_Enhancements.pdf".

Service Parts Planning (SPP)
  • Chapter "Distribution Requirements Planning (DRP)"

           The "Prerequisites" section must be enhanced by the following:

    • You have implemented SAP Note 801109 to allow SPP to distinguish receipts from purchase orders within the network as opposed to receipts from purchase orders from suppliers.


**********************************************************************************************************************************************
The following corrections are available in the documentation DVDs for SAP SCM 7.0 (material number 50102520) that are available as of December 2010.

Supply Network Planning (SNP)
  • Chapter "Functions for InfoObjects and Planning Folders"

           The parameter 'GRID2' is mentioned throughout the document in the incorrect format 'GRID=2'. All instances of 'GRID=2' must be changed to 'GRID2'.

           This change is also relevant for the Demand Planning (DP) application help.

Service Parts Planning (SPP)
  • Chapter "Historical Data Capture with SAP ERP"

           The following must be added to the "Prerequisites" section:

           "In the demand history, SAP Service Parts Planning (SPP) requires fields from sales orders that do not exist in releases of SAP ERP earlier than enhancement package (EHP) 2.

           To make the required fields available in enhancement package (EHP) 2 for SAP ERP 6.0 or higher, you have activated the business function Integration of SCM and ERP (SCM_GEN_01) in transaction SFW5. For more information, see SCM, ERP Integration.

           To make the required fields available in SAP ERP releases before enhancement package (EHP) 2 for SAP ERP 6.0, you have followed the approach described for the UEPOS and EZEIT fields. For more information, see Manually Enhancing DataSource 2LIS_11_VASCL."

           The following text must be changed in the "Prerequisites" section.

           Old text:

           To load order data from SAP ERP SD, you have maintained DataSource 2LIS_11_VASCL in SAP ERP and replicated it to the BI system of SAP SCM. There you have mapped this DataSource to InfoSource 2LIS_02_SCL.

           New text:

           To load stock transfer data from SAP ERP SD, you have maintained DataSource 2LIS_02_SCL in SAP ERP and replicated it to the BI system of SAP SCM. There you have mapped this DataSource to InfoSource 2LIS_02_SCL.

  • Chapter "Update Rules for Updating in 9ARAWDAT and 9ADEMAND"

           The following paragraph must be deleted from section "Features" -> "Check Master Data":

           Unit of measure

           The system checks whether a product's unit of measure is the same as the unit of measure in the SAP SCM master data. Only in this case does the system take the order item into account when capturing the historical data.

Production Planning and Detailed Scheduling (PP/DS)
  • Chapter "Rules for Creating a Procedure Package" (Under Model Mix Planning)

           Under the section "Allowed combinations of procedures for multiline planning," there is a table with the column header "Medium-term horizon". Under "Possible procedures," there is only one entry ("LP Procedure"). However, a second one must also be mentioned, as follows:

           "Genetic Algorithm (Requirements-based with lot size 1 or cumulated)"


**********************************************************************************************************************************************
The following corrections are available in the documentation DVDs for SAP SCM 7.0 (material number 5010057) that are available as of July 2010.

Supply Chain Processes with SAP APO

This node and the included chapters is obsolete since SAP APO 5.1 and must be removed.

Master Data
  • Chapter "Merge Master Data of Active Version with Inactive Version" must be changed.

           Old text:

           "Results

           The system adopts the master data attributes of your template planning version in the active planning version. Master data attributes for which there are no parameters in the template planning version remain unchanged in the active planning version. Transaction data attributes likewise remain unchanged."

           New text:

           "Results

           The system adopts the version-dependent master data attributes of your template planning version in the active planning version. Master data attributes for which there are no parameters in the template planning version remain unchanged in the active planning version. Version-independent master data attributes and transaction data attributes likewise remain unchanged." Demand Planning

  • Chapter "Functions of the Graphic in Interactive Planning" must be changed, and the chapters below it restructured. For more information, see attachment "FunctGraph.pdf".

Supply Network Planning (SNP)
  • Chapter "Supply and Demand Propagation" must be corrected. For more information, see attachment "SupplyDemandProp.pdf".
  • Chapter "Executing Supply and Demand Propagation" must be changed. For more information, see attachment "ExcupplyDemandProp.pdf".
  • Chapter "Planning Area Administration" must be changed. For more information, see attachment "Planning_Area_Administration.pdf".
  • Chapter "Maintaining SNP Master Data and Time Series" must be added. For more information, see attachment "Maintaining_SNP_MD_and_TS.pdf".
  • Chapter "Delta Initilaiztaion of Planning Areas" must be added. For more information, see attachment "Delta_Init_of_Planning_Areas.pdf".
  • Chapter "Consistency Check for SNP Time Series Network" must be added. For more information, see attachment "Cons_Check_for_SNP_TS_Network.pdf".
  • Chapter "Reorganize SNP Time Series" must be added. For more information, see attachment "Reorganize_SNP_Time_Series.pdf".
  • Chapter "Processing Master Data Queues in Supply Network Planning (SNP)" must be changed. For more information, see attachment "Proc_MD_Queues_in_SNP.pdf".
  • Chapter "Aggregates and Planning Objects" must be added. For more information, see attachment "Aggregates_and_Planning_Objects.pdf".
  • Chapter "Saving Data in DP and SNP" must be changed. For more information, see attachment "Saving_Data_in_DP_and_SNP.pdf".
Production Planning and Detailed Scheduling (PP/DS)
  • Chapter "APO Order: Split, Merge and Product Change" and all sub-chapters

           The functionality of flexible order transactions is not supported. Therefore, the documentation for flexible order transactions, which is included in the documentation node "APO Order: Split, Merge and Product Change" (including all subchapters), must be removed from the following documentation nodes:

    • SAP Advanced Planning and Optimization (SAP APO) -> Production Planning and Detailed Scheduling (PP/DS) ->  PP/DS Process -> Manufacturing Execution
    • SAP Advanced Planning and Optimization (SAP APO) -> Industry-Specific Applications -> SAP for Automotive -> APO Repetitive Manufacturing

           For more information, see SAP Note 1406424.

           To implement the correction, copy the corrected CHM and SAR files to the server/directory where you have installed the application documentation (SAP LIbrary). The files are included in the following zip files that are attached to this SAP Note:

    • SCM700_APO_PPS_FOT_CHM_DE.zip
    • SCM700_APO_PPS_FOT_SAR_DE.zip
    • SCM700_APO_PPS_FOT_CHM_EN.zip
    • SCM700_APO_PPS_FOT_SAR_EN.zip

           Global Available-to-Promise

  • Chapter "Multi-Item Single Delivery Location"

           In the list of functions of the rules-based ATP check that the MISL does not take into consideration, the entry "Production" must be replaced with "Production with the exception of multilevel ATP check (MATP)".

  • Chapter "Backorder Processing in the Background"

           The sentence "For more information about rescheduling in the ERP system, see 'Rescheduling of Sales Documents'." must be replaced by the following sentence:

           "For more information about rescheduling in the ERP system, see SAP Libray for SAP ERP Central Component under Logistics -> Sales and Distribution (SD) -> Availability Check and Requirements in Sales and Distribution Processing -> Availability Check in Sales and Distribution Processing -> Rescheduling Sales Documents."
Service Parts Planning (SPP)

  • Chapter "Anticipated Demand Coverage" must be changed. For more information about the changes, see attachment "AntDemCoverage.pdf".
  • Chapter "Trigg's Tracking Signal" must be changed as follows:
    • In the introductory paragraph, the word "non-systematic " must be deleted, so that the text reads as follows:

                    Trigg's tracking signal checks whether the chosen forecast model is suitable for a certain location product, or whether it would be better to choose a new forecast model. To do so, it compares the results of one of the previous forecasts with the actual demand and checks whether a forecast error has exceeded a certain limit value too often. In this case, Trigg's tracking signal sets the Tracking Threshold: Date Exceeded date on the Interactive Forecasting screen. If you have scheduled the Perform Combined Forecast planning service in which Trigg's tracking signal is integrated, the system firstly sets the exceed date and then checks certain stability criteria before triggering automatic model selection.

  • Section "Queries in the Planner's Worklist"

           In the sub-section "Critical Sales Orders", the following change must be made:

           Old text:

           The system rates all sales orders as critical that are completely or partly in backlog.

           New text:

           The system rates all sales orders as critical that are completely or partly in backorder.


**********************************************************************************************************************************************
The following corrections are available in the documentation DVDs for SAP SCM 7.0 (material number 50097766) that are available as of December 2009.

Roles for SAP APO
  • Section "Roles for Supply Network Planning (SNP) must be enhanced with new topics "SNP Planner", "SNP Administrator" and "SNP Expert". For details, see attachment "Roles for SNP.doc"
Master Data
  • Section "Automatic Creation of Transportation Lanes" needs to be changed according to SAP Note 1372636. The following paragraph must be deleted:

           "Removal of Special Procurement Type from the Material Master Record

           If you have removed the special procurement type from the material master record in the ERP system, the SCM system locks the already created transportation lane so that it cannot be used in orders."

Service Parts Planning (SPP)
  • Section "Virtual Location for Consolidated Ordering" must be changed. For details, see attachment "Virtual_Location_for_Consolid.pdf".
  • Section "Alert Types (English)" must be changed as follows:

           Old text for the "Desription" section of alert type 7849:

           "The alert was created by DRP because of the following reasons:
a) Net demand or surplus exists within the freeze horizon
b) Net demand or surplus exists within limited freeze horizon, and 'Method for order dispatching' = 'No change of purchase order quantity' is selected in stability rule DRP or the net demand or the surplus cannot be changed."

           New text:

           "The system creates this alert because DRP cannot cover a net demand.
The reasons for this are:
A net demand occurs inside the freeze horizon.
A net demand occurs in the limited freeze or plan submission horizon and the stability rules do not allow DRP to cover the net demand.
"

  • Section "Calc. of Lead Times in Depl. and Inventory Balancing" must be changed. For more information about what the changed section should look like, see attachment "Calc_Lead_Times_Depl.pdf"
  • Section "Forecast with Intermittent Forecast Model" needs to be changed as follows:

           Old text, under the "Process" keyblock:

           This forecast model uses a current counter for zero-demand periods. If there is demand in the current period, the system sets this counter to zero. Otherwise it increases the counter by one each period.

           New text:

           This forecast model uses a current counter for zero-demand periods. If there is demand in the current period, the system sets this counter to one. Otherwise it increases the counter by one each period.

           Old text, under the "Process" keyblock:

           The system only carries out a forecast under the following conditions:

    • There is demand during the current period.
    • The counter is larger than the average time between demand periods after initialization, or is larger than the smoothed time between the demand periods within the forecast run.

           New text:

           The system only carries out a forecast under the following conditions:

    • There is demand during the current period.

           OR

    • During initialization, the counter is larger than the average time between demand periods after initialization, or is larger than the smoothed time between the demand periods within the forecast run.

           After intitialization, the counter is larger than the smoothed time between the demand periods within the forecast run.

           Old text, under the "Process" keyblock:

           You can define alpha on the Model Parameter tab page in the Smoothing Factor for Time in Intermittent Forecast Model parameter.

New text:
           You can define alpha on the Model Parameter tab page in the Smoothing Factor for Time in Intermittent Forecast Model parameter.

           The smoothed time between demand periods that is multiplied by (1 - alpha) is the smoothed time between demand periods of the last period. For the first ex-post forecast calculation however, there is no smoothed time between demand periods of a previous period. For this calculation, the system uses a start value instead. This start value is the average time between demand periods (initialization periods divided by the number of non-zero demand periods).

  • Section "Determination of the Main Supplier"

           The numbered list under "Process" needs to be changed as follows:

           Old text:

           1) The system checks the quota arrangement of the suppliers in the quota arrangement master data. If you have not created a quota arrangement for your suppliers, or if all quota arrangements are equally high, the system continues with step 2. Otherwise, it chooses the supplier with the highest quota arrangement as the main supplier.

           2) The system checks the replenishment lead time of the suppliers in the transportation lane master data. If the replenishment lead times of your suppliers are all the same length, the system continues with step 3. Otherwise, it chooses the supplier with the longest replenishment lead time as the main supplier.

           3) The system checks the internal ID and chooses a supplier as the main supplier. The system does not consider the business background; this process simply ensures that the system always chooses the same supplier as the main supplier.

           New text:

           1) The system checks the quota arrangement of the suppliers in the quota arrangement master data. If you have not created a quota arrangement for your suppliers, the system treats this as a quota arrangement of 0. If you set the highest quota arrangement value for multiple suppliers, the system continues with step 2 for these suppliers. Otherwise, it chooses the supplier with the highest quota arrangement as the main supplier.

           2) The system checks the transportation duration of the suppliers in the transportation lane master data. If you set the longest transportation duration for multiple suppliers, the system continues with step 3 for these suppliers. Otherwise, it chooses the supplier with the longest transportation duration.

           3) The system checks the types of the external procurement relationships. If the external procurement relationship of only one supplier is a scheduling agreement, the system chooses this supplier. If the external procurement relationship of multiple suppliers is a scheduling agreement, the system continues with step 4 for these suppliers. Otherwise, the system continues with step 4 for all suppliers.

           4) The system checks the internal ID and chooses a supplier as the main supplier. The system does not consider the business background; this process simply ensures that the system always chooses the same supplier as the main supplier.

  • Section "Alert Types (English)"

           The "Created by" column of alert type 7822, needs to be changed as follows:

           Old text:

           DRP Service

           New text:

           DRP Stability Rules

  • Section "DRP Approval Rules"
    • The bulletpoint "MAXTOTVAL" needs to be changed as follows:

           Old text:

           MAXTOTVAL

           DRP has changed a scheduling agreement schedule line, whereby the total quantity of the scheduling agreement exceeds the maximum allowed value. In this case, the system creates the alert 7886.

           On the Define Management Approval screen, you have defined the maximum allowed total quantity of the scheduling agreement in a profile for management approval in the Upper Limit for Total Quantity of SA field. You have specified this profile in the location product master data in Profile ID MaxVals field.

           To access the Define Management Approval screen, on the SAP Easy Access screen, choose  Advanced Planning and Optimization -> Service Parts Planning (SPP) -> Planning -> Distribution Requirements Planning (DRP) -> DRP Approval.

           New text:

           MAXTOTVAL

           DRP has changed a scheduling agreement schedule line, whereby the total quantity of the scheduling agreement exceeds the maximum allowed value. In this case, the system creates the alert 7886.

           On the Maximum Values for Rules screen, you have defined the maximum allowed total quantity of the scheduling agreement in a profile for management approval in the Maximum Total Value of a Scheduling Agreement field. You have specified this profile in the location product master data in Profile ID MaxVals field.

           To access the Maximum Values for Rules screen, on the SAP Easy Access screen, choose  Advanced Planning and Optimization ->  Service Parts Planning (SPP) ->  Planning -> Distribution Requirements Planning (DRP) -> DRP Approval.

    • The bulletpoint MAX_VALUE needs to be changed as follows:

           Old text:

           MAX_VALUE

           DRP has manually changed a scheduling agreement schedule line, whereby this scheduling agreement schedule line exceeds the maximum allowed value. In this case, the system creates the alert 7835.

           On the Define Management Approval screen, you have defined the maximum allowed schedule line value in a profile for management approval in the Upper Limit for Schedule Line Value field. You have specified this profile in the location product master data in Profile ID MaxVals field.

           New text:

           MAX_VALUE

           DRP has changed a scheduling agreement schedule line, whereby this scheduling agreement schedule line exceeds the maximum allowed value. In this case, the system creates the alert 7835.

           On the Maximum Values for Rules screen, you have defined the maximum allowed schedule line value in a profile for management approval in the Maximum Sched. Agr. Schedule Line Value field. You have specified this profile in the location product master data in Profile ID MaxVals field.

Global Available-to-Promise
  • Chapter "Making Settings for Source Determination"

           From the path specified in the first step of the Customizing settings, the formulation "Rules-Based Availability Check ->" must be deleted.

           From the path specified in the second step of the Customizing settings, the formulation "Rules-Based ATP Check ->" must be deleted.

           The information about the settings for determining a supplier contract location must be included under "Customizing Settings".

           You can find these changes in the attached "Settings_for_Source_Determ.pdf" file.

  • Chapter "Settings for TPOP by Product Allocation"

           The following settings have to be included:

    • Requirements profile for TPOP
    • Determination of the initial location
    • Determination of a supplier contract location

           You can find these changes in the attached "Settings_for_TPOP_by_PAL.pdf" file.

  • New Chapter "Locations in Third-Party Order Processing"

           The new chapter "Locations in Third-Party Order Processing" must be included under "Third-Party Order Processing in Global ATP".

           You can find the new chapter in the attached "Locations_in_TPOP.pdf" file.

  • New Chapter "Pick from Goods Receipt"

           The new chapter "Pick from Goods Receipt" needs to be included under "Functions of the Redistribution".

           You can find the new chapter in the attached "Pick_from_Goods_Receipt.pdf" file.

  • Chapter "Order Due Lists"

           In the German version of this chapter, the following paragraph needs to be exchanged:

           "- AFL, in die das System Positionen speichert, die eine Bestätigung erhalten sollen

           Weitere Informationen finden Sie im IMG des SAP SCM unter Advanced Planning and Optimization -> Globale Verfügbarkeitsprüfung (Globale ATP-Prüfung) -> Ereignisgesteuerte Mengenzuordnung -> Neuzuordnung von Auftragsbestätigungen (NAB) -> Auftragsfälligkeitslisten konfigurieren (Bestätig. abgeben)."

           This paragraph needs to be exchanged by the following paragraph:

           "- AFL, in die das System Positionen speichert, die eine Bestätigung erhalten sollen

           Weitere Informationen finden Sie im IMG des SAP SCM unter Advanced Planning and Optimization -> Globale Verfügbarkeitsprüfung (Globale ATP-Prüfung) -> Ereignisgesteuerte Mengenzuordnung -> Neuzuordnung von Auftragsbestätigungen (NAB) -> Auftragsfälligkeitslisten konfigurieren (Bestätig. erhalten)."

  • Chapter "Event-Driven Quantity Assignment (SCM-APO-ATP-EQA)"

           In the "Features" section, the list of activities that can trigger EDQA events must be enhanced with the following activities:

    • Changing the refurbishment order
    • Changing the planned order
  • Chapter "EDQA Event: Reassignment of Order Confirmations"

           In the "More Information" section, the navigation path must be corrected.

           The old text is the following:

           "For more information about the ROC event, see the SAP Library for SAP Customer Relationship Management (SAP CRM) under  Components and Functions -> Sales -> Availability Check -> Availability Check using SAP APO -> Additional ATP Functions in Service Parts Management -> Controlling of the ATP Check in the Sales Order -> Reassignment of Sales Orders."

           The new text is the following:

           "For more information about the ROC event, see the SAP Library for SAP Customer Relationship Management (SAP CRM) under  Components and Functions -> Sales -> Availability Check -> Availability Check using SAP APO -> Additional ATP Functions in Service Parts Management -> Controlling the ATP Check in the Sales Order -> Reassignment of Order Confirmations."

  • Chapter "EDQA Event: Backorder Processing"

           In the "Use" and "Process" sections, the list of activities must be enhanced with the following activities:

    • Changing the refurbishment order
    • Changing the planned order
  • Chapter "Order Due Lists"

           In the "Prerequisites" section, the title of the Customizing activity "Global Availablity Check (Global ATP Check)" must be replaced by "Global Available-to-Promise (Global ATP)".

           In the "Features" section, the last bullet point must be corrected.

           The old text is the following:

           "ODLs with items that can lose their confirmation

           Event-driven quantity assignment uses these ODLs in processes of the type Quantity Assignment to Order Due Lists."

           The new text is the following:

           "ODLs with items that can lose their confirmation


           Event-driven quantity assignment uses these ODLs in processes of the type Reassignment of Order Confirmations."


**********************************************************************************************************************************************
The following corrections are available in the documentation DVDs for SAP SCM 7.0 (material number 50092364) that are available as of May 2009.

Transportation Planning/Vehicle Scheduling (TP/VS)
  • Chapter "TP/VS-Specific Customizing Settings in SAP APO": The bullet point "Transportation modes (only relevant for automatic shipment generation)" has to be deleted.
  • Two new chapters "Automatic Release to Shipment" and "Configuration of the Automatic Release to Shipment" have to be inserted under "Dynamic Route Determination".

           You can find the new chapters in the attached file "Automatic_Release_To_Shipment_70.pdf".
Service Parts Planning (SPP)

  • Chapter "Calculation of EOQ and SFT Using Poisson Distribution" must be changed as follows:
    • Section: "Process", step 2., "The EOQ is at least twice as large as the average demand size per order item." must be deleted.
  • Chapter "Fixed Demands and Fixed Receipts" must be changed as follows:
    • Section: "Displaying Fixed Demands and Fixed Receipts" a second example must be inserted. For more information, see Attachment "Example.pdf".
  • Chapter "Calendar for Determining Procurement Lead Times" the calendar "synchronization calendar for goods receipt" must be added in table 1. as follows:
    • Synchronization calendar for goods receipt      Transportation lane master data under Product-Specific Transportation Lane in Parameter area
  • Chapter "Calendar for Determining Procurement Lead Times" the lead time "synchronization of start of goods receipt" must be added in table 2. as follows:
    • Synchronization of start of goods receipt    Synchronization calendar for goods receipt    Synchronization calendar for goods receipt
  • Chapter "Data Realignment for Change to Location Determination Proc. Lean" must be added. For more information, see attachment "Data_Realignment.pdf".
  • Chapter "Service to Check Data Upload is Processed by BI RDA" must be added. For more information, see attachment "Check_Data_Upl.pdf".
  • Chapter "Updating Supersession Obsolescence" must be added. For more information, see attachment "Upd_Sup_Obs.pdf".
  • Chapter "Update Rules for Updating in 9ARAWDAT and 9ADEMAND" must be changed as follows:
    • Under section "Recognize Special Order Items" the following Note must be inserted: "The system does not support third-party order processing for SAP ERP, only for SAP CRM. It does not check produce-to-order products in SAP ERP, either."


Global Available-to-Promise

  • Chapter "EDQA Event: Quantity Assignment to Order Due Lists"

           Abbreviation "MAFL" must be replaced by "EDQA".

  • Chapter "EDQA Event: Push Deployment" and "EDQA Event: Backorder Processing", "EDQA Event: Reassignment of Order Confirmation", and "EDQA Event: Quantity Assignment to Order Due Lists"

           Customizing path must be updated to match system texts.

           Old text:

           "You have made the standard settings for the SAP Business Workflow.

           For more information, see the IMG for SAP SCM under SAP Web Application Server -> Business Management -> SAP Business Workflow -> Maintain Standard Settings."

           New text:

           "You have made the standard settings for the SAP Business Workflow.

           For more information, see Customizing for SAP SCM under SAP NetWeaver -> Application Server -> Business Management -> SAP Business Workflow -> Maintain Standard Settings."

  • Chapter "Order Due Lists"

    • Abbreviation "AFL" must be replaced by "ODL.
    • Customizing path must be corrected.

                    Old text:

                    "ODL in which the system saves items that can issue confirmation

                    For more information, see the IMG for SAP SCM under Advanced Planning and Optimization -> Global Availability Check (Global ATP Check) -> Event-Driven Quantity Assignment -> Quantity Assignment to Order Due Lists  -> Configure Order Due Lists (Receive Confirmation)."

                    New text:

                    "ODL in which the system saves items that can lose a confirmation.

                    For more information, see Customizing for SAP SCM under  Advanced Planning and Optimization  -> Global Availability Check (Global ATP Check) ->  Event-Driven Quantity Assignment (EDQA) -> Reassignment of Order Confirmation (ROC) -> Configure Order Due Lists (Give Up Confirmation)."

  • Chapter "Processing of Order Due Lists"

           Abbreviation "AFL" must be replaced by "ODL.

  • Chapter "General Settings for Global ATP"

           The title of this chapter must be exchanged by the title "Settings for Global ATP".

           The figure depicting the general settings must be updated.

           Under "Features", the new section "Settings for the Product Availability Check" must be included.

           Under "Activities", the following sentence has to be included: "To make the settings for the product availability check, in Customizing for SAP Supply Chain Management (SAP SCM) choose Advanced Planning and Optimization -> Global Available-to-Promise (Global ATP) -> Product Availability Check."

           You can find the changes in the attached document "Settings_for_Global_ATP.pdf".

  • Chapter "Scheduling Using Configurable Process Scheduling"

           Under "Prerequisites", the following paragraph must be included: "If you want to use scheduling schema SCHEDL_RLD, you have defined that backorder processing considers the release date for requirements. To make this setting, on the 'SAP Easy Access' screen choose "Advanced Planning and Opimization -> Global ATP -> Backorder Processing -> Batch Backorder Processing", and select the 'Consider Release Date' checkbox in the filter on the 'Confirmation Situation' tab page."

           A "Features" section must be included describing the existing scheduling schemas, such as the following:

    • SCHEDL
    • SCHEDL_ROUTE
    • SCHEDL_SDD
    • SCHEDL_RLD
    • SCHEDL_TPOP
    • SCHEDL_MM

           A new chapter "Scheduling Using Route Determination" must be inserted under the chapter "Scheduling Using Configurable Process Scheduling".

           You can find the new chapter and the changes to the chapter "Scheduling Using Configurable Process Scheduling" in the attached file "Scheduling_With_Route_Determ.pdf".

           

Production Planning and Detailed Scheduling
The issues re splitting operations listed below only occur in the documentation DVD with the material number 50094468. The issues are resolved in the documentation DVD with the material number 50096046. To resolve the issue in your local documentation installation, copy the attached Plain HTML files and the HTML Help files in the relevant directories. The file names are SCM700_APO_PPS_OpSplit_en.zip and
SCM700_APO_PPS_OpSplit_de.zip.

  • Chapter "Splitting Operations"

           The "Splitting Operations" is not supported in SAP APO. Therefore, the chapter "Splitting Operations" was removed from the documentation. If statements in other chapters mention this function or refer to this function, these statements need to be corrected accordingly.

  • Chapter "Calculating the Resource Consumptions of an Activity"

           The "Splitting Operations" is not supported in SAP APO. Therefore, the following sentence needs to be deleted:

           "To prevent the resource capacity from being exceeded, you can specify in the production process model that the system is to automatically split an operation when an order is created."

  • Chapter "Calculation of the Duration of an Activity
    • The "Splitting Operations" is not supported in SAP APO. Therefore, the following sentence needs to be deleted:
    • "The system can split an operation automatically when an order is created."


Affected Releases
Software Component Release From Release To Release And subsequent
SCM700700700

Correction delivered in Support Package
Support Packages Release Package Name
SCM700SAPKY70006

Related Notes
154735924X7_TS: Special lock for SNP administration tools
1406424Implementation recommendations for APO 7.0 PP/DS