Using ChartFields in Time and Labor

This section provides a brief overview of ChartFields and discusses the:

Configuration and integration.
Impact on task templates.
Impact on time reporting pages.
ChartField storage in reported time and task profile.
ChartField storage in payable time.
Time and Labor validation options.

ChartFields are fields used to report General Ledger charts of accounts with transactional data. These accounts determine the logging of transactions and the tracking of information for General Ledger purposes. ChartFields enable you to report up to 21 chart of accounts when entering transactional data. Both Commitment Accounting and Non-Commitment Accounting customers can utilize the ChartField functionality for their business processes.

Configuration and Integration

You can configure and activate all or a subset of the 21 ChartFields using the Standard ChartField Configuration page. The Standard ChartField Configuration page enables you to activate, change the order of display, relabel the fields, and change the field length displayed for individual ChartFields.

If you integrate your HCM database with PeopleSoft General Ledger (GL), then you also set up the Standard ChartField Configuration that is owned by PeopleSoft Financial Management Systems (FMS). This configuration is defined and sent to HCM via Integration Broker. Any changes must be made directly in the FMS database and then sent to HCM.

If the HCM database is not integrated with PeopleSoft General Ledger, but you still want to enter ChartField values, then the Standard ChartField Configuration is accessible and can be updated directly. This may be used to capture chart of account values to send to a third party GL application or to just capture these details for HCM purposes. No matter where the configuration is entered, once you press the Apply button and the application engine runs, the pages displaying ChartFields will reflect the configured display.

See Application Fundamentals: Understanding PeopleSoft ChartFields.

Impact on Task Template

After you press the Apply button on the Standard ChartField Configuration page, the impact to Time and Labor (TL) begins with the task template. The task template reflects the activated ChartField values when combo code is an enabled field. For example, if the Standard ChartField Configuration has activated GL account, department and project, and the application engine (using the Apply button) has been run, then the enabling of combo code field on the task template also enables the GL account, department and project as individual ChartField values.

When the system enables the combo code on the task template, the HR business unit is also enabled. The reason is in order to validate the combination of individual ChartField values, associated with a new or existing combo code, a GL business unit is required. HR business units are mapped to GL business units through the GL/HR Business Unit Mapping page (Setup HCM, Common Definitions, ChartField Configuration, GL/HR Business Unit Mapping). With this mapping, when a HR business unit is reported then the GL business unit can be derived and validation performed. If a HR business unit is not mapped to a GL business unit, the system displays an error message. This error message is triggered online, at the point of validation, or during validation in the Submit Time application process.

The TL Product, TL Project,and TL Activity fields can be enabled on the task template depending on the Standard ChartField Configuration and the integration with PS/Projects and PS/EPM. The chart below describes when the fields are available and when they are not.

PRODUCT	TL_Product Available
Combo Code is enabled and Product is an active ChartField.	N
Combo Code enabled and Product is an inactive ChartField.	Y
Combo Code is not enabled.	Y

PROJECT	TL_Project Available
Combo Code is enabled and Project is an active ChartField. Integrate with PS/Projects is either enabled or NOT enabled	N
Combo Code enabled and Project is an inactive ChartField. Integrate with PS/Projects is enabled.	N
Combo Code enabled and Project is an inactive ChartField. Integrate with PS/Projects is NOT enabled.	Y
Combo Code is not enabled and Integrate with PS/Projects is enabled.	N

ACTIVITY	TL_ACTIVITY Available
PS/Project installed	N
PS/EPM installed	N
PS/EPM and PS/Projects are not installed	Y

Impact on Time Reporting Pages

In Time and Labor, the system prepopulates the HR business unit on the transaction pages based on the User ID and the default HR business unit from the JOB record. This value can be overwritten to reflect the user preference when entering transactional details, but to ensure that a HR business unit is reflected for combo code validation, the system performs the prepopulation process.

Task reporting, on transaction rows, is driven by the taskgroup selected (either through default or borrowing). When reporting time you have the option of entering or selecting the Combo Code on the page or using the ChartFields link to search for ChartField combinations or add new ChartField combinations.

See Application Fundamentals: Understanding PeopleSoft ChartFields.

Chartfield Storage on Reported Time and Task Profile

Reported time (TL_RPTD_TBL) and the task profile (TL_TSKPRF_DETL) only store the combo code, they do not store the values for individual chartfields.

ChartField Storage on Payable Time

Payable Time table (TL_PAYABLE_TIME) stores both the combo code and individual ChartField values because ChartField integration with Global Payroll and Payroll for North America are handled differently.

Time and Labor Validation Options

On the Time and Labor Installation page there are three options for ChartField validation.

Term	Definition
Sync Message	This option sends a message with ChartField data to FMS and receives a response of valid or not.
Table Validation	This option uses the Valid Combo Table to allow or deny a combination of individual ChartField values.
None	This options allows you to turn off validation for Time and Labor transactions. Note: If you set the validation option to None, then only individual ChartField values will be validated and not the combination. If a combo code is generated without an associated GL Account, and this combo code is used in the integration with Payroll for North America, the associated transaction will fail when sent to General Ledger. In this case users that are integrating with Payroll for North America should always enter a GL_Account value even if the validation option is set to None.

Term

Definition

Sync Message

This option sends a message with ChartField data to FMS and receives a response of valid or not.

Table Validation

This option uses the Valid Combo Table to allow or deny a combination of individual ChartField values.

None

This options allows you to turn off validation for Time and Labor transactions.

Note: If you set the validation option to None, then only individual ChartField values will be validated and not the combination. If a combo code is generated without an associated GL Account, and this combo code is used in the integration with Payroll for North America, the associated transaction will fail when sent to General Ledger. In this case users that are integrating with Payroll for North America should always enter a GL_Account value even if the validation option is set to None.

GL Account is a required field when sending transactional data to General Ledger from any feeder system. Validations performed using Integration Broker or the Table Validation always require you to enter a GL Account value (at minimum).