tableInventoryofficial - Microsoftderived - from the source, no model text

Table 7156 "Item Analysis View Budg. Entry"

Base Application · Microsoft.Inventory.Analysis

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC2810 fields changed
  5. BC29-30unchanged

Neighbourhood 8 connected objects and pages

Table 27 "Item" (relates to, 2 links)ItemTable 14 "Location" (relates to)LocationTable 18 "Customer" (relates to)CustomerTable 23 "Vendor" (relates to)VendorTable 7132 "Item Budget Name" (relates to)Item Budget NameTable 7152 "Item Analysis View" (relates to)Item Analysis ViewPage 7154 "Item Analy. View Budg. Entries" (pages and codeunits on it, 3 links)Item Analy. View Budg. EntriesTable 5821 "Item Statistics Buffer" (referenced by, 3 links)Item Statistics Buffer

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.

Base Application · Microsoft.Inventory.Analysis · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Item Analysis View Budg. Entry
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 Analysis Area Enum “Analysis Area Type” — enum Enum 7130 “Analysis Area Type”
2 Analysis View Code Code[10] — TableRelation Table 7152 “Item Analysis View” (“Item Analysis View”.Code where(“Analysis Area” = field(“Analysis Area”), Code = field(“Analysis View Code”))); NotBlank
3 Budget Name Δ BC28 Code[10] Specifies the name of the budget that the analysis view budget entries are linked to. TableRelation Table 7132 “Item Budget Name” (“Item Budget Name”.Name where(“Analysis Area” = field(“Analysis Area”)))
4 Item No. Δ BC28 Code[20] Specifies the number of the item that the analysis view budget entry is linked to. TableRelation Table 27 “Item”
5 Source Type Enum “Analysis Source Type” — enum Enum 7131 “Analysis Source Type”
6 Source No. Code[20] — TableRelation Table 18 “Customer”, Table 23 “Vendor”, Table 27 “Item” (if (“Source Type” = const(Customer)) Customer else if (“Source Type” = const(Vendor)) Vendor else if (“Source Type” = const(Item)) Item)
8 Location Code Δ BC28 Code[10] Specifies the code of the location to which the analysis view budget entry was posted. TableRelation Table 14 “Location”
9 Dimension 1 Value Code Δ BC28 Code[20] Specifies the dimension value you selected for the analysis view dimension that you defined as Dimension 1 on the analysis view card.
10 Dimension 2 Value Code Δ BC28 Code[20] Specifies which dimension value you have selected for the analysis view dimension that you defined as Dimension 2 on the analysis view card.
11 Dimension 3 Value Code Δ BC28 Code[20] Specifies which dimension value you have selected for the analysis view dimension that you defined as Dimension 1 on the analysis view card.
12 Posting Date Δ BC28 Date Specifies the date on which the item budget entries in an analysis view budget entry were posted.
13 Entry No. Integer —
21 Quantity Δ BC28 Decimal Specifies the item budget entry quantity included in an analysis view budget entry.
22 Sales Amount Δ BC28 Decimal Specifies the item budget entry sales amount included in an analysis view budget entry.
23 Cost Amount Δ BC28 Decimal Specifies the item budget entry cost amount included in an analysis view budget entry.

Keys

  • Key1: Analysis Area, Analysis View Code, Budget Name, Item No., Source Type, Source No., Dimension 1 Value Code, Dimension 2 Value Code, Dimension 3 Value Code, Location Code, Posting Date, Entry No. (clustered)

Procedures

  • GetCaptionClass(AnalysisViewDimType: Integer): Text[250]

Relations

Referenced by

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

Pages and codeunits on this table

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: "Item Analysis View Budg. Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources