Configuring an application ingestion and replication task

Source Objects

• •On the Selected Objects tab, individually select the check box for each source object you want to include. Clear the check box for any objects you do not want to include. To select all objects, select the Object check box at the top.
The Field count for an object shows the total number of fields in the object.
If you select the objects you want to include, all the selected and unselected objects are displayed by default. To view the selected objects only, use the filter next to the object selection count and change the view from All to Selected.
To find objects or fields, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns objects and fields that include CDC anywhere in their names. To narrow the search to only object names or field names, select Object Name or Fields in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for objects.
To add an object rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without wildcards, as the condition.
Tips:
• - You can copy an existing object rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit an object rule directly in its row by clicking the Type or Match Condition value.
• - To view the objects and fields that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the object names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If an object name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple object rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if an object rule specifies "Exclude CDC" followed by "Include C", all objects with names beginning with "C" are selected, including the CDC objects.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Objects by Rule Type	Generate and download a list of the source objects that match the object selection criteria. If you used rule-based object selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Fields check box to include fields in the list, regardless of which object selection method you used. Click the Download icon to download the list.
Start Date	For initial load and combined initial and incremental load jobs, specify the date and time when the ingestion job should start replicating the source data.
Initial Start Poing for Incremental Load	For incremental load jobs, specify the point in the source data stream from which the ingestion job associated with the application ingestion and replication task starts extracting change records. Note: You must specify the date and time in Coordinated Universal Time (UTC).
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Tables

• •On the Selected Tables tab, individually select the check box for each source table you want to include. Clear the check box for any tables you do not want to include. To select all tables, select the Table check box at the top.
The Column count for a table shows the total number of columns in the table.
If you select the tables you want to include, all the selected and unselected tables are displayed by default. To view the selected tables only, use the filter next to the table selection count and change the view from All to Selected.
To find tables or columns, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns tables and columns that include CDC anywhere in their names. To narrow the search to only table names or column names, select Table Name or Columns in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for tables.
To add a table rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without wildcards, as the condition.
Tips:
• - You can copy an existing table rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit a table rule directly in its row by clicking the Type or Match Condition value.
• - To view the tables and columns that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the table names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If a table name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple table rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if a table rule specifies "Exclude CDC" followed by "Include C", all tables with names beginning with "C" are selected, including the CDC tables.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Tables by Rule Type	Generate and download a list of the source tables that match the table selection criteria. If you used rule-based table selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Columns check box to include columns in the list, regardless of which table selection method you used. Click the Download icon to download the list.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. Note: You must specify the date and time in Coordinated Universal Time (UTC).
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Tables

• •On the Selected Tables tab, individually select the check box for each table and column you want to include. Clear the check box for any table and column you do not want to include. To select all tables and columns, select the Table check box at the top.
The Column count for a table shows the total number of columns in the table.
Note:
If you deselect one or more columns for a table, a minus (-) appears next to the table name in the list.
If you select the tables you want to include, all the selected and unselected tables are displayed by default. To view the selected tables only, use the filter next to the table selection count and change the view from All to Selected.
To find tables or columns, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns tables and columns that include CDC anywhere in their names. To narrow the search to only table names or column names, select Table Name or Columns in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for tables and columns.
• - To add a table rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without the wildcards, as the condition.
• - To add a column rule for a table, click the plus (+) sign at the right end of the table row. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without the * wildcard, as the condition.
• - Validate the rule. The validation warns if your rule excludes a primary key column.
Tips:
• - You can copy an existing table rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit a table or column rule directly in its row by clicking the Type or Match Condition value.
• - To view the tables and columns that match a rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the table and column names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If a table or column name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple table rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if a table rule specifies "Exclude CDC" followed by "Include C", all objects with names beginning with "C" are selected, including the CDC object.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Tables by Rule Type	Generate and download a list of the source tables that match the table selection criteria. If you used rule-based table selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Columns check box to include columns in the list, regardless of which table selection method you used. Click the Download icon to download the list.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. Note: You must specify the date and time in Greenwich Mean Time (GMT).
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes.
Fetch Size	Enter the number of records that the application ingestion and replication job associated with the task reads at a time from the source. The default value is 5000.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Objects

• •On the Selected Objects tab, individually select the check box for each source object you want to include. Clear the check box for any objects you do not want to include. To select all objects, select the Object check box at the top.
The Field count for an object shows the total number of fields in the object.
If you select the objects you want to include, all the selected and unselected objects are displayed by default. To view the selected objects only, use the filter next to the object selection count and change the view from All to Selected.
To find objects or fields, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns objects and fields that include CDC anywhere in their names. To narrow the search to only object names or field names, select Object Name or Fields in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for objects.
To add an object rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without wildcards, as the condition.
Tips:
• - You can copy an existing object rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit an object rule directly in its row by clicking the Type or Match Condition value.
• - To view the objects and fields that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the object names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If an object name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple object rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if an object rule specifies "Exclude CDC" followed by "Include C", all objects with names beginning with "C" are selected, including the CDC objects.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Objects by Rule Type	Generate and download a list of the source objects that match the object selection criteria. If you used rule-based object selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Fields check box to include fields in the list, regardless of which object selection method you used. Click the Download icon to download the list.
Include Child Objects	Get the child object data of an object using an Oracle Fusion Cloud source. This applies only for the REST replication approach and for all load types only when the target is Google Big Query.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. Note: You must specify the date and time in the time zone configured for the Oracle Fusion Cloud instance.
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes.
Fetch Size	Enter the number of records that the application ingestion and replication job associated with the task reads at a time from the source. The default value is 50000.
Enable chunking	Select this checkbox to chunk data during the extraction process in an application ingestion and replication task. Chunking applies to initial load tasks, and in the initial portion in combined initial and incremental load tasks that use the BICC replication approach. Chunking is not applicable for CDC tasks. Options are: - None. Extracts data as a whole without dividing it into chunks. Default is None. - By Primary Key. Select this option to chunk data based on a numeric primay key. This option requires that your datastore contains a single numeric primary key column without Null values. - By Creation Date. Select this option to divide data into chunks at intervals defined by the number of days for date range extraction. This option requires selection of the Is Creation Date option in the BICC Console for a column or columns in the column list, which represent the creation date.
Number of Rows	If you select the By Primary Key chunking option, specify the number of rows to chunk extracts. Enter a positive integer. Make sure that the combination of total rows and chunk size results in no more than 250 chunks. For example, if you have 2500 rows with a chunk size of 10, it results in 250 chunks, which is the maximum chunks allowed.
Number of Days	If you select the By Creation Date chunking option, enter the number of days to set the interval for data extraction. For example, if you specify 365 days, the data is divided into segments that each cover a 365-day period, starting from the initial date. To prevent performance issues, consider specifying a larger number of days for the interval.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Objects

• •On the Selected Objects tab, individually select the check box for each source object and field you want to include. Clear the check box for any objects and fields you do not want to include. To select all objects and fields, select the Object check box at the top.
The Field count for an object shows the total number of fields in the object.
Note:
If you deselect one or more fields for an object, a minus (-) appears next to the object name in the list.
If you select the objects you want to include, all the selected and unselected objects are displayed by default. To view the selected objects only, use the filter next to the object selection count and change the view from All to Selected.
To find objects or fields, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns objects and fields that include CDC anywhere in their names. To narrow the search to only object names or field names, select Object Name or Fields in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for objects and fields.
• - To add an object rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without the wildcards, as the condition.
• - To add a field rule for an object, click the plus (+) sign at the right end of the object row. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without the * wildcard, as the condition.
• - Validate the rule. The validation warns if your rule excludes a primary key field.
Tips:
• - You can copy an existing object rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit an object or field rule directly in its row by clicking the Type or Match Condition value.
• - To view the objects and fields that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the object and field names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If an object or field name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple object rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if an object rule specifies "Exclude CDC" followed by "Include C", all objects with names beginning with "C" are selected, including the CDC object.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Objects by Rule Type	Generate and download a list of the source objects that match the object selection criteria. If you used rule-based object selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Fields check box to include fields in the list, regardless of which object selection method you used. Click the Download icon to download the list.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. Note: You must specify the date and time in Greenwich Mean Time (GMT).
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes.
Fetch Size	Enter the number of records that the application ingestion and replication job associated with the task reads at a time from the source. The default value for initial load operations is 50000 and the default value for incremental load operations is 2000. Note: For combined initial and incremental load tasks, you must specify the fetch size separately for initial load operations and incremental load operations.
Include Base64 Fields	Select this check box to replicate the source fields of Base64 data type. Note: - You can replicate the Base64 fields only if you select Standard (REST) API as the Salesforce API. - Replication of Base64 data might slow down the initial load operation of the application ingestion and replication job.
Maximum Base64 Body Size	If you selected the Include Base64 Fields check box, specify the maximum body size in megabytes (MB) for Base64 encoded data.
Include Archived and Deleted Rows	For initial load and combined initial and incremental load jobs, select this check box to replicate the archived and soft-deleted rows from the source during the initial loading of data.
Enable Partitioning	For initial load and combined initial and incremental load tasks, select this check box to partition the source objects for initial loading.
Chunk Size	If you enable partitioning of source objects,enter the number of records to be processed in a single partition. Based on the chunk size, bulk jobs are created in Salesforce. The default value is 50000 and the minimum value is 100.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Salesforce Max Parallel Partition	The maximum number of partition threads that can be used to query the source for data in parallel during initial load processing or the unload phase of combined jobs. Use this property to control the number of source partition queries that can be executed against the source at the same time. For example, if a table contains data in 100 partitions, all 100 partitions are queried at the same time by default. However, you can use this property to reduce the number of concurrent queries. Default value is equal to the total number of partitions.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Objects

• •On the Selected Objects tab, individually select the check box for each source object you want to include. Clear the check box for any objects you do not want to include. To select all objects, select the Object check box at the top.
The Field count for an object shows the total number of fields in the object.
If you select the objects you want to include, all the selected and unselected objects are displayed by default. To view the selected objects only, use the filter next to the object selection count and change the view from All to Selected.
To find objects or fields, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns objects and fields that include CDC anywhere in their names. To narrow the search to only object names or field names, select Object Name or Fields in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for objects.
To add an object rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without wildcards, as the condition.
Tips:
• - You can copy an existing object rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit an object rule directly in its row by clicking the Type or Match Condition value.
• - To view the objects and fields that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the object names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If an object name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple object rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if an object rule specifies "Exclude CDC" followed by "Include C", all objects with names beginning with "C" are selected, including the CDC objects.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Objects by Rule Type	Generate and download a list of the source objects that match the object selection criteria. If you used rule-based object selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Fields check box to include fields in the list, regardless of which object selection method you used. Click the Download icon to download the list.
Batch Size	Enter the number of records that the application ingestion and replication job associated with the task reads at a time from the source. Default is 2500.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Tables

