tableInventoryofficial - Microsoftderived - from the source, no model text

Table 5804 "Avg. Cost Adjmt. Entry Point"

Base Application · Microsoft.Inventory.Costing

Across versions

  1. BC23present
  2. BC241 events added, 1 events removed
  3. BC25unchanged
  4. BC261 procedures added
  5. BC27unchanged
  6. BC285 fields changed
  7. BC29-30unchanged

Neighbourhood 8 connected objects and pages

Table 14 "Location" (relates to)LocationTable 27 "Item" (relates to)ItemTable 5401 "Item Variant" (relates to)Item VariantPage 5815 "Avg. Cost Adjmt. Entry Points" (pages and codeunits on it, 2 links)Avg. Cost Adjmt. Entry PointsCodeunit 5823 "Cost Adjustment Item Runner" (calls, 2 links)Cost Adjustment Item RunnerCodeunit 360 "Accounting Period Mgt." (calls)Accounting Period Mgt.Codeunit 362 "PeriodPageManagement" (calls)PeriodPageManagementCodeunit 5824 "Cost Adjustment Params Mgt." (calls)Cost Adjustment Params Mgt.

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

Properties

Property Value
Caption Avg. Cost Adjmt. Entry Point
DataClassification CustomerContent
LookupPageId Avg. Cost Adjmt. Entry Points

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 Item No. Δ BC28 Code[20] Specifies the item number. TableRelation Table 27 “Item”
2 Variant Code Δ BC28 Code[10] Specifies the variant code. TableRelation Table 5401 “Item Variant” (“Item Variant”.Code where(“Item No.” = field(“Item No.”)))
3 Location Code Δ BC28 Code[10] Specifies the location code. TableRelation Table 14 “Location”
4 Valuation Date Δ BC28 Date Specifies the valuation date from which the entry is included in the average cost calculation.
5 Cost Is Adjusted Δ BC28 Boolean Specifies whether the cost is adjusted on the valuation date

Keys

  • Key1: Item No., Variant Code, Location Code, Valuation Date (clustered)
  • Key2: Item No., Cost Is Adjusted, Valuation Date

Events published

  • OnAfterSetAvgCostAjmtFilter(var AvgCostAdjmtEntryPoint: Record "Avg. Cost Adjmt. Entry Point") (integration)
  • OnValuationExistsOnAfterGetItem(var Item: Record Item; ValueEntry: Record "Value Entry"; var AvgCostAdjmtEntryPoint: Record "Avg. Cost Adjmt. Entry Point") + BC24 − BC24 (integration)

Procedures

  • ValuationExists(ValueEntry: Record "Value Entry"): Boolean
  • PrevValuationAdjusted(ValueEntry: Record "Value Entry"): Boolean
  • UpdateValuationDate(ValueEntry: Record "Value Entry")
  • AvgCostCalcTypeIsChanged(FromDate: Date): Boolean
  • GetAvgCostCalcTypeIsChgPeriod(var NextFiscalYearAccPeriod: Record "Accounting Period"; FromDate: Date)
  • GetValuationPeriod(var CalendarPeriod: Record Date)
  • IsAvgCostCalcTypeItem(ValuationDate: Date): Boolean
  • SetAvgCostAjmtFilter(var AvgCostAdjmtEntryPoint: Record "Avg. Cost Adjmt. Entry Point")
  • RunCostAdjustmentUntilValuationDate() + BC26

Plus 4 local procedures.

Triggers

OnDelete, OnInsert, OnModify

Relations

Pages and codeunits on this table

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.

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: "Avg. Cost Adjmt. Entry Point"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources