Date Fields of SC_REQUEST TABLE

priyanka1028
Tera Contributor

‎10-06-2024 11:28 AM - edited ‎10-06-2024 09:59 PM

Hi all,

 

I need a description and the logic of how the fields in the SC_REQUEST table are populated.

If anyone has any insights, please provide an answer. Thank you!

 

Fields: 

opened_at
sys_created_on
expected_start
work_start
due_date
work_end
closed_at
business_duration
activity_due
calendar_duration
calendar_stc
follow_up
made_sla
requested_date
time_worked
0 Helpfuls
  • 755 Views
1 REPLY 1

Community Alums
Not applicable

‎10-06-2024 11:35 AM

Hi @priyanka1028 

 

  • opened_at: The date and time when the request was created.

    • Population: Automatically populated when a new request is created, typically by the system at the moment the request form is submitted.

  • sys_created_on: The timestamp for when the record was created.

    • Population: Automatically set by the system when the record is inserted into the database.

  • expected_start:The anticipated start date and time for the request.

    • Population: This can be set manually by the user or automatically by business rules or workflows depending on service-level agreements (SLAs) or other criteria.

  • work_start:The actual start date and time of work on the request.

    • Population: Usually populated by workflow actions or scripts when work on the request officially begins.

  • due_date:The date and time by which the request should be completed.

    • Population: Can be automatically set based on SLAs or service agreements, often calculated from the expected_start.

  • work_end:The date and time when work on the request is completed.

    • Population: Populated when the request is closed or marked complete.

  • closed_at:The date and time when the request was closed.

    • Population: Automatically populated when the request status changes to "Closed" or "Resolved."

  • business_duration:The total business time taken to fulfill the request.

    • Population: Automatically calculated based on the work start and work end times, factoring in business hours and any applicable holidays.

  • activity_due:The deadline for related activities within the request.

    • Population: Can be set manually or automatically based on workflows and task dependencies.

  • calendar_duration:The total elapsed time for the request, regardless of business hours.

    • Population: Calculated based on the difference between the work start and work end timestamps.

  • calendar_stc:Represents the calendar time taken, potentially including specific scheduling conditions.

    • Population: Can be calculated similarly to calendar_duration, but might involve additional business logic or conditions.

  • follow_up: Indicates if a follow-up action is required for the request.

    • Population: Typically set by users or workflows depending on the nature of the request.

  • made_sla:A boolean field indicating whether the request was completed within the SLA.

    • Population: Automatically set based on the comparison between the due date and the closed date.

  • requested_date:The date and time when the request was initiated.

    • Population: Similar to opened_at, usually set when the request is created.

  • time_worked:The total time spent working on the request.

    • Population: Often populated by tracking work hours entered by users or calculated from the work start and end times.

Please mark it helpful, if it helps.