Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration
  • All Products

Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Chunking transformation
  9. Cleanse transformation
  10. Data Masking transformation
  11. Data Services transformation
  12. Deduplicate transformation
  13. Expression transformation
  14. Filter transformation
  15. Hierarchy Builder transformation
  16. Hierarchy Parser transformation
  17. Hierarchy Processor transformation
  18. Input transformation
  19. Java transformation
  20. Java transformation API reference
  21. Joiner transformation
  22. Labeler transformation
  23. Lookup transformation
  24. Machine Learning transformation
  25. Mapplet transformation
  26. Normalizer transformation
  27. Output transformation
  28. Parse transformation
  29. Python transformation
  30. Rank transformation
  31. Router transformation
  32. Rule Specification transformation
  33. Sequence transformation
  34. Sorter transformation
  35. SQL transformation
  36. Structure Parser transformation
  37. Transaction Control transformation
  38. Union transformation
  39. Vector Embedding transformation
  40. Velocity transformation
  41. Verifier transformation
  42. Web Services transformation

Transformations

Transformations

Back Next

File target properties

File target properties

You configure file target properties on the
Target
 tab of the Properties panel.
The following table describes the file target details:
Property
Description
Connection
Name of the target connection.
Target Type
Target type, either single object or parameter.
Object
Name of the target object.
In advanced mode, the object name cannot contain the dollar sign character,
$
. The dollar sign is a reserved character for parameters.
Formatting Options
Flat file format options. Opens the
Formatting Options
 dialog box to define the format of the file.
You can choose either a delimited or fixed-width file type. Default is delimited.
To write to a delimited flat file type, configure the following file format options:
  • Delimiter. Delimiter character. Can be a comma, tab character, colon, semicolon, nonprintable control character, or a single-byte or multibyte character that you specify.
  • Treat multiple characters as a single delimiter
    .
    Treats the specified set of delimiters as one delimiter. For example, a source file contains the following record: abc~def|ghi~|~|jkl|~mno. If you specify the delimiter as ( ~ | ), Data Integration reads the record as three columns separated by two delimiters: abc~def|ghi, NULL, jkl|~mno. If you disable this option, Data Integration reads the record as nine columns separated by eight delimiters: abc, def, ghi, NULL, NULL, NULL, jkl, NULL, mno.
  • Treat consecutive delimiters as one. Treats one or more consecutive column delimiters as one. The default is to treat consecutive delimiters as a null value.
  • Row Delimiter. Line break character. Select a line break character from the list. The default is line-feed, \012 LF.
    Linux machines write "\n" as the line-feed character. Windows machines write "\r\n" as the line-feed character.
  • Text Qualifier. Character to qualify text.
  • Escape character. Escape character.
  • Field labels. Determines if the
    mapping
     task generates field labels or imports labels from the source file.
  • First data row. The first row of data. The task starts the read at the row number that you enter.
You can use a tab, space, or any printable special character as a delimiter. The delimiter can have a maximum of 10 characters. The delimiter must be different from the escape character and text qualifier.
Use caustion when updating the file formating options after you have updated the target field metadata. Changes to the formating options can synchronize fields with fields in the target object. For more information see Target fields.
To write to a fixed-width flat file type, select the fixed-width file format to use. If the list includes multiple fixed-width file formats with the same name, use the project and folder location that's appended to the name to determine the appropriate file format to use. If you do not have a fixed-width file format, click
New
Components
Fixed Width File Format
 to create one.
Operation
For file targets, the operation is always Insert.
The following table describes the advanced properties for flat file targets:
Property
Description
Forward Rejected Rows
Indicates whether the
mapping
 task forwards rejected rows to the reject file.
If you enable row error handling, the
mapping
 task writes the rejected rows and the dropped rows to the row error logs instead of generating a reject file. If you want to write the dropped rows to the session log in addition to the row error logs, you can enable verbose data tracing.
If you don't forward rejected rows, the
mapping
 task drops rejected rows and writes them to the session log.
