XMLP DevelopmentGuide
XMLP DevelopmentGuide
INTRODUCTION TO XMLP
Version .50
CEDARCRESTONE INC.
Table of Contents
Introduction! 1
Structure of XMLP! 2
XML Source! 2
RTF! 2
Report Setup! 2
File Layout! 3
Application Package! 6
Name of report! i
Company
Design Helper! 10
Creating an RTF! 11
Start Word! 11
Data Source! 16
Report Definition! 18
Definition! 18
Template! 19
Output! 20
Understanding Security! 21
Roles! 21
What it is! 22
Name of report! ii
CEDARCRESTONE INC
Introduction
SQR Very flexible and can do calculations May not be supported in fusion, All
as well as run sql against the development must be done by
database developers
Crystal What you see is what you get. Easy Requires crystal. Everything must be
to develop in. driven via QUERY
XML Publisher What you see is what you get. Can Must have PeopleCode skills
be driven by query or peoplecode.
Can be called from the page or from
a process
Structure of XMLP
XML Source
Publisher requires an XML source to create a report. The two most common sources are Query and an XML File. A
query may be used if there is no nesting of children within the report. A file should be used if there are children records.
The XML file can be created by a variety of processes. In most cases an Application Package will be used to create the
XML File
RTF
The Rich Text File is the template for the report. This file is merged with the source to create the XML Report. This file is
created in Microsoft Word using the Oracle XMLP addition in word.
Report Setup
Once an RTF is created it must be linked to the data source. This is done via the PIA.
File Layout
Under the properties of the file layout it must also be set to XML
Application Package
Design Helper
Design Helper is an Oracle tool for MS Word that helps in the development of XMLP Reports. This tool should be
installed prior to creating the report. Navigate to Reporting Tools- XML Publisher-Setup-Design Helper to find the page
with the program. Install the program by clicking the link to download and install program on a Windows PC with Word.
Creating an RTF
Start Word
Start MS Word and create a template with static text. for example if you would like the word NAME: to appear on the
document you will need to type that in.
Inserting Fields
Fields can be inserted onto the page for level 0 without having to create a table. From the Template Builder menu, select
Insert-Fields. this will open up the fields box. You can drag the fields from this box to the template.
Level 1 data can be inserted into tables so that more than one row can be printed under a parent. The Tables can be
formated by MS word. To insert the table goto Template Builder- Insert- Table. This will open the Insert Table window.
Drag the nodes from the Left to the Right to build your table. If you decide to drop single nodes, the fields will need to be
dropped on top of the node name.
When you are done building the table click OK. the table will be inserted into the report.
The F and E are a for and end loop. To see or change their logic go to the Template Builder- Tools- Field Browser
Editing Tags
The tags may be edited to perform loops and breaks. When creating a table the F and E tags are created. the F tage
contains <?for-Each:ROWSET?> and the E is the <?end for-each?> If a new tag needs to be created. Copy any tag in
word by selecting the gray block and doing a ctrl-c. Paste the block where the new tag is needed. Now go into the
Field browser and edit the new tag. This will need to be done if you decide to create a report that does a page break by
student. Tags may not be used in the Header or Footer of a page.
Once the file has been created it must be saved as an RTF file and NOT a DOC file. Go to Template Builder- Preview -
PDF. This will create a PDF Preview. You may also do a preview within word by selecting RTF for the preview
Once the preview looks correct you can continue on building the data source and template definitions.
Data Source
A Data Source is the file that feeds the merge process. Each report must have a data source. To Add a data source
goto Reporting Tools-XML Publisher- Data Sources
The Data Source Name should be the same as the report name. Since we created an XML file out we will use the XML
File as the source
The Schema File is used for bursting. Bursting is the ability to send parts of the report to different departments.
Report Definition
The Report Definition ties the Data Source to the RTF file. This must be done prior to running the application. The
Definition name should be the same as the name specified in the code. This is located under Reporting Tools-XML
Publisher-Report Definition.
Definition
This page contains basic information about the report. The file formats are related to the template that was created. For
our example we are using RTF. The status must be Active prior to running
Template
The Template page is where the RTF is uploaded. A report may have more than one template. The Status need to be
active prior to running
Output
The Output page is the where the output format is set.
The Default value will be used by the program during run time.
Understanding Security
Roles
Peoplesoft has two different roles need for XMLP development.
The Power User role allows users to add Query Data Sources and change the RTF Templates. The Report Developer
role allows for the addition of File Data Sources and RTF Development. These roles give access to the pages as well as
access to the technology.
What it is
A template project has been created for XMLP. This template contains the code needed for a simple App Engine/App
Package XMLP Process. The Code can be used as an example on how to create your own XMLP. The Project is called
ASU_XMLP_TEMPLATE. It contains a file layout, application engine, and app package. This template will help with the
creation of the XML file.
How to use it
Clone the objects within the template. Once you have cloned objects do the following find and replaces as highlighted
within the table below. Once you have completed those steps go on to the Next Steps section. All the code that needs
to be changed is under Report. The code under the Util does not need to be touched.
Child record for the select ASU_XMLP_CHILD The name of your child
record
File Layout Defn that shows ASU_XMLP_TEMPLATE_FL Your File Layout Name
Parent Child relationship
Next Steps
Once the changes have been made, criteria needs to be added to the parent and child selects. You must join the child
record to the parent record to preserve the relationship. Other criteria may be added as well. The two SQL Objects that
will need to be touched are highlighted below in the table.
&SQL_HDR The SQL is used to drive the report. The criteria used here
is to limit the rows that come back. If a row is not selected it
will not be printed on the report. In most cases this SQL will
do a select all since the App Engine does the limiting of
data.