Creating xml publisher documents with people code

Creating XML Publisher Documents with PeopleCode
Randall Groncki
Northrop Grumman Corporation

Introduction
XML Publisher is a powerful reporting tool available with PeopleTools versions 8.48 and higher. Though
most demonstrations and training focus on Query based XML Publisher reports, the tool’s real power is
when it is embedded into the application pages where users would naturally expect the reports.

Query based XML Publisher reports are ad-hoc with better formatting than Excel spreadsheets. Multi-
user use of a report requires public queries which are open to modification by any user with PSQuery
access. Reports based upon private, protected queries can only be viewed by the query owners.

The delivered PeopleCode XML Publisher Application packages allow full control of the reports with more
options to the designer. The data source structures are protected from end users while the developer has
multiple options to invoke and deliver the reports.

This paper discusses using PeopleCode and other tools within the Application Designer to create and
deliver XML Publisher reports within the PeopleSoft application. It assumes that the user is familiar with
the fundamentals of creating and XML Publisher Report Definition:

1. Define the data source and provide sample XML data file

2. Create the XML Publisher Report template using the sample XML data file

3. Tie all parts together with security in a XML Publisher Report Definition

The paper is divided into three sections:

• XML File Creation discuses using four different tools to generate the source data file for the report

• Report Evocation and Creation shows how to use the delivered XML Publisher Application
Packages to generate the report and combine multiple reports into a single result file if needed.

• The Output section demonstrates a few ways to present the report to the user including the
Report Repository, popup window and emailing the report.

XML File Creation
New for PeopleTools version 8.50, XML Publisher reports can only use XML Files, Queries and
Connected Queries as data sources for reports. Prior versions of the tool also included options for
XMLDoc & Rowsets Objects as data sources. Though no new data sources may be defined as type
Rowset or XMLDoc, backward compatibility allows XML Publisher reports created in earlier tools versions
using these objects to continue functioning.

Since all versions use XML Files as a data source, this section will focus on generating XML Files using
four different methods:

• Manual, freehand creation of an XML File

1
Collaborate 10 Copyright ©2010 Northrop Grumman

• File Layout Object

• Rowset Object

• XMLDoc Object

Premise for all XML File Creation Examples.

In order to demonstrate the differences of the four XML File creation techniques, all demonstrations will
use the same report premise: A letter to all employees summarizing their current job and showing all
training taken through the company. This is a complex data set with a parent/child relationship. Each
Root
employee will get a separate page in the report. For each employee, there will be zero or more training
entries. See Appendix A for the function populating (Parent Record)
Employee Record: X_EE_RPT_LTR_VW this data structure. The function returns this Rowset
object:
• EMPLID

• NAME

• DEPTID

• LOCATION

• JOBCODE

• COMPRATE

• CHANGE_PCT

• LOCATION_DESCR

• JOB_DESCR

• COMPANY_DESCR

Training Record: X_TRAINING_VW (Child Record)

• EMPLID

• COURSE_START_DT

• COURSE

• SESSION_NBR

• COURSE_TITLE

• COURSE_END_DT

• ATTENDANCE
Freehand creation of an XML File
• TRAINING_REASON

• COURSE_GRADE

• PREREQ_MET 2
• DEPTID

• BUSINESS_UNIT

Manually creating an XML file by concatenating strings and tags may be the most expedient method for
small data files, but also the most error prone and the most work to build and maintain. The programmer
must create and track all opening and closing tags replicating an exact structure. Any errors will most
likely cause an error in the XML parser at read time.

In the example below, the field names from each of the records are used as field tags. Notice how the
root and Freehand Example ***/
/**** each record tag is closed out.
Local string &XML_String, &XML_Filename_path;
See Appendix B for the XML File created by this code.
Local File &oXML_File;
Local Rowset &RS_Employee, &RS_Training;
Local integer &i, &j, &f;
Local Record &X_EE_RPT_LTR_VW_REC, &X_TRAINING_VW_Rec;

&RS_Employee = LoadTestDataSet();

&XML_String = "<?xml version='1.0'?>";
&XML_String = &XML_String | "<root>";

For &i = 1 To &RS_Employee.ActiveRowCount
&XML_String = &XML_String | "<EMPLOYEE_DATA>";
&X_EE_RPT_LTR_VW_REC =
&RS_Employee(&i).GetRecord(Record.X_EE_RPT_LTR_VW);
For &f = 1 To &X_EE_RPT_LTR_VW_REC.FieldCount
&XML_String = &XML_String | "<" |
&X_EE_RPT_LTR_VW_REC.GetField(&f).Name | ">";
&XML_String = &XML_String |
String(&X_EE_RPT_LTR_VW_REC.GetField(&f).Value);
&XML_String = &XML_String | "</" |
&X_EE_RPT_LTR_VW_REC.GetField(&f).Name | ">";
End-For; /* employee fields */

/* run through child rowset */
&RS_Training = &RS_Employee(&i).GetRowset(Scroll.X_TRAINING_VW);
For &j = 1 To &RS_Training.ActiveRowCount

&X_TRAINING_VW_Rec = &RS_Training(&j).GetRecord(Record.X_TRAINING_VW);
&XML_String = &XML_String | "<TRAINING_DATA>";
For &f = 1 To &X_TRAINING_VW_Rec.FieldCount
&XML_String = &XML_String | "<" |
&X_TRAINING_VW_Rec.GetField(&f).Name | ">";
&XML_String = &XML_String |
String(&X_TRAINING_VW_Rec.GetField(&f).Value);
&XML_String = &XML_String | "</" |
&X_TRAINING_VW_Rec.GetField(&f).Name | ">";
End-For; /* child fields */
/* close the child rowset tags */
&XML_String = &XML_String | "</TRAINING_DATA>";

End-For; /* child rowset */
/* close the parent rowset tags */
&XML_String = &XML_String | "</EMPLOYEE_DATA>";
End-For; /* parent rowset */

/*close out the XML File Root */
&XML_String = &XML_String | "</root>";

&oXML_File = GetFile("FREE_HAND.xml", "W");
&oXML_File.WriteLine(&XML_String); 3
/* save file name and path for publishing */
&XML_Filename_path = &oXML_File.Name;
&oXML_File.Close();

File Layout method of creating an XML File

PeopleSoft’s File Layout Object allows us to quickly create XML files. Given the right conditions, this is
the fastest method to create an XML File.

Create a record structure reflecting your final XML file structure,
then, add those records accordingly to the file layout object.
Remember to correctly record the Parent/Child relationships of
the XML file on the file layout.

On the “Use” tab of the Properties box, define the file
layout type as “XML”.

4

The File Layout object is assigned to the file during after the GetFile statement. Then, the file object
inherits an internal Rowset Object reachable through PeopleCode.

In the example below, the data Rowset Object is copied directly into the File Layout Rowset Object since
they are intentionally identical. Then, the Rowset can be dumped to file with the “WriteRowset” method
of the File Object. Since the File Layout Type is defined as XML, PeopleSoft creates a properly formatted
XML File.

See Appendix C for the XML File created by this code.
Local File &XML_File;
Local Rowset &RS_Employee, &FILEROWSET;
Local string &XML_Filename_path;
Local string &my_xml;

/* output files */


&XML_File = GetFile("FILELAYOUT.xml", "W");
&XML_File.SetFileLayout(FileLayout.X_FILELAYOUT);

&FILEROWSET = &XML_File.CreateRowset();
&RS_Employee.CopyTo(&FILEROWSET);
&XML_File.WriteRowset(&FILEROWSET, True);
&XML_Filename_path = &XML_File.Name;

&XML_File.Close();

5

Rowset method of creating an XML File

The Rowset Method uses delivered PeopleCode Application Package “PSXP_XMLGEN” to generate both
the XML File and XML Schema file (XSD). In the example below, the data Rowset is passed to the class
method “getXSDSchema” and “getXMLData”. The method result is a string containing a XML or
XSD file. Write this string to the file object with one write statement.

Important to know about the XML File generated with this method is that field tags have “fld_” appended
to the front of the field names. Example: EMPLID becomes tag “fld_EMPLID” in the XML File. This has to
be accounted for in your template mapping.

This example creates both the schema and XML file.

• See appendix D for the XML File generated

• See appendix E for the XSD file generated

D import PSXP_XMLGEN:*;

Local PSXP_XMLGEN:RowSetDS &oXML_GENERATOR;
Local File &XSD_File, &XML_File;
Local Rowset &RS_Employee;
Local string &XML_Filename_path, &XSD_Filename_path, &my_schema, &my_xml;
Local integer &i;

/* Load data into rowset */

/* output files */

/* create xsd */
&oXML_GENERATOR = create psxp_xmlgen:RowSetDS();
&my_schema = &oXML_GENERATOR.getXSDSchema(&RS_Employee);
&XSD_File = GetFile("Rowset.xsd", "W");
&XSD_File.WriteLine(&my_schema);

/* Get filename and path for creating xml file */
&XSD_Filename_path = &XSD_File.Name;
&XSD_File.Close();

rem create sample xml file;
rem &my_xml = &oXML_GENERATOR.getXMLData(&RS_Employee, &XSD_Filename_path);
&my_xml = &oXML_GENERATOR.getXMLData(&RS_Employee, "");
&XML_File = GetFile("Rowset.xml", "W");
&XML_File.WriteLine(&my_xml);

/* save file name and path for publishing */
&XML_Filename_path = &XML_File.Name;
&XML_File.Close();

6

XMLDoc method of creating an XML File

The XMLDoc object is PeopleTools utility to manipulate XML Files in their native format. One of these
objects methods is to generate a formatted XML string from the current XMLDoc structure. The
developer creates an XMLDoc structure and adds “Nodes” to the document to create tags and structure.
The level the node is attached to determines the structure of the XML document.

Though this code may look similar to the freehand method, realize that the object is maintaining the
structure. The developer is not concerned with end tags and completing parent child structures for the
document. As each node is added, the value of that node is set.

When all the data has been moved to the XMLDoc object, use the “GenFormattedXmlString”
method of the object to create the entire XML file in one string. Then write that string to file.

See appendix F for the result XML File.
Local XmlDoc &inXMLDoc;
Local XmlNode &childNode, &textNode, &midNode, &rowNode;
Local Rowset &RS_Employee, &RS_Training;
Local Record &X_TRAINING_VW_REC, &X_EE_RPT_LTR_VW_REC;
Local integer &i, &j, &f;
Local string &Xml_String, &XML_Filename_path;
Local File &XML_File;


/* Create & Load XMLDoc */
&inXMLDoc = CreateXmlDoc("<?xml version='1.0'?><root/>");

&rowNode = &inXMLDoc.DocumentElement.AddElement("EMPLOYEE_DATA");
&X_EE_RPT_LTR_VW_REC = &RS_Employee(&i).GetRecord(Record.X_EE_RPT_LTR_VW);

For &f = 1 To &X_EE_RPT_LTR_VW_REC.FieldCount
&childNode =
&rowNode.AddElement(&X_EE_RPT_LTR_VW_REC.GetField(&f).Name);
&childNode.NodeValue = String(&X_EE_RPT_LTR_VW_REC.GetField(&f).Value);
End-For; /* record fields */

For &j = 1 To &RS_Training.ActiveRowCount
&X_TRAINING_VW_REC = &RS_Training(&j).GetRecord(Record.X_TRAINING_VW);
&midNode = &rowNode.AddElement("TRAINING_DATA");

For &f = 1 To &X_TRAINING_VW_REC.FieldCount
&childNode =
&midNode.AddElement(&X_TRAINING_VW_REC.GetField(&f).Name);
&childNode.NodeValue =
String(&X_TRAINING_VW_REC.GetField(&f).Value);
End-For; /* record fields */
End-For; /* training rowset */
End-For; /* employee rowset */

&Xml_String = &inXMLDoc. GenFormattedXmlString ();
&XML_File = GetFile("XMLDOC.xml", "W");
&XML_File.WriteLine(&Xml_String);
7
&XML_File.Close();

XML File Generation Considerations

Concurrency: Generating multiple versions of the same report simultaneously.

PeopleSoft by its very nature may have multiple, different users attempting to create the same
report at the same time. Ensure that your code accounts for this probability by making the file
names unique per each instance of the report. One Idea to accomplish this is to append the User
or Employee ID to the file creating a unique file name. Another method is to append the current
date/time stamp to the filename to force uniqueness.

If your report is popular, you could be littering the file server with thousands of no longer needed
XML files which will not endear yourself to the administrators. After your XML Publisher report
has been created, delete your source data file using the “delete” method of the file object.

Schema Files

For PeopleTools version 8.48 & 8.49, XML Publisher requires XML Schema files for the correct
mapping of tags to a PDF Template. You could include these for RTF (MSWord) templates, but
they were not necessary.

The easiest way to generate correct schemas for the generated XML Files is to use an XML File
editing utility such as XML Spy or XML Fox. XML Fox is a freeware utility that works very nicely.
These utilities can generate schemas from your final XML Files.

As demonstrated earlier, the Rowset method has a utility to generate the schema file at the time
the XML File is created.

Starting with PeopleTools 8.50, XML Publisher does not require a schema file for PDF Template
mapping. Only a sample data file is required.

Sample Files for defining XML Publisher Data Sources.

You must provide a Sample XML Data file when creating a new XML Publisher report. A good
idea is to execute a version of the XML File generation code using a sample or representative
employee. Another good idea is to, for the sample run, modify your code to put the XML Tag
names as values in the XML File. This will aid in mapping and formatting: do you have the right
field in the right place on your report.

House Keeping

Depending on data policies of the implementations site, it may be a good idea to delete the XML
Publisher Source files from the files directory after the report documents have been created. The
easiest way to delete the file is to re-open the file after the XML Publisher code is complete, then
use the “delete()” method instead of the “close()” method. This will remove the file from
the servers.

8

Report Evocation and Creation
Generating the Report

Once the XML File is generated, it’s very simple to create the report and give it to the user. The delivered
PeopleCode Application Package handles all the XML Publisher Report functions.

This example displays the report to the user in a new popup window on their display. Given the report
window, the user can print, save or do whatever they like with the result.

1) Import the application package and instantiate

import PSXP_RPTDEFNMANAGER:*;
&oXML_PUB = create PSXP_RPTDEFNMANAGER:ReportDefn("Report
Definition name");
&oXML_PUB.Get();

2) Set the data source
&oXML_PUB.SetRuntimeDataXMLfile(&XML_Filename_path);

3) Process the report

This process creates the report object itself. After this step, the developer just has to decide how
to present the report to the user.
/* Process Report */
&oXML_PUB.ProcessReport("", "", %Date, "");

/* save to clear think time functions */
DoSaveNow();

4) Display the output in a new popup window
&oXML_PUB.DisplayOutput();

Generating the report to a file on the server

XML Publisher creates directories and files under the Application Server temp file space during operation.
The fully qualified file name can be derived using a quick PeopleCode routine and properties of the
XML_Publisher object.
[...code creating report…]
In the example below, the resulting report’s fully qualified file name is placed in the
“&ReportFilePath” string variable.
DoSaveNow();

&ReportFileName = &oXML_PUB.ID | "." |
9
Lower(&oXML_PUB.GetOutDestFormatString(2));
&ReportFilePath = &oXML_PUB.OutDestination | &sDirSep | "RptInst" | &sDirSep
| &ReportFileName;

Combining XML Publisher PDF Reports

In some cases, it may be best to combine two existing PDF reports or split an existing PDF report into two
separate documents for population, then recombine them before delivery. Good examples are
government forms with dependent information. Where the number of dependents exceeds the available
positions on the form, the person would just attach an additional copy of that form page to the completed
document to report all dependents. Separating the report into person information and dependent
information, creating as many dependent pages as required and then recombining the two reports into
one for delivery is a method to accomplish the task.

XML Publisher delivers a PDF Join utility to PeopleCode through an internal Java class. The code
example below combines two PDF reports into one report.

import PSXP_ENGINE:*;
&oMerger = create PSXP_ENGINE:PDFMerger();

&PDF_Merge_Error = "";
&PDF_Merge_Array = CreateArray(&FirstReportFilePath);
&PDF_Merge_Array.Push(&SecondReportFilePath);

&PDF_Merge_Result = &oMerger.mergePDFs(&PDF_Merge_Array,
&PDF_Merge_File_name, &PDF_Merge_Error);

See Appendix G for a complete version of this PeopleCode event.

10

Output
The delivered application package contains several options for presenting the report:

1) Send to the PeopleSoft Report Repository:

&XML_PUB_Object.Publish(&sServerName, &reportPath, &sFolderName,
&processInstanceId);

2) Send the report to a printer:

&XML_PUB_Object.PrintOutput(&DestPrinter As string);

3) Send the report to a new popup window (shown above)

&XML_PUB_Object.DisplayOutput()

4) Mail the report

The following code sends the resultant XML Publisher report to the email address or addresses
contained the “&MAIL_TO” string.

[...code creating report…]
DoSaveNow();

&ReportFileName = &oXML_PUB.ID | "." |
Lower(&oXML_PUB.GetOutDestFormatString(2));
&ReportFilePath = &oXML_PUB.OutDestination | &sDirSep | "RptInst" |
&sDirSep | &ReportFileName;

&MAIL_FLAGS = 0;
&MAIL_CC = "";
&MAIL_BCC = "";
&MAIL_SUBJECT = &Email_Subject;
&MAIL_FILES = &ReportFilePath;
&MAIL_TITLES = "xml_pub.PDF";
&ret = SendMail(&MAIL_FLAGS, &MAIL_TO, &MAIL_CC, &MAIL_BCC,
&MAIL_SUBJECT, &MAIL_TEXT, &MAIL_FILES, &MAIL_TITLES, &MAIL_SENDER);

If Not (&ret = 0) Then
MessageBox(0, "", 299, 1, "Return status from mail %1" | &ret);
End-If;

11

Appendix A
Data set function for data source creation. This function populates and returns a complex RowSet object.

/*********************************************************/
/** Northrop Grumman **/
/** Information Technology **/
/** XML Publisher **/
/** XML File Generation Examples **/
/** Contact: Randy.Groncki@NGC.com **/
/*********************************************************/
import PSXP_XMLGEN:*;

