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

Table 8053 "Subscription Contract Type"

Subscription Billing · Microsoft.SubscriptionBilling

Across versions

  1. BC23-28not present
  2. BC29present
  3. BC30changed

Neighbourhood 10 connected objects and pages

Page 8054 "Contract Types" (pages and codeunits on it, 3 links)Contract TypesTable 8007 "Overdue Subscription Line" (referenced by)Overdue Subscription LineTable 8010 "Imported Cust. Sub. Contract" (referenced by)Imported Cust. Sub. ContractTable 8022 "Contract Billing Err. Log" (referenced by)Contract Billing Err. LogTable 8052 "Customer Subscription Contract" (referenced by)Customer Subscription ContractTable 8063 "Vendor Subscription Contract" (referenced by)Vendor Subscription ContractTable 8066 "Cust. Sub. Contract Deferral" (referenced by)Cust. Sub. Contract DeferralTable 8072 "Vend. Sub. Contract Deferral" (referenced by)Vend. Sub. Contract DeferralGeneral setup (Learn pages)General setupSubscription contract types (Learn pages)Subscription contract types

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 · BC29-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 8054 “Contract Types” (2 Learn pages).

Properties

Property Value
Caption Subscription Contract Type
DataClassification CustomerContent
LookupPageId Contract Types
DrillDownPageId Contract Types

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 Code Code[10] Specifies the unique code of the Subscription Contract Type. via Page 8054 “Contract Types” NotBlank
2 Description Text[50] Specifies a brief description of the type of contract. via Page 8054 “Contract Types”
3 HarmonizedBillingCustContracts Boolean Specifies that the contract elements of the Customer Subscription Contracts with this Subscription Contract Type are billed on a common key date. via Page 8054 “Contract Types”
4 Def. Without Contr. Deferrals Boolean Specifies the default value for the associated field in the contract. via Page 8054 “Contract Types” obsolete Pending 27.0; #if not CLEANSCHEMA30
5 Create Contract Deferrals Boolean Specifies the default value for the associated field in the contract. via Page 8054 “Contract Types”
6 Allow Diff. Curr. in Vend. UD Boolean Specifies whether vendor contracts of this type allow usage data with a currency different from the contract currency. If enabled, amounts will be automatically converted to the vendor contract currency when creating usage data billing. If disabled, an error will be raised when the usage data curren…
7 Allow Diff. Curr. in Cust. UD Boolean Specifies whether customer contracts of this type allow usage data with a currency different from the contract currency. If enabled, amounts will be automatically converted to the customer contract currency when creating usage data billing. If disabled, an error will be raised when the usage data cu…

Keys

  • PK: Code (clustered)

Procedures

  • CustomerContractsExist(): Boolean
  • VendorContractsExist(): Boolean
  • GetDescription(ContractTypeCode: Code[10]): Text[50] (internal)

Plus 3 local procedures.

Triggers

OnDelete

Relations

Referenced by

7 fields in 7 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

Recent changes

Deprecations

  • field Def. Without Contr. Deferrals: Pending 27.0 (#if not CLEANSCHEMA30), “Removed in favor of Create Contract Deferrals.”

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: "table", object_name: "Subscription Contract Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources