Creating JD Edwards XML Publisher Objects

This chapter provides an overview of the JD Edwards EnterpriseOne XML Publisher Object Repository (P95600) and discusses how to create, upload, and modify XML Publisher objects.

Understanding the XML Publisher Object Repository

The XML Publisher Object Repository (P95600) allows users to create, upload, update, copy, and delete XML Publisher objects. XML Publisher uses three types of objects:

• Templates

• Transformations

• Translations and localizations

Templates

XML Publisher templates are used to format reports using the data that resides in the JD Edwards EnterpriseOne database. You can create templates using:

• Microsoft Word (RTF format only)

• Microsoft Excel (XLS or XSL)

• Adobe Acrobat (PDF)

This table describes how templates are created.

Oracle's BI Publisher Template Builder (formerly Oracle's XML Publisher Template Builder) is an extension to Microsoft Word that simplifies the development of RTF templates. It automates many of the manual steps that you would otherwise have to perform. Use the Template Builder in conjunction with the Oracle XML Publisher Core Components Guide 10.1.3.3 to increase your productivity.

Note. The BI Publisher Template Builder for Word Add-in includes features to log in to and interact with Oracle Business Intelligence Publisher Enterprise. The following menu items only work with the Oracle BI Publisher Enterprise or Oracle BI Enterprise Edition implementations: Log In, Open, Upload, and Upload Template As. See the Template Builder help for more information.

The Template Builder is tightly integrated with Microsoft Word and allows you to perform the following functions. Instructions and tutorials for using the Template Builder are available from the readme and help files delivered with the tool.

• Insert data fields.

• Insert data-driven tables.

• Insert data-driven forms.

• Insert data-driven charts.

• Preview your templates with sample XML data.

• Browse and update the content of form fields.

• Extract boilerplate text into an XLIFF translation file and test translations.

Manual steps for performing these functions are covered in the Oracle XML Publisher Core Components Guide 10.1.3.3. Instructions and tutorials for using the Template Builder are available from the readme and help files delivered with the tool.

See Oracle XML Publisher Core Components Guide 10.1.3.3

Excel templates must be created manually using Microsoft Excel. To create PDF templates, you must have the full version of Adobe Acrobat.

Note. For more information on creating templates specifically for JD Edwards EnterpriseOne, see “Creating XML Publisher Templates for JD Edwards EnterpriseOne” on the Oracle|PeopleSoft Customer Connection site.

Transformations

XML Publisher transformations are eXtensible Stylesheet Language (XSL) templates that are used to map data and transform an XML file into another XML file with a different format. This is beneficial when, for example, you use a template that was created using different field names and you need to map those field names to JD Edwards EnterpriseOne-specific field names.

Translations and Localizations

XML Publisher for JD Edwards EnterpriseOne introduces the concepts of localization and translation. Translations are XML files that are created to translate static text of the template into other languages. You can think of translations as a list of words on a template that are translated from one language, typically English, to another language at runtime. Translations are available for RTF templates only.

This is an example of an XML file that translates the static text of an English RTF template to German.

German translation of English template

By contrast, a localization is a different version of an existing template that not only translates the static text from one language to another, but also includes or excludes specific data elements when compared to the base template. For example, a base template might have a data element that displays salary information. If displaying this information is illegal in a particular country, you can copy the base template and remove the salary data element.

Uploading, Updating, and Deleting JD Edwards XML Publisher Objects

This section provides overviews of uploading XML Publisher objects, updating XML Publisher objects, and deleting XML Publisher objects and discusses how to:

• Upload XML Publisher objects.

• Add translations and localizations.

• Modify XML Publisher object properties.

• Modify effective dates.

• Modify XML Publisher objects.

• Delete XML Publisher objects.

Understanding XML Publisher Objects

You must upload XML Publisher objects to JD Edwards EnterpriseOne before you can create report definitions for the desired output types. You use XML Publisher Object Repository (P95600) on either the web client or the Microsoft Windows client to upload templates, translations, localizations, and transformations into JD Edwards EnterpriseOne.

To upload XML Publisher objects, you must add a new XML Publisher object to JD Edwards EnterpriseOne. Name the object according to these recommended naming conventions:

• Use all capital letters.

• Do not begin the object name with a dash (–).

• Use a maximum of 50 characters.

Enter a brief but meaningful description of the object. This description should include the purpose of the object.

Identify the XML Publisher object as a specific object type. The following object types are available:

• eText.

• PDF.

• Rich text format (RTF).

• Extensible stylesheet language (XSL).

• Transformation.

• Translation.

After creating a new object in JD Edwards EnterpriseOne, you can search and select the XML Publisher object that you need to upload. XML Publisher objects are stored in the JD Edwards EnterpriseOne database in the F95600 table.

The file types that you can upload for each XML Publisher object type are shown in this table:

The recommended maximum default XML Publisher object size is 50MB. You can modify the XML Publisher object size on the Windows client by changing the object size in the INTERACTIVE RUNTIME section of the jde.ini using the following definition:

[INTERACTIVE RUNTIME]
MaxFileUploadSize = 50

It is recommended that you use the Windows client to upload XML Publisher objects. However, if the web client is used to upload objects you can modify the XML Publisher object size in the OWWEB section of the jas.ini using the following definition:

[OWWEB]
MaxFileUploadSize = 50

Note. You can increase or decrease the default maximum file upload size. The default maximum size is 50MB. If the XML Publisher object exceeds the maximum size definition, an error displays.

Effective Dates

Effective dates indicate when an object is available for use. If an object will be used indefinitely, it is not necessary to specify an end date. You can upload additional templates with the same name and give them specific start and end dates as long as the effective dates do not overlap. The version without an end date becomes the default version when none of the other versions' effective dates correspond to the current date.

