We set this up in 2005, and the same method works now with current WorldShip, DBA, and Win 7.  No external software is used.
 
First set up the ODBC database (Control Panel, ODBC...)
 
In UPS Worldship, create an export map like this:
 
Field Mappings:
 
     WorldShip Field (Container::Field)
           ODBC Data Source Field (Table::Field)
 
     Package::Tracking Number
           BKARDESC::BK_DESC_NOTES
     Shipment Information::Service Type
           BKARDESC::BK_DESC_NOTES
     Shipment Information::Void Indicator
           BKARDESC::BK_DESC_NOTES
     Shipment Information::Collection date
           BKARDESC::BK_DESC_NOTES
     Package::Reference 2
           BKARDESC::BK_DESC_NUM
 
Still in Worldship, set up Auto Export, Export after shipment processing for this export map.
 
When you enter a shipment, DBA SO number goes into UPS shipment reference field 2 (this could be changed in above map)
 
Result in DBA Classic notes looks like this:
1Z6566X90156041201  UPS  Next Day Air   20140618
 
I do have two problems that I'd really like resolved:
 
The Evo wiki ( https://evoerp.com/wiki/index.php?title=Evo/DBA_Shipping_information_to_UPS_%26_
pass_freight_%26_Tracking_number_back ) explains that the note should start with Tracking #.  I can't find a way to put text at the beginning of the exported note.
 
The note is only in DBA classic note form.  It can't be edited in Evo if you're using Evo Notes.  This is the only thing that makes us still have to use DBA classic.

The update released in June 2014 uses a field in the sales order header BKAR.INV.TRACK that is populated in SO-E and passes to the invoice header during invoice posting.  This field and the BKAR.INV.SHPVIA can be printed on any of the sames forms.  The Wiki instructions need to be updated to reflect this new location for the tracking information.

In thinking back to when we were setting this up I remember trying to use the BKAR.INV.TRACK field for my purpose but discovered that a major drawback of UPS Worldship is that it cannot update existing records, only append. This is why we had to use ISSOHBOX, a table we currently don't use for anything else. Worldship will export to this table fine I just have the problem of no readily available visibility.
 
I was digging through the other tables and stumbled across BKARRINV and it was clean and had a tracking # field so for the heck of it I linked Worldship to export the same info (as it exports to ISSOHBOX) to this table as well. Checking in Pervasive it is sending the information there as well so I tried to add the BKAR.INV.TRACK from BKARRINV to our invoice form (T6SOF3) but that didn't work either.
 
Thoughts? Our current method is working fine for exporting the tracking #s via EDI but our customer still calls looking for them sometimes (even though they are supposed to be in their system). I am just looking for a relatively simple way to provide our users some sort of easy visibility.
 
Any ideas?

Quote from Lynn_Pantic on 07/23/14 at 17:01:52:

 
If I'm understanding correctly, the update works to associate a Tracking Number with a Shipment, so that multiple shipments on a single SO get their own TN? We recently set up UPS Online Worldship to import address information, but hadn't done anything with exporting TNs back because of the Classic/Evo Notes situation. It appears that this new process doesn't use the Notes at all, but:
 
Quote from btaylor on 07/24/14 at 12:26:39:

 
I believe this is true. So, is the new process helpful to UOW importing? Or is it so far just an improvement for manually entered TNs?

Unposted invoices do not exist.  They are still Sales Orders at that point.  The information is in the SO Header and when the invoice is created by posting in SO-G it passed to the invoice.

It is cleared from the SO header after it is passed to the invoice.

We're not currently using Crossware, but would consider it if the desired results can be obtained. Definitely interested in hearing your experience.