How to use S_AP9_75000087 - IMG Activity: APO_PPS_CDPSC4

SAP Transaction Code - Details

• Transaction Code: S_AP9_75000087

  Description: IMG Activity: APO_PPS_CDPSC4

  Release: S/4HANA only

  Menu Path:

  • Logistics > Advanced Planning > Production Planning > Environment > Current Settings > Maintain Time Profiles

• • Program: SAPLS_CUS_IMG_ACTIVITY

    Screen: 200

    Authorization Object:

  • Development Package: APOC

    Package Description: IMG/Customizing for APO

    Parent Package: /SAPAPO/APO_STRUCTURE

  • Module/Component: SCM-APO-CA

    Description: APO Cross-Application Components

Smart SAP Assistant

• SAP Tcode: S_AP9_75000087 - IMG Activity: APO_PPS_CDPSC4

  
  Overview: 
  S_AP9_75000087 is an SAP transaction code used to access the IMG Activity APO_PPS_CDPSC4. This activity is part of the Production Planning and Detailed Scheduling (PP/DS) component of the SAP Advanced Planning and Optimization (APO) module. 
  
  Functionality: 
  The IMG Activity APO_PPS_CDPSC4 allows users to define the parameters for the Capacity Planning and Detailed Scheduling (CDPS) process. This includes setting up the planning horizon, defining the scheduling parameters, and configuring the capacity requirements. 
  
  Step-by-step How to Use: 
  1. Enter transaction code S_AP9_75000087 in the SAP command field. 
  2. Select IMG Activity APO_PPS_CDPSC4 from the list of activities. 
  3. Set up the planning horizon by entering a start date and end date for the planning period. 
  4. Define the scheduling parameters, such as the scheduling type, scheduling direction, and scheduling interval. 
  5. Configure the capacity requirements by entering a capacity requirement type, capacity requirement unit, and capacity requirement value. 
  6. Save your changes and exit the activity. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the parameters available in IMG Activity APO_PPS_CDPSC4 before making any changes to ensure that they are properly configured for their specific needs. Additionally, users should always test their changes in a non-production environment before deploying them in production.