OSP2 - Repetitive Mfg Profile

SAP Transaction Code - Details

• Transaction Code: OSP2

  Description: Repetitive Mfg Profile

  Release: S/4HANA and ECC 6

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: MD4C

    Package Description: Customizing Repetitive Manufacturing

    Parent Package: APPL

  • Module/Component: PP-REM

    Description: Repetitive Manufacturing

Smart SAP Assistant

• SAP Tcode: OSP2 - Repetitive Mfg Profile

  
  Overview:
  The SAP transaction code OSP2 is used to maintain the Repetitive Manufacturing Profile. This profile is used to define the production process for repetitive manufacturing. It contains information about the production process, such as the number of operations, the sequence of operations, and the resources required for each operation. 
  
  Functionality: 
  The OSP2 transaction code allows users to create, modify, and delete repetitive manufacturing profiles. It also allows users to view and print existing profiles. Additionally, it provides a graphical representation of the production process, which can be used to quickly identify any potential problems or inefficiencies in the process. 
  
  Step-by-step How to Use: 
  1. Enter the OSP2 transaction code into the SAP command field. 
  2. Select the profile you wish to view or modify from the list of available profiles. 
  3. If creating a new profile, enter all relevant information such as number of operations, sequence of operations, and resources required for each operation. 
  4. If modifying an existing profile, make any necessary changes and save them. 
  5. To view a graphical representation of the production process, select “Display Graphically” from the menu bar. 
  6. To print a copy of the profile, select “Print” from the menu bar. 
  7. When finished, exit out of the transaction code by selecting “Exit” from the menu bar. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all aspects of the OSP2 transaction code before attempting to use it. Additionally, users should ensure that all changes made to existing profiles are thoroughly tested before being implemented in a live environment.