Table 91 "User Setup"
Base Application · System.Security.User
Across versions
- BC23present
- BC241 fields added
- BC251 procedures added
- BC26unchanged
- BC271 procedures changed
- BC282 fields added
- BC29-30unchanged
Neighbourhood 65 connected objects and pages
Base Application · System.Security.User · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 119 “User Setup” (4 Learn pages), Page 663 “Approval User Setup” (2), Page 30095 “APIV2 - Approval User Setup” (2).
Properties
| Property | Value |
|---|---|
| Caption | User Setup |
| 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 | User ID | Code[50] | Specifies the ID of the user who posted the entry, to be used, for example, in the change log. via Page 119 “User Setup” | TableRelation User.“User Name”; NotBlank; DataClassification EndUserIdentifiableInformation |
| 2 | Allow Posting From | Date | Specifies the earliest date on which the user is allowed to post to the company. via Page 119 “User Setup” | |
| 3 | Allow Posting To | Date | Specifies the last date on which the user is allowed to post to the company. via Page 119 “User Setup” | |
| 4 | Register Time | Boolean | Specifies whether to register the user’s time usage defined as the time spent from when the user logs in to when the user logs out. Unexpected interruptions, such as idle session timeout, terminal server idle session timeout, or a client crash are not recorded. via Page 119 “User Setup” | |
| 5 | Allow Deferral Posting From | Date | Specifies the earliest date on which the user is allowed to post deferrals to the company. via Page 119 “User Setup” | |
| 6 | Allow Deferral Posting To | Date | Specifies the last date on which the user is allowed to post deferrals to the company. via Page 119 “User Setup” | |
| 10 | Salespers./Purch. Code | Code[20] | Specifies the code for the salesperson or purchaser for the user. via Page 119 “User Setup” | TableRelation Table 13 “Salesperson/Purchaser” (“Salesperson/Purchaser” where(Blocked = const(false))) |
| 11 | Approver ID | Code[50] | Specifies the user ID of the person who must approve records that are made by the user in the User ID field before the record can be released. via Page 663 “Approval User Setup” | TableRelation Table 91 “User Setup” (“User Setup”.“User ID”); DataClassification EndUserIdentifiableInformation |
| 12 | Sales Amount Approval Limit | Integer | Specifies the maximum amount in LCY that this user is allowed to approve for this record. via Page 663 “Approval User Setup” | |
| 13 | Purchase Amount Approval Limit | Integer | Specifies the maximum amount in LCY that this user is allowed to approve for this record. via Page 663 “Approval User Setup” | |
| 14 | Unlimited Sales Approval | Boolean | Specifies that the user on this line is allowed to approve sales records with no maximum amount. If you select this check box, then you cannot fill the Sales Amount Approval Limit field. via Page 663 “Approval User Setup” | |
| 15 | Unlimited Purchase Approval | Boolean | Specifies that the user on this line is allowed to approve purchase records with no maximum amount. If you select this check box, then you cannot fill the Purchase Amount Approval Limit field. via Page 663 “Approval User Setup” | |
| 16 | Substitute | Code[50] | Specifies the User ID of the user who acts as a substitute for the original approver. via Page 663 “Approval User Setup” | TableRelation Table 91 “User Setup” (“User Setup”.“User ID”); DataClassification EndUserIdentifiableInformation |
| 17 | Text[100] | Specifies the user’s email address. via Page 119 “User Setup” | ||
| 18 | Phone No. | text[30] | Specifies the user’s phone number. via Page 119 “User Setup” | |
| 19 | Request Amount Approval Limit | Integer | Specifies the maximum amount in LCY that this user is allowed to approve for this record. via Page 663 “Approval User Setup” | |
| 20 | Unlimited Request Approval | Boolean | Specifies that the user on this line can approve all purchase quotes regardless of their amount. If you select this check box, then you cannot fill the Request Amount Approval Limit field. via Page 663 “Approval User Setup” | |
| 21 | Approval Administrator | Boolean | Specifies the user who has rights to unblock approval workflows, for example, by delegating approval requests to new substitute approvers and deleting overdue approval requests. via Page 663 “Approval User Setup” | |
| 22 | Allow VAT Date From | Date | Specifies the earliest date on which the user is allowed to post VAT to the company books is allowed. via Page 119 “User Setup” | |
| 23 | Allow VAT Date To | Date | Specifies the last date on which the user is allowed to post VAT to the company books is allowed. via Page 119 “User Setup” | |
| 31 | License Type | Option | Specifies the user’s License Type. via Page 119 “User Setup” | FlowField: lookup(User.“License Type” where(“User Name” = field(“User ID”))); OptionCaption: Full User,Limited User,Device Only User,Windows Group,External User,External Administrator,External Accountant,Application,Microsoft Entra group |
| 80 | Sales Invoice Posting Policy | Enum “Invoice Posting Policy” | Specify if you want user who posts warehouse shipment, sales shipments, or inventory pick to be able to post invoice/credit-memo as well. via Page 119 “User Setup” | enum Enum 80 “Invoice Posting Policy” |
| 90 | Purch. Invoice Posting Policy | Enum “Invoice Posting Policy” | Specify if you want user who posts purchase receipt or inventory put-away to be able to post invoice/credit-memo as well. via Page 119 “User Setup” | enum Enum 80 “Invoice Posting Policy” |
| 950 | Time Sheet Admin. | Boolean | Specifies if a user is a time sheet administrator. A time sheet administrator can access any time sheet and then edit, change, or delete it. via Page 119 “User Setup” | |
| 5600 | Allow FA Posting From | Date | — | |
| 5601 | Allow FA Posting To | Date | — | |
| 5700 | Sales Resp. Ctr. Filter | Code[10] | Specifies the code for the responsibility center to which you want to assign the user. via Page 119 “User Setup” | TableRelation Table 5714 “Responsibility Center” (“Responsibility Center”.Code) |
| 5701 | Purchase Resp. Ctr. Filter | Code[10] | Specifies the code for the responsibility center to which you want to assign the user. via Page 119 “User Setup” | TableRelation Table 5714 “Responsibility Center” (Responsibility Center) |
| 5900 | Service Resp. Ctr. Filter | Code[10] | Specifies the code for the responsibility center you want to assign to the user. The user will only be able to see service documents for the responsibility center specified in the field. This responsibility center will also be the default responsibility center when the user creates new service docum… via Page 119 “User Setup” | TableRelation Table 5714 “Responsibility Center” (Responsibility Center) |
| 5980 | Service Invoice Posting Policy + BC24 | Enum “Invoice Posting Policy” | Specify if you want user who posts warehouse shipment or service shipments to be able to post invoice/credit-memo as well. via Page 119 “User Setup” | enum Enum 80 “Invoice Posting Policy” |
| 5991 | Allow Posting From DateFormula + BC28 | DateFormula | Specifies a date formula to calculate the earliest date, relative to today’s date, on which posting to the company books is allowed. via Page 119 “User Setup” | |
| 5992 | Allow Posting To DateFormula + BC28 | DateFormula | Specifies a date formula to calculate the latest date, relative to today’s date, on which posting to the company books is allowed. via Page 119 “User Setup” |
Keys
- Key1: User ID (clustered)
- Key2: Salespers./Purch. Code
Events published
OnBeforeEnsureUniqueSalesPersonPurchCode(var UserSetup: Record "User Setup"; var IsHandled: Boolean)(integration)OnBeforeValidateApprovalAdministrator(var UserSetup: Record "User Setup"; var IsHandled: Boolean)(integration)
Procedures
CreateApprovalUserSetup(User: Record User)GetDefaultSalesAmountApprovalLimit(): IntegerGetDefaultPurchaseAmountApprovalLimit(): IntegerHideExternalUsers()UpdateSalesPerson(FieldNumber: Integer)Δ BC27CheckAllowedVATDates(NotificationType: Option Error,Notification)CheckAllowedPostingDates(NotificationType: Option Error,Notification)CheckAllowedDeferralPostingDates(NotificationType: Option Error,Notification)
Plus 3 local procedures.
Triggers
OnDelete, OnInsert
Relations
- drill-down page Page 119 “User Setup”
- lookup page Page 119 “User Setup”
- Salespers./Purch. Code: TableRelation Table 13 “Salesperson/Purchaser”
- Purchase Resp. Ctr. Filter: TableRelation Table 5714 “Responsibility Center”
- Sales Resp. Ctr. Filter: TableRelation Table 5714 “Responsibility Center”
- Service Resp. Ctr. Filter: TableRelation Table 5714 “Responsibility Center”
- Approver ID: TableRelation Table 91 “User Setup”
- Substitute: TableRelation Table 91 “User Setup”
Referenced by
54 fields in 44 objects relate to this table (TableRelation or CalcFormula).
- Table 1523 “Workflow Step Argument”: Approver User ID, Notification User ID, Response User ID
- Table 1511 “Notification Entry”: Recipient User ID, Sender User ID
- Table 156 “Resource”: Time Sheet Approver User ID, Time Sheet Owner User ID
- Table 8010 “Imported Cust. Sub. Contract”: Assigned User ID, Processed by
- Table 91 “User Setup”: Approver ID, Substitute
- Table 950 “Time Sheet Header”: Approver User ID, Owner User ID
- Table 951 “Time Sheet Line”: Approved By, Approver ID
- Table 954 “Time Sheet Header Archive”: Approver User ID, Owner User ID
- Table 955 “Time Sheet Line Archive”: Approved By, Approver ID
- Table 1512 “Notification Setup”: User ID
- Table 1513 “Notification Schedule”: User ID
- Table 1541 “Workflow User Group Member”: User Name
- Table 167 “Job”: Project Manager
- Table 1804 “Approval Workflow Wizard”: Approver ID
- Table 20360 “Use Case Archival Log Entry”: User ID
- Table 20362 “Tax Type Archival Log Entry”: User ID
- Table 295 “Reminder Header”: Assigned User ID
- Table 302 “Finance Charge Memo Header”: Assigned User ID
- Table 36 “Sales Header”: Assigned User ID
- Table 38 “Purchase Header”: Assigned User ID
- Table 458 “Overdue Approval Entry”: Sent to ID
- Table 5107 “Sales Header Archive”: Assigned User ID
- Table 5109 “Purchase Header Archive”: Assigned User ID
- Table 5135 “Job Archive”: Project Manager
- Table 5405 “Production Order”: Assigned User ID
- Table 5740 “Transfer Header”: Assigned User ID
- Table 5900 “Service Header”: Assigned User ID
- Table 6010 “Service Header Archive”: Assigned User ID
- Table 6218 “Sustainability Scorecard”: Owner
- Table 6219 “Sustainability Goal”: Owner
- Table 6923 “Expense User”: User Id For Approvals
- Table 8008 “Imported Subscription Header”: Processed by
- Table 8009 “Imported Subscription Line”: Processed by
- Table 8022 “Contract Billing Err. Log”: Assigned User ID
- Table 8052 “Customer Subscription Contract”: Assigned User ID
- Table 8061 “Billing Line”: User ID
- Table 8063 “Vendor Subscription Contract”: Assigned User ID
- Table 8064 “Billing Line Archive”: User ID
- Table 8066 “Cust. Sub. Contract Deferral”: User ID
- Table 8072 “Vend. Sub. Contract Deferral”: User ID
- Table 8374 “Fin. Report Package Recipient”: User Email
- Table 900 “Assembly Header”: Assigned User ID
- Table 9059 “Administration Cue”: User Posting Period
- Table extension 6903 “User Setup Ext”: Interim Approver ID
Pages and codeunits on this table
- Page 119 “User Setup” (source table)
- Page 1825 “Time Sheet User Setup Subform” (source table)
- Page 30095 “APIV2 - Approval User Setup” (source table)
- Page 30436 “Approval Users” (source table)
- Page 663 “Approval User Setup” (source table)
- Page 9819 “User Setup FactBox” (source table)
Extended by
- Table extension 6210 “User Setup - TabExt”
- Table extension 6903 “User Setup Ext”
- Table extension 8012 “User Setup”
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 5700 “User Setup Management” (4 calls:
CheckAllowedDeferralPostingDates → CheckAllowedPostingDatesRange,CheckAllowedPostingDates → CheckAllowedPostingDatesRange,CheckAllowedPostingDates → GetDateRange, …) - Codeunit 457 “Environment Information” (1 call:
HideExternalUsers → IsSaaS) - Codeunit 9520 “Mail Management” (1 call:
SetEmailOnRecord → CheckValidEmailAddress)
Countries that replace it
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "User Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.