Supported Transformations and Mapping Objects
The mapping objects in a workflow must be supported by Informatica Cloud.
A mapping can include the following source and target types:
- •Flat file
- •FTP/SFTP
- •Database
- •Salesforce
- •SAP
- •Web service
- •Most add-on connectors
To find out if the add-on connector you use supports PowerCenter tasks, see the appropriate Informatica Cloud connector guide.
A mapping can include the following transformations:
- •Aggregator transformation
- •Data Masking transformation
- •Expression transformation
- •Filter transformation
- •HTTP transformation
- •Java transformation
- •Joiner transformation
- •Lookup transformation
- •Normalizer transformation
- •Router transformation
- •Salesforce Lookup transformation
- •Salesforce Picklist transformation
- •Salesforce Merge transformation
- •SAP IDOC Interpreter transformation
- •SAP IDOC Prepare transformation
- •Sequence Generator transformation
- •Sorter transformation
- •Stored Procedure transformation
- •Transaction Control transformation
- •Union transformation
- •Update Strategy transformation
- •Web Services Consumer transformation
- •XML Parser transformation with file or database sources
- •XML Generator transformation with file or database sources
If the workflow contains transformations or mapping objects other than the objects listed above, the workflow upload to Informatica Cloud might fail.
Exception Handling in Stored Procedures
When a mapping that you want to use in a PowerCenter task contains a Stored Procedure transformation, the stored procedure must include exception handling. Exception handling can be as complex as necessary. Or, you can use the following simple example:
Exception
when NO_DATA_FOUND
then NULL;
END;
For example, you have the following stored procedure in a PowerCenter workflow:
CREATE OR REPLACE PROCEDURE SP_GETSAL_WITH_EXCEPTION (EMP_ID NUMBER, EMP_NAME OUT VARCHAR, SAL OUT NUMBER)
AS
BEGIN
SELECT EMPNAME INTO EMP_NAME FROM EMPLOYEE WHERE EMPID=EMP_ID;
SELECT SALARY INTO SAL FROM EMPLOYEE WHERE EMPID=EMP_ID;
Before you export the workflow, add exception handling as follows:
CREATE OR REPLACE PROCEDURE SP_GETSAL_WITH_EXCEPTION (EMP_ID NUMBER, EMP_NAME OUT VARCHAR, SAL OUT NUMBER)
AS
BEGIN
SELECT EMPNAME INTO EMP_NAME FROM EMPLOYEE WHERE EMPID=EMP_ID;
SELECT SALARY INTO SAL FROM EMPLOYEE WHERE EMPID=EMP_ID;
Exception
when NO_DATA_FOUND
then NULL;
END;