Effective dates enable a company to have multiple, slightly different versions of the same template. For example, to customize a newsletter with different logos for each month, you can design a master template and upload it to the XML Publisher Object Repository with a start date, but no end date. Then you can create twelve copies of the original template, add a monthly logo to each one, and upload them with the same name as the original template but with different start and end dates for each copy.

Updating XML Publisher Objects

You can update XML Publisher objects that have been uploaded to JD Edwards EnterpriseOne. First download the XML Publisher object to your local machine. Then make the required modifications to the XML Publisher object. Upload the modified XML Publisher object to JD Edwards EnterpriseOne.

Deleting XML Publisher Objects

You can delete XML Publisher objects that have been uploaded to JD Edwards EnterpriseOne. From the JD Edwards EnterpriseOne XML Publisher Object Repository application, select the XML Publisher object. Click Delete.

When you select to delete an object, the system displays a Delete XML Publisher Object Warning form. Click OK to delete the object or click Cancel if you do not want to delete the object.

If the object is active when you attempt to delete it, the system displays a Delete Object Violation form. Click OK to close the form and return to the XML Publisher Object Repository. Select the object again and access Effective Dates from the row menu to remove the start and end dates. After removing the effective dates, select the object and click Delete to remove the reporting object.

When you delete an XML Publisher reporting object, the object record is deleted from the F95600 table. In addition, all associations to the deleted reporting object are also deleted. Associations reside in these tables:

• XML Publisher UBE Associations (F95610).

• XML Publisher Object Associations (F95611).

Prerequisite

Refer to the Getting Started chapter for a list of implementation steps that you need to perform.

See Getting Started with JD Edwards EnterpriseOne XML Publisher.

Forms Used to Upload and Update XML Publisher Objects

Creating XML Publisher Objects

Access the Add XML Publisher Object to Repository form.

Object Name	Enter the name of the XML Publisher object.
Object Description	Enter a meaningful description of the object.
Object Type	Select a user-defined code (UDC) (H95|XP) that indicates the object type of the reporting object.
Product Code	Select a product code from the 55–59 client reserved range.
Product Code Reporting	Select a product code that indicates where the reporting data resides.
Object Region	For templates, select a UDC (H95|XC) that indicates the region for which the template was created. For translations, select the region in which the report will be presented. This field is not required if the object type is a transformation.
Object Language	For templates, select the language that is used in the template. For translations, select the language in which the report will be presented. This field is not required if the object type is a transformation.
Localization	Select this option if the object is a localization of an existing template. The localization object must have the same name and document type as the template upon which it is based.
Start Date	After clicking OK and uploading the object, add a start date to indicate when the object is available for use. If an object does not have a start date or if the start date is in the future, the object has an Inactive status.
End Date	Do not enter an end date if the object is to be used indefinitely. Enter an end date only if the object is to be used for a specific period of time.

Note. The Localization check box is available only when adding a localization object with the same name as an uploaded template. The Start Date, and End Date fields are not available until an object has been uploaded into the repository.

Uploading XML Publisher Objects

Click OK on the Add XML Publisher Object to Repository form to access the File Upload form.

1. Click Browse to locate the appropriate XML Publisher object.

2. Validate the object type and file extension.

   Note. The system does not allow you to upload a file with an invalid extension.

3. On the File Upload form, click Load to upload the XML Publisher object from your local directory to JD Edwards EnterpriseOne.

Adding Translations and Localizations

Access the XML Publisher Object Repository form.

1. Find and select the template to which you want to add a translation or localized template.

2. From the Row menu, select either Add Translation or Add Localization.

3. On either the Add XMLP Translation to Repository form or the Add XMLP Localized Template to Repository form, complete the following fields and click OK:

   • Description

   • Product Code

   • Product System Code

   • Object Region

   • Object Language

4. On the File Upload form, locate the translation or localized template and click Load to upload the file from your local directory to JD Edwards EnterpriseOne.

   Note. You must upload the correct file type or an error message will display. Translations must be either .xml or .xlf files. Localizations must be .rtf files, the same as the templates on which they are based.

5. Enter a Start Date for the template if you want to make the template active, and an End Date if the template is to be used for only a specific period of time.

Modifying XML Publisher Object Properties

Access the Update XML Publisher Object in Repository form.

1. Modify object information and click OK.

2. On the Upload File form, click No in answer to the question Would you like to upload the file again?

3. Click Close.

Modifying Effective Dates

Access the Update XMLP Object Effective Dates form.

1. Add, modify or delete the start date.

2. Add, modify, or delete the end date.

3. Click OK.

Modifying XML Publisher Objects

Access the XML Publisher Object Repository form.

1. Select an XML Publisher object.

2. From the Row menu, select Download.

3. On the Microsoft Windows client, the file downloads automatically.

4. On the web client, select either Open or Save. on the File Download form.

Note. On the web client, when you select Download from the Row menu of the XML Publisher Object Repository form, the XML Publisher object is cached on your machine. As long as the File Download form remains open, you can continue to open and save the object. When you close the File Download form, the cache is cleared.

Revising XML Publisher Objects

After the file downloads, you can revise the XML Publisher object.

See Oracle XML Publisher Core Components Guide 10.1.3.3

1. Modify the XML Publisher object using the appropriate editor, and save the object to your local machine.

2. Close the editor.

3. On the XML Publisher Object Repository form, select the object that you just modified, and click Select.

4. On the Update XML Publisher Object in Repository form, modify the object information and click OK.

5. On the Upload File form, click Yes in response to the question, “Would you like to upload the file again?”

6. Click the XML Publisher object name to upload the modified version.

7. Click Close.