• •On the Selected Tables tab, individually select the check box for each source table you want to include. Clear the check box for any tables you do not want to include. To select all tables, select the Table check box at the top.
The Column count for a table shows the total number of columns in the table.
If you select the tables you want to include, all the selected and unselected tables are displayed by default. To view the selected tables only, use the filter next to the table selection count and change the view from All to Selected.
To find tables or columns, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns tables and columns that include CDC anywhere in their names. To narrow the search to only table names or column names, select Table Name or Columns in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for tables.
To add a table rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without wildcards, as the condition.
Tips:
• - You can copy an existing table rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit a table rule directly in its row by clicking the Type or Match Condition value.
• - To view the tables and columns that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the table names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If a table name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple table rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if a table rule specifies "Exclude CDC" followed by "Include C", all tables with names beginning with "C" are selected, including the CDC tables.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Tables by Rule Type	Generate and download a list of the source tables that match the table selection criteria. If you used rule-based table selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Columns check box to include columns in the list, regardless of which table selection method you used. Click the Download icon to download the list.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs.
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 1 day.
Fetch Size	Enter the number of records that the application ingestion and replication job associated with the task reads at a time from the source.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Data Sources

• •On the Selected Data Sources tab, individually select the check box for each data source you want to include. Clear the check box for any data sources you do not want to include. To select all data sources, select the Data Source check box at the top.
The Field count for a data source shows the total number of fields in the data source.
If you select the data sources you want to include, all the selected and unselected data sources are displayed by default. To view the selected data sources only, use the filter next to the data source selection count and change the view from All to Selected.
To find data sources or fields, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns data sources and fields that include CDC anywhere in their names. To narrow the search to only object names or field names, select Data Source Name or Fields in the drop-down list adjacent to the Find box.
• •Click Show Fields to display the actual columns from the SAP source. Otherwise, the columns for the selected data sources display as dummy.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for data sources.
To add a data source rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without wildcards, as the condition.
Tips:
• - You can copy an existing data source rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit a data source rule directly in its row by clicking the Type or Match Condition value.
• - To view the data sources and fields that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the data sources to be included. For an Exclude rule, it shows the data sourcess to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the data source names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If an object name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple data source rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if a data source rule specifies "Exclude CDC" followed by "Include C", all data sources with names beginning with "C" are selected, including the CDC data source.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Data Sources by Rule Type	Generate and download a list of the data sources that match the table selection criteria. If you used rule-based table selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Fields check box to include fields in the list, regardless of which object selection method you used. Click the Download icon to download the list.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. Note: By default, the ingestion job retrieves the change records from the latest available position in the data stream.
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes. Note: The CDC interval must be less than the data retention period configured in the SAP system for the Operational Delta Queue (ODQ).
Fetch Size	Enter the size of data that the application ingestion and replication job associated with the task reads at a time from the source. The value must be in megabytes (MB). The default value is 8.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Tables

• •On the Selected Tables tab, individually select the check box for each table and column you want to include. Clear the check box for any table and column you do not want to include. To select all tables and columns, select the Table check box at the top.
The Column count for a table shows the total number of columns in the table.
Note:
If you deselect one or more columns for a table, a minus (-) appears next to the table name in the list.
If you select the tables you want to include, all the selected and unselected tables are displayed by default. To view the selected tables only, use the filter next to the table selection count and change the view from All to Selected.
To find tables or columns, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns tables and columns that include CDC anywhere in their names. To narrow the search to only table names or column names, select Table Name or Columns in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for tables and columns.
• - To add a table rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without the wildcards, as the condition.
• - To add a column rule for a table, click the plus (+) sign at the right end of the table row. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without the * wildcard, as the condition.
• - Validate the rule. The validation warns if your rule excludes a primary key column.
Tips:
• - You can copy an existing table rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit a table or column rule directly in its row by clicking the Type or Match Condition value.
• - To view the tables and columns that match a rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the table and column names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If a table or column name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple table rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if a table rule specifies "Exclude CDC" followed by "Include C", all objects with names beginning with "C" are selected, including the CDC object.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
CDC Script	For incremental loads and combined initial and incremental loads, generate a script for enabling CDC on source tables and then run or download the script. The only available option is Enable CDC for all columns. Click Execute to run the script if you have the required privileges. Or click the Download icon to download the script so that you can give it to your DBA to run.
List Tables by Rule Type	Generate and download a list of the source tables that match the table selection criteria. If you used rule-based table selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Columns check box to include columns in the list, regardless of which table selection method you used. Click the Download icon to download the list.
Enable Persistent Storage	For incremental loads and combined initial and incremental loads, select this check box to enable persistent storage of transaction data in a disk buffer so that the data can be consumed continually, even when the writing of data to the target is slow or delayed. Benefits of using persistent storage are faster consumption of the source transaction logs, less reliance on log archives or backups, and the ability to still access the data persisted in disk storage after restarting an ingestion job. Persisted data is stored on the Secure Agent. It is not encrypted. The Secure Agent's files and directories are expected to be secured from unwanted access by using native file system access permissions or file system support of encryption natively.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. Note: By default, the ingestion job retrieves the change records from the latest available position in the data stream.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Tables

