How to use CUST_VV_T685Z_M1 - Upper/Lower Limits for Conditions

SAP Transaction Code - Details

• Transaction Code: CUST_VV_T685Z_M1

  Description: Upper/Lower Limits for Conditions

  Release: S/4HANA only

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: ME0C

    Package Description: Customizing Purchasing

    Parent Package: APPL

  • Module/Component: MM-PUR-GF

    Description: Basic Functions

Smart SAP Assistant

• SAP Tcode: CUST_VV_T685Z_M1 - Upper/Lower Limits for Conditions

  
  Overview: 
  CUST_VV_T685Z_M1 is a SAP transaction code used to set upper and lower limits for conditions in the SAP system. It is used to define the range of values that can be used for a particular condition type. This helps to ensure that the system is configured correctly and that all conditions are within the specified range. 
  
  Functionality: 
  The CUST_VV_T685Z_M1 transaction code allows users to set upper and lower limits for condition types. This helps to ensure that all conditions are within the specified range and that the system is configured correctly. The transaction code also allows users to view existing upper and lower limits for condition types, as well as modify or delete them if necessary. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code CUST_VV_T685Z_M1 in the command field. 
  2. Select the condition type for which you want to set upper and lower limits. 
  3. Enter the upper and lower limits for the condition type. 
  4. Click “Save” to save your changes. 
  5. To view existing upper and lower limits, select “Display” from the menu bar. 
  6. To modify or delete existing upper and lower limits, select “Change” or “Delete” from the menu bar respectively. 
  7. Click “Save” to save your changes or “Cancel” to discard them. 
  
  Other Recommendations: 
  It is important to note that setting upper and lower limits for condition types can have an impact on other areas of the system, so it is important to ensure that any changes are made with caution and with full understanding of their implications. Additionally, it is recommended that users test any changes in a non-production environment before making them in a production environment.