Mapping

Click the "Name" or the "x" icon to remove the "Name".

To map index, go to "Data" - "Index mapping". Click the pen icon for the index value to be mapped. Drop-down lists will be shown for: * Type of media * Angle * Priority Click to select a “Type of media” that is best suited for the uploaded "Supplier index". Click to select a “Angle” that matches the angle for the uploaded "Supplier index". Note that the selectable values for “Angle” might be different for different “Type of media”. If having several "Supplier index" mapped to the same "Type of media" and "Angle", different priorities can be selected to set the ordinal. Click to select “Priority”. Click "Save". The index mapping will be saved.

To start edit an already saved index mapping, click the three dotted icon. Click to select "Edit". Drop-down lists will be shown for: * Type of media * Angle * Priority Mapped values will be selected. Click to select a new value from any of the three drop-down lists. Click "Save". The changes will be saved.

To start clear an already saved index mapping, click the three dotted icon. Click "Clear" to clear the index mapping. The index mapping will be cleared.

If trying to leave the page without saving any changes, a pop-up window appears saying there are unsaved changes. Click "Cancel" to go back to "Index mapping". Click "Discard changes" to leave "Index mapping" without saving any changes. Click "Save changes" to save any changes and leave the "Index mapping".

Seasons will be empty before any seasons has been mapped, or uploaded* in a master data file (PRICAT). Suppliers must map a season “Name” to a universal “B24 Season” before a master data file (PRICAT) can be uploaded. This "Name" must be the same as for "Period/Season" in the header of the master data file (PRICAT) to be uploaded. If using any of the "B24 Season" in the master data file (PRICAT), there is no need for mapping it before uploading. The season will be mapped automatically. Buyers don't have to map seasons, unless they want to receive other season names than the universal seasons, "B24 Season". Universal seasons, "B24 Season", will automatically be added as a new season on the buyers side with the universal seasons, "B24 Season" as "Name".

There is a list of universal "B24 Season" names to choose from when mapping seasons in the platform. These seasons are named from the most common season names within the retail industry. The "NOS" season is independent of years, while the rest are year specific. Below examples of "B24 Season" names for 2022: * 2022 * Spring/Summer 2022 * Fall/Winter 2022 * Q1 2022 * Q2 2022 * Q3 2022 * Q4 2022 * Pre-spring 2022 * Spring 2022 * Main-spring 2022 * Pre-summer 2022 * Summer 2022 * High-summer 2022 * Pre-fall 2022 * Back-to-school 2022 * Fall 2022 * Winter 2022 * Holiday 2022 * Resort 2022 * M1/January 2022 * M2/February 2022 * M3/Mars 2022 * M4/April 2022 * M5/May 2022 * M6/June 2022 * M7/July 2022 * M8/August 2022 * M9/September 2022 * M10/October 2022 * M11/November 2022 * M12/December 2022

To map a season, go to "Data" - "Seasons". Click to enter a "Name". Buyers will see a list of already mapped seasons, if any, and can click to select any of those seasons. When start typing a name, a drop-down list appears, adding what is being entered with "Add new season" after it. When done typing, click "Add new season" in the drop-down list. The "Name" will be added. Click "Select season". A drop-down list with "B24 seasons" appears. Type to search for a relevant "B24 season", and/or scroll to find a value. Click to select. The selected "B24 season" will be added. Click the plus icon to map the season. The "Name" will be added to the list of mapped seasons. More information: Step by step guide from uploading to publishing master data.

A supplier cannot map the same "Name" to different "B24 season". If trying to add a "Name" that has already been mapped, an error occurs saying "Name must be unique".

It´s possible for a supplier to map different "Name" to the same "B24 season", as for the "B24 season" "2024" in the example below.

A buyer cannot map the same "B24 season" to different "Name". If trying to add a "B24 season" that has already been mapped, an error occurs saying "There is already a season mapped to the selected B24 season".

It´s possible for a buyer to map different "B24 season" to the same "Name", as for the "Name" "2024" in the example below.

When mapping supplier indexes in the platform, selections are made from "Type of media", "Angle" and "Priority". Each selection gives a number and concatenated they will result in the "B24 universal Indexes". For example: A supplier index for images presenting a product from the front, with no mannequin/model, should preferably be mapped to: 2 - Images with no mannequin/model 1 - Front 1 - Priority 1 This will result in 211 as the "B24 universal Index". If there are several indexes presenting a product with no mannequin/model from the front, different priorities should be used: 2 - Images with no mannequin/model 1 - Front 2 - Priority 2 This will result in 212 as the "B24 universal Index".

Click the "B24 season" or the "x" icon to remove the "B24 season".

Click "Search seasons..." to start searching for a season "Name". Enter a "Name" to search for. Click "Search". The result will be shown.

Click the pen icon to start editing. Click the field for "Name", and enter a "Name". Click the padlock icon to save.

As a supplier it´s only possible to delete a season before any PRICAT has been uploaded to that season. Click the trashcan icon to start deleting the season. A pop-up window appears asking "Are you sure you want to delete the season?". Click "Cancel" to go back without deleting the season. Click "OK" to delete the season. The season will be deleted.

Parties very often have different definitions of common properties. In the Gender property, the female value can be for example one of the following: * Female * F * Women * Womens * Wmn * Wms * etc. Since parties for obvious reasons benefit from receiving this and other properties in a uniform way, all parties have an option to require their business partners to map of a selection of different properties. Parties map their values to the Btwentyfour universal values, which can then be mapped to proprietary values of choice by each business partner. Examples of mappable properties are: * Size * Gender * Age * Country of Origin * Unit of Measure * etc. Important: Each property value only needs to be mapped once. Once done, the BOP will store, and reuse the specific mapping, regardless of business partner and product for all future.

Buyers, like for example some marketplaces, might require models to be mapped towards categories as a first step in the validation process. The reason for that is that each category could have different requirements regarding what data to be needed, or what data to be mapped. For example, a buyer might require more information for models mapped to a category called "jacket" than for models mapped to categories like "shirt" or "trouser". After the first validation of a publication towards a buyer requiring model mapping, validation error regarding model mapping will be shown. When models has been mapped, the publication should be re-validated to see if any further data mappings is required, and/or any data is missing. In the example above models mapped to category "jackets" has received validation errors as the buyer require "season" and "materialPercentage" to be uploaded for models mapped to that category. For more information: How to map models?

"Model Mapping" will be visible in the menu when a publication has been validated towards a buyer that requires model category mapping. They are in place to determine the category of each uploaded product. Go to "Data" - "Model mapping". Click to select "Buyer". Click to select "Season". Note that available seasons are depending on selected buyer. "Mandatory mapping" will show a list of models to be mapped. To start mapping a model, click "Select category...". Click to enter a value to search for, and/or scroll to find a value to select. Click to select. The selected category will be applied to the model. Click "Save mappings". The mappings will be saved... ...and can be found under "Completed mappings". Fore more information: What is category driven validations?

Enter data according to the following: Property The name of the property as specified in the portal. For example: "ageGroup" Action Could be either "Add" or "Delete". Enter "Add" for new values to be imported. Enter "Delete" to delete values from the database. To update an existing value, the value needs to be deleted at first. Set The name of the set as specified by the party. For example: "AgeGroup" Code The code for the value. For example: "001", "002" Value The property value. For example: "Children", "Youth" Ordinal Sets the order of the values in the UI. For example: "1", "2" Save the file.

Go to "Data" - "Data Sets". To start downloading a file, click "Select property", and select the property to download. Click "Download". A pop-up window appears. The only format available is "Excel (*.xlsx)", and it is selected by default. Click "Download". A download process will start, and the file will be ready for download when done.

Partners having validations that requires either the partner or its suppliers to map their values towards a party specific set in the platform could upload new or delete existing values and sets by importing an Excel file. Note that to update an existing value, the value needs to be deleted at first. Go to "Data" - "Data Sets". Drop an Excel file in the area for "Upload file", or click in the area for "Upload file" to select an Excel file from your computer. Click "Upload". The file will be uploaded.

To clear a mapping, start by clicking "Clear". The mapping will be cleared. Note that any changes made needs to be saved.

Parties very often have different definitions of common properties. In the Gender property, the female value can be for example one of the following: * Female * F * Women * Womens * Wmn * Wms * etc. Since parties for obvious reasons benefit from receiving this and other properties in a uniform way, all parties have an option to require their business partners to map of a selection of different properties. Parties map their values to the Btwentyfour universal values, which can then be mapped to proprietary values of choice by each business partner. Examples of mappable properties are: * Size * Gender * Age * Country of Origin * Unit of Measure * etc. Important Each property value only needs to be mapped once. Once done, the BOP will store, and reuse the specific mapping, regardless of business partner and product for all future.

To filter by “Property” click on the drop-down list and select the property to filter by. When a property has been selected, the property will be added to the top of the drop-down list... ...and the results will be affected immediately. The different filtering’s will affect each other, why properties to be selected under “Property” might be less if any filtering has been made for a specific “Party” or a specific “Publication”.

To filter by “Party” click on the drop-down list and select the party to filter by. When a party has been selected, the party will be added to the top of the drop-down list... ...and the results will be affected immediately. The different filtering’s will affect each other, why parties to be selected under “Party” might be less if any filtering has been made for a specific “Property” or a specific “Publication”.

To filter by “Publication” click on the drop-down list and select the publication to filter by. When a publication has been selected, the publication will be added to the top of the drop-down list... ...and the results will be affected immediately. The different filtering’s will affect each other, why publications to be selected under “Publication” might be less if any filtering has been made for a specific “Property” or a specific “Party”.

Click "Clear filter" to remove any filterings made.

It is possible to search for a “Source value” by entering a search value in the field for “Search source value”. The result will be shown immediately.

Go to "Data" - "Data mapping". Click on the set to view the underlying set name(s), if not already showing. Click on the row for the set to be mapped. A new page will open for the set selected. “Mappings to do” will be listed. Any completed mappings will be shown below the “Mappings to do”. To select a set for all source values to be mapped to, click "Select set". Scroll to find a set suitable for the source value to be mapped, or type to search for a suitable set, and click to select the set. The target set will be selected. If there is a target value within the selected target set that matches the uploaded source value, target set will be set on each row and target value will be added automatically. If there is no target value within the selected target set that matches the uploaded source value, target value needs to be selected manually. Click "Save mappings" to save mappings. More information: Step by step guide from uploading to publishing master data.

Click "Select set". Scroll to find a set suitable for the source value to be mapped, or type to search for a suitable set, and click to select the set. The target set will be selected. If there is no target value within the selected target set that matches the uploaded source value, target value needs to be selected manually.

Click "Select value". Scroll to find a value to map, or type to search for a value, and click to select the value. The value will be selected.

To select a set for all source values to be mapped to, click "Select set". Scroll to find a set suitable for the source value to be mapped, or type to search for a suitable set, and click to select the set. The target set will be selected. If there is a target value within the selected target set that matches the uploaded source value, target set will be set on each row and target value will be added automatically. If there is no target value within the selected target set that matches the uploaded source value, target value needs to be selected manually.

It´s possible to edit a saved mapping, if for example in need of map to another value or clear a mapping. Click "Edit" to start editing. It´s possible to edit both "Target set"... ...and "Target value". Note that any changes made needs to be saved.

This feature enables BOP to map GLNs to and from configured internal id mapped values. Set up a mapped value for each party that needs a mapped value. Every mapped value must be unique. Once a mapped value has been saved, it can be changed the same day, but after that it is locked for one month. To unlock a mapped value, Btwentyfour Support must be contacted.

To clear all mappings in a set, start by clicking "Edit" for one mapping. Click then "Edit" for another mapping. A button for "Clear all" will appear above all "Clear" buttons. Click "Clear all" to remove all mappings in that set. All mappings will be cleared. Note that any changes needs to be saved.

A pop-up window appears saying there are unsaved changes. Click "Leave without saving" to go back to the tab of mappings without saving any changes. Click "Go back and keep editing" to go back to the set where editing was made.

A pop-up window appears saying changes was saved. Click "Go to mappings list" to go back to the tab of mappings. Click "Go back and keep editing" to go back to the set where editing was made.

PRICAT is the only message type available now and is selected by default. More message types to be added.

Not selectable now. "Inbound" selected by default.

The result of the message type and direction filtering will be shown under three different sections: * Mandatory mapping - Contains the mappings that needs to be done before being able to publish the products to a recipient. * Optional mapping - The optional mappings are data that can be mapped, but where there are no validations for any recipient forcing the supplier to map. * Completed mapping - An overview of all mappings made. For all three sections, information will be shown under the following table headers: * Set – The name of the set containing the values to be mapped. * Values – The values to be mapped. * Set owner – The owner of the set. This could either be Btwentyfour or a party. * Values to map/Mapped values – Shows how many values there is to be mapped for “Mandatory mapping” and “Optional mapping”, or how many values that have been mapped for “Completed mapping”.

When a message has been validated or published with validation errors regarding mapping due to requirements from either a receiving party or Btwentyfour, the values needed to be mapped will be listed under “Mandatory mapping”.

"Optional mappings" are data that can be mapped, but where there are no validations for any recipient forcing the supplier to map. These mappings will be listed under "Optional mappings". Completed mappings that are cleared and saved when editing will be moved to "Optional mapping". Regardless if it´s a property that requires mapping or not. When triggered from a validation error, such a property will be moved from "Optional mapping" to "Mandatory mapping".

All mappings made will be listed under "Completed mapping".

Indexes can be provided with media information in a master data file (PRICAT), and these indexes can be mapped in the portal towards Btwentyfour´s universal indexes. If using the "B24 universal Indexes" in a master data file (PRICAT), the indexes will be mapped automatically in the platform. Index mapping will contain no data to be mapped before any master data has been uploaded. Index values uploaded by a supplier in a master data file (PRICAT) will be listed chronological to the left in the list of indexes. When mapped, mapped indexes will be shown with a “B24 Index”. A description of the index mapping will also be shown for mapped indexes. It´s possible to filter media in the platform using the universal indexes. If a supplier is using our service for storage the images can also be downloaded by a supplier or a buyer from the result of these filtering´s.