Improve Functional Screen Tuning with SAP Transaction Variants

  • by Martin Gillet, SAP HR Consultant, Cogilius bvba
  • May 15, 2008
Create a dedicated transaction and screen variant for your common standard transactions — without extensive programming. Learn how to adapt the standard screens beyond the usual customizing configuration and use transaction and screen variants to best serve your business requirements.
Key Concept

A transaction and screen variant is a functionality of SAP’s QuickWin that enables flexible configuration for tuning the standard screen. You can use this functionality in parallel with your standard customizing tool and with an efficient authorization concept.

While working on different projects and teaching SAP classes, I often hear from SAP users that they cannot meet all their business requirements when using the customizing tool that SAP provides. In these cases, I direct them to a workaround: the transaction variant. In this article, I’ll illustrate two examples of this handy but unfamiliar functionality, which is available from SAP R/3 4.6B onwards. Functionality shown in this article is from SAP ERP 6.0.

Why Use the Transaction and Screen Variant?

Using a transaction and screen variant provides two major benefits. The first is that the standard configuration options, such as table T588M (infotype screen control), are often not sufficient in providing the flexibility that the implementation team needs. A second benefit is the SAP authorization concept, which checks the access to the infotypes using authorization object S_TCODE. For example, to access transaction code PA30 (HR maintain master data), the authorization team inserts the value PA30 into the authorization object using profile maintenance in transaction code PFCG.

On top of the transaction access clearance, SAP delivers the standard authorization check for HR master data, P_ORGIN. However, it is not possible to narrow the authorization down to the field level of each infotype. Transaction and screen variants, however, allow you to hide or set the field to display only inside the infotype at the field level.

Martin Gillet

Martin Gillet is an SAP-certified HR consultant (ECC 6.0, SAP R/3 Enterprise, and 4.0B) who works freelance on international projects. He graduated with honors in Human Resources Management from Belgian Haute Ecole Namuroise Catholique (HENaC). Martin has worked with SAP R/3 since 1997 in the chemical, catering, pharmaceuticals, telecommunications, food, banking, and oil industries. He has focused on SAP HR since 1998 and has other SAP expertise including XSS, LSO, E-Recruiting, CATS, Reporting, Authorizations, and SAP NetWeaver Portal. Martin is the author of Configuring and Customizing Employee and Manager Self-Services in SAP ERP HCM. The book explores the options for customizing ESS and MSS to meet specific business needs.

Martin will be presenting at the upcoming SAPinsider HR 2017 conference November 8-10, 2017, in Copenhagen. For information on the event, click here.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.