Explore topic-wise InterviewSolutions in .

PTPT2600 this only for Developer, which will GIVE an access to all XMLP Component including buffing FEATURE ALSO.

PTPT 2500 this is only for power users, it will provide the access to QUERY DATA sources for Ad-hoc reporting, this also provide the access to report definition, Bursting feature is view only.

PTPT1000: This will give the access to access the report repository.

PTPT2600 this only for Developer, which will give an access to all XMLP Component including buffing feature also.

PTPT 2500 this is only for power users, it will provide the access to query data sources for Ad-hoc reporting, this also provide the access to report definition, Bursting feature is view only.

PTPT1000: This will give the access to access the report repository.

XMLP Global Engine settings are DEFINED in xdo.cfg file, which is LOCATED at
$PSHOME / APP SERVER DIRECTORY

XMLP Global Engine settings are defined in xdo.cfg file, which is located at
$PSHOME / APP SERVER Directory

• Report Manager Definition class
• Report Manager Search class
• XML GENERATION class
• XML publisher engine class

Note:The Xml publisher report OUTPUT

Note:The Xml publisher report output

RTF: For- each SYNTAX REPEATING the group of ELEMENTS

• Template – Field
• Form – Field
• Form – Field
• Xml – data field

PDF: Two OPTIONS for creating fields here

1. Manual creation and we can map that fields top XML data.
2. Create fields with same name as XML elements.

RTF: For- each syntax repeating the group of elements

PDF: Two options for creating fields here

1. PSXP- RPTDEFMANAGER
2. PSXP -REPORTMGR
3. PSXP -XMLGEN
4. PSXP –ENGINE

XML FILE is the PREFERRED data source for lager process such as paycecks, ROWSET and xml DOC have performance/memory limitations, and we can use this only for small reports.

XML file is the preferred data source for lager process such as paycecks, rowset and xml doc have performance/memory limitations, and we can use this only for small reports.

In the report definition Tab, we need to SET the report STATUS should be active, report CATEGORY ID and object OWNER ID and we need to choose the template TYPES.

In the report definition Tab, we need to set the report status should be active, report category ID and object owner ID and we need to choose the template types.

The template formats are: .RFT, PDF, .XLS, .XSLT After the creation of template files, we NEED to load the “XML FILE”, and then only we can DESIGN our report.

The template formats are: .RFT, PDF, .XLS, .XSLT After the creation of template files, we need to load the “XML file”, and then only we can design our report.

Here we can USE either MS-Word or adode to develop and maintain CUSTOM REPORT formats.

Here we can use either MS-Word or adode to develop and maintain custom report formats.

The DATA sources can be:

PS-Query, ROWSET, PEOPLECODE, XMLDoc and XML file.

In case of PS-Query, the system by default generates the XML file and schema file.

The data sources can be:

PS-Query, Rowset, peoplecode, XMLDoc and XML file.

In case of PS-Query, the system by default generates the XML file and schema file.

• Define XMLP SETTINGS
• Setup XMLP PERMISSION list SECURITY
• Setup REPORT manager
• Define Report categories, including report definition editor security
• Download design plug-ins to facilitate the offline template design ACTIVITY.

All the XML PUBLISHER report OUTPUTS are available in Report Manger, not in Process MONITOR.

All the xml publisher report outputs are available in Report Manger, not in Process Monitor.

• IBYDE_D_DEEN--> GERMAN Domestic payment
• IBYDE_FR_EN--> French EFT Payments
• IBYDE_F_DEEN--> German INTERNATIONAL EFT payments
• IBYDE_F_NLEN-->NETHERLANDS International EFT
• IBYDE_Z_JPEN--> Japanese Zengin Format

An EFT is an electronic TRANSMISSION of financial DATA and payments to BANKS in a specific fixed-position format FLAT FILE (text).

An EFT is an electronic transmission of financial data and payments to banks in a specific fixed-position format flat file (text).

Through APP engine or Peoplecode we scheduling.

IMPORT Application PACKAGES, PSXP_MALGEN this is used for GENERATE xml scheme file and xml DATE file.

Through App engine or Peoplecode we scheduling.

Import Application Packages, PSXP_MALGEN this is used for generate xml scheme file and xml date file.

Data source--> generate xml and schema files--> load xml file to template--> create report definition (DECLARE E-text template type)-->UPLOAD template file--> setting the PROPERTIES for security purpose (setting report categories ID)-->viewing output

Data source--> generate xml and schema files--> load xml file to template--> create report definition (declare E-text template type)-->upload template file--> setting the properties for security purpose (setting report categories ID)-->viewing output

An E-Text template is an RTF-based template that is used to generate text output for Electronic FUNDS Transfer (EFT) and Electronic DATA Interchange (EDI). At runtime, BI Publisher APPLIES this template to an INPUT XML data FILE to create an output text file that can be transmitted to a bank or other customer.

An E-Text template is an RTF-based template that is used to generate text output for Electronic Funds Transfer (EFT) and Electronic Data Interchange (EDI). At runtime, BI Publisher applies this template to an input XML data file to create an output text file that can be transmitted to a bank or other customer.

