AMN Specificities

This page describe the specific import done for AMN for tyre feed

AMN B2C handles its product catalog through Treadware (software) edited by Pearl

Frequency of updates: Weekly

TW > Global DB: the night between tuesday and wednesday

Global DB > Datastream: the night between wednesday and thursday

Schema of AMN Treadware Architecture

FOR PRODUCTS

IMPORT (TW > Global DB)

Product (`Tyre`) is imported as 'active' within global DB if 'WEBSITE-SHOW-TIREMODEL = 'Y' within Treadware (Tab: 'accelerator-brand-dates), if 'WEBSITE-SHOW-TIREMODEL = 'N', then the product is 'inactive' within globalDB

EXPORT (Global DB > Datastream)

Product (`Tyre`) is exported as 'active' except :

• if the product is deactivated in Global DB

• if all articles have end date in the past or if all articles are deactivated

• if season is empty

If 'startDate' is empty within Treadware, then we take the oldest 'startDate' from its articles

if 'endDate' is empty within Treadware, the we take the further 'endDate' from its articles

FOR ARTICLES

IMPORT (TW > Global DB)

Article (`CAI`) is imported as 'active within global DB if 'launch_date' is not empty within Treadware (tab: brand-line-size-country). If launch date is empty, the article is 'inactive' within globalDB

EXPORT (Global DB > Datastream)

Article (`CAI`) is exported as 'active' except :

• if the article is deactivated in Global DB

• if its end date is before the current date

• if its product end date is before the current date

=> In those 3 cases, it will be send as 'inactive'