The specific job objects TradeItemManagerFillCache and TradeItemManagerBookCache are used to update any article information.

The TradeItemManagerFillCache and the alternate TradeItemManagerDirectSql can populate four different manifestations of the pool and must be set accordingly. These provide the following options:

1. Items¹⁾
2. Prices²⁾
3. Texts³⁾
4. Additional information⁴⁾

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⁵⁾, PriceListDocument⁶⁾,TextDocument⁷⁾ and 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.

A standard procedure for the update of the article data looks in a supplier system as a rule as follows: The specific job objects TradeItemManagerFillCache and TradeItemManagerBookCache are used. Provided you have a database that supports the stored procedures used by eBiss for this purpose⁹⁾See )). Alternatively the slower TradeItemManagerDirectSql¹⁰⁾ is used.

Note: Suitable for all database systems which are supported by eBiss.

Note: Only for use with MSSQL as database system.

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 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.

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

Here, the respective corresponding External “Fill” procedure must then be defined in the TradeItemManagerFillCache.