====== TradeItemManagerBookCache ======

The TradeItemManagerBookCache requires the Jobstep [[en:prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerfillcache]], it stores the article details, price lines or texts transferred to the cache tables into the corresponding ArticlePoolTable by means of a stored procedure.

{{:images:sign_warning.png?nolink|}}**Note:** __Works only with MSSQL__ and needs to be used after [[en:prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerfillcache]].
On non __MS-SQL Server__ systems, the [[en:prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerbookcache|]]  must be used.

^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.|
|**BookOption**| **//UpdateAndInsert://** By default, changes existing articles, if new, and adds new ones. ** // NoUpdate: // ** Only adds new articles. ** // NoInsert: // ** Updates only existing articles, adds no new ones. ** // ForceUpdate: // ** How ** // UpdateAndInsert // ** (change + insert) and marks all affected records as changed, that is, including those where there are no changes to the data. Note: This option is effective for posting articles.|
|**OverwriteArticleDetail**|Allows you to override items in the database.|
|**SqlCommandTimeout**|Here the SQL server timeout can be entered for the SQL queries.|
|**UpdateOnly**|This option is only for price lines. It affects neither articles nor text containers. ** // True: // ** Only make changes to existing price bookings. ** // False: // ** New and changed price lines are posted in ArticlePool.|

===== Posting items in the Supplier.ArticlePool =====
 
Articles are posted in the Supplier.ArtikelPool according to the following procedure: \\ \\ ** Articles are searched in the database for article number, color, size **

  - case: **Article is not available in database:**        
     * **EAN available:** Article from article catalog is not written to database --> Log entry: duplicate article.  
     * **Ean not available:** Article from article catalog is newly created in the database.  
  - Case: **Article exists in database:**        
        * **EAN is equal:** Article from article catalog is compared with the one from database, changed fields are saved in database.  
        * **EAN is not equal:** Article from article catalog is not written into the database --> log entry: double article.

{{:images:sign_warning.png?nolink|}}**Note:** In order to avoid the simultaneous booking of article data in the cache tables or in the article data tables by two consecutive jobs, this jobstep is equipped with a lock mechanism.

===== Option OverwriteArticleDetail =====

The OverwriteArticleDetail option allows you to override an article in the database. This results in the following constellations:

  - Case **Article is not available in database:**        
     * ** EAN available:** Data record for the EAN is deleted in database, then a new data record for the article is created from the article catalog and stored in the database.  
     * ** Ean not available:** Article from article catalog is created in database.  
  - Case **Article exists in database:**        
     * ** EAN is equal:** Article from article catalog is compared with the one from database, changed fields are updated in database  
     * ** EAN is not the same:** Search record with Ean and delete from database, create new record for articles from the article catalog in database and save.  



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

  * [[en:prozessdefinition:jobs:jobsteps:allgemein:MessageSelector]]
  * [[en:prozessdefinition:jobs:jobsteps:allgemein:TaskNotificatorEx]]