CData BizTalk Adapter for FedEx 2019 - Online Help
Questions / Feedback?

Working with FedEx

CData BizTalk Adapter for FedEx 2019 - Build 19.0.7354

The primary functionality of the CData BizTalk Adapter for FedEx 2019 lies in its stored procedures, which interact directly with the available services for FedEx. However, many of these stored procedures rely on information stored in the provider's tables. These tables must be populated by the user and will contain all of the information that certain stored procedures will need. Among the most important stored procedures that will rely on these tables are CalculateRates, GenerateLabels, GenerateReturnLabels, and SchedulePickup. Among the tables that the stored procedures will rely on are Senders, Recipients, Packages, and Shipments. See the queries below for an example of some basic preparation needed for use of the GenerateLabels stored procedure:

INSERT INTO Senders (SenderId, FirstName, LastName, Phone, Address1, City, State, ZipCode, CountryCode) VALUES (1, 'John', 'Doe', '336-773-0111', '101 Some Street Dr', 'Chapel Hill', 'NC', '27517', 'US')
INSERT INTO Recipients (RecipientId, FirstName, LastName, Phone, Address1, City, State, ZipCode, CountryCode) VALUES (1, 'Jane', 'Doe', '336-111-0377', '343 Bad Traffic Rd', 'Raleigh', 'NC', '27609', 'US')
INSERT INTO Packages (PackageId, Weight, Length, Width, Height) VALUES (1, 34.3, 48, 24, 12)
INSERT INTO Packages (PackageId, Weight, Length, Width, Height) VALUES (2, 13.37, 24, 24, 24)
INSERT INTO Shipments (ShipmentId, SenderId, RecipientId, PackagingType, PackageId) VALUES (1, 1, 1, 'YOURPACKAGING', '1,2')

Once the needed input data is present, one can execute a stored procedure like GenerateLabels by running an Execute statement. The example below will use the data provided in earlier insert examples:

EXECUTE GenerateLabels ServiceType = 'FedEx_Ground', ShipmentId = 1

In addition to the input tables are tables that will accumulate the output of subsequent runs of a stored procedure. Among these tables are LabelHistory, RateHistory, and TrackHistory. A user may query these tables at any time to review the contents of successful stored procedures. Additionally, a user may join them with related a input table such as Recipients or Packages.

All of the tables will be stored in an underlying database in the local machine. The database's exact location will be determined by the CacheConnection connection property. For more information on all of the available tables, stored procedures, and the relationships between them, see the Data Model.

 
 
Copyright (c) 2020 CData Software, Inc. - All rights reserved.
Build 19.0.7354.0