Supply Lens

Read a failed Document

Lesson 21 of 24 6 min read

When a Document stops, its status and logs tell you why. Learn to find the failing value quickly, and the tools that help you fix master data straight from the Document.

Sooner or later a Document will stop because something on it doesn't match your master data. The fix is usually quick; finding what to fix is the skill. This lesson gives you a routine for reading a failed Document, which the next two lessons apply to the two most common errors.

Statuses that matter here

  • PendingThe data has arrived and is waiting to be processed. Documents usually spend only a fraction of a second here.
  • ProcessingThe Document is being processed right now.
  • CompleteThe Document was processed successfully to at least one Mapping.
  • ReadyA matching Mapping is set to manual, so the Document is waiting for someone to process it.
  • FailedAn error was thrown during processing. The logs say why.

Master data problems show up as Failed.

A routine for any failed Document

  1. Open the Document from its list, for example Sales → Orders. Filter by status, or by document date, to find the failures.
  2. Look for missing green ticks. Each party and line that matched one of your records has a green tick. A missing tick shows you which party or line wasn't recognised.
  3. Read the Logs section. The error names the value that failed, such as the SKU, and often the line number.
  4. Decide where the fix belongs: in Supply Lens master data (a missing identifier, conversion or Party), or in another system (a product missing from your ERP's item master).
  5. Fix it, then reprocess the Document from its screen.

Tools that save time

  • Download CSV. Every log window has a Download CSV button that saves all entries at the severities you've ticked as a spreadsheet, up to 10,000 entries.
  • Logs for many items at once. On the Documents, Source data or Target data lists, select up to 100 rows and click Logs above the list to see all their entries together. Handy when a batch of orders fails overnight.
  • Click a green tick to jump to the Party, Location or Product a line matched, to check it matched the record you expected.
  • Compare two Documents. Where a Document refers to another (an invoice to its order), you can compare their lines side by side. If a line didn't match a Product, you can link its code to one so it matches next time.

Monday morning at Hilltop

Priya filters Sales → Orders to Failed and finds three Greenleaf orders from the weekend. She selects all three and clicks Logs. Two say no conversion could be found for a traded unit size of 12; one says a product code doesn't exist. Two different problems, and she knows exactly which lines to look at. The next two lessons follow her fixes.

Fix the cause, then reprocess in bulk

If the same value fails on many Documents, fix it once in your master data (or your item master), then reprocess all the affected Documents together.

Recap

  • Master data problems show up as Failed Documents.
  • Look for missing green ticks, then read the Logs to find the exact value that failed.
  • Decide whether the fix belongs in Supply Lens master data or in another system.
  • Use multi-row Logs and Download CSV to handle batches of failures.
  • Fix the cause once, then reprocess every affected Document.
Complete and continue

Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.

Add Locations and their identifiersFix: a product with this Id or code does not exist