Overview
This reference documents the structure of the SYSNOW data table 9outbu_sysnow_general_requests. It is intended to help administrators understand the fields stored by the related application/module. This article describes schema only and does not expose customer or operational record values.
How this table is used
The owning module reads and writes records in this table according to its workflow, permissions, and validation rules. Use the module interface for normal data entry; do not edit production rows directly unless following an approved maintenance procedure.
Field-by-field reference
The following fields were discovered from the database schema. “Significance” is an inferred guide based on the field name and type; verify business rules with the owning module before changing data.
| Field | Data type | Required / key | Significance |
|---|---|---|---|
id |
Number / Boolean bigint unsigned |
Required by schema; key: PRI | Unique identifier used to distinguish this record from other records. |
request_no |
Text / Choice varchar(32) |
Required by schema; key: UNI | Text value used to store this attribute for display, search, or application processing. Confirm the exact business meaning with the owning module. |
user_id |
Number / Boolean bigint unsigned |
Required by schema; key: MUL | Unique identifier used to distinguish this record from other records. |
requester_name |
Text / Choice varchar(190) |
Required by schema | Primary display name used to identify this item in lists and searches. |
requester_email |
Text / Choice varchar(190) |
Required by schema | Email address used for contact, notifications, or account identification. |
department |
Text / Choice varchar(190) |
Required by schema | Text value used to store this attribute for display, search, or application processing. Confirm the exact business meaning with the owning module. |
category |
Text / Choice varchar(80) |
Required by schema; key: MUL | Classification used to group, filter, and report on related records. |
priority |
Text / Choice varchar(20) |
Required by schema | Urgency or business importance used to help order work. |
required_date |
Date / Time date |
Optional by schema | Date/time value used to record when an event occurs or a validity period applies. |
location |
Text / Choice varchar(190) |
Required by schema | Text value used to store this attribute for display, search, or application processing. Confirm the exact business meaning with the owning module. |
subject |
Text / Choice varchar(255) |
Required by schema | Text value used to store this attribute for display, search, or application processing. Confirm the exact business meaning with the owning module. |
details |
Text / Choice longtext |
Required by schema | Text value used to store this attribute for display, search, or application processing. Confirm the exact business meaning with the owning module. |
status |
Text / Choice varchar(30) |
Required by schema; key: MUL | Current state of the record; commonly used to track progress or availability. |
admin_notes |
Text / Choice longtext |
Optional by schema | Additional context, observations, or handling details. |
created_at |
Date / Time datetime |
Required by schema | Timestamp showing when the record was created. |
updated_at |
Date / Time datetime |
Required by schema | Timestamp showing when the record was last updated. |
Access and safety
Restrict schema and database maintenance to authorized administrators. Back up the database before structural changes. Inferred field meanings are guidance, not a substitute for module source code or business-process documentation.