Clarification on Origin and Origin Table fields in Incident records

[Saurav_Kumar]

I’d like clarification on the Origin and Origin Table fields:

• What is their intended purpose in the Incident table?
• How are they populated (manually, via integrations, or system processes)?
• Are they primarily used for tracking where the incident was created and how do organizations leverage them in reporting or workflows?

Any insights, best practices, or examples of how these fields are used in real-world implementations would be very helpful.

Thanks

Saurav Kumar

[Shashank_Jain]

Hello @Saurav_Kumar ,

origin_table – Generally exists on Incident but has no default usage or system logic in out‑of‑the‑box Incident processes unless you customize it.

origin_id – Also present but not used by standard Incident logic by default.

These fields are schema fields available for integrations or custom use, but ServiceNow does not automatically populate them unless a business rule/flow sets them.

[Shashank_Jain]

@Saurav_Kumar ,

Check out this community post:
https://www.servicenow.com/community/itsm-forum/can-someone-please-explain-the-meaning-behind-the-fo...
There are some fields listed with their usecase. It might be helpful for you.

[RahelaM]

Please note that origin_id and origin_table are important for the following property within SOW Configurations: Close Interaction when linked Incident is resolved [sn_sow_inc.autoclose_origin.interaction]. The auto closure of interaction record is handled by a Business Rule "Close interaction from incident". If you take a look at the script, the interaction to be closed is fetched based on the originId.