(GDS) Reporting
      Back to home
      1. Customer Support Knowledge Base
      2. GraspDATA
      3. (GDS) Reporting

      GDS Reporting (GraspDATA Ancillary Product)

      GraspDATA GDS reporting is an ancillary product. GDS feed is through a 3rd party, rather than back office data.

      If you do not currently have our GraspDATA (GDS) product and would like more information, please email the request to support@grasptech.com.

       

      The information below contains best practices when running (GDS) reports and general information about the data and fields that are available for (GDS) reporting. The (GDS) cycles are continuous throughout the day and night, versus the typical GraspDATA back office sync, which takes place overnight.  

       

      What do GraspDATA (GDS) Reports Include?

      • Bookings queued by agency to their 3rd party provider
      • Uses a separate data source for reporting via a 3rd party vendor
      • Current PNR data allowing you to see bookings as they appear in the GDS
      • GDS data is booked itineraries and will not show invoiced/ticketed/interfaced items
      • No accounting information – no ticket numbers, invoice #’s, invoice remarks, etc.
      • No stored PNR history.  GraspDATA will only show the most recent PNR queued
      • No Sort Information (Corporation Sorts)
      • Information is not comparable to back-office data
      • The report names, date fields, and filters contain (GDS) in the name

       

      (GDS) Reports
      The “Core” Arrival and Departure Manifests are updated versions of #1370 and #1371.
      Please note, if you don’t see that report #, search by REPORT NAME as the report # may be different  on your server.

      • #1362 Air Activity with Segments (GDS)
      • #1371 Arrival Manifest (GDS)
      • #1370 Departure Manifest (GDS)
      • #1367 Mini Itinerary Report (GDS)
      • #10276 Grasp Core Where Are My Travelers (GDS)
        • Report 10276 will show car and/or hotel data when using Date Field: On-the-road (GDS)
      • #10325 Grasp Core Arrival Manifest (GDS)
      • #10326 Grasp Core Departure Manifest (GDS)

       

      (GDS) Reporting Fields

      Do NOT use Issued Date, which is the default when running reports. You will want to use one of the Date Fields below.

      • Date Fields (Options tab) to use:
        • Booking Date
        • Departure Date
        • Segments Arriving or Departing Between (GDS) (Bookings)
        • Segment Depart Date (segments only)
        • Segment Arrive Date (segments only)
        • On-the-road (GDS)
          • Use On-the-road (GDS) to see car and/or hotel data on report (GDS) Grasp Core Where Are My Travelers

         
      • Date Filters (Filters tab) available to use:
        • Booking Agent (GDS)
        • Segment Arrive/Depart City (GDS)
        • Segment Arrive/Depart Region (GDS)
        • Segment Arrive/Depart State (GDS)
        • Segment Arrive/Depart Country (GDS) 
        • UDIDs (GDS)
        • Segment Arrival City
        • Segment Departure City

                 

      • Report Builder Tables for GDS (if applicable):
        • rb_GDSbookings
        • rb_GDSsegments
        • rb_GDSUDIDs

       

      Additional GDS Information 

      • Data Cafe is not applicable with GDS reporting, as that feature uses invoiced bookings.
      • Our system is based on the account table. If reservations are made, and that account does not exist in the back office, we will get the data, but it will not be associated to an account. The same is for vendor and agent information.
      • Third Party Vendors available for GDS Reporting with Grasp Technologies are Agency Technologies, Concur/GDSX, and Magnatech.
      • Each vendor offers a different feed, providing different field availability.
      • Unused ticket GDS reporting only available via Magnatech.