Payroll Transformation Formula Operations
The transformation formula is invoked several times to derive different components that are required for processing the incoming data.
This table explains the various operations that you can do with the formula.
Operation Type |
Return Value |
Example |
---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Delimiter
The default delimiter that separates values is a pipe character. If your file uses a different delimiter, you must set the delimiter you want your formula.
This example specifies a comma character as the delimiter.
/* Calculations */
IF OPERATION='FILETYPE' THEN
OUTPUTVALUE='DELIMITED'
ELSE IF OPERATION='DELIMITER' THEN
OUTPUTVALUE=','
MAP
The MAP operation defines the return values related to a particular object. The return values must have the same names as the attributes specified in the application for that object.
For example, these RETURN values can be used to generate an Element Entry dat file.
RETURN BusinessOperation,FileDiscriminator,FileName,AssignmentId,AssignmentNumber,CreatorType,DateEarned,EffectiveEndDate,EffectiveStartDate,ElementEntryId,ElementName,ElementTypeId,EntryType,GUID,LegislativeDataGroupId,LegislativeDataGroupName,MultipleEntryCount,Reason,SourceSystemId,SourceSystemOwner,Subpriority
Here, the BusinessOperation
is set to MERGE and the BusinessObject
is set to Element Entry.
METADATALINEINFORMATION
The application generates the file either
with all defined attributes or with only specified attributes, depending
on whether you specify a value for METADATALINEINFORMATION
or not.
-
If you don't specify a value for
METADATALINEINFORMATION
, then the application generatesMETADATLINE
in the transformed file with all defined attributes for the business object. -
If you specify a value, then the transformed file will contain only the attributes that you specified.
For the METADATALINEINFORMATION
operation, you specify an array per business object being processed
in the formula. The number of arrays should match the number specified
in the NUMBEROFBUSINESSOBJECTS
operation.
The name of the array should be METADATA
with the number as suffix . For example, RETURN
METADATA1
, METADATA2
when
the NUMBEROFBUSINESSOBJECTS
is 2.
Note: The first two entries in the array are reserved
to specify the FileName
and FileDiscriminator
of the business object.
Additionally, for METADATALINEINFORMATION
, you can specify attributes with special characters for that business
objects.
Notice that in this example BalAdjBatchId(SourceSystemId)
has parenthesis.
If the file contains either Flexfield or SourceSystem references, then the application can't resolve the default mapping of output parameter names and attributes.
Let's consider this syntax: jobEffSegment1(PER_JOBS_EIT_EFF=context)
. To allow this
construct to be generated in the HCM Data Loader file, you define
the METADATA
line in the transformation
formula. For each business object that appears in the output, you
must define the METADATA
content in
an array.
Example:
METADATA2[1] = 'Job' /*FileName*/
METADATA2[2] = 'JobExtraInfo' /*FileDiscriminator*/
METADATA2[3] = 'EffectiveStartDate'
METADATA2[4] = 'EffectiveEndDate'
METADATA2[5] = 'JobCode'
METADATA2[6] = 'SetCode'
METADATA2[7] = 'FLEX:PER_JOBS_EIT_EFF'
METADATA2[8] = 'EFF_CATEGORY_CODE'
METADATA2[9] = 'InformationType'
METADATA2[10] = 'JeiInformationCategory'
METADATA2[11] = 'LegislationCode'
METADATA2[12]= 'SequenceNumber'
METADATA2[13]= 'jobEffSegment1(PER_JOBS_EIT_EFF=job-eff-context)'
Here's how the generated HCM Data Loader file looks like.
METADATA|JobExtraInfo|EffectiveStartDate|EffectiveEndDate|JobCode|SetCode|FLEX:PER_JOBS_EIT_EFF|EFF_CATEGORY_CODE|InformationType|JeiInformationCategory|LegislationCode|SequenceNumber|jobEffSegment1(PER_JOBS_EIT_EFF=job-eff-context)
NUMBEROFBUSINESSOBJECTS
This operation indicates the number of business objects being processed in the formula.