Codeunit 2624 "Stat. Acc. Jnl. Line Post"

StatisticalAccounts · Microsoft.Finance.Analysis.StatisticalAccount · BC29-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnBeforeInsertStatisticalLedgerEntry(var StatisticalAccJournalLine: Record "Statistical Acc. Journal Line"; var StatisticalLedgerEntry: Record "Statistical Ledger Entry") (integration)
• OnAfterTransferStatisticalAccJournalLineTo(var StatisticalAccJournalLine: Record "Statistical Acc. Journal Line"; var StatisticalLedgerEntry: Record "Statistical Ledger Entry") (integration)

Procedures

• PostLine(var StatisticalAccJournalLine: Record "Statistical Acc. Journal Line") (internal)
• PostLine(var StatisticalAccJournalLine: Record "Statistical Acc. Journal Line"; var NextEntryNo: Integer; TransactionNumber: Integer) (internal)
• TransferStatisticalAccJournalLineTo(var StatisticalAccJournalLine: Record "Statistical Acc. Journal Line"; var StatisticalLedgerEntry: Record "Statistical Ledger Entry")

Triggers

OnRun

Relations

• runs on Table 2631 “Statistical Acc. Journal Line”

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.

• Codeunit 2627 “Stat. Acc. Telemetry” (1 call: PostLine → LogPostingUsage)

Called by

• Codeunit 2626 “Stat. Acc. Post. Batch” (1 call: ProcessLines → PostLine)

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: "Stat. Acc. Jnl. Line Post"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.