Data update
This section gives all the details about B2B data updates.
Products
Articles launches in 2021
Activate/deactivate products
B2B database, as all other databases, contains only an article level (regroups all the CAIs available for the chosen product activity line).
As our website are working on a product (range) level, we are using a Product Template to gather all the information about products in one place: product's name, start/end dates, its family, product characteristics (Mileage, Fuel Saving, RFID, Regroovable, etc.).
To activate a product in Product Template the following information must be present:
product's name -> product's name must be the same as the one in product catalog, if you want to display it differently use display name column
template TDP
universes,
usages.
To deactivate a product you need to simply put an end date set in the past to a Product you wish to deactivate.
B2B data update system is complex. In order to avoid any desynchronization or data deletion, this solution is the easiest one.
How to update your Product Template
The latest Product Template must be downloaded from Lizeo Back Office (the procedure can be found here). All the changes must be made on downloaded Product Template.
Remember! Do not change the columns order as the importer’s mapping is based on the columns’ numeration.
Once product template updated, a Jira ticket (https://jfa-prd.michelin.com/jfa/projects/MIB2BX/) needs to be created. When creating a new ticket, please choose "DCAD-Data Update" as an Issue Type. It will automatically assign your ticket to Séverine Ramadour from Lizeo team. She will update the Product Template, push the new data to the websites and inform once done.
Tyre - retread mapping
How the retread offerings are determined:
For a given tire, first check that the Not_Retreadable column of NEWTIRE_MASTER is not set
For each valid size for the tire from the TRUCK table, select valid retreads from RETREAD_MASTER/MCPL where:
casing_size matches the size from truck (using the size before space - need to be split)
if retread width is 390mm the casing size must not start with '445/50...'
if retread width is 385mm the casing size must not start with '445/50...'
if retread width is 375mm the casing size must not start with '455/55...'
At this point a retread is considered valid no matter what if it matches the corresponding_retread column from NEWTIRE_MASTER or the tire's name is the base of the retread's name. Example: for the tire X One Line Energy D the two retreads X One Line Energy D PM and X One Line Energy D CM would be valid even if their positions or applications did not match. Otherwise, continue checking that:
tire/retread have the same position
if tire is X One, the retread must have "X One" in the name
if tire is not X One, the retread must not have "X One" in the name
tire and retread must share at least one application
The image shown next to the available retreads on the current site is the tire's image based on the size.
Here is the Python code in html format (other formats are not accepted in Gitbook):
There is one rule that needs to be applied manually: if tire is X One, the retread must have "X One" in the name / if tire is not X One, the retread must not have "X One" in the name.
Jira ticket
Europe
Europe database is being updates every two months using Jira ticket. As mentioned earlier, B2B database import and export is a complex process that consist on integrating five different elements: Product Template, RAG, AUG PL and Covered.
List of people responsable for European catalog updates:
Product Template by Country Responsible (in case of any problem please contact Florence Cottier)
RAG by @Thomas Puvis
AUG PL by @Damien Gonzales
Covered by @Jean-Maxime Moureaux @Benjamin Allegre @Celine Faure
USA
USA is using 4 databases: RAG, Covered, Access PL and their own dealer database. RAG and Covered databases follow the same update pattern as Europe. The two other databases Access PL databases (for truck tyres and retreads) and dealer database are automatized.
With every update CARGOXBIB2 and TWEELS CAIs must be checked before Lizeo's update as those CAIs are being added manually.
Sort order update
B2B has two different sort orders:
generic sort order -> used in search by: Univers/VehicleType, Size and Position
usage sort order -> used in search by Usage
Generic sort order is updated via Product Template (column C - Generic Sort Order).
Sort order by usage is updated via Sort Order per Usage file. Every usage has its proper sort order, where 1 is the highest priority (Tyre marked as 1 will be displayed on top of the list).
The request of sort order change needs to be created using Jira ticket (https://jfa-prd.michelin.com/jfa/projects/MIB2BX). When creating a new ticket please choose "DCAD-Data Update" as an Issue Type and assign it to Kamila Jamroz.
Dealers
In progress
How data is being update in Datastream
Remember! Products and articles cannot be authored via Apostrophe. All the information is data driven, must be updated via product catalogs and product template.
What happens in Michelin Database (Datastream) when you update the information?
It's cancel&replace system on the product level (not feed level!). On every database update, Datastream delete the elements present in the new feed and import the new information.
What does it mean?
When there is no changes, old data stays in the database.
If you need to delete a tyre or a dealer from the website, you need to deactivate it! It will hide the information from the website.
Deleting information from Lizeo BO, will not delete it from the website.
Last updated
Was this helpful?