Building the OneStream Job Key with BRIDGE

BRIDGE inserts a new OneStream Job Key column into a JDE Job Extract workbook so it can be matched or VLOOKUP'd against the OneStream WIP export (OPUJOB_RPT_01), which identifies jobs with one packed string instead of separate columns.

What it expects

Drag the daily MRSG Job Extract .xlsx onto the dropzone, or click to browse. BRIDGE checks the first sheet's header row for Company, Job Number, and Job Name — if any of those three are missing, it rejects the file with a message naming which ones weren't found, rather than guessing at column positions. The upload limit is 50 MB.

What it does

Click Build Key Column. BRIDGE inserts a new Column A, OneStream Job Key, ahead of Company, built as:

E<Company>_<sanitized Job Number> - <Job Name, first 30 characters>

The result downloads as <original name> - Bridged.xlsx. Like SLICE, the file is processed on BENCH's server in memory and is never saved there — the download response is the only copy that exists once the request completes.

Flagged Job Numbers

If a row's Job Number contains a character the key formula hasn't been verified against in a real Job Extract/WIP comparison, that row is listed in a warning after the download finishes — worth a quick check that the key still lines up with the WIP for those rows. Everything else is keyed the same way regardless of the flag; it's a heads-up, not an error.