Codeunit 1700 "Exp. Launcher Pos. Pay"
Base Application · Microsoft.Bank.PositivePay
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Bank.PositivePay · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Check Ledger Entry |
| Permissions | TableData “Check Ledger Entry” = rimd, TableData “Data Exch.” = rimd |
Procedures
PositivePayProcess(var CheckLedgerEntry: Record "Check Ledger Entry"; ShowDialog: Boolean): Executes the complete positive pay export process for the specified check ledger entries.
Plus 4 local procedures.
Triggers
OnRun
Relations
- runs on Table 272 “Check Ledger Entry”
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 1711 “Positive Pay Export Mgt” (5 calls:
ProcessDetails → ExportDataExchToFlatFile,ProcessFooters → ExportDataExchToFlatFile,ProcessFooters → PreparePosPayFooter, …) - Codeunit 1708 “Exp. Writing Pos. Pay” (2 calls:
PositivePayProcess → CleanUpPositivePayWorkTables,PositivePayProcess → ExportPositivePay) - Codeunit 1709 “Exp. External Data Pos. Pay” (1 call:
PositivePayProcess → CreateExportFile) - Codeunit 419 “File Management” (1 call:
PositivePayProcess → ServerTempFileName)
Called by
- Table 272 “Check Ledger Entry” (1 call:
ExportCheckFile → (object))
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: "Exp. Launcher Pos. Pay"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.