Data Integration Solutions: Flat File

Processing Multibyte Characters Like UNICODE Characters in Fixed Width Files

Working with Multibyte Data in Fixed-Width Filess

Processing fixed width file in Informatica PowerCenter is not a big deal. But this can be bit tricky if the fixed file contins both multi byte and single byte characters such as unicode characters. This is because of the fact that fixed width flat files are byte oriented, which means the field width is measured in bytes. So if a single character takes two bytes for its representation, it will be treated as width two. In this article, lets see how such files are handled in Informatica PowerCenter.

Informatica Source, Target Command Makes File Processing Easier than Before

Source, Target Command Makes File Processing Easier than Beforen

Most of the time when we process flat files in Informatica PowerCenter, we do some kind of file pre or post processing, such as unzip the source file, create a custom header or footer for the target file etc. Such processing is normally done using Unix or Windows scripts, which is called using pre or post session script. Now Informatica PowerCenter has provided Source, Target Commands to make such processing easy than before.

Extracting Information from the Source File Name can Never be Easier

Extracting Information from the Source File Name in Informatica powercenter workflow

Many times we get data files from different sources and the source file name itself might contain some valid information like 'file creation date', 'file generated department name', 'region name' etc... We used to use Unix script to extract such information from the file name, but we don't have to write such scripts anymore. In this article let's look at the option provided by Informatica PowerCenter to extract information from the source file name.

Informatica Mapping to Populate Header Values to Detail Records from a Flat File

character encoding in Informatica powercenter workflow

Many times it is possible that you get flat files with a header record, which has a different structure from the other detail record. The header record gives some audit information like Number of total records in the file, File creation date, Unique file identifier etc... which aslo makes some business value. You can be asked to populate these header record column to the target along with each detail records from a Flat File Source.

Split Your Informatica PowerCenter Target File Dynamically Based on the Content

Split your target file dynamically based on the content

There can be scenarios, where you need to generate multiple flat file using an informatica mapping based on the source data content or some other business rule; from a single data source. For example, you may need to generate last months top revenue generating customer list, which is split into multiple files based on the customer residence state. In this article we will see how to split your target file dynamically based on the business rule.

Dynamically Change Your Target Flat File Name Using Informatica Mapping

When ever you create a flat file using a PowerCenter Workflow, the name of the file will be static, which is specified in the Session 'Output Filename' property. There can be business cases where you need to generate flat files with dynamic file name, like add Timestamp with the file name . Here in this article we will discuss how we can generate flat files with dynamically changing name.

Customize Your Target Flat File Column Headings Using Informatica Mapping

When you create flat file using a Power Center workflow, it creates the file with target table port name as the column headings, But you might need to change the column heading, which make more meaning to the column data before it can be given to the business users. Here in this article we will see how we can customize the target file column header.
Continue Reading

Popular Posts

Random Posts

Posts Being Viewed