codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 1213 "Pmt. Export Cust. Ledger Check"

Base Application · Microsoft.Bank.Payment

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 21 "Cust. Ledger Entry" (relates to)Cust. Ledger EntryCodeunit 1208 "Pmt Export Mgt Cust Ledg Entry" (calls)Pmt Export Mgt Cust Ledg Entry

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

Properties

Property Value
TableNo Cust. Ledger Entry

Events published

  • OnPmtExportCustLedgerCheck(var CustLedgerEntry: Record "Cust. Ledger Entry") (integration): Integration event that allows customization of customer ledger entry validation logic for payment export. This event is raised during customer ledger entry validation to allow external extensions to add custom validation rules.

Procedures

6 local procedures, no public ones.

Triggers

OnRun

Relations

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: "Pmt. Export Cust. Ledger Check"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources