Creating XML Outputs for Events

Once the staging tables are loaded with the eSocial event data that is identified for the reference month, together with driver and cross reference tables, XML outputs for event data are ready to be generated using the XML Reporting Framework.

Customers are ready to generate XML outputs for eSocial reporting when:

• The XML Reporting Framework is set up for eSocial functionality.

  The setup (for example, XML set, template, and node root) is delivered as part of the eSocial functionality.

  See Also Setting Up XML Reporting Framework

• Tables views are created for event layouts to be used in the XML output creation process.

  They are delivered as part of the eSocial functionality.

• The XML-specific setup is configured for events and companies that are enabled for eSocial reporting.

  See Also XML Batch Group Definition Page, Events Setup Page and XML Options Page

• eSocial data is loaded in driver, cross-reference, and staging tables.

PeopleSoft delivers run control pages that invoke the XML output creation process. While these pages are built for specific event categories, the process flow remains the same.

This diagram illustrates the high-level process flow for generating XML outputs for eSocial reporting.

The XML output creation process can be invoked from these run control pages: eSocial Basic Initial Page, eSocial Employee Initial Page, eSocial Basic Table Event Page, and eSocial Non Periodic Event Page.

When the process is invoked from an eSocial run control page (with Create XML selected as the process option), it:

1. Reads the parameters that are specified on the run control page, and selects from the driver table data rows that match those parameters and are in the SUCC (Success) or XERR (XML Error) status. It populates these data rows to the temporary record, waiting to be processed.

2. Updates the status of these data rows to XRDY in the driver table to prevent them from being used by other processes.

3. Validates the status of the events that are associated with all data rows that are available in the temporary record:

   • If the event of a row is active, the row is populated to XML records (XMLFG_ITEM and XMLFG_RC) for file creation.

   • If the event of a row is inactive, the row status is set to XERR (XML Error) in the driver record. The row is sent for error handling.

4. Calls the XMLFG_PRNT process of the XML Reporting Framework to create XML outputs for rows found in the XML records.

   This step applies to companies that have their XML output type set to file on the XML Options page.

5. Updates the status of each data row that has its XML output created successfully to XCRT (XML Create) in driver records. For those that didn’t have their outputs generated, their row statuses are set to XERR, and their rows sent for error handling.

6. Writes the process results to the log.

Based on the output type (string or file) that is specified on the XML Options page, PeopleSoft either generates an XML string to be inserted into the XMLGF_STRNG_TBL record, or generates XML files to be stored in the specified directory for the corresponding company. Customers are responsible for submitting XML outputs to the eSocial environment using third-party or their own in-house systems.

Customers have the option to recreate XML outputs (file or string) for eSocial events if necessary. PeopleSoft delivers the eSocial Recreate XML Files Page that recreates XML outputs for selected companies, establishments and events.

Use the eSocial Recreate XML Files page (GPBR_RUN_XML) to recreate XML outputs for selected events, companies, and establishments.

Navigation:

Global Payroll & Absence Mgmt > Absence and Payroll Processing > Reports > eSocial BRA > eSocial Recreate XML

This example illustrates the fields and controls on the eSocial Recreate XML Files page.