Report Painter

Coles Myer Report Painting Manual
















To be used to assist the report painting process


Compiled June 1998


Table of Contents



Report Painter Guide 3

Introduction 3
Tables 4
Library 5
Library Naming Conventions 9
Reports 10
Report Naming Conventions 10
Row Definition 11
Column Definition 12
Formula Column 13
GeneralData Selection 15
Include in Report Group 17
Report Groups 18
Report Group Naming Conventions 18
Sets 19
Basic Set 20
Single-Dimension Set 22
Set Naming Conventions 24
Variables 25
Variable Naming Conventions 28
Standard Layout 29
Standard Layout Naming Conventions 29
Header 30
Page/Control 31
Row Totals 32
Row Texts 33
Column Totals 34Column Texts 35
Representation 36
Assigning Standard Layouts and Other Formatting 37
Transporting Reports 38
Maintaining the Reporting Tree. 40
Editing the Reporting Tree. 40
Adding a new report to the Reporting Tree. 41
Creating and Assigning a Change Request. 43
Releasing a transport request 44
Troubleshooting 46



Report Painter Guide


IntroductionThe ‘Report Painter Guide’ has been designed for Report Developers and for use in the development and ongoing maintenance of reports. This guide will briefly cover all areas such as the structures within Report Painter, Naming Conventions, Maintenance of the Reporting Tree, Troubleshooting and any other information that assists in the quick and efficient development of reports. It is expectedthat this document would supplement a training course and then hand written notes would fill any questions you may have. We have tried to leave as much space as possible to write your own notes.

This document will not cover the Report Writer, as the Report Painter is effectively the Report Writer with a graphical front end. All reports developed as a part of the MGBT Project (Project Link) havebeen developed with Report Painter or ABAP (Advanced Business and Application Programming) which is the SAP programming language.

The following diagram shows the Report Painter component relationships:


















All changes to the reports or the reporting tree should be done in client 012 in MTD and then transported to production. See the subsequent sections ontransporting of reporting objects.


Tables


The SAP report painter can extract information from many tables including:

GLT0 – Reporting from GL (Only reports at a Company Code Level)
GLPCT – Reporting from PCA (Can report down to Profit Centre level)
CCSS – Reporting from CCA (Can report down to a Cost Centre level)

These are predefined tables within SAP that contain information and havebeen flagged for use by the RP.

The MGBT Project has so far only used the Profit Centre Accounting module for RP reporting (Table GLPCT).


Library


Transaction: FGRP – Information Systems>Adhoc Reports> Report Painter - Report Writer>Library>Create.

All reports are created in a library. A library defines the table and the table’s characteristics, key figures, and predefined columnsthat will be available for creating reports. More than one library can exist for each table. Several pre-defined libraries are delivered with SAP standard reports. These libraries should never be changed. The system delivered libraries should be copied as a reference when creating your own.

When the library is created, either a reference library or the table for which the library is beingbuilt must be input.

Save the library name then begin to build the library components.




Press the Header button to define whether the SAPGUI will be used or if a user-defined interface will be selected. If any authorizations are going to be defined for the use of the library, the group is entered on the header. If any reports are to be called up as a result of the reports created in...