Many earnings and deductions - such as salary, pension deductions, and taxes - are discussed under specific functional headings, such as Salary and Grade Related Pay, or Savings and Retirement, or Payroll Statutory Deductions. In this area, we look at payroll earnings and deductions, such as wage attachments, that have not already been covered under other functional headings.
We also focus on additional setup required by Oracle Payroll for processing earnings and deductions. This setup includes the creation of formulas and balances. In some localizations, and for certain types of earnings and deductions, you can select template elements in the Configuration Workbench, or you can use the Element Design Wizard or template windows to generate all the components required for payroll processing, including elements, formulas, balances, and formula result rules.
Certain types of earnings and deductions require additional setup to enable special processing such as net-to-gross and proration, where this is enabled for your localization. Such setup is also discussed in this section.
Note: Mexico only: Oracle HRMS for Mexico does not support net-to-gross processing.
To get the most out of the earnings and deductions functionality of Oracle HRMS, you need to understand the following key concepts:
Pay values
Formulas
Frequency rules
Payroll balances
Earnings and deductions templates
Proration
Net-to-gross processing
Third party payments
Oracle HRMS provides an integrated solution for Human Resources and Payroll. Therefore your setup of compensation and benefits supports both compensation management and payroll management.
Yes it can, through its use of formulas to specify calculations for each earnings or deduction. These formulas use values from the HRMS database and can include conditional logic to perform different calculations for different groups of employees. For example, they can check balances or employee status to control how to process the earning or deduction. Many of the formulas you need, for example for tax calculations, are supplied with Oracle Payroll.
The sequence of processing in a payroll run is determined by classifications, such as Pre-tax Deductions and Tax Deductions. You can also prioritize the processing for an individual employee, for example to determine the order in which deductions are processed for wage attachments.
You control whether any value is processed just once, in every payroll run, or periodically (such as once a quarter). Your formulas can also change or stop the processing of an earning or deduction during a run, based on employee status.
The system can accumulate balances of payroll run results or values entered before the run. You can accumulate a balance over different time dimensions such as current run, month, and year to date. You can review balances after payroll processing and use balances to control the processing performed in the payroll run.
Yes, you can define whatever additional balances your enterprise requires. For example, you may require a Pensionable Earnings balance for a defined benefit pension plan your enterprise offers employees.
Some values, such as salary, can be entered once and used in every payroll run (or periodic runs) until you need to update them. Other values, such as hours worked, need to be entered or calculated fresh for each run.
You can do one of the following:
Use default values (which may be different for groups of employees)
Enter values employee-by-employee
Enter values in a batch
Leave it to the system to enter values based on calculations performed during the payroll run
You can define validation rules to minimize data entry errors.
The wage attachments that you can process depend on the specific payments that apply to your legislation. Examples of payments include child support payments, educational loans, taxes to local authorities, alimony, and bankruptcy orders.
See: Third Party Payments Overview, Oracle HRMS Compensation and Benefits Management Guide
US Only:
When the court issues a release notice for a wage attachment, or if you receive a Form 668-D for a federal tax levy, you must end the employee's wage attachment. Oracle Payroll also stops processing wage attachments when the total owed is reached.
Oracle Payroll supports electronic funds transfer (EFT) of state child support garnishments for the state of Illinois. However, all states accept the Oracle EFT format, but normally require different data dependent upon individual state requirements. You can use the Illinois EFT format to send support payments electronically to all states. You need to include only the information required by the state in the file. You create a separate file for each state containing different routing and account numbers, so you need to set up a separate third party payment method for each state.
Yes, if you operate in the US, you can use the Wage Attachment Fee Administration process to recoup costs. This process recoups costs in administering alimony, bankruptcy orders, employee requested attachments, and tax levies.
Using Wage Attachment Earnings Rules you can determine which earnings types are considered disposable income and liable for wage attachment deductions.
You can determine the overall priority of a wage attachment compared to other deductions, and you can also determine sub priorities. For example, if an employee has multiple court orders against them, you can ensure that Oracle Payroll deducts the most important order first.
The standard processing priority order for processing the various categories of attachment is the following:
Child Support orders
Bankruptcy orders
Federal tax levies
Debt Collection Improvement Act orders
Student loan garnishments
State tax levies (not supported by Oracle Payroll)
Local tax levies (not supported by Oracle Payroll)
Creditor garnishments
Employer deductions
If enabled for your localization, you can use Oracle Payroll's Cheque Writer features to produce cheques for either organizations or individuals. Localizations that do not have Oracle Payroll's Cheque Writer features available can make payments by credit transfer.
You can use an external system to manage your wage attachments. If you want to make entries from that system into Oracle Payroll for payroll processing, you can use predefined deductions that come with Oracle Payroll.
Oracle Payroll fully supports the federal overtime calculation rule. The new functionality performs calculations for periods that are longer than a single workweek. You can configure the product to handle either Federal FLSA or State FLSA. You can also configure alternative overtime calculations as specified by selected states or by union contract.
Oracle Payroll uses the term Augments to refer to amounts paid which are in addition to the employee's regular rate of pay and which are considered to be non-discretionary, such as a commission or bonus. The new functionality prorates the augment across all periods during which it was earned.
Balances show the positive or negative accumulation of particular values over periods of time. They are fed either by the direct run results (that is, Pay Values) of elements processed in the payroll run, or by input values. For example, in North American installations, the input value Hours of the element Time Entry Wages feeds the balance Regular Hours Worked.
Balances exist for various time dimensions, such as current run, period to date, month, quarter to date, and year to date.
Balances also exist at different levels, such as assignment level or person level. Balances for individual employee assignments are at the assignment level (in North America, they can be at the assignment level within a GRE). If your enterprise permits employees to hold more than one assignment at the same time, you can hold balances at the person level. For example, a person level Gross Earnings balance is the sum of an employee's assignment level Gross Earnings balances.
You can select elements to feed a balance in three ways:
Select a primary classification. The run results of all elements in the classification feed the balance. However, you must have an input value of Pay Value if you want to create a feed between an element and a balance.
Select a secondary classification. You choose which elements from a primary classification (such as Earnings) are to feed the balance by giving these elements a secondary classification. Again it is the run results of the elements that feed the balance.
Note: Secondary classifications are not used in the North American versions of Oracle Payroll at this time.
Select an individual element. You can select either the run result or an input value to feed the balance. The input value must have the same unit of measure (such as hours or number) as the balance.
You can choose any number of classifications or any number of elements to feed a balance. However you cannot use a mixture of classifications and individual elements to feed a balance. When you select an element or classification as a balance feed, you specify whether the run results (or input values) should add to or subtract from the balance.
The balances and balance feeds for the elements supplied with Oracle Payroll are present in the system when you receive it. For North American users, when you initiate earnings types, deductions and other items that process in the payroll run, the system generates the appropriate balances and balance feeds together with the necessary elements.
You can define any additional balances your enterprise requires. For example, you may require a Pensionable Earnings balance for a pension plan your enterprise offers employees.
Important: You cannot have two or more elements with the same primary balance. This setup will cause incorrect elements to show up on reports or Statement of Earnings when the process uses balance reporting architecture.
You define primary balance using the following navigation:
Balance window (Total Compensation > Basic > Balance):
You define primary balance by selecting an element and an input value in the Primary Balance region in the Balance window. This type of balance is fed by a single element and can only be inserted if no balance feeds exist for the balance, with the exception of Balance Initialization feeds. When you create a primary balance, the associated feed is created automatically. No other feeds can be created for the balance. Note that if the Primary Balance region is disabled, then the primary balance functionality is not enabled for that localization.
Earnings or Deductions window:
When you create a balance, the balance gets created with name same as that of the element and the element input "Pay Value" gets added as a feed to this balance. This balance is considered as a Primary Balance for this element and can be seen from the Primary Balance field in the Element Description, Further Information window. Changing this Primary Balance in the Further Element Information will result in incorrect values to be reported. For example, Statement of Earnings (SOE) is designed to display the values based on the Primary Balance associated with the elements that are processed.
The following dimensions are predefined. You can create additional dimensions at the assignment level, if you require them.
You are likely to use these dimensions to sum values for single assignments for your own balances.
| _ASG_RUN | during one payroll run |
These statutory dimensions are normally used for summing balance feeds for single assignments to predefined balances.
You can view assignment-level balances for a specific legal entity (indicated by LE in the balance dimension name).
| _ASG_RUN | since the start of this month |
| _ASG_PTD | since the start of this payroll processing period |
| ASG_QTD | since the start of tax year, reset every three months |
| ASG_YTD | since the start of the payroll processing year |
| _ASG_LTD | since the start of the assignment to date |
| _ASG_FQTD | since the start of the fiscal year, reset each fiscal quarter |
| _ASG_FYTD | since the start of the fiscal year, reset each fiscal year |
| _ASG_LE_MONTH | since the start of this calendar month |
| _ASG_LE_PTD | since the start of this payroll processing period |
| _ASG_LE_QTD | since the start of the tax year, reset every three months |
| _ASG_LE_RUN | for this payroll run |
| _ASG_LE_YTD | since the start of the payroll processing year |
| _ASG_LE_LTD | since the start of the assignment to date |
| _ASG_LE_FQTD | since the start of the fiscal year, reset each fiscal quarter |
| _ASG_LE_FYTD | since the start of the fiscal year, reset each fiscal year |
These statutory dimensions are usually associated with predefined balances for summing balance feeds for an employee's multiple assignments, known as person level balances. You can also use these dimensions to show total contributions per person to a specific legal entity, irrespective of the number of assignments held by the employee.
| _PER_MONTH | since the start of this calendar month |
| _PER_PTD | since the start of this payroll period |
| _PER_QTD | since the start of this tax year, reset every three months |
| _PER_RUN | during one payroll period |
| PER_YTD | since the start of the clendar year, reset each year |
| _PER_LTD | since the start of the assignemnts to date |
| _PER_FQTD | since the start of the fiscal year, reset each quarter |
| _PER_LE_MONTH | since the start of this calendar month |
| _PER_LE_PTD | since the start of this payroll period |
| _PER_LE_QTD | since the start of this tax year, reset every three months |
| _PER_LE_RUN | during one payroll period |
| _PER_LE_YTD | since the start of the calendar year, reset each year |
| _PER_LE_LTD | since the start of the assignment to date |
| _PER_LE_FQTD | since the start of the fiscalk year, reset each fiscal quarter |
| _PER_LE_FYTD | since the start of the fiscal year, reset each fiscal year |
This is a special dimension which aggregates results from payroll runs that have been picked up in a particular pre-payments run.
| _PAYMENTS | for a set of payroll runs |
You can select these dimensions in the Accrual Plan window to determine the date for resetting the payroll balance that stores gross accruals.
Dimensions for business groups that use Date Paid as the PTO Balance Type:
| _ASG_PTO_YTD | since the start of the calendar year |
| _ASG_PTO_SM_YTD | since 1 June |
| _ASG_PTO_HD_YTD | since the anniversary of the assignment's hire date |
Dimensions for business groups that use Date Earned as the PTO Balance Type:
| _ASG_PTO_DE_YTD | since the start of the calendar year |
| _ASG_PTO_DE_SM_YTD | since 1 June |
| _ASG_PTO_DE_HD_YTD | since the anniversary of the assignment's hire date |
Use the Balance Feeds window to select balances to be fed by the input values of an element. Balances are either fed by whole classifications of elements or by individual elements, but not by both. Therefore, in this window you cannot select balances that are fed by classifications. You can query a balance in the Balance window and choose the Classifications button to view the list of classifications that feed it.
You can use an element to feed as many balances as you require.
To create balance feeds for one element
Set your effective date to when you want the balance feed to start.
Enter or query the element in the Element window and choose the Balance Feeds button.
In the Balance Feeds window, select the input value that you want to feed the balance with.
The list displays all the input values defined for the element. These input values may have different units of measure. When you select an input value its unit of measure displays in the Units field. To feed a balance with the element's direct run result, select Pay Value.
Select the balance you want the input value to feed.
The list restricts your choice to balances having the same unit of measure as the input value you selected.
To calculate Voluntary CPF Contribution, feed the Voluntary CPF Contribution element to the following balances:
Employer Vol CPF Contributions Ordinary Earnings
Employee Vol CPF Contributions Ordinary Earnings
Employer Vol CPF Contributions Additional Earnings
Employee Vol CPF Contributions Additional Earnings
For 1984 Frozen CPF Calculation, feed the CPF Elig Comp 1984 Frozen Earnings element to the following balances:
CPF Elig Comp 1984 Frozen Salary and Other Earnings
CPF Elig Comp 1984 Frozen NPVP
CPF Elig Comp 1984 Frozen NPC
Select Add or Subtract for the balance feed.
In the Balance Feed Control window, you can classify an element using secondary classifications. These determine the balances that the element feeds. You can query a balance in the Balance window and choose the Classifications button to view the list of classifications that feed it.
To select or remove secondary element classifications
Set your effective date to when you want the element to begin feeding the balances that the secondary classifications feed.
Enter or query the element in the Element window and choose the Balance Feed Control button.
In the Balance Feed Control window, delete any default secondary classifications you do not require for the element.
When this window opens, it displays any default secondary classifications for the element's primary classification. Unless they are predefined, you can delete any of these classifications, and you can change their effective start dates.
Select any non-default secondary classifications you require.
Defining a balance includes defining its feeds and dimensions. When selecting feeds for the balance you have to choose between specifying element input values directly, and selecting element classifications to determine the feeds. You cannot choose both methods together.
You can group similar balances - such as all earnings balances - in a single category for quicker and easier processing. Each localization has a defined set of categories. If there are no categories in the list of values, this means your legislation is not yet using the category functionality.
Balances often share a common relevancy to certain assignments. In some localizations, you can define base balances to imply a relationship between the balances that can be relied upon when processing and reporting. For example, "Loan Repayment" could be the base balance for "Loan Repayment Arrears".
You define balances in the Balance window.
To define a user balance
Do one of the following:
Enter a unique name and a reporting name for the new balance. If you do not provide a reporting name, the first seven characters of the balance name appear on reports.
Query any user balances you want to change.
Optionally, select a balance category in the Category field.
Australian Users: Attach all user-defined balances to the relevant balance category and to the _ASG_RUN and _ASG_YTD dimensions to populate the run balances. You must attach all user-defined allowance balances required to be reported individually on the Payment Summary to the Balance Category of Allowance and to the _ASG_LE_RUN and _ASG_LE_YTD dimensions.
New Zealand Users: You must assign a balance category for each element that you define.
Optionally, select a Base Balance.
Enter the unit of measure for the balance. The choices are days, hours (listed in different formats), integer, money and number. If you select money as the unit you must also select a currency.
Note: Do not select the Use for Remuneration check box. This displays the balance that has been predefined as the Remuneration balance. Only one balance within a legislation can have this value.
To define a primary balance - one fed by a single element - select an element and input value in the Primary Balance region (if this region is available for your localization).
Go to the Balance Feeds window or the Balance Classifications window.
Set your effective date to the start date for the balance feeds.
Select one or more elements to feed the balance. Only those elements whose input values have the same unit of measure as the balance are listed.
When you select an element, its classification is displayed. You can select elements with different classifications.
Select the input value that is to feed the balance.
For most payroll balances select Pay Value so that the element's run result feeds the balance.
Select Add or Subtract for the balance feed.
Select one or more element classifications and select Add or Subtract for each. The run results of all elements in the classification will feed the balance.
The list includes all the primary and secondary element classifications that are valid for this balance. If you select a secondary classification, you cannot also select its parent primary classification.
Note: Secondary classifications are not used in the North American or Singapore versions of Oracle Payroll at this time.
Choose the Dimensions button.
Select the dimensions you require.
New Zealand Users: For each new balance, you must attach the balance dimension _ASG_RUN for it to generate run balances.
Australian Users: Select the _ASG_RUN and _ASG_YTD dimensions for all user-defined balances. You must attach the _ASG_LE_YTD and _ASG_LE_RUN dimensions to the allowance balances required in the Payment Summary reports.
You can remove any dimension previously selected for a user-defined balance. You can also add dimensions to the startup balances included with your system, and later remove these additional dimensions. However, you cannot remove the dimensions that were predefined for the startup balances.
Note: To hold balances for a fiscal year that is different from the calendar year, you must supply the fiscal year start date for your Business Group.
Optionally, select the Grossup Balance check box for one of the dimensions, to make the balance eligible for grossup.
UK users: If you want to make the balance eligible for grossup, you must select this check box for the _ASG_RUN dimension.
Choose the Initial Feed button.
In the Initial Balance Feed window you can see details of the element and input value used for the Initial Balance feed. This feed is defined by implementation consultants prior to performing an initial balance upload at implementation time.
Choose the Attributes button.
Select an attribute definition and a dimension.
Balance attributes identify which balances can be used in which reports. Attributes can be predefined by localizations, created as a result of predefined defaults, or you can enter them in this window.
Note: For UK SOE Balances, ensure you attach the attribute to the Balances1 segment in the Business Group Information. Attach the attribute to each balance you want to display on the Online SOE. For every balance with an attached attribute, you must add individual balance to the SOE Details Information (in the Business Group Information).
The balances you attach to the SOE Details Information are defined at business group level, hence even if you change the user category profile it will not have any result on the data defined in the SOE Details Information.
Additional Information: Saudi Users: Oracle Payroll provides Saudi SOE Balance Attributes to view the SOE report. You can use the predefined balance attributes or create your own balance attributes.
Oracle Payroll enables employers to calculate and deduct the statutory contributions paid by employees and employers. Oracle HRMS for Singapore supports the following deductions:
Central Provident Fund (CPF)
Foreign Workers Levy (FWL)
Skills Development Fund Levy (SDL)
Central Provident Fund (CPF)
Community Funds
Community Chest/SHARE
Oracle Payroll provides as startup all the elements, balances and other components that you need to process voluntary and involuntary employer and employee deductions that are payable to the CPF Board and other legislative deductions, including FWL. Payments are made in the monthly CPF report.
It also provides legislative upgrades to keep your payroll processing up to date with current legislation.
Oracle HRMS provides a Statutory Deductions element that is used to process all employee and employer deductions. SG_STAT, a formula that is attached to the Statutory Deductions element, is used to calculate and initiate the various statutory deductions, except for Community Fund, which uses the SG_COMM_FUND formula. This approach enables multiple results to be stored against the specific contribution type and provides a single source of information about that contribution for reporting purposes.
See: Predefined Elements for a list of the elements provided with Oracle HRMS for Singapore.
Community Chest/SHARE deductions are the voluntary monthly donations made to the Community Chest (ComChest) fund-raising organization.
Community Fund deductions are employee involuntary and voluntary deductions that are paid to one or more community funds, for example, the Chinese Development and Assistance Fund, on a monthly basis. The amount that is deducted from an employee is determined using the Community Fund rates tables.
Monthly employer and employee CPF deductions (both mandatory and voluntary), are paid to the CPF Board for all employees who are Singapore citizens or permanent residents. CPF deductions are based on eligible employees' total earnings, including additional earnings, such as bonuses or overtime payments. The amount of CPF payable is calculated using the 13 CPF rate tables.
The monthly employer FWL deduction is paid to the Ministry of Manpower for all foreign national employees holding a valid work permit. Oracle HRMS identifies non-Singaporean employees holding valid work permits, and then uses the FWL rates table to calculate the amount payable, either using a daily rate if the work permit was not valid for the entire month, otherwise using a flat monthly rate.
The monthly employer SDL deduction is payable for each employee whose basic monthly salary is less than a predefined amount.
Oracle HRMS enables you to calculate proportionate earnings amounts whenever payroll-relevant data is changed during a payroll period, for example, if an employee joins or leaves the company during a payroll period or if an employee's pay grade changes during a payroll period. Oracle HRMS performs a proration calculation to ensure that the employees' earnings are calculated correctly after taking account of these changes.
If you want to prorate an earnings element, such as basic salary, assign an event group to it. An event group is a collection of proration points that share similar characteristics. You can create an event group to group together all proration points that affect an employee's salary, for example. This event group could contain proration points such as salary increases, assignment changes, and pay rate changes.
You then process the element using a formula that handles proration. You can either use a payroll formula that handles proration, or create a separate proration formula that runs after the main payroll formula only in payroll periods when a proration event occurs.
See: Sample Payroll Formulas Enabled for Proration (UK), Oracle HRMS FastFormula User Guide, Sample Proration Formula, Oracle HRMS FastFormula User Guide, and Writing Proration Formulas, Oracle HRMS FastFormula User Guide
When you define the event group, you select the events that will activate proration calculation, such as:
An employee joining or leaving the enterprise
Changes to pay grades or grade rates
Changes to pay scales and progression points
Changes to hourly or annual pay rates
Changes to working hours
Changes to allowances or deductions
Note: The proration unit can be periods, days, or hours. Proration can be applied to a monetary, time-based, or numeric amount.
Follow these steps if you want to set up your system for proration or retro-notification.
To complete basic setup for proration or retro-notification
In the Table Event Updates window, ensure that the events you want to use are already included in the required tables. Enter the table name. The lower half of the screen displays the fields that trigger proration or retro-notification if their values are changed.
If the table has already been defined but the required event is missing, create either an Update, Delete, or Insert event and enter the table row or column to which the event refers. You can only enter a column name if you are creating an Update event. Select the change type defined by the event.
Note: The Table Event Update window is not available in all localizations.
See: Making Table Event Updates, Oracle HRMS Payroll Processing Management Guide
If the events you require have not been defined in the Table Event Update window, set up the dynamic triggers for proration or retro-notification in the Dynamic Trigger Generation window. The triggers you need depend on the method you use to compensate your employees. For example, the tables required for compensation using Salary Administration are different from those required for compensation using pay grades. The tables you are likely to use are:
PER_ALL_ASSIGNMENTS_F
PER_ALL_PEOPLE_F
PAY_ELEMENT_ENTRIES_F
PAY_ELEMENT_ENTRY_VALUES_F
PER_SPINAL_POINT_PLACEMENTS_F
PER_GRADE_RULES_F
See: Defining Dynamic Triggers, Oracle HRMS Payroll Processing Management Guide
Note: French users: Ensure you enable the dynamic triggers for PAY_ELEMENT_ENTRIES_F and PER_ALL_ASSIGNMENTS_F.
Create an event group for your proration or retro-notification events. You must create the event groups before you can create your elements.
Select the Incident Register functional area in the Functional Area Maintenance window. Make sure that your triggers are included in this functional area. If your triggers are not included, insert them.
You must also activate the triggers according to legislation or business group. For more information, see: Grouping Dynamic Triggers into Legislative Functional Areas, Oracle HRMS Payroll Processing Management Guide
Setup for retro-notification should now be complete, meaning you can proceed to running the appropriate report. However, if you are setting up proration continue with the next steps.
To set up the elements for proration
Create your proration element. US and Mexico users: Initiate the earnings type or deduction, then query the generated element in the Element window to add a proration group and, optionally, a proration formula.
Make sure that you select a proration group for each element
Select a proration formula if you are using a separate proration formula to handle proration events (rather than enabling your payroll formula to handle proration)
Select Actual Termination as the termination processing rule
Define the input values for the element. For example, if you were using the sample payroll formulas that are enabled for proration, you would create the following input values:
Amount for a salary management element
Date Worked for a spinal point/pay scale element
Annual Deduction for a deduction or allowance
See: Defining an Element's Input Values, Oracle HRMS Compensation and Benefits Management Guide
Link the element to a specific payroll or payrolls. If you want the element to be used automatically each time the payroll is assigned, select the Standard check box. If you do not select this check box, you must enter the element for each assignment.
See: Defining Element Links, Oracle HRMS Compensation and Benefits Management Guide
To create the formula
Check that the database items to be used in your formula are available. If the required database items are not available, create them.
Create the proration formula or write a payroll formula that is enabled for proration.
To create a proration formula, see: Writing Proration Formulas, Oracle HRMS FastFormula User Guide
UK users: For examples of payroll formulas enabled for proration, see: Sample Payroll Formulas Enabled for Proration, Oracle HRMS FastFormula User Guide
For more information on writing formulas, see: Writing or Editing a Formula, Oracle HRMS FastFormula User Guide and Writing Payroll Formulas for Elements, Oracle HRMS FastFormula User Guide
Link the formula to your element in the Formula Result Rules window.
See: Defining Formula Processing and Result Rules, Oracle HRMS FastFormula User Guide
Attach the element to the salary basis if the salary is relevant for proration. Select the input value you created (such as Amount) in the Input Value Name field of the Salary Basis window.
See: Defining a Salary Basis, Oracle HRMS Compensation and Benefits Management Guide
You define an event group from the Table Event Group window. You use an event group to group together all proration or retro-notification points that affect an employee's salary, such as salary increases.
To define an event group
Enter a name for your event group.
Select one of the following event group types:
Proration for a proration event group
Retro for a retro-notification event group
Select the proration or retro period.
Save your entries.
Select the events that can trigger proration or retro-notification in the Datetracked Events region. To do this, select the update type, the table containing the data, and the table column.
Save your work.