codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 5469 "Library API - General Journal"

Base Application · Microsoft.Finance.GeneralLedger.Journal

Across versions

  1. BC23-30present

Neighbourhood 7 connected objects and pages

Page 20049 "APIV1 - JournalLines" (calls, 2 links)APIV1 - JournalLinesPage 20058 "APIV1 - Customer Payments" (calls, 2 links)APIV1 - Customer PaymentsPage 30055 "APIV2 - Customer Payments" (calls, 2 links)APIV2 - Customer PaymentsPage 30060 "APIV2 - Vendor Payments" (calls, 2 links)APIV2 - Vendor PaymentsCodeunit 230 "GenJnlManagement" (calls)GenJnlManagementCodeunit 308 "No. Series - Batch" (calls)No. Series - BatchPage 30049 "APIV2 - JournalLines" (calls)APIV2 - JournalLines

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

Procedures

  • InitializeLine(var GenJournalLine: Record "Gen. Journal Line"; LineNo: Integer; DocumentNo: Code[20]; ExternalDocumentNo: Code[35]): Initializes a general journal line with proper line number, document numbers, and default values based on existing lines. Replicates journal page behavior for API-driven journal line creation with appropriate field inheritance.
  • EnsureGenJnlBatchExists(TemplateNameTxt: Text[10]; BatchNameTxt: Text[10]): Ensures that a general journal batch exists for the specified template and batch names, creating it if necessary. Provides batch creation with default configuration for API scenarios requiring guaranteed batch availability.
  • GetBatchNameFromId(JournalBatchId: Guid): Code[10]: Retrieves journal batch name from the specified system ID for API lookup scenarios. Provides system ID to batch name resolution for API integration requirements.

Plus 3 local procedures.

Triggers

OnRun

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: "Library API - General Journal"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources