Configurational data types

Configurational data types are required at the time that the system is set up for the first time. After the system is set up, these data types must only be changed when a configuration changes.

Considerations

Consider the following points when you upload data for Configurational data types.

  • Configurational feeds must be loaded in the following sequence. The Fulfillment network feed must be the first data feed to be loaded.
    1. Fulfillment network node data type
    2. Service Level Agreement (SLA) data type
    3. Shipping dimension weight factor data type
    4. Node carrier applicability SLA data type
    5. Shipping rate card data type
    6. Shipping transit days data type
  • For the Service Level Agreement and Shipping dimension weight factor data types, unique identifiers are generated when the data is uploaded to the database.
  • When other dependent feeds (Node carrier applicability, Shipping rate card, and Shipping transit days) are uploaded, the unique identifiers that are generated for the Service Level Agreement and Shipping dimension weight factor data types are used as foreign key references between the data tables/collections.
  • It is recommended that for all Configurational data types, data must be maintained and uploaded with one data file. However, considering the large data volume, you can split the data into multiple files.

    For example, NCA data for the carrier UPS can be added by using one file and NCA data for the carrier FedEx can be added by using another file.

Example

In the following example, the corresponding Service Level Agreement and Shipping dimension weight factor data must be uploaded before the Node carrier applicability data is uploaded. Otherwise, the Node carrier applicability feed fails. Similarly, for Shipping rate card and Shipping transit days, the Shipping dimension weight factor data is a prerequisite.

If the Service Level Agreement feed is:

SLAName,SLADays

1BUSDAY,1

And the Shipping dimension weight factor feed is:

Carrier Name,Carrier Service,DM factors,Weight Limit,Transit Days

UPS,BWTI_UPS.UPS.NDA,194,150,

The Node carrier applicability feed is uploaded as:

NodeID,Carrier,ServiceName,SLAName

352,UPS,BWTI_UPS.UPS.NDA,1BUSDAY

Considerations for global postal code handling

Consider the following points when you upload data for Configurational data types and when using global postal codes. For more information, see Globalization.
  • Configurational feeds must be loaded in the following sequence. The Fulfillment network feed must be the first data feed to be loaded.
    1. Fulfillment network node data type
    2. Service Level Agreement (SLA) data type
    3. Add the Carrier Name and the Carrier Service Name by using the Set Carrier API and the Set Carrier Service API.
    4. Add zone definitions by using the Set Zone Definitions API.
    5. Map the Carrier Service to the required nodes and the supported SLAs by using the Node carrier applicability SLA data type (NCA).
    6. Add the Rate card for the carrier by using the Upload Transit Rates API.
    7. Add the Transit data for the carrier by using the Upload Transit Durations API.
  • It is recommended that for all Configurational data types, data must be maintained and uploaded with one data file. However, considering the large data volume, you can split the data into multiple files.

    For example, NCA data for the carrier UPS can be added by using one file and NCA data for the carrier FedEx can be added by using another file.