Reporting tool--> XML publisher-->query REPORT SCHEDULER -->Run BUTTON (Distribution) we can view the MAIL.

Reporting tool--> xml publisher-->query report scheduler -->Run button (Distribution) we can view the mail.

Data source--> generate XML and schema files--> load xml file to template--> CREATE report definition (declare template TYPE)-->upload template file--> setting the properties for security purpose (setting report categories ID)--> viewing output

Data source--> generate xml and schema files--> load xml file to template--> create report definition (declare template type)-->upload template file--> setting the properties for security purpose (setting report categories ID)--> viewing output

Xml publishers’ GLOBAL ENGINE SETTINGS are DEFINED in the xdo.cfg FILE

Xml publishers’ global engine settings are defined in the xdo.cfg file

• HTML
• PDF
• RTF
• XLS

• PDF
• RTF
• E-text
• XSL

• PSQuery
• XMLDoc
• ROWSET
• XML FILE

It is advised to use the Microsoft Word Insert menu OPTION to insert the image, as the additional properties that need to be set for the RTF template to CORRECTLY generate reports with those images are automatically set by using this method. Additionally, DRAGGING and DROPPING an image onto a template creates a link to the local machine being used and may cause problems when the report is GENERATED.

The user has to be online to access the image referenced in the URL.

It is advised to use the Microsoft Word Insert menu option to insert the image, as the additional properties that need to be set for the RTF template to correctly generate reports with those images are automatically set by using this method. Additionally, dragging and dropping an image onto a template creates a link to the local machine being used and may cause problems when the report is generated.

The user has to be online to access the image referenced in the URL.

If a QUERY is RUN through Reporting Tools, Query, Schedule Query, the XML Publisher-related prompts do not appear. Only the basic table-formatted query results are GENERATED.

If a query is run through Reporting Tools, Query, Schedule Query, the XML Publisher-related prompts do not appear. Only the basic table-formatted query results are generated.

Yes, template must exist before it can be translated. Template translations are not available for template types other than RTF. For a PDF report, there must be multiple PDF templates REGISTERED to the report, one for each locale or language as required.

Yes, template must exist before it can be translated. Template translations are not available for template types other than RTF. For a PDF report, there must be multiple PDF templates registered to the report, one for each locale or language as required.

The TEMPLATE Translation feature is based upon STANDARD LOCALIZATION Interchange File FORMAT (XLIFF) .xlf file processing. Each report template or sub-template file can have related translation XLIFF files. These XLIFF files include translation units for each content element to be TRANSLATED.

The Template Translation feature is based upon standard Localization Interchange File Format (XLIFF) .xlf file processing. Each report template or sub-template file can have related translation XLIFF files. These XLIFF files include translation units for each content element to be translated.

Sub-TEMPLATES are secondary RTF or XSL templates that are imported by primary RTF or XSL report templates. The primary template accesses the sub-template through the XSL import style sheet FEATURE.

The sub-template files are independently stored and are not REGISTERED in ASSOCIATION with a data source or primary template.

Sub-templates are secondary RTF or XSL templates that are imported by primary RTF or XSL report templates. The primary template accesses the sub-template through the XSL import style sheet feature.

The sub-template files are independently stored and are not registered in association with a data source or primary template.

It MUST be registered with the data SOURCE of the report DEFINITION.

It must be registered with the data source of the report definition.

BURSTED reports must be RUN from the Query Report Scheduler COMPONENT.

Bursted reports must be run from the Query Report Scheduler component.

Bursting is an optional ADVANCED feature that is only available when reports are run through Process Scheduler and is not intended for real-time online viewing. It is typically used when you are repeating the GENERATION of a templated report layout many TIMES for multiple like sets of data.

For example, generating a batch run on vendor PURCHASE orders or CUSTOMER invoices. With bursting, you can generate individual report files resulting in separate secured output. For example, generating a file for each vendor, customer or employee.

Bursting is an optional advanced feature that is only available when reports are run through Process Scheduler and is not intended for real-time online viewing. It is typically used when you are repeating the generation of a templated report layout many times for multiple like sets of data.

For example, generating a batch run on vendor purchase orders or customer invoices. With bursting, you can generate individual report files resulting in separate secured output. For example, generating a file for each vendor, customer or employee.

You can check the format of an XML OUTPUT FILE by opening it using Microsoft Internet Explorer (IE). IE opens the file and ALERTS you to any problems, such as UNCLOSED tags.

You can check the format of an XML output file by opening it using Microsoft Internet Explorer (IE). IE opens the file and alerts you to any problems, such as unclosed tags.

When creating a REPORT definition, you can SELECT a PeopleSoft QUERY data source that has not YET been registered and that data source is registered automatically once the report definition is saved. However, all other types of data SOURCES must be registered before they can be associated with a report definition.

When creating a report definition, you can select a PeopleSoft Query data source that has not yet been registered and that data source is registered automatically once the report definition is saved. However, all other types of data sources must be registered before they can be associated with a report definition.

REPORT definition access is BASED on USER PERMISSION LIST security and roles.

Report definition access is based on user permission list security and roles.

