Table 456 "Posted Approval Entry"

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

Learn documents this table through its pages: Page 30093 “APIV2 - Pstd. Approval Entries” (2 Learn pages).

Properties

Property	Value
Caption	Posted Approval Entry
DataClassification	CustomerContent
LookupPageId	Posted Approval Entries
DrillDownPageId	Posted Approval Entries

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 659 “Posted Approval Entries”
3	Document No.	Code[20]	Specifies the document number copied from the relevant sales or purchase document, such as a purchase order or a sales quote. via Page 659 “Posted Approval Entries”
4	Sequence No.	Integer	Specifies the order of approvers when an approval workflow involves more than one approver. via Page 659 “Posted Approval Entries”
5	Approval Code	Code[20]	—
6	Sender ID	Code[50]	Specifies the ID of the user who sent the approval request for the document to be approved. via Page 659 “Posted Approval Entries”	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
7	Salespers./Purch. Code	Code[20]	Specifies the code for the salesperson or purchaser that was in the document to be approved. It is not a mandatory field, but is useful if a salesperson or a purchaser responsible for the customer/vendor needs to approve the document before it is sent. via Page 659 “Posted Approval Entries”
8	Approver ID	Code[50]	Specifies the ID of the user who must approve the document. via Page 659 “Posted Approval Entries”	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
9	Status	Enum “Approval Status”	Specifies the approval status for the entry: via Page 659 “Posted Approval Entries”	enum Enum 455 “Approval Status”
10	Date-Time Sent for Approval	DateTime	Specifies the date and the time that the document was sent for approval. via Page 659 “Posted Approval Entries”
11	Last Date-Time Modified	DateTime	Specifies the date when the approval entry was last modified. If, for example, the document approval is canceled, this field will be updated accordingly. via Page 659 “Posted Approval Entries”
12	Last Modified By ID	Code[50]	Specifies the ID of the person who last modified the approval entry. If, for example, the document approval is canceled, this field will be updated accordingly. via Page 659 “Posted Approval Entries”	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
13	Comment	Boolean	Specifies whether there are comments related to the approval of the document. If you want to read the comments, click the field to open the Comment Sheet window. via Page 659 “Posted Approval Entries”	FlowField: exist(“Posted Approval Comment Line” where(“Table ID” = field(“Table ID”), “Document No.” = field(“Document No.”), “Posted Record ID” = field(“Posted Record ID”))); not editable
14	Due Date	Date	Specifies the date when the document is due for approval by the approver. via Page 659 “Posted Approval Entries”
15	Amount	Decimal	—
16	Amount (LCY) Δ BC28	Decimal	Specifies the total amount (excl. VAT) on the document waiting for approval. The amount is stated in the local currency. via Page 659 “Posted Approval Entries”
17	Currency Code	Code[10]	Specifies the code of the currency of the amounts on the sales or purchase lines. via Page 659 “Posted Approval Entries”	TableRelation Table 4 “Currency”
18	Approval Type	Enum “Workflow Approval Type”	—	enum Enum 458 “Workflow Approval Type”
19	Limit Type	Enum “Workflow Approval Limit Type”	—	enum Enum 457 “Workflow Approval Limit Type”
20	Available Credit Limit (LCY) Δ BC27 Δ BC28	Decimal	—
22	Posted Record ID	RecordID	—
23	Delegation Date Formula	DateFormula	Specifies for the posted approval entry when an overdue approval request was automatically delegated to the relevant substitute. The field is filled with the value in the Delegate After field in the Workflow Responses window, translated to a date formula. The date of automatic delegation is then cal… via Page 659 “Posted Approval Entries”
26	Number of Approved Requests	Integer	—
27	Number of Rejected Requests	Integer	—
28	Iteration No.	Integer	Specifies the number of handling iterations that this approval request has reached. via Page 659 “Posted Approval Entries”
29	Entry No.	Integer	—	AutoIncrement
32	Approver Full Name + BC28	Text[80]	—	FlowField: lookup(User.“Full Name” where(“User Name” = field(“Approver ID”)))
33	Sender Full Name + BC28	Text[80]	—	FlowField: lookup(User.“Full Name” where(“User Name” = field(“Sender ID”)))
34	Salespers./Purch. Name + BC28	Text[80]	Salespers./Purch. Full Name caption	FlowField: lookup(“Salesperson/Purchaser”.Name where(“Code” = field(“Salespers./Purch. Code”)))

Keys

Key1: Entry No. (clustered)
Key2: Posted Record ID

Procedures

ShowRecord()

Triggers

OnDelete

Relations

drill-down page Page 659 “Posted Approval Entries”
lookup page Page 659 “Posted Approval Entries”
Salespers./Purch. Name: CalcFormula Table 13 “Salesperson/Purchaser”
Currency Code: TableRelation Table 4 “Currency”
Comment: CalcFormula Table 457 “Posted Approval Comment Line”

Pages and codeunits on this table

Page 30093 “APIV2 - Pstd. Approval Entries” (source table)
Page 659 “Posted 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: "Posted Approval Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.