Standardized Reporting Fields
There is a long-term goal to get all clients Reporting fields Standardized so if a client is collecting a common reporting field we have a standard UDID # to utilize for that.
This will be an on-going effort to transition our existing clients into this new standardized format. We can work with our clients to prepare for this and then we can work with reporting and other affected areas to start transitioning clients to this format. You can view clients current reporting fields here.
Internal Name | Notes | |
1 |
| |
| ||
| ||
| ||
| ||
| ||
| ||
| ||
| ||
| ||
Unused | Reserved for additional client fields if needed | |
12 | Unused | Reserved for additional client fields if needed |
13 | Unused | Reserved for additional client fields if needed |
14 | Unused | Reserved for additional client fields if needed |
15 | Unused | Reserved for additional client fields if needed |
16 | Unused | Reserved for additional client fields if needed |
17 | Unused | Reserved for additional client fields if needed |
18 | Unused | Reserved for additional client fields if needed |
19 | Automatically done by Scripting (DO NOT ADD TO AIRPORTAL) | |
20 | Travel Arranger's Email | Used by clients who want arrangers to ONLY have visibility of trips they booked, using this email to match. |
| ||
DO NOT ADD TO AIRPORTAL, Open Jira ticket for GDS support | ||
| ||
Job/Event/Project- Name/# |
| |
If client doesn't have 14 day advance Purchase | ||
26 | If client doesn't purchase 7 days in advance can show them what they could have booked the trip at (price wise) | |
27 | Speedtype, Banner index#, RequestID, TR#, Authorization…etc. (approver name) | |
28 | Unused |
|
Agent manually overriding service fee saying "Charge this amount instead of the regular amount" for whatever reason | ||
30 | Humanitarian uses potentially accounting use (has $ amounts) | |
31 |
| |
| ||
Booked by- OBT Requested by- Agent (never using Agents name, always name of person at client making the booking on behalf of someone? | ||
34 | Puts the record locator if Diff. Ex. Inbound and outbound flights different PNR's (cross references PNR's) | |
35 | Independent Contractor Booking Overriding and putting in the IC's to get credit. | |
36 | Tonya can potentially remove from a UDID but being investigated | |
37 | Special logic around mapping with faces and needing dropdown values updated in faces PROFILE FIELD | |
38 | Run LOTS of reports needing to be in a UDID to run reports with Aggresso Data TRIP FIELD | |
39 | Unused |
|
Concur has a named field so must map at agency level | ||
41 | Explains WHY client took Higher fare | |
42 | Code saying I took a higher fare than was available | |
43 | Code saying I took a higher fare than was available | |
44 | Explains why client took higher fare | |
45 | We enter in remarks to know what we did in Afterhours to know what to charge | |
46 | Explains why client took higher fare | |
47 | A complex trip UDID where if there is a car segment it asks and determines whether or not to use direct bill | |
48 | Mid office script will | |
49 | The cost the travelers (Not business) is responsible for | |
50 | Do we still need HMHF values or consolidate options can we set it as "none" or does it have to be blank | |
51 | Something to do with Split tickets (Fare exceptions when more than one ticket issued) | |
52 | ||
NDC | Trip UDID that is for internal use only to inform us whether or not the Trip booked was booked on NDC content | |
IVR Keith takes it from PNR puts it in a UDID | ||
55 | Unused |
|
| ||
58 | Use for Non-Arc Tickets (no exchange info is picked up when done directly with an airline, used so we can upload to Ibank reporting and show what original ticket was | |
59 | Unique User identifier provided by client | |
60 | "Clientbase" is a system that is used by some clients that has 4 fields | |
61 | "Clientbase" is a system that is used by some clients that has 4 fields | |
62 | "Clientbase" is a system that is used by some clients that has 4 fields | |
63 | "Clientbase" is a system that is used by some clients that has 4 fields | |
64 | To show that this was ticketed in Compleat (used most for exchanges) | |
65 | Compleat adds value to UDID to let you know there is no AIR (something to do with Agresso) | |
66 | Category the group to either- University Group, University Event or AMI Group | |
67 | Specifically for AMI | |
68 | This is a unique identifier to identify the groups | |
69 | DO NOT ADD TO AP, open Jira ticket for GDS support | |
Penalty Fee | Needed for Prime analytics (we have it in PNR elsewhere but need in a UDID to pass into Prime) | |
Unused |
| |
Unused |
| |
Hotel 1 Public/BAR/Rack | Public/Bar/Rack rate for first hotel segment | |
Hotel 2 Public/BAR/Rack | Public/Bar/Rack rate for second hotel segment | |
Hotel 3 Public/BAR/Rack | Public/Bar/Rack rate for third hotel segment | |
Other description for Air | ||
77 | Other description for Car | |
78 | Other description for hotel | |
79 | Other description for Misc | |
80 | Unused |
|
Grand total for Air | ||
82 | Breakdown for Air | |
83 | Breakdown for air | |
84 | Grand total for car | |
85 | Breakdown for Car | |
86 | Grand total for Hotel | |
87 | Breakdown for hotel | |
88 | Breakdown for Misc. | |
89 | Grand total for ALL savings | |
90 | Company/Org/department/region/Division/Location/Cost Center (1) | floaters, can be used for any of these if original field is taken |
Company/Org/department/region/Division/Location/cost center (2) | floaters, can be used for any of these if original field is taken | |
Division | not using OBT "Org unit/Division" | |
Org | not using OBT "Org unit/Division" | |
Department | ||
Division/Org unit (OBT ONLY) | OBT specific and can only be used with Concur & Deem's Org unit/Division | |
| ||
| ||
|
| |
|