• •On the Selected Tables tab, individually select the check box for each source table you want to include. Clear the check box for any tables you do not want to include. To select all tables, select the Table check box at the top.
The Column count for a table shows the total number of columns in the table.
If you select the tables you want to include, all the selected and unselected tables are displayed by default. To view the selected tables only, use the filter next to the table selection count and change the view from All to Selected.
To find tables or columns, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns tables and columns that include CDC anywhere in their names. To narrow the search to only table names or column names, select Table Name or Columns in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for tables.
To add a table rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without wildcards, as the condition.
Tips:
• - You can copy an existing table rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit a table rule directly in its row by clicking the Type or Match Condition value.
• - To view the tables and columns that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the table names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If a table name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple table rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if a table rule specifies "Exclude CDC" followed by "Include C", all tables with names beginning with "C" are selected, including the CDC tables.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Property	Description
List Tables by Rule Type	Generate and download a list of the source tables that match the table selection criteria. If you used rule-based table selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Select the Include Columns check box to include columns in the list, regardless of which table selection method you used. Click the Download icon to download the list.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. Note: You must specify the date and time in Greenwich Mean Time (GMT).
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes.
Fetch Size	Enter the number of records that the application ingestion and replication job associated with the task reads at a time from the source. The default value is 10000.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Source Operations

• •On the Selected Operations tab, individually select the check box for each source operation you want to include. Clear the check box for any ooperations you do not want to include. To select all operations, select the Operation check box at the top.
The Attribute count for an operation shows the total number of attributes in the operation.
If you select the operations you want to include, all the selected and unselected operations are displayed by default. To view the selected operations only, use the filter next to the operation selection count and change the view from All to Selected.
To find operations or attributes, you can type all or part of a name in the Find box and click Search. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns operations and attributes that include CDC anywhere in their names. To narrow the search to only operation names or field names, select Operation Name or Attributes in the drop-down list adjacent to the Find box.
• •On the Selection Rules tab, you can create inclusion and exclusion rules for operations.
To add an operation rule, click the plus (+) sign in the upper right corner. In the Type field, select Include or Exclude as the rule type. Then enter a string, with or without wildcards, as the condition.
Tips:
• - You can copy an existing operation rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.
• - You can edit an operation rule directly in its row by clicking the Type or Match Condition value.
• - To view the operations and attributes that match a single rule, click View Objects in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.
When you define a condition in a rule, use the following guidelines:
• - The task wizard is case sensitive. Enter the source operation names or masks in the case with which they were defined.
• - A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.
• - Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.
• - If an source operation name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.
Note:
If you define multiple operation rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if an operation rule specifies "Exclude CDC" followed by "Include C", all operations with names beginning with "C" are selected, including the CDC operations.

Advanced Source Properties

1. 1Complete the following optional advanced properties as needed:

Method	Description
List Operations by Rule Type	Generate and download a list of the sourceoperation that match the operation selection criteria. If you used rule-based operation selection, you can select the type of selection rules to use. Options are: - Include Rules Only - Exclude Rules Only - Include And Exclude Rules Click the Download icon to download the list.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. Note: You must specify the date and time in Coordinated Universal Time (UTC).
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes.
Fetch Size	Enter the number of records that the application ingestion and replication job associated with the task reads at a time from the source. The default value is 100. Note: The Fetch Size field appears only for the SOAP API.
Extract Non-default Fields	Select this check box to replicate the source fields that do not contain any default value. Note: The Extract Non-default Fields check box appears only for the SOAP API.

2. 2Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. Note: A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Add Operation Type	Select this check box to add a metadata column that records the source SQL operation type in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. In Audit mode, the job writes "I" for inserts, "U" for updates, "E" for upserts, or "D" for deletes to this metadata column. In Soft Deletes mode, the job writes "D" for deletes or NULL for inserts, updates, and upserts. When the operation type is NULL, the other "Add Operation..." metadata columns are also NULL. Only when the operation type is "D" will the other metadata columns contain non-null values. By default, this check box is selected. You cannot deselect it if you are using Soft Deletes.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. By default, this check box is not selected.
Add Operation Sequence	Select this check box to add a metadata column that records a generated, ascending sequence number for each change operation that the job inserts into the target tables. The sequence number reflects the change stream position of the operation. This field is available only when Apply Mode is set to Audit. By default, this check box is not selected.
Add Cycle ID	Select this check box to add a metadata column that includes the cycle ID of each CDC cycle in each target table. A cycle ID is a number that's generated by the CDC engine for each successful CDC cycle. If you integrate the job with Data Integration taskflows, the job can pass the minimum and maximum cycle IDs in output fields to the taskflow so that the taskflow can determine the range of cycles that contain new CDC data. This capability is useful if data from multiple cycles accumulates before the previous taskflow run completes. By default, this check box is not selected.
Prefix for Metadata Columns	Add a prefix to the names of the added metadata columns to easily identify them and to prevent conflicts with the names of existing columns. The default value is INFA_.
Enable Case Transformation	By default, target table names and column names are generated in the same case as the corresponding source names, unless cluster-level or session-level properties on the target override this case-sensitive behavior. If you want to control the case of letters in the target names, select this check box. Then select a Case Transformation Strategy option.
Case Transformation Strategy	If you selected Enable Case Transformation, select one of the following options to specify how to handle the case of letters in generated target table (or object) names and column (or field) names: - Same as source. Use the same case as the source table (or object) names and column (or field) names. - UPPERCASE. Use all uppercase. - lowercase. Use all lowercase. The default value is Same as source. Note: The selected strategy will override any cluster-level or session-level properties on the target for controlling case.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available:

