Rules and Guidelines for SAP Sources and Targets

• •When you configure an SAP source, configure row limits using the advanced source properties available on the scheduling page of the task wizard. Row limits on the data filters page of the task wizard are not enabled for SAP sources.
• •Do not use tables as SAP Table sources if the sources have circular primary key-foreign key relationships.
• •When you use more than one SAP table in a Data Synchronization task, you can use one cluster table or one pool table. If you use more than one cluster or pool table, errors occur at run time. You can use the Object Search dialog box to see if a table is a cluster table or a pool table. You can use multiple transparent tables in a task.
• •When you join a cluster table or pool table with a transparent table, include all key fields in the transparent table in the join condition. List the fields in the order that they appear in the SAP system.
• •When you join a cluster table or pool table with a transparent table, use all of the source fields in the transparent table that you use in the joins and filters in the field mapping. Also, map at least one field from the cluster or pool table.
• •Define relationships for multiple sources after the data preview displays the data. You can use the wizard in advanced mode to avoid waiting to preview data.
• •Data sorting is not supported on cluster or pool table fields.
• •You can use Informatica Cloud variables and ABAP variables in simple data filters for SAP tables. Do not use ABAP syntax in simple data filters for SAP tables.
• •You can use ABAP variables and ABAP syntax in advanced data filters for SAP tables. Do not use Informatica Cloud variables in advanced data filters for SAP tables.
• •Do not use the Is Null or Is Not Null operators in data filters for SAP cluster and pool tables.
• •Do not use the Is Null or Is Not Null operators in data filters on SAP character fields.
• •Due to an SAP limitation, tasks that require a read longer than 30 minutes can fail. You might use one or more of the following suggestions if you encounter this problem:
• - Use the SAP advanced source properties to limit the number of rows to be read.
• - Configure a data filter to reduce the number of rows to be read.
• - Reduce the number of output fields for the task.
• - Configure the SAP parameter rdisp/max_wprun_time to allow more time for the read. For more information, see the SAP documentation.
• - To increase the amount of records that the Secure Agent can retrieve at one time, you can increase the Java heap memory for the Secure Agent. To do this, edit the Secure Agent. In the System Configuration Details section, select DTM and set the JVMOption1 property to the following value: Xmx512m. Click OK to save the change and restart the Secure Agent. Adjust the value for the JVMOption1 property based on the amount of records you want to retrieve and the available memory on the Secure Agent machine.
• •For a lookup on an SAP object, configure the lookup to return less than 20 rows. Tasks might fail if the lookup returns more than 20 rows.
• •A lookup on an SAP object does not return matching rows if the lookup comparison value is NULL.
• •When you define a reject file name for an SAP target, use the default name or the variable $ErrorFileName. The $ErrorFileName variable uses the following convention for reject file name:
s_dss_<task name>_<run number>_error.csv.bad
• •When you define a reject directory for an SAP target, use the variable $PMBadFileDir. When you use the $PMBadFileDir variable, the Data Synchronization task writes the reject file to the following Secure Agent directory:
<SecureAgent_InstallDir>/main/rdtmDir/error