Function LoadTestDataSet() Returns Rowset;
Local Rowset &RS_Training, &RS_Employee;
Local Record &JOB_REC, &LOCATION_TBL_REC, &COMPANY_TBL_REC,
&JOBCODE_TBL_REC;
Local integer &i;

/* create records */
&JOB_REC = CreateRecord(Record.JOB);
&LOCATION_TBL_REC = CreateRecord(Record.LOCATION_TBL);
&COMPANY_TBL_REC = CreateRecord(Record.COMPANY_TBL);
&JOBCODE_TBL_REC = CreateRecord(Record.JOBCODE_TBL);

/* create rowsets */
&RS_Training = CreateRowset(Record.X_TRAINING_VW); /* child rowset */
&RS_Employee = CreateRowset(Record.X_EE_RPT_LTR_VW, &RS_Training); /*
parent rowset */

/* Fill Parent */
&RS_Employee.Fill("where emplid like 'KU000%' and exists (select 'x'
from ps_training t where t.emplid = fill.emplid)");

/* Loop through parent rowset for processing on each row */

/* Fill child rowset */
&RS_Training.Fill("where emplid = :1",
&RS_Employee(&i).X_EE_RPT_LTR_VW.EMPLID.Value);

/* Get job row for linking other data */
&JOB_REC.EMPLID.Value =
&RS_Employee(&i).X_EE_RPT_LTR_VW.EMPLID.Value;
&JOB_REC.EMPL_RCD.Value = 0;
/* get the current effdt & effseq for the EEs job row */
SQLExec("select %dateout(j.effdt), j.effseq from ps_job j where
j.emplid = :1 and j.empl_rcd = :2 and j.effdt = (select max(j2.effdt) from
ps_job j2 where j2.emplid = j.emplid and j2.empl_rcd = j.empl_rcd and
j2.effdt <= %datein(:3)) and j.effseq = (select max(j3.effseq) from ps_job
j3 where j3.emplid = j.emplid and j3.empl_rcd = j.empl_rcd and j3.effdt =
j.effdt)", &JOB_REC.EMPLID.Value, &JOB_REC.EMPL_RCD.Value, %Date,
&JOB_REC.EFFDT.Value, &JOB_REC.EFFSEQ.Value);
&JOB_REC.SelectByKey();
12

Data set function for data source creation (Continued)

/* retrieve specific location data for description in report */
&LOCATION_TBL_REC.SETID.Value = &JOB_REC.SETID_LOCATION.Value;
&LOCATION_TBL_REC.LOCATION.Value = &JOB_REC.LOCATION.Value;
&LOCATION_TBL_REC.SelectByKeyEffDt(%Date);
&RS_Employee(&i).X_EE_RPT_LTR_VW.LOCATION_DESCR.Value =
&LOCATION_TBL_REC.DESCR.Value;

/* retrieve specific company data for description in report */
&COMPANY_TBL_REC.COMPANY.Value = &JOB_REC.COMPANY.Value;
&COMPANY_TBL_REC.Se lectByKeyEffDt(%Date);
&RS_Employee(&i).X_EE_RPT_LTR_VW.COMPANY_DESCR.Value =
&COMPANY_TBL_REC.DESCR.Value;

/* retrieve specific jobcode data for description in report */
&JOBCODE_TBL_REC.SETID.Value = &JOB_REC.SETID_JOBCODE.Value;
&JOBCODE_TBL_REC.JOBCODE.Value = &JOB_REC.JOBCODE.Value;
&JOBCODE_TBL_REC.SelectByKeyEffDt(%Date);
&RS_Employee(&i).X_EE_RPT_LTR_VW.JOB_DESCR.Value =
&JOBCODE_TBL_REC.DESCR.Value;

End-For;

Return &RS_Employee;

End-Function;

13

Appendix B
Freehand XML File Example

<?xml version='1.0'?>
<root>
<EMPLOYEE_DATA>
<EMPLID>KU0005</EMPLID>
<NAME>Aliverdi,Reza</NAME>
<DEPTID>10000</DEPTID>
<LOCATION>KUNY00</LOCATION>
<JOBCODE>420060</JOBCODE>
<COMPRATE>5156.666667</COMPRATE>
<CHANGE_PCT>0</CHANGE_PCT>
<LOCATION_DESCR>Corporation Headquarters</LOCATION_DESCR>
<JOB_DESCR>Director-Human Resources</JOB_DESCR>
<COMPANY_DESCR>Global Business Institute</COMPANY_DESCR>
<TRAINING_DATA>
<COURSE_START_DT>2000-09-11</COURSE_START_DT>
<COURSE>K018</COURSE>
<SESSION_NBR>0004</SESSION_NBR>
<COURSE_TITLE>PeopleTools 1</COURSE_TITLE>
<COURSE_END_DT>2000-09-15</COURSE_END_DT>
<ATTENDANCE>E</ATTENDANCE>
<TRAINING_REASON></TRAINING_REASON>
<COURSE_GRADE></COURSE_GRADE>
<PREREQ_MET>N</PREREQ_MET>
<BUSINESS_UNIT>US001</BUSINESS_UNIT>
</TRAINING_DATA>
</EMPLOYEE_DATA>
</root>

