Known limitations

• •PC to Cloud Conversion cannot scan PowerCenter export XML files that are larger than 70 MB.
Workaround: Export PowerCenter workflows or folders to multiple, smaller files. Select all of the files when you create the conversion project.
• •When multiple workflows within a folder contains sessions with the same name, only one session is converted.
• •If you create a project with multiple PowerCenter XML files, one file contains a workflow with a mapping, and the other file contains a mapping with the same name that is not within a workflow, only one mapping is converted.
• •If you do not convert PowerCenter mapplets to Data Integration native mapplets, then PowerCenter mappings that contain mapplets with source or target connections are converted, but they cannot be published.
• •When you convert and publish a PowerCenter mapping that uses a connected flat file lookup, the Lookup transformation in the converted mapping contains no lookup object and the connection object is not created.
• •If you convert a workflow that contains multiple sessions, and the sessions use the same mapping with different connections, each of the converted mapping tasks uses the same connection objects.
• •If you convert a PowerCenter mapping that contains a target with port names that do not match the port names in the upstream transformation, the incoming field names shown in the target transformation are incorrectly listed as the target transformation field names instead of the incoming field names.
• •When you run a converted mapping task that contains an Expression transformation, and the expression performs a calculation using numeric fields, the mapping task might fail with an "operand cannot be converted to a number error."
Workaround: In the mapping task Advanced Session Properties, set Enable High Precision to yes.
• •You cannot convert PowerCenter mappings and sessions that contain Microsoft SQL Server sources, targets, or lookup objects that use the following datatypes: real, text, bit, and datetime2.
• •Conversion fails for PowerCenter XML files that contain the unit separator character (ASCII 31).
Workaround: Edit the XML file, and delete or replace the unit separator characters.
• •When you click an area in the Top Issues panel on the project details page, the Assets list is not filtered.
• •Ordering of the target load order groups are not converted.
• •PC to Cloud Conversion converts PowerCenter Source Qualifier transformations to a placeholder Expression transformations based on the number and types of sources that are associated with the Source Qualifier transformation.
• •Source query overrides are converted to source custom queries.
• •PC to Cloud Conversion becomes invalid for a taskflow with a parameterized PowerCenter task. This issue occurs because the PowerCenter task does not expose the parameter file directory and name fields to the taskflow.
• •PC to Cloud Conversion does not support the conversion of nested functions in assignment task.
• •PC to Cloud Conversion does not include the values of the service variables $PMSuccessEmailuser and $PMFailureEmailuser from PowerCenter to Cloud Data Integration during the workflow conversion.
• •Currently Processed Flat File name property is supported only when the source object is not parameterized in Cloud Data Integration. If source object is parameterized in the mapping and you set the Currently Processed Flat File name property, the Currently Processed Flat File name property is not supported in Cloud Data Integration.
• •File Listener Object is assigned to a different runtime environment instead of the one selected during publish.
• •PC to Cloud Conversion fails to convert parallel links. Decision on Start task becomes invalid in converted taskflow. (PC2C-2076)
• •PC to Cloud Conversion does not support conversion of workflows with $Start.EndTime" and "$Start.StartTime" predefined variables. (PC2C-675)
• •PC to Cloud Conversion cannot convert a Source when the last partition point does not contain a file path. (PC2C-2746)
• •If you have a pipeline lookup in Oracle ADW, the PC to Cloud Conversion converts the pipeline lookup as a regular lookup in Oracle.
• •PC to Cloud Conversion cannot convert the lookup table name definition overwritten at the session level for Oracle ADW.
• • Sybase IQ target conversion does not support the following functionality:
• - External loader connection parameterization
• - Creation of target table at runtime
• - Parameter object type
• - UPDATE, DELETE, and UPSERT operations
• - View and schema
• •PC to Cloud Conversion converts a connected or unconnected lookup when you specify Transformationtype=Lookup in the connection map in the Config zip file. PC to Cloud Conversion converts pipeline lookup object when you specify Transformationtype=Lookup, Source in the connection map in the Config zip file.
• •PC to Cloud Conversion does not convert the following source properties while converting static SAP ABAP mappings from PowerCenter to dynamic SAP ABAP mappings:
• - Select single
• - Select all
• - Select distinct
• - Order by ports
• - Source table name
• - Dynamic filter
• - Install ABAP program name and enable override
• - Install ABAP program mode, such as stream or file
• - Output is deterministic
• - Parameterized connection
• - Column description
• - Pushdown optimization
• - Partitioning other than key range partition
• •PC to Cloud Conversion does not convert the following target properties while converting static SAP ABAP mappings from PowerCenter to dynamic SAP ABAP mappings:
• - Data driven
• - Parameterized connection
• - Column description
• •PC to Cloud Conversion does not convert the following properties while converting dynamic SAP ABAP mappings from PowerCenter to dynamic SAP ABAP mappings:
• - Parameters with CDS views
• - Parameterized file based connections
• - Lookup filter
• - Partitioning
• •PC to Cloud Conversion has the following known limitations while converting dynamic SAP ABAP mappings from PowerCenter to dynamic SAP ABAP mappings:
• - The converted mapping does not contain space between the operator in the filter value. You can update the filter value in the converted mapping. For example, PowerCenter filter: ZEMP_SRC.COL1>1007 AND ZEMP_SRC.COL4>=3000, and you must set the filter in cloud as follows: ZEMP_SRC.COL1 > 1007 AND ZEMP_SRC.COL4 >= 3000.
• - PC to Cloud Conversion converts the join condition defined in the dynamic ABAP mapping as an advanced join in the converted mapping. After conversion, you can edit the mapping to change it to a custom join with a predefined operator. This is because Cloud Data Integration does not support advanced joins in the dynamic ABAP sources.
• •PC to Cloud Conversion has the following known limitations while converting static SAP ABAP mappings from PowerCenter to dynamic SAP ABAP mappings:
• - If you have PowerCenter mappings that generate ABAP code using Exec SQL or Force Nested Loop, PC to Cloud Conversion converts it to mappings that generate ABAP code using the Force Nested Loop (Open SQL) program by default.
• - PC to Cloud Conversion does not convert the ABAP program flow options, such as Insert Function, New ABAP Code Block, and ABAP program variables.
• - If you have PowerCenter mappings that disable ABAP authority check while you generate and install the ABAP program, PC to Cloud Conversion converts it to cloud mappings that does the authority check by default.
• - If you have static filter defined at mapping level and filter overridden at the session level, the session level filter gets the higher precedence than the mapping level. The converted mapping contains the filter value of the session. Since the filter format differs in PowerCenter and Cloud Data Integration, you can update the filter value in the mapping. For example, PowerCenter filter: KNA1 = KNA1-MANDT = 800, and you must set the filter in cloud as follows: KNA1.MANDT = '800'.
• - PC to Cloud Conversion converts the join condition defined in static ABAP mapping as an advanced join in the converted mapping. After conversion, you can edit the mapping to change it to a custom join with a predefined operator. This is because Cloud Data Integration does not support advanced joins in the dynamic ABAP sources.