Codeunit 1708 "Exp. Writing Pos. Pay"

Base Application · Microsoft.Bank.PositivePay · BC23-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• ExportPositivePay(DataExchEntryCodeDetail: Integer; DataExchEntryCodeFooter: Integer; Filename: Text; DataExchEntryCodeFooterArray: array[100] of Integer): Exports the positive pay data by combining header, detail, and footer records into the final file format.
• CleanUpPositivePayWorkTables(DataExchEntryCodeHeaderArray: array[100] of Integer; DataExchEntryCodeDetailArray: array[100] of Integer; DataExchEntryCodeFooterArray: array[100] of Integer): Cleans up temporary positive pay work tables after the export process is complete.

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.

• Codeunit 1700 “Exp. Launcher Pos. Pay” (2 calls: PositivePayProcess → CleanUpPositivePayWorkTables, PositivePayProcess → ExportPositivePay)

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. Writing Pos. Pay"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.