Date: 201706
Local time of day: 0601-1200
Location: STL.Tower, MO
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B STL
ATC / advisory: Tower STL
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Confusion; Training / Qualification
Second reporter function: Pilot Flying; Captain
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: At the gate we received a revised CPDLC clearance which I loaded from the Clearance page. We reviewed the new route on the Route page 2 and agreed it was correct. During the Before Push Checklist we noticed the runway was not on the takeoff reference page; it was there earlier because we reviewed the departure procedure during the brief. I then re-input the runway and reloaded the takeoff data and we completed the checklist. The taxi out and takeoff were uneventful.After takeoff in the initial climb; somewhere around 1000 ft AGL the Captain asked me to confirm we were on the correct departure path. We had confirmed LNAV and the FMA had the green LNAV; however; no magenta line was currently in view. As I was reviewing the chart and crosschecking the FMC data; ATC queried if we were headed to JAHNY or something similar. I believe I replied we were on the JAHNY Departure; and after some congestion on the radio we were given direct MAP and continued without incident. During my review of the chart and our FMC data it appeared HEFNR; DAFUS; and TRAVS were not there and the LNAV was navigating to JAHNY. I'm not sure what caused this.I'm still unsure of our error but assume we missed a crosscheck somewhere during the CPDLC reroute. A more thorough review may have caught the error.


Second narrative: On the ground; at the gate we received a CPDLC reroute. The FO loaded the reroute and we confirmed the route together on Route page 2 in the FMC. The new route was 110 miles greater than the original flight plan. I called Dispatch and received a new enroute burn and made the necessary amendment to the Release. The Dispatcher already planned the flight with extra fuel so additional fuel was not needed. During the Before Push Checklist; we noticed [dashed] lines where the runway should be. We stopped the checklist and re-entered the runway; N1's and Speeds and completed the Before Push Checklist. Taxi and takeoff were uneventful. After takeoff at approximately 400 ft I said confirm LNAV. LNAV was verified on the FMA and LNAV was green at this point and the FO said LNAV verified. The flight director commanded a right turn. LEGS page 1 was showing JAHNY as the next fix. I started the right turn and asked the FO to check the departure and as he was doing that ATC asked where we were going. The FO said we were on the JAHNY 3 Departure. ATC then cleared us direct MAPLES. At that point; I realized that HEFNR; DAFUS and TRAVS were not on JAHNY3 Departure we had in the FMC. When LNAV was selected we turned to JAHNY before ever reaching HEFNR. No TCAS or other safety issues were encountered.After receiving a CPDLC reroute make sure the runway and full departure are in the box. Make sure the runway connects to the SID.


Synopsis: B737 Flight Crew reported after a CPDLC reroute was loaded; no runway transition was selected and a track deviation occurred.