reportFinanceofficial - Microsoftderived - from the source, no model text

Report 8612 "Create Vendor Journal Lines"

Base Application · Microsoft.Finance.GeneralLedger.Journal

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 230 "GenJnlManagement" (calls)GenJnlManagement

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

Properties

Property Value
Caption Create Vendor Journal Lines
UsageCategory Tasks
ApplicationArea Basic, Suite

Procedures

  • Initialize(var StdGenJnl: Record "Standard General Journal"; JnlBatchName: Code[10]): Initializes vendor journal line creation process with standard journal configuration and batch settings. Sets up journal template context, batch assignment, and line numbering for vendor-specific journal line generation.
  • InitializeRequest(DocumentTypesFrom: Option; PostingDateFrom: Date; DocumentDateFrom: Date): Initializes report request parameters for document type, posting date, and document date configuration. Sets up basic posting parameters for vendor journal line creation from external calls or batch processing.
  • InitializeRequestTemplate(JournalTemplateFrom: Text[10]; BatchNameFrom: Code[10]; TemplateCodeFrom: Code[20]): Initializes report template configuration parameters for vendor journal creation with template and batch settings. Sets up the target journal destination and optional standard template for vendor transaction automation.
  • SetDefaultDocumentNo(NewDocumentNo: Code[20]): Sets the default document number to be applied to created vendor journal lines when no document number is specified. Provides centralized document numbering control for bulk vendor journal line creation and vendor transaction management.

Plus 5 local procedures.

Triggers

OnPostReport

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: "report", object_name: "Create Vendor Journal Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources