FAQ for SAP Table Connector

How can I avoid the CPIC error in the SAP instance when I run a mapping?

For more information about the issue and steps to avoid the CPIC error, see the CPIC error Knowledge article.

How to solve the following error that occurs when I import metadata for an SAP table at design time: “OPTION_NOT_VALID: OPTION_NOT_VALID Message 000 of class SAIS type E”

For more information about the issue when you import metadata for an SAP table at design time, see the SAP language code Knowledge article.

How can I avoid truncation of the tab character when the CHAR data type in an SAP table contains a tab character at the end?

For more information about the issue and steps to avoid the truncation error, see the Truncation of the tab character Knowledge article.

How can I improve performance of an SAP Table mapping that is configured for delta extraction for a large volume of data?

For more information about improving performance of a mapping configured for delta extraction, see the Delta extraction for a large volume of data Knowledge article.

How to solve the following error that occurs when I process the query to look up or filter data from the SAP Table object: An exception with the type CX_SY_DYNAMIC_OSQL_SYNTAX occurred, but was neither handled locally, nor declared in a RAISING clause.

For more information about the issue and steps to avoid the error, see the Processing query to look up or filter data Knowledge article.

How can I import the SAP metadata that contains a SSTRING, STRING, or RAWSTRING data type with precision that is not defined in the SAP system?

For more information about importing the SAP metadata that contains a SSTRING, STRING, or RAWSTRING data type with precision that is not defined in the SAP system, see Importing metadata with SSTRING, STRING, and RAWSTRING data types.

How to solve the following error that occurs when I use an SAP table as a source object in a synchronization task: Field QUERYRESULT not a member of TABLES

You need to install the latest transport files and clear the browser cache.

How to solve the data corruption issue when I read SAP Table data encoded with the UTF-16 code page?

To solve the data corruption issue, configure the SAPStandardCodePage custom property in the Secure Agent.

1. 1Log in to Informatica® Intelligent Data Management Cloud™ (IDMC).
2. 2Select Administrator > Runtime Environments.
3. 3On the Runtime Environments page, select the Secure Agent.
4. 4Click Edit.
5. 5In the Custom Configuration Details section, select Data Integration Server as the service and DTM as the type.
6. 6Enter SAPStandardCodePage in the Name field and set the value to 4103.

7. 7Click Save and run the mapping again.