pageSales & Receivablesofficial - Microsoftderived - from the source, no model text

Page 8071 "Vendor Contracts"

Subscription Billing · Microsoft.SubscriptionBilling

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 8 connected objects and pages

Table 8063 "Vendor Subscription Contract" (relates to)Vendor Subscription ContractTable 8063 "Vendor Subscription Contract" (pages and codeunits on it, 2 links)Vendor Subscription ContractPage 8070 "Vendor Contract" (pages and codeunits on it)Vendor ContractManaging contracts, subscriptions, and subscription lines (Learn pages)Managing contracts, subscrip…Posting documents (Learn pages)Posting documentsSubscription contract deferrals (Learn pages)Subscription contract deferr…Subscription contract renewal (Learn pages)Subscription contract renewalVendor subscription contracts (Learn pages)Vendor subscription contracts

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Subscription Billing · Microsoft.SubscriptionBilling · captioned “Vendor Subscription Contracts” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Vendor Subscription Contracts
SourceTable Vendor Subscription Contract
PageType List
UsageCategory Lists
ApplicationArea Basic, Suite

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Control1 No. No. Specifies the number of the involved entry or record, according to the specified number series.
Description DescriptionText Specifies the description of the Subscription Contract.
Buy-from Vendor No. Buy-from Vendor No. Specifies the name of the vendor who delivered the items.
Buy-from Vendor Name Buy-from Vendor Name Specifies the name of the vendor who delivered the items.
Contract Type Contract Type Specifies the classification of the contract.
Shortcut Dimension 1 Code Shortcut Dimension 1 Code Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window.
Shortcut Dimension 2 Code Shortcut Dimension 2 Code Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window.
Purchaser Code Purchaser Code Specifies which purchaser is assigned to the Vendor Subscription Contract.
Assigned User ID Assigned User ID Specifies the ID of the user who is responsible for the document.
Active Active Specifies whether the contract is active.
Your Reference Your Reference Specifies the vendor’s reference.
Exclude from Price Update DefaultExcludeFromPriceUpdate Specifies whether price updates are are allowed for that contract. Setting it to yes will exclude all contract lines from all price updates.

Actions

Group Action ToolTip Runs
Vendor Subscription Contract Create Contract Invoice The action creates a contract invoice for the current contract.
Dimensions View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.
Vendor Subscription Contract Deferrals Vendor Subscription Contract Deferrals. Page 8081 “Vendor Contract Deferrals”
Update Dimensions in Deferrals Updates the dimensions in all contract deferrals that have not yet been released for this contract.

Procedures

  • GetVendorContractSelection(): Text (internal)

Triggers

OnAfterGetRecord, OnOpenPage

Relations

Pages and codeunits on this table

Documented on Microsoft Learn

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). 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: "page", object_name: "Vendor Contracts"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 6 sources