Property	Description
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Operation Type	Select this check box to add a metadata column that records the source SQL operation type in the output that the job propagates to the target. For incremental loads, the job writes "I" for insert, "U" for update, or "D" for delete. For initial loads, the job always writes "I" for insert. By default, this check box is selected for incremental load and initial and incremental load jobs, and cleared for initial load jobs.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. For initial loads, the job always writes the current date and time. By default, this check box is not selected.
Add Orderable Sequence	Select this check box to add a metadata column that records a combined epoch value and an incremental numeric value for each change operation that the job inserts into the target tables. The sequence value is always ascending, but not guaranteed to be sequential and gaps may exist. The sequence value is used to identify the order of activity in the target records. By default, this check box is not selected.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Add Operation Type	Add a metadata column that records the source SQL operation type in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. In Audit mode, the job writes "I" for inserts, "U" for updates, "E" for upserts, or "D" for deletes to this metadata column. In Soft Deletes mode, the job writes "D" for deletes or NULL for inserts, updates, and upserts. When the operation type is NULL, the other "Add Operation..." metadata columns are also NULL. Only when the operation type is "D" will the other metadata columns contain non-null values. By default, this check box is selected and you you cannot deselect it.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. By default, this check box is not selected.
Add Operation Sequence	Select this check box to add a metadata column that records a generated, ascending sequence number for each change operation that the job inserts into the target tables. The sequence number reflects the change stream position of the operation. This field is available only when Apply Mode is set to Audit. By default, this check box is not selected.
Prefix for Metadata Columns	Add a prefix to the names of the added metadata columns to easily identify them and to prevent conflicts with the names of existing columns. The default value is INFA_.
Create Unmanaged Tables	Select this check box if you want the task to create Databricks target tables as unmanaged tables. After you deploy the task, you cannot edit this field to switch to managed tables. By default, this option is cleared and managed tables are created. If you selected Personal Staging Location in the Staging Environment field in the selected Databricks target connection, this check box is disabled. You cannot use unmanaged tables in this situation. For more information about Databricks managed and unmanaged tables, see the Databricks documentation.
Unmanaged Tables Parent Directory	If you choose to create Databricks unmanaged tables, you must specify a parent directory in Amazon S3 or Microsoft Azure Data Lake Storage to hold the Parquet files that are generated for each target table when captured DML records are processed. Note: To use Unity Catalog, you must provide an existing external directory. Note: For volume staging, provide the complete parent directory path.
Staging File Format	Select the format of the staging files in the staging environment specified in the Databricks connection. The files hold data before it's loaded into Databricks tables. Format options are: - CSV - Parquet Default is CSV.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Add Operation Type	Add a metadata column that records the source SQL operation type in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. In Audit mode, the job writes "I" for inserts, "U" for updates, "E" for upserts, or "D" for deletes to this metadata column. In Soft Deletes mode, the job writes "D" for deletes or NULL for inserts, updates, and upserts. When the operation type is NULL, the other "Add Operation..." metadata columns are also NULL. Only when the operation type is "D" will the other metadata columns contain non-null values. By default, this check box is selected and you you cannot deselect it.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. By default, this check box is not selected.
Add Operation Sequence	Select this check box to add a metadata column that records a generated, ascending sequence number for each change operation that the job inserts into the target tables. The sequence number reflects the change stream position of the operation. This field is available only when Apply Mode is set to Audit. By default, this check box is not selected.
Prefix for Metadata Columns	Add a prefix to the names of the added metadata columns to easily identify them and to prevent conflicts with the names of existing columns. Do not include special characters in the prefix. Otherwise, task deployment will fail. The default value is INFA_.
Enable Case Transformation	By default, target table names and column names are generated in the same case as the corresponding source names, unless cluster-level or session-level properties on the target override this case-sensitive behavior. If you want to control the case of letters in the target names, select this check box. Then select a Case Transformation Strategy option.
Case Transformation Strategy	If you selected Enable Case Transformation, select one of the following options to specify how to handle the case of letters in generated target table (or object) names and column (or field) names: - Same as source. Use the same case as the source table (or object) names and column (or field) names. - UPPERCASE. Use all uppercase. - lowercase. Use all lowercase. The default value is Same as source. Note: The selected strategy will override any cluster-level or session-level properties on the target for controlling case.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Operation Type	Select this check box to add a metadata column that records the source SQL operation type in the output that the job propagates to the target. For incremental loads, the job writes "I" for insert, "U" for update, or "D" for delete. For initial loads, the job always writes "I" for insert. By default, this check box is selected for incremental load and initial and incremental load jobs, and cleared for initial load jobs.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. For initial loads, the job always writes the current date and time. By default, this check box is not selected.
Add Orderable Sequence	Select this check box to add a metadata column that records a combined epoch value and an incremental numeric value for each change operation that the job inserts into the target tables. The sequence value is always ascending, but not guaranteed to be sequential and gaps may exist. The sequence value is used to identify the order of activity in the target records. By default, this check box is not selected.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Operation Type	Select this check box to add a metadata column that includes the source SQL operation type in the output that the job propagates to the target. The job writes "I" for insert, "U" for update, or "D" for delete. By default, this check box is selected.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. By default, this check box is not selected.
Add Orderable Sequence	Select this check box to add a metadata column that records a combined epoch value and an incremental numeric value for each change operation that the job inserts into the target tables. The sequence value is always ascending, but not guaranteed to be sequential and gaps may exist. The sequence value is used to identify the order of activity in the target records. By default, this check box is not selected.
Async Write	Controls whether to use synchronous delivery of messages to Kafka. - Clear this check box to use synchronous delivery. Kafka must acknowledge each message as received before Application Ingestion and Replication sends the next message. In this mode, Kafka is unlikely to receive duplicate messages. However, performance might be slower. - Select this check box to use asynchronous delivery. Application Ingestion and Replication sends messages as soon as possible, without regard for the order in which the changes were retrieved from the source. By default, this check box is selected.
Producer Configuration Properties	Specify a comma-separated list of key=value pairs to enter Kafka producer properties for Apache Kafkatargets. You can specify Kafka producer properties in either this field or in the Additional Connection Properties field in the Kafka connection. If you enter the producer properties in this field, the properties pertain to the application ingestion and replication jobs associated with this task only. If you enter the producer properties for the connection, the properties pertain to jobs for all tasks that use the connection definition, unless you override the connection-level properties for specific tasks by also specifying properties in the Producer Configuration Properties field. For information about Kafka producer properties, see the Apache Kafka documentation.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available:

Property	Description
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Operation Type	Select this check box to add a metadata column that records the source SQL operation type in the output that the job propagates to the target. For incremental loads, the job writes "I" for insert, "U" for update, or "D" for delete. For initial loads, the job always writes "I" for insert. By default, this check box is selected for incremental load and initial and incremental load jobs, and cleared for initial load jobs.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. For initial loads, the job always writes the current date and time. By default, this check box is not selected.
Add Orderable Sequence	Select this check box to add a metadata column that records a combined epoch value and an incremental numeric value for each change operation that the job inserts into the target tables. The sequence value is always ascending, but not guaranteed to be sequential and gaps may exist. The sequence value is used to identify the order of activity in the target records. By default, this check box is not selected.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Prefix for Metadata Columns	Add a prefix to the names of the added metadata columns to easily identify them and to prevent conflicts with the names of existing columns. Do not include special characters in the prefix. Otherwise, task deployment will fail. The default value is INFA_.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available:

Property	Description
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Field	Description
Add Operation Type	Add a metadata column that records the source SQL operation type in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. In Audit mode, the job writes "I" for inserts, "U" for updates, "E" for upserts, or "D" for deletes to this metadata column. In Soft Deletes mode, the job writes "D" for deletes or NULL for inserts, updates, and upserts. When the operation type is NULL, the other "Add Operation..." metadata columns are also NULL. Only when the operation type is "D" will the other metadata columns contain non-null values. By default, this check box is selected and you you cannot deselect it.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. By default, this check box is not selected.
Prefix for Metadata Columns	Add a prefix to the names of the added metadata columns to easily identify them and to prevent conflicts with the names of existing columns. The default value is INFA_.
Enable Case Transformation	Not applicable.
Case Transformation Strategy	Not applicable.
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Add Cycle ID	Select this check box to add a metadata column that includes the cycle ID of each CDC cycle in each target table. A cycle ID is a number that's generated by the CDC engine for each successful CDC cycle. If you integrate the job with Data Integration taskflows, the job can pass the minimum and maximum cycle IDs in output fields to the taskflow so that the taskflow can determine the range of cycles that contain new CDC data. This capability is useful if data from multiple cycles accumulates before the previous taskflow run completes. By default, this check box is not selected.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available:

Property	Description
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Add Operation Type	Select this check box to add a metadata column that records the source SQL operation type in the output that the job propagates to the target. For incremental loads, the job writes "I" for insert, "U" for update, or "D" for delete. For initial loads, the job always writes "I" for insert. By default, this check box is selected for incremental load and initial and incremental load jobs, and cleared for initial load jobs.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. For initial loads, the job always writes the current date and time. By default, this check box is not selected.
Add Orderable Sequence	Select this check box to add a metadata column that records a combined epoch value and an incremental numeric value for each change operation that the job inserts into the target tables. The sequence value is always ascending, but not guaranteed to be sequential and gaps may exist. The sequence value is used to identify the order of activity in the target records. By default, this check box is not selected.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Add Source Table Name	Adds a metadata column to each target table to store the name of the respective source table.
Add Source Schema Name	Adds a metadata column to each target table to store the name of the respective source schema.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Property	Description
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Add Cycle ID	Select this check box to add a metadata column that includes the cycle ID of each CDC cycle in each target table. A cycle ID is a number that's generated by the CDC engine for each successful CDC cycle. If you integrate the job with Data Integration taskflows, the job can pass the minimum and maximum cycle IDs in output fields to the taskflow so that the taskflow can determine the range of cycles that contain new CDC data. This capability is useful if data from multiple cycles accumulates before the previous taskflow run completes. By default, this check box is not selected.
Prefix for Metadata Columns	Add a prefix to the names of the added metadata columns to easily identify them and to prevent conflicts with the names of existing columns. Do not include special characters in the prefix. Otherwise, task deployment will fail. The default value is INFA_.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Field	Description
Add Operation Type	Select this check box to add a metadata column that records the source SQL operation type in the output that the job propagates to the target. For incremental loads, the job writes "I" for insert, "U" for update, or "D" for delete. For initial loads, the job always writes "I" for insert. By default, this check box is selected for incremental load and initial and incremental load jobs, and cleared for initial load jobs.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. For initial loads, the job always writes the current date and time. By default, this check box is not selected.
Add Orderable Sequence	Select this check box to add a metadata column that records a combined epoch value and an incremental numeric value for each change operation that the job inserts into the target tables. The sequence value is always ascending, but not guaranteed to be sequential and gaps may exist. The sequence value is used to identify the order of activity in the target records. By default, this check box is not selected.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Field	Description
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp in UTC format at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Add Operation Type	Select this check box to add a metadata column that records the source SQL operation type in the output that the job propagates to the target database or inserts into the target table. This field is available only when the Apply Mode option is set to Audit. In Audit mode, the job writes "I" for insert, "U" for update, or "D" for delete. By default, this check box is selected.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit. By default, this check box is not selected.
Add Operation Sequence	Select this check box to add a metadata column that records a generated, ascending sequence number for each change operation that the job inserts into the target tables. The sequence number reflects the change stream position of the operation. This field is available only when Apply Mode is set to Audit. By default, this check box is not selected.
Add Cycle ID	Select this check box to add a metadata column that includes the cycle ID of each CDC cycle in each target table. A cycle ID is a number that's generated by the CDC engine for each successful CDC cycle. If you integrate the job with Data Integration taskflows, the job can pass the minimum and maximum cycle IDs in output fields to the taskflow so that the taskflow can determine the range of cycles that contain new CDC data. This capability is useful if data from multiple cycles accumulates before the previous taskflow run completes. By default, this check box is not selected.
Prefix for Metadata Columns	Add a prefix to the names of the added metadata columns to easily identify them and to prevent conflicts with the names of existing columns. The default value is INFA_.
Enable Case Transformation	By default, target table names and column names are generated in the same case as the corresponding source names. If you want to control the case of letters in the target names, select this check box. Then select a Case Transformation Strategy option.
Case Transformation Strategy	If you selected Enable Case Transformation, select one of the following options to specify how to handle the case of letters in generated target table (or object) names and column (or field) names: - Same as source. Use the same case as the source table (or object) names and column (or field) names. - UPPERCASE. Use all uppercase. - lowercase. Use all lowercase. The default value is Same as source.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
2. 2Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
3. 3Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define the following optional advanced target property that you want to use:

Property	Description
Ingestion Mode	The ingestion mode to load data into Salesforce 360. You can select from the following options based on the data volume, processing speed, and near real-time requirements: - Bulk API. Loads large datasets. - Streaming API. Processes near-real-time micro-batch datasets.
Enable Case Transformation	Not applicable.
Case Transformation Strategy	Not applicable.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available:

Property	Description
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.

Advanced Target Properties

1. 1Under Advanced Options, define any of the following optional advanced target properties that you want to use:

Field	Description
Add Last Replicated Time	Select this check box to add a metadata column that records the timestamp at which a record was inserted or last updated in the target table. For initial loads, all loaded records have the same timestamp, except for Snowflake targets that use the Superpipe option where minutes and seconds might vary slightly. For incremental and combined initial and incremental loads, the column records the timestamp of the last DML operation that was applied to the target. By default, this check box is not selected.
Add Operation Type	Add a metadata column that records the source SQL operation type in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. In Audit mode, the job writes "I" for inserts, "U" for updates, "E" for upserts, or "D" for deletes to this metadata column. In Soft Deletes mode, the job writes "D" for deletes or NULL for inserts, updates, and upserts. When the operation type is NULL, the other "Add Operation..." metadata columns are also NULL. Only when the operation type is "D" will the other metadata columns contain non-null values. By default, this check box is selected and you you cannot deselect it.
Add Operation Time	Select this check box to add a metadata column that records the source SQL operation timestamp in the output that the job propagates to the target database or inserts into the audit table on the target system. This field is available only when the Apply Mode option is set to Audit or Soft Deletes. By default, this check box is not selected.
Add Operation Sequence	Select this check box to add a metadata column that records a generated, ascending sequence number for each change operation that the job inserts into the target tables. The sequence number reflects the change stream position of the operation. This field is available only when Apply Mode is set to Audit. By default, this check box is not selected.
Add Cycle ID	Select this check box to add a metadata column that includes the cycle ID of each CDC cycle in each target table. A cycle ID is a number that's generated by the CDC engine for each successful CDC cycle. If you integrate the job with Data Integration taskflows, the job can pass the minimum and maximum cycle IDs in output fields to the taskflow so that the taskflow can determine the range of cycles that contain new CDC data. This capability is useful if data from multiple cycles accumulates before the previous taskflow run completes. By default, this check box is not selected.
Prefix for Metadata Columns	Add a prefix to the names of the added metadata columns to easily identify them and to prevent conflicts with the names of existing columns. The default value is INFA_.
Superpipe	Select this check box to use the Snowpipe Streaming API to quickly stream rows of data directly to Snowflake Data Cloud target tables with low latency instead of first writing the data to stage files. This option is available for all load types. When you configure the target connection, select KeyPair authentication. By default, this check box is selected. Deselect it if you want to write data to intermediate stage files. Note: If you enable the Superpipe option for a task that uses the Soft Deletes apply mode, make sure the source tables contain a primary key.
Merge Frequency	When Superpipe is selected, you can optionally set the frequency, in seconds, at which change data rows are merged and applied to the Snowflake target tables. The merge frequency affects how often the stream change data is merged to the Snowflake base table. A Snowflake view joins the stream change data with the base table. Set this value to balance the costs of merging data to the base table with the performance of view join processing. This field applies to incremental load and combined initial and incremental load tasks. Valid values are 60 through 604800 seconds. Default is 3600 seconds.
Enable Case Transformation	By default, target table names and column names are generated in the same case as the corresponding source names, unless cluster-level or session-level properties on the target override this case-sensitive behavior. If you want to control the case of letters in the target names, select this check box. Then select a Case Transformation Strategy option.
Case Transformation Strategy	If you selected Enable Case Transformation, select one of the following options to specify how to handle the case of letters in generated target table (or object) names and column (or field) names: - Same as source. Use the same case as the source table (or object) names and column (or field) names. - UPPERCASE. Use all uppercase. - lowercase. Use all lowercase. The default value is Same as source. Note: The selected strategy will override any cluster-level or session-level properties on the target for controlling case.

