MS64 - Create Simulation Version

SAP Transaction Code - Details

• Transaction Code: MS64

  Description: Create Simulation Version

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Production > Production Planning > Demand Management > Environment > Copy Version
  • Logistics > Production > Production Planning > Long-Term Planning > Planned Independent Requirements > Copy Version
  • Logistics > Production - Process > Production Planning > Demand Management > Environment > Copy Version
  • Logistics > Production - Process > Production Planning > Long-Term Planning > Planned Independent Requirements > Copy Version

• • Program: RM60SIMU

    Screen: 0

    Authorization Object:

  • Development Package: MDPB

    Package Description: Application development R/3 purchasing

    Parent Package: APPL

  • Module/Component: PP-MP-DEM

    Description: Demand Management

Smart SAP Assistant

• SAP Tcode: MS64 - Create Simulation Version

  
  Overview:
  The SAP transaction code MS64 is used to create a simulation version of a material master record. This allows users to test changes to the material master record without affecting the live version. 
  
  Functionality: 
  The MS64 transaction code allows users to create a simulation version of a material master record. This simulation version can be used to test changes to the material master record without affecting the live version. The simulation version can then be compared to the live version and any changes can be accepted or rejected. 
  
  Step-by-step How to Use: 
  1. Enter the MS64 transaction code in the SAP command field. 
  2. Enter the material number of the material master record you want to create a simulation version of. 
  3. Select “Create Simulation Version” from the menu. 
  4. Enter the required data for the simulation version and save it. 
  5. The simulation version is now created and can be used for testing changes to the material master record. 
  
  Other Recommendations: 
  It is recommended that users always create a simulation version before making any changes to a material master record, as this allows them to test changes without affecting the live version. Additionally, it is important that users always compare the simulation version with the live version before accepting any changes, as this ensures that only valid changes are made to the material master record.