Ans: A Planning Version can be frozen and unfrozen using Function Module /SAPCS/TS_PAREA_VERSIO_FREEZE so that no further changes to the planning version can be done.
Ans: To use two tables on one screen of Planning Book/Data View – select indicator next to second page title and give name. Additional tab page is displayed in Planning Book Maintenance wizard to define the keyfigures for the second table.
Click Here <<< SAP CS
Ans: The categories defined in Category Group ST1 (can be maintained in table /SAPCS/CSCGC) determine the stock categories that are displayed in the Initial bucket in the Stock on Hand keyfigure. Subsequent buckets are dynamically computed.
Ans: Dynamic Alerts do not show up in the stand-alone alert monitor. Network alerts are to show pegging relationships.
Ans: The report for executing MassD in background job is MASSBACK.
Ans: SE93 – Transaction code for Transaction Code E.g. CRC1 Create Resource has txn code CRAH. So if you do not have authorization to create resource you can use SE93 and enter txn CRAH and then Test F8 button to go to the txn.
Ans: Report /SAPCS/CHECK_LOCATION_TYPE can be used to change location type (say from 1001 to 1002 or vice-versa) of existing locations in CS. The table to refer is /SAPCS/LOCMAP. SAP does not recommend this process.
Ans: To copy a process chain to another process chain, goto the Process Chain you want to copy and then type copy in the tool tar and hit enter. It will allow you to copy the Process Chain to another Process Chain that can be modified as per user’s requirement, saved, activated and used.
Ans: Use OLIX to first delete previous MRP planning versions. Then use MCB& to create the new MRP planning versions by choosing the appropriate version you want to create as ICO Version. The info structure in this case is S094.
Ans: Release Profile is used to release timeseries data from DP to SNP/PPDS. You need to define the DP Planning Area and timeseries keyfigure the data in which is released and the SNP Category Type (typically FA) to which data is released. You may maintain a Daily Buckets Profile it will define the number of working days (working days determined based on Shipping Calendar maintained for the location master) starting on and from the From Date if released online/ interactively or that many workdays of the planning horizon when release is carried out in background. The Period Split (blank, 1 and 2) field in the SNP2 tab of location-product master determines how demand plan is released to SNP from DP (how bucketed data is disaggregated to the workdays).
Ans: Master Data in Demand Planning primarily is Charcateristic Value Combinations commonly termed CVCs. CVCs are the planning combinations against which data is stored in keyfigures.
Procurement Type X – source selection is based on matching due date then priority then cost. If both In-house Production and External Procuremnet is possible then In-house Production (PPM) is chosen as source of supply.
Ans: PP/DS fixing Horizon defines the PP/DS time Fence – within that period if heuristic is run no orders get changed.
Ans: Reuse mode in Product Heuristic – makes the system to reuse orders already present in the heuristic run i.e. orders are not deleted and recreated.
Ans: Planning Procedure in Product Master (PP/DS) defines that when you convert a planned order to process order it is in Deallocated state and not Scheduled state and more.
Ans: SAP SCM 4.1 is the new available Supply Chain Management Solution offered by SAP. The SAP SCM 4.1 System includes SAP CS 4.1 (Advanced Planning and Optimization), SAP ICH 4.1 (Inventory Collaboration Hub) and SAP EM 4.1 (Event Management).
Ans: SAP SCM 4.1 is based on the SAP Web Application Server 6.40. All SAP SCM 4.1 Architecture Components can be installed on one hardware server, as long as this server is sized for all used application components.
Ans: SAP CS stands for SAP Advanced Planning and Optimization and is the planning component within the mySAP SCM solution.
Ans: No, SAP CS always requires a backend ERP system for execution functions. In most cases, the backend system is an SAP R/3 system.
Ans: No, SAP CS requires a separate server. The actual size of the SAP CS system may vary and depends on the data volume to be processed. You can find more details on this subject under the alias /sizing on the SAP Service Marketplace (//http:/service.sap.com).
Ans: Through the CS Core Interface (CIF) which supplies SAP CS with master and transaction data in real time. CIF is delivered through the R/3 Plug-In, which is something you have to install in your SAP R/3 system. This is the same Plug-In that you need for connecting a BW or a CRM system.
Ans: With SAP CS you have a real-time integration to SAP R/3. The minute you change something in one system, it is immediately being transferred to the other and vice versa. And that goes for all data, be it a sales order, a production order or a purchase order. You do not have to perform any batch jobs for transferring data between the systems.
Ans: No. You create and change master data exclusively in SAP R/3. If you want to work with SAP CS, you need to transfer the master data from the SAP R/3 system. Depending on the scenario you want to use in SAP CS, you may have to enhance the transferred data with SAP CS specific settings, which are not relevant to SAP R/3.
Ans: SAP Best Practices for Supply Chain Management. Choose one or more of the mySAP SCM business scenarios that SAP Best Practices for SCM provide.
Click Here <<< SAP CS