Data
The data block of the XML definition defines the fields to be mapped, calculated, and exported by the standard Payroll Export process. Therefore, you must define each field to be exported in this block.
See
Source data.
If you require a temporary field for export purposes, you can define a
<dummy_field>
tag.
Here is an example of a data block:
<data>
<field name='emp_name' />
<field name='emp_lastname'/>
<field name='emp_firstname'/>
<field name='wrkd_work_date'/>
<field name='wrkd_minutes'/>
<field name='wrkd_rate'/>
<field name='dept_name'/>
<field name='emp_val6'/>
<field name='wrks_auth_date'/>
<dummy_field name='earn_code'/>
<dummy_field name='earn_sub_code'/>
</data>
<field name='emp_name'
datatype='int'/>
, which causes the emp_name
column to be
ordered by integer value instead of string. You may want to use this option when the
emp_name
field in your implementation is an integer value. You can only
specify int
for this option. No other values are available.Although dept_name is not in the source data view, the Code Mapper resolves dept_name from dept_id (which is in one of the source data views). You can use fields that can be resolved from an ID in the source data views.
The
<dummy_field>
elements are temporary fields that
you can reference in the mapping logic and formatting section of the XML
definition.
In any payroll XML definition, these data fields must be exported:
- emp_name
- wrkd_work_date
- wrkd_minutes
- wrkd_rate
- dummy_field='earn_code'