Thousand Separator
Thousand separator character. Can be none, comma, or period. Cannot be the same as the decimal separator or the delimiter character.
Field type must be Number. You might also need to update the field precision and scale.
Default is None.
Decimal Separator
Decimal character. Can be a comma or period. Cannot be the same as the thousand separator or delimiter character.
Field type must be Number. You might also need to update the field precision and scale.
Default is Period.
Datetime Format
Optional. Overrides the datetime format specified in the flat file connection.
Enter the datetimeformat to override.
For example, YYYYMMDD.
Append if Exists
Appends the output data to the target files and reject files for each partition. You cannot use this option for FTP/SFTP target files.
If you do not select this option, the
mapping
 task truncates each target file before writing the output data to the target file. If the file does not exist, the
mapping
 task creates it.
Create Target Directory
Creates the target directory if it doesn't exist as specified in the Output file directory field.
Header Options
Creates a header row in the file target. You can choose the following options:
  • No Header. Do not create a header row in the flat file target.
  • Output Field Names. Create a header row in the file target with the output field names.
  • Use header command output. Use the command in the Header Command field to generate a header row. For example, you can use a command to add the date to a header row for the file target.
Default is No Header.
Header Command
Command used to generate the header row in the file target. For example, you can use a command to add the date to a header row for the file target.
Footer Command
Command used to generate the footer row in the file target.
Output Type
Type of target for the task. Select
File
 to write the target data to a file target. Select
Command
 to output data to a command.
You cannot select
Command
 for FTP/SFTP target connections.
Output File Name
File name or file name and path of the output file. By default, the
mapping
 task names output files after the target object.
Target objects must use one of the following file extensions:
csv, dat, txt
Output File Directory
Name of the output directory for a flat file target. By default, the
mapping
 task writes output files to the target connection directory.
You can also use an input parameter to specify the target file directory.
If you use the service process variable directory $PMTargetFileDir, the task writes target files to the configured path for the system variable. To find the configured path of a system variable, see the pmrdtm.cfg file located at the following directory: 
<Secure Agent installation directory>\apps\Data_Integration_Server\<Data Integration Server version>\ICS\main\bin\rdtm
You can also find the configured path for the $PMTargetFileDir variable in the Data Integration Server system configuration details in Administrator.
Reject File Directory
Directory path to write the reject file. By default, the
mapping
 task writes all reject files to the following service process variable directory: 
$PMBadFileDir/<federated task ID>
If you specify both the directory and file name in the
Reject File Name
 field, clear this field. The
mapping
 task concatenates this field with the
Reject File Name
 field when it runs the task.
Reject File Name
File name, or file name and path of the reject file. By default, the
mapping
 task names the reject file after the target object name: <target name>.bad.
The
mapping
 task concatenates this field with the
Reject File Directory
 field when it runs the task. For example, if you have
C:\reject_file\
 in the
Reject File Directory
 field, and enter
filename.bad
 in the
Reject File Name
 field, the
mapping
 task writes rejected rows to
C:\reject_file\filename.bad
.
The following table describes the advanced properties when you write a message to a file target:
Property
Description
Input Type
Type of input to write to the target. Select one of the following options:
  • Buffer
  • File
The available options depend on the incoming data from upstream transformations. Default is buffer.
Acknowledgement Options
Options to save the acknowledgement. Select one of the following options:
  • Save to session log
     to write the acknowledgement to the session log.
  • Save to file
     to save the acknowledgement to a file.
  • Discard
     to discard the acknowledgement.
Acknowledgement File Path
File path to write the acknowledgement if you save the acknowledgement to a file.
Operation if File Exists
Operation to perform if the acknowledgement file already exists. Select one of the following operations:
  • Rename
     to rename the acknowledgement file.
  • Append
     to append the acknowledgement to the file.
  • Overwrite
     to overwrite the acknowledgement file.
Fail the job if acknowledgement is not AA/CA
Fails the job if the acknowledgement code is not AA or CA.
Retry the job if acknowledgement is AR/CR
Tries to run the job again if the acknowledgement code is AR or CR.
Message Retry Attempts
Number of attempts to try writing the message.
Message Retry Interval
Time interval in seconds to try writing the message again.
Validate Message
Indicates whether
Data Integration
 validates the message.
Forward Rejected Rows
Indicates whether the
mapping
 task forwards rejected rows to the reject file.
If you enable row error handling, the
mapping
 task writes the rejected rows and the dropped rows to the row error logs instead of generating a reject file. If you want to write the dropped rows to the session log in addition to the row error logs, you can enable verbose data tracing.
If you don't forward rejected rows, the
mapping
 task drops rejected rows and writes them to the session log.
0 COMMENTS
We’d like to hear from you!