====== TradeItemManager (Retail) ======

The **eBiss.Retail.TradeItemManager** writes all articles extracted from an **eBiss.Retail.TradeItemDocument** entity or document, into the eBiss database.
The inventory levels are updated in the WWS by incoming OrderResponse and DispatchAdvice documents.

^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.|
|**AutoCreateLocations**|True or False; in True, a new location is created with the GLN from document, and False searches for a location with GLN from the document with the partners in the eBiss database.|
|**PosActionDeleteThanRemoveArticle**|(False) ArticleDetail (Ean) is marked as deleted but the record remains in the ArticlePool. \\ (True) ArticleDetail (Ean) is deleted from ArticlePool.|

==== Overwriting recycled article details (eans) ====

The Jobstep **eBiss.Retail.TradeItemManager** can register recycled eans. The **OverwriteEan** configuration is the default setting of the job task. However, there is the possibility to ban the **OverwriteEan** property at the TradingPartner location level. For this purpose, an eBiss variable called "OverwriteEan" must be created, or be imported into eBiss using a template.

In addition, the value of the variable must be explicitly set to "False" at the corresponding TradingPartner location. If you have not yet instantiated the variable at the corresponding TradingPartnerLocation, you can do this by instantiating the variable "OverwriteEan" . You can set the False value by removing the Hook of the "FlagValue" option. Then the TradeItemManager will trigger an error if an ean with a different article number, color or size already exists in the ArticlePool