14

Appendix C
File Layout XML File Example

<?xml version='1.0'?>
<Start>
<X_EE_RPT_LTR_VW>
<NAME>Aliverdi,Reza K</NAME>
<CHANGE_PCT>0.000</CHANGE_PCT>
<X_TRAINING_VW>
<COURSE_START_DT>09/11/2000</COURSE_START_DT>
<COURSE_END_DT>09/15/2000</COURSE_END_DT>
<TRAINING_REASON> </TRAINING_REASON>
<COURSE_GRADE> </COURSE_GRADE>
</X_TRAINING_VW>
</X_EE_RPT_LTR_VW>
</Start>

15

Appendix D
Rowset XML File Example

<?xml version="1.0"?>
<rs_X_EE_RPT_LTR_VW numrows="1" rowsetname="X_EE_RPT_LTR_VW"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="">
<row_X_EE_RPT_LTR_VW rownumber="1">
<fld_EMPLID>KU0005</fld_EMPLID>
<fld_NAME>Aliverdi,Reza K</fld_NAME>
<fld_DEPTID>10000</fld_DEPTID>
<fld_LOCATION>KUNY00</fld_LOCATION>
<fld_JOBCODE>420060</fld_JOBCODE>
<fld_COMPRATE>5156.666667</fld_COMPRATE>
<fld_CHANGE_PCT>0</fld_CHANGE_PCT>
<fld_LOCATION_DESCR>Corporation Headquarters</fld_LOCATION_DESCR>
<fld_JOB_DESCR>Director-Human Resources</fld_JOB_DESCR>
<fld_COMPANY_DESCR>Global Business Institute</fld_COMPANY_DESCR>
<rs_X_TRAINING_VW numrows="1" rowsetname="X_TRAINING_VW">
<row_X_TRAINING_VW rownumber="1">
<fld_EMPLID>KU0005</fld_EMPLID>
<fld_COURSE_START_DT>2000-09-11</fld_COURSE_START_DT>
<fld_COURSE>K018</fld_COURSE>
<fld_SESSION_NBR>0004</fld_SESSION_NBR>
<fld_COURSE_TITLE>PeopleTools 1</fld_COURSE_TITLE>
<fld_COURSE_END_DT>2000-09-15</fld_COURSE_END_DT>
<fld_ATTENDANCE>E</fld_ATTENDANCE>
<fld_TRAINING_REASON></fld_TRAINING_REASON>
<fld_COURSE_GRADE></fld_COURSE_GRADE>
<fld_PREREQ_MET>N</fld_PREREQ_MET>
<fld_DEPTID>10000</fld_DEPTID>
<fld_BUSINESS_UNIT>US001</fld_BUSINESS_UNIT>
</row_X_TRAINING_VW>
</row_X_EE_RPT_LTR_VW>
</rs_X_EE_RPT_LTR_VW>

16

Appendix E
Rowset Schema (XSD) File Example

