Codeunit 16 "Gen. Jnl.-Show CT Entries"
Base Application · Microsoft.Finance.GeneralLedger.Journal
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Finance.GeneralLedger.Journal · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Gen. Journal Line |
Events published
OnBeforeOnRun(var GenJournalLine: Record "Gen. Journal Line"; var IsHandled: Boolean)(integration): Integration event raised before executing the main credit transfer entry display logic. Enables custom handling or bypassing of credit transfer entry display functionality.OnSetFiltersOnCreditTransferEntryOnCaseElse(var GenJournalLine: Record "Gen. Journal Line"; var CreditTransferEntry: Record "Credit Transfer Entry"; var FoundCorrespondingLedgerEntry: Boolean)(integration): Integration event raised for custom account types not handled by standard customer, vendor, or employee logic. Enables extension of credit transfer entry filtering for additional account types.
Procedures
SetFiltersOnCreditTransferEntry(var GenJournalLine: Record "Gen. Journal Line"; var CreditTransferEntry: Record "Credit Transfer Entry"): Sets appropriate filters on credit transfer entries based on journal line account type and application details. Configures filters for account type, applies-to information, currency code, and ledger entry matching.
Triggers
OnRun
Relations
- runs on Table 81 “Gen. 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.
- Page 1206 “Credit Transfer Reg. Entries” (1 call:
OnRun → (object))
Called by
- Table 81 “Gen. Journal Line” (2 calls:
DrillDownExportedAmount → SetFiltersOnCreditTransferEntry,TotalExportedAmount → SetFiltersOnCreditTransferEntry) - Codeunit 367 “CheckManagement” (1 call:
RemoveCreditTransfers → SetFiltersOnCreditTransferEntry)
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: "Gen. Jnl.-Show CT Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.