REPORT definitions ASSOCIATE a data source with template files. A data source registers the schema and sample data design files. It is the EXTRACTED APPLICATION fields from the data source files that are placed into the template files to CREATE the final report.

Report definitions associate a data source with template files. A data source registers the schema and sample data design files. It is the extracted application fields from the data source files that are placed into the template files to create the final report.

Only when the application PROCESS that RUNS the report is ASSIGNED the process type of XML PUBLISHER.

Only when the application process that runs the report is assigned the process type of XML Publisher.

Report CATEGORY is a required ATTRIBUTE on all report definitions and Content LIBRARY sub-templates. By assigning a report category, you are actually applying row level security to the data on those components.

Report Category is a required attribute on all report definitions and Content Library sub-templates. By assigning a report category, you are actually applying row level security to the data on those components.

The -Dxdo.ConfigFile setting is RELATIVE to the application SERVER or process SCHEDULER DOMAIN directory, which is the CURRENT directory when the domain starts up.

The -Dxdo.ConfigFile setting is relative to the application server or process scheduler domain directory, which is the current directory when the domain starts up.

XML Publisher menu access is permission list DRIVEN and depends on permission list and role assignment. PeopleTools delivers permission list security and ROLES for XML Publisher report developers and XML Publisher power users.

Permission list PTPT2600 is intended for report developers.

Permission list PTPT2500 is intended for power users and provides access to Query data sources for ad hoc reporting through Query Report VIEWER and Query Report Scheduler.

Users assigned to other permission lists and roles, such as permission list PTPT1000, MAY only have access to the XML Publisher Report Repository.

XML Publisher menu access is permission list driven and depends on permission list and role assignment. PeopleTools delivers permission list security and roles for XML Publisher report developers and XML Publisher power users.

Permission list PTPT2600 is intended for report developers.

Permission list PTPT2500 is intended for power users and provides access to Query data sources for ad hoc reporting through Query Report Viewer and Query Report Scheduler.

Users assigned to other permission lists and roles, such as permission list PTPT1000, may only have access to the XML Publisher Report Repository.

XML Publisher security can be separated into THREE categories:

1. DEFINING reports.
2. RUNNING reports.
3. Viewing reports.

XML Publisher security can be separated into three categories:

XML Publisher implementation can be DIVIDED into the FOLLOWING phases:

• Configure XML Publisher.
• REGISTER data sources.
• Create templates.
• Define XML Publisher reports.
• Run XML Publisher reports.
• Locate and view PUBLISHED XML Publisher reports.

XML Publisher implementation can be divided into the following phases:

Oracle has developed a standalone Java-based reporting technology CALLED XML Publisher (XMLP) that streamlines REPORT and form generation. A primary feature of Oracle's XML Publisher PRODUCT is the separation of the DATA extraction process from the report layout. XML Publisher provides the ability to design and create report layout templates with the more common desktop applications of Microsoft Word and Adobe ACROBAT, and renders XML data based on those templates.

Oracle has developed a standalone Java-based reporting technology called XML Publisher (XMLP) that streamlines report and form generation. A primary feature of Oracle's XML Publisher product is the separation of the data extraction process from the report layout. XML Publisher provides the ability to design and create report layout templates with the more common desktop applications of Microsoft Word and Adobe Acrobat, and renders XML data based on those templates.

It can GENERATE reports in many formats (PDF, RTF, EXCEL, HTML, and so on) in many LANGUAGES.

It can generate reports in many formats (PDF, RTF, Excel, HTML, and so on) in many languages.

Because XML Publisher uses managed object functionality, you do not have the ability to use the switching feature of multi-language DATA entry. You can populate RELATED language tables by LOGGING in and establishing a DIFFERENT SESSION language. The related language table for that session can then be populated.

Because XML Publisher uses managed object functionality, you do not have the ability to use the switching feature of multi-language data entry. You can populate related language tables by logging in and establishing a different session language. The related language table for that session can then be populated.

Vb.net is product of micro Soft Corporation. it is for DEVELOPING APPLICATION programs. Xml is an open standard one. It is for representing DATA. Xml is not restricted to the particular language. We can use to represent data of any type of application. XML is common one. For business to business communication XML is BEST one.

Vb.net is product of micro Soft Corporation. it is for developing application programs. Xml is an open standard one. It is for representing data. Xml is not restricted to the particular language. We can use to represent data of any type of application. XML is common one. For business to business communication XML is Best one.

• XMLP have different datasources to GET the data.
• In XMLP, we can easily DESIGN OUTPUT template through MS Word.
• We can easily MAINTAIN security in XMLP

We can run XMLP USING Query Report Viewer and SCHEDULING is DONE with Query Report SCHEDULER.

We can run XMLP using Query Report Viewer and Scheduling is done with Query Report Scheduler.

REPORT DEFINITION

Report Definition

Bursting is just LIKE GROUP by CLAUSE in SQL. Its optional in XMLP.

Bursting is just like Group by clause in SQL. Its optional in XMLP.

PDF,RTF,EXCEL and HTML

PDF,RTF,Excel and HTML