2. 2Under Table Renaming Rules, if you want to rename the target objects that are associated with the selected source tables, define renaming rules.
1. aClick the + (Add new row) icon and enter a source table name or name mask and enter a corresponding target table name or name mask.
2. bTo define a mask, include one or more the asterisk (*) wildcards. Then, press Enter.
For example, to add the prefix "PROD_" to the names of target tables that correspond to all selected source tables, enter the * wildcard for the source table and enter PROD_* for the target table.
You can enter multiple rules.
Notes:
• - If you enter the wildcard for a source table mask, you must also enter the wildcard for a target table mask.
• - If a table name includes special characters, such as a backslash (\), asterisk(*), dot (.), or question mark (?), escape each special character in the name with a backslash (\).
• - On Windows, if you enter target table renaming criteria that causes a target table name to exceed 232 characters in length, the name is truncated to 222 characters. Data Ingestion and Replication appends 14 characters to the name to add a date-time yyyyMMddHHmmss value, which causes the name to exceed the Windows maximum limit of 255. Ensure that the names of any renamed target tables do not exceed 232 characters.
3. 3Under Data Type Rules, if you want to override the default mappings of source data types to target data types, define data type rules. Click the + (Add new row) icon and enter a source data type and corresponding target data type. Then press Enter.
Also, in the Source Data Type value, you can include the percent (%) wildcard to represent the data type precision, scale, or size, for example, NUMBER(%,4), NUMBER(8,%), or NUMBER(%). Use the wildcard to cover all source columns that have the same data type but use different precision, scale, or size values, instead of specifying each one individually. For example, enter FLOAT(%) to cover FLOAT(16), FLOAT(32), and FLOAT(84). You cannot enter the % wildcard in the target data type. A source data type that uses the % wildcard must map to a target data type that uses specific precision, scale, or size value. For example, you could map the source data type FLOAT(%) to a target data type specification such as NUMBER(38,10)
4. 4Under Custom Properties, you can enter one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the Property Name field, select a property and then enter a property value, or select the Custom option and manually enter both the property name and value.
The following table describes the properties that are available, depending on the load type:

Property	Description
Writer Distributor Count	The number of distributors that can run on separate threads in parallel to process data during an initial load job or the unload phase of a combined load job when the Writer Unload Multiple Distributors custom property is set to true. Using parallel distributor threads can improve job performance, particularly for high-volume data transfers. Default value is 3. If your system has ample resources, Informatica recommends that you set this parameter to 8. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal distributor count. You can override the value from auto-tuning by setting this custom property.
Writer Helper Thread Count	The number of writer helper threads that are used to convert incoming change data rows or initial unload rows to the output format configured for the target, such as Avro, CSV, or Parquet. Default value is 2. If two threads can’t keep up with the incoming volume of data, you can increase the number of threads. Consider increasing the number of threads in the following situations: 1) the incoming volume is high, 2) multiple writer distributors are in use, or 3) some rows are very large or wide, which increases conversion time. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine the optimal thread count. You can override the value from auto-tuning by setting this custom property.
Writer Unload Multiple Distributors	Indicates whether multiple distributor threads can be used to process data in parallel during initial load jobs and the unload phase of combined load jobs. The distributors perform work such as uploading data files to staging areas and flushing data to the target. Set this property to true to use multiple distributor threads. Default value is false. Note: If you select the Auto-Tune option on the Let's Go! page of the task wizard, auto-tuning can determine whether to use multiple distributors. You can override the value from auto-tuning by setting this custom property.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).
Tip:
To delete a custom property after you've entered it, click the Delete icon at the right end of the property row.