Jeff's Cluttered Mind

In the Target Table session properties there is an option to Truncate existing data before loading. It is important to realize Informatica does not always use the TRUNCATE function to clear the table, sometimes a DELETE statement is issued, this decision is made at runtime depending on different factors, noted in the table below.

Calling JDE Business Services (BSSV), aka Web Services, can be tricky and there is little information on Oracle's or Informatica's website showing how. In fact, importing the JDE CustomerManager.wsdl into an Informatica web service consumer creates a large confusing, near impossible to understand transformation.

Here's a high level overview to create a usable JDE 9.0 Customer Manager BSSV, be aware your requirements may be different and you may have to deviate from these steps to fit your need.

Here's a solution to an obscure issue. A workflow/session completes successfully when ran manually but gives error LM_44127 Failed to prepare the task when ran from the scheduler.

If you are using Versioning, ALL objects must be checked in. Use the option Versioning > Find Checkouts to see any checked out objects. Check in all objects.

Also, IMPORTANT, if using shortcuts for sources, targets or transformations, the objects the shortcuts are copied from must also be checked in, look in the folder(s) where the shortcuts where copied from, make sure those are also checked in.

This page will be a running list of tips and workarounds for Data Integration Hub 10.

This issue was found in Informatica Data Integration Hub 10 on Windows Server 2012 using SQL Server 2012 as the Repository.

The PowerCenter Workflow DX_ETL can abort in mapping m_SET_CURRENT_CUTOFF giving the errors:

• Timestamp parameters with a scale, must have a scale less than ten and a precision equal to 20 plus the scale. You specified a precision of 999 and scale of 9.
• Fractional second precision exceeds the scale specified in the parameter binding.

I created this simple PowerCenter mapplet to format phone numbers. Informatica Developer (IDQ) may have a different or easier way to do it but I wanted something I could use in PowerCenter without the hassle of maintaining a separate object in IDQ and having to import it into PowerCenter. You can alter the mapplet to format other data like postal codes, SSNs, etc.

Download the mapplet and give it a try.

Mapplet Overview

My approach is a simple one, take the phone number, remove all special characters, then reformat the number with dashes as 999-999-9999. This approach allows me to ignore how the phone number comes into the mapplet, for example partially formatted , not formatted or formatted correctly but not how I need it.

The mapplet's input is the telephone number without a country identifier. In addition to the reformatted phone number, the mapplet also outputs:

• a Pattern (example xxx-xxx-xxx) based on the input number (this could be used for a quick/dirty data profiling)
• the phone number parsed into its parts, area code, central office
• the length of the input phone number

Read further to see detail on the mapplet works.

When extracting large tables from SAP, you can limit the amount of data selected by using Informatica parameters.  Here are two examples.

1. Use a parameter to limit the extract to retrieve only a specified set of data. Your target uses a truncate and load scenario.
2. Use parameters as in the example above but also use a persistent cache lookup on the target table. Append new rows to the table.

Here are some notes on an Informatica PowerCenter 9.6.1 64 bit server install.  This also includes the setup of the Informatica Cloud Secure Agent (64)

Most of the install went smooth.  However I want to list some of the problems I encountered.