
Environment
What happens
After running Process Data on an imported file:
| Field | Value |
|---|---|
| No. of Usage Data Blobs | 1 |
| No. of Imported Lines | 0 |
| No. of Imported Line Errors | 0 |
| Processing Step | Process Usage Data Billing |
| Processing Status | Error |
| Reason (Preview) | No data found for processing step Process Usage Data Billing. |
So the file is accepted (blob count = 1), but zero lines ever make it into the Usage Data Generic Import table, with zero line-level errors logged to explain why - and the pipeline only reports failure four steps later, at the billing stage, rather than where the data actually stops flowing (Create Imported Lines).
What I've already ruled out
Tested independently, with no change in outcome each time:
Every combination produces the identical result: 0 imported lines, 0 line errors, then "No data found" at the billing step.
Question
Since the file content and every format variable appear to be ruled out, has anyone seen this specific error and found what actually causes Create Imported Lines / Process Imported Lines to silently produce zero output? Is there a setting outside the Data Exchange Definition (e.g., on the Usage Data Supplier, the Subscription, or the Usage Data Supplier Reference) that's required for lines to actually populate table 8018?
Any working example file + Data Exchange Definition combo would be hugely appreciated.
Regards,