Do you want to play a crucial role in shaping Jet Global products?
Would be more intuitive for GP Jet Pro users. Many GP users think of their main or natural account segment as their account and get confused about how to filter on just the natural account vs the full account string. This renaming convention would parallel the way that the Jet Function Wizard changes "Global Dimension 1" and "Global Dimension 2" filters to the names of those global dimensions (depending on the language setting in Jet). If we did this you might rename "Account" in the GL Wizard to Account String/Full Account Sequence or something similar. If the Segment Name column in SY00300 is blank, you could default to Segment 1, Segment 2, and so on. One potential challenge is that the SY00300 table is company-specific; it's not something stored in the DYNAMICS database, so in theory it can differ by company. I can't recall ever having run into this though. You could also indicate in some way which is the Main Segment (indicated by the Main Segment Indicator field in the same table)
I concur with Gabriele's suggestion re: use of the user-friendly segment descriptions rather than generic names such as "Segment 1". In case it helps I'm attaching a sample screen shot to better describe the product suggestion.
If we were going to get really fancy, the GL function would be greatly improved by adding the following: 1. the ability to limit lists of accounts to only active accounts. Right now, in order to create replicators that list only active accounts, users need to use an NL function off of a GP view such as Accounts or Jet GL Account, as explained here. 2. Allowing users to pull back Segment descriptions (from GL 40200) in the same way that they can now pull back CategoryName or AccountName (this, again, is now built using an NL function). These are consistently requested by my students and involve functionality that's directly related to how the GL function already works.
As of now the dropdown lists for Categories and Accounts include their respective descriptions. It would be great if in the dropdown sample values for the Segments we included the Segment descriptions from the GL40200 table (where available).
Pulling from SY00300 would also allow us to only list the number of segments allowed by a particular company, rather than the system-wide limit listed in the DYNAMICS database, so the number of fields in the GL function would match the number of segments in a specific company.