Reports Fundamentals
·
Reports structure and print information
from a database.
·
Reports print and display documents in the
application.
·
The report data is collected and presented
on the screen or printed on the paper when the report is run.
·
The report description contains properties,
triggers, sections, controls, a request form, a request page and RDL data. The
last two components are required for reports that are developed for the
RoleTailored client. The following shows components of a report and how they
are related:
Properties
A
property is an attribute of an object, or its component, that characterizes and
specifies behavior of the parent in some ways, such as whether it is visible.
Triggers
Certain
predefined events that occur to a report cause the system to execute a
user-definable C/AL function. The event and the function together are called a
trigger.
Triggers in a
report can be divided into six categories:
·
Report triggers
·
Data item triggers
·
Section triggers
·
Request form triggers
·
Request page triggers
·
Control triggers
Report
triggers include OnPreReport that contains statements that are executed right
before the report is run, and OnPostReport that contains statements that are
executed right before the report execution is completed. Triggers in a report
are edited in the C/AL Editor.
Data Items
The data model of a
report is built from data items. A data item corresponds to a table. When the
report is run, each data item is iterated for all records in the underlying
table. When a report is based on more than one table, establish a hierarchy of
data items to control how the information is collected by indenting data items.
Sections
Reports
can be a printing or nonprinting report. A nonprinting report is used for
processing a certain task and does not produce a displayed output. A printing
report displays the result in the screen or prints output on the paper.
A
section is a visual element of a report. The visual element of a report
includes the sections. In a printing report, one or more sections can be
attached to each data item. There are several types of sections. Each has a
specific function. Usually, the bulk of the data is printed in the Body section
of a data item, whereas the Header section of the data item is used to print
information before any record of the data item is printed, such as column captions.
There can be reports where the Body section is not used at all, and all
information is printed in other sections.
Controls
The
information that is printed in the sections is made of controls. Controls are
also available in the request form and the request page.
Request Form
The
request form is the form that is run before the actual report begins execution.
It is used to collect requests and options from the user of the report of
things such as sort order or level of detail. The request form is run when the
report is run in the Classic client.
Types of Printing Reports
List Reports : A List report prints a list of records from
a table. This data item represents the
table being listed. The table is either a Master table or a Supplemental table.
Test Reports: A
test report is printed from a Journal Table. Its purpose is to test each
Journal Line according to certain criteria that are used for posting so that
all the errors can be found and fixed before posting. As soon as an error is
found during posting, processing stops and the error must be fixed before
posting can be tried again.
Posting Reports: A
Posting report prints from the Register table. It lists all the transactions
(ledger
entries) that are
posted into that Register. A Posting report can be printed as part of the Post
and Print option in a Journal.
Transaction Reports:
·
It lists all the ledger entries for each
record in the Ledger table.
·
It contains a
subtotal for each Master table record, and a grand total for all tables
printed.
·
It is used to view
all transactions for a particular Master record.
·
It has no standard
naming convention.
No comments:
Post a Comment