tablePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table 7604 "Where Used Base Calendar"

Base Application · Microsoft.Foundation.Calendar

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-28unchanged
  4. BC295 fields changed
  5. BC30unchanged

Neighbourhood 1 connected objects and pages

Table 7600 "Base Calendar" (relates to)Base Calendar

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

Properties

Property Value
Caption Where Used Base Calendar
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 Source Type Δ BC29 Enum “Calendar Source Type” Specifies whether this customized calendar entry was set up for your company, a customer, vendor, location, shipping agent, or a service. enum Enum 7602 “Calendar Source Type”; not editable
2 Source Code Δ BC29 Code[20] Specifies the source identity of the business partner the customized calendar is set up for. not editable
3 Additional Source Code Δ BC29 Code[20] Specifies the code of the shipping agent service if the Source Type field contains Shipping Agent. not editable
4 Base Calendar Code Code[10] — TableRelation Table 7600 “Base Calendar” (Base Calendar)
5 Source Name Δ BC29 Text[50] Specifies the source name associated with this entry. not editable
6 Customized Changes Exist Δ BC29 Boolean Specifies that this entry has used the base calendar to create a customized calendar. not editable

Keys

  • Key1: Base Calendar Code, Source Type, Source Code, Source Name (clustered)

Relations

Countries that replace it

CZ

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: "Where Used Base Calendar"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources