Task "XSuiteHelixLookupImport"
The following properties apply specifically to the task of type "XSuiteHelixLookupImport." This task transfers master data from SAP or another local data source to the Lookup Service in the xSuite Helix Cloud.
Notice
This procedure is obsolete. Use the "XSuiteHelixDataImport" task instead.
Property | Description |
|---|---|
Schedule[].Task[].Database.ConnectionString*(§) Schedule[].Task[].Database.Select* Schedule[].Task[].Database.Password(§) | In the For both properties, use the same syntax as for the connection of external data sources in the context of a scenario configuration (see External Data Sources). The same data sources are also supported. The password required in the connection string can be defined separately in |
Schedule[].Task[].Lookup.Url* Schedule[].Task[].Lookup.RequestTimeout Schedule[].Task[].Lookup.Keycloak* Schedule[].Task[].Lookup.ProxyServer | Connection data for the lookup service in the xSuite Helix Cloud In For For |
Schedule[].Task[].Lookup.DataSource.Name* Schedule[].Task[].Lookup.DataSource.KeyField Schedule[].Task[].Lookup.DataSource.Clear Schedule[].Task[].Lookup.DataSource.MaxBatchSize Schedule[].Task[].Lookup.DataSource.SignalUpdate | Properties of the target data source in the lookup service When specifying
The Boolean value
To ensure that for all data sources transfer and common signaling is not performed until the end, define one task per data source within a schedule-worker instance. For all tasks but the last, use the |
Schedule[].Task[].Localize.GroupByField[]* Schedule[].Task[].Localize.KeyField* Schedule[].Task[].Localize.ValueField* Schedule[].Task[].Localize.PropertyName Schedule[].Task[].Localize.KeyMapping[] | Properties for localizing data records to be transferred (optional) This requires specially structured source data records. Related data sets that represent the same content in different languages must be returned in immediate succession in the query result. A language-specific value (e.g., an article description) is permitted for one field only. In some predefined queries, these kinds of source data records are provided by systems such as "SAPWMDQUERY." In When transferred to the lookup service, the records defined with a common key value are combined to form a single group. Only for the corresponding language-dependent part of a data set is a multiple value transferred. The value is composed of pairs consisting of language indicator and value specification. You can configure the name of the property for these value pairs by using If the language tags from the source records do not match those expected by the lookup service, you can map them as needed (e.g., from "E" to "en-US"). Map them in
|
Schedule[].Task[].Field[]* | Definition of the fields to be transferred from the source system to the target system Make field specifications in the form of multiple subparameters. Source fields that are not explicitly specified will be ignored.
Base the name of the source field on the source system. In a relational database, for instance, the name should correspond to the field name returned by the SELECT query. However, do not give calculated or aggregated fields a dedicated name. If you have not given these fields an explicit name per AS clause, the fields will be given the pseudonym "Column {field number}". For the source system "SAPWMDQUERY," the name always corresponds to the value in the metadata field "E_LISTDESC.FNAME" of the query result. The The target dataset is a JSON object. The By default, the data types of the values are retained in the form in which they have been read from the source system. You can integrate required transformation functions into an SQL-SELECT query. Alternatively, the The primary purpose of the |
Schedule[].Task[].ContentLogFolder | Folder path where the full contents of the records transferred to the lookup service are logged (optional) This feature is primarily for the purposes of analysis and should not be used in normal operation. |