SET Operations on HDL file in Fusion

SET CREATE_DEFAULT_WORKING_HOUR_PATTERN Y/N
To request automatic creation of a default working-hour pattern for all worker assignments in a Worker.dat file, include the SET CREATE_DEFAULT_WORKING_HOUR_PATTERN instruction.
For example:
SET CREATE_DEFAULT_WORKING_HOUR_PATTERN Y

SET DISABLE_POST_PROCESS_TASKS
By default, these processes run automatically after we load worker.dat file:
Refresh Manager Hierarchy
Update Person Search Keywords
To prevent Refresh Manager Hierarchy from running automatically, include this SET instruction in the Worker.dat file:
SET DISABLE_POST_PROCESS_TASKS RefreshManagerHierarchy
To prevent Update Person Search Keywords from running automatically, include this SET instruction in the Worker.dat file:
SET DISABLE_POST_PROCESS_TASKS UpdatePersonSearchKeywords
Tip: To prevent both processes from running automatically, use the SET INVOKE_POST_PROCESS instruction.

SET INVOKE_POST_PROCESS
By default, these processes run automatically after we load workers:
Refresh Manager Hierarchy
Update Person Search Keywords
To prevent both processes from running automatically, include this SET instruction in the Worker.dat file:
SET INVOKE_POST_PROCESS N

SET FILE_DELIMITER
Use this instruction to change the default file delimiter, which is the vertical bar (|). For example, to change it to a comma, include this instruction:
SET FILE_DELIMITER ,
The new value can be up to 10 characters.

SET FILE_ESCAPE
Use this instruction to change the default file escape character, which is the backslash (). For example, to change it to the equal sign (=), include this instruction:
SET FILE_ESCAPE =
The new value can be up to 10 characters.

SET FILE_NEWLINE
Use this instruction to change the default file newline character, which is the character n. For example, to change it to the string newline, include this instruction:
SET FILE_NEW_LINE newline
The new value can be up to 10 characters. For example, you could set the newline character to newline and the file delimiter to comma (,) using the following SET commands:

SET FILE_DELIMITER ,
SET FILE_NEW_LINE newline
In this case, METADATA and MERGE lines could appear as follows:
METADATA,Address,AddressLine1
MERGE,Address,TheSteadingnewlineKier Allan

SET PURGE_FUTURE_CHANGES
When you create business objects containing date-effective components, you include this instruction at the start of the file:
SET PURGE_FUTURE_CHANGES Y -> Replace mode
This instruction sets the date-effective maintenance mode to Replace. In this mode, which is the default mode, the contents of the .dat file replace any existing data.
A single record replaces existing date effective records for the date range specified on the update.
SET PURGE_FUTURE_CHANGES N -> Retain Mode
This instruction sets the date-effective maintenance mode to Retain. In this mode, any existing future-dated changes are retained.

Example:
To change the working hours to 37.5 from 2012/01/10 without affecting future-dated records, you use this data file:
SET PURGE_FUTURE_CHANGES N
METADATA|Assignment|SourceSystemId|EffectiveStartDate|EffectiveSequence|EffectiveLatestChange|EffectiveEndDate|ActionCode|NormalHours
MERGE|Assignment|223724|2012/01/10||Y|#RETAIN|ASG_CHANGE|37.5

SET ENABLE_INCREMENTAL_LOAD_EVENTS Y in Worker.dat or Salary.dat to enable triggers such as Benefit life events

If you know any other SET operations post them in the comments section, I will update the post with those details.

Tip: SET commands are used to override the default behavior of HCM Data Loader and can be effectively used for achieving requirement.