Glossary #
Xtract Universal uses the following terms for its components:
| Term | Description |
|---|---|
| Extraction | Extractions are the main entities in Xtract Universal. An extraction is a combination of a source (SAP system), destination (e.g., SQL server) an extraction type (e.g., Table) and the SAP data that is extracted. When running an extraction, the SAP data that is defined in the extraction type is extracted from the assigned SAP source and written to the assigned destination. Example: The SAP table KNA1 is extracted from an SAP S/4HANA system and written to an SQL Server. A list of all created extractions is displayed in the main window of the Designer:  |
| Extraction Type | The extraction type defines what SAP data is extracted by which method. Xract Universal offers the following extraction types: BAPI, BWCube, BW Hierarchy, DeltaQ, ODP, OHS, SAP Query, Report, Table and Table CDC. |
| Source | A source represents a connection to an SAP System, see Creating an SAP Connection. |
| Destination | A destination defines how the extracted SAP data is processed. This could be a conversion to file-based formats for local or cloud-based file systems or to deliver the data to targets like databases and other APIs. For a complete list of available destinations, see Destinations. |
Example
Basic Functionality - Architecture #
Using Xtract Universal contains two main phases: design phase and execution phase.
In the design phase the user can:
- create and modify extractions, sources and destinations.
- alter the server settings in the Designer.
In the execution phase the user can:
- execute the extractions designed in the design phase.
- parameterize extractions that use runtime parameters.
The execution of the extractions takes place on the server.
Depending on the target environment an execution can be triggered either by the XU command line tool - xu.exe / xu.elf or by the consuming destination.
For more information, see Pull and Push Destinations.
Find more information in the following subsections: