Report Manager is built in any 10g application, there is scheduling,
conservation and viewing result(pdf, xls), works with Report Server, minimum additives in code trigger RDF
(5 added lines without change the logic), universal screen of the acceptance parameter,
start RDF, stored procedures, Unix scripts asynchronous functioning,
possibility to kill report, creation Excel files with spredsheets...
The Manager for object defines:
- Report
- Parameters
- Static and dynamic value sets(for parametes checking)
- Creating SQL script for change request
User interface:
- Start the report/procedures
- Set Parameters
- Scheduling and sending mails after job completing
- Save and view job results
As a part of subsystem, but can work absolutely apart,stored package exists,
which got parameters creates on server database file Excel.
Procedure parameters:
- Query text
- File path
- Query parameters list
The main parameter - a select statement with parameters(as bind variable, type, :P_CUSTOMER)
and parameters name-importance-type themselves and else much what in the manner of XML.
In select text it possible to use the special language,
which covers all possibility a trigger and placeholders Oracle*Reports
and gives possibility to build select optimally , that there is, from experience
I see that if user does not use layout and he needs Excel,
all possible set for minute moreover final select is got such that DBA remain complacent.
And Excel file is got cultural, in colour, there is separate spredsheet,
where appear select user parameters, headline, which has assigned the user in aliases of select fields.
Language commands:
- VAR CHAR | NUMBER ;
- EXPR ;
- BEFORE {PL/SQL block} ;
- AFTER {PL/SQL block} ;
- IIF_EXPR {boolean expression} {String if true} {String if false} ;
- IS_NOT_NULL {Bind variable} {String if Bind variable is not null} ;
- IS_NULL {Bind variable} {String if Bind variable is null} ;
- TITLE {Title};
- BOTTOM_SUM {Total bottom title} B C ...Z ;
- ROW_SUM {Total column title} B C D ... Z;