Troubleshooting
Problem
Information on Service Code indicators for UPS using YCS
Symptom
PART: Manifest 6.2 SP2 DCS
COMPONENT: YCS 2.0
Service Code
indicators for UPS how are they converted for UPNA and UP2A.
Cause
Resolving The Problem
We checked the service code (UPS calls it service type) of YCS/YCS
documentation with the UPS documentation. They matched correctly for both "UPS
Next Day Air Early AM" ("14") and "UPS 2nd Day Air AM" ("59"). But please note
that what gets generated on Tracking# is not "Service Type" but "Service Level
Indicator". "Service Level Indicator" is derived from "Service Type" and
additional Special Services. For "Service Type" "14" with no extra service,
"Service Level Indicator" is indeed "15". And YCS also generates it as "15".
And "59" with no extra services we generate it with "07".
This is how
DCS/YCS work.
DCS: In order download, you can download all the special
services in a record type called "ORDNAM" and it gets stored in
"ORD_REL_NAM_VALUE". When DCS has to generate a tracking # for a carton
(manifest client/wh132), it passes the special services to YCS.
YCS:
Mapping between YCS and UPS:
Service column in YCS_CARRIER_SERVICE maps
to "Service Type" of UPS.
SpecialServiceGroup in YCS_CARRIER_SPECIAL_SERVICE
maps to "Service Level Indicator" of UPS.
List of all Special Services for
the "Service Level Indicator" is stored in YCS_SPECIAL_SERVICE_GROUP table for
the SpecialServiceGroup in YCS_CARRIER_SPECIAL_SERVICE.
For the Service
Code passed, it loads all SpecialServiceGroup. From this list of
SpecialServiceGroups, it then determines the correct SpecialServiceGroup based
on the list of Special Services that the customer has requested. This
SpecialServiceGroup is what is printed in Tracking#.
Historical Number
PRI49297
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21531907