tableInventoryofficial - Microsoftderived - from the source, no model text

Table 5430 "Planning Error Log"

Base Application · Microsoft.Inventory.Planning

Across versions

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

Neighbourhood 12 connected objects and pages

Table 244 "Req. Wksh. Template" (relates to)Req. Wksh. TemplateTable 245 "Requisition Wksh. Name" (relates to)Requisition Wksh. NameTable 27 "Item" (relates to)ItemPage 5430 "Planning Error Log" (pages and codeunits on it, 3 links)Planning Error LogCodeunit 99000861 "Mfg. Planning Integration" (event subscribers)Mfg. Planning IntegrationPage 26 "Vendor Card" (calls)Vendor CardPage 30 "Item Card" (calls)Item CardPage 456 "No. Series" (calls)No. SeriesPage 5 "Currencies" (calls)CurrenciesPage 5700 "Stockkeeping Unit Card" (calls)Stockkeeping Unit CardPage 5747 "Transfer Routes" (calls)Transfer RoutesAbout planning functionality (Learn pages)About planning functionality

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

Learn documents this table through its pages: Page 5430 “Planning Error Log” (1 Learn page).

Properties

Property Value
Caption Planning Error Log
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 Worksheet Template Name Code[10] — TableRelation Table 244 “Req. Wksh. Template” (Req. Wksh. Template)
2 Journal Batch Name Code[10] — TableRelation Table 245 “Requisition Wksh. Name” (“Requisition Wksh. Name”.Name where(“Worksheet Template Name” = field(“Worksheet Template Name”)))
3 Entry No. Integer —
4 Item No. Δ BC28 Code[20] Specifies the item number associated with this entry. TableRelation Table 27 “Item”
5 Error Description Δ BC28 Text[250] Specifies the description to the error in this entry.
6 Table ID Integer — TableRelation AllObjWithCaption.“Object ID” where(“Object Type” = const(Table))
7 Table Position Text[250] —

Keys

  • Key1: Worksheet Template Name, Journal Batch Name, Entry No. (clustered)

Events published

Procedures

  • Caption(): Text
  • SetJnlBatch(WkshTemplName: Code[10]; JnlBatchName: Code[10]; ItemNo: Code[20])
  • SetError(TheError: Text[250]; TheTableID: Integer; TheTablePosition: Text[250])
  • GetError(var PlanningErrorLog: Record "Planning Error Log"): Boolean
  • GetErrors(var PlanningErrorLog: Record "Planning Error Log"): Boolean + BC28: Gets all planning errors and inserts them into the provided record.
  • ShowError()

Plus 1 local procedures.

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: "Planning Error Log"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources