SAP Connector

Back Next

SAP mapplet properties

You can commit data, cache data, and handle errors for the target in an SAP BAPI/RFC mapping task.

To configure the SAP mapplet properties for the target, click the

Runtime Options

tab of the SAP BAPI/RFC mapping task. Expand the

SAP Mapplet Properties

section, and configure the mapplet properties.

The following table describes the commit properties you can configure in an SAP BAPI/RFC mapping task:

Property	Description
Perform Commit	Issues a commit with a BAPI commit function. If you disable this option, Data Integration does not call a commit function. It also ignores the commit interval and does not wait for a commit to continue to run the mapping task. Default is enabled.
Perform Commit Wait	Waits until the commit is complete to continue to run the mapping task. SAP sends a return call to Data Integration when the commit is complete. If you disable this option, Data Integration continues to process data during the commit. Default is enabled.
Commit Interval	Number of BAPI/RFC calls after which Data Integration issues a commit. To issue a commit, Data Integration makes a BAPI/RFC commit call. If you disable the Perform Commit option, Data Integration ignores this value. Default is 1000.
Commit Function	Determines how Data Integration makes a BAPI/RFC call when it issues a commit. Data Integration makes the call either from outside SAP or from within BAPI based on the following options you select: ABAP4_COMMIT_WORK. Makes a BAPI/RFC call from ABAP and then issues a commit. BAPI_TRANSACTION_COMMIT. Makes call from outside SAP and then issues a commit. If you disable the Perform Commit option, Data Integration ignores this value. Default is BAPI_TRANSACTION_COMMIT.

The following table describes the data caching properties you can configure in an SAP BAPI/RFC mapping task:

Property	Description
Cache Directory	Default directory used to cache BAPI data. By default, the cache files are created in a directory specified by the variable $PMCacheDir. If you override the directory, make sure the directory exists and contains enough disk space for the cache files.
Cache Size	Total memory in bytes allocated to Data Integration to cache data prepared for BAPI/RFC mapplets. Default is 10 MB.

The following table describes the error handling properties you can configure in an SAP BAPI/RFC mapping task:

Property	Description
Duplicate Parent Row Handling	Determines how Data Integration handles duplicate parent rows in a mapping task. Select one of the following options: First Row. Passes the first duplicate row to the target. Data Integration rejects rows with the same primary key that it processes after this row. Last Row. Passes the last duplicate row to the target. Error. Data Integration passes the first row to the target. Rows that follow with duplicate primary keys increment the error count. The mapping task fails when the error count exceeds the error threshold. Default is First Row.
Orphan Row Handling	Determines how Data Integration handles orphan rows in a mapping task. Select one of the following options: Ignore. Ignores orphan rows. Error. The mapping task fails when the error count exceeds the error threshold. Default is Ignore.
Continue on Error	Determines if you want to continue to run the mapping task when a BAPI/RFC error is encountered. Default is enabled.