Home Cezary Opacki

Cezary Opacki

Email: This e-mail address is being protected from spambots. You need JavaScript enabled to view it

This article is written based on Power Center 9.0.0. But it seems to apply to other versions as well. Let's assume that one needs to write a BASE64 encoded string to a flat file.

This is article available through URL:

http://oracleappstechnology.blogspot.com/2007/10/difference-between-utf8-and-al32utf8.html

Written by Vikram Das.

 UTF8 and AL32UTF8 are encodings of the Unicode character set and include all the characters in all modern languages. UTF8 and AL32UTF8 allow Oracle Applications to be run from one database instance using any combination of supported languages. The advantage of AL32UTF8 over UTF8 is in the handling of supplementary characters, which are increasingly used in certain languages. AL16UTF16 is the current default database character set for Oracle databases 10g and 11g and Oracle E-Business Suite R12.

Code Page configuration in Informatica™ PowerCenter is quite complex. Below note can be useful but not sufficient to setup PowerCenter Code Page.

Data locations and where the code page is set:

The attached PDF describes how to avoid certain errors while reading from an excel file, in particular: To few parameters. Expected XXX.

To download the PDF click the following button:

PowerCenter flat file target can be configured to redirect output to shell command standard input instead of a flat file.

This technique can be used to:

In the article is mentioned issue of end of line character in source fixed length files. 

Every row in a fixed-length file must have the same length. At the and of row can be:

  1. no end of line characters;
  2. lf - line feed character;
  3. cr + lf - carriage return and line feed characters;

If you use any text editor to create the file, it is going to add end of line characters.

The "Power Center Designer Guide" features

Chapter 5: Mappings

The "Creating Target Files by Transaction" section conveniently describes how to dynamically create flat files with names evaluated in the mapping.

The following is an excerpt from the Informatica "Designer Guide", "Working with Flat Files" manual:

"(...) Fixed-width flat files are byte-oriented, which means that the field lengths are measured in bytes. They can also be line sequential, which means each row ends with a newline character. You can import a fixed-width file that does not contain binary data or multibyte character data greater than two bytes per character. (...)"

 

 The samples below show how to use expression variables to count rows and how to check if string follows required pattern.

 Variable usage example (expression local variables):

The solution shows how to:

·       use shell command to generate input flat file list.

·       each flat file with name <name>.<extension> from the list above is processed and written to output file under the name <name>_O.<extension>.

·       to achieve that transaction control transformation is required. For every transaction it is generated flat file with new name.   

·       expression transformation shows how to check whether new input file is processed. If new file is processed port NewFile is set to 1 (0 in other case). This is used in transaction control transformation to generate new transaction. One of more interesting issues is using local variables in the expression transformation.

«StartPrev1234NextEnd»
Page 3 of 4