How to use OLMRLIST - Gérer variante de liste

SAP Transaction Code - Details

• Transaction Code: OLMRLIST

  Description: Gérer variante de liste

  Release: S/4HANA and ECC 6

• • Program: SAPMSHD0

    Screen: 500

    Authorization Object:

  • Development Package: MRM

    Package Description: Appl. Development: R/3 Decentralized Invoice Verification

    Parent Package: APPL

  • Module/Component: MM-IV-LIV

    Description: Logistics Invoice Verification

Smart SAP Assistant

• SAP Tcode: OLMRLIST - Gérer variante de liste

  
  Overview:
  The SAP transaction code OLMRLIST is used to maintain list variants in the SAP system. List variants are used to define the selection criteria for a list of data that is displayed in a report. This transaction code allows users to create, change, and delete list variants. 
  
  Functionality: 
  The OLMRLIST transaction code allows users to maintain list variants in the SAP system. List variants are used to define the selection criteria for a list of data that is displayed in a report. This transaction code allows users to create, change, and delete list variants. 
  
  Step-by-Step How to Use 
  1. Enter the transaction code OLMRLIST into the command field and press enter. 
  2. Select the “Create” button to create a new list variant. 
  3. Enter the name of the list variant and select “Continue”. 
  4. Select the fields that you want to include in the list variant and select “Continue”. 
  5. Select the “Save” button to save your changes. 
  6. Select the “Back” button to return to the main screen of the transaction code. 
  7. To change an existing list variant, select it from the list and select “Change” button. 
  8. Make your changes and select “Save” when you are finished. 
  9. To delete an existing list variant, select it from the list and select “Delete” button. 
  10. Confirm your deletion by selecting “Yes” when prompted. 
  
  Other Recommendations: 
  It is recommended that users take caution when creating or changing list variants as they can have a significant impact on reports that use them for selection criteria. It is also recommended that users back up their changes before saving them in case they need to revert back to an earlier version of their changes.