Great video! However, I have been trying to get a clear explanation of the "Switch GAP off" option, and you also didn't explain it very well. Every site I visit has either such poor English or such an imprecise explanation that I still don't understand what it is or how it will work...
With the checkbox "Switch GPA off" you can fill fields within a variant using SPA/GPA. SPA/GPA is a standard field within SAP Structure RSVAR that stores the information. RSVAR is a structure used for transfer for variant maintenance. SPA/GPA parameters are stored in SAP memory. Fields can be filled here across all transactions. The SAP memory is available to the user during a logon. The storage of values in SPA/GPA parameters is user-specific. This attribute appears only if you have created the corresponding selection criterion using 'MEMORY ID xxx'. You can switch the SPA/GPA handling on and off in the variant. This means that fields filled using SPA/GPA appear with their initial values after you have loaded a variant in which those fields have an initial value. Related to the SPA/GPA parameters (SAP memory) is the ABAP memory. If a field supports a parameter id, the checkbox/column is visible. SPA/GPA is not active in background processing.
Thanks man but I have a question: You succeed completing the 1st "Posting date" field with the variant but how can we set the variant to fill the second field too? In my case I only want to fill the second field, the 1st field needs to be empty. Thanks for your help
Thank you so much. What exactly do you mean with "first posting date" and "second posting date"? So what kind of fields? If you want to have a range within the selection criteria you can choose "less than or equal to" instead of "equal" to achieve a range.
Fantastic, very good explaination !!! ❤but here I have a problem. I am end user and have created several variants (10) within last year. These variants have saved my time a lot. A few weeks ago our admin has deleted ALL of them, telling me end user is not allowed to create variants. He says: there is not enough space if every user would have so many, is it true? Does it run into a limited table? I considered it for end users ? Is it really only for admins? For me it would be ok with a rule, for example, all users create with Z_....then it is clearly a user variant. Or, Admin provides variants for our whole department (admin deleted all variants of my colleagues, too). All of us loose valued time now. I cannot really find info about it, is it for end users or only for admins. Pls, don't get me wrong, I presume admin wants to keep ABAP table under control, but now we all need much more time with manual settings. Is there any way to solve the problem for all sides? Thank you in advance. Sonja😊
Dear Sonja, Thank you for your kind words and insightful question ☺ Variants are designed to meet the individual needs of SAP users. They are designed to save time by eliminating the need to repeatedly enter the same data. However, it is important to follow the rules and policies set by your SAP Basis and Business department. If they prohibit the creation and use of variants, it is important to follow these guidelines. Variants are stored in tables such as VARID, VARIT, and VARI. Of course a lot of entries in a table can slow down the usage of these tables. But there are usually no restrictions on the number of variants that can be created for a program. However, some transactions may have restrictions on variants (e.g. Generic Articles - help.sap.com/docs/SAP_S4HANA_ON-PREMISE/bc6b9325fedd4344a84412b2195064fa/d28665066c354e429f032617d664590f.html?locale=en-US). I do not currently see any changes to creating user-specific variants. However, I recommend that you discuss your need for variants again with your SAP Basis (Admins). You can explain the importance of variants in your daily work with the SAP system and explore possible solutions, such as using prefixes (e.g. based on the first letter of your first and last name) and limiting the number of variants to avoid cluttering the variant catalogue. I wish you the best of luck in finding a solution. If you have any further questions, please let me know.
Your Admins are fools if they are not allowing you to use Variants. It is one of the primary benefits of using SAP - the ability for users to save the criteria they input and share with other users.
Thank you - now I have also understood it, well explained👍🏼
The best video I have watched about SAP variants. Kudos.
Wow, what a great feedback. Thank you very much 😀
that helped me solve my problem, many thanks :)
Good to hear. You' re welcome :)
Great video :)
Thank you. Great video :)
SAP Variants can save you time while working with SAP transactions that offer a selection screen. What are your thoughts? 😊
I use variants a lot. Great video.
благадарю👍
👍
Great video! However, I have been trying to get a clear explanation of the "Switch GAP off" option, and you also didn't explain it very well. Every site I visit has either such poor English or such an imprecise explanation that I still don't understand what it is or how it will work...
With the checkbox "Switch GPA off" you can fill fields within a variant using SPA/GPA. SPA/GPA is a standard field within SAP Structure RSVAR that stores the information. RSVAR is a structure used for transfer for variant maintenance.
SPA/GPA parameters are stored in SAP memory. Fields can be filled here across all transactions. The SAP memory is available to the user during a logon. The storage of values in SPA/GPA parameters is user-specific.
This attribute appears only if you have created the corresponding selection criterion using 'MEMORY ID xxx'. You can switch the SPA/GPA handling on and off in the variant. This means that fields filled using SPA/GPA appear with their initial values after you have loaded a variant in which those fields have an initial value.
Related to the SPA/GPA parameters (SAP memory) is the ABAP memory.
If a field supports a parameter id, the checkbox/column is visible.
SPA/GPA is not active in background processing.
Thanks man but I have a question: You succeed completing the 1st "Posting date" field with the variant but how can we set the variant to fill the second field too? In my case I only want to fill the second field, the 1st field needs to be empty. Thanks for your help
Thank you so much.
What exactly do you mean with "first posting date" and "second posting date"? So what kind of fields?
If you want to have a range within the selection criteria you can choose "less than or equal to" instead of "equal" to achieve a range.
Fantastic, very good explaination !!! ❤but here I have a problem. I am end user and have created several variants (10) within last year. These variants have saved my time a lot. A few weeks ago our admin has deleted ALL of them, telling me end user is not allowed to create variants. He says: there is not enough space if every user would have so many, is it true? Does it run into a limited table? I considered it for end users ? Is it really only for admins? For me it would be ok with a rule, for example, all users create with Z_....then it is clearly a user variant. Or, Admin provides variants for our whole department (admin deleted all variants of my colleagues, too). All of us loose valued time now. I cannot really find info about it, is it for end users or only for admins. Pls, don't get me wrong, I presume admin wants to keep ABAP table under control, but now we all need much more time with manual settings. Is there any way to solve the problem for all sides? Thank you in advance. Sonja😊
Dear Sonja,
Thank you for your kind words and insightful question ☺
Variants are designed to meet the individual needs of SAP users. They are designed to save time by eliminating the need to repeatedly enter the same data. However, it is important to follow the rules and policies set by your SAP Basis and Business department. If they prohibit the creation and use of variants, it is important to follow these guidelines.
Variants are stored in tables such as VARID, VARIT, and VARI. Of course a lot of entries in a table can slow down the usage of these tables. But there are usually no restrictions on the number of variants that can be created for a program. However, some transactions may have restrictions on variants (e.g. Generic Articles - help.sap.com/docs/SAP_S4HANA_ON-PREMISE/bc6b9325fedd4344a84412b2195064fa/d28665066c354e429f032617d664590f.html?locale=en-US).
I do not currently see any changes to creating user-specific variants. However, I recommend that you discuss your need for variants again with your SAP Basis (Admins). You can explain the importance of variants in your daily work with the SAP system and explore possible solutions, such as using prefixes (e.g. based on the first letter of your first and last name) and limiting the number of variants to avoid cluttering the variant catalogue. I wish you the best of luck in finding a solution.
If you have any further questions, please let me know.
Your Admins are fools if they are not allowing you to use Variants. It is one of the primary benefits of using SAP - the ability for users to save the criteria they input and share with other users.