Automate

 View Only

  • 1.  Script Cataloging & Organization

    Employee
    Posted 07-09-2025 12:05

    Hi Customers, 

    This discussion keeps coming up and this topic applies to desktop and server customers to varying degrees. 

    I am curious how the community is handling this. Please chime in and help us create a pool of ideas others can pull from. Thank you!

    1. How do you organize scripts? by Tcode? by functional area? by team?
    2. If you have multiple MM02 scripts, how do you make sure the purpose is clear? where do you document what fields does it update etc 
    3. What naming conventions do you follow? can you share examples?
    4. How and where do you document what the script was created for?  
    5. How often do you audit your script library and clean up what is no longer needed?
    6. What are your favorite reports you use for script usage insights?
    7. Any other script management best practices that you want to share?


    ------------------------------
    Jayasri Varyani
    SE
    *Precisely Software Inc.
    ------------------------------


  • 2.  RE: Script Cataloging & Organization

    Posted 07-11-2025 01:36

    hi,

    I always put the tcode at start of the script name. If it is based on Direct, often I put the related tcode and (shortened) name of the BAPI. I refer to specific conditions types and key combinations. The name roughly shows what it is meant for but that is sometimes difficult, in that case I try to put more generic words (like "MRP1 and 2" rather than naming the fields specifically). To keep scripts lean, not always all fields are in it. We do not have Studio Runners, hence, I am asked for a template (with short explanation what they want to do) by data stewards and I provide them. In that way I have control (specifically related to versions) and give them the correct one. Several scripts/templates are with a specific purpose, sometimes only used once. I do not make fancy templates with VBA etc. Some scripts are only initiated/executed by me, think of some housekeeping kind of tasks. Although I know that I could share via Evolve platform, I am struggling with access management and I would need more explanation text per template what it is about. I try to not pollute but that is difficult in the pace of day. I only occasionally look at usage. When very specific, in the template, I provide additional explanation to the data stewards. Some examples of names: VK12_ZPN0 KC4 SO_CustHier_Act_PH1_PH2_PH3_PH4_Material, BP0_FLCU01 Customer Relationship Attribute Change, C202_Change recipe operations, ME12_Change Info Rec and or add pricing, VB02_ZL01-ZE01_DELETE keycomb_1_Listing or Exclusion.



    ------------------------------
    Ed Meiners
    Lead Consultant MDIM
    Wessanen Nederland Holding BV
    Amsterdam
    ------------------------------

    Original Message


  • 3.  RE: Script Cataloging & Organization

    Posted 07-11-2025 09:10

    Hi Jayasri

    1. How do you organize scripts? by Tcode? by functional area? by team?
      1. Currently, we organize by team and then by function or region within the team
    2. If you have multiple MM02 scripts, how do you make sure the purpose is clear? where do you document what fields does it update etc 
      1. We try to name the scripts in a way that makes the function clear
    3. What naming conventions do you follow? can you share examples?
      1. We have developers around the globe, so naming convention isn't consistent. For myself (and those I have personally trained), we put the t-code first (or BP if it's a bapi), then name based on the main function of the script/query. Example screenshot attached
      2. We also align the name of the template to make it easy to match them up.
    4. How and where do you document what the script was created for?  
      1. We don't, I think there are maybe a small handful with documentation as to why, as they were scenarios that have higher level of visibility. Otherwise, there is no "why" documented. We use Studio globally and for almost every function/line of business in the company, so any process that can be made more efficient, we do it.
    5. How often do you audit your script library and clean up what is no longer needed?
      1. Not often, however, if there is a need to recreate a script, the old version will be removed. Or if a team reaches out asking to remove one, it will get removed. A lot of times I will keep a backup stored locally just in case as you never know if they are going to change their mind, or provided the wrong script name.
    6. What are your favorite reports you use for script usage insights?
      1. We don't use the reporting function much. I will use Foundation "dashboard" reports if I need to show where our most used t-codes and biggest savings are when management asks.
    7. Any other script management best practices that you want to share?
      1. Don't create specific libraries unless it's absolutely necessary. I did this early on and am wishing I hadn't. Just create folders, and set proper access.

    Naming Convention Example:



    ------------------------------
    Vanessa Kutasi
    Foundation Admin./Application Analyst II
    Idexx Operations, Inc.
    USA
    ------------------------------

    Original Message