====== ArticleSubscriptionSelectorDirectSql ======

The JobStep ArticleSubscriptionSelectorDirectSql can select articles and load them into the memory for further processing by means of an article subscription saved with location.\\ 

The ArticleSubscriptionSelectorDirectSql returns at the end all ArticleDetails for each selected article.
The filter is set to article detail level, then the articles are selected from the found article details and then article details of these articles are loaded. 
This is necessary because the pool with which notes which articles the other side has received works on article level.


{{:images:sign_warning.png?nolink|}}**Note:** Works only with MSSQL!

{{images:ArticleSubscriptionSelectorDirectSql.png?nolink}} 

^Name  ^Meaning|
|Type|Type of the job step.|
|Name|Name of the job step that will appear in the job designer|
|Description|Optional description for the job step.|
|**Communication direction**|Here, the communication direction of the message (** Inbound, Outbound **) can be set using the provided UseCase.|
|**Selection**|Here you can set the method by which articles are extracted. |
|**Selection strategy for price lines**|Sets the value for the SelectedPriceLine in the created object of type eBiss.Supplier.SupplierArticleDocument. The following options are possible: ** Fixed: ** The value from 'Standard price line'. ** Templatepartner: ** The price line from the Templatepartner of the Tradingpartner. If this is not available, then the value from 'Standard price line'. If 'Standard price line' is not set, then an error is output. ** Tradingpartner: ** The price line of the Tradingpartner. If this is not available, then the value from 'Standard price line'. If 'Standard price line' is not set, then an error is output. ** Tradingpartner and Templatepartner: ** A combination of 'Tradingpartner' and 'Templatepartner'. |
|**Default Priceline**|Used in the 'selection strategy for price lines', see above.|
|**Link article to article pool**|True or False, if True, already used articles (using the ArticlePoolLinkTable) are memorized and only sent if they have not yet occurred there.
|**Locationfilter**|The way in which these filters are to be applied, whether the results should be included or excluded.|
|**GLN of the location**|Optional filter, which can be used to restrict the affected locations according to the GLN. Wildcards are not possible, they are filtered after the start of the GLN. \\ Note: It is filtered by the GLN of the location, not by the GLN of the partner.|
|**name of the location**|Optional filter which can be used to restrict the affected locations by name. Wildcards are not possible, it is filtered by the beginning of the name. \\ Note: It is filtered by the name of the location, not by the name of the partner.|
|**Group name of the location**|Optional filter as a semicolon-separated list of subscription group names to be taken into account.|
|**Item information**|Article information such as prices and article texts are summarized. The SupplierArticleDocument then contains only one valid price or text item for each item detail, as well as only one item for additional item information. This item is determined depending on the partner who defined the respective article subscription, whereby also superordinate price lines as well as the validity area of the price lines are taken into account.|
|**Max. Number per batch**|Number of items to be processed at once.|
|**Timeout**|Timeout for executing commands on the database in seconds.|



===== The following JobSteps are usually connected to the ArticleSubscriptionSelectorDirectSql =====

  * [[en:prozessdefinition:jobs:jobsteps:allgemein:delegatorjob]]
  * [[en:prozessdefinition:jobs:jobsteps:allgemein:EntityTransformer]]
  * [[en:prozessdefinition:jobs:jobsteps:allgemein:MessageSelector]]