<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:documentati
on>Schema for PeopleSoft RowSet:
X_EE_RPT_LTR_VW</xsd:documentation></xsd:annotation><xsd:element
name="rs_X_EE_RPT_LTR_VW" type="rs_X_EE_RPT_LTR_VWtype"/><xsd:complexType
name="rs_X_EE_RPT_LTR_VWtype"><xsd:sequence><xsd:element
maxOccurs="unbounded" minOccurs="0" name="row_X_EE_RPT_LTR_VW"
type="row_X_EE_RPT_LTR_VWtype"/></xsd:sequence><xsd:attribute
name="rowsetname" type="xsd:string"/><xsd:attribute name="numrows"
type="xsd:integer"/></xsd:complexType><xsd:complexType
name="row_X_EE_RPT_LTR_VWtype"><xsd:sequence><xsd:element name="fld_EMPLID"
type="fld_EMPLIDtype"/><xsd:element name="fld_NAME"
type="fld_NAMEtype"/><xsd:element name="fld_DEPTID"
type="fld_DEPTIDtype"/><xsd:element name="fld_LOCATION"
type="fld_LOCATIONtype"/><xsd:element name="fld_JOBCODE"
type="fld_JOBCODEtype"/><xsd:element name="fld_COMPRATE"
type="fld_COMPRATEtype"/><xsd:element name="fld_CHANGE_PCT"
type="fld_CHANGE_PCTtype"/><xsd:element name="fld_LOCATION_DESCR"
type="fld_LOCATION_DESCRtype"/><xsd:element name="fld_JOB_DESCR"
type="fld_JOB_DESCRtype"/><xsd:element name="fld_COMPANY_DESCR"
type="fld_COMPANY_DESCRtype"/><xsd:element name="rs_X_TRAINING_VW"
type="rs_X_TRAINING_VWtype"/></xsd:sequence><xsd:attribute name="rownumber"
type="xsd:integer"/></xsd:complexType><xsd:simpleType
name="fld_EMPLIDtype"><xsd:restriction base="xsd:string"><xsd:maxLength
value="11"/></xsd:restriction></xsd:simpleType><xsd:simpleType
name="fld_NAMEtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_DEPTIDtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_LOCATIONtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_JOBCODEtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_COMPRATEtype"><xsd:restriction base="xsd:decimal"><xsd:totalDigits
name="fld_CHANGE_PCTtype"><xsd:restriction
base="xsd:decimal"><xsd:totalDigits
name="fld_LOCATION_DESCRtype"><xsd:restriction
base="xsd:string"><xsd:maxLength
name="fld_JOB_DESCRtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_COMPANY_DESCRtype"><xsd:restriction
value="30"/></xsd:restriction></xsd:simpleType>

Continued next page

17

XSD File Continued

<xsd:complexType name="rs_X_TRAINING_VWtype"><xsd:sequence><xsd:element
maxOccurs="unbounded" minOccurs="0" name="row_X_TRAINING_VW"
type="row_X_TRAINING_VWtype"/></xsd:sequence><xsd:attribute name="rowsetname"
type="xsd:string"/><xsd:attribute name="numrows"
type="xsd:integer"/></xsd:complexType><xsd:complexType
name="row_X_TRAINING_VWtype"><xsd:sequence><xsd:element name="fld_EMPLID"
type="fld_EMPLIDtype"/><xsd:element name="fld_COURSE_START_DT"
type="xsd:date"/><xsd:element name="fld_COURSE"
type="fld_COURSEtype"/><xsd:element name="fld_SESSION_NBR"
type="fld_SESSION_NBRtype"/><xsd:element name="fld_COURSE_TITLE"
type="fld_COURSE_TITLEtype"/><xsd:element name="fld_COURSE_END_DT"
type="xsd:date"/><xsd:element name="fld_ATTENDANCE"
type="fld_ATTENDANCEtype"/><xsd:element name="fld_TRAINING_REASON"
type="fld_TRAINING_REASONtype"/><xsd:element name="fld_COURSE_GRADE"
type="fld_COURSE_GRADEtype"/><xsd:element name="fld_PREREQ_MET"
type="fld_PREREQ_METtype"/><xsd:element name="fld_DEPTID"
type="fld_DEPTIDtype"/><xsd:element name="fld_BUSINESS_UNIT"
type="fld_BUSINESS_UNITtype"/></xsd:sequence><xsd:attribute name="rownumber"
type="xsd:integer"/></xsd:complexType><xsd:simpleType
name="fld_COURSEtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_SESSION_NBRtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_COURSE_TITLEtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_ATTENDANCEtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_TRAINING_REASONtype"><xsd:restriction
name="fld_COURSE_GRADEtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_PREREQ_METtype"><xsd:restriction base="xsd:string"><xsd:maxLength
name="fld_BUSINESS_UNITtype"><xsd:restriction
value="5"/></xsd:restriction></xsd:simpleType></xsd:schema>

18

Appendix F
XMLDoc XML File Example

<root>
<EMPLOYEE_DATA>
<NAME>Aliverdi,Reza K</NAME>
<CHANGE_PCT>0</CHANGE_PCT>
<TRAINING_DATA>
<COURSE_START_DT>2000-09-11</COURSE_START_DT>
<COURSE_END_DT>2000-09-15</COURSE_END_DT>
<TRAINING_REASON></TRAINING_REASON>
<COURSE_GRADE></COURSE_GRADE>
</TRAINING_DATA>
</EMPLOYEE_DATA>
</root>

19

Appendix G

Combining PDF Files
import PSXP_RPTDEFNMANAGER:*;
import PSXP_ENGINE:*;

/* PeopleTools 8.49 and higher */
rem import PTXMLP_ENGINE:*;

Declare Function GetDirSeparator PeopleCode PSXPFUNCLIB.FUNCLIB
FieldFormula;

Local XmlDoc &First_XMLDoc, &Second_XMLDoc;
Local XmlNode &childNode, &rowNode;
Local string &Xml_String, &FIRST_Filename_path;
Local string &FirstReportFilePath, &SecondReportFilePath;
Local string &PDF_Merge_File_name, &FIRST_XML_Filename_path,
&Second_XML_Filename_path, &SecondReportFileName;
Local File &FIRST_XML_File, &SECOND_XML_File, &PDF_Merge_File;

/* Create & FIRST XMLDoc */
&First_XMLDoc = CreateXmlDoc("<?xml version='1.0'?><root/>");
&rowNode = &First_XMLDoc.DocumentElement.AddElement("FIRST_Report");
&childNode = &rowNode.AddElement("FIRST_DATA");
&childNode.NodeValue = "FIRST DATA";
&Xml_String = &First_XMLDoc.GenFormattedXmlString();

&FIRST_XML_File = GetFile("FIRST_DATA.xml", "W");
&FIRST_XML_File.WriteLine(&Xml_String);
&FIRST_XML_Filename_path = &FIRST_XML_File.Name;
&FIRST_XML_File.Close();

/* Create & Second XMLDoc */
&Second_XMLDoc = CreateXmlDoc("<?xml version='1.0'?><root/>");
&rowNode = &Second_XMLDoc.DocumentElement.AddElement("Second_Report");
&childNode = &rowNode.AddElement("Second_DATA");
&childNode.NodeValue = "Second DATA";
&Xml_String = &Second_XMLDoc.GenFormattedXmlString();

&SECOND_XML_File = GetFile("Second_DATA.xml", "W");
&SECOND_XML_File.WriteLine(&Xml_String);
&Second_XML_Filename_path = &SECOND_XML_File.Name;
&SECOND_XML_File.Close();

/* Create the first pdf doc */
&oXML_PUB_1 = create PSXP_RPTDEFNMANAGER:ReportDefn("X_PDF_FIRST");
&oXML_PUB_1.Get();
&oXML_PUB_1.SetRuntimeDataXMLfile(&FIRST_XML_Filename_path);
&oXML_PUB_1.ProcessReport("", "", %Date, "");
DoSaveNow();

[Continued below…]

20

Continued…

[Continued from above…]

&sDirSep = GetDirSeparator();
&FirstReportFileName = &oXML_PUB_1.ID | "." |
Lower(&oXML_PUB_1.GetOutDestFormatString(2));
&FirstReportFilePath = &oXML_PUB_1.OutDestination | &sDirSep | "RptInst" |
&sDirSep | &FirstReportFileName;

/* Create the second pdf doc */
&oXML_PUB_2 = create PSXP_RPTDEFNMANAGER:ReportDefn("X_PDF_SECOND");
&oXML_PUB_2.Get();
&oXML_PUB_2.SetRuntimeDataXMLfile(&FIRST_XML_Filename_path);
&oXML_PUB_2.ProcessReport("", "", %Date, "");
DoSaveNow();

&SecondReportFileName = &oXML_PUB_2.ID | "." |
Lower(&oXML_PUB_2.GetOutDestFormatString(2));
&SecondReportFilePath = &oXML_PUB_2.OutDestination | &sDirSep | "RptInst" |
&sDirSep | &SecondReportFileName;

/* Merge Documents */
/* define result file location and name */
&PDF_Merge_File = GetFile("PDF_MERGE.pdf", "W");
&PDF_Merge_File_name = &PDF_Merge_File.Name;
&PDF_Merge_File.Close();

/* PeopleTools 8.49 and higher */
rem Local PTXMLP_ENGINE:PDFMerger &oMerger;

/* PeopleTools 8.48 */
&oMerger = create PSXP_ENGINE:PDFMerger();

&PDF_Merge_Error = "";
&PDF_Merge_Array = CreateArray(&FirstReportFilePath);
&PDF_Merge_Array.Push(&SecondReportFilePath);
&PDF_Merge_Result = &oMerger.mergePDFs(&PDF_Merge_Array,
&PDF_Merge_File_name, &PDF_Merge_Error);

MessageBox(0, "", 299, 1, "Error: %1, Result: %2", &PDF_Merge_Error,
&PDF_Merge_Result);

&FIRST_XML_File = GetFile("FIRST_DATA.xml", "W");
&FIRST_XML_File.Delete();
&SECOND_XML_File = GetFile("Second_DATA.xml", "W");
&SECOND_XML_File.Delete();

21

Creating xml publisher documents with people code

In this document

More Related Content

What's hot

Similar to Creating xml publisher documents with people code

Creating xml publisher documents with people code