====== Article import/update ======

The specific job objects **[[en:prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerfillcache|]]** and **[[en:prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerbookcache|]]** are used to update any article information. 

===== Update methods =====

The [[prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerfillcache|]] and the alternate [[prozessdefinition:jobs:jobsteps:supplier:deprecated:tradeitemmanagerdirectsql|]] can populate four different manifestations of the pool and must be set accordingly. 
These provide the following options:
  - Items((eBiss.Supplier.TradeItemDocument))
  - Prices((eBiss.Supplier.PriceListDocument))
  - Texts((eBiss.Supplier.TextDocument))
  - Additional information((eBiss.Supplier.AdditionalInfoDocument))

Depending on the settings made here, a suitable in-house file must be available, and mappings from the in-house format to the eBiss structures **TradeItemDocument((eBiss.Supplier. TradeItemDocument)), PriceListDocument((eBiss.Supplier.PriceListDocument)),TextDocument((eBiss.Supplier.TextDocument))** and **AdditionalInfoDocument((eBiss.Supplier.AdditionalInfoDocument))** exist to post prices and item data. It is of course also conceivable to fill all or some of the eBiss structures with only one in-house type. Then it needs accordingly less selectors.
===== Conventional Integration via file =====

A standard procedure for the update of the article data looks in a supplier system as a rule as follows:
The specific job objects **[[en:prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerfillcache|]]** and **[[en:prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerbookcache|]]** are used.
Provided you have a database that supports the stored procedures used by eBiss for this purpose((Usable only for [[en:ueberblick:systemvoraussetzungen:mssql|]] data base system.))See )).
Alternatively the slower **[[en:prozessdefinition:jobs:jobsteps:supplier:deprecated:tradeitemmanagerdirectsql|]]**((Usable for all eBiss supported data base systems.)) is used.

==== Update job ====

{{:images:sign_warning.png?nolink|}}**Note:** Suitable for all database systems which are supported by eBiss.

{{:howtos:supplierarticlepool:import_update:articlepool-file-integration.png?nolink|}}

==== Update job with DirectSQL ====

{{:images:sign_warning.png?nolink|}}**Note:** Only for use with MSSQL as database system.

{{:howtos:supplierarticlepool:import_update:articlepool-file-integration_tradeitemmanagerdirectsql.png?nolink|}}



===== Integration via database connection and external procedure =====

Post article data directly from inventory management or from the ERP system.
Data from the ERP system can be written directly into the eBiss database using existing views. From here the data can be transferred very quickly (see [[:ueberblick:benchmarks:artikelpool|performance]]) into the ArticlePool. 
The corresponding views are:

  * **ArticlePool_FillArticleCache_View**, for the article data.
  * **ArticlePool_FillPriceLineCache_View**, for the price data.
  * **ArticlePool_FillTextCache_View**, for the texts.
  * **ArticlePool_FillCustomItemsCache_View**, for the article custom items.

==== Update Job ====
A corresponding job to transfer the data can look like this:

{{:howtos:supplierarticlepool:import_update:articlepool-db-integration.png?nolink|}}

Here, the respective corresponding External "Fill" procedure must then be defined in the [[prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerfillcache|]].


===== Expert Topics =====

{{indexmenu>.#1|navbar}}