anyone know why Department (header level) might be blank on the RA record if it's populated on the related source record/SO (header level)?

Is the field mapped in Revenue Recognition Field Mapping?

only line fields are supported for the target RA for mapping

Sorry, I missed that it was header. Did the source record Department field get updated after the RA was generated? It should be comparable in the System Notes. If so, there isn't a native update to re-sync the header fields that I've seen.

check the source transaction, does it have Dept populated at the header level?

yup, header dept is populated and it is mandatory at creation. also no changes to that field in system notes

natively the field must be populated from the source transaction. something happened in between. check the WFs, scripts, etc.

If there are merged arrangements, I believe the standard behavior is that the Department on the main line is cleared due to multiple source transactions. Are these merged arrangements?

@Karina i figured as much... crying

thank you for sharing this @SuiteReg. I have not ever heard that transactional values convert into header values…. this is very odd and I would confirm it with someone else

Good to know that those mainline segment fields on RAs are completely unreliable. 🫣 Did you have anything in your processes or reports that rely on the mainline Department?

NetSuite support came back and confirmed the same yesterday evening (i hadn't shared my findings with them since i continued testing after i opened the ticket): As per SuiteAnswersID: 49236 | Viewing Revenue Arrangements, the values for Classification section such as Department, Class, and Location are derived from the source documents. Also, these fields are populated in the header only when all revenue elements in the arrangement share the same value.