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

Codeunit 283 "Cross-Company No. Series"

Business Foundation · Microsoft.Foundation.NoSeries

Across versions

  1. BC23not present
  2. BC24added
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 284 "Cross-Company No. Series Impl." (calls, 3 links)Cross-Company No. Series Impl.Table 1262 "Isolated Certificate" (calls, 3 links)Isolated Certificate

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.

Business Foundation · Microsoft.Foundation.NoSeries · BC24-30 · source at ea08af5e · facts from BC29

Procedures

  • CreateNoSeries(NoSeriesCode: Code[10]; NoSeriesDescription: Text[50]; LastUsedNo: Code[10]): Creates a new cross-company No. Series
  • GetNextNo(NoSeriesTenant: Record "No. Series Tenant"): Code[20]: Gets the next available number for the given cross-company No. Series
  • GetNextNo(NoSeriesCode: Code[10]): Code[20]: Gets the next available number for the given cross-company No. Series
  • Exists(NoSeriesCode: Code[10]): Boolean: Checks if the given cross-company No. Series exists

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.

Called by

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: "codeunit", object_name: "Cross-Company No. Series"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources