Node carrier applicability SLA data type (NCA)
The node carrier applicability SLA data type corresponds with the shipping carriers and the supported SLAs that are available for each node. This information is used to calculate shipping fulfillment network details.
Delta updates are supported for the Node carrier applicability SLA data type.
Prerequisites
- You must add the SLA Name by using the Service Level Agreement data type (SLA) feed.
- You must add the Carrier Name and Carrier Service Name by using the Shipping dimension weight factor data type (CMF) feed.
Using the Active and Upgrade fields
The Active field provides users with the capability to turn off a carrier service or an SLA for a carrier service at any node. The Upgrade field provides users with the capability to identify upgrade carrier services for an SLA.
| Action | Field value |
|---|---|
| Turn off a carrier service at a node. | Set the Active field to N for all the rows where the carrier service is mapped to the Node Key. |
| Turn off an SLA at a node. | Set the Active field to N for all the rows where the SLA is mapped to the Node Key. |
| Turn off an SLA for a specific carrier service at a specific node. | Set the Active field to N only for the rows where the SLA is mapped to the Node Key and carrier service. |
| Turn off a specific SLA for multiple carrier services at a node. | Set the Active field to N for all the rows where the SLA is mapped to the required carrier services and Node Key. |
| Mark a carrier service as an upgraded carrier service for an SLA. | Set the Upgrade field to Y for all the rows
where the carrier service is mapped to the SLA. Note: This setting indicates the shipment as
UPGRADED on the Optimization explainer UI, which only serves
reporting purposes and has no impact on optimization decisions.
|
File name and separator
This data type uses the comma (,) separator.
The recommended format for the file name is: NCA_[CUSTOMER NAME]_YYYYMMDDHHMISS.csv
Fields
| Field Name | Required | Type | Description |
|---|---|---|---|
| Node Key | Yes | STRING | The Node Key attribute corresponds to the node ID. The Node Key value must uniquely identify the node, such as a store or a distribution center. This value must match the Node key that is uploaded by using the Fulfillment network node data type (FN) feed. |
| Carrier Name | Yes | STRING | The Carrier Name is the name for a specific carrier. |
| Carrier Service | Yes | STRING | The Carrier Service attribute corresponds with the level of service each carrier provides. For example, FedEx 1 Day Shipping, FedEx 2 Day Shipping, and so on. |
| SLAName | Yes | STRING | The SLA Name must match the values in the SLA feed, for example:
|
| Active | Yes | STRING | Set to N to turn off a particular SLA and carrier for a node. The default value for the field is Y. |
| Upgrade | Yes | STRING | Set to Y to mark a carrier as an upgrade carrier for an SLA. The default value for the field is N. |
Sample for NCA_[CUSTOMER NAME]_YYYYMMDDHHMISS.csv
|
nodeId,carrierName,carrierServiceName,SLAName,Active,Upgrade 809,UPS,BWTI_UPS.UPS.NDA,1BUSDAY,Y,Y 809,UPS,BWTI_UPS.UPS.NDS,1BUSDAY,Y,N 809,UPS,BWTI_UPS.UPS.2DA,2BUSDAY,Y,Y 809,UPS,BWTI_UPS.UPS.GND,2BUSDAY,N,Y 809,UPS,BWTI_UPS.UPS.NDA,2BUSDAY,N,N |
Sample script to upload data by using the file adapter
/<Install_dir>//AsperaClientLinuxDist/asperaTransferClient.sh -jobname NCAPush
-contentType NCA -server -userid -password -op UPLOAD -src -dest/NCA
-conf /<Install_dir>//AsperaLinuxDist/asperaTransferOption.properties