How to use S_AHR_61009311 - IMG-AktivitSt: OHAQTI210

SAP Transaction Code - Details

• Transaction Code: S_AHR_61009311

  Description: IMG-AktivitSt: OHAQTI210

  Release: S/4HANA and ECC 6

• • Program: SAPLS_CUS_IMG_ACTIVITY

    Screen: 200

    Authorization Object:

  • Development Package: P13C

    Package Description:

    Parent Package:

  • Module/Component:

    Description:

Smart SAP Assistant

• SAP Tcode: S_AHR_61009311 - IMG-AktivitSt: OHAQTI210

  
  Overview: 
  S_AHR_61009311 is an SAP transaction code used to access the IMG-AktivitSt OHAQTI210 activity in the SAP system. This activity is used to configure the settings for the Quality Inspection (QI) process. 
  
  Functionality: 
  The IMG-AktivitSt OHAQTI210 activity allows users to configure the settings for the Quality Inspection (QI) process. This includes setting up the inspection lot size, defining the inspection type, and setting up the inspection plan. It also allows users to define the sampling procedure and set up the inspection characteristics. 
  
  Step-by-step How to Use: 
  1. Access the IMG-AktivitSt OHAQTI210 activity by entering S_AHR_61009311 in the SAP transaction code field. 
  2. Set up the inspection lot size by entering a value in the “Lot Size” field. 
  3. Define the inspection type by selecting an option from the “Inspection Type” dropdown menu. 
  4. Set up the inspection plan by entering values in the “Inspection Plan” fields. 
  5. Define the sampling procedure by selecting an option from the “Sampling Procedure” dropdown menu. 
  6. Set up the inspection characteristics by entering values in the “Inspection Characteristics” fields. 
  7. Save your changes by clicking on “Save” at the top of the screen. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the settings available in this activity before making any changes, as incorrect settings can lead to inaccurate results or errors in the QI process. Additionally, it is recommended that users test their changes in a test environment before applying them to a production environment, as this will ensure that any errors are caught before they can cause any issues in production.