Table 458 "Overdue Approval Entry"

Base Application · System.Automation · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 666 “Overdue Approval Entries” (1 Learn page).

Properties

Property	Value
Caption	Overdue Approval Entry
DataClassification	CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Table ID	Integer	Specifies the ID of the table where the record that is subject to approval is stored. via Page 666 “Overdue Approval Entries”
2	Document Type	Enum “Approval Document Type”	Specifies the type of document that an approval entry has been created for. Approval entries can be created for six different types of sales or purchase documents: via Page 666 “Overdue Approval Entries”	enum Enum 454 “Approval Document Type”
3	Document No.	Code[20]	Specifies the number of the document that was sent for approval. The number is copied from the relevant sales or purchase document, such as a purchase order or a sales quote. via Page 666 “Overdue Approval Entries”	TableRelation Table 36 “Sales Header”, Table 38 “Purchase Header” (if (“Table ID” = const(36)) “Sales Header”.“No.” where(“Document Type” = field(“Document Type”)) else if (“Table ID” = const(38)) “Purchase Header”.“No.” where(“Document Type” = field(“Document Type”)))
4	Sent to ID	Code[50]	Specifies the ID of the user who sent the mail notifying the approver that they has document approvals that are overdue. via Page 666 “Overdue Approval Entries”	TableRelation Table 91 “User Setup” (User Setup)
5	Sent Time	Time	Specifies the time when the overdue notification mail was sent to the approver who should approve the document. via Page 666 “Overdue Approval Entries”
6	Sent Date	Date	Specifies the date when the overdue notification mail was sent to the approver who should approve the document. via Page 666 “Overdue Approval Entries”
7	E-Mail	Text[100]	Specifies the email address of the user to whom the overdue notification was sent. via Page 666 “Overdue Approval Entries”
8	Sent to Name	Text[30]	—
9	Sequence No.	Integer	Specifies the order of approvers when an approval workflow involves more than one approver. via Page 666 “Overdue Approval Entries”
10	Due Date	Date	Specifies the date when the document is due for approval. via Page 666 “Overdue Approval Entries”
11	Approver ID	Code[50]	Specifies the ID of the user who must approve the document. via Page 666 “Overdue Approval Entries”	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
12	Approval Code	Code[20]	—
13	Approval Type	Enum “Workflow Approval Type”	—	enum Enum 458 “Workflow Approval Type”
14	Limit Type	Enum “Workflow Approval Limit Type”	—	enum Enum 457 “Workflow Approval Limit Type”
15	Record ID to Approve	RecordID	—

Keys

Key1: Table ID, Document Type, Document No., Sequence No., Sent Date, Sent Time, Record ID to Approve (clustered)
Key2: Approver ID

Events published

OnBeforeShowRecord(var OverdueApprovalEntry: Record "Overdue Approval Entry"; var IsHandled: Boolean) (integration)

Procedures

ShowRecord()

Triggers

OnDelete

Relations

Document No.: TableRelation Table 36 “Sales Header” (conditional)
Document No.: TableRelation Table 38 “Purchase Header” (conditional)
Sent to ID: TableRelation Table 91 “User Setup”

Pages and codeunits on this table

Page 666 “Overdue Approval Entries” (source table)

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Codeunit 700 “Page Management” (1 call: ShowRecord → PageRun)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Overdue Approval Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.