Overview
The Lyftron Provider for UPS offers the most natural way to access UPS data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing UPS data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s UPS data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
Key Features
- Comprehensive Delta load mechanism.
- Real-time access to UPS.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
Prerequisites
The user must have credentials for UPS, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your UPS connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click UPS for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish UPS connection with Lyftron.
"Server='https://wwwcie.ups.com/ups.app/xml';AccessKey='346DAC9059AF258';Password='zxczxqqtyiuowkdlkn';AccountNumber='11F0E7A';UserId='alsdkfjpqoewiru';
PrintLabelLocation='C:\users\username\documents\mylabels';CacheLocation='C:\users\username\documents\upscache';"
| Key | Value | Field |
| Connection Name | Enter your connection details | Required |
| Server | Enter server name | Required |
| AccessKey | Enter AccessKey | Required |
| Password | Enter Password | Required |
| AccountNumber | Enter AccountNumber | Required |
| UserId | Enter UserId | Required |
| Logfile** | Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx | Optional |
| Verbosity** | Choose verbosity 1-5 based on the severity of debugging | Optional |
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
Hurray! Now you have successfully connected with the Lyftron UPS connector and can utilize the connector to Extract, Warehouse, Analyze, Visualize and Share your data.
Data Model
You can work with all the tables in your account using the provider. The provider connects to UPS and gets the list of tables and the metadata for the tables by calling the appropriate Web services. Any changes you make to your Wasabi account, such as adding a new table, adding new columns, or changing the data type of a column, will immediately be reflected when you connect using the provider.
| Name | Type | Description |
| CommercialInvoices | Tables | Details of a commercial invoice to be included in a freight or international shipment. This table is initially empty and must be populated by user action. Stored Procedures may then retrieve this information as input via Id references. |
| Commodities | Tables | Details about a commodity item. This table is initially empty and must be populated by user action. Stored Procedures may then retrieve this information as input via Id references. Specification of at least one commodity item is required only for freight and international shipments. |
| LabelHistory | Tables | Stored details about generated labels for each shipped package. This table is populated by the GenerateLabels and GenerateReturnLabels stored procedures. Consequently, it is not possible to INSERT or UPDATE this table directly, but DELETE is still enabled. It should also be noted that the CancelShipment and CancelPackage stored procedures will remove records from this table. |
| Packages | Tables | Type and measures of a given package. This table is initially empty and must be populated by user action. Stored Procedures may then retrieve this information as input via Id references. All shipments will need at least one package specified for them. |
| Payors | Tables | Details of a payor for certain shipments. A Payor will only need to be defined if the shipment's PayorType is Recipient or Thirdparty. |
| Pickups | Tables | Details of scheduled Pickups from a sender's location. This table is populated by the SchedulePickups stored procedure. Consequently, it is not possible to INSERT or UPDATE this table directly, but DELETE is still enabled. It should also be noted that the CancelPickup stored procedure will remove records from this table. |
| RateHistory | Tables | Collection of calculated service rates. This table is populated by the CalculateRates stored procedure. Consequently, it is not possible to INSERT or UPDATE this table directly, but DELETE is still enabled. |
| Recipients | Tables | Contact and address details about known shipment recipients. This table is initially empty and must be populated by user action. Stored Procedures may then retrieve this information as input via Id references. All shipments will need a recipient specified for them. |
| Senders | Tables | Contact and address details about known shipment senders. This table is initially empty and must be populated by user action. Stored Procedures may then retrieve this information as input via Id references. All shipments will need a sender specified for them. |
| Shipments | Tables | Linked entity associations for a shipment. Every shipment will at least need a Sender, Recipient, and at least one Package. It will be from a specified ShipmentId that certain stored procedures (like GenerateLabels) will fetch needed input information from the other related tables, such as Senders, Recipients, and Packages. |
| TimeHistory | Tables | Collection of determined shipping time details. This table is populated by the GetShippingTime stored procedure. Consequently, it is not possible to INSERT or UPDATE this table directly, but DELETE is still enabled. |
| TrackHistory | Tables | Contains tracked events for a shipment's progress. This table is populated by the TrackShipment stored procedure. Consequently, it is not possible to INSERT or UPDATE this table directly, but DELETE is still enabled. |
Advanced Settings
To view a detailed advanced settings options, go to UPS Advanced Settings. Complete list of the parameters you can configure in the connection string can be found by clicking Connection String Parameters.