Athena 101 · Lesson 05 · Turn scattered files into the team's report
Transcript
Transcript
In this lesson, you’ll turn six carrier files into the team’s weekly exceptions report, with every mismatch flagged.Your weekly exceptions report can fill itself in from the carrier files. Six carriers send invoices every week, each in its own layout. Ask for the report in Northwind’s own template, not a new spreadsheet. Say that each shipment gets one row, matched by its Shipment ID. Say what to check against the rate sheet, and to mark anything that doesn’t match. And ask how many rows came from each file, so you can check that nothing was dropped. The more rules you put in this first prompt, the less you fix later.Now the report fills in while you watch. Athena reads all eight files: the six invoices, the template, and the rate sheet. Then it opens your template as a sheet, and writes every shipment into the columns your team already uses. Each step names the cells it changed, so you can see where every row went. The Flag column marks the shipments the rate sheet can’t price.Before anyone uses the report, you can check that it’s complete. The answer lists how many rows came from each file. Compare those with what each carrier sent. Then go to the flagged rows. Click Scroll to cell, and the sheet shows you the Flag column. Each flag is a shipment the rate sheet can’t price. Some are real exceptions, and some are typos. Either way, a person decides.Now the report is ready to send, with your fixes in it. Row nine is a typo in the lane name. Fix it in the cell, and it saves on its own. Ask Athena to recheck that row, and the flag clears. Your edits and Athena’s sit in the same sheet, and every change is recorded. Format the money columns from the ribbon: Number, then Accounting number format. To share a file, open File, pick the XLSX download, and click Export. The sheet stays here as the working copy.Quick check. Why ask for row counts per file? So you can check nothing was dropped before anyone uses the report.Here’s how a logistics team uses this. Each carrier sends a different export every week. They point Athena at their existing report template, and the shipment number they match on. The rows land in the same columns as always, and the mismatches are flagged for a person to decide.Try it in your own workspace with this prompt. Look for an Updated card that names the range, a Flag column, and row counts in the answer.
Before you start
Upload these files from the Northwind starter kit: The carrier files in Northwind carrier files/wk 41, Northwind exceptions template.xlsx, and Northwind rate sheet.xlsx. A finished sheet is in Checkpoints/Lesson 05. Name the uploaded carrier folder Northwind carrier files (wk 41). Create the working sheet during the lesson; no connection or special admin setup is needed. You can work in a fresh chat if you have not made the lesson 04 Project.Steps
1
Ask for the report in your template
Mention the carrier files, template, and rate sheet. Ask for one row per shipment, matched by shipment ID, with unmatched shipments flagged and a count from each file.
2
Watch the template fill
Check that Athena fills the columns your team already uses. Read the update cards to see which cells changed.
3
Check completeness and exceptions
Compare the reported counts with the source files. Use Scroll to cell to review flagged shipments and decide which need correction.
4
Fix and export
Correct a typo, then ask Athena to recheck that row. Format the report, open File, and download an Excel copy while keeping the working sheet in Athena.
Try it
Combine these files into @[your template]. One row per shipment, matched by shipment ID. Flag rows that do not match @[reference sheet], and tell me how many rows came from each file.Look for an update card naming the changed cells, flagged rows, and counts from each file.