Table extension 8052 "Item"

Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29

Extends Item.

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
8052	Subscription Option	Enum “Item Service Commitment Type”	Specifies whether or not Subscription Lines can be linked to this item, or if the item is being used for recurring billing. This is only relevant if you are using Subscription Billing functionalities. via Page extension 8054 “Item Card”	enum Enum 8056 “Item Service Commitment Type”; DataClassification CustomerContent
8020	Usage Data Suppl. Ref. Exists	Boolean	Specifies that at least one usage data supplier reference exists for the item. This is only relevant if you are using Subscription Billing functionalities. via Page extension 8054 “Item Card”	FlowField: exist(“Item Vendor” where(“Item No.” = field(“No.”), “Supplier Ref. Entry No.” = filter(<> 0))); not editable

Events published

OnBeforeErrorIfServiceCommitmentOptionIsNotValidForServiceCommitmentPackage(Rec: Record Item; var IsHandled: Boolean) (integration)

Procedures

OpenItemServCommitmentPackagesPage() (internal)
IsServiceCommitmentItem(): Boolean (internal)
GetDoNotAllowInvoiceDiscountForServiceCommitmentItemErrorText(): Text (internal)
HasSNSpecificItemTracking(): Boolean

Plus 6 local procedures.

Relations

extends Table 27 “Item”
Usage Data Suppl. Ref. Exists: CalcFormula Table 99 “Item Vendor”

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