Build Package Overview

Packages, which download the data from the source database, can be built for a single table or for all tables in a source database.

When a package is created, the following SQL commands are built:

  • Create Table SQL commands
  • Select command for the package to execute
  • Primary key (if the source system is a SAP database)

This section contains the following topics:

Package Types

Package Types are ways in which data is downloaded from the source. The following table outlines the various package types supported in Collect:

Package Type



Uses Remote Function Calls from SAP to download data. This is a modified form of SAPRFC, and Syniti recommends BOARFC over SAPRFC


Uses a CranPort package.

NOTE: The component is referred to as Assemble in the help. The package type is still CranPort.

DBMoto Download

Uses Syniti Data Replication's Refresh replication method to download a snapshot of data.

DBMoto Mirror

Uses Syniti Data Replication's Continuous Mirroring replication method. This enables one-direction mirroring from Source to Target. This process starts with a full extract and then mirrors the changes.

Excel Import

Reads the data from an Excel file.

IG Universal Connect

Uses a Boomi Process that executes against the IG Universal Connect data source. This package type is set by default for IG Universal Connect data sources and cannot be edited.


Uses a custom CranPort™ package created by the user.

Manual Data Services

Uses a custom Data Services package created by the user.

NOTE: The Data Services Job that is run with this package type must follow the naming conventions defined for Collect. Refer to Use the Manual Data Services Package Type for more information.


Uses a custom SSIS package created by the user.

SAP Data Services

Uses the Data Services module of SAP. This is the recommended package type.

NOTE: When using this package type, it is recommended that the Delete Target Table On Build check box be disabled in Collect on the Target Sources page’s Vertical View on the Advanced tab. In this case, if the check box is enabled, dspCompose™ will  delete every record in the target table during the Final Finish process (during which data posted in the target ERP system by the request is downloaded to tables.)

SAP Data Services using RFC

Uses Remote Function Calls via Data Services to extract data from an SAP Application instance.


Uses Remote Function Calls from SAP. SAP provides this package, but BOARFC is recommended.

SAP Text

Uses Remote Function Calls  from SAP to download data only from the tables STXH and STXL with certain parameters that are defined in Collect.


Uses an SSIS package (Microsoft).

Build Package for Table

To build a package for a table:

  1. Click Tables in the Navigation pane.
  2. Verify the table is active.
  3. Verify a package name is listed for the table.
  4. Click Targets in the Navigation pane.
  5. Click Sources for Target.
  6. Click Tables for Source.
  7. Select the Table.
  8. Click Build And Refresh on Page toolbar to build the package and download table from source; a confirmation message displays.
  9. Click Ok.

NOTE: If the package for the table already exists, it is only refreshed (i.e., data is pulled from the Source database). If the package for the table does not exist, the package is built and the table is refreshed. To build only the package, and not refresh it, click Build Package on the Page toolbar.

Build Package for Schedule Group

To build a package for a schedule group:

  1. Click Targets in Navigation pane.
  2. Click Sources for Target.
  3. Click Schedule Groups for Source. 
  4. Select the Schedule Group.

    NOTE: If building a group with a Syniti Data Replication package the following applies:

    • if Schedule Group is set to NO GROUP, both Download and Mirror package will be built as an individual replication in Syniti Data Replication.
    • If Schedule Group is set to AUTO and if it is a Download package, the replication will be part of a group named <GroupPrefix>_Downloads.
    • Otherwise, if it is a Mirror package the replication will be part of a group called <GroupPrefix>_<number>> where number is an incremental value to count the number of groups. Groups cannot contain more than <Group_Size> replications.
    • If Schedule Group is set to "existing group name" with no restriction to the <Group_Size> parameter the replication is built into that group.

      NOTE: The Replication Mode must be consistent with the Replication Group Mode (e.g a download package cannot be grouped with a mirror package).

  1. Click Build Package on Page toolbar; a confirmation message displays.
  2. Click Ok.

    NOTE: If no package exists, a package is immediately scheduled to be built and the table is refreshed. If a package exists, the table is refreshed.