Enhance Your Report Painter/Report Writer Capabilities with Transaction GRCT

  • by Jayesh Narwaney, Senior SAP Support Specialist
  • October 15, 2005
Instead of using ABAP code to write a report in FI and CO, many users build a Report Painter/ Report Writer library using transaction MC27. However, this workaround has some drawbacks. Little known transaction GRCT solves these problems in most cases, and eliminates the need to use transaction MC27.
Key Concept
Super users and end users can use Report Painter/Report Writer tools to write their own reports. Giving them the ability to report on additional fields at their discretion shifts the report maintenance burden to them, saving SAP support groups time and effort normally spent creating and maintaining the reports.

Say a reporting requirement comes to you for a trial balance report by the Accounting Clerk field, which is maintained on the G/L account company code data. You cannot use standard reports or build a report using available Report Painter/Report Writer libraries, because it is not a characteristic on which it is standard to report. You must seek a solution elsewhere. You could resort to a custom ABAP report or a quick and easy SAP query, but these might not be cost-effective or efficient ways to handle the variants of that requirement.

Those familiar with logistics reporting transaction MC27 (create evaluation structure) could use it to create a new library based on the desired table or table view. Transaction MC27 is part of the flexible analysis capability of the Logistics Information System (LIS), which allows you to create a Report Painter/Report Writer library based upon any Data Dictionary (DDIC) table, several DDIC tables, or existing evaluation structures for logistics reporting. With MC27, you can use any other table that includes financial tables for reporting, so you are not limited to logistics tables.

However, creating a report library from MC27 and then building reports from it may not meet all of the requirements of the FI and CO modules. Soon you may come across some problems, such as:

  • You no longer get descriptions of certain characteristics that include the G/L account or profit center.
  • Many variables are created for the new library that will never be used, which makes selection of other variables difficult.
  • The Report Painter/Report Writer library is automatically created with a system-assigned name, which does not follow the desired naming convention.
  • The biggest problem is that transaction MC27 creates a basic key figure for each of the amount or quantity fields it comes across in the table used for defining a library. If you are using a totals table in your new library that accumulates key figures in various fields identified by each period, the issue you come across is, "How am I going to build a report when I don't have a combined key figure available to slice using period as my selection criteria?"

Jayesh Narwaney

Jayesh Narwaney works for a financial services organization as a senior SAP support specialist in the SAP production support department. He has an MBA in finance and more than nine years of SAP experience, including six as a consultant in the FI and CO modules. He now works on the FS-CD module, the industry solution for financial services in SAP.

See more by this author


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.