codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 375 "Bank Acc. Entry Set Recon.-No."

Base Application · Microsoft.Bank.Reconciliation

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Codeunit 1252 "Match Bank Rec. Lines" (calls, 11 links)Match Bank Rec. LinesReport 1496 "Suggest Bank Acc. Recon. Lines" (calls)Suggest Bank Acc. Recon. LinesTable 274 "Bank Acc. Reconciliation Line" (calls)Bank Acc. Reconciliation Line

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

Properties

Property Value
Permissions TableData “Bank Account Ledger Entry” = rm, TableData “Check Ledger Entry” = rm

Events published

  • OnBeforeApplyEntries(var BankAccReconciliationLine: Record "Bank Acc. Reconciliation Line"; var BankAccountLedgerEntry: Record "Bank Account Ledger Entry"; var Relation: Option "One-to-One","One-to-Many") (integration): Integration event raised before applying bank reconciliation entries to ledger entries. Allows subscribers to perform custom validation or modifications before the application process begins.
  • OnAfterApplyEntries(var BankAccReconciliationLine: Record "Bank Acc. Reconciliation Line"; var BankAccountLedgerEntry: Record "Bank Account Ledger Entry"; var Relation: Option "One-to-One","One-to-Many") (integration): Integration event raised after successfully applying bank reconciliation entries to ledger entries. Allows subscribers to perform post-application processing, logging, or additional updates.
  • OnBeforeModifyBankAccReconLine(var BankAccReconciliationLine: Record "Bank Acc. Reconciliation Line") (integration): Integration event raised before modifying a bank reconciliation line. Allows subscribers to perform custom validation or field updates before the line is saved.
  • OnBeforeRemoveApplication(var BankAccountLedgerEntry: Record "Bank Account Ledger Entry") (integration): Integration event raised before removing an application from a bank account ledger entry. Allows subscribers to perform custom validation or pre-processing before application removal.
  • OnAfterRemoveApplication(var BankAccountLedgerEntry: Record "Bank Account Ledger Entry") (integration): Integration event raised after successfully removing an application from a bank account ledger entry. Allows subscribers to perform post-removal processing, cleanup, or additional updates.
  • OnAfterSetReconNo(var BankAccountLedgerEntry: Record "Bank Account Ledger Entry") (integration): Integration event raised after successfully setting a reconciliation number on a bank account ledger entry. Allows subscribers to perform post-assignment processing, notifications, or additional updates.
  • OnAfterRemoveReconNo(var BankAccountLedgerEntry: Record "Bank Account Ledger Entry"; Test: Boolean) (integration): Integration event raised after successfully removing a reconciliation number from a bank account ledger entry. Allows subscribers to perform post-removal processing, auditing, or cleanup operations.

Procedures

  • ApplyEntries(var BankAccReconLine: Record "Bank Acc. Reconciliation Line"; var BankAccLedgEntry: Record "Bank Account Ledger Entry"; Relation: Option "One-to-One","One-to-Many","Many-to-One"): Boolean: Applies bank reconciliation lines to bank account ledger entries with the specified relationship type. Manages the matching process for different reconciliation scenarios including one-to-one, one-to-many, and many-to-one relationships. Updates applied amounts, reconciliation numbers, and maintains …
  • SetLineCount(NewLineCount: Integer): Sets the line count for tracking purposes during the reconciliation process. Used internally to maintain counters for multi-line reconciliation operations.
  • SetLineNumber(NewLineNumber: Integer) (internal): Sets the line number for internal tracking during reconciliation operations. Used to maintain state information for complex matching scenarios.
  • SetAppliedAmount(NewAppliedAmount: Integer) (internal): Sets the applied amount for tracking during reconciliation operations. Maintains running totals of amounts applied in multi-entry matching scenarios.
  • RemoveApplication(var BankAccLedgEntry: Record "Bank Account Ledger Entry"): Removes applications for bank account ledger entries that participate in many-to-one matching relationships. Handles the cleanup of multiple bank reconciliation lines that were matched to a single ledger entry, updating applied amounts, entry counts, and removing associated payment matching details.
  • SetReconNo(var BankAccLedgEntry: Record "Bank Account Ledger Entry"; var BankAccReconLine: Record "Bank Acc. Reconciliation Line"): Assigns reconciliation statement numbers to bank account and check ledger entries. Validates entry states, handles corrupt statement statuses, and updates both bank account and associated check ledger entries with statement information for proper reconciliation tracking.
  • RemoveReconNo(var BankAccLedgEntry: Record "Bank Account Ledger Entry"; var BankAccReconLine: Record "Bank Acc. Reconciliation Line"; Test: Boolean): Removes reconciliation statement numbers from bank account and check ledger entries. Clears statement status, statement numbers, and line numbers from both bank account and associated check ledger entries to revert them to an open, unreconciled state.

Plus 4 local procedures.

Triggers

OnRun

Called by

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: "codeunit", object_name: "Bank Acc. Entry Set Recon.-No."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources